changeset 23:a5e1ebc1d6ee

Redo the index page (flesh it out about halfway), and a couple tweaks to the license page.
author Rob Landley <>
date Sun, 05 Nov 2006 01:01:34 -0500
parents 64d6e0a2f030
children c8d0f1876c40
files www/index.html www/license.html
diffstat 2 files changed, 69 insertions(+), 9 deletions(-) [+]
line wrap: on
line diff
--- a/www/index.html	Sat Nov 04 23:57:18 2006 -0500
+++ b/www/index.html	Sun Nov 05 01:01:34 2006 -0500
@@ -1,6 +1,64 @@
+<h2>What is ToyBox?</h2>
+<p>Toybox aims to implement all the Linux command line utilities in under one
+megabyte.  This project aims for small, simple, and efficient implementations,
+with configurable levels of functionality.  It should scale from tiny embedded
+systems up to full fledged desktop and development environments.</p>
+<p>The project is <a href=license.html>Licensed under GPL version 2</a>.</p>
+<p>Toybox can be built as a single "swiss army knife" executable (ala BusyBox
+or Red Hat's Nash), or each command can be built as a traditional independent
+<h2>Which commands are planned?</h2>
+<b><h3>Relevant Standards</h3></b>
+<p>Most commands are implemented according to
+<a href=>The
+Single Unix Specification version 3</a>.  This does not mean that Toybox is
+implementing every SUSv3 utility: some such as SCCS and ed are obsolete, while
+others such as c99 are outside the scope of the project.  Toybox also isn't
+implementing full internationalization support: it should be 8-bit clean and
+handle UTF-8, but otherwise we leave this to X11 and higher layers.</p>
+<p>The other major sources of commands are the Linux man pages, and testing
+the behavior of existing commands (although not generally looking at their
+source code).</p>
+<b><h3>Command Shell</h3></b>
+<p>The Toybox Shell aims to be a reasonable bash replacement.  It implements
+the "sh" and "toysh" commands, plus the built-in commands "cd" and "exit".
+The following additional commands may be built into the shell (but not as
+separate executables): cd, exit, if, while, for, function, fg, bg, jobs, source,
+<a href="">alias</a>,
+export, set, unset, read, trap, and exec.</p>
+<b><h3>General Purpose Commands:</h3></b>
+<b><h3>Development tools:</h3></b>
+<p>Commands: ar, make [TODO]</p>
+<b><h2>What commands are implemented?</h2></b>
+<p>Toybox is a work in progress, and nowhere near a 1.0 release.  The first
+commit was September 27, 2006, and work is ongoing.</p>
+<p>Partial (in progress): sh/toysh (cd, exit), df, which.</p>
+<p>Complete: hello, pwd.</p>
 <p>This project is maintained as a mercurial archive.  To get a copy of the
 current development version, "hg clone static-",
 or check <a href=download>the download directory</a> for release tarballs.
--- a/www/license.html	Sat Nov 04 23:57:18 2006 -0500
+++ b/www/license.html	Sun Nov 05 01:01:34 2006 -0500
@@ -3,9 +3,10 @@
 <h2>Toybox is licensed under the terms of GPLv2.</h2>
 <p>The complete text of the General Public License version 2 is included in the
-file LICENSE in each source tarball.  Version 2 is the only version of
-this license which toybox is distributed under.  (I.E. It doesn't have the
-strange "or later" dual license some projects have.)</p>
+file LICENSE in each source tarball, and again at the end of this page.
+Version 2 is the only version of this license which toybox is distributed
+under.  (I.E. It doesn't have the strange "or later" dual license some projects
@@ -22,7 +23,8 @@
 individual source files.</b>  This doesn't mean you can change what license the
 code is under, or that you can remove other people's copyright notices.  You
 certainly can't change the test of the GPL itself.  What it means is that if
-you use this code in a project that distributes source in zip files instead of
+a file says "see file LICENSE in this tarball for details" and you use this
+code in a project that distributes source in zip files instead of
 tarballs, or your package's copy of the GPLv2 text isn't in a file called
 "LICENSE", it's silly to preserve an obsolete notice verbatim and add some
 kind of "correction" after the old notice.</p>
@@ -30,7 +32,7 @@
 <p>Some lawyers seem to think a strict reading of GPLv2 section 1 (and later
 sections including section 1 by reference) requires maintaining old notices in
 perpetuity.  Even if you had code that used to be dual licensed, but created
-a derived work that's just under one of the two licenses, so the old license
+a derived work that's just under one of the two licenses, and the old license
 notice is not just strange or misleading but actually incorrect for the new
 file.  (For example, splicing GPLv2 only code into a dual "GPLv2 or later"
 project produces a result that can be distributed under the terms of GPLv2,
@@ -155,7 +157,7 @@
   The precise terms and conditions for copying, distribution and
 modification follow.
@@ -210,7 +212,7 @@
     License.  (Exception: if the Program itself is interactive but
     does not normally print such an announcement, your work based on
     the Program is not required to print an announcement.)
 These requirements apply to the modified work as a whole.  If
 identifiable sections of that work are not derived from the Program,
 and can be reasonably considered independent and separate works in
@@ -268,7 +270,7 @@
 access to copy the source code from the same place counts as
 distribution of the source code, even though third parties are not
 compelled to copy the source along with the object code.
   4. You may not copy, modify, sublicense, or distribute the Program
 except as expressly provided under this License.  Any attempt
 otherwise to copy, modify, sublicense or distribute the Program is
@@ -325,7 +327,7 @@
 This section is intended to make thoroughly clear what is believed to
 be a consequence of the rest of this License.
   8. If the distribution and/or use of the Program is restricted in
 certain countries either by patents or by copyrighted interfaces, the
 original copyright holder who places the Program under this License