<?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: Jaunty Server on Compact Flash: running Ubuntu 9.04 on a Thin Client</title>
	<atom:link href="http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/feed/" rel="self" type="application/rss+xml" />
	<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/</link>
	<description>Taher Shihadeh's ragbag</description>
	<lastBuildDate>Mon, 26 Jul 2010 07:08:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Wes Crucius</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1453</link>
		<dc:creator>Wes Crucius</dc:creator>
		<pubDate>Tue, 06 Oct 2009 18:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1453</guid>
		<description>Here&#039;s a significantly different approach...  Just [dramatically] reduce the frequency at which the kernel flushes the disk cache!  To do that, you add the appropriate modifications to kernel parameters in /etc/sysctl.conf:
vm.laptop_mode = 600
vm.dirty_ratio = 40
vm.dirty_background_ratio = 1
vm.dirty_writeback_centisecs = 60000

In this way, you run a much higher risk losing (the recently written) data during a power loss, but just add a UPS with comms and you can save and shutdown cleanly, then no problems at all!

If you want to get a little bit more fancy (and have sufficient RAM), you can mount most of the /var stuff on a RAM drive (during boot up using simple tmpfs entries in mtab), and you can probably reduce the number of archive copies of each log file (see the cron logrotate configs) just to save precious CF space...

I&#039;ll admit that I only have about a year&#039;s worth of run time on the dozen or so machines that I set up this way, however the first experiment (close eyes and pretend it&#039;s magnetic media) failed reliably within a month!</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a significantly different approach&#8230;  Just [dramatically] reduce the frequency at which the kernel flushes the disk cache!  To do that, you add the appropriate modifications to kernel parameters in /etc/sysctl.conf:<br />
vm.laptop_mode = 600<br />
vm.dirty_ratio = 40<br />
vm.dirty_background_ratio = 1<br />
vm.dirty_writeback_centisecs = 60000</p>
<p>In this way, you run a much higher risk losing (the recently written) data during a power loss, but just add a UPS with comms and you can save and shutdown cleanly, then no problems at all!</p>
<p>If you want to get a little bit more fancy (and have sufficient RAM), you can mount most of the /var stuff on a RAM drive (during boot up using simple tmpfs entries in mtab), and you can probably reduce the number of archive copies of each log file (see the cron logrotate configs) just to save precious CF space&#8230;</p>
<p>I&#8217;ll admit that I only have about a year&#8217;s worth of run time on the dozen or so machines that I set up this way, however the first experiment (close eyes and pretend it&#8217;s magnetic media) failed reliably within a month!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1191</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 09 Sep 2009 17:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1191</guid>
		<description>Hello again, Taher!
Now I finally made it to work. (Ubuntu Server 9.04 LAMP + SSH + Samba)

Ok... Found a typo in your posting. The lines for the fstab:

&quot;tmpfs /var/lib/nfs tmpfs 0 0&quot;
Should be:
&quot;tmpfs /var/lib/nfs tmpfs default 0 0&quot;

Then I wonder if the &quot;proc /proc proc defaults 0 0&quot; really is necessary, since the &quot;/proc&quot; is already made into tmpfs by default(?). You probably know that better than me.

The mtab solution gives an &quot;fail&quot; message during boot process:

rm /etc/mtab
ln -s /proc/mounts /etc/mtab

But it looks like everything is still okay. The &quot;/proc/mounts&quot; do have a little bit more lines and information than the regular &quot;/etc/mtab&quot; got. Maybe the fail message can be ignored without any worries.



The madoka -file for my setup looks like this:

------------------------------------------------------
#!/bin/sh
### BEGIN INIT INFO
# Provides:          madoka
# Required-Start:    $local_fs
# Required-Stop:     $local_fs
# Default-Start:     2 3 4 5
# Default-Stop:      1
# X-Start-Before:    bootlogs sysklogd
# Short-Description: recreate /var/log structure for Madoka
# Description:       recreate /var/log structure for Madoka
### END INIT INFO

