Fastboot Initscript Patches

z4ziggy · 2004-12-09 03:26:34

~6s is a lot of time... maybe its worth it. wonder if someone can post diff/patches to test such a script.

punkrockguy318 · 2004-12-09 03:44:05

My initscripts weren't really geared towards login managers: They were geared towards console login. You can just put kdm as the first daemon and boot up very quickly. But for the people who login via console, you need to wait for EVERY daemon to load.. which is a pain.

Shofs · 2004-12-16 03:31:35

It would be cool to apply the info from this thread to this.

Bootchart is a tool for performance analysis and visualization of the GNU/Linux boot process. Resource utilization and process information are collected during the boot process and are later rendered in an SVG or PNG encoded chart.

dtw · 2004-12-16 04:13:01

If the initscripts are to be rehashed to include this rather excelent idea then, please, PLEASE can support for bootsplash and fbsplash be included in the initscripts!

It is extremely frustrating to be able to set up all the bootsplash/fbsplash stuff but then be stuck becuase you can't patch the initscripts - surely catering for the users that want to use boot/fb splash is ok - it's not like it is going to massively bloat the initscripts at ALL!

Also, something that still remains and issue - if you update initscripts with the -U option then it WILL overwrite all the files - whether you have set them as to "do not remove under any circumstance" in rc.conf - if you then reinstall the old package without copying your own files back from the pacsaves they will be overwritten and you will lose them.

Should I submit bug reports/requests for this? Would i receive support - not meaning to thread hijack too much!

Hum · 2004-12-16 14:18:33

dibblethewrecker wrote:

If the initscripts are to be rehashed to include this rather excelent idea then, please, PLEASE can support for bootsplash and fbsplash be included in the initscripts!
It is extremely frustrating to be able to set up all the bootsplash/fbsplash stuff but then be stuck becuase you can't patch the initscripts - surely catering for the users that want to use boot/fb splash is ok - it's not like it is going to massively bloat the initscripts at ALL!
Also, something that still remains and issue - if you update initscripts with the -U option then it WILL overwrite all the files - whether you have set them as to "do not remove under any circumstance" in rc.conf - if you then reinstall the old package without copying your own files back from the pacsaves they will be overwritten and you will lose them.
Should I submit bug reports/requests for this? Would i receive support - not meaning to thread hijack too much!

add
"NoUpgrade = etc/rc.sysinit" to your etc/pacman.conf file that should prevent pacman from overwriting your files.

dtw · 2004-12-17 06:46:30

Thanks HUM - i did that - i said i already did that - and it doesn't work - sorry PunkRockGuy

loserMcloser · 2004-12-18 05:33:51

Here is a simple fastboot patch that I worked up. It allows you to specify in rc.conf which daemons to load up in the background during boot by prefixing them with an @ symbol. Note: this patch is totally separate from punkrockguy's patch, do not use both of them.

It is available here. As with punkrockguy's patch, apply it from the src directory of the initscripts package with a

patch -p1 < /path/to/bkgdDaemons.patch

Example use: my DAEMONS list in rc.conf now looks like

DAEMONS=(syslog-ng @hotplug network @netfs @sshd portmap nfslock @nfsd @acpid @crond @fam)

Warning: If you boot up into xdm/kdm/gdm and your video card requires certain kernel modules to be loaded (eg. nvidia), you may need to explicitly add those modules to the MODULES list in rc.conf if you background the hotplug daemon. This is so that the modules are loaded and initialized in time for X to start up.

Cover-My-Butt-Warning: Use this patch at your own risk. This patch messes with the scripts that boot up / shutdown your computer and as such could result in a non-booting system. Back up your init scripts before using. Make sure you have a rescue disk on hand.

punkrockguy318 · 2004-12-18 13:31:03

loserMcloser wrote:

Here is a simple fastboot patch that I worked up. It allows you to specify in rc.conf which daemons to load up in the background during boot by prefixing them with an @ symbol. Note: this patch is totally separate from punkrockguy's patch, do not use both of them.
It is available here. As with punkrockguy's patch, apply it from the src directory of the initscripts package with a
patch -p1 < /path/to/bkgdDaemons.patch
Example use: my DAEMONS list in rc.conf now looks like
DAEMONS=(syslog-ng @hotplug network @netfs @sshd portmap nfslock @nfsd @acpid @crond @fam)
Warning: If you boot up into xdm/kdm/gdm and your video card requires certain kernel modules to be loaded (eg. nvidia), you may need to explicitly add those modules to the MODULES list in rc.conf if you background the hotplug daemon. This is so that the modules are loaded and initialized in time for X to start up.
Cover-My-Butt-Warning: Use this patch at your own risk. This patch messes with the scripts that boot up / shutdown your computer and as such could result in a non-booting system. Back up your init scripts before using. Make sure you have a rescue disk on hand.

Sounds very nice. I tried something like this at first, but I didn't think of that simple solution. I had a DAEMONS array and a DAEMONSB array. That made things complicated. This sounds like a very good idea! Good work

aCoder · 2004-12-18 22:12:43

I like the '@' prefix idea as well. It seems consistent with the '!' to disable a daemon.

dp · 2004-12-18 23:52:08

aCoder wrote:

I like the '@' prefix idea as well. It seems consistent with the '!' to disable a daemon.

i second this ... it looks very clean

kakabaratruskia · 2004-12-19 01:13:06

I like this idea, cause I like to know if some daemons like the network are running.

