diff options
Diffstat (limited to 'config/busybox/util-linux/Config.in')
| -rw-r--r-- | config/busybox/util-linux/Config.in | 439 |
1 files changed, 236 insertions, 203 deletions
diff --git a/config/busybox/util-linux/Config.in b/config/busybox/util-linux/Config.in index 32e55fcda..a1a127a9e 100644 --- a/config/busybox/util-linux/Config.in +++ b/config/busybox/util-linux/Config.in @@ -4,27 +4,36 @@ # menu "Linux System Utilities" - depends on BUSYBOX -config BB_CONFIG_DMESG +config BUSYBOX_BLKID + bool "blkid" + default n + select BUSYBOX_VOLUMEID + help + Lists labels and UUIDs of all filesystems. + WARNING: + With all submodules selected, it will add ~8k to busybox. + +config BUSYBOX_DMESG bool "dmesg" default n help - dmesg is used to examine or control the kernel ring buffer. When the + 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 + 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 + are also logged to the system console. Enable this option if you wish to enable the 'dmesg' utility. -config BB_CONFIG_FEATURE_DMESG_PRETTY +config BUSYBOX_FEATURE_DMESG_PRETTY bool "Pretty dmesg output" default y - depends on BB_CONFIG_DMESG + 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 "<#>". + The syslog level is a string prefixed to every line with the form + "<#>". With this option you will see: # dmesg @@ -38,263 +47,261 @@ config BB_CONFIG_FEATURE_DMESG_PRETTY <6>BIOS-provided physical RAM map: <6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable) -config BB_CONFIG_FBSET +config BUSYBOX_FBSET bool "fbset" default n help fbset is used to show or change the settings of a Linux frame buffer - device. The frame buffer device provides a simple and unique - interface to access a graphics display. Enable this option + 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 BB_CONFIG_FEATURE_FBSET_FANCY +config BUSYBOX_FEATURE_FBSET_FANCY bool "Turn on extra fbset options" default n - depends on BB_CONFIG_FBSET + 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 + framebuffer size, color depth, etc. interface to access a graphics + display. Enable this option if you wish to enable extended fbset options. -config BB_CONFIG_FEATURE_FBSET_READMODE +config BUSYBOX_FEATURE_FBSET_READMODE bool "Turn on fbset readmode support" default n - depends on BB_CONFIG_FBSET + 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 BB_CONFIG_FDFLUSH +config BUSYBOX_FDFLUSH bool "fdflush" default n help fdflush is only needed when changing media on slightly-broken - removable media drives. It is used to make Linux believe that a + 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 + 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 + you change a disk. Most people have working hardware and can safely leave this disabled. -config BB_CONFIG_FDFORMAT +config BUSYBOX_FDFORMAT bool "fdformat" default n help fdformat is used to low-level format a floppy disk. -config BB_CONFIG_FDISK +config BUSYBOX_FDISK bool "fdisk" default n help The fdisk utility is used to divide hard disks into one or more - logical disks, which are generally called partitions. This utility + 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 BB_CONFIG_FDISK_SUPPORT_LARGE_DISKS +config BUSYBOX_FDISK_SUPPORT_LARGE_DISKS bool "Support over 4GB disks" default y - depends on BB_CONFIG_FDISK + depends on BUSYBOX_FDISK help Enable this option to support large disks > 4GB. -config BB_CONFIG_FEATURE_FDISK_WRITABLE +config BUSYBOX_FEATURE_FDISK_WRITABLE bool "Write support" default y - depends on BB_CONFIG_FDISK + 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 + and write those changes out to disk. If you leave this option disabled, you will only be able to view the partition table. -config BB_CONFIG_FEATURE_AIX_LABEL +config BUSYBOX_FEATURE_AIX_LABEL bool "Support AIX disklabels" default n - depends on BB_CONFIG_FDISK && BB_CONFIG_FEATURE_FDISK_WRITABLE + 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. -config BB_CONFIG_FEATURE_SGI_LABEL +config BUSYBOX_FEATURE_SGI_LABEL bool "Support SGI disklabels" default n - depends on BB_CONFIG_FDISK && BB_CONFIG_FEATURE_FDISK_WRITABLE + 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. -config BB_CONFIG_FEATURE_SUN_LABEL +config BUSYBOX_FEATURE_SUN_LABEL bool "Support SUN disklabels" default n - depends on BB_CONFIG_FDISK && BB_CONFIG_FEATURE_FDISK_WRITABLE + 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. -config BB_CONFIG_FEATURE_OSF_LABEL +config BUSYBOX_FEATURE_OSF_LABEL bool "Support BSD disklabels" default n - depends on BB_CONFIG_FDISK && BB_CONFIG_FEATURE_FDISK_WRITABLE + 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. -config BB_CONFIG_FEATURE_FDISK_ADVANCED +config BUSYBOX_FEATURE_FDISK_ADVANCED bool "Support expert mode" default n - depends on BB_CONFIG_FDISK && BB_CONFIG_FEATURE_FDISK_WRITABLE + 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 + partition, and similarly evil things. Unless you have a very good reason you would be wise to leave this disabled. -config BB_CONFIG_FINDFS +config BUSYBOX_FINDFS bool "findfs" default n - select BB_CONFIG_VOLUMEID + select BUSYBOX_VOLUMEID help - This is similar to the findfs program that is part of the e2fsprogs - package. However, the e2fsprogs version only support ext2/3. This - version supports those in addition to FAT, swap, and ReiserFS. + Prints the name of a filesystem with given label or UUID. WARNING: With all submodules selected, it will add ~8k to busybox. -config BB_CONFIG_FREERAMDISK +config BUSYBOX_FREERAMDISK bool "freeramdisk" default n help - Linux allows you to create ramdisks. This utility allows you to + 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 + 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 + ramdisk. If you have no use for freeing memory from a ramdisk, leave this disabled. -config BB_CONFIG_FSCK_MINIX +config BUSYBOX_FSCK_MINIX bool "fsck_minix" default n help The minix filesystem is a nice, small, compact, read-write filesystem - with little overhead. It is not a journaling filesystem however and + 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 + 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 BB_CONFIG_MKFS_MINIX +config BUSYBOX_MKFS_MINIX bool "mkfs_minix" default n 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. + with little overhead. If you wish to be able to create minix + filesystems this utility will do the job for you. comment "Minix filesystem support" - depends on BB_CONFIG_FSCK_MINIX || BB_CONFIG_MKFS_MINIX + depends on BUSYBOX_FSCK_MINIX || BUSYBOX_MKFS_MINIX -config BB_CONFIG_FEATURE_MINIX2 +config BUSYBOX_FEATURE_MINIX2 bool "Support Minix fs v2 (fsck_minix/mkfs_minix)" default y - depends on BB_CONFIG_FSCK_MINIX || BB_CONFIG_MKFS_MINIX + 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. + 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 BB_CONFIG_GETOPT +config BUSYBOX_GETOPT bool "getopt" default n 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 + 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 + written by others, this utility may be for you. Most people will wisely leave this disabled. -config BB_CONFIG_HEXDUMP +config BUSYBOX_HEXDUMP bool "hexdump" default n 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 BB_CONFIG_FEATURE_HEXDUMP_REVERSE +config BUSYBOX_FEATURE_HEXDUMP_REVERSE bool "Support -R, reverse of 'hexdump -Cv'" default n - depends on BB_CONFIG_HEXDUMP + 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. -config BB_CONFIG_HD +config BUSYBOX_HD bool "hd" default n - select BB_CONFIG_HEXDUMP + select BUSYBOX_HEXDUMP help hd is an alias to hexdump -C. -config BB_CONFIG_HWCLOCK +config BUSYBOX_HWCLOCK bool "hwclock" default n help The hwclock utility is used to read and set the hardware clock - on a system. This is primarily used to set the current time on + 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 BB_CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS +config BUSYBOX_FEATURE_HWCLOCK_LONG_OPTIONS bool "Support long options (--hctosys,...)" default n - depends on BB_CONFIG_HWCLOCK && BB_CONFIG_GETOPT_LONG + depends on BUSYBOX_HWCLOCK && BUSYBOX_GETOPT_LONG help - By default, the hwclock utility only uses short options. If you + 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 BB_CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS +config BUSYBOX_FEATURE_HWCLOCK_ADJTIME_FHS bool "Use FHS /var/lib/hwclock/adjtime" default y - depends on BB_CONFIG_HWCLOCK + 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 + at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish to use the FHS behavior, answer Y here, otherwise answer N for the classic /etc/adjtime path. - http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO + pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO -config BB_CONFIG_IPCRM +config BUSYBOX_IPCRM bool "ipcrm" default n - select BB_CONFIG_FEATURE_SUID + select BUSYBOX_FEATURE_SUID help The ipcrm utility allows the removal of System V interprocess communication (IPC) objects and the associated data structures from the system. -config BB_CONFIG_IPCS +config BUSYBOX_IPCS bool "ipcs" default n - select BB_CONFIG_FEATURE_SUID + select BUSYBOX_FEATURE_SUID help The ipcs utility is used to provide information on the currently allocated System V interprocess (IPC) objects in the system. -config BB_CONFIG_LOSETUP +config BUSYBOX_LOSETUP bool "losetup" default n 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 + file or block device, and to query the status of a loop device. This version does not currently support enabling data encryption. -config BB_CONFIG_MDEV +config BUSYBOX_MDEV bool "mdev" default n help @@ -303,39 +310,47 @@ config BB_CONFIG_MDEV For more information, please see docs/mdev.txt -config BB_CONFIG_FEATURE_MDEV_CONF +config BUSYBOX_FEATURE_MDEV_CONF bool "Support /etc/mdev.conf" default n - depends on BB_CONFIG_MDEV + 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 BB_CONFIG_FEATURE_MDEV_RENAME +config BUSYBOX_FEATURE_MDEV_RENAME bool "Support subdirs/symlinks" default n - depends on BB_CONFIG_FEATURE_MDEV_CONF + depends on BUSYBOX_FEATURE_MDEV_CONF help Add support for renaming devices and creating symlinks. For more information, please see docs/mdev.txt -config BB_CONFIG_FEATURE_MDEV_EXEC +config BUSYBOX_FEATURE_MDEV_RENAME_REGEXP + bool "Support regular expressions substitutions when renaming device" + default n + 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 n - depends on BB_CONFIG_FEATURE_MDEV_CONF + 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 BB_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE +config BUSYBOX_FEATURE_MDEV_LOAD_FIRMWARE bool "Support loading of firmwares" default n - depends on BB_CONFIG_MDEV + depends on BUSYBOX_MDEV help Some devices need to load firmware before they can be usable. @@ -343,88 +358,86 @@ config BB_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE /lib/firmware/ and if it exists, send it to the kernel for loading into the hardware. -config BB_CONFIG_MKSWAP +config BUSYBOX_MKSWAP bool "mkswap" default n 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 + 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 + 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 BB_CONFIG_FEATURE_MKSWAP_V0 +config BUSYBOX_FEATURE_MKSWAP_V0 bool "Version 0 support" default n - depends on BB_CONFIG_MKSWAP + depends on BUSYBOX_MKSWAP # depends on MKSWAP && DEPRECATED help Enable support for the old v0 style. If your kernel is older than 2.1.117, then v0 support is the only option. -config BB_CONFIG_MORE +config BUSYBOX_MORE bool "more" default n 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 + 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 + 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 BB_CONFIG_FEATURE_USE_TERMIOS +config BUSYBOX_FEATURE_USE_TERMIOS bool "Use termios to manipulate the screen" default y - depends on BB_CONFIG_MORE || BB_CONFIG_TOP + depends on BUSYBOX_MORE || BUSYBOX_TOP help This option allows utilities such as 'more' and 'top' to determine - the size of the screen. If you leave this disabled, your utilities + the size of the screen. If you leave this disabled, your utilities that display things on the screen will be especially primitive and will be unable to determine the current screen size, and will be unable to move the cursor. -config BB_CONFIG_VOLUMEID - bool "Routines for detecting label and uuid on common filesystems" +config BUSYBOX_VOLUMEID + bool #No description makes it a hidden option default n - help - TODO -config BB_CONFIG_FEATURE_VOLUMEID_EXT +config BUSYBOX_FEATURE_VOLUMEID_EXT bool "Ext filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_REISERFS +config BUSYBOX_FEATURE_VOLUMEID_REISERFS bool "Reiser filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_FAT +config BUSYBOX_FEATURE_VOLUMEID_FAT bool "fat filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_HFS +config BUSYBOX_FEATURE_VOLUMEID_HFS bool "hfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_JFS +config BUSYBOX_FEATURE_VOLUMEID_JFS bool "jfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO @@ -435,45 +448,45 @@ config BB_CONFIG_FEATURE_VOLUMEID_JFS ### help ### TODO -config BB_CONFIG_FEATURE_VOLUMEID_XFS +config BUSYBOX_FEATURE_VOLUMEID_XFS bool "xfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_NTFS +config BUSYBOX_FEATURE_VOLUMEID_NTFS bool "ntfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_ISO9660 +config BUSYBOX_FEATURE_VOLUMEID_ISO9660 bool "iso9660 filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_UDF +config BUSYBOX_FEATURE_VOLUMEID_UDF bool "udf filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_LUKS +config BUSYBOX_FEATURE_VOLUMEID_LUKS bool "luks filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_LINUXSWAP +config BUSYBOX_FEATURE_VOLUMEID_LINUXSWAP bool "linux swap filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO @@ -484,10 +497,10 @@ config BB_CONFIG_FEATURE_VOLUMEID_LINUXSWAP ### help ### TODO -config BB_CONFIG_FEATURE_VOLUMEID_CRAMFS +config BUSYBOX_FEATURE_VOLUMEID_CRAMFS bool "cramfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO @@ -498,17 +511,17 @@ config BB_CONFIG_FEATURE_VOLUMEID_CRAMFS ### help ### TODO -config BB_CONFIG_FEATURE_VOLUMEID_ROMFS +config BUSYBOX_FEATURE_VOLUMEID_ROMFS bool "romfs filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_FEATURE_VOLUMEID_SYSV +config BUSYBOX_FEATURE_VOLUMEID_SYSV bool "sysv filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO @@ -526,7 +539,7 @@ config BB_CONFIG_FEATURE_VOLUMEID_SYSV ### depends on VOLUMEID ### help ### TODO -### +### ### config FEATURE_VOLUMEID_MSDOS ### bool "msdos filesystem" ### default n @@ -534,10 +547,10 @@ config BB_CONFIG_FEATURE_VOLUMEID_SYSV ### help ### TODO -config BB_CONFIG_FEATURE_VOLUMEID_OCFS2 +config BUSYBOX_FEATURE_VOLUMEID_OCFS2 bool "ocfs2 filesystem" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO @@ -590,44 +603,44 @@ config BB_CONFIG_FEATURE_VOLUMEID_OCFS2 ### help ### TODO -config BB_CONFIG_FEATURE_VOLUMEID_LINUXRAID +config BUSYBOX_FEATURE_VOLUMEID_LINUXRAID bool "linuxraid" default n - depends on BB_CONFIG_VOLUMEID + depends on BUSYBOX_VOLUMEID help TODO -config BB_CONFIG_MOUNT +config BUSYBOX_MOUNT bool "mount" default n help All files and filesystems in Unix are arranged into one big directory - tree. The 'mount' utility is used to graft a filesystem onto a - particular part of the tree. A filesystem can either live on a block + 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 + NFS filesystems. Most people using BusyBox will also want to enable the 'mount' utility. -config BB_CONFIG_FEATURE_MOUNT_FAKE +config BUSYBOX_FEATURE_MOUNT_FAKE bool "Support option -f" default n - depends on BB_CONFIG_MOUNT + depends on BUSYBOX_MOUNT help Enable support for faking a file system mount. -config BB_CONFIG_FEATURE_MOUNT_VERBOSE +config BUSYBOX_FEATURE_MOUNT_VERBOSE bool "Support option -v" default n - depends on BB_CONFIG_MOUNT + 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. -config BB_CONFIG_FEATURE_MOUNT_HELPERS +config BUSYBOX_FEATURE_MOUNT_HELPERS bool "Support mount helpers" default n - depends on BB_CONFIG_MOUNT + 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 @@ -636,61 +649,61 @@ config BB_CONFIG_FEATURE_MOUNT_HELPERS "sometype [-o opts] fs /mnt" if simple mount syscall fails. The idea is to use such virtual filesystems in /etc/fstab. -config BB_CONFIG_FEATURE_MOUNT_LABEL +config BUSYBOX_FEATURE_MOUNT_LABEL bool "Support specifiying devices by label or UUID" default n - depends on BB_CONFIG_MOUNT - select BB_CONFIG_VOLUMEID + 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 findfs. + name. This feature utilizes the same functionality as blkid/findfs. -config BB_CONFIG_FEATURE_MOUNT_NFS +config BUSYBOX_FEATURE_MOUNT_NFS bool "Support mounting NFS file systems" default n - depends on BB_CONFIG_MOUNT - select BB_CONFIG_FEATURE_HAVE_RPC - select BB_CONFIG_FEATURE_SYSLOG + depends on BUSYBOX_MOUNT + select BUSYBOX_FEATURE_HAVE_RPC + select BUSYBOX_FEATURE_SYSLOG help Enable mounting of NFS file systems. -config BB_CONFIG_FEATURE_MOUNT_CIFS +config BUSYBOX_FEATURE_MOUNT_CIFS bool "Support mounting CIFS/SMB file systems" default n - depends on BB_CONFIG_MOUNT + depends on BUSYBOX_MOUNT help Enable support for samba mounts. -config BB_CONFIG_FEATURE_MOUNT_FLAGS - depends on BB_CONFIG_MOUNT +config BUSYBOX_FEATURE_MOUNT_FLAGS + depends on BUSYBOX_MOUNT bool "Support lots of -o flags in mount" default y help - Without this, mount only supports ro/rw/remount. With this, it + 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 BB_CONFIG_FEATURE_MOUNT_FSTAB - depends on BB_CONFIG_MOUNT +config BUSYBOX_FEATURE_MOUNT_FSTAB + depends on BUSYBOX_MOUNT bool "Support /etc/fstab and -a" default y help Support mount all and looking for files in /etc/fstab. -config BB_CONFIG_PIVOT_ROOT +config BUSYBOX_PIVOT_ROOT bool "pivot_root" default n 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 + 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 + Note: This is for initrd in linux 2.4. Under initramfs (introduced in linux 2.6) use switch_root instead. -config BB_CONFIG_RDATE +config BUSYBOX_RDATE bool "rdate" default n help @@ -699,102 +712,122 @@ config BB_CONFIG_RDATE the RFC868 protocol, which is built into the inetd daemon on most systems. -config BB_CONFIG_READPROFILE +config BUSYBOX_RDEV + bool "rdev" + default n + help + Print the device node associated with the filesystem mounted at '/'. + +config BUSYBOX_READPROFILE bool "readprofile" default n help This allows you to parse /proc/profile for basic profiling. -config BB_CONFIG_RTCWAKE +config BUSYBOX_RTCWAKE bool "rtcwake" default n help Enter a system sleep state until specified wakeup time. -config BB_CONFIG_SETARCH +config BUSYBOX_SCRIPT + bool "script" + default n + help + The script makes typescript of terminal session. + +config BUSYBOX_SETARCH bool "setarch" default n help The linux32 utility is used to create a 32bit environment for the - specified program (usually a shell). It only makes sense to have + 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 BB_CONFIG_SWAPONOFF +config BUSYBOX_SWAPONOFF bool "swaponoff" default n help This option enables both the 'swapon' and the 'swapoff' utilities. Once you have created some swap space using 'mkswap', you also need - to enable your swap space with the 'swapon' utility. The 'swapoff' + 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 + space. If you are not using any swap space, you can leave this option disabled. -config BB_CONFIG_SWITCH_ROOT +config BUSYBOX_FEATURE_SWAPON_PRI + bool "Support priority option -p" + default n + depends on BUSYBOX_SWAPONOFF + help + Enable support for setting swap device priority in swapon. + +config BUSYBOX_SWITCH_ROOT bool "switch_root" default n 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.) + 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, + (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. + list of active mount points. That's why. -config BB_CONFIG_UMOUNT +config BUSYBOX_UMOUNT bool "umount" default n 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'. + 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 BB_CONFIG_FEATURE_UMOUNT_ALL +config BUSYBOX_FEATURE_UMOUNT_ALL bool "Support option -a" default n - depends on BB_CONFIG_UMOUNT + depends on BUSYBOX_UMOUNT help Support -a option to unmount all currently mounted filesystems. comment "Common options for mount/umount" - depends on BB_CONFIG_MOUNT || BB_CONFIG_UMOUNT + depends on BUSYBOX_MOUNT || BUSYBOX_UMOUNT -config BB_CONFIG_FEATURE_MOUNT_LOOP +config BUSYBOX_FEATURE_MOUNT_LOOP bool "Support loopback mounts" default n - depends on BB_CONFIG_MOUNT || BB_CONFIG_UMOUNT + 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. + 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 BB_CONFIG_FEATURE_MTAB_SUPPORT +config BUSYBOX_FEATURE_MTAB_SUPPORT bool "Support for the old /etc/mtab file" default n - depends on BB_CONFIG_MOUNT || BB_CONFIG_UMOUNT - select BB_CONFIG_FEATURE_MOUNT_FAKE + 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 + 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 + 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 @@ -804,7 +837,7 @@ config BB_CONFIG_FEATURE_MTAB_SUPPORT features like separate per-process filesystem namespaces, requires that your /etc directory be writeable, 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.) + 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. |