Bug#769907: general: non-sysvinit init systems are made of fail
On 11/18/2014 03:50 AM, Michal Suchanek wrote:
> With
> current sysvinit the serial console is also used as main but
> sysvinit-core does not produce any messages on tty0 whatsoever and so
> does not mislead the user into thinking that useful boot progress
> feedback can be obtained on that terminal.
This is because bootlogd only supports a single output at a time, and
therefore only outputs on the *last* occurrence of the console= boot
parameter. The patch that I pointed to resolves this by adding support
for outputting to multiple consoles. If you want it for Wheezy, I have
it here (as I use it for my unofficial OpenStack backport repo, it's in
that repository):
http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/
On 11/18/2014 03:50 AM, Michal Suchanek wrote:
> systemd on the other hand
> prints selected messages on both terminals but most messages go only
> to the main serial terminal.
Yet another "WTF", and probably if you ask upstream, they'll find a good
reason for that, and will tag +wontfix if you submit a bug... I'd be
curious to know what's the (twisted) reasoning behind. Maybe because
upstream considers that ttyS0 is for debugging, which IMO is wrong (it
should be considered as a normal console, just like tty0, and debug
messages should also be printed to tty0 anyway). BTW, it's good to know
that we have a way to debug things with systemd, thanks for the tip! :)
On 11/18/2014 03:50 AM, Michal Suchanek wrote:
> For completeness I tried upstart and it produces two error messages on
> both terminals and 6 progress messages on serial terminal never giving
> a login prompt on either. This is unexpected as it used to work on
> wheezy.
I would strongly suggest that you file bugs against both systemd and
upstart then! (and *not* using the "general" pseudo-package...)
Cheers,
Thomas Goirand (zigo)
Reply to: