On Tue, 18 Apr 2000, Jeremy Fitzhardinge wrote:
> I added this in order to support the common case of /net, where an NFS
> server may export a tree of filesystems which autofs should treat as a
> unit, atomically mounting and umounting. In other words, it treats all
> filesystems mounted under /net/hostname as being a single tree, which is
> why it traverses across mountpoints during the expire test.
OK, care to describe the setup in details?
> In your example with /home, it will fail to remount ~/cdrom, because
> you've manually interfered with its turf. It's really a matter of either
> accepting the automation or doing things manually. If you want to mount
> the cdrom in autofs controlled space, you should get autofs to manage it.
Except that you may very well have autofs-served $HOME by external policy.
In that case you are pretty much stuck.
> It could be solved, I suppose, by having automount keep a list of the
> filesystems its responsible for, but that has the risk of getting out of
> sync with the system state and confusing things (a chronic problem with
> Sun's automounter). One of the design criteria was insisting that
> automount not keep private state, but be able to adapt to the system
> state.
Eww... Why not pass the flag to mount and let the kernel remember that
these mountpoints are volatile?
-
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 : Sun Apr 30 2000 - 21:00:16 EST