mirror of
git://git.openwrt.org/openwrt/openwrt.git
synced 2025-10-30 13:34:27 -04:00
84da2a677a
Refresh patches, delete patches that have been applied upstream. Signed-off-by: Magnus Kroken <mkroken@gmail.com> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [fix defaults]
831 lines
30 KiB
Plaintext
831 lines
30 KiB
Plaintext
# DO NOT EDIT. This file is generated from Config.src
|
|
#
|
|
# For a description of the syntax of this configuration file,
|
|
# see scripts/kbuild/config-language.txt.
|
|
#
|
|
|
|
menu "Linux System Utilities"
|
|
|
|
config BUSYBOX_CONFIG_ACPID
|
|
bool "acpid"
|
|
default BUSYBOX_DEFAULT_ACPID
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
acpid listens to ACPI events coming either in textual form from
|
|
/proc/acpi/event (though it is marked deprecated it is still widely
|
|
used and _is_ a standard) or in binary form from specified evdevs
|
|
(just use /dev/input/event*).
|
|
|
|
It parses the event to retrieve ACTION and a possible PARAMETER.
|
|
It then spawns /etc/acpi/<ACTION>[/<PARAMETER>] either via run-parts
|
|
(if the resulting path is a directory) or directly as an executable.
|
|
|
|
N.B. acpid relies on run-parts so have the latter installed.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_ACPID_COMPAT
|
|
bool "Accept and ignore redundant options"
|
|
default BUSYBOX_DEFAULT_FEATURE_ACPID_COMPAT
|
|
depends on BUSYBOX_CONFIG_ACPID
|
|
help
|
|
Accept and ignore compatibility options -g -m -s -S -v.
|
|
config BUSYBOX_CONFIG_BLKDISCARD
|
|
bool "blkdiscard"
|
|
default BUSYBOX_DEFAULT_BLKDISCARD
|
|
help
|
|
blkdiscard discards sectors on a given device.
|
|
config BUSYBOX_CONFIG_BLKID
|
|
bool "blkid"
|
|
default BUSYBOX_DEFAULT_BLKID
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
select BUSYBOX_CONFIG_VOLUMEID
|
|
help
|
|
Lists labels and UUIDs of all filesystems.
|
|
WARNING:
|
|
With all submodules selected, it will add ~8k to busybox.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_BLKID_TYPE
|
|
bool "Print filesystem type"
|
|
default BUSYBOX_DEFAULT_FEATURE_BLKID_TYPE
|
|
depends on BUSYBOX_CONFIG_BLKID
|
|
help
|
|
Show TYPE="filesystem type"
|
|
config BUSYBOX_CONFIG_BLOCKDEV
|
|
bool "blockdev"
|
|
default BUSYBOX_DEFAULT_BLOCKDEV
|
|
help
|
|
Performs some ioctls with block devices.
|
|
config BUSYBOX_CONFIG_DMESG
|
|
bool "dmesg"
|
|
default BUSYBOX_DEFAULT_DMESG
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
dmesg is used to examine or control the kernel ring buffer. When the
|
|
Linux kernel prints messages to the system log, they are stored in
|
|
the kernel ring buffer. You can use dmesg to print the kernel's ring
|
|
buffer, clear the kernel ring buffer, change the size of the kernel
|
|
ring buffer, and change the priority level at which kernel messages
|
|
are also logged to the system console. Enable this option if you
|
|
wish to enable the 'dmesg' utility.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_DMESG_PRETTY
|
|
bool "Pretty dmesg output"
|
|
default BUSYBOX_DEFAULT_FEATURE_DMESG_PRETTY
|
|
depends on BUSYBOX_CONFIG_DMESG
|
|
help
|
|
If you wish to scrub the syslog level from the output, say 'Y' here.
|
|
The syslog level is a string prefixed to every line with the form
|
|
"<#>".
|
|
|
|
With this option you will see:
|
|
# dmesg
|
|
Linux version 2.6.17.4 .....
|
|
BIOS-provided physical RAM map:
|
|
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
|
|
|
|
Without this option you will see:
|
|
# dmesg
|
|
<5>Linux version 2.6.17.4 .....
|
|
<6>BIOS-provided physical RAM map:
|
|
<6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
|
|
config BUSYBOX_CONFIG_FATATTR
|
|
bool "fatattr"
|
|
default BUSYBOX_DEFAULT_FATATTR
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
fatattr lists or changes the file attributes on a fat file system.
|
|
config BUSYBOX_CONFIG_FBSET
|
|
bool "fbset"
|
|
default BUSYBOX_DEFAULT_FBSET
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
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 graphics display. Enable this option
|
|
if you wish to enable the 'fbset' utility.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_FBSET_FANCY
|
|
bool "Turn on extra fbset options"
|
|
default BUSYBOX_DEFAULT_FEATURE_FBSET_FANCY
|
|
depends on BUSYBOX_CONFIG_FBSET
|
|
help
|
|
This option enables extended fbset options, allowing one to set the
|
|
framebuffer size, color depth, etc. interface to access a graphics
|
|
display. Enable this option if you wish to enable extended fbset
|
|
options.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_FBSET_READMODE
|
|
bool "Turn on fbset readmode support"
|
|
default BUSYBOX_DEFAULT_FEATURE_FBSET_READMODE
|
|
depends on BUSYBOX_CONFIG_FBSET
|
|
help
|
|
This option allows fbset to read the video mode database stored by
|
|
default BUSYBOX_DEFAULT_FEATURE_FBSET_READMODE /etc/fb.modes, which can be used to set frame buffer
|
|
device to pre-defined video modes.
|
|
config BUSYBOX_CONFIG_FDFORMAT
|
|
bool "fdformat"
|
|
default BUSYBOX_DEFAULT_FDFORMAT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
fdformat is used to low-level format a floppy disk.
|
|
config BUSYBOX_CONFIG_FDISK
|
|
bool "fdisk"
|
|
default BUSYBOX_DEFAULT_FDISK
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
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
|
|
'disk slices' that are defined on a hard drive.
|
|
|
|
config BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
|
|
bool "Support over 4GB disks"
|
|
default BUSYBOX_DEFAULT_FDISK_SUPPORT_LARGE_DISKS
|
|
depends on BUSYBOX_CONFIG_FDISK
|
|
depends on !BUSYBOX_CONFIG_LFS # with LFS no special code is needed
|
|
help
|
|
Enable this option to support large disks > 4GB.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
bool "Write support"
|
|
default BUSYBOX_DEFAULT_FEATURE_FDISK_WRITABLE
|
|
depends on BUSYBOX_CONFIG_FDISK
|
|
help
|
|
Enabling this option allows you to create or change a partition table
|
|
and write those changes out to disk. If you leave this option
|
|
disabled, you will only be able to view the partition table.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_AIX_LABEL
|
|
bool "Support AIX disklabels"
|
|
default BUSYBOX_DEFAULT_FEATURE_AIX_LABEL
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_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 BUSYBOX_CONFIG_FEATURE_SGI_LABEL
|
|
bool "Support SGI disklabels"
|
|
default BUSYBOX_DEFAULT_FEATURE_SGI_LABEL
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
help
|
|
Enabling this option allows you to create or change SGI disklabels.
|
|
Most people can safely leave this option disabled.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_SUN_LABEL
|
|
bool "Support SUN disklabels"
|
|
default BUSYBOX_DEFAULT_FEATURE_SUN_LABEL
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
help
|
|
Enabling this option allows you to create or change SUN disklabels.
|
|
Most people can safely leave this option disabled.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_OSF_LABEL
|
|
bool "Support BSD disklabels"
|
|
default BUSYBOX_DEFAULT_FEATURE_OSF_LABEL
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
help
|
|
Enabling this option allows you to create or change BSD disklabels
|
|
and define and edit BSD disk slices.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_GPT_LABEL
|
|
bool "Support GPT disklabels"
|
|
default BUSYBOX_DEFAULT_FEATURE_GPT_LABEL
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
help
|
|
Enabling this option allows you to view GUID Partition Table
|
|
disklabels.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_FDISK_ADVANCED
|
|
bool "Support expert mode"
|
|
default BUSYBOX_DEFAULT_FEATURE_FDISK_ADVANCED
|
|
depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
|
|
help
|
|
Enabling this option allows you to do terribly unsafe things like
|
|
define arbitrary drive geometry, move the beginning of data in a
|
|
partition, and similarly evil things. Unless you have a very good
|
|
reason you would be wise to leave this disabled.
|
|
config BUSYBOX_CONFIG_FINDFS
|
|
bool "findfs"
|
|
default BUSYBOX_DEFAULT_FINDFS
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
select BUSYBOX_CONFIG_VOLUMEID
|
|
help
|
|
Prints the name of a filesystem with given label or UUID.
|
|
WARNING:
|
|
With all submodules selected, it will add ~8k to busybox.
|
|
config BUSYBOX_CONFIG_FLOCK
|
|
bool "flock"
|
|
default BUSYBOX_DEFAULT_FLOCK
|
|
help
|
|
Manage locks from shell scripts
|
|
config BUSYBOX_CONFIG_FDFLUSH
|
|
bool "fdflush"
|
|
default BUSYBOX_DEFAULT_FDFLUSH
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
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
|
|
leave this disabled.
|
|
|
|
config BUSYBOX_CONFIG_FREERAMDISK
|
|
bool "freeramdisk"
|
|
default BUSYBOX_DEFAULT_FREERAMDISK
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Linux allows you to create ramdisks. This utility allows you to
|
|
delete them and completely free all memory that was used for the
|
|
ramdisk. For example, if you boot Linux into a ramdisk and later
|
|
pivot_root, you may want to free the memory that is allocated to the
|
|
ramdisk. If you have no use for freeing memory from a ramdisk, leave
|
|
this disabled.
|
|
config BUSYBOX_CONFIG_FSCK_MINIX
|
|
bool "fsck_minix"
|
|
default BUSYBOX_DEFAULT_FSCK_MINIX
|
|
help
|
|
The minix filesystem is a nice, small, compact, read-write filesystem
|
|
with little overhead. It is not a journaling filesystem however and
|
|
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.
|
|
config BUSYBOX_CONFIG_FSTRIM
|
|
bool "fstrim"
|
|
default BUSYBOX_DEFAULT_FSTRIM
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Discard unused blocks on a mounted filesystem.
|
|
config BUSYBOX_CONFIG_GETOPT
|
|
bool "getopt"
|
|
default BUSYBOX_DEFAULT_GETOPT
|
|
help
|
|
The getopt utility is used to break up (parse) options in command
|
|
lines to make it easy to write complex shell scripts that also check
|
|
for legal (and illegal) options. If you want to write horribly
|
|
complex shell scripts, or use some horribly complex shell script
|
|
written by others, this utility may be for you. Most people will
|
|
wisely leave this disabled.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_GETOPT_LONG
|
|
bool "Support option -l"
|
|
default BUSYBOX_DEFAULT_FEATURE_GETOPT_LONG if BUSYBOX_CONFIG_LONG_OPTS
|
|
depends on BUSYBOX_CONFIG_GETOPT
|
|
help
|
|
Enable support for long options (option -l).
|
|
config BUSYBOX_CONFIG_HEXDUMP
|
|
bool "hexdump"
|
|
default BUSYBOX_DEFAULT_HEXDUMP
|
|
help
|
|
The hexdump utility is used to display binary data in a readable
|
|
way that is comparable to the output from most hex editors.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_HEXDUMP_REVERSE
|
|
bool "Support -R, reverse of 'hexdump -Cv'"
|
|
default BUSYBOX_DEFAULT_FEATURE_HEXDUMP_REVERSE
|
|
depends on BUSYBOX_CONFIG_HEXDUMP
|
|
help
|
|
The hexdump utility is used to display binary data in an ascii
|
|
readable way. This option creates binary data from an ascii input.
|
|
NB: this option is non-standard. It's unwise to use it in scripts
|
|
aimed to be portable.
|
|
|
|
config BUSYBOX_CONFIG_HD
|
|
bool "hd"
|
|
default BUSYBOX_DEFAULT_HD
|
|
help
|
|
hd is an alias to hexdump -C.
|
|
config BUSYBOX_CONFIG_HWCLOCK
|
|
bool "hwclock"
|
|
default BUSYBOX_DEFAULT_HWCLOCK
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
The hwclock utility is used to read and set the hardware clock
|
|
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 BUSYBOX_CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS
|
|
bool "Support long options (--hctosys,...)"
|
|
default BUSYBOX_DEFAULT_FEATURE_HWCLOCK_LONG_OPTIONS
|
|
depends on BUSYBOX_CONFIG_HWCLOCK && BUSYBOX_CONFIG_LONG_OPTS
|
|
help
|
|
By default, the hwclock utility only uses short options. If you
|
|
are overly fond of its long options, such as --hctosys, --utc, etc)
|
|
then enable this option.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS
|
|
bool "Use FHS /var/lib/hwclock/adjtime"
|
|
default BUSYBOX_DEFAULT_FEATURE_HWCLOCK_ADJTIME_FHS # util-linux-ng in Fedora 13 still uses /etc/adjtime
|
|
depends on BUSYBOX_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.
|
|
|
|
pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO
|
|
config BUSYBOX_CONFIG_IPCRM
|
|
bool "ipcrm"
|
|
default BUSYBOX_DEFAULT_IPCRM
|
|
help
|
|
The ipcrm utility allows the removal of System V interprocess
|
|
communication (IPC) objects and the associated data structures
|
|
from the system.
|
|
config BUSYBOX_CONFIG_IPCS
|
|
bool "ipcs"
|
|
default BUSYBOX_DEFAULT_IPCS
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
The ipcs utility is used to provide information on the currently
|
|
allocated System V interprocess (IPC) objects in the system.
|
|
config BUSYBOX_CONFIG_LOSETUP
|
|
bool "losetup"
|
|
default BUSYBOX_DEFAULT_LOSETUP
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
losetup is used to associate or detach a loop device with a regular
|
|
file or block device, and to query the status of a loop device. This
|
|
version does not currently support enabling data encryption.
|
|
config BUSYBOX_CONFIG_LSPCI
|
|
bool "lspci"
|
|
default BUSYBOX_DEFAULT_LSPCI
|
|
#select PLATFORM_LINUX
|
|
help
|
|
lspci is a utility for displaying information about PCI buses in the
|
|
system and devices connected to them.
|
|
|
|
This version uses sysfs (/sys/bus/pci/devices) only.
|
|
config BUSYBOX_CONFIG_LSUSB
|
|
bool "lsusb"
|
|
default BUSYBOX_DEFAULT_LSUSB
|
|
#select PLATFORM_LINUX
|
|
help
|
|
lsusb is a utility for displaying information about USB buses in the
|
|
system and devices connected to them.
|
|
|
|
This version uses sysfs (/sys/bus/usb/devices) only.
|
|
config BUSYBOX_CONFIG_MDEV
|
|
bool "mdev"
|
|
default BUSYBOX_DEFAULT_MDEV
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
mdev is a mini-udev implementation for dynamically creating device
|
|
nodes in the /dev directory.
|
|
|
|
For more information, please see docs/mdev.txt
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MDEV_CONF
|
|
bool "Support /etc/mdev.conf"
|
|
default BUSYBOX_DEFAULT_FEATURE_MDEV_CONF
|
|
depends on BUSYBOX_CONFIG_MDEV
|
|
help
|
|
Add support for the mdev config file to control ownership and
|
|
permissions of the device nodes.
|
|
|
|
For more information, please see docs/mdev.txt
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
|
|
bool "Support subdirs/symlinks"
|
|
default BUSYBOX_DEFAULT_FEATURE_MDEV_RENAME
|
|
depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
|
|
help
|
|
Add support for renaming devices and creating symlinks.
|
|
|
|
For more information, please see docs/mdev.txt
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME_REGEXP
|
|
bool "Support regular expressions substitutions when renaming device"
|
|
default BUSYBOX_DEFAULT_FEATURE_MDEV_RENAME_REGEXP
|
|
depends on BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
|
|
help
|
|
Add support for regular expressions substitutions when renaming
|
|
device.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MDEV_EXEC
|
|
bool "Support command execution at device addition/removal"
|
|
default BUSYBOX_DEFAULT_FEATURE_MDEV_EXEC
|
|
depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
|
|
help
|
|
This adds support for an optional field to /etc/mdev.conf for
|
|
executing commands when devices are created/removed.
|
|
|
|
For more information, please see docs/mdev.txt
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE
|
|
bool "Support loading of firmwares"
|
|
default BUSYBOX_DEFAULT_FEATURE_MDEV_LOAD_FIRMWARE
|
|
depends on BUSYBOX_CONFIG_MDEV
|
|
help
|
|
Some devices need to load firmware before they can be usable.
|
|
|
|
These devices will request userspace look up the files in
|
|
/lib/firmware/ and if it exists, send it to the kernel for
|
|
loading into the hardware.
|
|
config BUSYBOX_CONFIG_MKE2FS
|
|
bool "mke2fs"
|
|
default BUSYBOX_DEFAULT_MKE2FS
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Utility to create EXT2 filesystems.
|
|
|
|
config BUSYBOX_CONFIG_MKFS_EXT2
|
|
bool "mkfs.ext2"
|
|
default BUSYBOX_DEFAULT_MKFS_EXT2
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Alias to "mke2fs".
|
|
config BUSYBOX_CONFIG_MKFS_MINIX
|
|
bool "mkfs_minix"
|
|
default BUSYBOX_DEFAULT_MKFS_MINIX
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
The minix filesystem is a nice, small, compact, read-write filesystem
|
|
with little overhead. If you wish to be able to create minix
|
|
filesystems this utility will do the job for you.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MINIX2
|
|
bool "Support Minix fs v2 (fsck_minix/mkfs_minix)"
|
|
default BUSYBOX_DEFAULT_FEATURE_MINIX2
|
|
depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
|
|
help
|
|
If you wish to be able to create version 2 minix filesystems, enable
|
|
this. If you enabled 'mkfs_minix' then you almost certainly want to
|
|
be using the version 2 filesystem support.
|
|
config BUSYBOX_CONFIG_MKFS_REISER
|
|
bool "mkfs_reiser"
|
|
default BUSYBOX_DEFAULT_MKFS_REISER
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Utility to create ReiserFS filesystems.
|
|
Note: this applet needs a lot of testing and polishing.
|
|
config BUSYBOX_CONFIG_MKDOSFS
|
|
bool "mkdosfs"
|
|
default BUSYBOX_DEFAULT_MKDOSFS
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Utility to create FAT32 filesystems.
|
|
|
|
config BUSYBOX_CONFIG_MKFS_VFAT
|
|
bool "mkfs.vfat"
|
|
default BUSYBOX_DEFAULT_MKFS_VFAT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Alias to "mkdosfs".
|
|
config BUSYBOX_CONFIG_MKSWAP
|
|
bool "mkswap"
|
|
default BUSYBOX_DEFAULT_MKSWAP
|
|
help
|
|
The mkswap utility is used to configure a file or disk partition as
|
|
Linux swap space. This allows Linux to use the entire file or
|
|
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.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MKSWAP_UUID
|
|
bool "UUID support"
|
|
default BUSYBOX_DEFAULT_FEATURE_MKSWAP_UUID
|
|
depends on BUSYBOX_CONFIG_MKSWAP
|
|
help
|
|
Generate swap spaces with universally unique identifiers.
|
|
config BUSYBOX_CONFIG_MORE
|
|
bool "more"
|
|
default BUSYBOX_DEFAULT_MORE
|
|
help
|
|
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
|
|
any need to reading text files, you can leave this disabled.
|
|
config BUSYBOX_CONFIG_MOUNT
|
|
bool "mount"
|
|
default BUSYBOX_DEFAULT_MOUNT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
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 BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
|
|
bool "Support option -f"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_FAKE
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
help
|
|
Enable support for faking a file system mount.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_VERBOSE
|
|
bool "Support option -v"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_VERBOSE
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
help
|
|
Enable multi-level -v[vv...] verbose messages. Useful if you
|
|
debug mount problems and want to see what is exactly passed
|
|
to the kernel.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_HELPERS
|
|
bool "Support mount helpers"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_HELPERS
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
help
|
|
Enable mounting of virtual file systems via external helpers.
|
|
E.g. "mount obexfs#-b00.11.22.33.44.55 /mnt" will in effect call
|
|
"obexfs -b00.11.22.33.44.55 /mnt"
|
|
Also "mount -t sometype [-o opts] fs /mnt" will try
|
|
"sometype [-o opts] fs /mnt" if simple mount syscall fails.
|
|
The idea is to use such virtual filesystems in /etc/fstab.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_LABEL
|
|
bool "Support specifying devices by label or UUID"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_LABEL
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
select BUSYBOX_CONFIG_VOLUMEID
|
|
help
|
|
This allows for specifying a device by label or uuid, rather than by
|
|
name. This feature utilizes the same functionality as blkid/findfs.
|
|
This also enables label or uuid support for swapon.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_NFS
|
|
bool "Support mounting NFS file systems on Linux < 2.6.23"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_NFS
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
select BUSYBOX_CONFIG_FEATURE_HAVE_RPC
|
|
select BUSYBOX_CONFIG_FEATURE_SYSLOG
|
|
help
|
|
Enable mounting of NFS file systems on Linux kernels prior
|
|
to version 2.6.23. Note that in this case mounting of NFS
|
|
over IPv6 will not be possible.
|
|
|
|
Note that this option links in RPC support from libc,
|
|
which is rather large (~10 kbytes on uclibc).
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_CIFS
|
|
bool "Support mounting CIFS/SMB file systems"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_CIFS
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
help
|
|
Enable support for samba mounts.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_FLAGS
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
bool "Support lots of -o flags in mount"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_FLAGS
|
|
help
|
|
Without this, mount only supports ro/rw/remount. With this, it
|
|
supports nosuid, suid, dev, nodev, exec, noexec, sync, async, atime,
|
|
noatime, diratime, nodiratime, loud, bind, move, shared, slave,
|
|
private, unbindable, rshared, rslave, rprivate, and runbindable.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_FSTAB
|
|
depends on BUSYBOX_CONFIG_MOUNT
|
|
bool "Support /etc/fstab and -a"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_FSTAB
|
|
help
|
|
Support mount all and looking for files in /etc/fstab.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_OTHERTAB
|
|
depends on BUSYBOX_CONFIG_FEATURE_MOUNT_FSTAB
|
|
bool "Support -T <alt_fstab>"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_OTHERTAB
|
|
help
|
|
Support mount -T (specifying an alternate fstab)
|
|
config BUSYBOX_CONFIG_NSENTER
|
|
bool "nsenter"
|
|
default BUSYBOX_DEFAULT_NSENTER
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Run program with namespaces of other processes.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_NSENTER_LONG_OPTS
|
|
bool "Enable long options"
|
|
default BUSYBOX_DEFAULT_FEATURE_NSENTER_LONG_OPTS
|
|
depends on BUSYBOX_CONFIG_NSENTER && BUSYBOX_CONFIG_LONG_OPTS
|
|
help
|
|
Support long options for the nsenter applet. This makes
|
|
the busybox implementation more compatible with upstream.
|
|
config BUSYBOX_CONFIG_PIVOT_ROOT
|
|
bool "pivot_root"
|
|
default BUSYBOX_DEFAULT_PIVOT_ROOT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
The pivot_root utility swaps the mount points for the root filesystem
|
|
with some other mounted filesystem. This allows you to do all sorts
|
|
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 BUSYBOX_CONFIG_RDATE
|
|
bool "rdate"
|
|
default BUSYBOX_DEFAULT_RDATE
|
|
help
|
|
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 BUSYBOX_CONFIG_RDEV
|
|
bool "rdev"
|
|
default BUSYBOX_DEFAULT_RDEV
|
|
help
|
|
Print the device node associated with the filesystem mounted at '/'.
|
|
config BUSYBOX_CONFIG_READPROFILE
|
|
bool "readprofile"
|
|
default BUSYBOX_DEFAULT_READPROFILE
|
|
#select PLATFORM_LINUX
|
|
help
|
|
This allows you to parse /proc/profile for basic profiling.
|
|
config BUSYBOX_CONFIG_REV
|
|
bool "rev"
|
|
default BUSYBOX_DEFAULT_REV
|
|
help
|
|
Reverse lines of a file or files.
|
|
config BUSYBOX_CONFIG_RTCWAKE
|
|
bool "rtcwake"
|
|
default BUSYBOX_DEFAULT_RTCWAKE
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Enter a system sleep state until specified wakeup time.
|
|
config BUSYBOX_CONFIG_SCRIPT
|
|
bool "script"
|
|
default BUSYBOX_DEFAULT_SCRIPT
|
|
help
|
|
The script makes typescript of terminal session.
|
|
config BUSYBOX_CONFIG_SCRIPTREPLAY
|
|
bool "scriptreplay"
|
|
default BUSYBOX_DEFAULT_SCRIPTREPLAY
|
|
help
|
|
This program replays a typescript, using timing information
|
|
given by script -t.
|
|
config BUSYBOX_CONFIG_SETARCH
|
|
bool "setarch"
|
|
default BUSYBOX_DEFAULT_SETARCH
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
The linux32 utility is used to create a 32bit environment for the
|
|
specified program (usually a shell). It only makes sense to have
|
|
this util on a system that supports both 64bit and 32bit userland
|
|
(like amd64/x86, ppc64/ppc, sparc64/sparc, etc...).
|
|
|
|
config BUSYBOX_CONFIG_LINUX32
|
|
bool "linux32"
|
|
default BUSYBOX_DEFAULT_LINUX32
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Alias to "setarch linux32".
|
|
|
|
config BUSYBOX_CONFIG_LINUX64
|
|
bool "linux64"
|
|
default BUSYBOX_DEFAULT_LINUX64
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Alias to "setarch linux64".
|
|
config BUSYBOX_CONFIG_SWAPON
|
|
bool "swapon"
|
|
default BUSYBOX_DEFAULT_SWAPON
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
This option enables the 'swapon' utility.
|
|
Once you have created some swap space using 'mkswap', you also need
|
|
to enable your swap space with the 'swapon' utility. The 'swapoff'
|
|
utility is used, typically at system shutdown, to disable any swap
|
|
space. If you are not using any swap space, you can leave this
|
|
option disabled.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_SWAPON_DISCARD
|
|
bool "Support discard option -d"
|
|
default BUSYBOX_DEFAULT_FEATURE_SWAPON_DISCARD
|
|
depends on BUSYBOX_CONFIG_SWAPON
|
|
help
|
|
Enable support for discarding swap area blocks at swapon and/or as
|
|
the kernel frees them. This option enables both the -d option on
|
|
'swapon' and the 'discard' option for swap entries in /etc/fstab.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_SWAPON_PRI
|
|
bool "Support priority option -p"
|
|
default BUSYBOX_DEFAULT_FEATURE_SWAPON_PRI
|
|
depends on BUSYBOX_CONFIG_SWAPON
|
|
help
|
|
Enable support for setting swap device priority in swapon.
|
|
|
|
config BUSYBOX_CONFIG_SWAPOFF
|
|
bool "swapoff"
|
|
default BUSYBOX_DEFAULT_SWAPOFF
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
This option enables the 'swapoff' utility.
|
|
config BUSYBOX_CONFIG_SWITCH_ROOT
|
|
bool "switch_root"
|
|
default BUSYBOX_DEFAULT_SWITCH_ROOT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
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.)
|
|
|
|
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 BUSYBOX_CONFIG_UEVENT
|
|
bool "uevent"
|
|
default BUSYBOX_DEFAULT_UEVENT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
uevent is a netlink listener for kernel uevent notifications
|
|
sent via netlink. It is usually used for dynamic device creation.
|
|
config BUSYBOX_CONFIG_UMOUNT
|
|
bool "umount"
|
|
default BUSYBOX_DEFAULT_UMOUNT
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
When you want to remove a mounted filesystem from its current mount
|
|
point, for example when you are shutting down the system, the
|
|
'umount' utility is the tool to use. If you enabled the 'mount'
|
|
utility, you almost certainly also want to enable 'umount'.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_UMOUNT_ALL
|
|
bool "Support option -a"
|
|
default BUSYBOX_DEFAULT_FEATURE_UMOUNT_ALL
|
|
depends on BUSYBOX_CONFIG_UMOUNT
|
|
help
|
|
Support -a option to unmount all currently mounted filesystems.
|
|
config BUSYBOX_CONFIG_UNSHARE
|
|
bool "unshare"
|
|
default BUSYBOX_DEFAULT_UNSHARE
|
|
depends on BUSYBOX_CONFIG_LONG_OPTS && !BUSYBOX_CONFIG_NOMMU
|
|
select BUSYBOX_CONFIG_PLATFORM_LINUX
|
|
help
|
|
Run program with some namespaces unshared from parent.
|
|
|
|
comment "Common options for mount/umount"
|
|
depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
|
|
bool "Support loopback mounts"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_LOOP
|
|
depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
|
|
help
|
|
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 BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP_CREATE
|
|
bool "Create new loopback devices if needed"
|
|
default BUSYBOX_DEFAULT_FEATURE_MOUNT_LOOP_CREATE
|
|
depends on BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
|
|
help
|
|
Linux kernels >= 2.6.24 support unlimited loopback devices. They are
|
|
allocated for use when trying to use a loop device. The loop device
|
|
must however exist.
|
|
|
|
This feature lets mount to try to create next /dev/loopN device
|
|
if it does not find a free one.
|
|
|
|
config BUSYBOX_CONFIG_FEATURE_MTAB_SUPPORT
|
|
bool "Support for the old /etc/mtab file"
|
|
default BUSYBOX_DEFAULT_FEATURE_MTAB_SUPPORT
|
|
depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
|
|
select BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
|
|
help
|
|
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 writable, tends to get easily confused
|
|
by --bind or --move mounts, won't update if you rename a directory
|
|
that contains a mount point, and so on. (In brief: avoid.)
|
|
|
|
About the only reason to use this is if you've removed /proc from
|
|
your kernel.
|
|
|
|
source volume_id/Config.in
|
|
|
|
endmenu
|