[systemd-devel] How to make debug-shell more usable?

Michael Biebl mbiebl at gmail.com
Sun Mar 1 13:20:10 PST 2015

2015-03-01 12:17 GMT+01:00 Lennart Poettering <lennart at poettering.net>:
> On Thu, 26.02.15 20:22, Michael Biebl (mbiebl at gmail.com) wrote:
>> 2015-02-26 1:12 GMT+01:00 Zbigniew Jędrzejewski-Szmek <zbyszek at in.waw.pl>:
>> > On Thu, Feb 26, 2015 at 01:04:55AM +0100, Michael Biebl wrote:
>> >> 2015-02-26 0:55 GMT+01:00 Michael Biebl <mbiebl at gmail.com>:
>> >> > To reproduce the problem, add e.g. a non-existing device to /etc/fstab
>> >> >
>> >> > The "Waiting for device to show up ..." messages are printed all over tty9.
>> > We made rescue.service conflict with emergency.service for similar
>> > reasons some time ago. We could do something similar here. OTOH,
>> > killing debug-shell.service to start emergency.service does not seem
>> > useful. So maybe we could hardcode not starting emergency.service in case
>> > debug-shell.service is already running.
>> Hm, I think it's fine to start emergency.service, but it should be
>> started on a defined tty, not simply the current active one.
> No. /dev/console is the only right thing this early in the boot, since
> it might point to anything, including serial ports, all depending on
> kernel cmdline params. Hardcoding a VT is not an option.

I wasn't arguing for hard-coding the VT.

Using /dev/console to find out the initial tty is fine. I just would
remember which tty it points to and use that then for the complete
boot process.

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

More information about the systemd-devel mailing list