Lines Matching refs:and

1 Please see the LICENSE file for details on copying and usage.
10   sed, shadow, sysklogd, sysvinit, tar, util-linux, and vim.  The utilities
13   and behave very much like their larger counterparts.
15   BusyBox has been written with size-optimization and limited resources in
16   mind, both to produce small binaries and to reduce run-time memory usage.
19   embedded systems; to create a working system, just add /dev, /etc, and a
22   disks, installers, and so on.
25   both embedded environments and more full featured systems concerned about
28   there yet (and for size reasons will probably support at most UTF-8 for
37   components and options you need, thereby reducing binary size.  Run 'make
42   "cp" it behaves like cp, as "sed" it behaves like sed, and so on.  Called
54   where to install, and installs hardlinks or symlinks depending
67   You can browse the up to the minute source code and change history online.
75   For those that are actively contributing and would like to check files in,
80   The developers also have a bug and patch tracking system
82   is generally a faster way of getting it fixed, and the complete archive of
102   transcript of a shell session that demonstrates the bad behavior and enables
125     and the latest uclibc from cvs.
129   note the careful description and use of examples showing not only what
138   Busybox is developed and tested on Linux 2.4 and 2.6 kernels, compiled
139   with gcc (the unit-at-a-time optimizations in version 3.4 and later are
140   worth upgrading to get, but older versions should work), and linked against
142   environment, the full set of busybox features should work, and if
146   and run just fine.  We just don't test them.  Since busybox consists of a
148   of which features work where.  Some busybox applets (such as cat and rm) are
149   highly portable and likely to work just about anywhere, while others (such as
150   insmod and losetup) require recent Linux kernels with recent C libraries.
152   Earlier versions of Linux and glibc may or may not work, for any given
155   tested, and inherently won't support certain features (such as long files
156   and --bind mounts).  The same is true for glibc 2.0 and 2.1: expect a higher
157   testing and debugging burden using such old infrastructure.  (The busybox
162   and missing many features: upgrade.  Linking against libc5 or dietlibc is
163   not supported and not interesting to the busybox developers.  (The first is
164   obsolete and has no known size or feature advantages over uClibc, the second
166   Linux kernels (2.0.x and earlier) are similarly uninteresting.
170   a different kernel and a different C library at the same time.  While it
174   and work your way up.
177   and libgloss, and some of his patches have been integrated.
182   support both 32 and 64 bit platforms, and both big and little endian
188   SH3/4/5, Sparc, and v850e.  Anything else probably won't work.
190   The module loading mechanism for the 2.6 kernel is much more generic, and
196 Please feed suggestions, bug reports, insults, and bribes back to the busybox
201 and/or maintainer: