On Mon, Feb 02, 2004 at 03:54:20PM -0800, Chris Wedgwood wrote:
> > You won't like it. Unix-based filesystems don't provide anything
> > special for translating an inode into a filename; you just have to
> > search the filesystem for the inode--and then you know the filename.
>
> Under Linux you could walk the dentries and get a usable path at the
> VFS layer. There is already code that does this.
You can't. To get a path you also need a vfsmnt.
> In fact, I was considering various ways to do something like dnotify
> that would give full path information via a magic network socket or
> something (exactly how it should work is still unclear to me,
> different permissions along the path might mean you aren't entitled to
> events you would otherwise get).
Again doesn't work. You can give the names of the directory entries
to dnotify (in fact I did a hack like that not long ago), but not
a full filename.
|