On Tuesday 28 October 2003 20:14, Vedran Ljubovic wrote: > Hi, > > > Recently there were some articles on Slashdot > proposing alternative boot procedures. Most of them > advocate parallelizing of SysV-init tasks. Motivated > by these I've decided to make a detailed analysis of > boot procedure and see how can I make it faster. > > I have an oldish PC that can run most modern software > fast enough. This is a vanilla Mdk 9.2 install and I > use the auto-login feature with KDE. Complete time > from pressing enter in lilo to a usable desktop is > exactly 81 seconds. On this same computer Win98 is > usable in around 35 seconds (I did some tweaking > though). > > Here is a detailed account of the boot procedure. I > made it using logs and a stopwatch. It should clearly > point the likely targets for optimization. > > [ skip ]
> - Do we need to run depmod if no new modules are > installed (many ways to check)? i think it use -A switch and so is runned only if it should. > - I just can't understand why kde takes so long to > start!??!? This has to do with the disk. a faster disk help moe than a faster processor. Maybe using -Os could help, but recompiling to test is maybe too much. > - Idea: postpone cups and scannerdrake startup for 60 > seconds to give desktop a chance to start and avoid > unnecessary context switching. It's very unlikely that > someone would like to print or scan something in the > first 60 seconds? The same trick could be used for > crond and atd I believe. So, the first 60 secondes would be as unusable as on windows ? -- Michaël Scherer
