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_REV
12 Reverse lines of a file or files.
14 config BUSYBOX_CONFIG_ACPID
18 acpid listens to ACPI events coming either in textual form from
19 /proc/acpi/event (though it is marked deprecated it is still widely
20 used and _is_ a standard) or in binary form from specified evdevs
21 (just use /dev/input/event*).
23 It parses the event to retrieve ACTION and a possible PARAMETER.
24 It then spawns /etc/acpi/<ACTION>[/<PARAMETER>] either via run-parts
25 (if the resulting path is a directory) or directly as an executable.
27 N.B. acpid relies on run-parts so have the latter installed.
29 config BUSYBOX_CONFIG_FEATURE_ACPID_COMPAT
30 bool "Accept and ignore redundant options"
32 depends on BUSYBOX_CONFIG_ACPID
34 Accept and ignore compatibility options -g -m -s -S -v.
36 config BUSYBOX_CONFIG_BLKID
39 select BUSYBOX_CONFIG_VOLUMEID
41 Lists labels and UUIDs of all filesystems.
43 With all submodules selected, it will add ~8k to busybox.
45 config BUSYBOX_CONFIG_DMESG
49 dmesg is used to examine or control the kernel ring buffer. When the
50 Linux kernel prints messages to the system log, they are stored in
51 the kernel ring buffer. You can use dmesg to print the kernel's ring
52 buffer, clear the kernel ring buffer, change the size of the kernel
53 ring buffer, and change the priority level at which kernel messages
54 are also logged to the system console. Enable this option if you
55 wish to enable the 'dmesg' utility.
57 config BUSYBOX_CONFIG_FEATURE_DMESG_PRETTY
58 bool "Pretty dmesg output"
60 depends on BUSYBOX_CONFIG_DMESG
62 If you wish to scrub the syslog level from the output, say 'Y' here.
63 The syslog level is a string prefixed to every line with the form
66 With this option you will see:
68 Linux version 2.6.17.4 .....
69 BIOS-provided physical RAM map:
70 BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
72 Without this option you will see:
74 <5>Linux version 2.6.17.4 .....
75 <6>BIOS-provided physical RAM map:
76 <6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
78 config BUSYBOX_CONFIG_FBSET
82 fbset is used to show or change the settings of a Linux frame buffer
83 device. The frame buffer device provides a simple and unique
84 interface to access a graphics display. Enable this option
85 if you wish to enable the 'fbset' utility.
87 config BUSYBOX_CONFIG_FEATURE_FBSET_FANCY
88 bool "Turn on extra fbset options"
90 depends on BUSYBOX_CONFIG_FBSET
92 This option enables extended fbset options, allowing one to set the
93 framebuffer size, color depth, etc. interface to access a graphics
94 display. Enable this option if you wish to enable extended fbset
97 config BUSYBOX_CONFIG_FEATURE_FBSET_READMODE
98 bool "Turn on fbset readmode support"
100 depends on BUSYBOX_CONFIG_FBSET
102 This option allows fbset to read the video mode database stored by
103 default n /etc/fb.modes, which can be used to set frame buffer
104 device to pre-defined video modes.
106 config BUSYBOX_CONFIG_FDFLUSH
110 fdflush is only needed when changing media on slightly-broken
111 removable media drives. It is used to make Linux believe that a
112 hardware disk-change switch has been actuated, which causes Linux to
113 forget anything it has cached from the previous media. If you have
114 such a slightly-broken drive, you will need to run fdflush every time
115 you change a disk. Most people have working hardware and can safely
118 config BUSYBOX_CONFIG_FDFORMAT
122 fdformat is used to low-level format a floppy disk.
124 config BUSYBOX_CONFIG_FDISK
128 The fdisk utility is used to divide hard disks into one or more
129 logical disks, which are generally called partitions. This utility
130 can be used to list and edit the set of partitions or BSD style
131 'disk slices' that are defined on a hard drive.
133 config BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
134 bool "Support over 4GB disks"
136 depends on BUSYBOX_CONFIG_FDISK
138 Enable this option to support large disks > 4GB.
140 config BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
143 depends on BUSYBOX_CONFIG_FDISK
145 Enabling this option allows you to create or change a partition table
146 and write those changes out to disk. If you leave this option
147 disabled, you will only be able to view the partition table.
149 config BUSYBOX_CONFIG_FEATURE_AIX_LABEL
150 bool "Support AIX disklabels"
152 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
154 Enabling this option allows you to create or change AIX disklabels.
155 Most people can safely leave this option disabled.
157 config BUSYBOX_CONFIG_FEATURE_SGI_LABEL
158 bool "Support SGI disklabels"
160 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
162 Enabling this option allows you to create or change SGI disklabels.
163 Most people can safely leave this option disabled.
165 config BUSYBOX_CONFIG_FEATURE_SUN_LABEL
166 bool "Support SUN disklabels"
168 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
170 Enabling this option allows you to create or change SUN disklabels.
171 Most people can safely leave this option disabled.
173 config BUSYBOX_CONFIG_FEATURE_OSF_LABEL
174 bool "Support BSD disklabels"
176 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
178 Enabling this option allows you to create or change BSD disklabels
179 and define and edit BSD disk slices.
181 config BUSYBOX_CONFIG_FEATURE_FDISK_ADVANCED
182 bool "Support expert mode"
184 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
186 Enabling this option allows you to do terribly unsafe things like
187 define arbitrary drive geometry, move the beginning of data in a
188 partition, and similarly evil things. Unless you have a very good
189 reason you would be wise to leave this disabled.
191 config BUSYBOX_CONFIG_FINDFS
194 select BUSYBOX_CONFIG_VOLUMEID
196 Prints the name of a filesystem with given label or UUID.
198 With all submodules selected, it will add ~8k to busybox.
200 config BUSYBOX_CONFIG_FLOCK
204 Manage locks from shell scripts
206 config BUSYBOX_CONFIG_FREERAMDISK
210 Linux allows you to create ramdisks. This utility allows you to
211 delete them and completely free all memory that was used for the
212 ramdisk. For example, if you boot Linux into a ramdisk and later
213 pivot_root, you may want to free the memory that is allocated to the
214 ramdisk. If you have no use for freeing memory from a ramdisk, leave
217 config BUSYBOX_CONFIG_FSCK_MINIX
221 The minix filesystem is a nice, small, compact, read-write filesystem
222 with little overhead. It is not a journaling filesystem however and
223 can experience corruption if it is not properly unmounted or if the
224 power goes off in the middle of a write. This utility allows you to
225 check for and attempt to repair any corruption that occurs to a minix
228 config BUSYBOX_CONFIG_MKFS_EXT2
232 Utility to create EXT2 filesystems.
234 config BUSYBOX_CONFIG_MKFS_MINIX
238 The minix filesystem is a nice, small, compact, read-write filesystem
239 with little overhead. If you wish to be able to create minix
240 filesystems this utility will do the job for you.
242 config BUSYBOX_CONFIG_FEATURE_MINIX2
243 bool "Support Minix fs v2 (fsck_minix/mkfs_minix)"
245 depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
247 If you wish to be able to create version 2 minix filesystems, enable
248 this. If you enabled 'mkfs_minix' then you almost certainly want to
249 be using the version 2 filesystem support.
251 config BUSYBOX_CONFIG_MKFS_REISER
255 Utility to create ReiserFS filesystems.
256 Note: this applet needs a lot of testing and polishing.
258 config BUSYBOX_CONFIG_MKFS_VFAT
262 Utility to create FAT32 filesystems.
264 config BUSYBOX_CONFIG_GETOPT
268 The getopt utility is used to break up (parse) options in command
269 lines to make it easy to write complex shell scripts that also check
270 for legal (and illegal) options. If you want to write horribly
271 complex shell scripts, or use some horribly complex shell script
272 written by others, this utility may be for you. Most people will
273 wisely leave this disabled.
275 config BUSYBOX_CONFIG_FEATURE_GETOPT_LONG
276 bool "Support option -l"
277 default n if BUSYBOX_CONFIG_LONG_OPTS
278 depends on BUSYBOX_CONFIG_GETOPT
280 Enable support for long options (option -l).
282 config BUSYBOX_CONFIG_HEXDUMP
286 The hexdump utility is used to display binary data in a readable
287 way that is comparable to the output from most hex editors.
289 config BUSYBOX_CONFIG_FEATURE_HEXDUMP_REVERSE
290 bool "Support -R, reverse of 'hexdump -Cv'"
292 depends on BUSYBOX_CONFIG_HEXDUMP
294 The hexdump utility is used to display binary data in an ascii
295 readable way. This option creates binary data from an ascii input.
296 NB: this option is non-standard. It's unwise to use it in scripts
297 aimed to be portable.
299 config BUSYBOX_CONFIG_HD
302 depends on BUSYBOX_CONFIG_HEXDUMP
304 hd is an alias to hexdump -C.
306 config BUSYBOX_CONFIG_HWCLOCK
310 The hwclock utility is used to read and set the hardware clock
311 on a system. This is primarily used to set the current time on
312 shutdown in the hardware clock, so the hardware will keep the
313 correct time when Linux is _not_ running.
315 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS
316 bool "Support long options (--hctosys,...)"
318 depends on BUSYBOX_CONFIG_HWCLOCK && BUSYBOX_CONFIG_LONG_OPTS
320 By default, the hwclock utility only uses short options. If you
321 are overly fond of its long options, such as --hctosys, --utc, etc)
322 then enable this option.
324 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS
325 bool "Use FHS /var/lib/hwclock/adjtime"
327 depends on BUSYBOX_CONFIG_HWCLOCK
329 Starting with FHS 2.3, the adjtime state file is supposed to exist
330 at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish
331 to use the FHS behavior, answer Y here, otherwise answer N for the
332 classic /etc/adjtime path.
334 pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO
336 config BUSYBOX_CONFIG_IPCRM
339 select BUSYBOX_CONFIG_FEATURE_SUID
341 The ipcrm utility allows the removal of System V interprocess
342 communication (IPC) objects and the associated data structures
345 config BUSYBOX_CONFIG_IPCS
348 select BUSYBOX_CONFIG_FEATURE_SUID
350 The ipcs utility is used to provide information on the currently
351 allocated System V interprocess (IPC) objects in the system.
353 config BUSYBOX_CONFIG_LOSETUP
357 losetup is used to associate or detach a loop device with a regular
358 file or block device, and to query the status of a loop device. This
359 version does not currently support enabling data encryption.
361 config BUSYBOX_CONFIG_LSPCI
365 lspci is a utility for displaying information about PCI buses in the
366 system and devices connected to them.
368 This version uses sysfs (/sys/bus/pci/devices) only.
370 config BUSYBOX_CONFIG_LSUSB
374 lsusb is a utility for displaying information about USB buses in the
375 system and devices connected to them.
377 This version uses sysfs (/sys/bus/usb/devices) only.
379 config BUSYBOX_CONFIG_MDEV
383 mdev is a mini-udev implementation for dynamically creating device
384 nodes in the /dev directory.
386 For more information, please see docs/mdev.txt
388 config BUSYBOX_CONFIG_FEATURE_MDEV_CONF
389 bool "Support /etc/mdev.conf"
391 depends on BUSYBOX_CONFIG_MDEV
393 Add support for the mdev config file to control ownership and
394 permissions of the device nodes.
396 For more information, please see docs/mdev.txt
398 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
399 bool "Support subdirs/symlinks"
401 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
403 Add support for renaming devices and creating symlinks.
405 For more information, please see docs/mdev.txt
407 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME_REGEXP
408 bool "Support regular expressions substitutions when renaming device"
410 depends on BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
412 Add support for regular expressions substitutions when renaming
415 config BUSYBOX_CONFIG_FEATURE_MDEV_EXEC
416 bool "Support command execution at device addition/removal"
418 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
420 This adds support for an optional field to /etc/mdev.conf for
421 executing commands when devices are created/removed.
423 For more information, please see docs/mdev.txt
425 config BUSYBOX_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE
426 bool "Support loading of firmwares"
428 depends on BUSYBOX_CONFIG_MDEV
430 Some devices need to load firmware before they can be usable.
432 These devices will request userspace look up the files in
433 /lib/firmware/ and if it exists, send it to the kernel for
434 loading into the hardware.
436 config BUSYBOX_CONFIG_MKSWAP
440 The mkswap utility is used to configure a file or disk partition as
441 Linux swap space. This allows Linux to use the entire file or
442 partition as if it were additional RAM, which can greatly increase
443 the capability of low-memory machines. This additional memory is
444 much slower than real RAM, but can be very helpful at preventing your
445 applications being killed by the Linux out of memory (OOM) killer.
446 Once you have created swap space using 'mkswap' you need to enable
447 the swap space using the 'swapon' utility.
449 config BUSYBOX_CONFIG_FEATURE_MKSWAP_UUID
452 depends on BUSYBOX_CONFIG_MKSWAP
454 Generate swap spaces with universally unique identifiers.
456 config BUSYBOX_CONFIG_MORE
460 more is a simple utility which allows you to read text one screen
461 sized page at a time. If you want to read text that is larger than
462 the screen, and you are using anything faster than a 300 baud modem,
463 you will probably find this utility very helpful. If you don't have
464 any need to reading text files, you can leave this disabled.
466 config BUSYBOX_CONFIG_FEATURE_USE_TERMIOS
467 bool "Use termios to manipulate the screen"
469 depends on BUSYBOX_CONFIG_MORE || BUSYBOX_CONFIG_TOP
471 This option allows utilities such as 'more' and 'top' to determine
472 the size of the screen. If you leave this disabled, your utilities
473 that display things on the screen will be especially primitive and
474 will be unable to determine the current screen size, and will be
475 unable to move the cursor.
477 config BUSYBOX_CONFIG_MOUNT
481 All files and filesystems in Unix are arranged into one big directory
482 tree. The 'mount' utility is used to graft a filesystem onto a
483 particular part of the tree. A filesystem can either live on a block
484 device, or it can be accessible over the network, as is the case with
485 NFS filesystems. Most people using BusyBox will also want to enable
488 config BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
489 bool "Support option -f"
491 depends on BUSYBOX_CONFIG_MOUNT
493 Enable support for faking a file system mount.
495 config BUSYBOX_CONFIG_FEATURE_MOUNT_VERBOSE
496 bool "Support option -v"
498 depends on BUSYBOX_CONFIG_MOUNT
500 Enable multi-level -v[vv...] verbose messages. Useful if you
501 debug mount problems and want to see what is exactly passed
504 config BUSYBOX_CONFIG_FEATURE_MOUNT_HELPERS
505 bool "Support mount helpers"
507 depends on BUSYBOX_CONFIG_MOUNT
509 Enable mounting of virtual file systems via external helpers.
510 E.g. "mount obexfs#-b00.11.22.33.44.55 /mnt" will in effect call
511 "obexfs -b00.11.22.33.44.55 /mnt"
512 Also "mount -t sometype [-o opts] fs /mnt" will try
513 "sometype [-o opts] fs /mnt" if simple mount syscall fails.
514 The idea is to use such virtual filesystems in /etc/fstab.
516 config BUSYBOX_CONFIG_FEATURE_MOUNT_LABEL
517 bool "Support specifying devices by label or UUID"
519 depends on BUSYBOX_CONFIG_MOUNT
520 select BUSYBOX_CONFIG_VOLUMEID
522 This allows for specifying a device by label or uuid, rather than by
523 name. This feature utilizes the same functionality as blkid/findfs.
524 This also enables label or uuid support for swapon.
526 config BUSYBOX_CONFIG_FEATURE_MOUNT_NFS
527 bool "Support mounting NFS file systems"
529 depends on BUSYBOX_CONFIG_MOUNT
530 select BUSYBOX_CONFIG_FEATURE_HAVE_RPC
531 select BUSYBOX_CONFIG_FEATURE_SYSLOG
533 Enable mounting of NFS file systems.
535 config BUSYBOX_CONFIG_FEATURE_MOUNT_CIFS
536 bool "Support mounting CIFS/SMB file systems"
538 depends on BUSYBOX_CONFIG_MOUNT
540 Enable support for samba mounts.
542 config BUSYBOX_CONFIG_FEATURE_MOUNT_FLAGS
543 depends on BUSYBOX_CONFIG_MOUNT
544 bool "Support lots of -o flags in mount"
547 Without this, mount only supports ro/rw/remount. With this, it
548 supports nosuid, suid, dev, nodev, exec, noexec, sync, async, atime,
549 noatime, diratime, nodiratime, loud, bind, move, shared, slave,
550 private, unbindable, rshared, rslave, rprivate, and runbindable.
552 config BUSYBOX_CONFIG_FEATURE_MOUNT_FSTAB
553 depends on BUSYBOX_CONFIG_MOUNT
554 bool "Support /etc/fstab and -a"
557 Support mount all and looking for files in /etc/fstab.
559 config BUSYBOX_CONFIG_PIVOT_ROOT
563 The pivot_root utility swaps the mount points for the root filesystem
564 with some other mounted filesystem. This allows you to do all sorts
565 of wild and crazy things with your Linux system and is far more
566 powerful than 'chroot'.
568 Note: This is for initrd in linux 2.4. Under initramfs (introduced
569 in linux 2.6) use switch_root instead.
571 config BUSYBOX_CONFIG_RDATE
575 The rdate utility allows you to synchronize the date and time of your
576 system clock with the date and time of a remote networked system using
577 the RFC868 protocol, which is built into the inetd daemon on most
580 config BUSYBOX_CONFIG_RDEV
584 Print the device node associated with the filesystem mounted at '/'.
586 config BUSYBOX_CONFIG_READPROFILE
590 This allows you to parse /proc/profile for basic profiling.
592 config BUSYBOX_CONFIG_RTCWAKE
596 Enter a system sleep state until specified wakeup time.
598 config BUSYBOX_CONFIG_SCRIPT
602 The script makes typescript of terminal session.
604 config BUSYBOX_CONFIG_SCRIPTREPLAY
608 This program replays a typescript, using timing information
611 config BUSYBOX_CONFIG_SETARCH
615 The linux32 utility is used to create a 32bit environment for the
616 specified program (usually a shell). It only makes sense to have
617 this util on a system that supports both 64bit and 32bit userland
618 (like amd64/x86, ppc64/ppc, sparc64/sparc, etc...).
620 config BUSYBOX_CONFIG_SWAPONOFF
624 This option enables both the 'swapon' and the 'swapoff' utilities.
625 Once you have created some swap space using 'mkswap', you also need
626 to enable your swap space with the 'swapon' utility. The 'swapoff'
627 utility is used, typically at system shutdown, to disable any swap
628 space. If you are not using any swap space, you can leave this
631 config BUSYBOX_CONFIG_FEATURE_SWAPON_PRI
632 bool "Support priority option -p"
634 depends on BUSYBOX_CONFIG_SWAPONOFF
636 Enable support for setting swap device priority in swapon.
638 config BUSYBOX_CONFIG_SWITCH_ROOT
642 The switch_root utility is used from initramfs to select a new
643 root device. Under initramfs, you have to use this instead of
644 pivot_root. (Stop reading here if you don't care why.)
646 Booting with initramfs extracts a gzipped cpio archive into rootfs
647 (which is a variant of ramfs/tmpfs). Because rootfs can't be moved
648 or unmounted*, pivot_root will not work from initramfs. Instead,
649 switch_root deletes everything out of rootfs (including itself),
650 does a mount --move that overmounts rootfs with the new root, and
651 then execs the specified init program.
653 * Because the Linux kernel uses rootfs internally as the starting
654 and ending point for searching through the kernel's doubly linked
655 list of active mount points. That's why.
657 config BUSYBOX_CONFIG_UMOUNT
661 When you want to remove a mounted filesystem from its current mount
662 point, for example when you are shutting down the system, the
663 'umount' utility is the tool to use. If you enabled the 'mount'
664 utility, you almost certainly also want to enable 'umount'.
666 config BUSYBOX_CONFIG_FEATURE_UMOUNT_ALL
667 bool "Support option -a"
669 depends on BUSYBOX_CONFIG_UMOUNT
671 Support -a option to unmount all currently mounted filesystems.
673 comment "Common options for mount/umount"
674 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
676 config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
677 bool "Support loopback mounts"
679 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
681 Enabling this feature allows automatic mounting of files (containing
682 filesystem images) via the linux kernel's loopback devices.
683 The mount command will detect you are trying to mount a file instead
684 of a block device, and transparently associate the file with a
685 loopback device. The umount command will also free that loopback
688 You can still use the 'losetup' utility (to manually associate files
689 with loop devices) if you need to do something advanced, such as
690 specify an offset or cryptographic options to the loopback device.
691 (If you don't want umount to free the loop device, use "umount -D".)
693 config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP_CREATE
694 bool "Create new loopback devices if needed"
696 depends on BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
698 Linux kernels >= 2.6.24 support unlimited loopback devices. They are
699 allocated for use when trying to use a loop device. The loop device
702 This feature lets mount to try to create next /dev/loopN device
703 if it does not find a free one.
705 config BUSYBOX_CONFIG_FEATURE_MTAB_SUPPORT
706 bool "Support for the old /etc/mtab file"
708 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
709 select BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
711 Historically, Unix systems kept track of the currently mounted
712 partitions in the file "/etc/mtab". These days, the kernel exports
713 the list of currently mounted partitions in "/proc/mounts", rendering
714 the old mtab file obsolete. (In modern systems, /etc/mtab should be
715 a symlink to /proc/mounts.)
717 The only reason to have mount maintain an /etc/mtab file itself is if
718 your stripped-down embedded system does not have a /proc directory.
719 If you must use this, keep in mind it's inherently brittle (for
720 example a mount under chroot won't update it), can't handle modern
721 features like separate per-process filesystem namespaces, requires
722 that your /etc directory be writable, tends to get easily confused
723 by --bind or --move mounts, won't update if you rename a directory
724 that contains a mount point, and so on. (In brief: avoid.)
726 About the only reason to use this is if you've removed /proc from
729 config BUSYBOX_CONFIG_VOLUMEID
730 bool #No description makes it a hidden option
733 menu "Filesystem/Volume identification"
734 depends on BUSYBOX_CONFIG_VOLUMEID
736 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_EXT
737 bool "Ext filesystem"
739 depends on BUSYBOX_CONFIG_VOLUMEID
743 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_BTRFS
744 bool "btrfs filesystem"
746 depends on BUSYBOX_CONFIG_VOLUMEID
750 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_REISERFS
751 bool "Reiser filesystem"
753 depends on BUSYBOX_CONFIG_VOLUMEID
757 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_FAT
758 bool "fat filesystem"
760 depends on BUSYBOX_CONFIG_VOLUMEID
764 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_HFS
765 bool "hfs filesystem"
767 depends on BUSYBOX_CONFIG_VOLUMEID
771 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_JFS
772 bool "jfs filesystem"
774 depends on BUSYBOX_CONFIG_VOLUMEID
778 ### config FEATURE_VOLUMEID_UFS
779 ### bool "ufs filesystem"
781 ### depends on VOLUMEID
785 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_XFS
786 bool "xfs filesystem"
788 depends on BUSYBOX_CONFIG_VOLUMEID
792 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_NTFS
793 bool "ntfs filesystem"
795 depends on BUSYBOX_CONFIG_VOLUMEID
799 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ISO9660
800 bool "iso9660 filesystem"
802 depends on BUSYBOX_CONFIG_VOLUMEID
806 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_UDF
807 bool "udf filesystem"
809 depends on BUSYBOX_CONFIG_VOLUMEID
813 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LUKS
814 bool "luks filesystem"
816 depends on BUSYBOX_CONFIG_VOLUMEID
820 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXSWAP
821 bool "linux swap filesystem"
823 depends on BUSYBOX_CONFIG_VOLUMEID
827 ### config FEATURE_VOLUMEID_LVM
830 ### depends on VOLUMEID
834 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_CRAMFS
835 bool "cramfs filesystem"
837 depends on BUSYBOX_CONFIG_VOLUMEID
841 ### config FEATURE_VOLUMEID_HPFS
842 ### bool "hpfs filesystem"
844 ### depends on VOLUMEID
848 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ROMFS
849 bool "romfs filesystem"
851 depends on BUSYBOX_CONFIG_VOLUMEID
855 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_SYSV
856 bool "sysv filesystem"
858 depends on BUSYBOX_CONFIG_VOLUMEID
862 ### config FEATURE_VOLUMEID_MINIX
863 ### bool "minix filesystem"
865 ### depends on VOLUMEID
869 ### These only detect partition tables - not used (yet?)
870 ### config FEATURE_VOLUMEID_MAC
871 ### bool "mac filesystem"
873 ### depends on VOLUMEID
877 ### config FEATURE_VOLUMEID_MSDOS
878 ### bool "msdos filesystem"
880 ### depends on VOLUMEID
884 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_OCFS2
885 bool "ocfs2 filesystem"
887 depends on BUSYBOX_CONFIG_VOLUMEID
891 ### config FEATURE_VOLUMEID_HIGHPOINTRAID
892 ### bool "highpoint raid"
894 ### depends on VOLUMEID
898 ### config FEATURE_VOLUMEID_ISWRAID
899 ### bool "intel raid"
901 ### depends on VOLUMEID
905 ### config FEATURE_VOLUMEID_LSIRAID
908 ### depends on VOLUMEID
912 ### config FEATURE_VOLUMEID_VIARAID
915 ### depends on VOLUMEID
919 ### config FEATURE_VOLUMEID_SILICONRAID
920 ### bool "silicon raid"
922 ### depends on VOLUMEID
926 ### config FEATURE_VOLUMEID_NVIDIARAID
927 ### bool "nvidia raid"
929 ### depends on VOLUMEID
933 ### config FEATURE_VOLUMEID_PROMISERAID
934 ### bool "promise raid"
936 ### depends on VOLUMEID
940 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXRAID
943 depends on BUSYBOX_CONFIG_VOLUMEID