[Pkg-sysvinit-devel] Bug#670106: Bug#670106: initscripts: please ignore noauto sysfs entries in fstab

[Carsten Hey]

* Carsten Hey [2012-04-30 02:00 +0200]:
> * Roger Leigh [2012-04-29 23:19 +0100]:
> > I was just thinking, is there a way to detect if the system was
> > bootstrapped with grml-bootstrap compared with plain debootstrap? If
> > that was the case, we could put a specific check for that in, and
> > clean up the fstab if so.  It would mean everyone else would get
> > the configuration preserved, and only the broken ones get updated,
> > which I think would be a reasonable compromise if possible.
>
> grml-debootstrap copies files into the chroot that is being created:
>
>   cp $VERBOSE $CONFFILES/chroot-script $MNTPOINT/bin/chroot-script
>   cp $VERBOSE $CONFFILES/config    $MNTPOINT/etc/debootstrap/
>
> ...
>
> If you choose this way of solving the issue, please drop us a mail so
> that we can look up if tests like the above would work with all relevant
> grml-debootstrap versions.

This still holds, if you think detecting grml-debootstrap'ed systems is
the way to go, please drop us a mail previously.  This would of course
not "fix" other systems with such a buggy fstab entry.

> > > > how do other distributions handle noauto in this situation?  Do they
> > > > respect it, ignore it, or not look at fstab at all?
> > >
> > > I know that at least some switched from requiring an /sys fstab entry to
> > > not requiring it, but I do not know what others do if there is still
> > > such a line.  This is what I meant by not being sure about the answers.
> > >
> > > Anyway, you seem to consider this questions to be important.  If you
> > > think that they are that important that the outcome of this discussion
> > > depends on it, I think the behaviour of other distributions can be
> > > investigated, it just will need some time.
> >
> > For current systems, I think it's useful to know what systemd and
> > upstart are doing.  systemd is simple enough to test on Debian;
> > for upstart we can look at Ubuntu.  Part of the reason for the mount
> > changes was to align the mount options with those used in the
> > initramfs (copied both ways, but mainly updating the initramfs with
> > the initscripts defaults), and also with systemd so that we have
> > consistent behaviour across all init systems and boot methods.
> > So if all the others choose to not respect noauto for specific
> > mounts, that's a point in favour of doing that.
>
> Being consistent to other init systems in Debian makes sense.  I'll send
> an other mail after knowing this.

I installed Fedora 16 (uses systemd as init and was released in November
2011) and the just released Ubuntu LTS (uses upstart) into a KVM
container and added a noauto sysfs line for /sys that matches (besides
noauto) their default mount options to /etc/fstab on both systems.

On both systems, /sys was mounted despite the noauto sysfs entry.

I don't know if upstart and systemd on Debian behave differently than on
their native distributions, but if they do, then I'd tend to consider
this derivation to be buggy unless there is a valid reason for it.


Regards
Carsten