documentation and typo fixes. By Dan Fandrich (dan AT coneharvesters.com)
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
@@ -133,7 +133,7 @@ Seems to be somewhat old, but contains useful bits for getty.c hacking
|
||||
characters will operate on the incoming data before it is delivered to
|
||||
the user.
|
||||
|
||||
In non-canonical mode, incoming data is quanitified by use of the
|
||||
In non-canonical mode, incoming data is quantified by use of the
|
||||
c_cc[VMIN and c_cc[VTIME] values in termios.c_cc[].
|
||||
|
||||
Some programmers use the select() call to detect the completion of a
|
||||
|
||||
@@ -33,7 +33,7 @@ The following people have contributed code to BusyBox whether they know it or
|
||||
not. If you have written code included in BusyBox, you should probably be
|
||||
listed here so you can obtain your bit of eternal glory. If you should be
|
||||
listed here, or the description of what you have done needs more detail, or is
|
||||
incorect, please send in an update.
|
||||
incorrect, please send in an update.
|
||||
|
||||
|
||||
=for html <br>
|
||||
@@ -158,7 +158,7 @@ John Lombardo <john@deltanet.com>
|
||||
|
||||
Glenn McGrath <bug1@iinet.net.au>
|
||||
|
||||
Common unarchving code and unarchiving applets, ifupdown, ftpgetput,
|
||||
Common unarchiving code and unarchiving applets, ifupdown, ftpgetput,
|
||||
nameif, sed, patch, fold, install, uudecode.
|
||||
Various bugfixes, review and apply numerous patches.
|
||||
|
||||
|
||||
@@ -124,7 +124,7 @@ an example:
|
||||
But when I use BusyBox date I get this instead:
|
||||
|
||||
$ date
|
||||
llegal instruction
|
||||
Illegal instruction
|
||||
|
||||
I am using Debian unstable, kernel version 2.4.19-rmk1 on an Netwinder,
|
||||
and the latest uClibc from CVS.
|
||||
|
||||
@@ -21,7 +21,7 @@ To help with that, busybox applets should have options to override
|
||||
default behavior, whatever that is for a given applet.
|
||||
|
||||
|
||||
Current sutiation is a bit of a mess:
|
||||
Current situation is a bit of a mess:
|
||||
|
||||
acpid - auto-backgrounds unless -d
|
||||
crond - auto-backgrounds unless -f, logs to syslog unless -d or -L.
|
||||
@@ -51,7 +51,7 @@ Total: 13 applets (+1 obsolete),
|
||||
5 never log to syslog (acpid httpd telnetd klogd syslogd, last two
|
||||
- for obviously correct reasons),
|
||||
there are no daemons which always log to syslog,
|
||||
12 auto-background if not run as inetd servies (all except dnsd.
|
||||
12 auto-background if not run as inetd services (all except dnsd.
|
||||
Note that there is no "standard" dnsd AFAIKS). But see below
|
||||
for daemons (tcpsvd etc) which don't auto-background.
|
||||
|
||||
|
||||
@@ -122,6 +122,6 @@ IOW: this will serialize concurrent mdev invocations.
|
||||
|
||||
If you want to activate this feature, execute "echo >/dev/mdev.seq" prior to
|
||||
setting mdev to be the hotplug handler. This writes single '\n' to the file.
|
||||
NB: mdev recognizes /dev/mdev.seq consisting of single '\n' characher
|
||||
NB: mdev recognizes /dev/mdev.seq consisting of single '\n' character
|
||||
as a special case. IOW: this will not make your first hotplug event
|
||||
to stall for two seconds.
|
||||
|
||||
@@ -9,7 +9,7 @@ Mark Whitley - the remix
|
||||
Thomas Lundquist - Trying to keep it updated.
|
||||
|
||||
When doing this you should consider using the latest svn trunk.
|
||||
This is a good thing if you plan to getting it commited into mainline.
|
||||
This is a good thing if you plan to getting it committed into mainline.
|
||||
|
||||
Initial Write
|
||||
-------------
|
||||
@@ -107,7 +107,7 @@ the function declaration. If not, add it somewhere anyway, with or without
|
||||
ifdefs to include or not.
|
||||
|
||||
You can look at libbb/Config.in and try to find out if the function is
|
||||
tuneable and add it there if it is.
|
||||
tunable and add it there if it is.
|
||||
|
||||
|
||||
Placement / Directory
|
||||
|
||||
@@ -7,7 +7,7 @@ And the complete list of all utilities that POSIX covers:
|
||||
http://www.opengroup.org/onlinepubs/9699919799/idx/utilities.html
|
||||
|
||||
This listing is a work in progress, and currently only covers
|
||||
tool options (not operands, enviroment variables, return codes, etc..).
|
||||
tool options (not operands, environment variables, return codes, etc..).
|
||||
For each option it is set if it (a) exists and (b) compliant to POSIX 2008.
|
||||
Some options exist but there is no value in the 'compliant' column: that
|
||||
means no one has yet bothered to make sure that the option does what it is
|
||||
|
||||
@@ -252,7 +252,7 @@ because it looks like whitespace; using lower-case is easy on the eyes.
|
||||
Exceptions:
|
||||
|
||||
- Enums, macros, and constant variables are occasionally written in all
|
||||
upper-case with words optionally seperatedy by underscores (i.e. FIFO_TYPE,
|
||||
upper-case with words optionally separated by underscores (i.e. FIFO_TYPE,
|
||||
ISBLKDEV()).
|
||||
|
||||
- Nobody is going to get mad at you for using 'pvar' as the name of a
|
||||
|
||||
Reference in New Issue
Block a user