changeset 1050:333c8f799302

Update lots and lots of web pages for the project name change to Aboriginal Linux.
author Rob Landley <rob@landley.net>
date Sun, 02 May 2010 17:15:06 -0500
parents 0e063506fd67
children a134d8bc8768
files www/FAQ.html www/about.html www/documentation.html www/downloads/README www/downloads/binaries/README www/header.html www/history.html www/news.html www/presentation.html www/screenshots/index.html
diffstat 10 files changed, 131 insertions(+), 357 deletions(-) [+]
line wrap: on
line diff
--- a/www/FAQ.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/FAQ.html	Sun May 02 17:15:06 2010 -0500
@@ -5,6 +5,8 @@
 <ul>
 <li><p><a href=#where_start>Q: Where do I start?</a></p></li>
 
+<li><p><a href=#name_change>Q: Didn't this used to be called Firmware Linux?</a></p></li>
+
 <li><p><a href=#add_package>Q: How do I add $PACKAGE to my system image's root filesystem?</a></p></li>
 
 <li><p><a href=#ubuntu_mispackaged_qemu>Q: ./run-emulator.sh says qemu-system-mips isn't found, but I installed qemu.  Why isn't this working?</a></p></li>
@@ -22,16 +24,6 @@
 
 <p>Most people want to do one of three things:</p>
 
