Posts: 1,741
Joined: Jul 2006
Reputation:
4
2008-07-05, 18:22
(This post was last modified: 2008-07-05, 18:56 by BLKMGK.)
Doing some of these myself, concurrent booting of system processes on a multicore system sounds useful, I am also looking at nodiratime rather than noatime for safeties sake and feedback on that would be appreciated. turned off all sorts of things like the BT manager, print queue junk, and evolution alarm since I don't use this box for mail. Still looking through suggestions looking for those that won't impact general data safety but provide some boost. What I've done so far seems pretty safe I think and ought to help at least a little.
Edit: found a GUI utility names BUM that looks good for managing services and whatnot. Bootchart also looks interesting but I've not yet run it. with this you can see what part of your boot process is problematic and slowing things.
Posts: 29
Joined: May 2008
Reputation:
0
Use pure Upstart for booting. Seriously, when done properly you have a REAL concurrent boot setup, unlike the current sysv script emulation of upstart in Ubuntu. You can almost negate boot time when done properly. If oyu have a powerful enough machine you can have things start basically instantly in 2-3 waves.
--Core Functions
----Modules
----Any pre-reqs of proprietary driver modules
--User Daemons
----LIRC
----MySQL/Whatever else
----Xorg Pre-reqs
--User-Space Stuff
----Start X, directly starting XBMC
----whatever else
Naturally this is grossly over simplified. I used to do this on my old mythbox to accomplish about a 5 second boot. I Accomplished this by moving parts of the generic schema above to user-space scripts, excluding MySQL, which at the time needed to load well before the MythTV server for me. But that's probably of no matter to most people.
Things like Apache, and the like could easily be rigged via startx, although that's a little hackish.
My recommendation is look in /etc/init.d pick out what you really need (I STRONGLY suggest reading up first), plot it out on a web. And then clear (backup) event.d, and start working on your own script hierarchy. After doing this with the bare bones, you can start adding more and more to it. Note: it gets very complex very quickly, so start basic, and go from there.
Posts: 29
Joined: May 2008
Reputation:
0
Forgot to mention that essentially your event.d scripts, for simplicity, will just point to /etc/init.d/* for various start stop reload calls. Otherwise it would take a far greater amount of time... but probably you would also cut a few more seconds off going Pureblood upstart.
Posts: 854
Joined: Jan 2008
Reputation:
13
I have read it this morning and found some informative paragraph; I guess Ubuntu will go that way for 9.04.
Posts: 265
Joined: Dec 2007
Reputation:
4
s7mx1
Senior Member
Posts: 265
Seems like the forum discriminate the letter which stands just before y. In the previous post I was saying to start xwindows early.