hush (a Bourne-style shell) for the GNO multitasking environment on the Apple IIgs
Go to file
Eric Andersen 837f058fb3 Peter Kjellerstedt at axis.com writes:
Hello,

the attached patch should bring extra/config in line
with the Linux 2.6.7 sources.

The following are the commit messages for the respective
files from the Linux bk-repository:

checklist.c:
* fix menuconfig choice item help display

confdata.c:
* config: choice fix
* kconfig: don't rename target dir when saving config

expr.c, expr.h:
* config: disable debug prints

mconf.c:
* fix menuconfig choice item help display

menu.c:
* Kconfig: use select statements

symbol.c:
* config: choice fix
* Avoid bogus warning about recursive dependencies
* c99 struct initialiser conversions

textbox.c:
* janitor: don't init statics to 0

util.c:
* fix lxdialog behaviour

//Peter
2004-07-15 06:01:05 +00:00
applets Larry Doolittle writes: 2004-04-14 17:51:38 +00:00
archival Update reference for zip format 2004-06-06 10:22:43 +00:00
console-tools Remove trailing whitespace. Update copyright to include 2004. 2004-03-15 08:29:22 +00:00
coreutils If read were to return with an error, bad things would happen. Fix it. 2004-05-26 15:21:19 +00:00
debian Remove the CONFIG_FEATURE_SH_APPLETS_ALWAYS_WIN option. It was sortof 2004-04-07 09:34:27 +00:00
debianutils Fix several problems with start-stop-daemon, add -m support 2004-04-13 18:28:46 +00:00
docs Fixup a few documentation bugs 2004-07-14 10:01:04 +00:00
editors Rob Landley writes: 2004-05-26 10:03:33 +00:00
examples Add an example inetd.conf file 2004-04-07 10:34:16 +00:00
findutils Make the grep option values a bit less horrible 2004-05-26 11:48:29 +00:00
include Patch from Bastian Blank: 2004-06-22 10:07:17 +00:00
init Patch from Bastian Blank: 2004-06-22 10:07:17 +00:00
libbb Revert my previous commit 2004-06-25 09:01:09 +00:00
libpwdgrp Larry Doolittle writes: 2004-04-14 17:51:38 +00:00
loginutils Patch from Bastian Blank: 2004-06-22 10:07:17 +00:00
miscutils Woops, the previous commit was an accident, its supplied in the patch, 2004-06-05 07:58:18 +00:00
modutils Fixup some cases of "QM_MODULES: not implemented" for both 2004-07-13 00:09:34 +00:00
networking Paul Fox writes: 2004-06-29 00:48:30 +00:00
patches Device table support for makedevs, the previous behaviour can been 2004-06-05 07:54:52 +00:00
procps Larry Doolittle writes: 2004-04-14 17:51:38 +00:00
scripts Peter Kjellerstedt at axis.com writes: 2004-07-15 06:01:05 +00:00
shell Fix compile error when math support disabled. 2004-06-25 07:05:13 +00:00
sysdeps/linux Do not prompt about FDISK large disk support when LFS is enabled. 2004-05-25 11:30:22 +00:00
sysklogd Do not mess with the console logging level unless 2004-06-25 11:23:03 +00:00
testsuite Add two fundamental tests for copying directories 2004-04-18 13:35:56 +00:00
util-linux Avoid a number of places where large drives could wrap a uint, and 2004-06-28 23:50:31 +00:00
.cvsignore Yet another major rework of the BusyBox config system, using the considerably 2002-12-05 08:41:41 +00:00
.indent.pro
AUTHORS Update my email address, document some of my tasks in the AUTHORS file 2004-04-25 05:11:19 +00:00
Changelog bump version, prepare for -pre10 2004-04-13 19:38:17 +00:00
INSTALL Remove trailing whitespace. Update copyright to include 2004. 2004-03-15 08:29:22 +00:00
LICENSE Update a bunch of docs. Run a script to update my email addr. 2003-07-14 21:21:08 +00:00
Makefile Eliminate all trace of the sgml based docs. It was a noble effort, 2004-04-06 15:26:25 +00:00
README "Mac OS X" is how it is written on the Apple website 2004-04-12 15:05:10 +00:00
Rules.mak bump version, prepare for -pre10 2004-04-13 19:38:17 +00:00
TODO Re-add the TODO list, mention tr 2004-05-01 00:49:49 +00:00

