At Fri, 30 Nov 2012 12:30:13 +0100, Damian Ivanov wrote:
So, as Raymond suggested, a part of the current bootsplash package can be split or merge into another for keeping only the tty background part, I suppose. Why not work with upstream plymouth to get that feature into plymouth?
Because the implementation has basically nothing to do with plymouth. The picture on tty is handled in the kernel bootsplash patch. Takashi
2012/11/30 Takashi Iwai <tiwai@suse.de>:
At Fri, 30 Nov 2012 11:28:10 +0100, Frederic Crozat wrote:
Le vendredi 30 novembre 2012 à 11:22 +0100, Takashi Iwai a écrit :
At Fri, 30 Nov 2012 11:08:55 +0100, Frederic Crozat wrote:
Le vendredi 30 novembre 2012 à 10:50 +0100, Raymond Wooninck a écrit :
On Friday 30 November 2012 10:46:08 Takashi Iwai wrote: > > The regression in o:F and SLES will be: semitranslucent > > background picture on tty1 when text is shown is gone. > > I have not told your product managers yet, but bootsplash > > (the .rpm and the implementation) is important for branding. > > Technically seen, keeping the background picture on tty1 while showing > bootsplash with plymouth shouldn't be too hard. But they are > exclusive currently in the package level, unfortunately.
I guess the better approach would be to split off from bootsplash the functionality that creates this background picture on tty1 and then package it within the branding packages ? Or we can make it even part of plymouth.
From what I understand of the way KMS is handled, it would require plymouth (or something) to keep running or at least, keep a FD open (and I'm not sure how the tty would react).
I'm also not strongly convinced branding tty is THAT important.
Why plymouth is convincing, then? :)
because it is maintained, cross-distro and allow flicker-free transition to X.
It is maintained, but its implementation is... Well let's stop ranting. FWIW, the bootsplash kernel patch has been maintained over 13 years until now.
"cross-distro" could be a gain, but only if it reduces the actual maintenance load.
The flicker-free transition to X is nothing new, it was already preset at the time of Meego. Basically it's no feature of plymouth but rather a new feature to X. The feature we added was dropped meanwhile since the patch wasn't accepted to X at that time. Now, by some reason, a similar patch was merged, so we are here. One good step forward.
When I was speaking of branding tty, I was of course speaking of the virtual console, once the boot is finished.
Yes, and my point is we can manage the tty background picture easily together with plymouth (suppose plymough doesn't do anything stupid). But in the package level, it's handled as conflicted because the tty background picture handling is currently always tied with kernel bootsplash, and plymouth doesn't cope with others (even X).
So, as Raymond suggested, a part of the current bootsplash package can be split or merge into another for keeping only the tty background part, I suppose.
Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org