-<ul>
-<li><p>Download a prebuilt cross compiler and cross-compile stuff with it.</p>
-
-<p>Go <a href=screenshots>here</a> and download the appropriate
-cross-compiler-<b>$TARGET</b>.tar.bz2 for your $TARGET, extract it, add its
-"bin" directory to your $PATH, and use the appropriate $TARGET-cc and
-$TARGET-ld and so on to compile your program.  (The tool names have prefixes
-so they can be in the same $PATH as your host's existing compiler.)</p>
-</li>
-
 <li><p>Download a prebuilt system image, boot it up under the emulator, and
 compile stuff natively for a target.</p>
 
@@ -51,11 +43,11 @@
 the virtual network, speeding up native builds significantly.<p>
 </li>
 
-<li><p>Build their own cross compilers and system images from source, using
+<li><p>Build your own cross compilers and system images from source, using
 the build scripts.</p>
 
-<p>Go to the <a href=downloads>downloads directory</a> and grab the highest
-numbered release tarball, extract it, and run <b>./build.sh</b> to list
+<p>Go to the <a href=downloads>downloads directory</a>, grab the most recent
+release tarball, extract it, and run <b>./build.sh</b> to list
 the available targets.  The run <b>./build.sh $TARGET</b> to compile
 the one you like.  The results wind up in the "build" directory.</p>
 
@@ -69,31 +61,41 @@
 them as environment variables.</p>
 
 <p>To grab the latest development version of the build scripts out of the
-source control system, go to the <a href=/ht/firmware>mercurial archive</a>.
+source control system, go to the
+<a href=http://impactlinux.com/hg/aboriginal>mercurial archive</a>.
 If you don't want to install mercurial, you can grab a
-<a href=/hg/firmware/archive/tip.tar.bz2>tarball</a> of the current code at
+<a href=http://impactlinux.com/hg/aboriginal/archive/tip.tar.bz2>tarball</a> of the current code at
 any time.</p>
 </li>
 
+<ul>
+<li><p>Download a prebuilt cross compiler and cross-compile stuff with it.</p>
+
+<p>Go <a href=screenshots>here</a> and download the appropriate
+cross-compiler-<b>$TARGET</b>.tar.bz2 for your $TARGET, extract it, add its
+"bin" directory to your $PATH, and use the appropriate $TARGET-cc and
+$TARGET-ld and so on to compile your program.  (The tool names have prefixes
+so they can be in the same $PATH as your host's existing compiler.)</p>
+</li>
+
 </ul>
 
-<p>For the first two, the <a href=downloads/binaries>downloads/binaries
-directory</a> has all the prebuilt binaries for the current release.</p>
-
-<p>For the third, go to the <a href=downloads>downloads directory and grab
-a release tarball</a>, or else look at the <a href=/ht/firmware>mercurial
-archive</a> to grab the latest development version out of source control.
-(If you don't want to mess with mercurial, you can grab a
-<a href=/hg/firmware/archive/tip.tar.bz2>tarball</a> of the current code
-at any time.</p>
-
 <p>If all else fails, look at the pretty
 <a href=screenshots>screenshots</a>.</p>
 
+<a name=name_change /><h2>Q: Didn't this used to be called Firmware Linux?</h2>
+
+<p>A: Yup.  The name changed shortly before the 1.0 release in 2010.</p>
+
+<p>If you're really bored, there's a page on
+<a href=history.html>the history of the project</a>, which includes the
+rationale for the name change.</p>
+
 <a name=add_package /><h2>Q: How do I add $PACKAGE to my system image's root filesystem?</h2>
 
-<p>A: The easy way is to build a new system image with a writeable root
-filesystem and enough extra space to install your package in.</p>
+<p>A: Use the rw-system-image instead of the system-image.  This gives
+you a writeable root filesystem with enough extra space to install your
+package in.</p>
 
 <p>FWL builds squashfs images by default, and the prebuilt binary tarballs in
 the downloads/binaries directory are built with the default values.  Squashfs
@@ -121,10 +123,9 @@
 <p>Note: since this is a writeable image, you'll have to fsck it.  You can
 also use "tune2fs -j" to turn it into an ext3 image.</p>
 
-<p>(The "hard way" to go with the above "easy way" is to cross compile the
-additional package and add it to the build/root-filesystem-$TARGET directory
-so system-image.sh packages it up into the squashfs.  You're on your own if
-you want to do that, it's not recommended.  Native building is much easier.)</p>
+<p>(You can also use the BUILD_RW_SYSTEM_IMAGE environment variable, which
+tells build.sh to package the system image two ways, creating a
+rw-system-image tarball with the above options.)</p>
 
 <a name=ubuntu_mispackaged_qemu /><h2>Q: ./run-emulator.sh says qemu-system-$TARGET isn't found, but I installed the qemu package and the executable "qemu" is there.  Why isn't this working?</h2>
 
--- a/www/about.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/about.html	Sun May 02 17:15:06 2010 -0500
@@ -1,17 +1,17 @@
 <!--#include file="header.html" -->
 
-<p>Firmware Linux is a set of tools for building custom virtual
+<p>Aboriginal Linux is a set of tools for building custom virtual
 machines.  It lets you boot virtual PowerPC, ARM, MIPS and other
 exotic systems on your x86 laptop, and do development in them.</p>
 
-<p>Firmware Linux was written to serve the embedded community, but it
+<p>Aboriginal Linux was written to serve the embedded community, but it
 has other uses as well - portability auditing and cross-platform
 regression testing, for starters.</p>
 
-<b><h1><a href=documentation.html>What is Firmware Linux?</a></h1></b>
+<b><h1><a href=documentation.html>What is Aboriginal Linux?</a></h1></b>
 
 <blockquote>
-<p>Firmware Linux is a build system for creating bootable system
+<p>Aboriginal Linux is a build system for creating bootable system
 images to be run under virtualization, intended to reduce or even
 eliminate the need for cross compiling.</p>
 
@@ -26,34 +26,35 @@
 page</a>.</p>
 </blockquote>
 
-<b><h1><a href=downloads>Downloading Firmware Linux</a></h1></b>
+<b><h1><a href=downloads>Downloading Aboriginal Linux</a></h1></b>
 
 <blockquote>
 <b><h2><a href=downloads>Source Code</a></h2></b>
-<p>The <a href=downloads>Firmware Linux source code</a> is
+<p>The <a href=downloads>Aboriginal Linux source code</a> is
 a series of shell scripts which run to create the various binary
 images.  See the <a href=downloads/README>README</a> for usage instructions,
 and the <a href=news.html>release notes</a>.</p>
 
 <p>Several <a href=downloads/binaries>prebuilt binary images</a>
-are available, based on the current Firmware Linux release.  The
+are available, based on the current Aboriginal Linux release.  The
 <a href=downloads/README>README</a> describes each tarball.  The
 release notes on the <a href=news.html>news page</a> explain recent
 changes.</p>
 
 </blockquote>
 
-<b><h1><a href=/hg/firmware>Development</a></h1></b>
-
-<p>The project maintains a <a href=/hg/firmware>development repository</a>
+<b><h1><a href=http://impactlinux.com/hg/aboriginal>Development</a></h1></b>
+<blockquote>
+<p>The project maintains a <a href=http://impactlinux.com/hg/aboriginal>development repository</a>
 using the Mercurial source control system.  This includes RSS feeds for
-<a href=/hg/firmware/rss-log>each checkin</a>
-and for <a href=/hg/firmware/rss-tags>new releases</a>.</p>
+<a href=http://impactlinux.com/hg/aboriginal/rss-log>each checkin</a>
+and for <a href=http://impactlinux.com/hg/aboriginal/rss-tags>new releases</a>.</p>
 
-<p>Questions about Firmware Linux should be addressed to the project's
+<p>Questions about Aboriginal Linux should be addressed to the project's
 <a href=http://lists.impactlinux.com/listinfo.cgi/firmware-impactlinux.com>mailing
-list</a>, or the IRC channel #firmware on irc.freenode.org.  The project
-maintainer's <a href=http://landley.net/notes.html>blog</a> often includes notes about
-ongoing Firmware Linux development.</p>
+list</a>, or the IRC channel #edev on irc.freenode.org.  The project
+maintainer's <a href=http://landley.net/notes.html>blog</a> often includes
+notes about ongoing Aboriginal Linux development.</p>
+</blockquote>
 
 <!--#include file="footer.html" -->
--- a/www/documentation.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/documentation.html	Sun May 02 17:15:06 2010 -0500
@@ -20,15 +20,15 @@
 
 <p>The name "Firmware Linux" reflects FWL's origins as a tool for
 embedded development. It provides an easy way to get started with
-that, building your own code against uClibc and testing it on non-x86
-hardware platforms. But it has other uses as well, including:
+that, building your own code against uClibc and testing it on various
+hardware platforms. But it has other uses as well, including
 cross-platform regression testing, portability auditing, and toolchain
 debugging.</p>
 
 <p>This documentation uses the name "Firmware Linux" (or abbreviation
 "FWL") to refer to the <a href=downloads>build system</a>, and calls
 the output of the build a "<a
-href=downloads/binaries/system-image>system image</a>".  The build
+href=downloads/binaries>system image</a>".  The build
 system is implemented as a series of bash scripts and configuration
 files which compile a Linux development environment for the specified
 target system and package it into a bootable binary image.</p>
@@ -83,12 +83,13 @@
 <p>System images boot a complete linux system under an emulator.  Each
 system-image tarball contains an ext2 root filesystem image, a Linux kernel
 configured to run under the emulator <a href=http://bellard.org/qemu/>QEMU</a>,
-and a run-emulator.sh script.</p>
+and scripts launch the virtual system under the emulator in various
+configurations.</p>
 
-<p>The steps to test boot a system image under qemu 0.9.1 are:</p>
+<p>The steps to test boot a system image under QEMU are:</p>
 <ul>
-<li>install QEMU 0.9.1 or later</li>
-<li>download the appropriate <a href=downloads/image>prebuilt binary tarball</a>
+<li>install QEMU 0.12.4 or later</li>
+<li>download the appropriate <a href=downloads/binaries>prebuilt binary tarball</a>
 for the target you're interested in</li>
 <li>extract it: <b>tar -xvjf system-image-$TARGET.tar.bz2</b></li>
 <li>cd into it: <b>cd system-image-$TARGET</b></li>
--- a/www/downloads/README	Sun May 02 16:16:51 2010 -0500
+++ b/www/downloads/README	Sun May 02 17:15:06 2010 -0500
@@ -1,10 +1,11 @@
-The downloads directory contains the Firmware Linux build scripts, which is
-the source code for the FWL project.  If you would like to build your own
-cross compiler or target system image from source, use these build scripts.
-They're written in bash and should be fairly easy to read.
+The downloads directory contains the Aboriginal Linux build scripts, which is
+the source code for the Aboriginal Linux project.  If you would like to build
+your own cross compiler or target system image from source, use these build
+scripts.  They're written in bash and should be fairly easy to read.
 
 If you want to download prebuilt binary cross compilers or system images,
-see the downloads/binaries directory (which has its own README).
+see the downloads/binaries directory (which has its own README).  The
+rest of this README describes the contents of the current source tarball.
 
 These scripts include the following stages:
 
--- a/www/downloads/binaries/README	Sun May 02 16:16:51 2010 -0500
+++ b/www/downloads/binaries/README	Sun May 02 17:15:06 2010 -0500
@@ -1,7 +1,7 @@
 The downloads/binaries directory contains prebuilt binary images, created by
-running sources/more/buildall.sh in the most recent Firmware Linux source
+running sources/more/buildall.sh in the most recent Aboriginal Linux source
 tarball.  The source packages for these binaries are mirrored at
-"http://impactlinux.com/fwl/mirror".
+"http://aboriginal.impactlinux.com/mirror".
 
 The following tarballs are found here:
 
@@ -30,11 +30,11 @@
   which you can extract and run on an appropriate target the same way you
   can extract and run the cross-compiler on the host.
 
-  You don't need this when using FWL's root filesystem images, which provide
+  You don't need this when using Aboriginal Linux's system images, which provide
   their own native compiler.  This is provided for use with existing target
   filesystems.
 
-system-image-ARCH.tar.bz2
+system-image-$ARCH.tar.bz2
 
   Prepackaged bootable system images image for each target.
 
@@ -43,7 +43,7 @@
   invoke the emulator QEMU on the two of them.
 
   This allows you to compile additional packages natively under QEMU.
-  Just wget the source tarball and build it normally.
+  (Just wget the source tarball at the shell prompt, and build it normally.)
 
   The run-emulator.sh wrapper script should produce a shell prompt, with
   the emulator's stdin/stdout connected to the emulated system's
@@ -62,6 +62,16 @@
   As far as the emulated build environment is concerned, it's still performing
   simple single-context native builds.)
 
+rw-system-image-$ARCH
+
+  Same as system-image-$ARCH, except that the root filesystem image is
+  a writeable ext2 image instead of a read-only squashfs.  This takes up
+  more space, and can't be shared between multiple simultaneous emulator
+  instances.  The advantage is that additional software can be installed
+  into the root filesystem.
+
+  This is created with the BUILD_RW_SYSTEM_IMAGE=1 config option.
+
 busybox-$ARCH
 
   This is a prebuilt static busybox binary for the given target, implementing
--- a/www/header.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/header.html	Sun May 02 17:15:06 2010 -0500
@@ -1,25 +1,21 @@
 <table border=0 cellpadding=4 cellspacing=0>
 <tr><td>
   <table border=0 cellspacing=1 cellpadding=4>
-    <tr><td><h1>Firmware Linux</h1></td></tr>
+    <tr><td><h1>Aboriginal Linux</h1></td></tr>
   </table>
 </td>
 <td>
 <table border=1><tr><td>
 <ul>
-<li><p>Build scripts (implemented in bash) which produce cross compilers, root
-filesystems, and system images for various hardware targets, configured to run
-under QEMU and provide an emulated native test/development environment based
-on BusyBox and uClibc.</p></li>
-<li><p>Current release (version 0.9.10, February 2, 2010):
-<a href=/code/firmware/downloads/firmware-0.9.10.tar.bz2>build scripts</a>,
-<a href=/code/firmware/downloads/binaries>prebuilt binaries</a>,
-<a href=/code/firmware/screenshots>screen shots</a>.</p></li>
+<li><p>Current release: (version 0.9.11, March 29, 2010):
+<a href=downloads/firmware-0.9.11.tar.bz2>build scripts</a>,
+<a href=downloads/binaries>prebuilt binaries</a>,
+<a href=screenshots>screen shots</a>.</p></li>
 <li><p>Development version:
-<a href=/hg/firmware>mercurial repository</a>,
-<a href=http://impactlinux.com/hg/firmware/rss-log>rss commit feed</a>,
-<a href=/hg/hgwebdir.cgi/firmware/archive/tip.tar.bz2>current tarball</a>,
-<a href="http://lists.impactlinux.com/listinfo.cgi/firmware-impactlinux.com">mailing list</a>.
+<a href=http://impactlinux.com/hg/aboriginal>mercurial repository</a>,
+<a href=http://impactlinux.com/hg/aboriginal/rss-log>rss commit feed</a>,
+<a href=http://impactlinux.com/hg/aboriginal/archive/tip.tar.bz2>current tarball</a>,
+<a href=http://lists.impactlinux.com/listinfo.cgi/firmware-impactlinux.com">mailing list</a>.
 </p></li>
 </ul>
 </td><tr></table>
@@ -30,33 +26,36 @@
 <table border=1><tr><td>
   <b>About</b>
   <ul>
-    <li><a href="news.html">News</a></li>
-    <li><a href="about.html">About</a></li>
-    <li><a href="screenshots">Screenshots</a></li>
-    <li><a href="documentation.html">Documentation</a></li>
-    <li><a href="downloads/README">README</a></li>
-    <li><a href="FAQ.html">FAQ</a></li>
-    <li><a href="presentation.html">Presentation</a></li>
+    <li><a href=news.html>News</a></li>
+    <li><a href=about.html>About</a></li>
+    <li><a href=README>README</a></li>
+    <li><a href=screenshots>Screenshots</a></li>
+    <li><a href=documentation.html>Documentation</a></li>
+    <li><a href=FAQ.html>FAQ</a></li>
+    <li><a href=presentation.html>Presentation</a></li>
   </ul>
   <b>Download</b>
   <ul>
-    <li><a href="downloads">Release Tarballs</a></li>
-    <li><a href="downloads/binaries">Prebuilt Binaries</a></li>
+    <li><a href=downloads>Release Tarballs</a>
+      <ul><li><a href=downloads/README>README</a></li></ul>
+    </li>
+    <li><a href=downloads/binaries>Prebuilt Binaries</a></li>
+    <ul><li><a href=downloads/binaries/README>README</a></li></ul>
   </ul>
   <b>Development</b>
   <ul>
     <li><a href="http://lists.impactlinux.com/listinfo.cgi/firmware-impactlinux.com">Mailing List</a></li>
     <li>IRC #edev on irc.freenode.org</li>
     <li><a href="http://landley.net/notes.html">Maintainer's Blog</a></li>
-    <li><a href="/hg/firmware">Source Control</a></li>
+    <li><a href="http://impactlinux.com/hg/aboriginal">Source Control</a></li>
     <ul>
-      <li><a href="/hg/firmware/archive/tip.tar.bz2">Snapshot</a></li>
+      <li><a href="http://impactlinux.com/hg/aboriginal/archive/tip.tar.bz2">Snapshot</a></li>
     </ul>
   </ul>
   <b>Mirrors</b>
   <ul>
-    <li><a href=http://impactlinux.com/fwl>Main site</a></li>
-    <li><a href=http://landley.net/fwl>Mirror</a></li>
+    <li><a href=http://aboriginal.impactlinux.com>Main site</a></li>
+    <li><a href=http://aboriginal.landley.net>Mirror</a></li>
   </ul>
 </td></tr></table>
 </td>
--- a/www/history.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/history.html	Sun May 02 17:15:06 2010 -0500
@@ -2,9 +2,9 @@
 
 <!--#include file="header.html" -->
 
-<h1>Where did "Firmware Linux" come from?  Our story so far...</h1>
+<h1>Where did "Aboriginal Linux" come from?  Our story so far...</h1>
 
-<p>My name is Rob Landley, and I've been working on Firmware Linux on and off
+<p>My name is Rob Landley, and I've been working on Aboriginal Linux on and off
 since the late 90's.  It's what got me into BusyBox and uClibc, embedded
 development, compiler internals, and so on.  Now it's where I put together
 everything else I'm doing (like toybox, tinycc, and the relocatable gcc
@@ -88,7 +88,7 @@
 packages I'd need to build and the constant maintenance of keeping it up to
 date kept that idea way down on my to-do list.</p>
 
-<h1>FWL v0: The WebOffice version</h1>
+<h1>Version 0: The WebOffice version</h1>
 
 <p>Towards the end of 2000 I met the founders of a local start-up through
 the Austin Linux Users Group (two Taiwanese guys named Lan and Lon), and at
@@ -371,8 +371,8 @@
 on Eric Raymond's couch for a few months doing an "editing pass" on The Art of
 Unix Programming that expanded the book from 9 chapters to 20.</p>
 
-<h1>FWL v1: Relaunch based on BusyBox and uClibc, and why it's called
-Firmware Linux</h1>
+<h1>Version 1: Relaunch based on BusyBox and uClibc, now called
+"Firmware Linux"</h1>
 
 <p>When I returned to Austin in August 2003, I bought a condo near the
 University of Texas (and near Metro, my favorite 24 hour coffee shop with
@@ -628,7 +628,7 @@
 
 <p>One new command was switch_root, for initramfs support.  I wrote an
 initramfs file for the kernel's Documentation directory because I investigated
-it for FWL.  (And later gave my first OLS presenation on the topic,
+it for Firmware Linux.  (And later gave my first OLS presenation on the topic,
 and write an article series about it when I worked at TimeSys.)</p>
 
 <p>Another new command was mdev, which was a rewrite of
--- a/www/news.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/news.html	Sun May 02 17:15:06 2010 -0500
@@ -3,6 +3,19 @@
 <b><h1>News</h1></b>
 
 <hr>
+<h2><a name="05-02-2010" />May 2, 2010</h2>
+<p>The name of the project is changing from Firmware Linux to Aboriginal
+Linux.  The new URL is "http://aboriginal.impactlinux.com".</p>
+
+<p>Some reasons to move away from the old name are
+<a href=http://lists.impactlinux.com/pipermail/firmware-impactlinux.com/2009-October/000374.html>listed here</a>,
+and some reasons to pick the new name are covered in
+<a href=http://lists.impactlinux.com/pipermail/firmware-impactlinux.com/2010-April/000671.html>this thread</a>.</p>
+
+<p>Some links may be broken while we switch over.  Let us know what we've
+missed on the mailing list...</p>
+
+<hr>
 <h2><a name="03-29-2010" />March 29, 2010</h2>
 <p><a href=downloads/firmware-0.9.11.tar.bz2>Version 0.9.11</a> is out,
 based on <a href=http://impactlinux.com/hg/firmware/shortlog/1020>hg commit
--- a/www/presentation.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/presentation.html	Sun May 02 17:15:06 2010 -0500
@@ -547,7 +547,7 @@
 
 <a name="howto_dev_environment" /><h2>Orthogonal layers</h2>
 
-<ul>	<li>The following is based on what our Firmware Linux project does.
+<ul>	<li>The following is based on what our Aboriginal Linux project does.
 	<ul>	<li>Other build systems need to do the same things, most of them just aren't as careful to separate the layers.</li>
 	</ul></li>
 	<li>Each of these layers can be swapped out
@@ -582,11 +582,11 @@
 
 <ul>	<li>Entirely optional step, can be skipped if your host is set up right, but that's seldom a good idea.</li>
 	<li>Serves same purpose as LFS chapter 5: an airlock preventing leakage.
-	<ul>	<li>LFS chroots, FWL adjusts the <code>$PATH</code> to remove stuff.</li>
+	<ul>	<li>LFS chroots, Aboriginal adjusts the <code>$PATH</code> to remove stuff.</li>
 		<li>Remember, adding stuff is easy. Removing stuff the host already has so cross compiling doesn't accidentally find and leak it into your build is one of the hard parts.</li>
 	</ul></li>
 	<li>Provides prerequisites automatically, no need to install packages by hand as root
-	<ul>	<li>Nothing the FWL build system does requires root access on the host. That's an explicit design goal.</li>
+	<ul>	<li>Nothing the Aboriginal build system does requires root access on the host. That's an explicit design goal.</li>
 	</ul></li>
 	<li>Isolate your build from variations in the host distro
 	<ul>	<li>Provide known versions of each tool</li>
@@ -613,7 +613,7 @@
 	</ul></li>
 	<li>The simple compiler above can be created without prerequisites</li>
 	<li>Thus creating a simple cross compiler is always the first step</li>
-	<li>For FWL releases we build a second cross compiler that's statically linked against uClibc on the host, which is a two-stage process
+	<li>For Aboriginal releases we build a second cross compiler that's statically linked against uClibc on the host, which is a two-stage process
 	<ul>	<li>First build an i686-gcc compiler, which outputs 32-bit x86 binaries</li>
 		<li>Then rebuild the cross compilers as <code>--static</code> binaries using that as the host compiler</li>
 		<li>This increases portability and decreases size. You can run the resulting binaries on 32 bit Red Hat 9 and on 64-bit Ubuntu 9.04.</li>
@@ -658,7 +658,7 @@
 	</ul></li>
 	<li>Install native toolchain
 	<ul>	<li>Same packages as cross compiler, plus uClibc++</li>
-		<li>Note, FWL builds a statically linked native compiler, which you can extract and run on an arbitrary target system.
+		<li>Note, Aboriginal Linux builds a statically linked native compiler, which you can extract and run on an arbitrary target system.
 		<ul>	<li>Same theory as the statically linked cross compiler, only for native builds on systems that don't come with a uClibc toolchain.</li>
 		</ul></li>
 	</ul></li>
@@ -954,7 +954,7 @@
 			<li>Note that an initramfs uses "<code>rdinit=</code>" instead of "<code>init=</code>".</li>
 		</ul></li>
 		<li>Try pointing init= at a statically linked "hello world" program.
-		<ul>	<li>FWL contains one at <code>/bin/hello-static</code></li>
+		<ul>	<li>Aboriginal Linux contains one at <code>/bin/hello-static</code></li>
 			<li>If this works, your dynamic linker is probably at fault.</li>
 		</ul></li>
 		<li>Then try a dynamically linked hello world. If that fails:
@@ -1258,7 +1258,7 @@
 	<ul>	<li>No <code>CROSS_COMPILER=prefix-</code>, no <code>$HOSTCC</code></li>
 		<li>As far as the build is concerned, it's building fully natively</li>
 	</ul></li>
-	<li>FWL sets this up for you automatically. To do it by hand:
+	<li>Aboriginal Linux sets this up for you automatically. To do it by hand:
 	<ul>	<li>on host<br>
 <strong><code>PATH=/path/to/cross-compiler-binaries /usr/bin/distccd --listen 127.0.0.1 --log-stderr --daemon -a 127.0.0.1 --no-detach --jobs $CPUS</code></strong>
 		</li>
@@ -1266,7 +1266,7 @@
 <pre><code>mkdir ~/distcc
 ln -s /usr/bin/distcc ~/distcc/gcc
 ln -s /usr/bin/distcc ~/distcc/cc
-cd ~/firmware
+cd ~/aboriginal
 export PATH=~/distcc:$PATH
 export DISTCC_HOSTS=10.0.2.2/$CPUS
 ./cross-compiler.sh armv4l</code></pre></li>
--- a/www/screenshots/index.html	Sun May 02 16:16:51 2010 -0500
+++ b/www/screenshots/index.html	Sun May 02 17:15:06 2010 -0500
@@ -1,253 +1,1 @@
-<html>
-<title>Available Targets</title>
-<body>
-<p>Each $TARGET includes some or all of the following links.  Click on
-the link name to get a description.</p>
-<ul>
-<li><a href="#screenshot">Screenshot</a></li>
-<li><a href="#crosscompiler">Cross Compiler</a></li>
-<li><a href="#nativecompiler">Native Compiler</a></li>
-<li><a href="#rootfilesystem">Root Filesystem</a></li>
-<li><a href="#systemimage">System Image</a></li>
-<li><a href="#busybox">Static Busybox Binary</a></li>
-<li><a href="#dropbear">Static Dropbear Binary</a></li>
-<li><a href="#strace">Static Strace Binary</a></li>
-</ul>
-
-<p>The following $TARGET families are available:</p>
-
-<ul>
-<li><a href="#arm">ARM</a> (<a href="../architectures.html#arm">description</a>)
-</li>
-<li><strike><a href="#m68k">M68k</a> (<a href="../architectures.html#m68k">description</a>)</strike></li>
-<li><a href="#mips">Mips</a> (<a href="../architectures.html#mips">description</a>)</li>
-<li><a href="#ppc">PowerPC</a> (<a href="../architectures.html#ppc">description</a>)</li>
-<li><strike><a href="#sparc">Sparc</a> (<a href="../architectures.html#sparc">description</a>)</strike></li>
-<li><a href="#sh4">Super Hitachi</a> (<a href="../architectures.html#sh4">description</a>)</li>
-<li><a href="#x86">x86</a> (<a href="../architectures.html#x86">description</a>)</li>
-</ul>
-
-<hr /><h1><center><a name="arm" /><a href="../architectures.html#arm">ARM</a></center></h1><hr />
-
-<table>
-<tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>ARMv4l</h2>
-<p>ARMv4, little endian, soft float, OABI</p>
-<!--#include file="screenshot-armv4l.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>ARMv4tl</h2>
-<p>ARMv4t, little endian, soft float, EABI</p>
-<!--#include file="screenshot-armv4tl.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>ARMv5l</h2>
-<p>ARMv5, little endian, VFP, EABI</p>
-<!--#include file="screenshot-armv5l.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>ARMv6l</h2>
-<p>ARMv6, little endian, VFP, EABI</p>
-<!--#include file="screenshot-armv6l.html" -->
-
-</tr></table>
-
-<hr /><h1><center><a name="mips" /><a href="../architectures.html#mips">Mips</a></center></h1></hr />
-
-<table><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>Mips</h2>
-<p>MIPS r4k, big endian</p>
-<!--#include file="screenshot-mips.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>Mipsel</h2>
-<p>MIPS r4k, little endian</p>
-<!--#include file="screenshot-mipsel.html" -->
-
-</tr></table>
-
-<hr /><h1><center><a name="mips" /><a href="../architectures.html#ppc">Power PC</a></center></h1></hr />
-
-<table><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>PowerPC</h2>
-<p>PowerPC 405, 32-bit, big endian</p>
-<!--#include file="screenshot-powerpc.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>PowerPC 440</h2>
-<p>PowerPC 440, 32-bit, big endian</p>
-<!--#include file="screenshot-powerpc-440fp.html" -->
-
-</tr></table>
-
-<hr /><h1><center><a name="sh4" /><a href="../architectures.html#sh4">Super Hitachi</a></center></h1><hr />
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>SH4</h2>
-<p>Super Hitachi 4, 32-bit</p>
-<!--#include file="screenshot-sh4.html" -->
-
-</tr></table>
-
-<hr /><h1><center><a name="x86" /><a href="../architectures.html#x86">x86</a></center></h1><hr />
-
-<table><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>i586</h2>
-<p>Pentium</p>
-<!--#include file="screenshot-i586.html" -->
-
-</tr><tr>
-
-<td><table border=1><tr><td colspan=2 border=1><center>
-<h2>i686</h2>
-<p>Pentium II</p>
-<!--#include file="screenshot-i686.html" -->
-
-</tr></table>
-
-<ul>
-<hr />
-<li>
-<p><a name="screenshot" /><b>Screenshot</b> - The boot messages produced by launching this system
-image under qemu (using the "run-emulator.sh" script included in each system
-image tarball), and then typing "cat /proc/cpuinfo" inside the emulated system.</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="crosscompiler" /><b>Cross Compiler</b> - A compiler which runs on a standard PC host (x86
-or x86-64 Linux system) and produces output binaries for the specified $TARGET
-architecture (Linux binaries linked against uClibc).  To use, extract the
-tarball and add its "bin" subdirectory to your $PATH, and then compile
-with $TARGET-cc as your compiler name, such as:</p>
-
-<blockquote>
-<pre>
-mips-cc root-filesystem-mips/usr/src/thread-hello2.c -lpthread -static -o hello
-</pre>
-</blockquote>
-
-<p>The "bin" subdirectory contains a bunch of tools prefixed with the $TARGET
-name followed by a dash, such as "powerpc-strip".  The "lib" subdirectory
-contains shared libraries built for the target, including uClibc as the
-standard C library to link binaries against and uClibc++ as the standard
-C++ library.  The "include" subdirectory contains the header files
-#included by programs.</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="nativecompiler" /><b>Native Compiler</b> - A compiler which runs on the $TARGET and
-produces output binaries which also run on the $TARGET.</p>
-
-<p>You should be able to extract this inside an existing target system, add
-its "bin" directory to the $PATH, and use it as you would the cross compiler.
-(Except its binaries have no $TARGET- prefixes.)</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="rootfilesystem" /><b>Root Filesystem</b> - A root filesystem for the target, suitable for
-chroot-ing into, containing the smallest/simplest Linux development environment
-capable of rebuilding itself from source code.</p>
-
-<p>This system is based on busybox and uClibc, includes a native compiler
-toolchain (binutils, gcc, linux headers), additional development utilities
-(make, bash, distcc), and miscelaneous files and directories (such as some /etc
-files and an sbin/init.sh boot script).</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="systemimage" /><b>System Image</b> - A bootable linux kernel and filesystem image
-configured for use with the emulator QEMU.</p>
-
-<p>The filesystem image contains the same set of files as the root filesystem
-tarball, this time packaged into a squashfs.  It also has Linux kernel
-configured for qemu, and shell scripts to launch qemu to run this kernel
-with this filesystem image.</p>
-
-<p>Basically you download this tarball, extract it, cd into the directory,
-and "./run-emulator.sh".  This gives you a shell prompt inside the emulator,
-ala the above screen shots.  Type "exit" when done.</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="busybox" /><b>Static Busybox Binary</b> - Busybox implements
-hundreds of standard [LINK] command line utilities in a single binary,
-generally smaller than one megabyte.</p>
-
-<p>Busybox is a "swiss army knife" binary, which behaves differently based on
-the name of its executable.  This means that populating a directory of
-symlinks to the busybox binary can provide access to all these commands
-without requiring multiple copies of the binary.</p>
-
-<p>This binary is statically linked against uClibc, so can be run
-independently on a target system, in a chroot environment, or via QEMU
-application emulation.</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="dropbear" /><b>Static Dropbear Binary</b> - Dropbear is
-a combination ssh server and client (and scp, and an encryption key generator)
-in a single executable (another "swiss army knife" binary) that weighs in at
-around 100k.</p>
-
-<p>This binary is statically linked against uClibc for maximum
-portability.</p>
-</li>
-
-<hr />
-
-<li>
-<p><a name="strace" /><b>Static Strace Binary</b> - Strace is a
-debugging tool that runs a child process, sniffing all the child's
-system calls and printing a description of them to stderr, ala:</p>
-
-<blockquote>
-<pre>
-execve("/bin/false", ["false"], [/* 34 vars */]) = 0
-brk(0)                                  = 0x14ca000
-mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb
-e69a44000
-access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
-...
-</pre>
-</blockquote>
-
-<p>And so on.  If a binary is failing or hanging, strace can give you an
-idea of what it's doing, at least when it interacts with the rest of the
-system.</p>
-
-<p>This binary is statically linked against uClibc for maximum portability.</p>
-</li>
-</ul>
-
-</body>
-</html>
+oldindex.html
\ No newline at end of file