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

[Michal Suchanek <hramrach@gmail.com>]

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?

I see announcements but not a way to obtain the key beforehand.
http://blog.szemtsov.net/?p=827 http://thomas.goirand.fr/blog/?p=220

Also the latter announcement mentions that the openstack is available
in jessie but installing bootlogd in jessie does *not* result in
messages being echoed to both consoles.

bootlogd(8) page does not mention any way to select log console other
than bootlogd using the kernel commandline to determine console
device.

Thanks

Michal