Dusty · 2004-12-19 05:31:17

I vote for it too.

ganlu · 2004-12-20 05:17:19

Aye, it could be better.

iBertus · 2004-12-20 05:55:46

This is a really interesting idea. With work this could become the best startup system found in any linux distro and would serve to cancel one of the few advantages that Windows has on the desktop.

FoPref · 2004-12-21 01:44:40

advantage? Arch boots without backgrounding in 15 seconds, can Windows ever do that *with* backgrounding?

iBertus · 2004-12-21 03:10:52

Win Xp on my Athlon XP w/ nForce2 and software IDE drivers boots to login in about 5 sec. not counting BIOS screens.

FoPref · 2004-12-21 11:21:35

nice. how long does arch need on your system?

iBertus · 2004-12-21 14:43:15

Just booted up for the first time in awile, but timed it at approx 12-15 sec. not counting BIOS screens but including the kernel stuff. I should point out that the Windows install, which is now destroyed in favor of a totally Arch system, had been there for quite awhlie and the prefetching mombo-jumbo was doing it's job pretty well. I havn't tried the new background loading initscripts so that startup time is with a default Arch init loading 6-7 daemons.

I am by no means disappointed with the performance of Arch considering I don't reboot this machine now nearly as often as I did with the Windows install and so I've probably already made that boot time back 10-fold in just not having to reboot. My interest in this is that I feel that it would be cool to be more stable than Windows but also faster on the reboot . 8)

I assume that people needing an instant response from their machine on boot could just use suspend to disk and be done with it. I don't power my machine down unless I have too for some reason beyond my control.

loserMcloser · 2004-12-21 15:22:47

oops, didn't notice rc.single needed to be edited too. updated patch is in same location, here.

phrakture · 2004-12-21 17:45:02

nice patch, i'll apply it now and try it when i get home

I vote for this added into the initscripts package (email it to judd).. and I agree the prefix thing seems more arch centric to goalong with the "!" prefixing....

iBertus · 2004-12-21 21:10:41

I also think the @ prefixing is a great idea. Perhaps this should be included with the default initscripts, but should it be enabled by default? Too bad we can't make intelligent daemon loaders that wait until the required things are loaded before trying to load one in the background (ie. fam and network).. Does this make sense?

Anywho, great work!

loserMcloser · 2004-12-21 22:12:41

It's easy to have it disabled by default -- just don't put any @'s in the DAEMONS line of the vanilla rc.conf. 8)

Pajaro · 2004-12-22 02:10:51

@ it's good.

I would have made it in my patch if I'd know enough bash programming.

I don't think it is really usefull, but we loose nothing having it avaible.

I made my initscripts load in background some time ago because nfsd spend more than a minute to be [DONE], so I really felt the difference.

That would have been great to simply add an @ instead off having to modify the initscripts by myself (that would have been great for other people, not for me: i've loved to learn the simplicity of linux).

phrakture · 2004-12-22 15:17:58

I would also like to suggest backgrounding the shared link update too... as that's the biggest hog (though it'd be better to have pacman run it after each install instead of on boot)

z4ziggy · 2004-12-22 15:54:54

actually, ldconfig is already running after each pacman package install... im guessing they'd put ldconfig in the rc.sysinit to avoid the initial ldconfig execution delay on pacman execution... this makes pacman looks faster
i myself removed it toally from rc.sysinit, since pacman will execute it anyway once its needed... who needs the 20 second delay at each startup.. 8)

Arch Linux

#26 2004-12-09 03:26:34

Re: Fastboot Initscript Patches

#27 2004-12-09 03:44:05

Re: Fastboot Initscript Patches

#28 2004-12-16 03:31:35

Re: Fastboot Initscript Patches

#29 2004-12-16 04:13:01

Re: Fastboot Initscript Patches

#30 2004-12-16 14:18:33

Re: Fastboot Initscript Patches

#31 2004-12-17 06:46:30

Re: Fastboot Initscript Patches

#32 2004-12-18 05:33:51

Re: Fastboot Initscript Patches

#33 2004-12-18 13:31:03

Re: Fastboot Initscript Patches

#34 2004-12-18 22:12:43

Re: Fastboot Initscript Patches

#35 2004-12-18 23:52:08

Re: Fastboot Initscript Patches

#36 2004-12-19 01:13:06

Re: Fastboot Initscript Patches

#37 2004-12-19 05:31:17

Re: Fastboot Initscript Patches

#38 2004-12-20 05:17:19

Re: Fastboot Initscript Patches

#39 2004-12-20 05:55:46

Re: Fastboot Initscript Patches

#40 2004-12-21 01:44:40

Re: Fastboot Initscript Patches

#41 2004-12-21 03:10:52

Re: Fastboot Initscript Patches

#42 2004-12-21 11:21:35

Re: Fastboot Initscript Patches

#43 2004-12-21 14:43:15

Re: Fastboot Initscript Patches

#44 2004-12-21 15:22:47

Re: Fastboot Initscript Patches

#45 2004-12-21 17:45:02

Re: Fastboot Initscript Patches

#46 2004-12-21 21:10:41

Re: Fastboot Initscript Patches

#47 2004-12-21 22:12:41

Re: Fastboot Initscript Patches

#48 2004-12-22 02:10:51

Re: Fastboot Initscript Patches

#49 2004-12-22 15:17:58

Re: Fastboot Initscript Patches

#50 2004-12-22 15:54:54

Re: Fastboot Initscript Patches

Board footer