<?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"
	>
<channel>
	<title>Comments on: Yellow Dog Linux</title>
	<atom:link href="http://www.alstongrove.com/posts/20/feed" rel="self" type="application/rss+xml" />
	<link>http://www.alstongrove.com/posts/20</link>
	<description>Welcome to the throes of my thoughts</description>
	<pubDate>Sun, 05 Feb 2012 18:29:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Rob Stevenson</title>
		<link>http://www.alstongrove.com/posts/20#comment-11</link>
		<dc:creator>Rob Stevenson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://maize.dhs.org/wp/?p=20#comment-11</guid>
		<description>Woot!  Glad to see that YDL worked out for you!  Strange about that bootup time though. Hmmm.

Personally, I'd dump Mozilla and pickup Firebird.  I've looked at Thunderbird as well and it seems a tad rough right now, but definitely looks like it has potential.

Linux just lacks that "Spit and Polish" that it needs to break into the more "Average Joe" user base.  Can a graphical startup screen be THAT difficult?  Just give a keystroke as an option to view the text bootup sequence (can be set as default) and you'll appease(?) the geek masses.

I'll be interested to see what you think of MacOnLinux (MOL)!!</description>
		<content:encoded><![CDATA[<p>Woot!  Glad to see that YDL worked out for you!  Strange about that bootup time though. Hmmm.</p>
<p>Personally, I&#8217;d dump Mozilla and pickup Firebird.  I&#8217;ve looked at Thunderbird as well and it seems a tad rough right now, but definitely looks like it has potential.</p>
<p>Linux just lacks that &#8220;Spit and Polish&#8221; that it needs to break into the more &#8220;Average Joe&#8221; user base.  Can a graphical startup screen be THAT difficult?  Just give a keystroke as an option to view the text bootup sequence (can be set as default) and you&#8217;ll appease(?) the geek masses.</p>
<p>I&#8217;ll be interested to see what you think of MacOnLinux (MOL)!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.alstongrove.com/posts/20#comment-12</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://maize.dhs.org/wp/?p=20#comment-12</guid>
		<description>The slow boot time is a problem for Linux in general.  With hardware running so fast now, maybe people overlook the problem, similar to how memory footprint of the desktop is overlooked.  I think the kernel actually initializes pretty quickly, but all the init scripts that run take time.  Why can't some of these scripts run in parallel?  There could still be dependencies, like run network first, but then kick off xinetd, cups, apache, etc in parallel.  

Maybe even give the user their login prompt while a few scripts are still running, like enabling swap space.  I understand the debugging value of having each task run separately on screen along with its output.  But we are going to have a graphical boot soon, so log all that boot stuff, and queue events to notify the user of problems after they login ("The system was unable to initialize swap space because ..." -- then pop up the help browser).

I like shell scripts for simplicity and maintenance, but I wonder how much faster binary code would run?  What if there were a compiler that turned the shell scripts into binaries?  I think the scripts are a bit inefficient too.  I noticed a lot of "sleep" commands being used in them on my RedHat system.

To be fair, my Windows 2000 desktop at work takes 2 minutes to boot also, but Linux should be better than that.
</description>
		<content:encoded><![CDATA[<p>The slow boot time is a problem for Linux in general.  With hardware running so fast now, maybe people overlook the problem, similar to how memory footprint of the desktop is overlooked.  I think the kernel actually initializes pretty quickly, but all the init scripts that run take time.  Why can&#8217;t some of these scripts run in parallel?  There could still be dependencies, like run network first, but then kick off xinetd, cups, apache, etc in parallel.  </p>
<p>Maybe even give the user their login prompt while a few scripts are still running, like enabling swap space.  I understand the debugging value of having each task run separately on screen along with its output.  But we are going to have a graphical boot soon, so log all that boot stuff, and queue events to notify the user of problems after they login (&#8221;The system was unable to initialize swap space because &#8230;&#8221; &#8212; then pop up the help browser).</p>
<p>I like shell scripts for simplicity and maintenance, but I wonder how much faster binary code would run?  What if there were a compiler that turned the shell scripts into binaries?  I think the scripts are a bit inefficient too.  I noticed a lot of &#8220;sleep&#8221; commands being used in them on my RedHat system.</p>
<p>To be fair, my Windows 2000 desktop at work takes 2 minutes to boot also, but Linux should be better than that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

