Hey Thomas :)
Quoting Thomas Schwinge (2015-02-20 23:38:49)
> On Fri, 20 Feb 2015 22:44:17 +0100, I wrote:
> > As in the subject, and see the attached QEMU screenshot. Has something
> > been changed in the boot process ("startup" is new; Justus CCed ;-) just
/hurd/startup is the new /hurd/init, I merely renamed it to a) reflect
the fact that it is the server speaking the startup protocol, and b)
to free /hurd/init for a roughly sysvinit-compatible minimal init.
> > in case) that would cause this non-root filesystem to be mounted that
> > early, so that e2fsck can't then process it anymore? "Erich" has not
> > needed a lot of e2fscks, but if my memory serves me right, this used to
> > work "until recently".
I must say, you have by far the oddest naming policies :D
> By the way, the same problem also happens if /dev/hd2, "erich" is clean.
> Only then you can't nicely see in the log how early it's being mounted,
> which definitely is too early:
> [...]
>
> I'd expect PID 91, the ext2fs for /dev/hd2 (who (only) serves home
> directories via a /home -> media/erich/home symlink) to appear only after
> the console or other login things have been started. Inside /etc/,
> /media/erich is only mentioned in /etc/fstab. Yet, something must be
> touching the /media/erich node early. I have not yet made an attempt to
> disentangle the boot process, waiting if someone has an idea already.
>
> > $ showtrans /media/erich
> > /hurd/ext2fs --no-atime /dev/hd2
> > $ grep hd2 < /etc/fstab
> > /dev/hd2 /media/erich ext2 defaults 0 2
That's odd. Though I must admit I do not use passive translator
records to mount disks. Maybe the Debian init scripts just aren't
compatible with that. Personally I'd be ok with that.
Justus
