Fwd: Re: Fwd: Re: A common VFS and a Common conf-system [Part II]

[gtg990h at mail.gatech.edu]

Quoting Dave Cridland <dave at cridland.net>:

> Everything else you say is implementation detail, precisely the same kind of
> erroneous argument (at this stage) as you're accusing Sean of. It doesn't
> matter, in principle, whether D-VFS mounts filesystems in the kernel, or
> whether the POSIX semantics rely on forwarding stuff via FUSE and similar to
> D-VFS.

Only theoretically. To the extent that the spec mandates things just not
possible on top of POSIX, the two cases become different. That said, I've
already told Sean that it's not really useful to harp on the specifics until we
see the real barriers POSIX puts up as D-VFS is implemented.
hat makes them any more unusual to handle in the kernel than, say, NTFS.

> You want an API that, when a process requests of D-VFS access to some file,
> D-VFS can essentially hand back a local filename - a sort of redirection.
> This would, presumably, always happen in the case of file scheme URIs
> referencing the local filesystem, but might also happen for WebDAV enabled
> "http" ones. Is that about right?

Or CIFS ones on SSH ones, or any of a number of others already supported by
various kernels.