On Mon, Feb 22, 1999 at 05:02:01AM -0800, H. Peter Anvin wrote:
> Okay, I'm planning to do outline the basic data structures of autofs
> v4 over the next several days. Some features are already a given:
>
> * Multimounts/scaffolding (/net being a special case of this).
> * Arbitrary mount point topology, without needing the
> spawn-an-automounter hack.
> * Mounting-process information passed to daemon.
> * Most of the filesystem data will live in "ready-to-eat" kernel data
> structures (inodes, dentries) as opposed to separate backing store.
One thing that amd has that would be nice if autofs has is symlink mounts.
If for instance, you have two systems, fred and barney. Fred exports /pebbles
and /dino, while barney exports /bambam, you might want to have a centralized
mount point for all disks:
/mnt/pebbles
/mnt/bambam
/mnt/dino
If you were on fred, /mnt/pebbles would be a symlink to /pebbles, /mnt/dino
would be a symlink to /dino (yeah, direct mounts would be great, but they won't
be provided), and /mnt/bambam would be automounted from barney. Even nicer if
you could share autofs maps between systems like amd did (under amd, you could
say if the system name was fred, do symlinks, otherwise do nfs mounts).
--
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
[EMAIL PROTECTED], 617-354-5416 (office), 617-354-7161 (fax)
