On 18 November 2014 00:52, Thomas Goirand <z...@debian.org> wrote: > 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/
This is nice but I wonder if it resolves the problem. Do fsck messages go through bootlogd? Also iirc bootlogd is an optional addon that logs the init messages into a file which is by default not installed. > > 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! :) I think that the reason is that ttyS0 comes later on kernel commandline and all init systems here agree that it should make it the main console. The problem is probably impedance mismatch when integrating several init bits. I suspect that systemd dutifully logs its own messages to all consoles but sysv-rc only logs to the main console. > > I would strongly suggest that you file bugs against both systemd and > upstart then! (and *not* using the "general" pseudo-package...) > Which one would it be in this case? Thanks Michal -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caomqctq-xjca+sedur4vneh1w-gvgm+zuh1uxmq5bduuu0s...@mail.gmail.com
