<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.damnsmalllinux.org/blog">
<channel>
 <title>Fordi's blog</title>
 <link>http://www.damnsmalllinux.org/blog/blog/46</link>
 <description></description>
 <language>en</language>
<item>
 <title>uDSL - Delays, delays, delays</title>
 <link>http://www.damnsmalllinux.org/blog/node/183</link>
 <description>&lt;p&gt;Well, it's April, and the work on uDSL continues.&lt;/p&gt;
&lt;p&gt;I blame my discovery of UnionFS.  It makes my dream of a unified ramless extension system real.&lt;/p&gt;
&lt;p&gt;Well, that, and the advances in things like udev and a minor patch to the loop kernel module (nothing big, just that my kernel now supports a full whopping 1M loop devices.)&lt;/p&gt;
&lt;p&gt;That, UnionFS and SquashFS put together let me make a 10M DSL core with the ability to add any software you want at no extra charge.&lt;/p&gt;
&lt;p&gt;Well, some extra charge.  from my calculations, you'll need an aditional 64k of ram per extension you add on.  &lt;/p&gt;
&lt;p&gt;Additionally, everything's being cross-compiled from scratch for two target platforms:  i386 PC and G3 Mac.&lt;/p&gt;
</description>
 <pubDate>Mon, 11 Apr 2005 05:07:06 +0000</pubDate>
</item>
<item>
 <title>uDSL - a personal experiment</title>
 <link>http://www.damnsmalllinux.org/blog/node/123</link>
 <description>&lt;p&gt;I wish to make an attempt to rebuild the entirety of DSL with a few implementation changes - an attempt to squeeze a few more bytes out of the already tight DSL project.&lt;/p&gt;
&lt;p&gt;1: everything (and I do mean everything) will be rebuilt from source using uClibc.&lt;/p&gt;
&lt;p&gt;2: I will be building a 2.6.10 kernel using the knoppix 3.7 configuration.  &lt;/p&gt;
&lt;p&gt;3: SquashFS will be implemented upon KNOPPIX.  sqsh type modules will be supported.&lt;/p&gt;
&lt;p&gt;4: The x apps, all user applications, and basically anything non-system will be removed and repackaged.  X-based user apps will be available in the least ram-using packages if available (like firefox), or be given a new package if not.  The generic command line non-system and x apps will be in udsl-clapps.sqsh and udsl-xapps.sqsh.&lt;/p&gt;
</description>
 <pubDate>Tue, 25 Jan 2005 20:04:47 +0000</pubDate>
</item>
<item>
 <title>SquashFS update</title>
 <link>http://www.damnsmalllinux.org/blog/node/50</link>
 <description>&lt;p&gt;Ok, I'm having fun with this:&lt;/p&gt;
&lt;p&gt;I have a squashfs.o that works in DSL 0.9.1, and will continue to work until DSL runs under a new kernel.  It DOES NOT REQUIRE A NEW KERNEL.  That's right.  It's just a module, and you can plug it in just like any other module.&lt;/p&gt;
&lt;p&gt;mksquashfs seems to work just fine with no extra libs.&lt;/p&gt;
&lt;p&gt;I'm working on an experimental proof-of-concept design for a SquashFS DSL module.  It will have all the benefits of both .dsl and .uci extensions, along with a feature stolen from .deb packages, but will not occupy much RAM at all. &lt;/p&gt;
&lt;p&gt;Essentially, it gets mounted like a uci.  Since the package for this is (and has to be) a dsl, mkwriteable is already run.  Once the module is mounted, it is linked into the root filesystem, its user.tar extracted into your home dir, and /sdmrc run (the feature stolen from .deb packages - controlscripts).  It also has /etc/init.d/sdm-config and /etc/rc5.d/S02sdm-config linking to that - ensuring that you can have .sdm - type modules on a liveCD.&lt;/p&gt;
</description>
 <pubDate>Mon,  3 Jan 2005 19:09:49 +0000</pubDate>
</item>
</channel>
</rss>
