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_BLKID
11 select BUSYBOX_CONFIG_VOLUMEID
13 Lists labels and UUIDs of all filesystems.
15 With all submodules selected, it will add ~8k to busybox.
17 config BUSYBOX_CONFIG_DMESG
21 dmesg is used to examine or control the kernel ring buffer. When the
22 Linux kernel prints messages to the system log, they are stored in
23 the kernel ring buffer. You can use dmesg to print the kernel's ring
24 buffer, clear the kernel ring buffer, change the size of the kernel
25 ring buffer, and change the priority level at which kernel messages
26 are also logged to the system console. Enable this option if you
27 wish to enable the 'dmesg' utility.
29 config BUSYBOX_CONFIG_FEATURE_DMESG_PRETTY
30 bool "Pretty dmesg output"
32 depends on BUSYBOX_CONFIG_DMESG
34 If you wish to scrub the syslog level from the output, say 'Y' here.
35 The syslog level is a string prefixed to every line with the form
38 With this option you will see:
40 Linux version 2.6.17.4 .....
41 BIOS-provided physical RAM map:
42 BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
44 Without this option you will see:
46 <5>Linux version 2.6.17.4 .....
47 <6>BIOS-provided physical RAM map:
48 <6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
50 config BUSYBOX_CONFIG_FBSET
54 fbset is used to show or change the settings of a Linux frame buffer
55 device. The frame buffer device provides a simple and unique
56 interface to access a graphics display. Enable this option
57 if you wish to enable the 'fbset' utility.
59 config BUSYBOX_CONFIG_FEATURE_FBSET_FANCY
60 bool "Turn on extra fbset options"
62 depends on BUSYBOX_CONFIG_FBSET
64 This option enables extended fbset options, allowing one to set the
65 framebuffer size, color depth, etc. interface to access a graphics
66 display. Enable this option if you wish to enable extended fbset
69 config BUSYBOX_CONFIG_FEATURE_FBSET_READMODE
70 bool "Turn on fbset readmode support"
72 depends on BUSYBOX_CONFIG_FBSET
74 This option allows fbset to read the video mode database stored by
75 default n /etc/fb.modes, which can be used to set frame buffer
76 device to pre-defined video modes.
78 config BUSYBOX_CONFIG_FDFLUSH
82 fdflush is only needed when changing media on slightly-broken
83 removable media drives. It is used to make Linux believe that a
84 hardware disk-change switch has been actuated, which causes Linux to
85 forget anything it has cached from the previous media. If you have
86 such a slightly-broken drive, you will need to run fdflush every time
87 you change a disk. Most people have working hardware and can safely
90 config BUSYBOX_CONFIG_FDFORMAT
94 fdformat is used to low-level format a floppy disk.
96 config BUSYBOX_CONFIG_FDISK
100 The fdisk utility is used to divide hard disks into one or more
101 logical disks, which are generally called partitions. This utility
102 can be used to list and edit the set of partitions or BSD style
103 'disk slices' that are defined on a hard drive.
105 config BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
106 bool "Support over 4GB disks"
108 depends on BUSYBOX_CONFIG_FDISK
110 Enable this option to support large disks > 4GB.
112 config BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
115 depends on BUSYBOX_CONFIG_FDISK
117 Enabling this option allows you to create or change a partition table
118 and write those changes out to disk. If you leave this option
119 disabled, you will only be able to view the partition table.
121 config BUSYBOX_CONFIG_FEATURE_AIX_LABEL
122 bool "Support AIX disklabels"
124 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
126 Enabling this option allows you to create or change AIX disklabels.
127 Most people can safely leave this option disabled.
129 config BUSYBOX_CONFIG_FEATURE_SGI_LABEL
130 bool "Support SGI disklabels"
132 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
134 Enabling this option allows you to create or change SGI disklabels.
135 Most people can safely leave this option disabled.
137 config BUSYBOX_CONFIG_FEATURE_SUN_LABEL
138 bool "Support SUN disklabels"
140 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
142 Enabling this option allows you to create or change SUN disklabels.
143 Most people can safely leave this option disabled.
145 config BUSYBOX_CONFIG_FEATURE_OSF_LABEL
146 bool "Support BSD disklabels"
148 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
150 Enabling this option allows you to create or change BSD disklabels
151 and define and edit BSD disk slices.
153 config BUSYBOX_CONFIG_FEATURE_FDISK_ADVANCED
154 bool "Support expert mode"
156 depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
158 Enabling this option allows you to do terribly unsafe things like
159 define arbitrary drive geometry, move the beginning of data in a
160 partition, and similarly evil things. Unless you have a very good
161 reason you would be wise to leave this disabled.
163 config BUSYBOX_CONFIG_FINDFS
166 select BUSYBOX_CONFIG_VOLUMEID
168 Prints the name of a filesystem with given label or UUID.
170 With all submodules selected, it will add ~8k to busybox.
172 config BUSYBOX_CONFIG_FREERAMDISK
176 Linux allows you to create ramdisks. This utility allows you to
177 delete them and completely free all memory that was used for the
178 ramdisk. For example, if you boot Linux into a ramdisk and later
179 pivot_root, you may want to free the memory that is allocated to the
180 ramdisk. If you have no use for freeing memory from a ramdisk, leave
183 config BUSYBOX_CONFIG_FSCK_MINIX
187 The minix filesystem is a nice, small, compact, read-write filesystem
188 with little overhead. It is not a journaling filesystem however and
189 can experience corruption if it is not properly unmounted or if the
190 power goes off in the middle of a write. This utility allows you to
191 check for and attempt to repair any corruption that occurs to a minix
194 config BUSYBOX_CONFIG_MKFS_MINIX
198 The minix filesystem is a nice, small, compact, read-write filesystem
199 with little overhead. If you wish to be able to create minix
200 filesystems this utility will do the job for you.
202 comment "Minix filesystem support"
203 depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
205 config BUSYBOX_CONFIG_FEATURE_MINIX2
206 bool "Support Minix fs v2 (fsck_minix/mkfs_minix)"
208 depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
210 If you wish to be able to create version 2 minix filesystems, enable
211 this. If you enabled 'mkfs_minix' then you almost certainly want to
212 be using the version 2 filesystem support.
214 config BUSYBOX_CONFIG_GETOPT
218 The getopt utility is used to break up (parse) options in command
219 lines to make it easy to write complex shell scripts that also check
220 for legal (and illegal) options. If you want to write horribly
221 complex shell scripts, or use some horribly complex shell script
222 written by others, this utility may be for you. Most people will
223 wisely leave this disabled.
225 config BUSYBOX_CONFIG_HEXDUMP
229 The hexdump utility is used to display binary data in a readable
230 way that is comparable to the output from most hex editors.
232 config BUSYBOX_CONFIG_FEATURE_HEXDUMP_REVERSE
233 bool "Support -R, reverse of 'hexdump -Cv'"
235 depends on BUSYBOX_CONFIG_HEXDUMP
237 The hexdump utility is used to display binary data in an ascii
238 readable way. This option creates binary data from an ascii input.
239 NB: this option is non-standard. It's unwise to use it in scripts
240 aimed to be portable.
242 config BUSYBOX_CONFIG_HD
245 select BUSYBOX_CONFIG_HEXDUMP
247 hd is an alias to hexdump -C.
249 config BUSYBOX_CONFIG_HWCLOCK
253 The hwclock utility is used to read and set the hardware clock
254 on a system. This is primarily used to set the current time on
255 shutdown in the hardware clock, so the hardware will keep the
256 correct time when Linux is _not_ running.
258 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS
259 bool "Support long options (--hctosys,...)"
261 depends on BUSYBOX_CONFIG_HWCLOCK && BUSYBOX_CONFIG_GETOPT_LONG
263 By default, the hwclock utility only uses short options. If you
264 are overly fond of its long options, such as --hctosys, --utc, etc)
265 then enable this option.
267 config BUSYBOX_CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS
268 bool "Use FHS /var/lib/hwclock/adjtime"
270 depends on BUSYBOX_CONFIG_HWCLOCK
272 Starting with FHS 2.3, the adjtime state file is supposed to exist
273 at /var/lib/hwclock/adjtime instead of /etc/adjtime. If you wish
274 to use the FHS behavior, answer Y here, otherwise answer N for the
275 classic /etc/adjtime path.
277 pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO
279 config BUSYBOX_CONFIG_IPCRM
282 select BUSYBOX_CONFIG_FEATURE_SUID
284 The ipcrm utility allows the removal of System V interprocess
285 communication (IPC) objects and the associated data structures
288 config BUSYBOX_CONFIG_IPCS
291 select BUSYBOX_CONFIG_FEATURE_SUID
293 The ipcs utility is used to provide information on the currently
294 allocated System V interprocess (IPC) objects in the system.
296 config BUSYBOX_CONFIG_LOSETUP
300 losetup is used to associate or detach a loop device with a regular
301 file or block device, and to query the status of a loop device. This
302 version does not currently support enabling data encryption.
304 config BUSYBOX_CONFIG_MDEV
308 mdev is a mini-udev implementation for dynamically creating device
309 nodes in the /dev directory.
311 For more information, please see docs/mdev.txt
313 config BUSYBOX_CONFIG_FEATURE_MDEV_CONF
314 bool "Support /etc/mdev.conf"
316 depends on BUSYBOX_CONFIG_MDEV
318 Add support for the mdev config file to control ownership and
319 permissions of the device nodes.
321 For more information, please see docs/mdev.txt
323 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
324 bool "Support subdirs/symlinks"
326 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
328 Add support for renaming devices and creating symlinks.
330 For more information, please see docs/mdev.txt
332 config BUSYBOX_CONFIG_FEATURE_MDEV_RENAME_REGEXP
333 bool "Support regular expressions substitutions when renaming device"
335 depends on BUSYBOX_CONFIG_FEATURE_MDEV_RENAME
337 Add support for regular expressions substitutions when renaming
340 config BUSYBOX_CONFIG_FEATURE_MDEV_EXEC
341 bool "Support command execution at device addition/removal"
343 depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
345 This adds support for an optional field to /etc/mdev.conf for
346 executing commands when devices are created/removed.
348 For more information, please see docs/mdev.txt
350 config BUSYBOX_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE
351 bool "Support loading of firmwares"
353 depends on BUSYBOX_CONFIG_MDEV
355 Some devices need to load firmware before they can be usable.
357 These devices will request userspace look up the files in
358 /lib/firmware/ and if it exists, send it to the kernel for
359 loading into the hardware.
361 config BUSYBOX_CONFIG_MKSWAP
365 The mkswap utility is used to configure a file or disk partition as
366 Linux swap space. This allows Linux to use the entire file or
367 partition as if it were additional RAM, which can greatly increase
368 the capability of low-memory machines. This additional memory is
369 much slower than real RAM, but can be very helpful at preventing your
370 applications being killed by the Linux out of memory (OOM) killer.
371 Once you have created swap space using 'mkswap' you need to enable
372 the swap space using the 'swapon' utility.
374 config BUSYBOX_CONFIG_FEATURE_MKSWAP_V0
375 bool "Version 0 support"
377 depends on BUSYBOX_CONFIG_MKSWAP
378 # depends on MKSWAP && BUSYBOX_CONFIG_DEPRECATED
380 Enable support for the old v0 style.
381 If your kernel is older than 2.1.117, then v0 support is the
384 config BUSYBOX_CONFIG_MORE
388 more is a simple utility which allows you to read text one screen
389 sized page at a time. If you want to read text that is larger than
390 the screen, and you are using anything faster than a 300 baud modem,
391 you will probably find this utility very helpful. If you don't have
392 any need to reading text files, you can leave this disabled.
394 config BUSYBOX_CONFIG_FEATURE_USE_TERMIOS
395 bool "Use termios to manipulate the screen"
397 depends on BUSYBOX_CONFIG_MORE || BUSYBOX_CONFIG_TOP
399 This option allows utilities such as 'more' and 'top' to determine
400 the size of the screen. If you leave this disabled, your utilities
401 that display things on the screen will be especially primitive and
402 will be unable to determine the current screen size, and will be
403 unable to move the cursor.
405 config BUSYBOX_CONFIG_VOLUMEID
406 bool #No description makes it a hidden option
409 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_EXT
410 bool "Ext filesystem"
412 depends on BUSYBOX_CONFIG_VOLUMEID
416 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_REISERFS
417 bool "Reiser filesystem"
419 depends on BUSYBOX_CONFIG_VOLUMEID
423 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_FAT
424 bool "fat filesystem"
426 depends on BUSYBOX_CONFIG_VOLUMEID
430 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_HFS
431 bool "hfs filesystem"
433 depends on BUSYBOX_CONFIG_VOLUMEID
437 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_JFS
438 bool "jfs filesystem"
440 depends on BUSYBOX_CONFIG_VOLUMEID
444 ### config FEATURE_VOLUMEID_UFS
445 ### bool "ufs filesystem"
447 ### depends on VOLUMEID
451 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_XFS
452 bool "xfs filesystem"
454 depends on BUSYBOX_CONFIG_VOLUMEID
458 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_NTFS
459 bool "ntfs filesystem"
461 depends on BUSYBOX_CONFIG_VOLUMEID
465 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ISO9660
466 bool "iso9660 filesystem"
468 depends on BUSYBOX_CONFIG_VOLUMEID
472 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_UDF
473 bool "udf filesystem"
475 depends on BUSYBOX_CONFIG_VOLUMEID
479 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LUKS
480 bool "luks filesystem"
482 depends on BUSYBOX_CONFIG_VOLUMEID
486 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXSWAP
487 bool "linux swap filesystem"
489 depends on BUSYBOX_CONFIG_VOLUMEID
493 ### config FEATURE_VOLUMEID_LVM
496 ### depends on VOLUMEID
500 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_CRAMFS
501 bool "cramfs filesystem"
503 depends on BUSYBOX_CONFIG_VOLUMEID
507 ### config FEATURE_VOLUMEID_HPFS
508 ### bool "hpfs filesystem"
510 ### depends on VOLUMEID
514 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_ROMFS
515 bool "romfs filesystem"
517 depends on BUSYBOX_CONFIG_VOLUMEID
521 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_SYSV
522 bool "sysv filesystem"
524 depends on BUSYBOX_CONFIG_VOLUMEID
528 ### config FEATURE_VOLUMEID_MINIX
529 ### bool "minix filesystem"
531 ### depends on VOLUMEID
535 ### These only detect partition tables - not used (yet?)
536 ### config FEATURE_VOLUMEID_MAC
537 ### bool "mac filesystem"
539 ### depends on VOLUMEID
543 ### config FEATURE_VOLUMEID_MSDOS
544 ### bool "msdos filesystem"
546 ### depends on VOLUMEID
550 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_OCFS2
551 bool "ocfs2 filesystem"
553 depends on BUSYBOX_CONFIG_VOLUMEID
557 ### config FEATURE_VOLUMEID_HIGHPOINTRAID
558 ### bool "highpoint raid"
560 ### depends on VOLUMEID
564 ### config FEATURE_VOLUMEID_ISWRAID
565 ### bool "intel raid"
567 ### depends on VOLUMEID
571 ### config FEATURE_VOLUMEID_LSIRAID
574 ### depends on VOLUMEID
578 ### config FEATURE_VOLUMEID_VIARAID
581 ### depends on VOLUMEID
585 ### config FEATURE_VOLUMEID_SILICONRAID
586 ### bool "silicon raid"
588 ### depends on VOLUMEID
592 ### config FEATURE_VOLUMEID_NVIDIARAID
593 ### bool "nvidia raid"
595 ### depends on VOLUMEID
599 ### config FEATURE_VOLUMEID_PROMISERAID
600 ### bool "promise raid"
602 ### depends on VOLUMEID
606 config BUSYBOX_CONFIG_FEATURE_VOLUMEID_LINUXRAID
609 depends on BUSYBOX_CONFIG_VOLUMEID
613 config BUSYBOX_CONFIG_MOUNT
617 All files and filesystems in Unix are arranged into one big directory
618 tree. The 'mount' utility is used to graft a filesystem onto a
619 particular part of the tree. A filesystem can either live on a block
620 device, or it can be accessible over the network, as is the case with
621 NFS filesystems. Most people using BusyBox will also want to enable
624 config BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
625 bool "Support option -f"
627 depends on BUSYBOX_CONFIG_MOUNT
629 Enable support for faking a file system mount.
631 config BUSYBOX_CONFIG_FEATURE_MOUNT_VERBOSE
632 bool "Support option -v"
634 depends on BUSYBOX_CONFIG_MOUNT
636 Enable multi-level -v[vv...] verbose messages. Useful if you
637 debug mount problems and want to see what is exactly passed
640 config BUSYBOX_CONFIG_FEATURE_MOUNT_HELPERS
641 bool "Support mount helpers"
643 depends on BUSYBOX_CONFIG_MOUNT
645 Enable mounting of virtual file systems via external helpers.
646 E.g. "mount obexfs#-b00.11.22.33.44.55 /mnt" will in effect call
647 "obexfs -b00.11.22.33.44.55 /mnt"
648 Also "mount -t sometype [-o opts] fs /mnt" will try
649 "sometype [-o opts] fs /mnt" if simple mount syscall fails.
650 The idea is to use such virtual filesystems in /etc/fstab.
652 config BUSYBOX_CONFIG_FEATURE_MOUNT_LABEL
653 bool "Support specifiying devices by label or UUID"
655 depends on BUSYBOX_CONFIG_MOUNT
656 select BUSYBOX_CONFIG_VOLUMEID
658 This allows for specifying a device by label or uuid, rather than by
659 name. This feature utilizes the same functionality as blkid/findfs.
661 config BUSYBOX_CONFIG_FEATURE_MOUNT_NFS
662 bool "Support mounting NFS file systems"
664 depends on BUSYBOX_CONFIG_MOUNT
665 select BUSYBOX_CONFIG_FEATURE_HAVE_RPC
666 select BUSYBOX_CONFIG_FEATURE_SYSLOG
668 Enable mounting of NFS file systems.
670 config BUSYBOX_CONFIG_FEATURE_MOUNT_CIFS
671 bool "Support mounting CIFS/SMB file systems"
673 depends on BUSYBOX_CONFIG_MOUNT
675 Enable support for samba mounts.
677 config BUSYBOX_CONFIG_FEATURE_MOUNT_FLAGS
678 depends on BUSYBOX_CONFIG_MOUNT
679 bool "Support lots of -o flags in mount"
682 Without this, mount only supports ro/rw/remount. With this, it
683 supports nosuid, suid, dev, nodev, exec, noexec, sync, async, atime,
684 noatime, diratime, nodiratime, loud, bind, move, shared, slave,
685 private, unbindable, rshared, rslave, rprivate, and runbindable.
687 config BUSYBOX_CONFIG_FEATURE_MOUNT_FSTAB
688 depends on BUSYBOX_CONFIG_MOUNT
689 bool "Support /etc/fstab and -a"
692 Support mount all and looking for files in /etc/fstab.
694 config BUSYBOX_CONFIG_PIVOT_ROOT
698 The pivot_root utility swaps the mount points for the root filesystem
699 with some other mounted filesystem. This allows you to do all sorts
700 of wild and crazy things with your Linux system and is far more
701 powerful than 'chroot'.
703 Note: This is for initrd in linux 2.4. Under initramfs (introduced
704 in linux 2.6) use switch_root instead.
706 config BUSYBOX_CONFIG_RDATE
710 The rdate utility allows you to synchronize the date and time of your
711 system clock with the date and time of a remote networked system using
712 the RFC868 protocol, which is built into the inetd daemon on most
715 config BUSYBOX_CONFIG_RDEV
719 Print the device node associated with the filesystem mounted at '/'.
721 config BUSYBOX_CONFIG_READPROFILE
725 This allows you to parse /proc/profile for basic profiling.
727 config BUSYBOX_CONFIG_RTCWAKE
731 Enter a system sleep state until specified wakeup time.
733 config BUSYBOX_CONFIG_SCRIPT
737 The script makes typescript of terminal session.
739 config BUSYBOX_CONFIG_SETARCH
743 The linux32 utility is used to create a 32bit environment for the
744 specified program (usually a shell). It only makes sense to have
745 this util on a system that supports both 64bit and 32bit userland
746 (like amd64/x86, ppc64/ppc, sparc64/sparc, etc...).
748 config BUSYBOX_CONFIG_SWAPONOFF
752 This option enables both the 'swapon' and the 'swapoff' utilities.
753 Once you have created some swap space using 'mkswap', you also need
754 to enable your swap space with the 'swapon' utility. The 'swapoff'
755 utility is used, typically at system shutdown, to disable any swap
756 space. If you are not using any swap space, you can leave this
759 config BUSYBOX_CONFIG_FEATURE_SWAPON_PRI
760 bool "Support priority option -p"
762 depends on BUSYBOX_CONFIG_SWAPONOFF
764 Enable support for setting swap device priority in swapon.
766 config BUSYBOX_CONFIG_SWITCH_ROOT
770 The switch_root utility is used from initramfs to select a new
771 root device. Under initramfs, you have to use this instead of
772 pivot_root. (Stop reading here if you don't care why.)
774 Booting with initramfs extracts a gzipped cpio archive into rootfs
775 (which is a variant of ramfs/tmpfs). Because rootfs can't be moved
776 or unmounted*, pivot_root will not work from initramfs. Instead,
777 switch_root deletes everything out of rootfs (including itself),
778 does a mount --move that overmounts rootfs with the new root, and
779 then execs the specified init program.
781 * Because the Linux kernel uses rootfs internally as the starting
782 and ending point for searching through the kernel's doubly linked
783 list of active mount points. That's why.
785 config BUSYBOX_CONFIG_UMOUNT
789 When you want to remove a mounted filesystem from its current mount
790 point, for example when you are shutting down the system, the
791 'umount' utility is the tool to use. If you enabled the 'mount'
792 utility, you almost certainly also want to enable 'umount'.
794 config BUSYBOX_CONFIG_FEATURE_UMOUNT_ALL
795 bool "Support option -a"
797 depends on BUSYBOX_CONFIG_UMOUNT
799 Support -a option to unmount all currently mounted filesystems.
801 comment "Common options for mount/umount"
802 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
804 config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
805 bool "Support loopback mounts"
807 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
809 Enabling this feature allows automatic mounting of files (containing
810 filesystem images) via the linux kernel's loopback devices.
811 The mount command will detect you are trying to mount a file instead
812 of a block device, and transparently associate the file with a
813 loopback device. The umount command will also free that loopback
816 You can still use the 'losetup' utility (to manually associate files
817 with loop devices) if you need to do something advanced, such as
818 specify an offset or cryptographic options to the loopback device.
819 (If you don't want umount to free the loop device, use "umount -D".)
821 config BUSYBOX_CONFIG_FEATURE_MTAB_SUPPORT
822 bool "Support for the old /etc/mtab file"
824 depends on BUSYBOX_CONFIG_MOUNT || BUSYBOX_CONFIG_UMOUNT
825 select BUSYBOX_CONFIG_FEATURE_MOUNT_FAKE
827 Historically, Unix systems kept track of the currently mounted
828 partitions in the file "/etc/mtab". These days, the kernel exports
829 the list of currently mounted partitions in "/proc/mounts", rendering
830 the old mtab file obsolete. (In modern systems, /etc/mtab should be
831 a symlink to /proc/mounts.)
833 The only reason to have mount maintain an /etc/mtab file itself is if
834 your stripped-down embedded system does not have a /proc directory.
835 If you must use this, keep in mind it's inherently brittle (for
836 example a mount under chroot won't update it), can't handle modern
837 features like separate per-process filesystem namespaces, requires
838 that your /etc directory be writeable, tends to get easily confused
839 by --bind or --move mounts, won't update if you rename a directory
840 that contains a mount point, and so on. (In brief: avoid.)
842 About the only reason to use this is if you've removed /proc from