An extended discussion has transpired under the thread, "Is Linux Really Faster Than MS Windows." That discussion generally focused on the respective boot times of the two operating systems and was dismissed by operators of production server systems. But, one size does not fit everyone.
In the world of desktop and laptop system operators, and to those concerned with energy efficiency, differential boot times for the two operating systems is a meaningful topic. These systems are frequently shutdown by many users. Is there some impediment to participation of knowledgeable list subscribers in laying out a linux boot scenario comparable to that of a typical MS Windows desktop system? Continuing relative disregard of the concerns of these users is helping to sustain the dominance of MS Windows systems in many end user markets.
Google searches turned up several relevant messages that I have drawn on for some suggestions of programs that might be omited from the boot list. Others I have included out of curiosity and ignorance. System security concern is also a factor.
Assume a desktop sytem with stable hardware configuration used for general office applications with telephone connection for fax send/receive, cable/dsl modem for internet connection to permit web browsing, e-mail, and ftp file transfers. Sys op is security conscious, but really does not want to be a sys op. Fedora installation omitted server installation rpms, but otherwise has a default Fedora system boot process. Which bootup programs could be omitted to reduce boot time and strengthen system security while retaining full support for office productivity, number crunching, etc.?
Boot exclusion candidates: anacron atd crond isdn (if no isdn connection) kudzu mdmpd microc-ctl (assuming non-intel system) nfs, nfslock, netfs, autofs, xfs pcmcia (if not a laptop) portmap sendmail ssh
Apparently, each of the above programs can be eliminated from boot startup by deleting the symlink files in /etc/rc.d/rc3.d & rc5.d. Are there strong reasons to not remove any of the above from boot startup?
Are there additional programs that could be dropped from boot startup without affecting the functionality of the SOHO type system outlined?
As Dave Jones mentioned, use "chkconfig" or the gui to disable services instead of messing with the symlinks by hand.
Here are the services that I run on my desktop FC3 system. Perfectly functional, except that I have scripts that I run myself that replace the normal cron scripts.
syslog network cups xfs iptables haldaemon messagebus
Boots from power off to level 3 login prompt in 41 seconds (including the grub timeout).
Regards,
John Wendel
