Details about a ShadowFS Implementation

[Moritz Schulte]

Hello there,
Hi Thomas,

I'm interested in working on a first ShadowFS implementation. (Please
note that i'm very new in Hurd development)

I already made some thoughts about (a libnetfs based) ShadowFS, but
there are some points unclear to me. It would be great if you could
elaborate a bit on these details. Then it would be easier to
understand it and work on it.

example: settrans /shadowfs /hurd/shadowfs /path1 /path2

An implementation of netfs_get_dirents() seems quite trivial to me
(with my approach, but i don't know wether it's the right thing): I
just get a directory listing of the shadowed filesystems via
dir_readdir and "merge" them, while considering the "priority"
(specified via the "order") of the nodes.

But how should netfs_dir_lookup() be implemented? My main problem is
the following:

example: "/shadowfs/bar" is accessed.

IMHO, there need to be a way to get the _name_ ("bar"), not the node
struct, of the accessed directory. Then i can simply map it to the
shadowed filesystem by appending it to the names of these filesystems:
=> /path[12]/bar

Or is this a totally wrong approach?
How should it be done right?

Thanks,
                moritz
-- 
Moritz Schulte <moritz@chaosdorf.de> http://www.chaosdorf.de/moritz/
Debian/GNU supporter - http://www.debian.org/ http://www.gnu.org/
GPG fingerprint = 3A14 3923 15BE FD57 FC06  B501 0841 2D7B 6F98 4199