menu "Linux System Utilities"
-
config CONFIG_DMESG
bool "dmesg"
default n
help
fbset is used to show or change the settings of a Linux frame buffer
device. The frame buffer device provides a simple and unique
- interface to access a graphic display. Enable this option if you wish
- to enable the 'fbset' utility.
-
+ interface to access a graphics display. Enable this option
+ if you wish to enable the 'fbset' utility.
config CONFIG_FEATURE_FBSET_FANCY
bool " Turn on extra fbset options"
depends on CONFIG_FBSET
help
This option enables extended fbset options, allowing one to set the
- framebuffer size, color depth, etc. interface to access a graphic
+ framebuffer size, color depth, etc. interface to access a graphics
display. Enable this option if you wish to enable extended fbset
options.
bool "fdflush"
default n
help
- Fdflush is only needed when changing media on slightly-broken
+ fdflush is only needed when changing media on slightly-broken
removable media drives. It is used to make Linux believe that a
hardware disk-change switch has been actuated, which causes Linux to
forget anything it has cached from the previous media. If you have
such a slightly-broken drive, you will need to run fdflush every time
you change a disk. Most people have working hardware and can safely
- say leave this disabled.
+ leave this disabled.
config CONFIG_FDFORMAT
bool "fdformat"
default n
help
- Fdformat is used to low-level format a floppy disk.
+ fdformat is used to low-level format a floppy disk.
config CONFIG_FDISK
bool "fdisk"
help
The fdisk utility is used to divide hard disks into one or more
logical disks, which are generally called partitions. This utility
- can be used to list and edit the set of partitions or BSD style
+ can be used to list and edit the set of partitions or BSD style
'disk slices' that are defined on a hard drive.
+config FDISK_SUPPORT_LARGE_DISKS
+ bool " support over 4GB disks"
+ default y
+ depends on CONFIG_FDISK
+ help
+ Enable this option to support large disks > 4GB.
+
config CONFIG_FEATURE_FDISK_WRITABLE
- bool " Write support"
+ bool " Write support"
default y
depends on CONFIG_FDISK
help
config CONFIG_FEATURE_AIX_LABEL
bool " Support AIX disklabels"
default n
- depends on CONFIG_FDISK && CONFIG_FEATURE_FDISK_WRITABLE
+ depends on CONFIG_FDISK && CONFIG_FEATURE_FDISK_WRITABLE
help
Enabling this option allows you to create or change AIX disklabels.
Most people can safely leave this option disabled.
config CONFIG_FEATURE_SUN_LABEL
bool " Support SUN disklabels"
default n
- depends on CONFIG_FDISK && CONFIG_FEATURE_FDISK_WRITABLE
+ depends on CONFIG_FDISK && CONFIG_FEATURE_FDISK_WRITABLE
help
Enabling this option allows you to create or change SUN disklabels.
Most people can safely leave this option disabled.
help
The minix filesystem is a nice, small, compact, read-write filesystem
with little overhead. It is not a journaling filesystem however and
- can encounted corruption if it is not properly unmounted or if the
+ can experience corruption if it is not properly unmounted or if the
power goes off in the middle of a write. This utility allows you to
check for and attempt to repair any corruption that occurs to a minix
filesystem.
default n
help
The hwclock utility is used to read and set the hardware clock
- on a system. This is primarily used to set the correct time in
- the hardware close, so the hardware will keep the correct time
- when Linux is _not_ running.
+ on a system. This is primarily used to set the current time on
+ shutdown in the hardware clock, so the hardware will keep the
+ correct time when Linux is _not_ running.
config CONFIG_FEATURE_HWCLOCK_LONGOPTIONS
bool " Support long options (--hctosys,...)"
depends on CONFIG_HWCLOCK
help
By default, the hwclock utility only uses short options. If you
- are overly fond of the long options, such as --hctosys, --utc, etc)
+ are overly fond of its long options, such as --hctosys, --utc, etc)
then enable this option.
+config CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS
+ bool " Use FHS /var/lib/hwclock/adjtime"
+ default y
+ depends on CONFIG_HWCLOCK
+ help
+ Starting with FHS 2.3, the adjtime state file is supposed to exist
+ at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish
+ to use the FHS behavior, answer Y here, otherwise answer N for the
+ classic /etc/adjtime path.
+
+ http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO
+
+config CONFIG_IPCRM
+ bool "ipcrm"
+ default n
+ select CONFIG_FEATURE_SUID
+ help
+ The ipcrm utility allows the removal of System V interprocess
+ communication (IPC) objects and the associated data structures
+ from the system.
+
+config CONFIG_IPCS
+ bool "ipcs"
+ default n
+ select CONFIG_FEATURE_SUID
+ help
+ The ipcs utility is used to provide information on the currently
+ allocated System V interprocess (IPC) objects in the system.
+
config CONFIG_LOSETUP
bool "losetup"
default n
file or block device, and to query the status of a loop device. This
version does not currently support enabling data encryption.
+config CONFIG_MDEV
+ bool "mdev"
+ default n
+ help
+ mdev is a mini-udev implementation: call it with -s to populate
+ /dev from /sys, then "echo /sbin/mdev > /proc/sys/kernel/hotplug" to
+ have it handle hotplug events afterwards. Device names are taken
+ from sysfs.
+
+config CONFIG_FEATURE_MDEV_CONF
+ bool " Support /etc/mdev.conf"
+ default n
+ depends on CONFIG_MDEV
+ help
+ The mdev config file contains lines that look like:
+
+ hd[a-z][0-9]* 0:3 660
+
+ That's device name (with regex match), uid:gid, and permissions.
+
+ Optionally, that can be followed (on the same line) by an asterisk
+ and a command line to run after creating the corresponding device(s),
+ ala:
+
+ hdc root:cdrom 660 *ln -s hdc cdrom
+
+ Config file parsing stops on the first matching line. If no config
+ entry is matched, devices are created with default 0:0 660. (Make
+ the last line match .* to override this.)
+
config CONFIG_MKSWAP
bool "mkswap"
default n
partition as if it were additional RAM, which can greatly increase
the capability of low-memory machines. This additional memory is
much slower than real RAM, but can be very helpful at preventing your
- applications being killed by the Linux out of memory (OOM) killer. Once
- you have created swap space using 'mkswap' you need to enable the swap
- space using the 'swapon' utility.
+ applications being killed by the Linux out of memory (OOM) killer.
+ Once you have created swap space using 'mkswap' you need to enable
+ the swap space using the 'swapon' utility.
config CONFIG_MORE
bool "more"
default n
help
- More is a simple utility which allows you to read text one screen
+ more is a simple utility which allows you to read text one screen
sized page at a time. If you want to read text that is larger than
the screen, and you are using anything faster than a 300 baud modem,
you will probably find this utility very helpful. If you don't have
help
This option allows utilities such as 'more' and 'top' to determine
the size of the screen. If you leave this disabled, your utilities
- that display things on the screen with be especially primitive and
+ that display things on the screen will be especially primitive and
will be unable to determine the current screen size, and will be
unable to move the cursor.
-comment "Common options for ls and more"
- depends on CONFIG_LS || CONFIG_MORE
+config CONFIG_MOUNT
+ bool "mount"
+ default n
+ help
+ All files and filesystems in Unix are arranged into one big directory
+ tree. The 'mount' utility is used to graft a filesystem onto a
+ particular part of the tree. A filesystem can either live on a block
+ device, or it can be accessible over the network, as is the case with
+ NFS filesystems. Most people using BusyBox will also want to enable
+ the 'mount' utility.
-config CONFIG_FEATURE_AUTOWIDTH
- bool " Calculate terminal & column widths"
- default y
- depends on CONFIG_LS || CONFIG_MORE
+config CONFIG_FEATURE_MOUNT_NFS
+ bool " Support mounting NFS file systems"
+ default n
+ depends on CONFIG_MOUNT
help
- This option allows utilities such as 'ls' and 'more' to determine the
- width of the screen, which can allow them to display additional text
- or avoid wrapping text onto the next line. If you leave this
- disabled, your utilities will be especially primitive and will be
- unable to determine the current screen width.
+ Enable mounting of NFS file systems.
config CONFIG_PIVOT_ROOT
bool "pivot_root"
of wild and crazy things with your Linux system and is far more
powerful than 'chroot'.
+ Note: This is for initrd in linux 2.4. Under initramfs (introduced
+ in linux 2.6) use switch_root instead.
+
config CONFIG_RDATE
bool "rdate"
default n
help
- The rdate utility allows you to syncronize the date and time of your
+ The rdate utility allows you to synchronize the date and time of your
system clock with the date and time of a remote networked system using
the RFC868 protocol, which is built into the inetd daemon on most
systems.
+config CONFIG_READPROFILE
+ bool "readprofile"
+ default n
+ help
+ This allows you to parse /proc/profile for basic profiling.
+
config CONFIG_SWAPONOFF
bool "swaponoff"
default n
space. If you are not using any swap space, you can leave this
option disabled.
-config CONFIG_MOUNT
- bool "mount"
+config CONFIG_SWITCH_ROOT
+ bool "switch_root"
default n
help
- All files and filesystems in Unix are arranged into one big directory
- tree. The 'mount' utility is used to graft a filesystem onto a
- particular part of the tree. A filesystem can either live on a block
- device, or it can be accessible over the network, as is the case with
- NFS filesystems. Most people using BusyBox will also want to enable
- the 'mount' utility.
+ The switch_root utility is used from initramfs to select a new
+ root device. Under initramfs, you have to use this instead of
+ pivot_root. (Stop reading here if you don't care why.)
-config CONFIG_NFSMOUNT
- bool " Support mounting nfs file systems"
- default n
- depends on CONFIG_MOUNT
- help
- Enable mounting of NFS file systems.
+ Booting with initramfs extracts a gzipped cpio archive into rootfs
+ (which is a variant of ramfs/tmpfs). Because rootfs can't be moved
+ or unmounted*, pivot_root will not work from initramfs. Instead,
+ switch_root deletes everything out of rootfs (including itself),
+ does a mount --move that overmounts rootfs with the new root, and
+ then execs the specified init program.
+
+ * Because the Linux kernel uses rootfs internally as the starting
+ and ending point for searching through the kernel's doubly linked
+ list of active mount points. That's why.
config CONFIG_UMOUNT
bool "umount"
the tool to use. If you enabled the 'mount' utility, you almost certainly
also want to enable 'umount'.
-config CONFIG_FEATURE_MOUNT_FORCE
- bool " Support forced filesystem unmounting"
- default n
- depends on CONFIG_UMOUNT
- help
- This allows you to _force_ a filesystem to be umounted. This is generally
- only useful when you want to get rid of an unreachable NFS system.
-
comment "Common options for mount/umount"
depends on CONFIG_MOUNT || CONFIG_UMOUNT
config CONFIG_FEATURE_MOUNT_LOOP
- bool " Support for loop devices"
+ bool " Support loopback mounts"
default n
depends on CONFIG_MOUNT || CONFIG_UMOUNT
help
- Enabling this feature allows mount to use the '-o' loop options,
- which lets you loop mount files. Mount will automagically setup and
- free the necessary loop devices so you do not need to mess with the
- 'losetup' utility unless you really want to. This is really only useful
- if you plan to loop mount files.
+ Enabling this feature allows automatic mounting of files (containing
+ filesystem images) via the linux kernel's loopback devices. The mount
+ command will detect you are trying to mount a file instead of a block
+ device, and transparently associate the file with a loopback device.
+ The umount command will also free that loopback device.
+
+ You can still use the 'losetup' utility (to manually associate files
+ with loop devices) if you need to do something advanced, such as
+ specify an offset or cryptographic options to the loopback device.
+ (If you don't want umount to free the loop device, use "umount -D".)
config CONFIG_FEATURE_MTAB_SUPPORT
- bool " Support for a real /etc/mtab (instead of /proc/mounts)"
+ bool " Support for the old /etc/mtab file"
default n
depends on CONFIG_MOUNT || CONFIG_UMOUNT
help
- If your root filesystem is writable and you wish to have the 'mount'
- utility create an mtab file listing the filesystems which have been
- mounted then you should enable this option. Most people that use
- BusyBox have a read-only root filesystem, so they will leave this
- option disabled and BusyBox will use the /proc/mounts file.
-
-config CONFIG_FEATURE_MTAB_FILENAME
- string " mtab file location"
- default "/etc/mtab"
- depends on CONFIG_FEATURE_MTAB_SUPPORT
- help
- Some people have a read only root filesystem, but they also wish to
- have the 'mount' utility create an mtab file listing the filesystems
- which have been mounted. This option allows you to specify an alternative
- location for the mtab file, such as /var/mtab, or /tmp/mtab. The default
- value is /etc/mtab, which is where this file is located on most desktop
- Linux systems.
+ Historically, Unix systems kept track of the currently mounted
+ partitions in the file "/etc/mtab". These days, the kernel exports
+ the list of currently mounted partitions in "/proc/mounts", rendering
+ the old mtab file obsolete. (In modern systems, /etc/mtab should be
+ a symlink to /proc/mounts.)
+
+ The only reason to have mount maintain an /etc/mtab file itself is if
+ your stripped-down embedded system does not have a /proc directory.
+ If you must use this, keep in mind it's inherently brittle (for
+ example a mount under chroot won't update it), can't handle modern
+ features like separate per-process filesystem namespaces, requires
+ that your /etc directory be writeable, tends to get easily confused
+ by --bind or --move mounts, and so on. (In brief: avoid.)
endmenu