Edgar Fuß <[email protected]> writes:
>> Maybe try and have amd(8) or automount(8) mount /private/etc
>> et.al? And use map entries fetched from NIS or Hesiod?
> And who starts amd or configures the network etc.?
The message I replied to presented the idea that the information
in /etc/fstab could be combined with information from a directory
service (networked, presumably). In order for this to happen,
the OS must already be running from a NFS-mounted root (since it
is a diskless system), and thus the kernel must already have
established some basic net connectivity.
Mounting file systems from /etc/fstab usually happens via the
rc.d framework, and that's also responsible for starting the
automounters. Both amd and automount can make use of remote
directory services in the form of NIS (both) and Hesiod (amd).
So, instead of inventing a new directory service for /etc/fstab
information, I tried to suggest that one should explore the
existing technology and see if it's fit for purpose (or could be
made to work).
This is probably moot anyway, since Ignatios Souvatzis described
a much better starting point in a later message.
-jarle
--
"Meh, good enough."
-- Mediocrates
