G'day ovedpo15,

Your post is missing a lot of information. For example:

This makes it very difficult to give you an answer. It would have been much better if you had provided an SSCCE.

From what you've written, I get the impression that you're not experiencing problems with Graph; your issue seems to be how to collect the data to populate the graph. The following script collects the data you've indicated you need. It is barebones but does the job assuming a Unix-like OS; you may want to use other modules (e.g. File::Find, File::Spec, etc.) but I'll leave that entirely up to you. 

#!/usr/bin/env perl

use strict;
use warnings;
use autodie;

use constant BASE_DIR => '/home/ken/tmp/pm_11143050';
use constant {
    LEN_BASE_DIR => length BASE_DIR,
    FS_DIR => BASE_DIR . '/fs',
};

use Cwd 'abs_path';
use Data::Dump;

my %fs_map;
walk_fs(FS_DIR, \%fs_map);
dd \%fs_map;

sub walk_fs {
    my ($path, $fs_map) = @_;

    opendir(my $dh, $path);

    while (readdir $dh) {
        next if /^\.{1,2}$/;
        my $entry = "$path/$_";
        my $fs_path = fs_path($entry);

        if (-f $entry) {
            $fs_map->{$fs_path} = [file => []];
        }
        elsif (-l $entry) {
            $fs_map->{$fs_path} = [link => [canon_path($entry)]];
        }
        elsif (-d $entry) {
            if (exists $fs_map->{fs_path($path)}) {
                push @{$fs_map->{fs_path($path)}[1]}, canon_path($entr
+y);
            }

            $fs_map->{$fs_path} =  [dir => []];

            walk_fs($entry, $fs_map);
        }
        else {
            warn "IGNORED '$entry': not a plain file, link or director
+y.\n";
        }
    }

    closedir $dh;

    return;
}

sub fs_path {
    return substr $_[0], LEN_BASE_DIR;
}

sub canon_path {
    return substr abs_path($_[0]), LEN_BASE_DIR;
}

[download]

I created the following directory structure for testing. It contains normal files, directories, subdirectories, links, links to links, and even a fifo. 

ken@titan ~/tmp/pm_11143050
$ ls -lR fs
fs:
total 0
drwxr-xr-x+ 1 ken None 0 Apr 19 03:49 a
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 t

fs/a:
total 1
prw-rw-rw-  1 ken None 0 Apr 19 03:49 a_named_pipe
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 b
-rw-r--r--  1 ken None 0 Apr 19 02:36 d
lrwxrwxrwx  1 ken None 5 Apr 19 02:42 r -> b/c/z
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 u
lrwxrwxrwx  1 ken None 8 Apr 19 02:35 x -> ../a/b/c

fs/a/b:
total 0
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 c
-rw-r--r--  1 ken None 0 Apr 19 02:37 e
lrwxrwxrwx  1 ken None 1 Apr 19 02:40 q -> y
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 v
lrwxrwxrwx  1 ken None 1 Apr 19 02:37 y -> .

fs/a/b/c:
total 0
-rw-r--r--  1 ken None 0 Apr 19 02:38 f
lrwxrwxrwx  1 ken None 7 Apr 19 02:40 p -> ../../x
drwxr-xr-x+ 1 ken None 0 Apr 19 02:46 w
lrwxrwxrwx  1 ken None 6 Apr 19 02:38 z -> ../../

fs/a/b/c/w:
total 0

fs/a/b/v:
total 0

fs/a/u:
total 0

fs/t:
total 0

[download]

Here's the output: 

ken@titan ~/tmp/pm_11143050
$ ./mapfs.pl
IGNORED '/home/ken/tmp/pm_11143050/fs/a/a_named_pipe': not a plain fil
+e, link or directory.
{
  "/fs/a"       => ["dir", ["/fs/a/b", "/fs/a/u"]],
  "/fs/a/b"     => ["dir", ["/fs/a/b/c", "/fs/a/b/v"]],
  "/fs/a/b/c"   => ["dir", ["/fs/a/b/c/w"]],
  "/fs/a/b/c/f" => ["file", []],
  "/fs/a/b/c/p" => ["link", ["/fs/a/b/c"]],
  "/fs/a/b/c/w" => ["dir", []],
  "/fs/a/b/c/z" => ["link", ["/fs/a"]],
  "/fs/a/b/e"   => ["file", []],
  "/fs/a/b/q"   => ["link", ["/fs/a/b"]],
  "/fs/a/b/v"   => ["dir", []],
  "/fs/a/b/y"   => ["link", ["/fs/a/b"]],
  "/fs/a/d"     => ["file", []],
  "/fs/a/r"     => ["link", ["/fs/a"]],
  "/fs/a/u"     => ["dir", []],
  "/fs/a/x"     => ["link", ["/fs/a/b/c"]],
  "/fs/t"       => ["dir", []],
}

[download]

So, %fs_map holds all of the data that you indicated you need. I'll leave you to use this to populate your graph.

— Ken

In reply to Re: Graph which represents the filesystem by kcott
in thread Graph which represents the filesystem by ovedpo15

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.