<?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: Managing Services in Ubuntu, Part I: An Introduction to Runlevels</title>
	<atom:link href="http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<pubDate>Sun, 07 Sep 2008 23:19:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-hemorrhage</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fatman</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-102034</link>
		<dc:creator>Fatman</dc:creator>
		<pubDate>Thu, 05 Jun 2008 11:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-102034</guid>
		<description>I should have looked this up ages ago. Now to read part 2. :)</description>
		<content:encoded><![CDATA[<p>I should have looked this up ages ago. Now to read part 2. <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ekin Akoglu</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-100184</link>
		<dc:creator>Ekin Akoglu</dc:creator>
		<pubDate>Thu, 08 May 2008 10:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-100184</guid>
		<description>Great article...It has been for a while since I started wondering about the upstart system and its differences from init. Now it seems clear...</description>
		<content:encoded><![CDATA[<p>Great article&#8230;It has been for a while since I started wondering about the upstart system and its differences from init. Now it seems clear&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maxo</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92612</link>
		<dc:creator>Maxo</dc:creator>
		<pubDate>Wed, 27 Feb 2008 20:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92612</guid>
		<description>Thanks for the tutorial.  I have known the very basics of the run levels from a Suse class I took, but we didn't go in to that detail.
I am curious if there is any difference in using the init and the telinit commands?  I've always used init to change run levels.</description>
		<content:encoded><![CDATA[<p>Thanks for the tutorial.  I have known the very basics of the run levels from a Suse class I took, but we didn&#8217;t go in to that detail.<br />
I am curious if there is any difference in using the init and the telinit commands?  I&#8217;ve always used init to change run levels.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92526</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 26 Feb 2008 20:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92526</guid>
		<description>The K stands for Kill, the S stands for Start. So yes, a process will be started or stopped in a given runlevel based off the symlink name.</description>
		<content:encoded><![CDATA[<p>The K stands for Kill, the S stands for Start. So yes, a process will be started or stopped in a given runlevel based off the symlink name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92525</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Tue, 26 Feb 2008 20:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92525</guid>
		<description>@Marius Scurtescu-  Yes.  If the script is an S-script, then Upstart will append 'start' to the script.  If it is a K-script, then Upstart will append a 'stop' to the script.</description>
		<content:encoded><![CDATA[<p>@Marius Scurtescu-  Yes.  If the script is an S-script, then Upstart will append &#8217;start&#8217; to the script.  If it is a K-script, then Upstart will append a &#8217;stop&#8217; to the script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marius Scurtescu</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92523</link>
		<dc:creator>Marius Scurtescu</dc:creator>
		<pubDate>Tue, 26 Feb 2008 20:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92523</guid>
		<description>The symlinks from the /etc/rc[0-6].d/ folders do not specify the start/stop argument. Is telinit adding start/stop as needed based on the symlinks name?</description>
		<content:encoded><![CDATA[<p>The symlinks from the /etc/rc[0-6].d/ folders do not specify the start/stop argument. Is telinit adding start/stop as needed based on the symlinks name?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92521</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Tue, 26 Feb 2008 20:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92521</guid>
		<description>@Tom-  Yeah, for the simplicity of this post that I was going after, the differences between Upstart and Init aren't really necessary.  However, Upstart is definitely under my radar, and will get a focus all it's own.  For the future posts in this series, I'm just targeting managing various services, and because Upstart is backwards-compatible with SysVInit, there won't be much to say in the way of Upstart quite yet.  Glad you enjoyed the tutorial, however.</description>
		<content:encoded><![CDATA[<p>@Tom-  Yeah, for the simplicity of this post that I was going after, the differences between Upstart and Init aren&#8217;t really necessary.  However, Upstart is definitely under my radar, and will get a focus all it&#8217;s own.  For the future posts in this series, I&#8217;m just targeting managing various services, and because Upstart is backwards-compatible with SysVInit, there won&#8217;t be much to say in the way of Upstart quite yet.  Glad you enjoyed the tutorial, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Vollerthun</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92517</link>
		<dc:creator>Tom Vollerthun</dc:creator>
		<pubDate>Tue, 26 Feb 2008 19:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92517</guid>
		<description>Great tutorial, Aaron, thank you!
Interestingly, you only mention the /etc/event.d shortly before you continue to explain very knowledgeable and well the /etc/rc*.d directories.
For me this is a pity, because I'm very apt with the normal SysV-Initscripts, but not at all with the new even based system (upstart).
If anyone (p.e. me :) is to create some of the missing event.d-skripts, entry level tutorials are necessary.
Noticing how competent yet accessible you are writing about complex topics generally, I can't help but hope you might pick up this specific topic in one of your future blogs.

No matter if or if not, I'm looking forward to reading the next part of this tutorial. I promise I won't mention the upstart-init system then again :)</description>
		<content:encoded><![CDATA[<p>Great tutorial, Aaron, thank you!<br />
Interestingly, you only mention the /etc/event.d shortly before you continue to explain very knowledgeable and well the /etc/rc*.d directories.<br />
For me this is a pity, because I&#8217;m very apt with the normal SysV-Initscripts, but not at all with the new even based system (upstart).<br />
If anyone (p.e. me <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> is to create some of the missing event.d-skripts, entry level tutorials are necessary.<br />
Noticing how competent yet accessible you are writing about complex topics generally, I can&#8217;t help but hope you might pick up this specific topic in one of your future blogs.</p>
<p>No matter if or if not, I&#8217;m looking forward to reading the next part of this tutorial. I promise I won&#8217;t mention the upstart-init system then again <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92513</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Tue, 26 Feb 2008 18:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92513</guid>
		<description>@Yves-  Thanks.  The 2nd part will be up tomorrow.

@K3nt1-  Yes, it is possible to set your default runlevel to 6, thus entering an infinite reboot.  In order to bypass it, the kernel allows appending a runlevel to the arguments (for the time being, only sulogin is working).  When GRUB boots, press [Esc] to show the GRUB prompt, then edit the kernel line, appending 's' or 'S' at the end.  Then, when the system boots into sulogin, re-edit the file with the appropriate change.</description>
		<content:encoded><![CDATA[<p>@Yves-  Thanks.  The 2nd part will be up tomorrow.</p>
<p>@K3nt1-  Yes, it is possible to set your default runlevel to 6, thus entering an infinite reboot.  In order to bypass it, the kernel allows appending a runlevel to the arguments (for the time being, only sulogin is working).  When GRUB boots, press [Esc] to show the GRUB prompt, then edit the kernel line, appending &#8217;s&#8217; or &#8216;S&#8217; at the end.  Then, when the system boots into sulogin, re-edit the file with the appropriate change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K3nt1</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92511</link>
		<dc:creator>K3nt1</dc:creator>
		<pubDate>Tue, 26 Feb 2008 18:30:40 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92511</guid>
		<description>Probably a silly question, but if you specify runlevel 6 as default, is it going to start booting and rebooting in loop and how will you be able to take back control of your machine...?

Anyway, great article, and I'm very impatient to see the upcoming articles.

Cheers.</description>
		<content:encoded><![CDATA[<p>Probably a silly question, but if you specify runlevel 6 as default, is it going to start booting and rebooting in loop and how will you be able to take back control of your machine&#8230;?</p>
<p>Anyway, great article, and I&#8217;m very impatient to see the upcoming articles.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves</title>
		<link>http://pthree.org/2008/02/26/managing-services-in-ubuntu-part-i-an-introduction-to-runlevels/#comment-92509</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Tue, 26 Feb 2008 18:03:46 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=556#comment-92509</guid>
		<description>Very nice tutorial, I am looking forward to the second part. Thank you!</description>
		<content:encoded><![CDATA[<p>Very nice tutorial, I am looking forward to the second part. Thank you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
