> The "clean" (or "fast", however you want to look at it) solution is to
> let the dentry layer do the work for you. For that you would need
> aliasing support for all dentries. Offhand, I don't see how you'd
> support a read-only option with a pure dentry scheme. In fact, I see
> the read-only requirement as a strong reason for doing it the "hard"
> way (i.e. not enhancing the VFS interface). A read-only lofs is great
> for securing ftp and tftp servers.
Erm... Says who that intermediate dentries in stack can't have inodes
associated with them? Sure, pure vnode scheme is nice, but our one is also
usable.
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/