Go to file
Denys Vlasenko e6a2f4cc5a libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it
The config item is FEATURE_USE_BSS_TAIL. When it is off (default):

function                                             old     new   delta
read_config                                          210     228     +18
doCommands                                          2279    2294     +15
ipneigh_list_or_flush                                763     772      +9
ipaddr_list_or_flush                                1256    1261      +5
display_process_list                                1301    1306      +5
conspy_main                                         1378    1383      +5
do_lzo_compress                                      352     355      +3
do_lzo_decompress                                    565     567      +2
push                                                  46      44      -2
inetd_main                                          2136    2134      -2
uevent_main                                          421     418      -3
addLines                                              97      92      -5
bb_common_bufsiz1                                   8193    1024   -7169
------------------------------------------------------------------------------
(add/remove: 0/0 grow/shrink: 8/5 up/down: 62/-7181)        Total: -7119 bytes
   text	   data	    bss	    dec	    hex	filename
 829850	   4086	   9080	 843016	  cdd08	busybox_old
 829901	   4086	   1904	 835891	  cc133	busybox_unstripped

FEATURE_USE_BSS_TAIL=y:

read_config                                          210     228     +18
doCommands                                          2279    2294     +15
ipneigh_list_or_flush                                763     772      +9
ipaddr_list_or_flush                                1256    1261      +5
display_process_list                                1301    1306      +5
conspy_main                                         1378    1383      +5
do_lzo_compress                                      352     355      +3
do_lzo_decompress                                    565     567      +2
inetd_main                                          2136    2134      -2
bb_common_bufsiz1                                   8193       -   -8193
------------------------------------------------------------------------------
(add/remove: 0/1 grow/shrink: 8/1 up/down: 62/-8195)        Total: -8133 bytes
   text	   data	    bss	    dec	    hex	filename
 829850	   4086	   9080	 843016	  cdd08	busybox_old
 829911	   4086	    880	 834877	  cbd3d	busybox_unstripped

