<?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>Running Systems&#187; boot image</title>
	<atom:link href="http://run.tournament.org.il/tag/boot-image/feed/" rel="self" type="application/rss+xml" />
	<link>http://run.tournament.org.il</link>
	<description>(and me chasing them)</description>
	<lastBuildDate>Wed, 02 Jun 2010 13:50:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>DSL (Damn Small Linux) Diskless boot</title>
		<link>http://run.tournament.org.il/dsl-damn-small-linux-diskless-boot/</link>
		<comments>http://run.tournament.org.il/dsl-damn-small-linux-diskless-boot/#comments</comments>
		<pubDate>Fri, 31 Aug 2007 09:32:45 +0000</pubDate>
		<dc:creator>ez-aton</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[boot image]]></category>
		<category><![CDATA[damn small linux]]></category>
		<category><![CDATA[diskless systems]]></category>
		<category><![CDATA[DSL]]></category>
		<category><![CDATA[knoppix]]></category>
		<category><![CDATA[Linux system]]></category>
		<category><![CDATA[network boot]]></category>
		<category><![CDATA[nfs mount]]></category>
		<category><![CDATA[thin client]]></category>
		<category><![CDATA[thin client hardware]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://www.tournament.org.il/run-new/?p=163</guid>
		<description><![CDATA[I have come across a requirement to boot a thin client on a very cheap hardware into Linux. Due to the tight hardware requirements, and the tight budget, I have decided to focus on diskless systems, which can be easily modified and purchased to our needs. Not only that, but due to the hardware configuration [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>I have come across a requirement to boot a thin client on a very cheap hardware into Linux. Due to the tight hardware requirements, and the tight budget, I have decided to focus on diskless systems, which can be easily modified and purchased to our needs.</p>
<p>Not only that, but due to the hardware configuration (Via 333MHz, 128MB RAM, etc) I have decided to focus on a miniature Linux system.</p>
<p>I dislike re-doing what someone else has done, unless I can do it noticeably better. I have decided to use <a href="http://damnsmalllinux.org/" target="_blank">DSL (Damn Small Linux)</a> as my system of choice, with only minor changes to fit my needs:</p>
<p>Out of the &#8220;box&#8221;, I was unable to find network-boot DSL. Quickly searching their site, the version which seemed to fit was the initrd-only system. I downloaded it from <a href="http://distro.ibiblio.org/pub/linux/distributions/damnsmall/current/" target="_blank">this mirror</a>, but you can find it as the dsl-x.x.x-initrd.iso file.</p>
<p>Extracting the initrd from the ISO file is quite simple:</p>
<blockquote><p>mkdir /mnt/iso<br />
mount -o loop dsl-x.x.x-initrd.iso /mnt/iso</p></blockquote>
<p>And from here you can just copy the contents of the directory /mnt/iso/boot/isolinux/ selectively to your tftpboot directory.</p>
<p>So I got 50MB initrd which worked just fine. Changing this was quite a procedure, because in addition to the steps per the <a href="http://www.damnsmalllinux.org/wiki/index.php/Hacking_DSL" target="_blank">wiki hacking guide</a>, I was required to extract the KNOPPIX file outside of the initrd, and repackage it when done. Quite messy, however, stand-alone as soon as the system has been able to boot.</p>
<p>An alternate I have decided to investigate into was of booting into nfs mount, aka, accessing the KNOPPIX iso disk through NFS and not through CDROM.</p>
<p>I was able to find some leads in <a href="http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=ST;f=2;t=5281;st=10" target="_blank">DSL forums at this page</a>, which lead to <a href="http://abel.sk.tsukuba.ac.jp/~janos/unix/howto/pxe.html" target="_blank">this guide</a>. I was able to download pxe boot image from Knoppix themselves, however, it was based on an old kernel (2.4.20-XFS) which was part of Knoppix 3.3 (cannot find it anymore) and although reached the level of actually booting my nfs, didn&#8217;t include enough network drivers (I wanted pcnet32 to be able to &#8220;play&#8221; with VMware for the task), and was incompatible with my existing DSL.</p>
<p>I had opened the supplied Knoppix initrd, and replaced the modules version to the one supplied with DSL &#8211; 2.4.24, per the rest of the system. In addition, I have added my required modules, etc, and was able to boot successfully both on VMware and on the thin client hardware.</p>
<p>To replace the modules, one needs to follow these <strong>general-only</strong> guidelines (these are not exactly step-by-step instructions):</p>
<blockquote><p>Mount through loop the DSL KNOPPIX image, for example, in /mnt/dsl<br />
Uncompress the Knoppix PXE initrd<br />
Mount through loop the uncompressed Knoppix PXE initrd, for example, in /mnt/initrd<br />
cd to /mnt/initrd/modules<br />
Replace all modules in the current tree with the ones supplied by DSL, obtainable from /mnt/dsl/lib/modules/2.4.26 directory tree, including the cloop.o module<br />
Umount the initrd image<br />
Compress the initrd image<br />
Boot using DSL linux and the new initrd image.</p></blockquote>
<p>In order to boot successfully, you need to supply the pxe boot these two instructions:</p>
<p>nfsdir=nfs-server:/path/to/KNOPPIX directory</p>
<p>(since I was quite unsure about the letter case required, I have created a symlink from lower-case to upper case, so I had a link /mnt/KNOPPIX to a directory /mnt/knoppix, and inside this directory, a file called knoppix and a symbolic link to this file KNOPPIX. In my case, the exported path was /mnt/ only. Notice this one!).</p>
<p>BOOT_IMAGE=KNOPPIX &#8211; but you can have different KNOPPIX images for different purposes.</p>
<p>Finally it has worked correctly. Changes can be done only to the KNOPPIX iso image, per the hacking guide.</p>
<p>This is my PXE-enabled initrd, based on the text above, which fits DSL-3.4.1: <a title="minirt24.gz" href="/files/packages/minirt24.gz" target="_blank">minirt24.gz</a></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://run.tournament.org.il/dsl-damn-small-linux-diskless-boot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
