[Pkg-sysvinit-devel] Re: New initscript to do all bind and loop
jdthood at yahoo.co.uk
Wed Jan 25 11:12:55 UTC 2006
On Tue, 2006-01-24 at 14:40 -0200, Henrique de Moraes Holschuh wrote:
> 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.
Well, there is no reason to break what already works. What I am saying is that
initscripts shouldn't try to support every imaginable arrangement of filesystems.
If people want to set up bind mounts and loopback mounts on network filesystems
or on each other then either they should add their own initscripts or install
some optional package that supports this. The optional package would include
its own initscripts and whatever else was necessary to fsck, mount and unmount
the extra filesystems.
> 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).
> Because of people with /my/chroot mounted on NFS and a
> local /my/chroot/proc and /my/chroot/var mounted on top of that.
> I agree that there should be a way to sort out the dependencies. In the
> above situation I don't think automount would work (.. reliably.)
> The network filesystems in /etc/fstab SHOULD all be marked as _netdev,
> and mount/umount should be extended to understand that if /my/chroot
> doesn't get mounted neither should it even try to mount /my/chroot/proc.
> Ofcourse you could also mark /my/chroot/proc as _netdev but that's ugly.
Here we face the problem that the util-linux maintainers, both upstream and
Debian, are not terribly keen to apply patches. Perhaps we should propose
a merger of the Debian sysvinit and util-linux teams.
More information about the Pkg-sysvinit-devel