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

[Henrique de Moraes Holschuh]

On Wed, 25 Apr 2012, Carsten Hey wrote:
> * Roger Leigh [2012-04-24 16:31 +0100]:
> > On Tue, Apr 24, 2012 at 02:55:55PM +0200, Michael Prokop wrote:
> > > * Carsten Hey [Mon Apr 23, 2012 at 01:07:17 +0200]:
> > >
> > > > Please ignore noauto sysfs entries in fstab.  Not mounting sysfs to /sys
> > > > if such a line is present in fstab leads to udev not starting.
> > >
> > > > If this bug is not fixed, this problems will show up after upgrading to
> > > > Wheezy on some systems.
> > > [...]
> > >
> > > FTR: According to my tests, bootstrapping wheezy with
> > > grml-debootstrap 0.49 fails WRT /sys mounting and bootstrapping
> > > whezzy with grml-debootstrap 0.50 (just released and uploaded, it
> > > does not add a noauto sysfs line any longer) succeeds.
> >
> > So does this problem still need addressing in initscripts?
> 
> The problem is that installing Squeeze via grml-debootstrap perfectly
> works and after upgrading to Wheezy udev will not start.  A wrongly
> generated /etc/fstab can't be fixed for existing systems by releasing
> a fixed version of a tool that is only run once during installation.

The correct thing to do would be to fix the broken /etc/fstab, then...

> initscripts is currently respecting what you obviously *think* are the
> wishes of the admin.  Since /sys is nowadays mounted on most or all

Which means we're following the principle of least surprise...

And you can mount /sys more than once, in weird places for whatever
reasons.  Those could conceivably be "noauto", so we'd have to ignore
noauto only on lines that attempt to mount the special filesystems where
we'd expect them to be mounted in the first place.

> In my opinion, the underlying problem is that there is no clear and
> distribution independent semantic of noauto when used in a fstab entry
> for those standard virtual file systems.  If there would be such a clear

The other distros ignore "noauto"?  Or do them ignore /etc/fstab
entirely for the special filesystems?  I suspect it is the later.

-- 
  "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