plymouth retain-splash

Muhammad Ammar mammar at gmail.com
Fri Oct 8 03:37:40 PDT 2010


Hi,


When i tried to install the latest(initscripts-9.21) initscripts from source
code, i am getting the following error:

mv: `//etc/sysconfig/network-scripts/ifup' and `//sbin/ifup' are the same
file

Any Idea about this?


Regards,


On Mon, Oct 4, 2010 at 10:33 PM, Ray Strode <halfline at gmail.com> wrote:

> Hi,
>
> On Mon, Oct 4, 2010 at 2:40 AM, Muhammad Ammar <mammar at gmail.com> wrote:
> > Hi All,
> > I am a user of Fedora 13. Whenever i reboot or shutdown the system,
> > following things happen
> > 1. contol switched to console showing messages (e.g, Stopping HAL daemon:
> [
> > OK ] etc. )
> > 2. then contol shows a plymouth splash of fedora
> > What i needed is, do not perform the step 1 just perform step 2 everytime
> i
> > reboot or shutdown the system.
> I believe I fixed this after fedora 13:
>
>
> http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=9d1c6c1e3bf176d3f89de4ec5551f9960c4986ed
>
>
> ---8<------------------------------------------------------------------------------------------------------------------------------
> Improve shutdown splash screen reliability
>
> Right now the splash screen and rc script are
> racing with each other so you occasionally see a few
> shutdown messages before plymouth is up.
>
> This commit ensures proper synchronization between prefdm,
> plymouthd, and the rc script.
>
> It does this by
>
> 1) fully stopping prefdm before letting rc start
> 2) fully starting plymouth before letting rc start
> 3) if prefdm is running (e.g. runlevel 5), waiting until it
>   is fully stopped before starting plymouthd
> 4) if prefdm is not running (e.g. runlevel 3), starting
>   plymouthd right away
>
> One bit of complication in this commit is the "splash
> manager".  It's a layer of indirection needed to handle the
> conditional mentioned in 3) and 4).
>
> There's no way within an upstart job file to say "start
> after the prefdm "stopped" event only if prefdm is not already
> stopped". We really need this to effectively happen, though,
> because if prefdm isn't in the process of stopping (because
> it was never started in the first place), it will never emit
> the stopped event and blocking for an event that never comes
> mean shutdown would never start.
>
> The splash manager checks if prefdm is already running and
> uses that information to emit an appropriate event that the
> plymouth-shutdown job can key of off.
>
> Note, one implication of 4) is we are showing plymouth when
> shutting down from runlevel 3 now.  This is a change in
> behavior, but makes sense, since we show plymouth when
> starting up into runlevel 3.
>
> ----------------------->8-------------------------------------------------
>
> --Ray
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/plymouth/attachments/20101008/adf3ffd1/attachment.html>


More information about the plymouth mailing list