2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
6 menu "Linux System Utilities"
8 config BUSYBOX_CONFIG_BLOCKDEV
12 Performs some ioctls with block devices.
13 config BUSYBOX_CONFIG_REV
17 Reverse lines of a file or files.
19 config BUSYBOX_CONFIG_ACPID
22 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
24 acpid listens to ACPI events coming either in textual form from
25 /proc/acpi/event (though it is marked deprecated it is still widely
26 used and _is_ a standard) or in binary form from specified evdevs
27 (just use /dev/input/event*).
29 It parses the event to retrieve ACTION and a possible PARAMETER.
30 It then spawns /etc/acpi/<ACTION>[/<PARAMETER>] either via run-parts
31 (if the resulting path is a directory) or directly as an executable.
33 N.B. acpid relies on run-parts so have the latter installed.
35 config BUSYBOX_CONFIG_FEATURE_ACPID_COMPAT
36 bool "Accept and ignore redundant options"
38 depends on BUSYBOX_CONFIG_ACPID
40 Accept and ignore compatibility options -g -m -s -S -v.
42 config BUSYBOX_CONFIG_BLKID
45 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
46 select BUSYBOX_CONFIG_VOLUMEID
48 Lists labels and UUIDs of all filesystems.
50 With all submodules selected, it will add ~8k to busybox.
52 config BUSYBOX_CONFIG_DMESG
55 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
57 dmesg is used to examine or control the kernel ring buffer. When the
58 Linux kernel prints messages to the system log, they are stored in
59 the kernel ring buffer. You can use dmesg to print the kernel's ring
60 buffer, clear the kernel ring buffer, change the size of the kernel
61 ring buffer, and change the priority level at which kernel messages
62 are also logged to the system console. Enable this option if you
63 wish to enable the 'dmesg' utility.
65 config BUSYBOX_CONFIG_FEATURE_DMESG_PRETTY
66 bool "Pretty dmesg output"
68 depends on BUSYBOX_CONFIG_DMESG
70 If you wish to scrub the syslog level from the output, say 'Y' here.
71 The syslog level is a string prefixed to every line with the form
74 With this option you will see:
76 Linux version 2.6.17.4 .....
77 BIOS-provided physical RAM map:
78 BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
80 Without this option you will see:
82 <5>Linux version 2.6.17.4 .....
83 <6>BIOS-provided physical RAM map:
84 <6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
86 config BUSYBOX_CONFIG_FBSET
89 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
91 fbset is used to show or change the settings of a Linux frame buffer
92 device. The frame buffer device provides a simple and unique
93 interface to access a graphics display. Enable this option
94 if you wish to enable the 'fbset' utility.
96 config BUSYBOX_CONFIG_FEATURE_FBSET_FANCY
97 bool "Turn on extra fbset options"
99 depends on BUSYBOX_CONFIG_FBSET
101 This option enables extended fbset options, allowing one to set the
102 framebuffer size, color depth, etc. interface to access a graphics
103 display. Enable this option if you wish to enable extended fbset
106 config BUSYBOX_CONFIG_FEATURE_FBSET_READMODE
107 bool "Turn on fbset readmode support"
109 depends on BUSYBOX_CONFIG_FBSET
111 This option allows fbset to read the video mode database stored by
112 default n /etc/fb.modes, which can be used to set frame buffer
113 device to pre-defined video modes.
115 config BUSYBOX_CONFIG_FDFLUSH
118 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
120 fdflush is only needed when changing media on slightly-broken
121 removable media drives. It is used to make Linux believe that a
122 hardware disk-change switch has been actuated, which causes Linux to
123 forget anything it has cached from the previous media. If you have
124 such a slightly-broken drive, you will need to run fdflush every time
125 you change a disk. Most people have working hardware and can safely
128 config BUSYBOX_CONFIG_FDFORMAT
131 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
133 fdformat is used to low-level format a floppy disk.
135 config BUSYBOX_CONFIG_FDISK
138 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
140 The fdisk utility is used to divide hard disks into one or more
141 logical disks, which are generally called partitions. This utility
142 can be used to list and edit the set of partitions or BSD style
143 'disk slices' that are defined on a hard drive.
145 config BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
146 bool "Support over 4GB disks"
148 depends on BUSYBOX_CONFIG_FDISK
150 Enable this option to support large disks > 4GB.
152 config BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
155 depends on BUSYBOX_CONFIG_FDISK
157 Enabling this option allows you to create or change a partition table
158 and write those changes out to disk. If you leave this option
159 disabled, you will only be able to view the partition table.
161 config BUSYBOX_CONFIG_FEATURE_AIX_LABEL
162 bool "Support AIX disklabels"
164 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
166 Enabling this option allows you to create or change AIX disklabels.
167 Most people can safely leave this option disabled.
169 config BUSYBOX_CONFIG_FEATURE_SGI_LABEL
170 bool "Support SGI disklabels"
172 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
174 Enabling this option allows you to create or change SGI disklabels.
175 Most people can safely leave this option disabled.
177 config BUSYBOX_CONFIG_FEATURE_SUN_LABEL
178 bool "Support SUN disklabels"
180 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
182 Enabling this option allows you to create or change SUN disklabels.
183 Most people can safely leave this option disabled.
185 config BUSYBOX_CONFIG_FEATURE_OSF_LABEL
186 bool "Support BSD disklabels"
188 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
190 Enabling this option allows you to create or change BSD disklabels
191 and define and edit BSD disk slices.
193 config BUSYBOX_CONFIG_FEATURE_GPT_LABEL
194 bool "Support GPT disklabels"
196 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
198 Enabling this option allows you to view GUID Partition Table
201 config BUSYBOX_CONFIG_FEATURE_FDISK_ADVANCED
202 bool "Support expert mode"
204 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
206 Enabling this option allows you to do terribly unsafe things like
207 define arbitrary drive geometry, move the beginning of data in a
208 partition, and similarly evil things. Unless you have a very good
209 reason you would be wise to leave this disabled.
211 config BUSYBOX_CONFIG_FINDFS
214 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
215 select BUSYBOX_CONFIG_VOLUMEID
217 Prints the name of a filesystem with given label or UUID.
219 With all submodules selected, it will add ~8k to busybox.
221 config BUSYBOX_CONFIG_FLOCK
225 Manage locks from shell scripts
227 config BUSYBOX_CONFIG_FREERAMDISK
230 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
232 Linux allows you to create ramdisks. This utility allows you to
233 delete them and completely free all memory that was used for the
234 ramdisk. For example, if you boot Linux into a ramdisk and later
235 pivot_root, you may want to free the memory that is allocated to the
236 ramdisk. If you have no use for freeing memory from a ramdisk, leave
239 config BUSYBOX_CONFIG_FSCK_MINIX
243 The minix filesystem is a nice, small, compact, read-write filesystem
244 with little overhead. It is not a journaling filesystem however and
245 can experience corruption if it is not properly unmounted or if the
246 power goes off in the middle of a write. This utility allows you to
247 check for and attempt to repair any corruption that occurs to a minix
250 config BUSYBOX_CONFIG_MKFS_EXT2
253 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
255 Utility to create EXT2 filesystems.
257 config BUSYBOX_CONFIG_MKFS_MINIX
260 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
262 The minix filesystem is a nice, small, compact, read-write filesystem
263 with little overhead. If you wish to be able to create minix
264 filesystems this utility will do the job for you.
266 config BUSYBOX_CONFIG_FEATURE_MINIX2
267 bool "Support Minix fs v2 (fsck_minix/mkfs_minix)"
269 depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
271 If you wish to be able to create version 2 minix filesystems, enable
272 this. If you enabled 'mkfs_minix' then you almost certainly want to
273 be using the version 2 filesystem support.
275 config BUSYBOX_CONFIG_MKFS_REISER
278 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
280 Utility to create ReiserFS filesystems.
281 Note: this applet needs a lot of testing and polishing.
283 config BUSYBOX_CONFIG_MKFS_VFAT
286 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
288 Utility to create FAT32 filesystems.
290 config BUSYBOX_CONFIG_GETOPT
294 The getopt utility is used to break up (parse) options in command
295 lines to make it easy to write complex shell scripts that also check
296 for legal (and illegal) options. If you want to write horribly
297 complex shell scripts, or use some horribly complex shell script
298 written by others, this utility may be for you. Most people will
299 wisely leave this disabled.
301 config BUSYBOX_CONFIG_FEATURE_GETOPT_LONG
302 bool "Support option -l"
303 default n if BUSYBOX_CONFIG_LONG_OPTS
304 depends on BUSYBOX_CONFIG_GETOPT
306 Enable support for long options (option -l).
308 config BUSYBOX_CONFIG_HEXDUMP
312 The hexdump utility is used to display binary data in a readable
313 way that is comparable to the output from most hex editors.
315 config BUSYBOX_CONFIG_FEATURE_HEXDUMP_REVERSE
316 bool "Support -R, reverse of 'hexdump -Cv'"
318 depends on BUSYBOX_CONFIG_HEXDUMP
320 The hexdump utility is used to display binary data in an ascii
321 readable way. This option creates binary data from an ascii input.
322 NB: this option is non-standard. It's unwise to use it in scripts
323 aimed to be portable.
325 config BUSYBOX_CONFIG_HD
328 depends on BUSYBOX_CONFIG_HEXDUMP
330 hd is an alias to hexdump -C.
332 config BUSYBOX_CONFIG_HWCLOCK
335 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
337 The hwclock utility is used to read and set the hardware clock
338 on a system. This is primarily used to set the current time on
339 shutdown in the hardware clock, so the hardware will keep the
340 correct time when Linux is _not_ running.
342 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS
343 bool "Support long options (--hctosys,...)"
345 depends on BUSYBOX_CONFIG_HWCLOCK && BUSYBOX_CONFIG_LONG_OPTS
347 By default, the hwclock utility only uses short options. If you
348 are overly fond of its long options, such as --hctosys, --utc, etc)
349 then enable this option.
351 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS
352 bool "Use FHS /var/lib/hwclock/adjtime"
354 depends on BUSYBOX_CONFIG_HWCLOCK
356 Starting with FHS 2.3, the adjtime state file is supposed to exist
357 at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish
358 to use the FHS behavior, answer Y here, otherwise answer N for the
359 classic /etc/adjtime path.
361 pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO
363 config BUSYBOX_CONFIG_IPCRM
367 The ipcrm utility allows the removal of System V interprocess
368 communication (IPC) objects and the associated data structures
371 config BUSYBOX_CONFIG_IPCS
374 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
376 The ipcs utility is used to provide information on the currently
377 allocated System V interprocess (IPC) objects in the system.
379 config BUSYBOX_CONFIG_LOSETUP
382 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
384 losetup is used to associate or detach a loop device with a regular
385 file or block device, and to query the status of a loop device. This
386 version does not currently support enabling data encryption.
388 config BUSYBOX_CONFIG_LSPCI
392 lspci is a utility for displaying information about PCI buses in the
393 system and devices connected to them.
395 This version uses sysfs (/sys/bus/pci/devices) only.
397 config BUSYBOX_CONFIG_LSUSB
401 lsusb is a utility for displaying information about USB buses in the
402 system and devices connected to them.
404 This version uses sysfs (/sys/bus/usb/devices) only.
406 config BUSYBOX_CONFIG_MDEV
409 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
411 mdev is a mini-udev implementation for dynamically creating device
412 nodes in the /dev directory.
414 For more information, please see docs/mdev.txt
416 config BUSYBOX_CONFIG_FEATURE_MDEV_CONF
417 bool "Support /etc/mdev.conf"
419 depends on BUSYBOX_CONFIG_MDEV
421 Add support for the mdev config file to control ownership and
422 permissions of the device nodes.
424 For more information, please see docs/mdev.txt
426 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
427 bool "Support subdirs/symlinks"
429 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
431 Add support for renaming devices and creating symlinks.
433 For more information, please see docs/mdev.txt
435 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME_REGEXP
436 bool "Support regular expressions substitutions when renaming device"
438 depends on BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
440 Add support for regular expressions substitutions when renaming
443 config BUSYBOX_CONFIG_FEATURE_MDEV_EXEC
444 bool "Support command execution at device addition/removal"
446 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
448 This adds support for an optional field to /etc/mdev.conf for
449 executing commands when devices are created/removed.
451 For more information, please see docs/mdev.txt
453 config BUSYBOX_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE
454 bool "Support loading of firmwares"
456 depends on BUSYBOX_CONFIG_MDEV
458 Some devices need to load firmware before they can be usable.
460 These devices will request userspace look up the files in
461 /lib/firmware/ and if it exists, send it to the kernel for
462 loading into the hardware.
464 config BUSYBOX_CONFIG_MKSWAP
468 The mkswap utility is used to configure a file or disk partition as
469 Linux swap space. This allows Linux to use the entire file or
470 partition as if it were additional RAM, which can greatly increase
471 the capability of low-memory machines. This additional memory is
472 much slower than real RAM, but can be very helpful at preventing your
473 applications being killed by the Linux out of memory (OOM) killer.
474 Once you have created swap space using 'mkswap' you need to enable
475 the swap space using the 'swapon' utility.
477 config BUSYBOX_CONFIG_FEATURE_MKSWAP_UUID
480 depends on BUSYBOX_CONFIG_MKSWAP
482 Generate swap spaces with universally unique identifiers.
484 config BUSYBOX_CONFIG_MORE
488 more is a simple utility which allows you to read text one screen
489 sized page at a time. If you want to read text that is larger than
490 the screen, and you are using anything faster than a 300 baud modem,
491 you will probably find this utility very helpful. If you don't have
492 any need to reading text files, you can leave this disabled.
494 config BUSYBOX_CONFIG_MOUNT
497 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
499 All files and filesystems in Unix are arranged into one big directory
500 tree. The 'mount' utility is used to graft a filesystem onto a
501 particular part of the tree. A filesystem can either live on a block
502 device, or it can be accessible over the network, as is the case with
503 NFS filesystems. Most people using BusyBox will also want to enable
506 config BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
507 bool "Support option -f"
509 depends on BUSYBOX_CONFIG_MOUNT
511 Enable support for faking a file system mount.
513 config BUSYBOX_CONFIG_FEATURE_MOUNT_VERBOSE
514 bool "Support option -v"
516 depends on BUSYBOX_CONFIG_MOUNT
518 Enable multi-level -v[vv...] verbose messages. Useful if you
519 debug mount problems and want to see what is exactly passed
522 config BUSYBOX_CONFIG_FEATURE_MOUNT_HELPERS
523 bool "Support mount helpers"
525 depends on BUSYBOX_CONFIG_MOUNT
527 Enable mounting of virtual file systems via external helpers.
528 E.g. "mount obexfs#-b00.11.22.33.44.55 /mnt" will in effect call
529 "obexfs -b00.11.22.33.44.55 /mnt"
530 Also "mount -t sometype [-o opts] fs /mnt" will try
531 "sometype [-o opts] fs /mnt" if simple mount syscall fails.
532 The idea is to use such virtual filesystems in /etc/fstab.
534 config BUSYBOX_CONFIG_FEATURE_MOUNT_LABEL
535 bool "Support specifying devices by label or UUID"
537 depends on BUSYBOX_CONFIG_MOUNT
538 select BUSYBOX_CONFIG_VOLUMEID
540 This allows for specifying a device by label or uuid, rather than by
541 name. This feature utilizes the same functionality as blkid/findfs.
542 This also enables label or uuid support for swapon.
544 config BUSYBOX_CONFIG_FEATURE_MOUNT_NFS
545 bool "Support mounting NFS file systems"
547 depends on BUSYBOX_CONFIG_MOUNT
548 select BUSYBOX_CONFIG_FEATURE_HAVE_RPC
549 select BUSYBOX_CONFIG_FEATURE_SYSLOG
551 Enable mounting of NFS file systems.
553 config BUSYBOX_CONFIG_FEATURE_MOUNT_CIFS
554 bool "Support mounting CIFS/SMB file systems"
556 depends on BUSYBOX_CONFIG_MOUNT
558 Enable support for samba mounts.
560 config BUSYBOX_CONFIG_FEATURE_MOUNT_FLAGS
561 depends on BUSYBOX_CONFIG_MOUNT
562 bool "Support lots of -o flags in mount"
565 Without this, mount only supports ro/rw/remount. With this, it
566 supports nosuid, suid, dev, nodev, exec, noexec, sync, async, atime,
567 noatime, diratime, nodiratime, loud, bind, move, shared, slave,
568 private, unbindable, rshared, rslave, rprivate, and runbindable.
570 config BUSYBOX_CONFIG_FEATURE_MOUNT_FSTAB
571 depends on BUSYBOX_CONFIG_MOUNT
572 bool "Support /etc/fstab and -a"
575 Support mount all and looking for files in /etc/fstab.
577 config BUSYBOX_CONFIG_PIVOT_ROOT
580 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
582 The pivot_root utility swaps the mount points for the root filesystem
583 with some other mounted filesystem. This allows you to do all sorts
584 of wild and crazy things with your Linux system and is far more
585 powerful than 'chroot'.
587 Note: This is for initrd in linux 2.4. Under initramfs (introduced
588 in linux 2.6) use switch_root instead.
590 config BUSYBOX_CONFIG_RDATE
594 The rdate utility allows you to synchronize the date and time of your
595 system clock with the date and time of a remote networked system using
596 the RFC868 protocol, which is built into the inetd daemon on most
599 config BUSYBOX_CONFIG_RDEV
603 Print the device node associated with the filesystem mounted at '/'.
605 config BUSYBOX_CONFIG_READPROFILE
609 This allows you to parse /proc/profile for basic profiling.
611 config BUSYBOX_CONFIG_RTCWAKE
614 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
616 Enter a system sleep state until specified wakeup time.
618 config BUSYBOX_CONFIG_SCRIPT
622 The script makes typescript of terminal session.
624 config BUSYBOX_CONFIG_SCRIPTREPLAY
628 This program replays a typescript, using timing information
631 config BUSYBOX_CONFIG_SETARCH
634 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
636 The linux32 utility is used to create a 32bit environment for the
637 specified program (usually a shell). It only makes sense to have
638 this util on a system that supports both 64bit and 32bit userland
639 (like amd64/x86, ppc64/ppc, sparc64/sparc, etc...).
641 config BUSYBOX_CONFIG_SWAPONOFF
644 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
646 This option enables both the 'swapon' and the 'swapoff' utilities.
647 Once you have created some swap space using 'mkswap', you also need
648 to enable your swap space with the 'swapon' utility. The 'swapoff'
649 utility is used, typically at system shutdown, to disable any swap
650 space. If you are not using any swap space, you can leave this
653 config BUSYBOX_CONFIG_FEATURE_SWAPON_PRI
654 bool "Support priority option -p"
656 depends on BUSYBOX_CONFIG_SWAPONOFF
658 Enable support for setting swap device priority in swapon.
660 config BUSYBOX_CONFIG_SWITCH_ROOT
663 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
665 The switch_root utility is used from initramfs to select a new
666 root device. Under initramfs, you have to use this instead of
667 pivot_root. (Stop reading here if you don't care why.)
669 Booting with initramfs extracts a gzipped cpio archive into rootfs
670 (which is a variant of ramfs/tmpfs). Because rootfs can't be moved
671 or unmounted*, pivot_root will not work from initramfs. Instead,
672 switch_root deletes everything out of rootfs (including itself),
673 does a mount --move that overmounts rootfs with the new root, and
674 then execs the specified init program.
676 * Because the Linux kernel uses rootfs internally as the starting
677 and ending point for searching through the kernel's doubly linked
678 list of active mount points. That's why.
680 config BUSYBOX_CONFIG_UMOUNT
683 depends on BUSYBOX_CONFIG_PLATFORM_LINUX
685 When you want to remove a mounted filesystem from its current mount
686 point, for example when you are shutting down the system, the
687 'umount' utility is the tool to use. If you enabled the 'mount'
688 utility, you almost certainly also want to enable 'umount'.
690 config BUSYBOX_CONFIG_FEATURE_UMOUNT_ALL
691 bool "Support option -a"
693 depends on BUSYBOX_CONFIG_UMOUNT
695 Support -a option to unmount all currently mounted filesystems.
697 comment "Common options for mount/umount"
698 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
700 config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
701 bool "Support loopback mounts"
703 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
705 Enabling this feature allows automatic mounting of files (containing
706 filesystem images) via the linux kernel's loopback devices.
707 The mount command will detect you are trying to mount a file instead
708 of a block device, and transparently associate the file with a
709 loopback device. The umount command will also free that loopback
712 You can still use the 'losetup' utility (to manually associate files
713 with loop devices) if you need to do something advanced, such as
714 specify an offset or cryptographic options to the loopback device.
715 (If you don't want umount to free the loop device, use "umount -D".)
717 config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP_CREATE
718 bool "Create new loopback devices if needed"
720 depends on BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
722 Linux kernels >= 2.6.24 support unlimited loopback devices. They are
723 allocated for use when trying to use a loop device. The loop device
726 This feature lets mount to try to create next /dev/loopN device
727 if it does not find a free one.
729 config BUSYBOX_CONFIG_FEATURE_MTAB_SUPPORT
730 bool "Support for the old /etc/mtab file"
732 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
733 select BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
735 Historically, Unix systems kept track of the currently mounted
736 partitions in the file "/etc/mtab". These days, the kernel exports
737 the list of currently mounted partitions in "/proc/mounts", rendering
738 the old mtab file obsolete. (In modern systems, /etc/mtab should be
739 a symlink to /proc/mounts.)
741 The only reason to have mount maintain an /etc/mtab file itself is if
742 your stripped-down embedded system does not have a /proc directory.
743 If you must use this, keep in mind it's inherently brittle (for
744 example a mount under chroot won't update it), can't handle modern
745 features like separate per-process filesystem namespaces, requires
746 that your /etc directory be writable, tends to get easily confused
747 by --bind or --move mounts, won't update if you rename a directory
748 that contains a mount point, and so on. (In brief: avoid.)
750 About the only reason to use this is if you've removed /proc from
753 config BUSYBOX_CONFIG_VOLUMEID
754 bool #No description makes it a hidden option
757 menu "Filesystem/Volume identification"
758 depends on BUSYBOX_CONFIG_VOLUMEID
760 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_EXT
761 bool "Ext filesystem"
763 depends on BUSYBOX_CONFIG_VOLUMEID
767 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_BTRFS
768 bool "btrfs filesystem"
770 depends on BUSYBOX_CONFIG_VOLUMEID
774 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_REISERFS
775 bool "Reiser filesystem"
777 depends on BUSYBOX_CONFIG_VOLUMEID
781 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_FAT
782 bool "fat filesystem"
784 depends on BUSYBOX_CONFIG_VOLUMEID
788 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_HFS
789 bool "hfs filesystem"
791 depends on BUSYBOX_CONFIG_VOLUMEID
795 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_JFS
796 bool "jfs filesystem"
798 depends on BUSYBOX_CONFIG_VOLUMEID
802 ### config FEATURE_VOLUMEID_UFS
803 ### bool "ufs filesystem"
805 ### depends on VOLUMEID
809 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_XFS
810 bool "xfs filesystem"
812 depends on BUSYBOX_CONFIG_VOLUMEID
816 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_NTFS
817 bool "ntfs filesystem"
819 depends on BUSYBOX_CONFIG_VOLUMEID
823 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ISO9660
824 bool "iso9660 filesystem"
826 depends on BUSYBOX_CONFIG_VOLUMEID
830 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_UDF
831 bool "udf filesystem"
833 depends on BUSYBOX_CONFIG_VOLUMEID
837 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LUKS
838 bool "luks filesystem"
840 depends on BUSYBOX_CONFIG_VOLUMEID
844 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXSWAP
845 bool "linux swap filesystem"
847 depends on BUSYBOX_CONFIG_VOLUMEID
851 ### config FEATURE_VOLUMEID_LVM
854 ### depends on VOLUMEID
858 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_CRAMFS
859 bool "cramfs filesystem"
861 depends on BUSYBOX_CONFIG_VOLUMEID
865 ### config FEATURE_VOLUMEID_HPFS
866 ### bool "hpfs filesystem"
868 ### depends on VOLUMEID
872 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ROMFS
873 bool "romfs filesystem"
875 depends on BUSYBOX_CONFIG_VOLUMEID
879 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_SYSV
880 bool "sysv filesystem"
882 depends on BUSYBOX_CONFIG_VOLUMEID
886 ### config FEATURE_VOLUMEID_MINIX
887 ### bool "minix filesystem"
889 ### depends on VOLUMEID
893 ### These only detect partition tables - not used (yet?)
894 ### config FEATURE_VOLUMEID_MAC
895 ### bool "mac filesystem"
897 ### depends on VOLUMEID
901 ### config FEATURE_VOLUMEID_MSDOS
902 ### bool "msdos filesystem"
904 ### depends on VOLUMEID
908 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_OCFS2
909 bool "ocfs2 filesystem"
911 depends on BUSYBOX_CONFIG_VOLUMEID
915 ### config FEATURE_VOLUMEID_HIGHPOINTRAID
916 ### bool "highpoint raid"
918 ### depends on VOLUMEID
922 ### config FEATURE_VOLUMEID_ISWRAID
923 ### bool "intel raid"
925 ### depends on VOLUMEID
929 ### config FEATURE_VOLUMEID_LSIRAID
932 ### depends on VOLUMEID
936 ### config FEATURE_VOLUMEID_VIARAID
939 ### depends on VOLUMEID
943 ### config FEATURE_VOLUMEID_SILICONRAID
944 ### bool "silicon raid"
946 ### depends on VOLUMEID
950 ### config FEATURE_VOLUMEID_NVIDIARAID
951 ### bool "nvidia raid"
953 ### depends on VOLUMEID
957 ### config FEATURE_VOLUMEID_PROMISERAID
958 ### bool "promise raid"
960 ### depends on VOLUMEID
964 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXRAID
967 depends on BUSYBOX_CONFIG_VOLUMEID