mirror of
https://git.busybox.net/busybox.git
synced 2024-11-23 13:43:28 +08:00
typo fixes
Signed-off-by: Dan Fandrich <dan@coneharvesters.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
parent
4dc35fb5b6
commit
b5de0c12d6
2
INSTALL
2
INSTALL
@ -97,7 +97,7 @@ first argument to determine which applet to behave as, for example
|
||||
"./busybox cat LICENSE". (Running the busybox applet with no arguments gives
|
||||
a list of all enabled applets.) The standalone shell can also call busybox
|
||||
applets without links to busybox under other names in the filesystem. You can
|
||||
also configure a standaone install capability into the busybox base applet,
|
||||
also configure a standalone install capability into the busybox base applet,
|
||||
and then install such links at runtime with one of "busybox --install" (for
|
||||
hardlinks) or "busybox --install -s" (for symlinks).
|
||||
|
||||
|
4
README
4
README
@ -44,7 +44,7 @@ Using busybox:
|
||||
run (I.E. "./busybox ls -l /proc").
|
||||
|
||||
The "standalone shell" mode is an easy way to try out busybox; this is a
|
||||
command shell that calls the builtin applets without needing them to be
|
||||
command shell that calls the built-in applets without needing them to be
|
||||
installed in the path. (Note that this requires /proc to be mounted, if
|
||||
testing from a boot floppy or in a chroot environment.)
|
||||
|
||||
@ -169,7 +169,7 @@ Portability:
|
||||
MacOS X, Solaris, Cygwin, or the BSD Fork Du Jour). This generally involves
|
||||
a different kernel and a different C library at the same time. While it
|
||||
should be possible to port the majority of the code to work in one of
|
||||
these environments, don't be suprised if it doesn't work out of the box. If
|
||||
these environments, don't be surprised if it doesn't work out of the box. If
|
||||
you're into that sort of thing, start small (selecting just a few applets)
|
||||
and work your way up.
|
||||
|
||||
|
@ -29,7 +29,7 @@ But we also need to handle the following problematic moments:
|
||||
Editors (vi, ed)
|
||||
|
||||
This case is a bit similar to "shell input", but unlike shell,
|
||||
editors may encounder many more unexpected unicode sequences
|
||||
editors may encounter many more unexpected unicode sequences
|
||||
(try to load a random binary file...), and they need to preserve
|
||||
them, unlike shell which can afford to drop bogus input.
|
||||
|
||||
|
@ -38,7 +38,7 @@
|
||||
//usage:#define nanddump_trivial_usage
|
||||
//usage: "[-o] [-b] [-s ADDR] [-f FILE] MTD_DEVICE"
|
||||
//usage:#define nanddump_full_usage "\n\n"
|
||||
//usage: "Dump the sepcified MTD device\n"
|
||||
//usage: "Dump the specified MTD device\n"
|
||||
//usage: "\n -o Omit oob data"
|
||||
//usage: "\n -b Omit bad block from the dump"
|
||||
//usage: "\n -s ADDR Start address"
|
||||
|
@ -30,7 +30,7 @@
|
||||
//usage: "\n -s Send successful replies only. Use this if you want"
|
||||
//usage: "\n to use /etc/resolv.conf with two nameserver lines:"
|
||||
//usage: "\n nameserver DNSD_SERVER"
|
||||
//usage: "\n nameserver NORNAL_DNS_SERVER"
|
||||
//usage: "\n nameserver NORMAL_DNS_SERVER"
|
||||
|
||||
#include "libbb.h"
|
||||
#include <syslog.h>
|
||||
|
@ -12,7 +12,7 @@
|
||||
//usage:#define lspci_full_usage "\n\n"
|
||||
//usage: "List all PCI devices"
|
||||
//usage: "\n"
|
||||
//usage: "\n -m Parseable output"
|
||||
//usage: "\n -m Parsable output"
|
||||
//usage: "\n -k Show driver"
|
||||
|
||||
#include "libbb.h"
|
||||
|
Loading…
Reference in New Issue
Block a user