do_start () {
# mkdir -p /var/log/mldonkey
 mkdir -p /var/log/apache2
   touch \
     /var/log/apache2/access.log               \
     /var/log/apache2/error.log                \
     /var/log/apache2/other_vhosts_access.log
   chown root:adm \
     /var/log/apache2                          \
     /var/log/apache2/access.log               \
     /var/log/apache2/error.log
   chmod 710 /var/log/apache2
   chmod 640 \
     /var/log/apache2/access.log               \
     /var/log/apache2/error.log
   chmod 644 /var/log/apache2/other_vhosts_access.log

 mkdir -p /var/log/apparmor
   chmod 755 /var/log/apparmor

 mkdir -p /var/log/apt
   touch /var/log/apt/term.log
   chmod 755 /var/log/apt
   chmod 600 /var/log/apt/term.log

 mkdir -p /var/log/ConsoleKit
   touch /var/log/ConsoleKit/history
   chmod 755 /var/log/ConsoleKit
   chmod 644 /var/log/ConsoleKit/history

 mkdir -p /var/log/dist-upgrade
   chmod 755 /var/log/dist-upgrade

 mkdir -p /var/log/fsck
   touch \
     /var/log/fsck/checkfs                     \
     /var/log/fsck/checkroot
   chown root:adm \
     /var/log/fsck/checkfs                     \
     /var/log/fsck/checkroot
   chmod 755 /var/log/fsck
   chmod 640 \
     /var/log/fsck/checkfs                     \
     /var/log/fsck/checkroot

 mkdir -p /var/log/installer
   chmod 755 /var/log/installer

 mkdir -p /var/log/landscape
   touch /var/log/landscape/sysinfo.log
   chown landscape:root \
     /var/log/landscape                        \
     /var/log/landscape/sysinfo.log
   chmod 755 /var/log/landscape
   chmod 644 /var/log/landscape/sysinfo.log

 mkdir -p /var/log/mysql
   chown mysql:adm /var/log/mysql
   chmod 2750 /var/log/mysql

 mkdir -p /var/log/news
   touch \
     /var/log/news/news.crit                   \
     /var/log/news/news.err                    \
     /var/log/news/news.notice
   chown news:news /var/log/news
   chown syslog:adm \
     /var/log/news/news.crit                   \
     /var/log/news/news.err                    \
     /var/log/news/news.notice
   chmod 2755 /var/log/news
   chmod 640 \
     /var/log/news/news.crit                   \
     /var/log/news/news.err                    \
     /var/log/news/news.notice

 mkdir -p \
   /var/log/samba                              \
   /var/log/samba/cores                        \
   /var/log/samba/cores/nmbd                   \
   /var/log/samba/cores/smbd                   \
   /var/log/samba/cores/winbindd
   chown root:adm /var/log/news
   chmod 750 /var/log/news
   chmod 700 \
     /var/log/samba/cores/nmbd                 \
     /var/log/samba/cores/smbd                 \
     /var/log/samba/cores/winbindd


 touch \
   /var/log/auth.log            \
   /var/log/boot                \
   /var/log/btmp                \
   /var/log/daemon.log          \
   /var/log/debug               \
   /var/log/dmesg               \
   /var/log/dpkg.log            \
   /var/log/faillog             \
   /var/log/kern.log            \
   /var/log/lastlog             \
   /var/log/lpr.log             \
   /var/log/mail.err            \
   /var/log/mail.info           \
   /var/log/mail.log            \
   /var/log/mail.warn           \
   /var/log/messages            \
   /var/log/mysql.err           \
   /var/log/mysql.log           \
   /var/log/pycentral.log       \
   /var/log/syslog              \
   /var/log/udev                \
   /var/log/user.log            \
   /var/log/wtmp

 chown syslog:adm \
   /var/log/auth.log            \
   /var/log/daemon.log          \
   /var/log/debug               \
   /var/log/kern.log            \
   /var/log/lpr.log             \
   /var/log/mail.err            \
   /var/log/mail.info           \
   /var/log/mail.log            \
   /var/log/mail.warn           \
   /var/log/messages            \
   /var/log/syslog              \
   /var/log/user.log

 chown root:utmp \
   /var/log/btmp                \
   /var/log/lastlog             \
   /var/log/wtmp

 chown root:adm \
   /var/log/boot                \
   /var/log/dmesg               \
   /var/log/dpkg.log

 chown mysql:adm \
   /var/log/mysql.err           \
   /var/log/mysql.log

 chown root:root \
   /var/log/faillog             \
   /var/log/pycentral.log       \
   /var/log/udev

 chmod 640 \
   /var/log/auth.log            \
   /var/log/boot                \
   /var/log/daemon.log          \
   /var/log/debug               \
   /var/log/dmesg               \
   /var/log/dpkg.log            \
   /var/log/kern.log            \
   /var/log/lpr.log             \
   /var/log/mail.err            \
   /var/log/mail.info           \
   /var/log/mail.log            \
   /var/log/mail.warn           \
   /var/log/messages            \
   /var/log/mysql.err           \
   /var/log/mysql.log           \
   /var/log/syslog              \
   /var/log/user.log

 chmod 664 \
   /var/log/btmp                \
   /var/log/lastlog             \
   /var/log/wtmp

 chmod 644 \
   /var/log/faillog             \
   /var/log/pycentral.log       \
   /var/log/udev
}

