<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: 5 steps to a faster Linux boot</title>
	<atom:link href="http://brajeshwar.com/2008/5-steps-to-a-faster-linux-boot/feed/" rel="self" type="application/rss+xml" />
	<link>http://brajeshwar.com/2008/5-steps-to-a-faster-linux-boot/</link>
	<description>Brajeshwar is an ardent believer of KISS (Keep It Simple Stupid), he envision pushing the technical envelop time and again for the betterment of commercial and practical applications.</description>
	<pubDate>Sun, 05 Jul 2009 03:39:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Mol</title>
		<link>http://brajeshwar.com/2008/5-steps-to-a-faster-linux-boot/comment-page-1/#comment-24927</link>
		<dc:creator>Michael Mol</dc:creator>
		<pubDate>Thu, 12 Feb 2009 02:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://brajeshwar.com/?p=955#comment-24927</guid>
		<description>My own reflections on the article:

1. Use a lightweight window manager

KDE and GNOME aren't just window managers, they're "desktop environments." For years, KDE and GNOME have competed to provide the most featureful graphical user interface for Linux. And with all those features comes a lot of CPU and RAM usage. Historically, this has meant that either of them worked really well on the lastest processors with plenty of RAM, but not so well on older systems. In modern terms, with modern versions of the software, KDE and GNOME's slowness is likely imperceptible on a dual-core machine with at least 1GB of RAM, but is likely noticable on anything older or less-well-powered than that.

Me, I use a tiling window manager named w3m. It sacrifices a large number of bells and whistles in order to occupy a very small footprint. This is pretty much at the bottom of the weight scale, as far as window managers go, though there are a few that are more-lightweight, and it's possible to do without a window manager entirely, in some situations.

If you don't want to learn something radically different from GNOME or KDE, try XFCE or Enlightenment. If you're feeling a little more adventurous, try Afterstep or WindowMaker.

One of the things you'll discover if you switch down from GNOME or KDE, however, is that most of the other window managers won't automatically mount CDs, flash drives or floppy disks for you. You can still do it manually, and it's possible to set it up to occur regardless of your window manager, but it's something you'll likely have to deal with.

2. De-select the unnecessary services
On any modern operating system, there are tens of programs running in the background, handling things without direct interaction from you. Most of these programs are started while you're booting up, at various "init" levels. Disabling these services means that your computer won't have to start them while you're still booting up.

I can't tell you what's safe to disable in your case, but I can tell you to be careful. Each program is there because either the maintainers of your distro thought it would be a good idea for it to be there, or because your system administrator thought it would be a good idea for it to be there. Removing them can cause issues ranging from a slow system (Such as when I disabled PulseAudio on my laptop a while back, and had to wait for programs using ALSA to timeout.) to a severely broken system. Killing inetd may make your system inaccessible from other computers. Killing ntpd could make your clock start running fast or slow. Killing klogd and syslogd could cause all sorts of problems.

3. Use a text-based login in lieu of Graphical login window

Technically, it's called a "display manager", for those interested in the terminology.

This is certainly a possibility, but it has its own drawbacks. While you can avoid having to start gdm, kdm or xdm (which do take a significant amount of time in my system's boot cycle...and I've got a top-of-the-line home-built desktop.), you'll have to learn at least a little bit about the command-line interface of Linux. Which is something you should do in any case if you plan to be proficient in using and administering your Linux box, but it's something you should be ready for, rather than surprised by.

Additionally, some modern distros *coughubuntucough* write a lot of messages to virtual-terminal console screens. These are the types of screens you'll be seeing initially if you get rid of gdm, kdm and xdm. As a result, using virtual terminals for system operation can get frustrating, as these message will often overwrite or push out whatever it was you were trying to see.

By the way: the "startx" command is the one you'll most likely be looking for first if you remove gdm, xdm and kdm.

