-BusyBox is maintained by Rob Landley, and +BusyBox is maintained by Rob Landley, and licensed under the -GNU GENERAL PUBLIC LICENSE +GNU GENERAL PUBLIC LICENSE
@@ -56,7 +56,7 @@ consider these fine companies! If you wish to be a sponsor, or if you have already contributed and would like -your name added here, email Erik. +your name added here, email Erik. diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html index 91e756f..f70c0e3 100644 --- a/docs/busybox.net/news.html +++ b/docs/busybox.net/news.html @@ -7,7 +7,7 @@ maintainership to Rob Landley was license enforcement. BusyBox and uClibc's existing license enforcement efforts (pro-bono representation by Erik's father's law firm, and the - Hall of Shame), haven't + Hall of Shame), haven't scaled to match the popularity of the projects. So we put our heads together and did the obvious thing: ask Pamela Jones of Groklaw for suggestions. She @@ -17,9 +17,9 @@ Software Freedom Law Center has agreed to represent BusyBox and uClibc. We join a number of other free and open source software projects (such as - X.org, + X.org, Wine, and - Plone + in being represented by a fairly cool bunch of lawyers, which is not a phrase you get to use every day.
@@ -35,7 +35,7 @@The new stable release is BusyBox 1.1.0. It has a number of improvements, including several new applets. - (It also has a few rough spots, + (It also has a few rough spots, but we're trying out a "release early, release often" strategy to see how that works. Expect 1.1.1 sometime in March.)
diff --git a/docs/busybox.net/programming.html b/docs/busybox.net/programming.html index f54f018..f5433f5 100644 --- a/docs/busybox.net/programming.html +++ b/docs/busybox.net/programming.html @@ -22,7 +22,7 @@Busybox aims to be the smallest and simplest correct implementation of the standard Linux command line tools. First and foremost, this means the @@ -31,7 +31,7 @@ and cleanest implementation we can manage, be standards compliant, minimize run-time memory usage (heap and stack), run fast, and take over the world.
-Busybox is like a swiss army knife: one thing with many functions. The busybox executable can act like many different programs depending on @@ -53,9 +53,9 @@ binaries for each applet, and a "libbb.so" to make the busybox common code available as a shared library. Neither is ready yet at the time of this writing.
- + -The directory "applets" contains the busybox startup code (applets.c and busybox.c), and several subdirectories containing the code for the individual @@ -95,7 +95,7 @@ html, txt, and man page formats) in the docs directory. See adding an applet to busybox for more information.
-Most non-setup code shared between busybox applets lives in the libbb directory. It's a mess that evolved over the years without much auditing @@ -110,7 +110,7 @@ of open(), close(), read(), and write() that test for their own failures and/or retry automatically, linked list management functions (llist.c), command line argument parsing (getopt_ulflags.c), and a whole lot more.
-To add a new applet to busybox, first pick a name for the applet and a corresponding CONFIG_NAME. Then do this:
@@ -151,10 +151,10 @@ bugs. Be sure to try both "allyesconfig" and "allnoconfig" (and -The standard we're paying attention to is the "Shell and Utilities" -portion of the Open +portion of the Open Group Base Standards (also known as the Single Unix Specification version 3 or SUSv3). Note that paying attention isn't necessarily the same thing as following it.
@@ -330,7 +330,7 @@ return 0 unless it has hit the end of input, and an attempt to write 0 bytes should be ignored by the OS.)As for short writes, play around with two processes piping data to each -other on the command line (cat bigfile | gzip > out.gz) and suspend and +other on the command line (cat bigfile | gzip > out.gz) and suspend and resume a few times (ctrl-z to suspend, "fg" to resume). The writer can experience short writes, which are especially dangerous because if you don't notice them you'll discard data. They can also happen when a system is under @@ -340,7 +340,7 @@ text console scrolling...)
So will data always be read from the far end of a pipe at the same chunk sizes it was written in? Nope. Don't rely on that. For one -counterexample, see rfc 896
+counterexample, see rfc 896 for Nagle's algorithm, which waits a fraction of a second or so before sending out small amounts of data through a TCP/IP connection in case more data comes in that can be merged into the same packet. (In case you were diff --git a/docs/busybox.net/shame.html b/docs/busybox.net/shame.html index 2c800c8..5cd868a 100644 --- a/docs/busybox.net/shame.html +++ b/docs/busybox.net/shame.html @@ -68,7 +68,7 @@ the busybox license by releasing the source code with your product.If you don't want to mess with subversion, you can download -all BusyBox patches or check the +all BusyBox patches or check the ten most recent.
In a gui environment, you'll probably want a web browser. -Konqueror Embedded requires QT -(or QT Embedded), but not KDE. The Dillo -requires GTK+, but not Gnome. Or you can try the graphical +Konqueror Embedded requires QT +(or QT Embedded), but not KDE. The Dillo +requires GTK+, but not Gnome. Or you can try the graphical version of links.
-- cgit v1.1