blob: 3c522f948b5adcb60b572568030ee549dfae7191
| 1 | # |
| 2 | # For a description of the syntax of this configuration file, |
| 3 | # see scripts/kbuild/config-language.txt. |
| 4 | # |
| 5 | |
| 6 | menu "Linux System Utilities" |
| 7 | |
| 8 | INSERT |
| 9 | |
| 10 | comment "Common options for mount/umount" |
| 11 | depends on MOUNT || UMOUNT |
| 12 | |
| 13 | config FEATURE_MOUNT_LOOP |
| 14 | bool "Support loopback mounts" |
| 15 | default y |
| 16 | depends on MOUNT || UMOUNT |
| 17 | help |
| 18 | Enabling this feature allows automatic mounting of files (containing |
| 19 | filesystem images) via the linux kernel's loopback devices. |
| 20 | The mount command will detect you are trying to mount a file instead |
| 21 | of a block device, and transparently associate the file with a |
| 22 | loopback device. The umount command will also free that loopback |
| 23 | device. |
| 24 | |
| 25 | You can still use the 'losetup' utility (to manually associate files |
| 26 | with loop devices) if you need to do something advanced, such as |
| 27 | specify an offset or cryptographic options to the loopback device. |
| 28 | (If you don't want umount to free the loop device, use "umount -D".) |
| 29 | |
| 30 | config FEATURE_MOUNT_LOOP_CREATE |
| 31 | bool "Create new loopback devices if needed" |
| 32 | default y |
| 33 | depends on FEATURE_MOUNT_LOOP |
| 34 | help |
| 35 | Linux kernels >= 2.6.24 support unlimited loopback devices. They are |
| 36 | allocated for use when trying to use a loop device. The loop device |
| 37 | must however exist. |
| 38 | |
| 39 | This feature lets mount to try to create next /dev/loopN device |
| 40 | if it does not find a free one. |
| 41 | |
| 42 | config FEATURE_MTAB_SUPPORT |
| 43 | bool "Support for the old /etc/mtab file" |
| 44 | default n |
| 45 | depends on MOUNT || UMOUNT |
| 46 | select FEATURE_MOUNT_FAKE |
| 47 | help |
| 48 | Historically, Unix systems kept track of the currently mounted |
| 49 | partitions in the file "/etc/mtab". These days, the kernel exports |
| 50 | the list of currently mounted partitions in "/proc/mounts", rendering |
| 51 | the old mtab file obsolete. (In modern systems, /etc/mtab should be |
| 52 | a symlink to /proc/mounts.) |
| 53 | |
| 54 | The only reason to have mount maintain an /etc/mtab file itself is if |
| 55 | your stripped-down embedded system does not have a /proc directory. |
| 56 | If you must use this, keep in mind it's inherently brittle (for |
| 57 | example a mount under chroot won't update it), can't handle modern |
| 58 | features like separate per-process filesystem namespaces, requires |
| 59 | that your /etc directory be writable, tends to get easily confused |
| 60 | by --bind or --move mounts, won't update if you rename a directory |
| 61 | that contains a mount point, and so on. (In brief: avoid.) |
| 62 | |
| 63 | About the only reason to use this is if you've removed /proc from |
| 64 | your kernel. |
| 65 | |
| 66 | source util-linux/volume_id/Config.in |
| 67 | |
| 68 | endmenu |
| 69 |