Re: Installing plymouth
On Wed, Jan 30, 2019 at 03:13:52PM +0100, Bastian Blank wrote: > systemd got two output mechanisms: status and log. > > log goes to the journal, but can also go via kmsg and the console. To the log goes all messages that are not startup status messages. So for example start and stop messages after the boot process finished. > status is only active on boot, before the gettys are active and the > output is cleared. The status output are the colorful start, failure and timeout messages during boot. They only go to the primary console right now, so the serial console. If I install plymouth and don't configure it any further on Buster, those status messages are sent to all consoles. So it may make sense to install it. The virtual console is cleared imediately before starting the getty, so it's use as status output is limited to error scenarious. Also I don't know if the output of for example cloud-init will show up there as well. Regards, Bastian -- Where there's no emotion, there's no motive for violence. -- Spock, "Dagger of the Mind", stardate 2715.1
Status of Debian accounts and legal agreements with cloud providers
Hi Jimmy, Hi Luca During out spring last october you agreed on handling accounts and legal agreements with cloud providers for Debian in your position as representatives of SPI. As cloud team we agreed that we would like to provide Buster already within those new agreements. In the time since the sprint no information about the current state or a timeline for those agreements where posted ever. Also my contact at Microsoft reported at least in december that no additional communication happened. Now we are past our initial deadline of transition freeze two weeks ago. What did happen on this matter? How do we want to go forward? Regards, Bastian [Cc leader@ as this affects legal agreements of Debian with outsiders] -- Landru! Guide us! -- A Beta 3-oid, "The Return of the Archons", stardate 3157.4
Re: Installing plymouth
On Wed, Jan 30, 2019 at 02:25:20PM +0100, Thomas Goirand wrote: > On 1/30/19 1:45 PM, Bastian Blank wrote: > > On Wed, Jan 30, 2019 at 12:47:01PM +0100, Thomas Goirand wrote: > >> To get systemd to log on all tty (ie: tty0 and ttyS0), plymouth is > >> needed. So, my proposal is to get plymouth installed by default on our > >> images, with the "nosplash" option on the kernel command line (so that > >> plymouth doesn't display a splash screen). > > I tried that and don't see any difference. Please describe in more > > detail what the expected behaviour is. > If you put systemd.show_status=true in the kernel command line, and if > there's: > console=tty0 console=ttyS0 > then systemd will only print to ttyS0 unless plymouth is installed > (though I am setting it up with "nosplash text" on the kernel command > line so it doesn't bother). "systemd.show_status=true" modifies the status output, not the log. Also on is the default and only overriden by "quiet". "nosplash" disables all plymouth services, see debian/patches/0005-cmdline.patch in the plymouth source. > >> Any objection? Or would you guys want this only in the OpenStack image? > > Yes. I don't see how it should do what you want. > And now? Well, it would be nice if you tried to explain what you are trying to accomplish or wanted to see. systemd got two output mechanisms: status and log. log goes to the journal, but can also go via kmsg and the console. status is only active on boot, before the gettys are active and the output is cleared. Regards, Bastian -- Each kiss is as the first. -- Miramanee, Kirk's wife, "The Paradise Syndrome", stardate 4842.6
Re: Installing plymouth
On 1/30/19 1:45 PM, Bastian Blank wrote: > On Wed, Jan 30, 2019 at 12:47:01PM +0100, Thomas Goirand wrote: >> To get systemd to log on all tty (ie: tty0 and ttyS0), plymouth is >> needed. So, my proposal is to get plymouth installed by default on our >> images, with the "nosplash" option on the kernel command line (so that >> plymouth doesn't display a splash screen). > > I tried that and don't see any difference. Please describe in more > detail what the expected behaviour is. If you put systemd.show_status=true in the kernel command line, and if there's: console=tty0 console=ttyS0 then systemd will only print to ttyS0 unless plymouth is installed (though I am setting it up with "nosplash text" on the kernel command line so it doesn't bother). Maybe the issue is only with Stretch though, I haven't tested with Buster. >> Any objection? Or would you guys want this only in the OpenStack image? > > Yes. I don't see how it should do what you want. And now? Cheers, Thomas Goirand (zigo)
Re: Installing plymouth
On Wed, Jan 30, 2019 at 12:47:01PM +0100, Thomas Goirand wrote: > To get systemd to log on all tty (ie: tty0 and ttyS0), plymouth is > needed. So, my proposal is to get plymouth installed by default on our > images, with the "nosplash" option on the kernel command line (so that > plymouth doesn't display a splash screen). I tried that and don't see any difference. Please describe in more detail what the expected behaviour is. > Any objection? Or would you guys want this only in the OpenStack image? Yes. I don't see how it should do what you want. Bastian -- Prepare for tomorrow -- get ready. -- Edith Keeler, "The City On the Edge of Forever", stardate unknown
Re: Installing plymouth
On Wed, Jan 30, 2019 at 12:47:01PM +0100, Thomas Goirand wrote: > To get systemd to log on all tty (ie: tty0 and ttyS0), plymouth is > needed. systemd logs to the kernel log. Or do you mean status output? > Note: logging to all tty is needed, as the tty0 port is used for the VNC > console, there's also a ttyS0 console, and we need logging to ttyS0 in > order for "openstack console log show" to work. Well, tty0 is not a log. Bastian -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, "Metamorphosis", stardate 3219.8
Installing plymouth
Hi, To get systemd to log on all tty (ie: tty0 and ttyS0), plymouth is needed. So, my proposal is to get plymouth installed by default on our images, with the "nosplash" option on the kernel command line (so that plymouth doesn't display a splash screen). Any objection? Or would you guys want this only in the OpenStack image? Note: logging to all tty is needed, as the tty0 port is used for the VNC console, there's also a ttyS0 console, and we need logging to ttyS0 in order for "openstack console log show" to work. Cheers, Thomas Goirand (zigo)