case &quot;$1&quot; in
 start)
 do_start
 ;;
 restart&#124;reload&#124;force-reload)
 echo &quot;Error: argument &#039;$1&#039; not supported&quot; &gt;&amp;2
 exit 3
 ;;
 stop)
 # No-op
 ;;
 *)
 echo &quot;Usage: $0 start&#124;stop&quot; &gt;&amp;2
 exit 3
 ;;
esac
------------------------------------------------------</description>
		<content:encoded><![CDATA[<p>Hello again, Taher!<br />
Now I finally made it to work. (Ubuntu Server 9.04 LAMP + SSH + Samba)</p>
<p>Ok&#8230; Found a typo in your posting. The lines for the fstab:</p>
<p>&#8220;tmpfs /var/lib/nfs tmpfs 0 0&#8243;<br />
Should be:<br />
&#8220;tmpfs /var/lib/nfs tmpfs default 0 0&#8243;</p>
<p>Then I wonder if the &#8220;proc /proc proc defaults 0 0&#8243; really is necessary, since the &#8220;/proc&#8221; is already made into tmpfs by default(?). You probably know that better than me.</p>
<p>The mtab solution gives an &#8220;fail&#8221; message during boot process:</p>
<p>rm /etc/mtab<br />
ln -s /proc/mounts /etc/mtab</p>
<p>But it looks like everything is still okay. The &#8220;/proc/mounts&#8221; do have a little bit more lines and information than the regular &#8220;/etc/mtab&#8221; got. Maybe the fail message can be ignored without any worries.</p>
<p>The madoka -file for my setup looks like this:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
#!/bin/sh<br />
### BEGIN INIT INFO<br />
# Provides:          madoka<br />
# Required-Start:    $local_fs<br />
# Required-Stop:     $local_fs<br />
# Default-Start:     2 3 4 5<br />
# Default-Stop:      1<br />
# X-Start-Before:    bootlogs sysklogd<br />
# Short-Description: recreate /var/log structure for Madoka<br />
# Description:       recreate /var/log structure for Madoka<br />
### END INIT INFO</p>
<p>do_start () {<br />
# mkdir -p /var/log/mldonkey<br />
 mkdir -p /var/log/apache2<br />
   touch \<br />
     /var/log/apache2/access.log               \<br />
     /var/log/apache2/error.log                \<br />
     /var/log/apache2/other_vhosts_access.log<br />
   chown root:adm \<br />
     /var/log/apache2                          \<br />
     /var/log/apache2/access.log               \<br />
     /var/log/apache2/error.log<br />
   chmod 710 /var/log/apache2<br />
   chmod 640 \<br />
     /var/log/apache2/access.log               \<br />
     /var/log/apache2/error.log<br />
   chmod 644 /var/log/apache2/other_vhosts_access.log</p>
<p> mkdir -p /var/log/apparmor<br />
   chmod 755 /var/log/apparmor</p>
<p> mkdir -p /var/log/apt<br />
   touch /var/log/apt/term.log<br />
   chmod 755 /var/log/apt<br />
   chmod 600 /var/log/apt/term.log</p>
<p> mkdir -p /var/log/ConsoleKit<br />
   touch /var/log/ConsoleKit/history<br />
   chmod 755 /var/log/ConsoleKit<br />
   chmod 644 /var/log/ConsoleKit/history</p>
<p> mkdir -p /var/log/dist-upgrade<br />
   chmod 755 /var/log/dist-upgrade</p>
<p> mkdir -p /var/log/fsck<br />
   touch \<br />
     /var/log/fsck/checkfs                     \<br />
     /var/log/fsck/checkroot<br />
   chown root:adm \<br />
     /var/log/fsck/checkfs                     \<br />
     /var/log/fsck/checkroot<br />
   chmod 755 /var/log/fsck<br />
   chmod 640 \<br />
     /var/log/fsck/checkfs                     \<br />
     /var/log/fsck/checkroot</p>
<p> mkdir -p /var/log/installer<br />
   chmod 755 /var/log/installer</p>
<p> mkdir -p /var/log/landscape<br />
   touch /var/log/landscape/sysinfo.log<br />
   chown landscape:root \<br />
     /var/log/landscape                        \<br />
     /var/log/landscape/sysinfo.log<br />
   chmod 755 /var/log/landscape<br />
   chmod 644 /var/log/landscape/sysinfo.log</p>
<p> mkdir -p /var/log/mysql<br />
   chown mysql:adm /var/log/mysql<br />
   chmod 2750 /var/log/mysql</p>
<p> mkdir -p /var/log/news<br />
   touch \<br />
     /var/log/news/news.crit                   \<br />
     /var/log/news/news.err                    \<br />
     /var/log/news/news.notice<br />
   chown news:news /var/log/news<br />
   chown syslog:adm \<br />
     /var/log/news/news.crit                   \<br />
     /var/log/news/news.err                    \<br />
     /var/log/news/news.notice<br />
   chmod 2755 /var/log/news<br />
   chmod 640 \<br />
     /var/log/news/news.crit                   \<br />
     /var/log/news/news.err                    \<br />
     /var/log/news/news.notice</p>
<p> mkdir -p \<br />
   /var/log/samba                              \<br />
   /var/log/samba/cores                        \<br />
   /var/log/samba/cores/nmbd                   \<br />
   /var/log/samba/cores/smbd                   \<br />
   /var/log/samba/cores/winbindd<br />
   chown root:adm /var/log/news<br />
   chmod 750 /var/log/news<br />
   chmod 700 \<br />
     /var/log/samba/cores/nmbd                 \<br />
     /var/log/samba/cores/smbd                 \<br />
     /var/log/samba/cores/winbindd</p>
<p> touch \<br />
   /var/log/auth.log            \<br />
   /var/log/boot                \<br />
   /var/log/btmp                \<br />
   /var/log/daemon.log          \<br />
   /var/log/debug               \<br />
   /var/log/dmesg               \<br />
   /var/log/dpkg.log            \<br />
   /var/log/faillog             \<br />
   /var/log/kern.log            \<br />
   /var/log/lastlog             \<br />
   /var/log/lpr.log             \<br />
   /var/log/mail.err            \<br />
   /var/log/mail.info           \<br />
   /var/log/mail.log            \<br />
   /var/log/mail.warn           \<br />
   /var/log/messages            \<br />
   /var/log/mysql.err           \<br />
   /var/log/mysql.log           \<br />
   /var/log/pycentral.log       \<br />
   /var/log/syslog              \<br />
   /var/log/udev                \<br />
   /var/log/user.log            \<br />
   /var/log/wtmp</p>
<p> chown syslog:adm \<br />
   /var/log/auth.log            \<br />
   /var/log/daemon.log          \<br />
   /var/log/debug               \<br />
   /var/log/kern.log            \<br />
   /var/log/lpr.log             \<br />
   /var/log/mail.err            \<br />
   /var/log/mail.info           \<br />
   /var/log/mail.log            \<br />
   /var/log/mail.warn           \<br />
   /var/log/messages            \<br />
   /var/log/syslog              \<br />
   /var/log/user.log</p>
<p> chown root:utmp \<br />
   /var/log/btmp                \<br />
   /var/log/lastlog             \<br />
   /var/log/wtmp</p>
<p> chown root:adm \<br />
   /var/log/boot                \<br />
   /var/log/dmesg               \<br />
   /var/log/dpkg.log</p>
<p> chown mysql:adm \<br />
   /var/log/mysql.err           \<br />
   /var/log/mysql.log</p>
<p> chown root:root \<br />
   /var/log/faillog             \<br />
   /var/log/pycentral.log       \<br />
   /var/log/udev</p>
<p> chmod 640 \<br />
   /var/log/auth.log            \<br />
   /var/log/boot                \<br />
   /var/log/daemon.log          \<br />
   /var/log/debug               \<br />
   /var/log/dmesg               \<br />
   /var/log/dpkg.log            \<br />
   /var/log/kern.log            \<br />
   /var/log/lpr.log             \<br />
   /var/log/mail.err            \<br />
   /var/log/mail.info           \<br />
   /var/log/mail.log            \<br />
   /var/log/mail.warn           \<br />
   /var/log/messages            \<br />
   /var/log/mysql.err           \<br />
   /var/log/mysql.log           \<br />
   /var/log/syslog              \<br />
   /var/log/user.log</p>
<p> chmod 664 \<br />
   /var/log/btmp                \<br />
   /var/log/lastlog             \<br />
   /var/log/wtmp</p>
<p> chmod 644 \<br />
   /var/log/faillog             \<br />
   /var/log/pycentral.log       \<br />
   /var/log/udev<br />
}</p>
<p>case &#8220;$1&#8243; in<br />
 start)<br />
 do_start<br />
 ;;<br />
 restart|reload|force-reload)<br />
 echo &#8220;Error: argument &#8216;$1&#8242; not supported&#8221; &gt;&amp;2<br />
 exit 3<br />
 ;;<br />
 stop)<br />
 # No-op<br />
 ;;<br />
 *)<br />
 echo &#8220;Usage: $0 start|stop&#8221; &gt;&amp;2<br />
 exit 3<br />
 ;;<br />
