the slow bootup of init is probably more of an issue on desktops or notebooks (i.e. machines used for personal purposes). since servers are expected to be mostly or always on, it isn't as much of a problem for people who run servers, or who rarely or never turn their machines off. the slow bootup time occurs once in a blue moon, so it impacts them less. alternative inits, like runit, tackle a different issue altogether. manageability of init scripts/configs for a variety of uses, becomes an important aspect of the init/startup script process.
however, speedups in the initialization process are definitely welcome. the biggest time sinks will probably be a) network initialization (especially if using dhcp), b) file system checks (really big time waster if you have humongous drives that _need_ to be checked). b was sort of solved by having journaled file systems that reduced or postponed time to check them. -- ___ \e/ .v. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
