Your message dated Thu, 24 Oct 2019 13:17:35 +0200
with message-id <d52e882b-6144-2280-c854-e7671737d...@debian.org>
and subject line Re: Bug#943392: Output to both tty0 and ttySX shouldn't be
using plymouth
has caused the Debian Bug report #943392,
regarding Output to both tty0 and ttySX shouldn't be using plymouth
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
943392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 242-7
Severity: important
Dear Systemd maintainers,
If one wants to have the boot process displayed on both tty0 and on the
serial port (ttyS1 in my case) AND have the services show, then the way
to go is to install Plymouth, eventually with the "nosplash" option on
the command line to avoid displaying a logo.
For example, the grub command line would be:
nosplash text console=tty0 console=ttyS1,115200 earlyprintk=ttyS1,115200
consoleblank=0 systemd.show_status=true
Unfortunately, this concept is broken by design. Indeed, plymouth is far
from being the first .service to start, and as a consequence, a lot of
the output is just missed on tty0.
If there is a way to configure systemd so that it output behaves correctly
(and by correctly, I mean as sysv-rc did for DECADES), please let me know,
and my appologies in advance. Though I've searched the web for a long time,
and what I describe is I believe correct. If I'm correct, then please
report the problem upstream and get this fixed.
Thanks for maintaining systemd,
Cheers,
Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Am 24.10.2019 um 12:09 schrieb Thomas Goirand:
> Package: systemd
> Version: 242-7
> Severity: important
>
> Dear Systemd maintainers,
>
> If one wants to have the boot process displayed on both tty0 and on the
> serial port (ttyS1 in my case) AND have the services show, then the way
> to go is to install Plymouth, eventually with the "nosplash" option on
> the command line to avoid displaying a logo.
>
> For example, the grub command line would be:
>
> nosplash text console=tty0 console=ttyS1,115200 earlyprintk=ttyS1,115200
> consoleblank=0 systemd.show_status=true
>
> Unfortunately, this concept is broken by design. Indeed, plymouth is far
> from being the first .service to start, and as a consequence, a lot of
> the output is just missed on tty0.
>
> If there is a way to configure systemd so that it output behaves correctly
> (and by correctly, I mean as sysv-rc did for DECADES), please let me know,
> and my appologies in advance. Though I've searched the web for a long time,
> and what I describe is I believe correct. If I'm correct, then please
> report the problem upstream and get this fixed.
>
You already raised this upstream.
https://github.com/systemd/systemd/issues/3403
The kernel documentation is pretty clear afaics: outputting to
/dev/console will only print to the last console that is specified on
the kernel command line.
Apparently some distros (like SuSE) used a software like blogd to work
around this limitation. If you do that, I don't see why you cant use
plymouth (which is usually started in the the initramfs and thus already
running when systemd is started).
I see no new arguments presented here, so closing the bug report.
If you can actually show that and *how* this actually worked in sysv-rc
without additional tools, feel free to reopen (and/or follow-up upstream).
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
--- End Message ---