esac<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taher Shihadeh</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1187</link>
		<dc:creator>Taher Shihadeh</dc:creator>
		<pubDate>Wed, 09 Sep 2009 11:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1187</guid>
		<description>Hi Peter! You&#039;re absolutely right!
I posted the wrong script, the first -non LSB-Init conformant- version that would have update-rc.d choke on it. I also missed the &#039;.&#039; on the invocation. I&#039;ve just updated the post. Thanks.

I&#039;m afraid I was a bit sloppy when I took the notes to write this ;-)
Hopefully I&#039;ll do a better job when I write about the Live-system installation. I&#039;m currently installing this same setup in under 200MB, so I&#039;ve got another 50-60 to save updates in my 256MB card.
I just need to make some free time to document the process, though.

Let me know if you find any more errors.</description>
		<content:encoded><![CDATA[<p>Hi Peter! You&#8217;re absolutely right!<br />
I posted the wrong script, the first -non LSB-Init conformant- version that would have update-rc.d choke on it. I also missed the &#8216;.&#8217; on the invocation. I&#8217;ve just updated the post. Thanks.</p>
<p>I&#8217;m afraid I was a bit sloppy when I took the notes to write this ;-)<br />
Hopefully I&#8217;ll do a better job when I write about the Live-system installation. I&#8217;m currently installing this same setup in under 200MB, so I&#8217;ve got another 50-60 to save updates in my 256MB card.<br />
I just need to make some free time to document the process, though.</p>
<p>Let me know if you find any more errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1185</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 09 Sep 2009 10:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1185</guid>
		<description>Hello Taher,
Thank you for this posting!

I&#039;m trying to apply this on a pure Jauntu Server installation. All seems to work except the script (madoka) that is supposed to re-create the environment inside the &#039;/var/log directory&#039;.

First,
Running &#039;update-rc.d madoka start 05 2&#039; gives an error back, complaining about a missing &quot;.&quot; at the end of the arguments.
I think I&#039;ve solved it by running &quot;update-rc.d madoka start 05 2 .&quot; instead.

Second,
The script doesn&#039;t run at boot, making the log file daemon complaining on missing files and folders.

I have not tried to apply the post on a Jauntu Desktop, since this is not my goal. So, how can the script execution be solved?

Sincerely,
Peter</description>
		<content:encoded><![CDATA[<p>Hello Taher,<br />
Thank you for this posting!</p>
<p>I&#8217;m trying to apply this on a pure Jauntu Server installation. All seems to work except the script (madoka) that is supposed to re-create the environment inside the &#8216;/var/log directory&#8217;.</p>
<p>First,<br />
Running &#8216;update-rc.d madoka start 05 2&#8242; gives an error back, complaining about a missing &#8220;.&#8221; at the end of the arguments.<br />
I think I&#8217;ve solved it by running &#8220;update-rc.d madoka start 05 2 .&#8221; instead.</p>
<p>Second,<br />
The script doesn&#8217;t run at boot, making the log file daemon complaining on missing files and folders.</p>
<p>I have not tried to apply the post on a Jauntu Desktop, since this is not my goal. So, how can the script execution be solved?</p>
<p>Sincerely,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Barrow</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1141</link>
		<dc:creator>Chris Barrow</dc:creator>
		<pubDate>Wed, 24 Jun 2009 21:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1141</guid>
		<description>Hi Taher,

From the reading I have done on the swap partition it does not get used unless you run out of RAM, as I have 2GB this is fairly unlikely depending on what I get up to of course. So far my monitoring has shown 0 swap usage.

I have followed your advice on moving the log files to tmpfs, I did consider disabling these completely but decided that for debug they would be useful. I have also moved my browser cache to tmp which is in tmpfs.

So far everything is running great with a full Ubuntu install on the 8gb card, still have 3.3gb free on the card though with the Amazon S3 it is really unlimited.

I will give it a few weeks and maybe splash out on a 300x CF card, the card make is SILICON POWER from Taiwan.</description>
		<content:encoded><![CDATA[<p>Hi Taher,</p>
<p>From the reading I have done on the swap partition it does not get used unless you run out of RAM, as I have 2GB this is fairly unlikely depending on what I get up to of course. So far my monitoring has shown 0 swap usage.</p>
<p>I have followed your advice on moving the log files to tmpfs, I did consider disabling these completely but decided that for debug they would be useful. I have also moved my browser cache to tmp which is in tmpfs.</p>
<p>So far everything is running great with a full Ubuntu install on the 8gb card, still have 3.3gb free on the card though with the Amazon S3 it is really unlimited.</p>
<p>I will give it a few weeks and maybe splash out on a 300x CF card, the card make is SILICON POWER from Taiwan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taher</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1138</link>
		<dc:creator>Taher</dc:creator>
		<pubDate>Tue, 23 Jun 2009 16:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1138</guid>
		<description>Chris: Nice setup, but I&#039;ve read that CFs tend to die in a couple of months, so at the very least I would turn off the swap.

Ravi: Assuming your CF /dev/sda1 is mounted under /mnt/cf, something like this should do:

grub-install /mnt/cf --recheck /dev/sda

This will install the bootloader, which you&#039;ll have to configure. Enter a chroot environment on your cf card and use update-grub

If you need more details, you could check out this post. There&#039;s a script that will show you every step needed: http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html</description>
		<content:encoded><![CDATA[<p>Chris: Nice setup, but I&#8217;ve read that CFs tend to die in a couple of months, so at the very least I would turn off the swap.</p>
<p>Ravi: Assuming your CF /dev/sda1 is mounted under /mnt/cf, something like this should do:</p>
<p>grub-install /mnt/cf &#8211;recheck /dev/sda</p>
<p>This will install the bootloader, which you&#8217;ll have to configure. Enter a chroot environment on your cf card and use update-grub</p>
<p>If you need more details, you could check out this post. There&#8217;s a script that will show you every step needed: <a href="http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html" rel="nofollow">http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Barrow</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1137</link>
		<dc:creator>Chris Barrow</dc:creator>
		<pubDate>Tue, 23 Jun 2009 09:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1137</guid>
		<description>Very interesting article, I have not implemented any of the suggestions as yet as I am still researching.

I set up my Acer laptop a couple of days back using a IDE CF card adapter I purchased form Hong Kong for £1.99 GBP and an 8GB x200 CF card for  £18.86 GBP. I installed the latest Ubuntu 9.04 - Jaunty.
For file storage I am using Amazon S3 and jungleDisk mapping my storage as drives on my laptop so basically I have unlimited storage. This works grate for Documents which now point to my S3 storage and I also have a separate storage area for Photo&#039;s.

The system runs quit fast and boots a lot quicker, my original Laptop HD was a 100gb 7200rpm drive so quite quick.

I have as yet not turned off my swap file or moved any log files to tempfs.

chris@chris-laptop:~$ sudo hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   888 MB in  2.00 seconds = 443.59 MB/sec
 Timing buffered disk reads:   80 MB in  3.00 seconds =  26.65 MB/sec</description>
		<content:encoded><![CDATA[<p>Very interesting article, I have not implemented any of the suggestions as yet as I am still researching.</p>
<p>I set up my Acer laptop a couple of days back using a IDE CF card adapter I purchased form Hong Kong for £1.99 GBP and an 8GB x200 CF card for  £18.86 GBP. I installed the latest Ubuntu 9.04 &#8211; Jaunty.<br />
For file storage I am using Amazon S3 and jungleDisk mapping my storage as drives on my laptop so basically I have unlimited storage. This works grate for Documents which now point to my S3 storage and I also have a separate storage area for Photo&#8217;s.</p>
<p>The system runs quit fast and boots a lot quicker, my original Laptop HD was a 100gb 7200rpm drive so quite quick.</p>
<p>I have as yet not turned off my swap file or moved any log files to tempfs.</p>
<p>chris@chris-laptop:~$ sudo hdparm -tT /dev/sda</p>
<p>/dev/sda:<br />
 Timing cached reads:   888 MB in  2.00 seconds = 443.59 MB/sec<br />
 Timing buffered disk reads:   80 MB in  3.00 seconds =  26.65 MB/sec</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ravi</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1136</link>
		<dc:creator>Ravi</dc:creator>
		<pubDate>Tue, 23 Jun 2009 05:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1136</guid>
		<description>Hi all,

Can any one tell me how to install grub on compact flash

I&#039;m using kernel 2.26.8</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>Can any one tell me how to install grub on compact flash</p>
<p>I&#8217;m using kernel 2.26.8</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taher</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1135</link>
		<dc:creator>Taher</dc:creator>
		<pubDate>Thu, 18 Jun 2009 19:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1135</guid>
		<description>I started playing around with live-helper, which seemed the way to go back in March. But really never had the chance to actually finish and document the process before I added the 2.5&quot;HDD. It definitely is still on my to-do list.</description>
		<content:encoded><![CDATA[<p>I started playing around with live-helper, which seemed the way to go back in March. But really never had the chance to actually finish and document the process before I added the 2.5&#8243;HDD. It definitely is still on my to-do list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danl</title>
		<link>http://unixwars.com/2009/03/07/jaunty-server-on-compact-flash-running-ubuntu-904-on-a-thin-client/comment-page-1/#comment-1134</link>
		<dc:creator>danl</dc:creator>
		<pubDate>Thu, 18 Jun 2009 19:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://unixwars.com/?p=360#comment-1134</guid>
		<description>It&#039;s great you are looking into this, since I can&#039;t find any other info on how to do this. I really need option #2 - everything in memory. Have you been able to make any progress? I&#039;ve successfully used Ubuntu&#039;s USB Creator to create a bootable USB from my ISO, but I&#039;d like to do the same with an IDE flash drive too.</description>
		<content:encoded><![CDATA[<p>It&#8217;s great you are looking into this, since I can&#8217;t find any other info on how to do this. I really need option #2 &#8211; everything in memory. Have you been able to make any progress? I&#8217;ve successfully used Ubuntu&#8217;s USB Creator to create a bootable USB from my ISO, but I&#8217;d like to do the same with an IDE flash drive too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