4. Use a lightweight Linux distro
In my experience, light-weight Linux distributions that aren't targeted to specific system purposes are essentially the same as the heavier distributions, but with some of the above steps already taken care of. They'll often use XFCE instead of GNOME or KDE, for example, and they'll use lightweight alternatives to OpenOffice, rather than OpenOffice itself. Sometimes they'll replace Firefox with Galeon or Opera.

All in all, they're good choices if they will do what you need them to do. However, keep in mind that it's the popular distributions that have the most community support. If you need assistance with something, you'll probably find help easier if you use Ubuntu or one of its derivatives than if you use Fluxbox.

5. Disable unnecessary kernel modules - Only for Geeks and Administrators!
If you've used wifi on Linux, there's a good chance you've already skirted this one. Otherwise, be very, very careful. Messing around with your kernel configuration is Risky Business, and not something to be done unless you can put up with making mistakes a couple times in the process. And these mistakes can mean everything from making the system unbootable to corrupting the data on your hard drive.

(That said, it was one of the first things I did when I first tried Linux as a kid. But I made lots of mistakes at first and lost my data a number of times. My friends--the ones who'd gotten me into Linux in the first place, and who were package and software maintainers on their own time--had no help to offer, as they hadn't messed with it themselves.)

Hope that helps.</description>
		<content:encoded><![CDATA[<p>My own reflections on the article:</p>
<p>1. Use a lightweight window manager</p>
<p><span class="caps">KDE </span>and <span class="caps">GNOME </span>aren&#8217;t just window managers, they&#8217;re &#8220;desktop environments.&#8221; For years, <span class="caps">KDE </span>and <span class="caps">GNOME </span>have competed to provide the most featureful graphical user interface for Linux. And with all those features comes a lot of <span class="caps">CPU </span>and <span class="caps">RAM </span>usage. Historically, this has meant that either of them worked really well on the lastest processors with plenty of <span class="caps">RAM, </span>but not so well on older systems. In modern terms, with modern versions of the software, <span class="caps">KDE </span>and <span class="caps">GNOME&#8217;</span>s slowness is likely imperceptible on a dual-core machine with at least 1GB of <span class="caps">RAM, </span>but is likely noticable on anything older or less-well-powered than that.</p>
<p>Me, I use a tiling window manager named w3m. It sacrifices a large number of bells and whistles in order to occupy a very small footprint. This is pretty much at the bottom of the weight scale, as far as window managers go, though there are a few that are more-lightweight, and it&#8217;s possible to do without a window manager entirely, in some situations.</p>
<p>If you don&#8217;t want to learn something radically different from <span class="caps">GNOME </span>or <span class="caps">KDE, </span>try <span class="caps">XFCE </span>or Enlightenment. If you&#8217;re feeling a little more adventurous, try Afterstep or WindowMaker.</p>
<p>One of the things you&#8217;ll discover if you switch down from <span class="caps">GNOME </span>or <span class="caps">KDE, </span>however, is that most of the other window managers won&#8217;t automatically mount CDs, flash drives or floppy disks for you. You can still do it manually, and it&#8217;s possible to set it up to occur regardless of your window manager, but it&#8217;s something you&#8217;ll likely have to deal with.</p>
<p>2. De-select the unnecessary services<br />
On any modern operating system, there are tens of programs running in the background, handling things without direct interaction from you. Most of these programs are started while you&#8217;re booting up, at various &#8220;init&#8221; levels. Disabling these services means that your computer won&#8217;t have to start them while you&#8217;re still booting up.</p>
<p>I can&#8217;t tell you what&#8217;s safe to disable in your case, but I can tell you to be careful. Each program is there because either the maintainers of your distro thought it would be a good idea for it to be there, or because your system administrator thought it would be a good idea for it to be there. Removing them can cause issues ranging from a slow system (Such as when I disabled PulseAudio on my laptop a while back, and had to wait for programs using <span class="caps">ALSA </span>to timeout.) to a severely broken system. Killing inetd may make your system inaccessible from other computers. Killing ntpd could make your clock start running fast or slow. Killing klogd and syslogd could cause all sorts of problems.</p>
<p>3. Use a text-based login in lieu of Graphical login window</p>
<p>Technically, it&#8217;s called a &#8220;display manager&#8221;, for those interested in the terminology.</p>
<p>This is certainly a possibility, but it has its own drawbacks. While you can avoid having to start gdm, kdm or xdm (which do take a significant amount of time in my system&#8217;s boot cycle&#8230;and I&#8217;ve got a top-of-the-line home-built desktop.), you&#8217;ll have to learn at least a little bit about the command-line interface of Linux. Which is something you should do in any case if you plan to be proficient in using and administering your Linux box, but it&#8217;s something you should be ready for, rather than surprised by.</p>
<p>Additionally, some modern distros <strong>coughubuntucough</strong> write a lot of messages to virtual-terminal console screens. These are the types of screens you&#8217;ll be seeing initially if you get rid of gdm, kdm and xdm. As a result, using virtual terminals for system operation can get frustrating, as these message will often overwrite or push out whatever it was you were trying to see.</p>
<p>By the way: the &#8220;startx&#8221; command is the one you&#8217;ll most likely be looking for first if you remove gdm, xdm and kdm.</p>
<p>4. Use a lightweight Linux distro<br />
In my experience, light-weight Linux distributions that aren&#8217;t targeted to specific system purposes are essentially the same as the heavier distributions, but with some of the above steps already taken care of. They&#8217;ll often use <span class="caps">XFCE </span>instead of <span class="caps">GNOME </span>or <span class="caps">KDE, </span>for example, and they&#8217;ll use lightweight alternatives to OpenOffice, rather than OpenOffice itself. Sometimes they&#8217;ll replace Firefox with Galeon or Opera.</p>
<p>All in all, they&#8217;re good choices if they will do what you need them to do. However, keep in mind that it&#8217;s the popular distributions that have the most community support. If you need assistance with something, you&#8217;ll probably find help easier if you use Ubuntu or one of its derivatives than if you use Fluxbox.</p>
<p>5. Disable unnecessary kernel modules - Only for Geeks and Administrators!<br />
If you&#8217;ve used wifi on Linux, there&#8217;s a good chance you&#8217;ve already skirted this one. Otherwise, be very, very careful. Messing around with your kernel configuration is Risky Business, and not something to be done unless you can put up with making mistakes a couple times in the process. And these mistakes can mean everything from making the system unbootable to corrupting the data on your hard drive.</p>
<p>(That said, it was one of the first things I did when I first tried Linux as a kid. But I made lots of mistakes at first and lost my data a number of times. My friends&#8211;the ones who&#8217;d gotten me into Linux in the first place, and who were package and software maintainers on their own time&#8211;had no help to offer, as they hadn&#8217;t messed with it themselves.)</p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://brajeshwar.com/2008/5-steps-to-a-faster-linux-boot/comment-page-1/#comment-22806</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Thu, 31 Jul 2008 06:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://brajeshwar.com/?p=955#comment-22806</guid>
		<description>Do most linux distributions provide hybrid sleep?

I never boot up my computer, just press the space bar and 2 seconds later I log in.


Greetz Erik</description>
		<content:encoded><![CDATA[<p>Do most linux distributions provide hybrid sleep?</p>
<p>I never boot up my computer, just press the space bar and 2 seconds later I log in.</p>
<p>Greetz Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 42gems</title>
		<link>http://brajeshwar.com/2008/5-steps-to-a-faster-linux-boot/comment-page-1/#comment-22802</link>
		<dc:creator>42gems</dc:creator>
		<pubDate>Thu, 31 Jul 2008 00:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://brajeshwar.com/?p=955#comment-22802</guid>
		<description>a lot of the more user-friendly distros, like ubuntu, or fedora, will load tons of crap like bluetooth and wi-fi drivers and CUPS at boot time, by default. kinda like windows...</description>
		<content:encoded><![CDATA[<p>a lot of the more user-friendly distros, like ubuntu, or fedora, will load tons of crap like bluetooth and wi-fi drivers and <span class="caps">CUPS </span>at boot time, by default. kinda like windows&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
