diff options
Diffstat (limited to 'package/busybox/config/util-linux/Config.in')
| -rw-r--r-- | package/busybox/config/util-linux/Config.in | 1543 |
1 files changed, 648 insertions, 895 deletions
diff --git a/package/busybox/config/util-linux/Config.in b/package/busybox/config/util-linux/Config.in index ff9dae4d1..bd6de5d38 100644 --- a/package/busybox/config/util-linux/Config.in +++ b/package/busybox/config/util-linux/Config.in @@ -1,677 +1,623 @@ # 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. +# see docs/Kconfig-language.txt. # menu "Linux System Utilities" -config BUSYBOX_BLKDISCARD - bool "blkdiscard" - default n +config BUSYBOX_ACPID + bool "acpid (9 kb)" + default y + select BUSYBOX_PLATFORM_LINUX help - blkdiscard discards sectors on a given device. + 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*). -config BUSYBOX_BLOCKDEV - bool "blockdev" - default n - help - Performs some ioctls with block devices. + 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. -config BUSYBOX_FALLOCATE - bool "fallocate (4.1 kb)" - default n - help - Preallocate space for files. + N.B. acpid relies on run-parts so have the latter installed. -config BUSYBOX_FATATTR - bool "fatattr" - default n - select BUSYBOX_PLATFORM_LINUX - help - fatattr lists or changes the file attributes on a fat file system. - -config BUSYBOX_FSTRIM - bool "fstrim" - default n - select BUSYBOX_PLATFORM_LINUX +config BUSYBOX_FEATURE_ACPID_COMPAT + bool "Accept and ignore redundant options" + default y + depends on BUSYBOX_ACPID help - Discard unused blocks on a mounted filesystem. - -config BUSYBOX_MDEV - bool "mdev" + Accept and ignore compatibility options -g -m -s -S -v. +config BUSYBOX_BLKDISCARD + bool "blkdiscard (4.3 kb)" default y select BUSYBOX_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_FEATURE_MDEV_CONF - bool "Support /etc/mdev.conf" + blkdiscard discards sectors on a given device. +config BUSYBOX_BLKID + bool "blkid (12 kb)" default y - depends on BUSYBOX_MDEV + select BUSYBOX_PLATFORM_LINUX + select BUSYBOX_VOLUMEID 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 + Lists labels and UUIDs of all filesystems. -config BUSYBOX_FEATURE_MDEV_RENAME - bool "Support subdirs/symlinks" +config BUSYBOX_FEATURE_BLKID_TYPE + bool "Print filesystem type" default y - depends on BUSYBOX_FEATURE_MDEV_CONF + depends on BUSYBOX_BLKID help - Add support for renaming devices and creating symlinks. - - For more information, please see docs/mdev.txt - -config BUSYBOX_FEATURE_MDEV_RENAME_REGEXP - bool "Support regular expressions substitutions when renaming device" + Show TYPE="filesystem type" +config BUSYBOX_BLOCKDEV + bool "blockdev (2.3 kb)" default y - depends on BUSYBOX_FEATURE_MDEV_RENAME help - Add support for regular expressions substitutions when renaming - device. - -config BUSYBOX_FEATURE_MDEV_EXEC - bool "Support command execution at device addition/removal" + Performs some ioctls with block devices. +config BUSYBOX_CAL + bool "cal (5.8 kb)" default y - depends on BUSYBOX_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_FEATURE_MDEV_LOAD_FIRMWARE - bool "Support loading of firmwares" + cal is used to display a monthly calendar. +config BUSYBOX_CHRT + bool "chrt (4.7 kb)" default y - depends on BUSYBOX_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_FEATURE_MDEV_DAEMON - bool "Support daemon mode" + Manipulate real-time attributes of a process. + This requires sched_{g,s}etparam support in your libc. +config BUSYBOX_DMESG + bool "dmesg (3.7 kb)" default y - depends on BUSYBOX_MDEV - help - Adds the -d option to run mdev in daemon mode handling hotplug - events from the kernel like udev. If the system generates many - hotplug events this mode of operation will consume less - resources than registering mdev as hotplug helper or using the - uevent applet. - -config BUSYBOX_MKE2FS - bool "mke2fs" - default n - select PLATFORM_LINUX - help - Utility to create EXT2 filesystems. - -config BUSYBOX_MKFS_EXT2 - bool "mkfs.ext2" - default n - select PLATFORM_LINUX - help - Alias to "mke2fs". - -config BUSYBOX_MKDOSFS - bool "mkdosfs" - default n - select PLATFORM_LINUX - help - Utility to create FAT32 filesystems. - -config BUSYBOX_NOLOGIN - bool "nologin" - default n - depends on BUSYBOX_FEATURE_SH_EMBEDDED_SCRIPTS - help - Politely refuse a login - -config BUSYBOX_NOLOGIN_DEPENDENCIES - bool "Enable dependencies for nologin" - default n # Y default makes it harder to select single-applet test - depends on BUSYBOX_NOLOGIN - select BUSYBOX_CAT - select BUSYBOX_ECHO - select BUSYBOX_SLEEP - help - nologin is implemented as a shell script. It requires the - following in the runtime environment: - cat echo sleep - If you know these will be available externally you can - disable this option. - -config BUSYBOX_NSENTER - bool "nsenter" - default n select BUSYBOX_PLATFORM_LINUX help - Run program with namespaces of other processes. - -config BUSYBOX_FEATURE_NSENTER_LONG_OPTS - bool "Enable long options" - default n - depends on BUSYBOX_NSENTER && BUSYBOX_LONG_OPTS - help - Support long options for the nsenter applet. This makes - the busybox implementation more compatible with upstream. - -config BUSYBOX_REV - bool "rev" - default n - help - Reverse lines of a file or files. + 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_UEVENT - bool "uevent" - default n - select BUSYBOX_PLATFORM_LINUX +config BUSYBOX_FEATURE_DMESG_PRETTY + bool "Pretty output" + default y + depends on BUSYBOX_DMESG help - uevent is a netlink listener for kernel uevent notifications - sent via netlink. It is usually used for dynamic device creation. + 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 + "<#>". -config BUSYBOX_UNSHARE - bool "unshare" - default n - depends on BUSYBOX_LONG_OPTS && !BUSYBOX_NOMMU - select BUSYBOX_PLATFORM_LINUX - help - Run program with some namespaces unshared from parent. + With this option you will see: + # dmesg + Linux version 2.6.17.4 ..... + BIOS-provided physical RAM map: + BIOS-e820: 0000000000000000 - 000000000009f000 (usable) -config BUSYBOX_ACPID - bool "acpid" - default n + 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_EJECT + bool "eject (4 kb)" + default y select BUSYBOX_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. + Used to eject cdroms. (defaults to /dev/cdrom) - N.B. acpid relies on run-parts so have the latter installed. - -config BUSYBOX_FEATURE_ACPID_COMPAT - bool "Accept and ignore redundant options" +config BUSYBOX_FEATURE_EJECT_SCSI + bool "SCSI support" default y - depends on BUSYBOX_ACPID + depends on BUSYBOX_EJECT help - Accept and ignore compatibility options -g -m -s -S -v. - -config BUSYBOX_BLKID - bool "blkid" + Add the -s option to eject, this allows to eject SCSI-Devices and + usb-storage devices. +config BUSYBOX_FALLOCATE + bool "fallocate (4.1 kb)" default y - select BUSYBOX_PLATFORM_LINUX - select BUSYBOX_VOLUMEID help - Lists labels and UUIDs of all filesystems. - WARNING: - With all submodules selected, it will add ~8k to busybox. - -config BUSYBOX_FEATURE_BLKID_TYPE - bool "Print filesystem type" - default n - depends on BUSYBOX_BLKID - help - Show TYPE="filesystem type" - -config BUSYBOX_DMESG - bool "dmesg" + Preallocate space for files. +config BUSYBOX_FATATTR + bool "fatattr (1.9 kb)" default y select BUSYBOX_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_FEATURE_DMESG_PRETTY - bool "Pretty dmesg output" - default y - depends on BUSYBOX_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) - + fatattr lists or changes the file attributes on a fat file system. config BUSYBOX_FBSET - bool "fbset" - depends on !BUSYBOX_DISABLE_FBSET - default n + bool "fbset (5.9 kb)" + default y select BUSYBOX_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. + 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_FEATURE_FBSET_FANCY - bool "Turn on extra fbset options" + bool "Enable extra options" default y depends on BUSYBOX_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. + 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_FEATURE_FBSET_READMODE - bool "Turn on fbset readmode support" + bool "Enable readmode support" default y depends on BUSYBOX_FBSET help - This option allows fbset to read the video mode database stored by - default as /etc/fb.modes, which can be used to set frame buffer - device to pre-defined video modes. - -config BUSYBOX_FDFLUSH - bool "fdflush" - default n - select BUSYBOX_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. - + This option allows fbset to read the video mode database stored by + default as /etc/fb.modes, which can be used to set frame buffer + device to pre-defined video modes. config BUSYBOX_FDFORMAT - bool "fdformat" - default n + bool "fdformat (4.4 kb)" + default y select BUSYBOX_PLATFORM_LINUX help - fdformat is used to low-level format a floppy disk. - + fdformat is used to low-level format a floppy disk. config BUSYBOX_FDISK - bool "fdisk" - default n - depends on !BUSYBOX_DISABLE_FDISK + bool "fdisk (37 kb)" + default y select BUSYBOX_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. + 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_FDISK_SUPPORT_LARGE_DISKS bool "Support over 4GB disks" default y depends on BUSYBOX_FDISK - depends on !BUSYBOX_LFS # with LFS no special code is needed - help - Enable this option to support large disks > 4GB. + depends on !BUSYBOX_LFS # with BUSYBOX_LFS no special code is needed config BUSYBOX_FEATURE_FDISK_WRITABLE bool "Write support" default y depends on BUSYBOX_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. + 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_FEATURE_AIX_LABEL bool "Support AIX disklabels" default n depends on BUSYBOX_FDISK && BUSYBOX_FEATURE_FDISK_WRITABLE help - Enabling this option allows you to create or change AIX disklabels. - Most people can safely leave this option disabled. + Enabling this option allows you to create or change AIX disklabels. + Most people can safely leave this option disabled. config BUSYBOX_FEATURE_SGI_LABEL bool "Support SGI disklabels" default n depends on BUSYBOX_FDISK && BUSYBOX_FEATURE_FDISK_WRITABLE help - Enabling this option allows you to create or change SGI disklabels. - Most people can safely leave this option disabled. + Enabling this option allows you to create or change SGI disklabels. + Most people can safely leave this option disabled. config BUSYBOX_FEATURE_SUN_LABEL bool "Support SUN disklabels" default n depends on BUSYBOX_FDISK && BUSYBOX_FEATURE_FDISK_WRITABLE help - Enabling this option allows you to create or change SUN disklabels. - Most people can safely leave this option disabled. + Enabling this option allows you to create or change SUN disklabels. + Most people can safely leave this option disabled. config BUSYBOX_FEATURE_OSF_LABEL bool "Support BSD disklabels" default n depends on BUSYBOX_FDISK && BUSYBOX_FEATURE_FDISK_WRITABLE help - Enabling this option allows you to create or change BSD disklabels - and define and edit BSD disk slices. + Enabling this option allows you to create or change BSD disklabels + and define and edit BSD disk slices. config BUSYBOX_FEATURE_GPT_LABEL bool "Support GPT disklabels" default n depends on BUSYBOX_FDISK && BUSYBOX_FEATURE_FDISK_WRITABLE help - Enabling this option allows you to view GUID Partition Table - disklabels. + Enabling this option allows you to view GUID Partition Table + disklabels. config BUSYBOX_FEATURE_FDISK_ADVANCED bool "Support expert mode" default y depends on BUSYBOX_FDISK && BUSYBOX_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. - + 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_FINDFS - bool "findfs" - default n + bool "findfs (12 kb)" + default y select BUSYBOX_PLATFORM_LINUX select BUSYBOX_VOLUMEID help - Prints the name of a filesystem with given label or UUID. - WARNING: - With all submodules selected, it will add ~8k to busybox. - + Prints the name of a filesystem with given label or UUID. config BUSYBOX_FLOCK - bool "flock" - default n + bool "flock (6.3 kb)" + default y + help + Manage locks from shell scripts +config BUSYBOX_FDFLUSH + bool "fdflush (1.3 kb)" + default y + select BUSYBOX_PLATFORM_LINUX help - Manage locks from shell scripts + 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_FREERAMDISK - bool "freeramdisk" - default n + bool "freeramdisk (1.3 kb)" + default y select BUSYBOX_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. - + 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_FSCK_MINIX - bool "fsck_minix" - default n + bool "fsck.minix (13 kb)" + default y 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. - + 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_FSFREEZE bool "fsfreeze (3.5 kb)" - default n + default y select BUSYBOX_PLATFORM_LINUX select BUSYBOX_LONG_OPTS help Halt new accesses and flush writes on a mounted filesystem. - -config BUSYBOX_MKFS_EXT2 - bool "mkfs_ext2" - default n - select BUSYBOX_PLATFORM_LINUX - help - Utility to create EXT2 filesystems. - -config BUSYBOX_MKFS_MINIX - bool "mkfs_minix" - default n - select BUSYBOX_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_FEATURE_MINIX2 - bool "Support Minix fs v2 (fsck_minix/mkfs_minix)" +config BUSYBOX_FSTRIM + bool "fstrim (4.4 kb)" default y - depends on BUSYBOX_FSCK_MINIX || BUSYBOX_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_MKFS_REISER - bool "mkfs_reiser" - default n - select BUSYBOX_PLATFORM_LINUX - help - Utility to create ReiserFS filesystems. - Note: this applet needs a lot of testing and polishing. - -config BUSYBOX_MKFS_VFAT - bool "mkfs_vfat" - default n select BUSYBOX_PLATFORM_LINUX help - Utility to create FAT32 filesystems. - + Discard unused blocks on a mounted filesystem. config BUSYBOX_GETOPT - bool "getopt" - default n + bool "getopt (5.8 kb)" + default y 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. + 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_FEATURE_GETOPT_LONG - bool "Support option -l" - default y if LONG_OPTS - depends on BUSYBOX_GETOPT + bool "Support -l LONGOPTs" + default y + depends on BUSYBOX_GETOPT && BUSYBOX_LONG_OPTS help - Enable support for long options (option -l). - + Enable support for long options (option -l). config BUSYBOX_HEXDUMP - bool "hexdump" - default n + bool "hexdump (8.6 kb)" + default y help - The hexdump utility is used to display binary data in a readable - way that is comparable to the output from most hex editors. + 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_FEATURE_HEXDUMP_REVERSE bool "Support -R, reverse of 'hexdump -Cv'" default y depends on BUSYBOX_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. + 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_HD - bool "hd" - default n + bool "hd (7.8 kb)" + default y help - hd is an alias to hexdump -C. - + hd is an alias to hexdump -C. config BUSYBOX_XXD bool "xxd (8.9 kb)" - default n + default y help The xxd utility is used to display binary data in a readable way that is comparable to the output from most hex editors. - config BUSYBOX_HWCLOCK - bool "hwclock" - default y if ADK_TARGET_WITH_RTC - default n - select BUSYBOX_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_FEATURE_HWCLOCK_LONG_OPTIONS - bool "Support long options (--hctosys,...)" + bool "hwclock (5.8 kb)" default y - depends on BUSYBOX_HWCLOCK && BUSYBOX_LONG_OPTS + select BUSYBOX_PLATFORM_LINUX 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. + 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_FEATURE_HWCLOCK_ADJTIME_FHS bool "Use FHS /var/lib/hwclock/adjtime" default n # util-linux-ng in Fedora 13 still uses /etc/adjtime depends on BUSYBOX_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 + 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_IONICE + bool "ionice (3.8 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Set/set program io scheduling class and priority + Requires kernel >= 2.6.13 config BUSYBOX_IPCRM - bool "ipcrm" - default n + bool "ipcrm (3.2 kb)" + default y help - The ipcrm utility allows the removal of System V interprocess - communication (IPC) objects and the associated data structures - from the system. - + The ipcrm utility allows the removal of System V interprocess + communication (IPC) objects and the associated data structures + from the system. config BUSYBOX_IPCS - bool "ipcs" - default n + bool "ipcs (11 kb)" + default y select BUSYBOX_PLATFORM_LINUX help - The ipcs utility is used to provide information on the currently - allocated System V interprocess (IPC) objects in the system. + The ipcs utility is used to provide information on the currently + allocated System V interprocess (IPC) objects in the system. +config BUSYBOX_LAST + bool "last (6.1 kb)" + default y + depends on BUSYBOX_FEATURE_WTMP + help + 'last' displays a list of the last users that logged into the system. +config BUSYBOX_FEATURE_LAST_FANCY + bool "Output extra information" + default y + depends on BUSYBOX_LAST + help + 'last' displays detailed information about the last users that + logged into the system (mimics sysvinit last). +900 bytes. config BUSYBOX_LOSETUP - bool "losetup" - default n + bool "losetup (5.5 kb)" + default y select BUSYBOX_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. - + 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_LSPCI - bool "lspci" - depends on !BUSYBOX_DISABLE_LSPCI - default n - #select PLATFORM_LINUX + bool "lspci (6.3 kb)" + default y + #select BUSYBOX_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. + 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_LSUSB - bool "lsusb" - depends on !BUSYBOX_DISABLE_LSUSB - default n - #select PLATFORM_LINUX + bool "lsusb (4.2 kb)" + default y + #select BUSYBOX_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_MDEV + bool "mdev (17 kb)" + default y + select BUSYBOX_PLATFORM_LINUX help - lsusb is a utility for displaying information about USB buses in the - system and devices connected to them. + mdev is a mini-udev implementation for dynamically creating device + nodes in the /dev directory. - This version uses sysfs (/sys/bus/usb/devices) only. + For more information, please see docs/mdev.txt -config BUSYBOX_MKSWAP - bool "mkswap" +config BUSYBOX_FEATURE_MDEV_CONF + bool "Support /etc/mdev.conf" + default y + depends on BUSYBOX_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_FEATURE_MDEV_RENAME + bool "Support subdirs/symlinks" + default y + depends on BUSYBOX_FEATURE_MDEV_CONF + help + Add support for renaming devices and creating symlinks. + + For more information, please see docs/mdev.txt + +config BUSYBOX_FEATURE_MDEV_RENAME_REGEXP + bool "Support regular expressions substitutions when renaming device" + default y + depends on BUSYBOX_FEATURE_MDEV_RENAME + help + Add support for regular expressions substitutions when renaming + device. + +config BUSYBOX_FEATURE_MDEV_EXEC + bool "Support command execution at device addition/removal" + default y + depends on BUSYBOX_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_FEATURE_MDEV_LOAD_FIRMWARE + bool "Support loading of firmware" + default y + depends on BUSYBOX_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_FEATURE_MDEV_DAEMON + bool "Support daemon mode" + default y + depends on BUSYBOX_MDEV + help + Adds the -d option to run mdev in daemon mode handling hotplug + events from the kernel like udev. If the system generates many + hotplug events this mode of operation will consume less + resources than registering mdev as hotplug helper or using the + uevent applet. +config BUSYBOX_MESG + bool "mesg (1.4 kb)" + default y + help + Mesg controls access to your terminal by others. It is typically + used to allow or disallow other users to write to your terminal + +config BUSYBOX_FEATURE_MESG_ENABLE_ONLY_GROUP + bool "Enable writing to tty only by group, not by everybody" + default y + depends on BUSYBOX_MESG + help + Usually, ttys are owned by group "tty", and "write" tool is + setgid to this group. This way, "mesg y" only needs to enable + "write by owning group" bit in tty mode. + + If you set this option to N, "mesg y" will enable writing + by anybody at all. This is not recommended. +config BUSYBOX_MKE2FS + bool "mke2fs (10 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Utility to create EXT2 filesystems. + +config BUSYBOX_MKFS_EXT2 + bool "mkfs.ext2 (10 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Alias to "mke2fs". +config BUSYBOX_MKFS_MINIX + bool "mkfs.minix (10 kb)" + default y + select BUSYBOX_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_FEATURE_MINIX2 + bool "Support Minix fs v2 (fsck_minix/mkfs_minix)" + default y + depends on BUSYBOX_FSCK_MINIX || BUSYBOX_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_MKFS_REISER + bool "mkfs_reiser" default n + select BUSYBOX_PLATFORM_LINUX 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. + Utility to create ReiserFS filesystems. + Note: this applet needs a lot of testing and polishing. +config BUSYBOX_MKDOSFS + bool "mkdosfs (7.2 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Utility to create FAT32 filesystems. + +config BUSYBOX_MKFS_VFAT + bool "mkfs.vfat (7.2 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Alias to "mkdosfs". +config BUSYBOX_MKSWAP + bool "mkswap (6.3 kb)" + default y + 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_FEATURE_MKSWAP_UUID bool "UUID support" default y depends on BUSYBOX_MKSWAP help - Generate swap spaces with universally unique identifiers. - + Generate swap spaces with universally unique identifiers. config BUSYBOX_MORE - bool "more" - default n + bool "more (7 kb)" + default y 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. - + 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_MOUNT - bool "mount" + bool "mount (23 kb)" default y - depends on !BUSYBOX_DISABLE_MOUNT select BUSYBOX_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. + 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. config BUSYBOX_FEATURE_MOUNT_FAKE - bool "Support option -f" - default n + bool "Support -f (fake mount)" + default y depends on BUSYBOX_MOUNT help - Enable support for faking a file system mount. + Enable support for faking a file system mount. config BUSYBOX_FEATURE_MOUNT_VERBOSE - bool "Support option -v" - default n + bool "Support -v (verbose)" + default y depends on BUSYBOX_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. + 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_FEATURE_MOUNT_HELPERS bool "Support mount helpers" - default y + default n depends on BUSYBOX_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. + 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_FEATURE_MOUNT_LABEL bool "Support specifying devices by label or UUID" @@ -679,138 +625,168 @@ config BUSYBOX_FEATURE_MOUNT_LABEL depends on BUSYBOX_MOUNT select BUSYBOX_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. + This allows for specifying a device by label or uuid, rather than by + name. This feature utilizes the same functionality as blkid/findfs. config BUSYBOX_FEATURE_MOUNT_NFS bool "Support mounting NFS file systems on Linux < 2.6.23" default n depends on BUSYBOX_MOUNT - select BUSYBOX_FEATURE_HAVE_RPC select BUSYBOX_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. + 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). + Note that this option links in RPC support from libc, + which is rather large (~10 kbytes on uclibc). config BUSYBOX_FEATURE_MOUNT_CIFS bool "Support mounting CIFS/SMB file systems" - default n + default y depends on BUSYBOX_MOUNT help - Enable support for samba mounts. + Enable support for samba mounts. config BUSYBOX_FEATURE_MOUNT_FLAGS depends on BUSYBOX_MOUNT - bool "Support lots of -o flags in mount" + bool "Support lots of -o flags" default y 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. + 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_FEATURE_MOUNT_FSTAB depends on BUSYBOX_MOUNT - bool "Support /etc/fstab and -a" + bool "Support /etc/fstab and -a (mount all)" default y help - Support mount all and looking for files in /etc/fstab. + Support mount all and looking for files in /etc/fstab. config BUSYBOX_FEATURE_MOUNT_OTHERTAB depends on BUSYBOX_FEATURE_MOUNT_FSTAB bool "Support -T <alt_fstab>" - default n + default y help - Support mount -T (specifying an alternate fstab) + Support mount -T (specifying an alternate fstab) +config BUSYBOX_MOUNTPOINT + bool "mountpoint (4.9 kb)" + default y + help + mountpoint checks if the directory is a mountpoint. +config BUSYBOX_NOLOGIN + bool "nologin" + default y + depends on BUSYBOX_FEATURE_SH_EMBEDDED_SCRIPTS + help + Politely refuse a login +config BUSYBOX_NOLOGIN_DEPENDENCIES + bool "Enable dependencies for nologin" + default n # Y default makes it harder to select single-applet test + depends on BUSYBOX_NOLOGIN + select BUSYBOX_CAT + select BUSYBOX_ECHO + select BUSYBOX_SLEEP + help + nologin is implemented as a shell script. It requires the + following in the runtime environment: + cat echo sleep + If you know these will be available externally you can + disable this option. +config BUSYBOX_NSENTER + bool "nsenter (6.5 kb)" + default y + select BUSYBOX_PLATFORM_LINUX + help + Run program with namespaces of other processes. config BUSYBOX_PIVOT_ROOT - bool "pivot_root" - default n + bool "pivot_root (1.1 kb)" + default y select BUSYBOX_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. + 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_RDATE - bool "rdate" - depends on !BUSYBOX_DISABLE_RDATE - default n + bool "rdate (5.6 kb)" + default y 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. - + 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_RDEV - bool "rdev" + bool "rdev (1.8 kb)" default y help - Print the device node associated with the filesystem mounted at '/'. - + Print the device node associated with the filesystem mounted at '/'. config BUSYBOX_READPROFILE - bool "readprofile" - default n - #select PLATFORM_LINUX + bool "readprofile (7.1 kb)" + default y + #select BUSYBOX_PLATFORM_LINUX help - This allows you to parse /proc/profile for basic profiling. - + This allows you to parse /proc/profile for basic profiling. +config BUSYBOX_RENICE + bool "renice (4.2 kb)" + default y + help + Renice alters the scheduling priority of one or more running + processes. +config BUSYBOX_REV + bool "rev (4.4 kb)" + default y + help + Reverse lines of a file or files. config BUSYBOX_RTCWAKE - bool "rtcwake" - default n + bool "rtcwake (6.8 kb)" + default y select BUSYBOX_PLATFORM_LINUX help - Enter a system sleep state until specified wakeup time. - + Enter a system sleep state until specified wakeup time. config BUSYBOX_SCRIPT - bool "script" - default n + bool "script (8.6 kb)" + default y help - The script makes typescript of terminal session. - + The script makes typescript of terminal session. config BUSYBOX_SCRIPTREPLAY - bool "scriptreplay" - default n + bool "scriptreplay (2.4 kb)" + default y help - This program replays a typescript, using timing information - given by script -t. - + This program replays a typescript, using timing information + given by script -t. config BUSYBOX_SETARCH - bool "setarch" - default n + bool "setarch (3.6 kb)" + default y select BUSYBOX_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...). + 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_LINUX32 - bool "linux32" - default n - select PLATFORM_LINUX + bool "linux32 (3.3 kb)" + default y + select BUSYBOX_PLATFORM_LINUX help - Alias to "setarch linux32". + Alias to "setarch linux32". config BUSYBOX_LINUX64 - bool "linux64" - default n - select PLATFORM_LINUX + bool "linux64 (3.3 kb)" + default y + select BUSYBOX_PLATFORM_LINUX help - Alias to "setarch linux64". - + Alias to "setarch linux64". config BUSYBOX_SETPRIV bool "setpriv (6.6 kb)" - default n + default y select BUSYBOX_PLATFORM_LINUX select BUSYBOX_LONG_OPTS help @@ -844,411 +820,188 @@ config BUSYBOX_FEATURE_SETPRIV_CAPABILITY_NAMES e.g. "net_admin", or using their index, e.g. "cap_12". Enabling this option allows using the human-readable names in addition to the index-based names. - +config BUSYBOX_SETSID + bool "setsid (3.6 kb)" + default y + help + setsid runs a program in a new session config BUSYBOX_SWAPON - bool "swapon" - default n - select PLATFORM_LINUX + bool "swapon (15 kb)" + default y + select BUSYBOX_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. + 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_FEATURE_SWAPON_DISCARD bool "Support discard option -d" - default n + default y depends on BUSYBOX_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. + 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_FEATURE_SWAPON_PRI bool "Support priority option -p" default y depends on BUSYBOX_SWAPON help - Enable support for setting swap device priority in swapon. + Enable support for setting swap device priority in swapon. config BUSYBOX_SWAPOFF - bool "swapoff" - default n - select PLATFORM_LINUX - help - This option enables the 'swapoff' utility. - -config BUSYBOX_SWITCH_ROOT - bool "switch_root" - default n - select BUSYBOX_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_UMOUNT - bool "umount" + bool "swapoff (14 kb)" default y - depends on !BUSYBOX_DISABLE_UMOUNT select BUSYBOX_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_FEATURE_UMOUNT_ALL - bool "Support option -a" - default y - depends on BUSYBOX_UMOUNT - help - Support -a option to unmount all currently mounted filesystems. - -comment "Common options for mount/umount" - depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT - -config BUSYBOX_FEATURE_MOUNT_LOOP - bool "Support loopback mounts" - default y - depends on BUSYBOX_MOUNT || BUSYBOX_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_FEATURE_MOUNT_LOOP_CREATE - bool "Create new loopback devices if needed" - default y - depends on BUSYBOX_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_FEATURE_MTAB_SUPPORT - bool "Support for the old /etc/mtab file" - default n - depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT - select BUSYBOX_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. - -config BUSYBOX_VOLUMEID - bool #No description makes it a hidden option - default n - -menu "Filesystem/Volume identification" - depends on BUSYBOX_VOLUMEID - -config BUSYBOX_FEATURE_VOLUMEID_BCACHE - bool "bcache filesystem" - default n - depends on BUSYBOX_VOLUMEID - help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_EXT - bool "Ext filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_BTRFS - bool "btrfs filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_REISERFS - bool "Reiser filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_F2FS - bool "f2fs filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - F2FS (aka Flash-Friendly File System) is a log-structured file system, - which is adapted to newer forms of storage. F2FS also remedies some - known issues of the older log structured file systems, such as high - cleaning overhead. - -config BUSYBOX_FEATURE_VOLUMEID_FAT - bool "fat filesystem" +config BUSYBOX_FEATURE_SWAPONOFF_LABEL + bool "Support specifying devices by label or UUID" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_SWAPON || BUSYBOX_SWAPOFF + select BUSYBOX_VOLUMEID help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_EXFAT - bool "exFAT filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - exFAT (extended FAT) is a proprietary file system designed especially - for flash drives. It has many features from NTFS, but with less - overhead. exFAT is used on most SDXC cards for consumer electronics. - -config BUSYBOX_FEATURE_VOLUMEID_HFS - bool "hfs filesystem" + This allows for specifying a device by label or uuid, rather than by + name. This feature utilizes the same functionality as blkid/findfs. +config BUSYBOX_SWITCH_ROOT + bool "switch_root (5.5 kb)" default y - depends on BUSYBOX_VOLUMEID + select BUSYBOX_PLATFORM_LINUX help - TODO + 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 BUSYBOX_FEATURE_VOLUMEID_MINIX - bool "minix filesystem" - default y - depends on BUSYBOX_VOLUMEID + 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. -config BUSYBOX_FEATURE_VOLUMEID_NILFS - bool "nilfs filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - TODO + * 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_FEATURE_VOLUMEID_JFS - bool "jfs filesystem" +config BUSYBOX_TASKSET + bool "taskset (4.2 kb)" default y - depends on BUSYBOX_VOLUMEID help - TODO + Retrieve or set a processes's CPU affinity. + This requires sched_{g,s}etaffinity support in your libc. -### config FEATURE_VOLUMEID_UFS -### bool "ufs filesystem" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -config BUSYBOX_FEATURE_VOLUMEID_XFS - bool "xfs filesystem" +config BUSYBOX_FEATURE_TASKSET_FANCY + bool "Fancy output" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_TASKSET help - TODO + Needed for machines with more than 32-64 CPUs: + affinity parameter 0xHHHHHHHHHHHHHHHHHHHH can be arbitrarily long + in this case. Otherwise, it is limited to sizeof(long). -config BUSYBOX_FEATURE_VOLUMEID_NTFS - bool "ntfs filesystem" +config BUSYBOX_FEATURE_TASKSET_CPULIST + bool "CPU list support (-c option)" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_FEATURE_TASKSET_FANCY help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_ISO9660 - bool "iso9660 filesystem" + Add support for taking/printing affinity as CPU list when '-c' + option is used. For example, it prints '0-3,7' instead of mask '8f'. +config BUSYBOX_UEVENT + bool "uevent (3.1 kb)" default y - depends on BUSYBOX_VOLUMEID + select BUSYBOX_PLATFORM_LINUX help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_UDF - bool "udf filesystem" + uevent is a netlink listener for kernel uevent notifications + sent via netlink. It is usually used for dynamic device creation. +config BUSYBOX_UMOUNT + bool "umount (5.1 kb)" default y - depends on BUSYBOX_VOLUMEID + select BUSYBOX_PLATFORM_LINUX help - TODO + 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_FEATURE_VOLUMEID_LUKS - bool "luks filesystem" +config BUSYBOX_FEATURE_UMOUNT_ALL + bool "Support -a (unmount all)" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_UMOUNT help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_LINUXSWAP - bool "linux swap filesystem" + Support -a option to unmount all currently mounted filesystems. +config BUSYBOX_UNSHARE + bool "unshare (7.2 kb)" default y - depends on BUSYBOX_VOLUMEID + depends on !BUSYBOX_NOMMU + select BUSYBOX_PLATFORM_LINUX + select BUSYBOX_LONG_OPTS help - TODO - -### config FEATURE_VOLUMEID_LVM -### bool "lvm" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -config BUSYBOX_FEATURE_VOLUMEID_CRAMFS - bool "cramfs filesystem" + Run program with some namespaces unshared from parent. +config BUSYBOX_WALL + bool "wall (2.6 kb)" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_FEATURE_UTMP help - TODO + Write a message to all users that are logged in. -### config FEATURE_VOLUMEID_HPFS -### bool "hpfs filesystem" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO +comment "Common options for mount/umount" + depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT -config BUSYBOX_FEATURE_VOLUMEID_ROMFS - bool "romfs filesystem" +config BUSYBOX_FEATURE_MOUNT_LOOP + bool "Support loopback mounts" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT help - TODO + 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. -config BUSYBOX_FEATURE_VOLUMEID_SQUASHFS - bool "SquashFS filesystem" - default y - depends on BUSYBOX_VOLUMEID && BUSYBOX_FEATURE_BLKID_TYPE - help - Squashfs is a compressed read-only filesystem for Linux. Squashfs is - intended for general read-only filesystem use and in constrained block - device/memory systems (e.g. embedded systems) where low overhead is - needed. + 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_FEATURE_VOLUMEID_SYSV - bool "sysv filesystem" +config BUSYBOX_FEATURE_MOUNT_LOOP_CREATE + bool "Create new loopback devices if needed" default y - depends on BUSYBOX_VOLUMEID + depends on BUSYBOX_FEATURE_MOUNT_LOOP help - TODO - -### config FEATURE_VOLUMEID_MINIX -### bool "minix filesystem" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO + 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. -### These only detect partition tables - not used (yet?) -### config FEATURE_VOLUMEID_MAC -### bool "mac filesystem" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO -### -### config FEATURE_VOLUMEID_MSDOS -### bool "msdos filesystem" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO + This feature lets mount to try to create next /dev/loopN device + if it does not find a free one. -config BUSYBOX_FEATURE_VOLUMEID_OCFS2 - bool "ocfs2 filesystem" - default y - depends on BUSYBOX_VOLUMEID +config BUSYBOX_FEATURE_MTAB_SUPPORT + bool "Support old /etc/mtab file" + default n + depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT + select BUSYBOX_FEATURE_MOUNT_FAKE help - TODO - -### config FEATURE_VOLUMEID_HIGHPOINTRAID -### bool "highpoint raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_ISWRAID -### bool "intel raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_LSIRAID -### bool "lsi raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_VIARAID -### bool "via raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_SILICONRAID -### bool "silicon raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_NVIDIARAID -### bool "nvidia raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -### config FEATURE_VOLUMEID_PROMISERAID -### bool "promise raid" -### default y -### depends on BUSYBOX_VOLUMEID -### help -### TODO - -config BUSYBOX_FEATURE_VOLUMEID_LINUXRAID - bool "linuxraid" - default y - depends on BUSYBOX_VOLUMEID - help - TODO - -config BUSYBOX_FEATURE_VOLUMEID_UBIFS - bool "UBIFS filesystem" - default y - depends on BUSYBOX_VOLUMEID - help - UBIFS (Unsorted Block Image File System) is a file - system for use with raw flash memory media. - - -endmenu + 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 package/busybox/config/util-linux/volume_id/Config.in endmenu |