<?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>SiD3WiNDR's Homepage &#187; Linux</title>
	<atom:link href="http://www.sid3windr.be/archives/category/linux/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sid3windr.be</link>
	<description>My homepage</description>
	<lastBuildDate>Tue, 11 Jan 2011 14:19:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Creating a Java package with make-jpkg</title>
		<link>http://www.sid3windr.be/archives/611/creating-a-java-package-with-make-jpkg</link>
		<comments>http://www.sid3windr.be/archives/611/creating-a-java-package-with-make-jpkg#comments</comments>
		<pubDate>Sat, 17 Apr 2010 11:17:20 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=611</guid>
		<description><![CDATA[Looks like this tool is going away, it&#8217;s not in squeeze or sid anymore, but hey, I needed a newer JDK&#8230; make-jpkg cannot create packages for Java 6 update 10 or newer, to fix this, edit /usr/share/java-package/sun-j2sdk.sh. Add this stanza: "jdk-6u"[0-9][0-9]"-linux-x64.bin") # SUPPORTED j2se_version=1.6.0+update${archive_name:6:2}${revision} j2se_expected_min_size=130 found=true ;; right after "jdk-6u"[0-9]"-linux-x64.bin") # SUPPORTED j2se_version=1.6.0+update${archive_name:6:1}${revision} j2se_expected_min_size=130 found=true [...]]]></description>
			<content:encoded><![CDATA[<p>Looks like this tool is going away, it&#8217;s not in squeeze or sid anymore, but hey, I needed a newer JDK&#8230;</p>
<p>make-jpkg cannot create packages for Java 6 update 10 or newer, to fix this, edit /usr/share/java-package/sun-j2sdk.sh.</p>
<p>Add this stanza:</p>
<pre>       "jdk-6u"[0-9][0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:2}${revision}
            j2se_expected_min_size=130
            found=true
            ;;
</pre>
<p>right after</p>
<pre>        "jdk-6u"[0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:1}${revision}
            j2se_expected_min_size=130
            found=true
            ;;
</pre>
<p>Then try again, should be golden.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/611/creating-a-java-package-with-make-jpkg/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tuxdroid!</title>
		<link>http://www.sid3windr.be/archives/597/tuxdroid</link>
		<comments>http://www.sid3windr.be/archives/597/tuxdroid#comments</comments>
		<pubDate>Thu, 13 Aug 2009 23:50:33 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[ProTip]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=597</guid>
		<description><![CDATA[Quite a while back, I read in one of my magazines about the Tux Droid, produced by apparently Belgian company Kysoh. Back then, it cost 79 EUR. I wanted one, but I didn&#8217;t feel 79 euro was to be spent, so I put it on my wishlist. I revisited it a few months ago, and [...]]]></description>
			<content:encoded><![CDATA[<p>Quite a while back, I read in one of my magazines about the Tux Droid, produced by apparently Belgian company <a href="http://www.kysoh.com">Kysoh</a>. Back then, it cost 79 EUR. I wanted one, but I didn&#8217;t feel 79 euro was to be spent, so I put it on my <a href="http://sales.sid3windr.be/wishlist">wishlist</a>. I revisited it a few months ago, and I almost fell off my chair when I saw the current price: 149 EUR!</p>
<p>My wife however found a nice deal a few weeks ago: if you buy the 2 year subscription to <a href="http://www.lpmagazine.org">Linux+ magazine</a> (for 49.99 EUR) you get a Tuxdroid as a welcome gift! That&#8217;s essentially a Tuxdroid for 50 euro with free shipping and with a free 2 year magazine as well <img src='http://www.sid3windr.be/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Mine&#8217;s on the way, thanks to my wife who gave it to me as a gift &#8211; already received 2 issues and they&#8217;re interesting (read a chapter about forensics cd&#8217;s today).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/597/tuxdroid/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>localhost not found</title>
		<link>http://www.sid3windr.be/archives/594/localhost-not-found</link>
		<comments>http://www.sid3windr.be/archives/594/localhost-not-found#comments</comments>
		<pubDate>Sat, 18 Jul 2009 00:43:39 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=594</guid>
		<description><![CDATA[I just had the following error while trying to start Smokeping on one of my newly installed machines: ERROR: fping (&#8216;/usr/bin/fping -C 1 localhost&#8217;) could not be run: localhost address not found After digging around somewhat (this worked fine when run on the commandline) turns out my /etc/hosts was chmodded 700 instead of 744. Weird, [...]]]></description>
			<content:encoded><![CDATA[<p>I just had the following error while trying to start <a href="http://oss.oetiker.ch/smokeping/">Smokeping</a> on one of my newly installed machines:</p>
<blockquote><p>ERROR: fping (&#8216;/usr/bin/fping -C 1 localhost&#8217;) could not be run: localhost address not found</p></blockquote>
<p>After digging around somewhat (this worked fine when run on the commandline) turns out my /etc/hosts was chmodded 700 instead of 744. Weird, but this meant only root could resolve it. What I don&#8217;t understand is why this did not work &#8211; my resolvers also return 127.0.0.1 for the &#8220;localhost&#8221; query. </p>
<p>Anyway, if you get this error, check if the smokeping user can resolve localhost too <img src='http://www.sid3windr.be/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>As <a href="http://www.krisbuytaert.be/blog/">Kris</a> would say, it was some sort of DNS problem&#8230; <img src='http://www.sid3windr.be/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/594/localhost-not-found/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rescanning your disks after creating a new Areca RAID volume through the CLI tool</title>
		<link>http://www.sid3windr.be/archives/586/rescanning-your-disks-after-creating-a-new-areca-raid-volume-through-the-cli-tool</link>
		<comments>http://www.sid3windr.be/archives/586/rescanning-your-disks-after-creating-a-new-areca-raid-volume-through-the-cli-tool#comments</comments>
		<pubDate>Wed, 08 Jul 2009 13:07:34 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=586</guid>
		<description><![CDATA[Once you have created a new volume in the CLI tool, Linux does not automatically see the disks. To remedy, use the following: # echo &#8220;- &#8211; -&#8221; > /sys/class/scsi_host/host0/scan If one of the volumes was still initializing when you did that, it will have been detected by the driver, but not assigned a device [...]]]></description>
			<content:encoded><![CDATA[<p>Once you have created a new volume in the CLI tool, Linux does not automatically see the disks. To remedy, use the following:</p>
<blockquote><p># echo &#8220;- &#8211; -&#8221; > /sys/class/scsi_host/host0/scan</p></blockquote>
<p>If one of the volumes was still initializing when you did that, it will have been detected by the driver, but not assigned a device node. In that case, performing the above ritual after it has been initialized will not help. You first have to remove the device again, then rescan again:</p>
<blockquote><p># dmesg|grep 0:0:<br />
scsi 0:0:0:3: Direct-Access     Areca    ARC-1260-VOL#03  R001 PQ: 1 ANSI: 3<br />
scsi 0:0:0:3: Attached scsi generic sg4 type 0<br />
# echo &#8220;scsi remove-single-device 0:0:0:3&#8243; > /proc/scsi/scsi<br />
# echo &#8220;- &#8211; -&#8221; > /sys/class/scsi_host/host0/scan<br />
# dmesg|grep 0:0:<br />
scsi 0:0:0:3: Direct-Access     Areca    ARC-1260-VOL#03  R001 PQ: 1 ANSI: 3<br />
scsi 0:0:0:3: Attached scsi generic sg4 type 0<br />
scsi 0:0:0:3: Direct-Access     Areca    ARC-1260-VOL#03  R001 PQ: 0 ANSI: 3<br />
sd 0:0:0:3: Attached scsi disk sdd<br />
sd 0:0:0:3: Attached scsi generic sg4 type 0
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/586/rescanning-your-disks-after-creating-a-new-areca-raid-volume-through-the-cli-tool/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Upgraded to Jaunty</title>
		<link>http://www.sid3windr.be/archives/578/upgraded-to-jaunty</link>
		<comments>http://www.sid3windr.be/archives/578/upgraded-to-jaunty#comments</comments>
		<pubDate>Sat, 04 Jul 2009 10:20:30 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Rants]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=578</guid>
		<description><![CDATA[Yesterday, I upgraded my Ubuntu Intrepid 8.10 laptop (fresh install) to Jaunty 9.04. Turns out this is a typical non-tested Ubuntu upgrade, as literally everything broke. My wifi is non-functional with the 2.6.28 kernel delivered with 9.04, luckily downgrading to the 8.10 kernel made it work fine. Purged linux-generic and all its descendants, so that&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday, I upgraded my Ubuntu Intrepid 8.10 laptop (fresh install) to Jaunty 9.04. Turns out this is a typical non-tested Ubuntu upgrade, as literally everything broke. My wifi is non-functional with the 2.6.28 kernel delivered with 9.04, luckily downgrading to the 8.10 kernel made it work fine. Purged linux-generic and all its descendants, so that&#8217;s &#8220;fixed&#8221;.</p>
<p>Next to that, I logged into KDE only to find the main panel missing. Having no clue how to fix this nor feeling like googling (especially since at that point my wifi did not work), I moved my old .kde out of the way and had it create a new one, so it worked again. Copied over some rc files for frequently used apps so most config could be saved, luckily.</p>
<p>When I &#8220;unplug&#8221; (turn off) my internal bluetooth adapter, or the laptop goes into suspend meaning the bluetooth sleeps too, the &#8220;KDE4 Bluetooth Framework&#8221; crashes. Somehow the bluetooth system tray icon still works though, it&#8217;s just odd.</p>
<p>I get most notifications a few times now, once in a tooltip popup from the system tray icon, and once in a generic yellow rectangle from KDE, containing the exact same text. How&#8217;s that for thoroughness!</p>
<p>The network manager icon no longer shows wifi strengh, it&#8217;s now a very ugly icon with some kind of antenna with radio wave circles around. Uergh.</p>
<p>KDE4&#8242;s battery manager icon is really fugly, and I mean &#8220;FUGLY could have done it better myself in mspaint in 20 seconds FUGLY&#8221;. Luckily, apt-get install kpowersave gets me the old power icon back with a way more useful hover tooltip, so I could remove the battery monitor applet.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/578/upgraded-to-jaunty/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>KDE trouble</title>
		<link>http://www.sid3windr.be/archives/549/kde-trouble</link>
		<comments>http://www.sid3windr.be/archives/549/kde-trouble#comments</comments>
		<pubDate>Fri, 17 Apr 2009 13:29:51 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=549</guid>
		<description><![CDATA[If you suddenly find your KDE on Ubuntu Intrepid without working keyboard focus and no window decorations (essentially, no window management functions), try getting to &#8220;system configuration&#8221; from the menu and check Appearance > Windows. If it says something about being able to load kcm_kwindecoration.so because of a missing libkephal.so, apt-get install kde-window-manager. Although it [...]]]></description>
			<content:encoded><![CDATA[<p>If you suddenly find your KDE on Ubuntu Intrepid without working keyboard focus and no window decorations (essentially, no window management functions), try getting to &#8220;system configuration&#8221; from the menu and check Appearance > Windows. If it says something about being able to load kcm_kwindecoration.so because of a missing libkephal.so, apt-get install kde-window-manager. Although it will already be installed, &#8220;somebody&#8221; fscked up dependencies.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/549/kde-trouble/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xen fails on Debian Lenny after upgrade from Etch</title>
		<link>http://www.sid3windr.be/archives/539/xen-fails-on-debian-lenny-after-upgrade-from-etch</link>
		<comments>http://www.sid3windr.be/archives/539/xen-fails-on-debian-lenny-after-upgrade-from-etch#comments</comments>
		<pubDate>Mon, 13 Apr 2009 11:55:20 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=539</guid>
		<description><![CDATA[Installed Debian Etch yesterday (I need a linux kernel with xen and vserver for now, and Lenny doesn&#8217;t have one) then upgraded it to Lenny. Afterwards the Xen tools wouldn&#8217;t start anymore and produced the following error: # /etc/init.d/xend start Restarting XEN control daemon: xendTraceback (most recent call last): File &#34;/usr/lib/xen-3.0.3-1/bin/xend&#34;, line 40, in &#60;module&#62; [...]]]></description>
			<content:encoded><![CDATA[<p>Installed Debian Etch yesterday (I need a linux kernel with xen and vserver for now, and Lenny doesn&#8217;t have one) then upgraded it to Lenny. Afterwards the Xen tools wouldn&#8217;t start anymore and produced the following error:</p>
<pre class="message"># /etc/init.d/xend start 
Restarting XEN control daemon: xendTraceback (most recent call last): 
File &quot;/usr/lib/xen-3.0.3-1/bin/xend&quot;, line 40, in &lt;module&gt; 
from xen.xend.server import SrvDaemon 
File &quot;/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py&quot;, line 17, in &lt;module&gt;
 import xen.lowlevel.xc 
ImportError: /usr/lib/xen-3.0.3-1/bin/../lib/python/xen/lowlevel/xc.so: undefined symbol: Py_InitModule4 </pre>
<p>You can solve this in 2 ways. First, the silly way:</p>
<pre>rm /usr/bin/python; ln -s /usr/bin/python2.4 /usr/bin/python
</pre>
<p>Or, the way you&#8217;re supposed to:</p>
<pre>apt-get install xen-utils-3.2-1&nbsp; </pre>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/539/xen-fails-on-debian-lenny-after-upgrade-from-etch/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Extracting a boot image from a CD</title>
		<link>http://www.sid3windr.be/archives/519/extracting-a-boot-image-from-a-cd</link>
		<comments>http://www.sid3windr.be/archives/519/extracting-a-boot-image-from-a-cd#comments</comments>
		<pubDate>Wed, 18 Mar 2009 10:33:05 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=519</guid>
		<description><![CDATA[Just needed to extract a boot image from a CD, geteltorito works nicely (except it outputs to stdout, sigh )]]></description>
			<content:encoded><![CDATA[<p>Just needed to extract a boot image from a CD, <a href="http://freshmeat.net/projects/geteltorito/">geteltorito</a>  works nicely (except it outputs to stdout, sigh <img src='http://www.sid3windr.be/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  )</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/519/extracting-a-boot-image-from-a-cd/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>debmirror gnupg problem</title>
		<link>http://www.sid3windr.be/archives/499/debmirror-gnupg-problem</link>
		<comments>http://www.sid3windr.be/archives/499/debmirror-gnupg-problem#comments</comments>
		<pubDate>Sun, 01 Mar 2009 23:32:59 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Debian]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=499</guid>
		<description><![CDATA[Something seems to have changed in the debmirror prorgam on lenny: gpgv: Signature made Sun Mar&#160; 1 16:27:33 2009 CET using DSA key ID 1F41B907 [GNUPG:] ERRSIG 07DC563D1F41B907 17 2 00 1235921253 9 [GNUPG:] NO_PUBKEY 07DC563D1F41B907 gpgv: Can&#8217;t check signature: public key not found This error turned up when I tried to mirror debian-multimedia.org after [...]]]></description>
			<content:encoded><![CDATA[<p>Something seems to have changed in the debmirror prorgam on lenny: </p>
<p>gpgv: Signature made Sun Mar&nbsp; 1 16:27:33 2009 CET using DSA key ID 1F41B907<br /> [GNUPG:] ERRSIG 07DC563D1F41B907 17 2 00 1235921253 9<br /> [GNUPG:] NO_PUBKEY 07DC563D1F41B907<br /> gpgv: Can&#8217;t check signature: public key not found </p>
<p>This error turned up when I tried to mirror debian-multimedia.org after upgrading debmirror. Apparently the new version looks for the keys in ~/.gnupg/trustedkeys.gpg. If you installed the debian-multimedia-keyring package, you can use the following:</p>
<p>&nbsp;gpg &#8211;no-default-keyring -a &#8211;keyring /usr/share/keyrings/debian-multimedia-keyring.gpg &#8211;export 07DC563D1F41B907 | gpg &#8211;no-default-keyring &#8211;keyring ~/.gnupg/trustedkeys.gpg &#8211;import - </p>
<p>This imports the current key into the new file.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/499/debmirror-gnupg-problem/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More lenny upgrade</title>
		<link>http://www.sid3windr.be/archives/490/more-lenny-upgrade</link>
		<comments>http://www.sid3windr.be/archives/490/more-lenny-upgrade#comments</comments>
		<pubDate>Sat, 21 Feb 2009 14:56:55 +0000</pubDate>
		<dc:creator>SiD3WiNDR</dc:creator>
				<category><![CDATA[Debian]]></category>

		<guid isPermaLink="false">http://www.sid3windr.be/?p=490</guid>
		<description><![CDATA[If you get the following error in your linux-vserver guest after upgrading it to lenny: Feb 21 14:03:22 ftp sshd[18392]: error writing /proc/self/oom_adj: Permission denied &#160; Adjust /etc/default/ssh &#8216;s SSHD_OOM_ADJUST=-17 into SSHD_OOM_ADJUST= then restart ssh to get rid of it. &#160;]]></description>
			<content:encoded><![CDATA[<p>If you get the following error in your linux-vserver guest after upgrading it to lenny:</p>
<pre>Feb 21 14:03:22 ftp sshd[18392]: error writing /proc/self/oom_adj: Permission denied</pre>
<pre>&nbsp;</pre>
<p>Adjust /etc/default/ssh &#8216;s <em>SSHD_OOM_ADJUST=-17</em> into <em>SSHD_OOM_ADJUST=</em> then restart ssh to get rid of it.</p>
<pre>&nbsp;</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.sid3windr.be/archives/490/more-lenny-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

