SUSE Rolls Out New Version Of Their In-Kernel Boot Splash Screen

[phoronix]

Phoronix: SUSE Rolls Out New Version Of Their In-Kernel Boot Splash Screen

Back in October I wrote about SUSE working on a new, in-kernel bootsplash project. That work has yet to be mainlined but it looks like it's still on track for going upstream in the future with the latest version now being released that addresses issues uncovered during review...

http://www.phoronix.com/scan.php?page=news_item&px=SUSE-Kernel-Bootsplash-V2

[davidbepo]

will be used by manjaro too

[tomtomme]

Kernel developers should the dev_info function instead of dev_err, then messages do not disturb boot. I made patches for removing stupid acpi and pci errors.

seriously? Since when is it useful to post kernel patches into a forum?

[tildearrow]

Typo:

alternative to the user-space Plytmouth and other programs.

[starshipeleven]

Kernel developers should the dev_info function instead of dev_err, then messages do not disturb boot. I made patches for removing stupid acpi and pci errors.

debianxfce should the patch to upstream kernel mailing list instead of Phoronix forums, then messages do not disturb unrelated people.

[starshipeleven]

Eagerly awaiting for this on Tumbleweed. Good to see that SUSE is still fighting the good battle.

[Charlie68]

We hope it will be soon introduced! When I install Linux, it's the first thing they ask me, "why those messages?" on the last kernels the thing is even worse, boot errors unimportant but annoying. Good work openSUSE!

[expectATIon]

I hope to see this in fedora soon. Plymouth is unreliable

[cyring]

Sounds nice for a Linux desktop but a pain for servers remote administration: pure vga is more efficiente than vesa fb.

[starshipeleven]

Sounds nice for a Linux desktop but a pain for servers remote administration: pure vga is more efficiente than vesa fb.

No offence, but why would you enable a boot splash that silences boot output on a server (or headless system)?

I personally like to see all text scrolling by when my stuff is booting because I can spot issues that way, and a sysadmin should probably prefer to do the same for the same reasons. I'm also a "sysadmin" to some extent but I rarely manage linux servers, or servers that are running on actual server hardware in a remote location, for that matter.