FIXME: setup_common_bufsiz() calls are missing.

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
2016-04-21 17:39:11 +02:00
applets build system: finer-grained selection of search speedup table. 2016-04-02 15:18:26 +02:00
applets_sh applets_sh/*: Add a few more examples of "shell applets" 2012-02-09 18:23:33 +01:00
arch/i386
archival libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
configs Rename FEATURE_INITRD to LINUXRC and make it separate, not an alias to init 2016-03-31 00:42:57 +02:00
console-tools libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
coreutils libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
debianutils libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
docs dd: support iflag=skip_bytes 2016-02-01 02:17:28 +01:00
e2fsprogs libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
editors libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
examples unrpm: clean up 2016-04-04 01:39:17 -04:00
findutils libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
include libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
init libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
libbb libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
libpwdgrp libbb: make parse_chown_usergroup_or_die() set unspecified uid/gid to -1 2015-10-19 04:37:19 +02:00
loginutils libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
mailutils Use bb_error_msg instead of bb_info_msg in all commented-out debug printouts 2016-03-30 16:04:37 +02:00
miscutils libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
modutils modprobe: skip non-.conf files only in subdirectories 2016-03-29 19:23:55 +02:00
networking libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
printutils printutils/*: convert to new-style "one file" applets 2015-10-19 00:45:46 +02:00
procps libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
qemu_multiarch_testing qemu_multiarch_testing/README: add a list of qemu's needed 2015-10-20 12:58:37 +02:00
runit libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
scripts libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
selinux libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
shell ash: bash-compatible $'...' shouldn't expand in double quotes 2016-04-15 22:16:46 +02:00
sysklogd libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
testsuite sed: make 's///w FILE' actually write to FILE. Closes 8251 2016-01-24 15:52:16 +01:00
util-linux libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
.gitignore Makefile: fix cscope target 2014-12-31 21:29:05 +01:00
.indent.pro
AUTHORS AUTHORS: mention Jie Zhang 2010-01-05 12:57:44 +01:00
Config.in build: add a sanitizer debug option 2016-02-12 22:12:47 -05:00
INSTALL Tweak INSTALL text 2012-04-17 12:28:13 +02:00
LICENSE
Makefile libbb: make bb_common_bufsiz1 1 kbyte, add capability to use bss tail for it 2016-04-21 17:39:11 +02:00
Makefile.custom applets: Add installation of individual binaries 2015-07-01 19:10:03 +02:00
Makefile.flags build: add a sanitizer debug option 2016-02-12 22:12:47 -05:00
Makefile.help build system: "make hosttools" doesn't exist, remove it from "make help" 2014-01-09 11:03:46 +01:00
README typo fix 2015-05-03 18:24:33 +02:00
TODO TODO file: remove mpstat, iostat, powertop - we have them now 2015-11-04 19:39:54 +01:00
TODO_unicode ls: unicode fixes 2010-01-31 05:15:38 +01:00

Please see the LICENSE file for details on copying and usage.
Please refer to the INSTALL file for instructions on how to build.

What is busybox:

  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 bzip2, coreutils, dhcp, diffutils, e2fsprogs,
  file, findutils, gawk, grep, inetutils, less, modutils, net-tools, procps,
  sed, shadow, sysklogd, sysvinit, tar, util-linux, and vim.  The utilities
  in BusyBox often have fewer options than their full-featured cousins;
  however, the options that are included provide the expected functionality
  and behave very much like their larger counterparts.

  BusyBox has been written with size-optimization and limited resources in
  mind, both to produce small binaries and to reduce run-time memory usage.
  Busybox is also extremely modular so you can easily include or exclude
  commands (or features) at compile time.  This makes it easy to customize
  embedded systems; to create a working system, just add /dev, /etc, and a
  Linux kernel.  Busybox (usually together with uClibc) has also been used as
  a component of "thin client" desktop systems, live-CD distributions, rescue
  disks, installers, and so on.

  BusyBox provides a fairly complete POSIX environment for any small system,
  both embedded environments and more full featured systems concerned about
  space.  Busybox is slowly working towards implementing the full Single Unix
  Specification V3 (http://www.opengroup.org/onlinepubs/009695399/), but isn't
  there yet (and for size reasons will probably support at most UTF-8 for
  internationalization).  We are also interested in passing the Linux Test
  Project (http://ltp.sourceforge.net).

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

Using busybox:

  BusyBox is extremely configurable.  This allows you to include only the
  components and options you need, thereby reducing binary size.  Run 'make
  config' or 'make menuconfig' to select the functionality that you wish to
  enable.  (See 'make help' for more commands.)

  The behavior of busybox is determined by the name it's called under: as
  "cp" it behaves like cp, as "sed" it behaves like sed, and so on.  Called
  as "busybox" it takes the second argument as the name of the applet to
  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 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.)

  The build automatically generates a file "busybox.links", which is used by
  'make install' to create symlinks to the BusyBox binary for all compiled in
  commands.  This uses the CONFIG_PREFIX environment variable to specify
  where to install, and installs hardlinks or symlinks depending
  on the configuration preferences.  (You can also manually run
  the install script at "applets/install.sh").

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

Downloading the current source code:

  Source for the latest released version, as well as daily snapshots, can always
  be downloaded from

    http://busybox.net/downloads/

  You can browse the up to the minute source code and change history online.

    http://git.busybox.net/busybox/

  Anonymous GIT access is available.  For instructions, check out:

    http://www.busybox.net/source.html

  For those that are actively contributing and would like to check files in,
  see:

    http://busybox.net/developer.html

  The developers also have a bug and patch tracking system
  (https://bugs.busybox.net) although posting a bug/patch to the mailing list
  is generally a faster way of getting it fixed, and the complete archive of
  what happened is the git changelog.

  Note: if you want to compile busybox in a busybox environment you must
  select CONFIG_DESKTOP.

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

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@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@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
	fri oct  8 14:19:41 mdt 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.

	-diligent

  note the careful description and use of examples showing not only what
  busybox does, but also a counter example showing what an equivalent app
  does (or pointing to the text of a relevant standard).  Bug reports lacking
  such detail may never be fixed...  Thanks for understanding.

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

Portability:

  Busybox is developed and tested on Linux 2.4 and 2.6 kernels, compiled
  with gcc (the unit-at-a-time optimizations in version 3.4 and later are
  worth upgrading to get, but older versions should work), and linked against
  uClibc (0.9.27 or greater) or glibc (2.2 or greater).  In such an
  environment, the full set of busybox features should work, and if
  anything doesn't we want to know about it so we can fix it.

  There are many other environments out there, in which busybox may build
  and run just fine.  We just don't test them.  Since busybox consists of a
  large number of more or less independent applets, portability is a question
  of which features work where.  Some busybox applets (such as cat and rm) are
  highly portable and likely to work just about anywhere, while others (such as
  insmod and losetup) require recent Linux kernels with recent C libraries.

  Earlier versions of Linux and glibc may or may not work, for any given
  configuration.  Linux 2.2 or earlier should mostly work (there's still
  some support code in things like mount.c) but this is no longer regularly
  tested, and inherently won't support certain features (such as long files
  and --bind mounts).  The same is true for glibc 2.0 and 2.1: expect a higher
  testing and debugging burden using such old infrastructure.  (The busybox
  developers are not very interested in supporting these older versions, but
  will probably accept small self-contained patches to fix simple problems.)

  Some environments are not recommended.  Early versions of uClibc were buggy
  and missing many features: upgrade.  Linking against libc5 or dietlibc is
  not supported and not interesting to the busybox developers.  (The first is
  obsolete and has no known size or feature advantages over uClibc, the second
  has known bugs that its developers have actively refused to fix.)  Ancient
  Linux kernels (2.0.x and earlier) are similarly uninteresting.

  In theory it's possible to use Busybox under other operating systems (such as
  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 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.

  In 2005 Shaun Jackman has ported busybox to a combination of newlib
  and libgloss, and some of his patches have been integrated.

Supported hardware:

  BusyBox in general will build on any architecture supported by gcc.  We
  support both 32 and 64 bit platforms, and both big and little endian
  systems.

  Under 2.4 Linux kernels, kernel module loading was implemented in a
  platform-specific manner.  Busybox's insmod utility has been reported to
  work under ARM, CRIS, H8/300, x86, ia64, x86_64, m68k, MIPS, PowerPC, S390,
  SH3/4/5, Sparc, and v850e.  Anything else probably won't work.

  The module loading mechanism for the 2.6 kernel is much more generic, and
  we believe 2.6.x kernel module loading support should work on all
  architectures supported by the kernel.

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

Please feed suggestions, bug reports, insults, and bribes back to the busybox
mailing list:

	busybox@busybox.net

and/or maintainer:

	Denys Vlasenko
	<vda.linux@googlemail.com>