Re: [9fans] p9p vac/vacfs compatibility: uid/gid, ctime, 9P2000.L, 9pserve

[David du Colombier <0intro@gmail.com>]

> When I use 9pfuse to mount the file system, I get a little further:
>
> lrw-rw---- 1 root root        6 Mar 10  2005 video ->
> -rw-rw---- 1 root root        3 Mar 10  2005 video10
>
> The symbolic links show up as links, but with the null string ("") as
> target.  The Linux kernel interperets null symlinks to mean "./",
> causing all the links to refer to the directory in which they
> reside. :( The device files still present as ordinary files with a
> size of 3 bytes. Running "readlink" on the symbolic links always
> returns the null string.

OK, I found the problem. At least concerning 9pfuse and symlink.

9pfuse read the symlink target from Dir.ext (libc.h), which is
a 9P2000.u extension. But 9P2000.u is not supported anymore.
It should read the symlink target from the data instead.

I've something that work, but it's ugly.

As supposed, other Unix special files don't seem to be currently
supported by 9pfuse at all.

Honestly, I've been using Vac for years and I never
encountered the need to store Unix special files.

If you want to back up a full Unix file system to Venti,
you should simply use vbackup(8).

--
David du Colombier