Hi, On Mon, Feb 24, 2014 at 10:09 AM, Dr. Werner Fink <werner@xxxxxxx> wrote: > With a step further such a patch would allow to have both a splash > screen on the virtual consoles and boot messages on all other consoles. Sure, I think that's actually the best answer. I've done some changes to make it easier to implement that in the code recently, but it needs a bit more work before I can change the behavior to act that way. > It is not that unusal to use a serial console out there, is it :) It's certainly not unusual, but what is somewhat unusual is wanting to see a splash and wanting to see a serial console at the same time. Most people who look at serial consoles, don't really care to look at splash screens, too. They have the console because they want their messages, and "fit and finish" during boot just isn't a priority relative to getting detailed output. There are definitely exceptions, of course, which is why I think what you propose above is the best medium-term way to go. To be honest, with boots on modern hardware routinely taking less than 5 seconds these days, plymouth is becoming less and less important overall. > Beside this IMHO plymouth may add O_NOCTTY to all open() of the > devices combinded with setsid() after its fork() to become a daemon :) I don't think plymouth does the wrong things here. If you want to discuss it further, though, take it to the plymouth mailing list (or bugs.freedesktop.org) and we can talk about it. > The question rises if upstream of plymouth will read this? I'm the primary plymouth author/maintainer upstream. --Ray -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html