<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>i summon one kim &#187; Debian</title>
	<atom:link href="http://kimmo.suominen.com/archives/tag/debian/feed/" rel="self" type="application/rss+xml" />
	<link>http://kimmo.suominen.com</link>
	<description>The website of Kimmo Suominen</description>
	<lastBuildDate>Thu, 15 Dec 2011 02:20:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<cloud domain='kimmo.suominen.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Asterisk installation</title>
		<link>http://kimmo.suominen.com/archives/2009/05/asterisk-installation/</link>
		<comments>http://kimmo.suominen.com/archives/2009/05/asterisk-installation/#comments</comments>
		<pubDate>Sun, 24 May 2009 14:28:42 +0000</pubDate>
		<dc:creator>Kimmo Suominen</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://kimmo.suominen.com/?p=278</guid>
		<description><![CDATA[Just a short note on getting a minimal Asterisk environment installed on current versions of Debian and Ubuntu: aptitude install asterisk m-a a-i zaptel modprobe ztdummy Also add ztdummy to /etc/modules so it gets loaded when the system starts. If the m-a command is not found, install the module-assistant package.]]></description>
			<content:encoded><![CDATA[<p>Just a short note on getting a minimal Asterisk environment installed on current versions of Debian and Ubuntu:</p>

<blockquote>
<pre><code>aptitude install asterisk
m-a a-i zaptel
modprobe ztdummy
</code></pre>
</blockquote>

<p>Also add <code>ztdummy</code> to <code>/etc/modules</code> so it gets loaded when the system starts.</p>

<p>If the <code>m-a</code> command is not found, install the <code>module-assistant</code> package.</p>]]></content:encoded>
			<wfw:commentRss>http://kimmo.suominen.com/archives/2009/05/asterisk-installation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New syslog on lenny</title>
		<link>http://kimmo.suominen.com/archives/2009/05/new-syslog-on-lenny/</link>
		<comments>http://kimmo.suominen.com/archives/2009/05/new-syslog-on-lenny/#comments</comments>
		<pubDate>Sun, 24 May 2009 14:03:16 +0000</pubDate>
		<dc:creator>Kimmo Suominen</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://kimmo.suominen.com/?p=274</guid>
		<description><![CDATA[New installations of Debian have rsyslog as the system logging daemon. Upgraders, however, will be left with sysklogd &#8212; and no instructions on how to switch. I&#8217;m hoping purging the old one and adding the new one will work ok, as I&#8217;ve made no local mods to the logging configuration&#8230;]]></description>
			<content:encoded><![CDATA[<p>New installations of <a href="http://www.debian.org/">Debian</a> have <a href="http://www.rsyslog.com/">rsyslog</a> as the system logging daemon. Upgraders, however, will be left with sysklogd &#8212; and no instructions on how to switch. I&#8217;m hoping purging the old one and adding the new one will work ok, as I&#8217;ve made no local mods to the logging configuration&#8230;</p>]]></content:encoded>
			<wfw:commentRss>http://kimmo.suominen.com/archives/2009/05/new-syslog-on-lenny/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading to lenny</title>
		<link>http://kimmo.suominen.com/archives/2009/05/upgrading-to-lenny/</link>
		<comments>http://kimmo.suominen.com/archives/2009/05/upgrading-to-lenny/#comments</comments>
		<pubDate>Sat, 23 May 2009 07:41:59 +0000</pubDate>
		<dc:creator>Kimmo Suominen</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[RAID]]></category>

		<guid isPermaLink="false">http://kimmo.suominen.com/?p=268</guid>
		<description><![CDATA[I&#8217;ve been always a fan of the robust upgrade procedure documented in the Debian release notes, which has worked without problems even over ssh to remote machines. This has made upgrading very painless (at least since sarge &#8212; I haven&#8217;t used Debian actively longer than that). Yesterday I ran into a problem, though, which was [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been always a fan of the robust upgrade procedure documented in the <a href="http://www.debian.org/releases/lenny/releasenotes">Debian release notes</a>, which has worked without problems even over ssh to remote machines. This has made upgrading very painless (at least since <a href="http://en.wikipedia.org/wiki/Debian#Releases">sarge</a> &#8212; I haven&#8217;t used <a href="http://www.debian.org/">Debian</a> actively longer than that).</p>

<p>Yesterday I ran into a problem, though, which was only saved by having remote console access. I have a system with a slightly more complicated disk setup: it has two <acronym title="Small Computer Systems Interface">SCSI</acronym> disks running as a <acronym title="Redundant Array of Independent Disks">RAID</acronym> 1 array using <a href="http://tldp.org/HOWTO/Software-RAID-HOWTO.html">md</a> and <a href="http://tldp.org/HOWTO/LVM-HOWTO/">lvm</a>. Upon rebooting after the upgrade, the system didn&#8217;t reappear on the network. What I found on the console was the initramfs panic shell: the root file system had not been found. Rebooting the old <a href="http://en.wikipedia.org/wiki/Debian#Releases">etch</a> kernel worked fine.</p>

<p>The workaround proved to be very simple, once I distilled it from the search engine results. Just add <code>rootdelay=10</code> to the kernel options in the bootloader. I&#8217;m using <a href="http://www.gnu.org/software/grub/">GRUB</a> so this translates to editing the <code>kopt</code> line in <code>/boot/grub/menu.lst</code> and running <code>update-grub</code>.</p>

<p>I had also added <code>raid1</code> to <code>modules</code> in <code>/etc/initramfs-tools</code> and regenerated the initrd, but that (alone) didn&#8217;t help. I&#8217;m not even sure it is needed at all &#8212; it might already be included anyway when using <code>MODULES=most</code> in <code>initramfs.conf</code>.</p>]]></content:encoded>
			<wfw:commentRss>http://kimmo.suominen.com/archives/2009/05/upgrading-to-lenny/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

