Bug#769907: general: non-sysvinit init systems are made of fail

[Michal Suchanek <hramrach@gmail.com>]

On 21 November 2014 06:38, Thomas Goirand <zigo@debian.org> wrote:
> On 11/19/2014 06:14 PM, Michal Suchanek wrote:
>> On 18 November 2014 00:52, Thomas Goirand <zigo@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/
>>>
>>
>> Hello,
>>
>> is the key for the juno archive available somewhere?
>
> You can install this:
> http://archive.gplhost.com/debian/pool/juno-backports/main/g/gplhost-archive-keyring/gplhost-archive-keyring_20100926-1_all.deb

Indeed. That, however, does not verify the archive before installing
packages from it.

>
>> bootlogd(8) page does not mention any way to select log console other
>> than bootlogd using the kernel commandline to determine console
>> device.
>
> Installing it isn't enough, you also need to set the kernel command line
> parameter to:
>
> console=tty0 console=ttyS0,115200
>

Of course. That's what I have and the Jessie bootlogd  does not give
messages on both consoles.

Or was this bit of openstack support not pushed to jessie?

Thanks

Michal