Hi,<div><br></div><div><br></div><div>When i tried to install the latest(<span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre; ">initscripts-9.21</span>) initscripts from source code, i am getting the following error:</div> <meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div><div>mv: `//etc/sysconfig/network-scripts/ifup' and `//sbin/ifup' are the same file</div></div><div><br></div><div>Any Idea about this?</div> <div><br></div><div><br></div><div>Regards,</div><div><br><br><div class="gmail_quote">On Mon, Oct 4, 2010 at 10:33 PM, Ray Strode <span dir="ltr"><<a href="mailto:halfline@gmail.com">halfline@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br> <div class="im"><br> On Mon, Oct 4, 2010 at 2:40 AM, Muhammad Ammar <<a href="mailto:mammar@gmail.com">mammar@gmail.com</a>> wrote:<br> > Hi All,<br> > I am a user of Fedora 13. Whenever i reboot or shutdown the system,<br> > following things happen<br> > 1. contol switched to console showing messages (e.g, Stopping HAL daemon: [<br> > OK ] etc. )<br> > 2. then contol shows a plymouth splash of fedora<br> > What i needed is, do not perform the step 1 just perform step 2 everytime i<br> > reboot or shutdown the system.<br> </div>I believe I fixed this after fedora 13:<br> <br> <a href="http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=9d1c6c1e3bf176d3f89de4ec5551f9960c4986ed" target="_blank">http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=9d1c6c1e3bf176d3f89de4ec5551f9960c4986ed</a><br> <br> ---8<------------------------------------------------------------------------------------------------------------------------------<br> Improve shutdown splash screen reliability<br> <br> Right now the splash screen and rc script are<br> racing with each other so you occasionally see a few<br> shutdown messages before plymouth is up.<br> <br> This commit ensures proper synchronization between prefdm,<br> plymouthd, and the rc script.<br> <br> It does this by<br> <br> 1) fully stopping prefdm before letting rc start<br> 2) fully starting plymouth before letting rc start<br> 3) if prefdm is running (e.g. runlevel 5), waiting until it<br> is fully stopped before starting plymouthd<br> 4) if prefdm is not running (e.g. runlevel 3), starting<br> plymouthd right away<br> <br> One bit of complication in this commit is the "splash<br> manager". It's a layer of indirection needed to handle the<br> conditional mentioned in 3) and 4).<br> <br> There's no way within an upstart job file to say "start<br> after the prefdm "stopped" event only if prefdm is not already<br> stopped". We really need this to effectively happen, though,<br> because if prefdm isn't in the process of stopping (because<br> it was never started in the first place), it will never emit<br> the stopped event and blocking for an event that never comes<br> mean shutdown would never start.<br> <br> The splash manager checks if prefdm is already running and<br> uses that information to emit an appropriate event that the<br> plymouth-shutdown job can key of off.<br> <br> Note, one implication of 4) is we are showing plymouth when<br> shutting down from runlevel 3 now. This is a change in<br> behavior, but makes sense, since we show plymouth when<br> starting up into runlevel 3.<br> <br> ----------------------->8-------------------------------------------------<br> <font color="#888888"><br> --Ray<br> </font></blockquote></div><br></div>