Please see the LICENSE file for details on copying and usage.

BusyBox combines tiny versions of many common UNIX utilities into a single
small executable. It provides minimalist replacements for most of the utilities
you usually find in GNU coreutils, util-linux, etc. The utilities in BusyBox
generally have fewer options than their full-featured GNU cousins; however, the
options that are included provide the expected functionality and behave very
much like their GNU counterparts.

BusyBox has been written with size-optimization and limited resources in mind.
It is also extremely modular so you can easily include or exclude commands (or
features) at compile time. This makes it easy to customize your embedded
systems. To create a working system, just add /dev, /etc, and a Linux kernel.
BusyBox provides a fairly complete POSIX environment for any small or embedded
system.

BusyBox is extremely configurable.  This allows you to include only the
components you need, thereby reducing binary size. Run 'make config' or
'make menuconfig' to select the functionality that you wish to enable.

After the build is complete, a busybox.links file is generated.  This is
used by 'make install' to create symlinks to the BusyBox binary for all
compiled in functions.  By default, 'make install' will place the symlink
forest into `pwd`/_install unless you have defined the PREFIX environment
variable (i.e., 'make PREFIX=/tmp/foo install')

If you wish to install hard links, rather than symlinks, you can use
'make PREFIX=/tmp/foo install-hardlinks' instead.

----------------

Supported architectures:

   BusyBox in general will build on any architecture supported by gcc.  It has
   a few specialized features added for __sparc__ and __alpha__.  insmod
   functionality is currently limited to x86, ARM, SH3/4, powerpc, m68k,
   MIPS, cris, and v850e.

Supported C Libraries:

   glibc-2.0.x, glibc-2.1.x, glibc-2.2.x, glibc-2.3.x, uClibc.  People
   are looking at newlib and diet-libc, but consider them unsupported,
   untested, or worse.  Linux-libc5 is no longer supported -- you
   should probably use uClibc instead if you want a small C library.

Supported kernels:

   Full functionality requires Linux 2.2.x or better.  A large fraction of the
   code should run on just about anything.  While the current code is fairly
   Linux specific, it should be fairly easy to port the majority of the code
   to, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you are into
   that sort of thing).

----------------

Getting help:

When you find you need help, you can check out the BusyBox mailing list
archives at http://busybox.net/lists/busybox/ or even join
the mailing list if you are interested.

----------------

Bugs:

If you find bugs, please submit a detailed bug report to the BusyBox mailing
list at busybox@mail.busybox.net.  A well-written bug report should include a
transcript of a shell session that demonstrates the bad behavior and enables
anyone else to duplicate the bug on their own machine. The following is such
an example:

    To: busybox@mail.busybox.net
    From: diligent@testing.linux.org
    Subject: /bin/date doesn't work

    Package: BusyBox
    Version: 1.00

    When I execute BusyBox 'date' it produces unexpected results.
    With GNU date I get the following output:

	$ date
	Sat Mar 27 14:19:41 MST 2004

    But when I use BusyBox date I get this instead:

	$ date
	illegal instruction

    I am using Debian unstable, kernel version 2.4.25-vrs2 on a Netwinder,
    and the latest uClibc from CVS.  Thanks for the wonderful program!

	-Diligent

Note the careful description and use of examples showing not only what BusyBox
does, but also a counter example showing what an equivalent GNU app does.  Bug
reports lacking such detail may never be fixed...  Thanks for understanding.

----------------

Downloads:

Source for the latest released version, as well as daily snapshots, can always
be downloaded from
    http://busybox.net/downloads/

----------------

CVS:

BusyBox now has its own publicly browsable CVS tree at:
    http://busybox.net/cgi-bin/cvsweb/busybox/

Anonymous CVS access is available.  For instructions, check out:
    http://busybox.net/cvs_anon.html

For those that are actively contributing there is even CVS write access:
    http://busybox.net/cvs_write.html

----------------

Please feed suggestions, bug reports, insults, and bribes back to:
	Erik Andersen
	<andersen@codepoet.org>