[Pkg-sysvinit-devel] New initscript to do all bind and loop mounts?

[Henrique de Moraes Holschuh]

On Tue, 24 Jan 2006, Thomas Hood wrote:
> The initscripts in the initscripts package are limited in purpose: they mount enough
> filesystems, using the information in /etc/fstab, to make the basic things available,
> including /usr and /var.
> 
> What's needed for more advanced setups is a program that can sort out the dependencies.
> Fortunately, such programs already exist.  automounters.  automounters have their own
> configuration files written in a language that is adequate to what automounters have
> to do.
> 
> Taking care of arbitrary filesystem setups should not be considered to be a
> responsibility of initscripts.  If someone's /usr or /var is a bind mount or a loop
> mount then this should to be regarded as a custom setup.

I disagree.  IMHO anything that can be correctly represented in /etc/fstab
AND does not depend on the network should be supported.  In fact, that's
what we have right now, and I for one use it extensively to setup
system-wide bind mounts for example.   Why break that?   As long as there is
properly ordering in /etc/fstab, it works.

Now, there's a *second* question: why do we special-case NFS?  We could
simply have a mount-networked-filesystems script, that again uses
/etc/fstab, and tries to mount everything in there that is auto and not
mounted yet.   That would take care of all sane setups (and of nfs too).


And surprisingly enough, it wouldn't even violate KISS :-)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh