Pathname Semantics with //
Quoted 12 lines
Jamie Lokier
Quoted 2 lines · David Dabbs
Shooting from the hip here. If we want to unify namespaces in a UNIXy
way,
Quoted 3 lines
what if we make the VFS expose all the non-file "protocol" namespaces through one mount point, device node or whatever. A filesystem, perhaps something built using FiST
[http://www.filesystems.org/], would "handle"
Quoted 12 lines
a
Quoted 1 line
protocol. Another, perhaps preferred, option is to steer in the
direction of
Quoted 3 lines
Plan9, where ftp can be mounted and handled by a user-space filesystem, ftpfs.
See http://plan9.bell-labs.com/magic/man2html/4/ftpfsYou can already do it, something like this:
mkdir /http:; mount none /http: -t uservfs -o view=http mkdir /ftp:; mount none /ftp: -t uservfs -o view=ftp
Quoted 6 lines
I don't see any compelling reason to make "//" special for this. However, if there is such a reason, then you could just mount protocol handlers on "//http:" and so on, and make "//" a normal directory with a special name.
-- Jamie
Jamie, we _definitely_ agree, except apps that want to create links to URLs will prepend one slash to the URL instead of two. Is your reference to uservfs a "foo" reference or do you mean
http://sourceforge.net/projects/uservfs/? It looks a little dusty. But we are pulling in the same direction.
The /file: node could simply be a symlink. Thus we have
cd /
ln -s / file:
mkdir http:; mount none /http: -t uservfs -o view=http mkdir ftp:; mount none /ftp: -t uservfs -o view=ftp #etc...
Pathnames would be resolved with the existing code in namei.c. I can understand mounting a URL whose protocol looks like a fs tree (e.g. ftp), but http? Namei() parses the pathname one component at a time, checks the dcache, and goes to the fs when that fails. Let's trace through how a URL might get resolved.
ln -s /http://sourceforge.net/projects/uservfs cat uservfs
Pathname would be resolved as
/http:
sourceforge.net/
projects/
uservfsI need to look closer at namei (or the uservfs code if it really supports a view=http). As long as a fs can generate meaningful, stateful values in response to VFS calls to real_lookup(), then this may work.
David
Quoted 11 lines · David Dabbs
Quoted 11 lines
Jamie Lokier
Quoted 3 lines · David Dabbs
Shooting from the hip here. If we want to unify namespaces in a UNIXy
Quoted 33 lines
Quoted 6 lines
way,
Quoted 3 lines
what if we make the VFS expose all the non-file "protocol" namespaces through one mount point, device node or whatever. A filesystem, perhaps something built using FiST
[http://www.filesystems.org/], would "handle"
Quoted 24 lines
a
Quoted 3 lines
protocol. Another, perhaps preferred, option is to steer in the
direction of
Quoted 4 lines
Plan9, where ftp can be mounted and handled by a user-space filesystem, ftpfs. See http://plan9.bell-labs.com/magic/man2html/4/ftpfs
You can already do it, something like this:
mkdir /http:; mount none /http: -t uservfs -o view=http mkdir /ftp:; mount none /ftp: -t uservfs -o view=ftp
I don't see any compelling reason to make "//" special for this.
However, if there is such a reason, then you could just mount protocol handlers on "//http:" and so on, and make "//" a normal directory with a special name.-- Jamie
Jamie, I like your approach, and I think it should go into LSB and be used by all distros. It improves closure in the OS.
Quoted 45 lines
Jamie, we _definitely_ agree, except apps that want to create links to URLs will prepend one slash to the URL instead of two. Is your reference to uservfs a "foo" reference or do you mean
http://sourceforge.net/projects/uservfs/? It looks a little dusty. But we are pulling in the same direction.The /file: node could simply be a symlink. Thus we have
cd /
ln -s / file:
mkdir http:; mount none /http: -t uservfs -o view=http mkdir ftp:; mount none /ftp: -t uservfs -o view=ftp #etc...Pathnames would be resolved with the existing code in
namei.c. I can understand mounting a URL whose protocol looks like a fs tree (e.g. ftp), but http?Namei()parses the pathname one component at a time, checks the dcache, and goes to the fs when that fails. Let's trace through how a URL might get resolved.ln -s /http://sourceforge.net/projects/uservfs cat uservfs
Pathname would be resolved as
/http: sourceforge.net/ projects/ uservfsI need to look closer at namei (or the uservfs code if it really supports a view=http). As long as a fs can generate meaningful, stateful values in response to VFS calls to
real_lookup(), then this may work.David