<?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: Init HackFest / New init systems in Debian</title>
	<atom:link href="http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/</link>
	<description>Sven's occasional log</description>
	<lastBuildDate>Mon, 23 Aug 2010 22:28:38 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gunnar Wolf</title>
		<link>http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/comment-page-1/#comment-1737</link>
		<dc:creator>Gunnar Wolf</dc:creator>
		<pubDate>Tue, 17 Apr 2007 19:14:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/#comment-1737</guid>
		<description>[...] Leaving just as the discussion gets started is bad, yes... But I&#039;m only now reading Erich&#039;s and Sven&#039;s follow-ups. Both (as well as some comments in my blog) ask why not integrating the startup links [...]</description>
		<content:encoded><![CDATA[<p>[...] Leaving just as the discussion gets started is bad, yes&#8230; But I&#8217;m only now reading Erich&#8217;s and Sven&#8217;s follow-ups. Both (as well as some comments in my blog) ask why not integrating the startup links [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sven</title>
		<link>http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/comment-page-1/#comment-1733</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Sat, 14 Apr 2007 07:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/#comment-1733</guid>
		<description>Ben: This is odd. When I logged in to the Wiki before writing my Blog post, I &lt;u&gt;did&lt;/u&gt; check the page to make sure the &quot;protected page&quot; message was still there after I logged in. And it was. Today though, I could edit the page. And will probably do so this evening.</description>
		<content:encoded><![CDATA[<p>Ben: This is odd. When I logged in to the Wiki before writing my Blog post, I <u>did</u> check the page to make sure the &#8220;protected page&#8221; message was still there after I logged in. And it was. Today though, I could edit the page. And will probably do so this evening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hutchings</title>
		<link>http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/comment-page-1/#comment-1731</link>
		<dc:creator>Ben Hutchings</dc:creator>
		<pubDate>Fri, 13 Apr 2007 23:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/#comment-1731</guid>
		<description>The wiki page is not specially protected. You have to be logged in to edit any page.</description>
		<content:encoded><![CDATA[<p>The wiki page is not specially protected. You have to be logged in to edit any page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim Breitner</title>
		<link>http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/comment-page-1/#comment-1729</link>
		<dc:creator>Joachim Breitner</dc:creator>
		<pubDate>Fri, 13 Apr 2007 17:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/04/13/init-hackfest-new-init-systems-in-debian/#comment-1729</guid>
		<description>I basically agree (as already commented on Gunnars blog). But some remark to your proposal:

I wonder if all these need to be script snippets. After all we also want to have fast init systems that donâ€™t spawn lots of shells. Therefore, these should be _either_ script snippets (for complicated cases) or some kind of even higher meta data. Examples:

 * Pre-Check could list files to check for
 * run could just name a binary and parameters
 * Probably more

Also, for daemons that support the run-scheme, no start/stop/status should be needed. If the init system relies on that scheme (eg sys-v-init) it can be derived from the run snippet.

Iâ€™m looking forward to what becomes of this!

Greetings, nomeata</description>
		<content:encoded><![CDATA[<p>I basically agree (as already commented on Gunnars blog). But some remark to your proposal:</p>
<p>I wonder if all these need to be script snippets. After all we also want to have fast init systems that donâ€™t spawn lots of shells. Therefore, these should be _either_ script snippets (for complicated cases) or some kind of even higher meta data. Examples:</p>
<p> * Pre-Check could list files to check for<br />
 * run could just name a binary and parameters<br />
 * Probably more</p>
<p>Also, for daemons that support the run-scheme, no start/stop/status should be needed. If the init system relies on that scheme (eg sys-v-init) it can be derived from the run snippet.</p>
<p>Iâ€™m looking forward to what becomes of this!</p>
<p>Greetings, nomeata</p>
]]></content:encoded>
	</item>
</channel>
</rss>
