> Hi, > > - Sysv is already mostly parallelized. It takes 26 > seconds which is better than I expected. Actually, as > I understand, on this single-cpu machine the overhead > of context switching is so high that xinetd and cups > would probably start faster if they were not > parallelized with X. > - Idea: sshd is the only service that uses xinetd. > Standalone sshd would probably boot faster? This > computer connects to the Internet using a modem, I > don't even own a network card. Therefore I probably > don't need sshd at all.
Isn't xinetd startup of ssh disabled by default, in favour of starting as a daemon? > - While I'm at it, I also don't need netfs, nfslock > (thus portmap) If you want to use NFS you need them all. If you don't use NFS, 'urpme nfs-utils-client' or whatever it is. AFAIK you need portmap for fam to work? > or tmdns. Isn't it possible to disable > these services if no NIC is detected during > installation? Also since this is a desktop pc i don't > need apmd. And you don't want to be able to use the sleep/wake buttons on your keyboard ;-). > Can't this also be detected? > - I just can't understand why kde takes so long to > start!??!? Unfortunately, gnome isn't much better. The > "loading session" part in kde can be accellerated by > disabling KOrganizer (if someone wants to use it, > he/she can find it in the menus) I don't think korganiser has a huge impact, and it's point is to remind you, not to tell you the things you want to be reminded of when you remember to run it, and it can easily be disabled. > - Idea: postpone cups and scannerdrake startup for 60 > seconds to give desktop a chance to start and avoid > unnecessary context switching. Yay, then Mandrake samba print servers will now only be usable 2 minutes after having fully booted ... since we HUP samba a minute after starting it to give CUPS time to pick up all the printers (I haven't removed this since samba-2.2.8a can't update the printers automatically as it is supposed to - it worked in 2.2.7a though ...). > It's very unlikely that > someone would like to print or scan something in the > first 60 seconds? Maybe on a desktop, and I guess it's not too bad on a server unless there's an MCSE driving it ... > The same trick could be used for > crond and atd I believe. > > What do you think? Should I apply these optimizations > to my Pc? will anything burn up (except the lg cd-rom) > ;) I wonder if the 23s to start KDE can be reduced significantly by pre-linking? BTW, Windows (even Windows 2000) shuts down very quickly (ie usually < 5 seconds on my laptop), and I think the margin is greater on shutdown ... Regards, Buchan
