diff options
Diffstat (limited to 'util-linux/Config.in')
-rw-r--r-- | util-linux/Config.in | 59 |
1 files changed, 24 insertions, 35 deletions
diff --git a/util-linux/Config.in b/util-linux/Config.in index 7007915ba..7fde01971 100644 --- a/util-linux/Config.in +++ b/util-linux/Config.in | |||
@@ -323,54 +323,43 @@ config CONFIG_UMOUNT | |||
323 | the tool to use. If you enabled the 'mount' utility, you almost certainly | 323 | the tool to use. If you enabled the 'mount' utility, you almost certainly |
324 | also want to enable 'umount'. | 324 | also want to enable 'umount'. |
325 | 325 | ||
326 | config CONFIG_FEATURE_MOUNT_FORCE | ||
327 | bool " Support forced filesystem unmounting" | ||
328 | default n | ||
329 | depends on CONFIG_UMOUNT | ||
330 | help | ||
331 | This allows you to _force_ a filesystem to be umounted. This is generally | ||
332 | only useful when you want to get rid of an unreachable NFS system. | ||
333 | |||
334 | comment "Common options for mount/umount" | 326 | comment "Common options for mount/umount" |
335 | depends on CONFIG_MOUNT || CONFIG_UMOUNT | 327 | depends on CONFIG_MOUNT || CONFIG_UMOUNT |
336 | 328 | ||
337 | config CONFIG_FEATURE_MOUNT_LOOP | 329 | config CONFIG_FEATURE_MOUNT_LOOP |
338 | bool " Support for loop devices" | 330 | bool " Support loopback mounts" |
339 | default n | 331 | default n |
340 | depends on CONFIG_MOUNT || CONFIG_UMOUNT | 332 | depends on CONFIG_MOUNT || CONFIG_UMOUNT |
341 | help | 333 | help |
342 | Enabling this feature allows automatic loopback mounts, meaning you can mount | 334 | Enabling this feature allows automatic mounting of files (containing |
343 | filesystems contained in normal files as well as in block devices. The mount | 335 | filesystem images) via the linux kernel's loopback devices. The mount |
344 | and umount commands will detect you are trying to mount a file instead of a | 336 | command will detect you are trying to mount a file instead of a block |
345 | block device, and transparently associate it with a loopback device (and free | 337 | device, and transparently associate the file with a loopback device. |
346 | the loopback device on unmount) for you. | 338 | The umount command will also free that loopback device. |
347 | 339 | ||
348 | You can still use the 'losetup' utility and mount the loopback device yourself | 340 | You can still use the 'losetup' utility (to manually associate files |
349 | if you need to do something advanced, such as specify an offset or cryptographic | 341 | with loop devices) if you need to do something advanced, such as |
350 | options to the loopback device. | 342 | specify an offset or cryptographic options to the loopback device. |
351 | 343 | (If you don't want umount to free the loop device, use "umount -D".) | |
352 | config CONFIG_FEATURE_MOUNT_LOOP_MAX | ||
353 | int " max number of loop devices" | ||
354 | default 7 | ||
355 | depends on CONFIG_FEATURE_MOUNT_LOOP | ||
356 | help | ||
357 | This option sets the highest numbered loop device to be used | ||
358 | automatically by the '-o loop' feature of mount. | ||
359 | 344 | ||
360 | config CONFIG_FEATURE_MTAB_SUPPORT | 345 | config CONFIG_FEATURE_MTAB_SUPPORT |
361 | bool " Support for a /etc/mtab file (instead of symlink to /proc/mounts)" | 346 | bool " Support for the old /etc/mtab file" |
362 | default n | 347 | default n |
363 | depends on CONFIG_MOUNT || CONFIG_UMOUNT | 348 | depends on CONFIG_MOUNT || CONFIG_UMOUNT |
364 | help | 349 | help |
365 | If your root filesystem is writable and you wish to have the 'mount' | 350 | Historically, Unix systems kept track of the currently mounted |
366 | utility create an mtab file listing the filesystems which have been | 351 | partitions in the file "/etc/mtab". These days, the kernel exports |
367 | mounted then you should enable this option. Most people that use | 352 | the list of currently mounted partitions in "/proc/mounts", rendering |
368 | BusyBox have a read-only root filesystem, so they will leave this | 353 | the old mtab file obsolete. (In modern systems, /etc/mtab should be |
369 | option disabled and BusyBox will use the /proc/mounts file. | 354 | a symlink to /proc/mounts.) |
370 | 355 | ||
371 | Note that even non-embedded developers probably want to have /etc/mtab | 356 | The only reason to have mount maintain an /etc/mtab file itself is if |
372 | be a symlink to /proc/mounts, since otherwise mtab can get out of sync | 357 | your stripped-down embedded system does not have a /proc directory. |
373 | with the real kernel mount state in numerous ways. | 358 | If you must use this, keep in mind it's inherently brittle (for |
359 | example a mount under chroot won't update it), can't handle modern | ||
360 | features like separate per-process filesystem namespaces, requires | ||
361 | that your /etc directory be writeable, tends to get easily confused | ||
362 | by --bind or --move mounts, and so on. (In brief: avoid.) | ||
374 | 363 | ||
375 | config CONFIG_READPROFILE | 364 | config CONFIG_READPROFILE |
376 | bool "readprofile" | 365 | bool "readprofile" |