On Tue, 30 May 2000, Alan Cox wrote:
> > filesystem. The latter is fs-dependent and opaque both for mount(8) and
> > sys_mount(). To add more fun, we'll need some syntax for loopbacks and
>
> Some of the MNT flags are not fs dependant - eg MS_RDONLY
To add more fun to that - here's the situation with parsing the mount
options:
-o remount => flag, magic changes of syntax.
-o noexec,nosuid,nodev => flags, should be actually per-mountpoint.
-o sync => flag, per-fs and pretty common. Otherwise VFS doesn't
care much.
-o mand => flag, per-fs and only VFS cares.
-o noatime,nodiratime => flag, per-fs
-o nosub => flag, not used anywhere
-t <type> => separate argument, chooses fs driver to talk with
-t bind => magic changes of syntax (my fault)
-o *quota => opaque, passed to fs drivers, ext2 explicitly
ignores, ufs flames, minix ignores everything, other filesystems don't
have quota support and either ignore or flame the options.
....
crapload of fs-specific (and not-too-specific - e.g. -o uid=...)
options, all parsed by fs drivers in all sorts of kludgy ways.
....
-o ???? => flag, allows multiple mounts
-o ???? or -? => flag, gives you union mount (two of them,
actually - depending on where we add a new component - head or tail).
-o ???? (or nothing) => flag, gives you mount-trap.
NFS mount => opaque data containing a binary structure.
ditto for other network filesystems, some of them with really
kinky tricks since connection is passed unauthorized.
We are stuck with existing interfaces, but I'm not happy about continuing
to kludge mount(2) one...
-
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/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:25 EST