Contents of /tags/mkinitrd-6_2_0/util-linux/Config.in
Parent Directory | Revision Log
Revision 816 -
(show annotations)
(download)
Fri Apr 24 18:33:46 2009 UTC (15 years, 5 months ago) by niro
Original Path: trunk/mkinitrd-magellan/busybox/util-linux/Config.in
File size: 23482 byte(s)
Fri Apr 24 18:33:46 2009 UTC (15 years, 5 months ago) by niro
Original Path: trunk/mkinitrd-magellan/busybox/util-linux/Config.in
File size: 23482 byte(s)
-updated to busybox-1.13.4
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 | config BLKID |
9 | bool "blkid" |
10 | default n |
11 | select VOLUMEID |
12 | help |
13 | Lists labels and UUIDs of all filesystems. |
14 | WARNING: |
15 | With all submodules selected, it will add ~8k to busybox. |
16 | |
17 | config DMESG |
18 | bool "dmesg" |
19 | default n |
20 | help |
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. |
28 | |
29 | config FEATURE_DMESG_PRETTY |
30 | bool "Pretty dmesg output" |
31 | default y |
32 | depends on DMESG |
33 | help |
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 |
36 | "<#>". |
37 | |
38 | With this option you will see: |
39 | # dmesg |
40 | Linux version 2.6.17.4 ..... |
41 | BIOS-provided physical RAM map: |
42 | BIOS-e820: 0000000000000000 - 000000000009f000 (usable) |
43 | |
44 | Without this option you will see: |
45 | # dmesg |
46 | <5>Linux version 2.6.17.4 ..... |
47 | <6>BIOS-provided physical RAM map: |
48 | <6> BIOS-e820: 0000000000000000 - 000000000009f000 (usable) |
49 | |
50 | config FBSET |
51 | bool "fbset" |
52 | default n |
53 | help |
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. |
58 | |
59 | config FEATURE_FBSET_FANCY |
60 | bool "Turn on extra fbset options" |
61 | default n |
62 | depends on FBSET |
63 | help |
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 |
67 | options. |
68 | |
69 | config FEATURE_FBSET_READMODE |
70 | bool "Turn on fbset readmode support" |
71 | default n |
72 | depends on FBSET |
73 | help |
74 | This option allows fbset to read the video mode database stored by |
75 | default as /etc/fb.modes, which can be used to set frame buffer |
76 | device to pre-defined video modes. |
77 | |
78 | config FDFLUSH |
79 | bool "fdflush" |
80 | default n |
81 | help |
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 |
88 | leave this disabled. |
89 | |
90 | config FDFORMAT |
91 | bool "fdformat" |
92 | default n |
93 | help |
94 | fdformat is used to low-level format a floppy disk. |
95 | |
96 | config FDISK |
97 | bool "fdisk" |
98 | default n |
99 | help |
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. |
104 | |
105 | config FDISK_SUPPORT_LARGE_DISKS |
106 | bool "Support over 4GB disks" |
107 | default y |
108 | depends on FDISK |
109 | help |
110 | Enable this option to support large disks > 4GB. |
111 | |
112 | config FEATURE_FDISK_WRITABLE |
113 | bool "Write support" |
114 | default y |
115 | depends on FDISK |
116 | help |
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. |
120 | |
121 | config FEATURE_AIX_LABEL |
122 | bool "Support AIX disklabels" |
123 | default n |
124 | depends on FDISK && FEATURE_FDISK_WRITABLE |
125 | help |
126 | Enabling this option allows you to create or change AIX disklabels. |
127 | Most people can safely leave this option disabled. |
128 | |
129 | config FEATURE_SGI_LABEL |
130 | bool "Support SGI disklabels" |
131 | default n |
132 | depends on FDISK && FEATURE_FDISK_WRITABLE |
133 | help |
134 | Enabling this option allows you to create or change SGI disklabels. |
135 | Most people can safely leave this option disabled. |
136 | |
137 | config FEATURE_SUN_LABEL |
138 | bool "Support SUN disklabels" |
139 | default n |
140 | depends on FDISK && FEATURE_FDISK_WRITABLE |
141 | help |
142 | Enabling this option allows you to create or change SUN disklabels. |
143 | Most people can safely leave this option disabled. |
144 | |
145 | config FEATURE_OSF_LABEL |
146 | bool "Support BSD disklabels" |
147 | default n |
148 | depends on FDISK && FEATURE_FDISK_WRITABLE |
149 | help |
150 | Enabling this option allows you to create or change BSD disklabels |
151 | and define and edit BSD disk slices. |
152 | |
153 | config FEATURE_FDISK_ADVANCED |
154 | bool "Support expert mode" |
155 | default n |
156 | depends on FDISK && FEATURE_FDISK_WRITABLE |
157 | help |
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. |
162 | |
163 | config FINDFS |
164 | bool "findfs" |
165 | default n |
166 | select VOLUMEID |
167 | help |
168 | Prints the name of a filesystem with given label or UUID. |
169 | WARNING: |
170 | With all submodules selected, it will add ~8k to busybox. |
171 | |
172 | config FREERAMDISK |
173 | bool "freeramdisk" |
174 | default n |
175 | help |
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 |
181 | this disabled. |
182 | |
183 | config FSCK_MINIX |
184 | bool "fsck_minix" |
185 | default n |
186 | help |
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 |
192 | filesystem. |
193 | |
194 | config MKFS_MINIX |
195 | bool "mkfs_minix" |
196 | default n |
197 | help |
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. |
201 | |
202 | comment "Minix filesystem support" |
203 | depends on FSCK_MINIX || MKFS_MINIX |
204 | |
205 | config FEATURE_MINIX2 |
206 | bool "Support Minix fs v2 (fsck_minix/mkfs_minix)" |
207 | default y |
208 | depends on FSCK_MINIX || MKFS_MINIX |
209 | help |
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. |
213 | |
214 | config GETOPT |
215 | bool "getopt" |
216 | default n |
217 | help |
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. |
224 | |
225 | config HEXDUMP |
226 | bool "hexdump" |
227 | default n |
228 | help |
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. |
231 | |
232 | config FEATURE_HEXDUMP_REVERSE |
233 | bool "Support -R, reverse of 'hexdump -Cv'" |
234 | default n |
235 | depends on HEXDUMP |
236 | help |
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. |
241 | |
242 | config HD |
243 | bool "hd" |
244 | default n |
245 | select HEXDUMP |
246 | help |
247 | hd is an alias to hexdump -C. |
248 | |
249 | config HWCLOCK |
250 | bool "hwclock" |
251 | default n |
252 | help |
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. |
257 | |
258 | config FEATURE_HWCLOCK_LONG_OPTIONS |
259 | bool "Support long options (--hctosys,...)" |
260 | default n |
261 | depends on HWCLOCK && GETOPT_LONG |
262 | help |
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. |
266 | |
267 | config FEATURE_HWCLOCK_ADJTIME_FHS |
268 | bool "Use FHS /var/lib/hwclock/adjtime" |
269 | default y |
270 | depends on HWCLOCK |
271 | help |
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. |
276 | |
277 | pathname.com/fhs/pub/fhs-2.3.html#VARLIBHWCLOCKSTATEDIRECTORYFORHWCLO |
278 | |
279 | config IPCRM |
280 | bool "ipcrm" |
281 | default n |
282 | select FEATURE_SUID |
283 | help |
284 | The ipcrm utility allows the removal of System V interprocess |
285 | communication (IPC) objects and the associated data structures |
286 | from the system. |
287 | |
288 | config IPCS |
289 | bool "ipcs" |
290 | default n |
291 | select FEATURE_SUID |
292 | help |
293 | The ipcs utility is used to provide information on the currently |
294 | allocated System V interprocess (IPC) objects in the system. |
295 | |
296 | config LOSETUP |
297 | bool "losetup" |
298 | default n |
299 | help |
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. |
303 | |
304 | config MDEV |
305 | bool "mdev" |
306 | default n |
307 | help |
308 | mdev is a mini-udev implementation for dynamically creating device |
309 | nodes in the /dev directory. |
310 | |
311 | For more information, please see docs/mdev.txt |
312 | |
313 | config FEATURE_MDEV_CONF |
314 | bool "Support /etc/mdev.conf" |
315 | default n |
316 | depends on MDEV |
317 | help |
318 | Add support for the mdev config file to control ownership and |
319 | permissions of the device nodes. |
320 | |
321 | For more information, please see docs/mdev.txt |
322 | |
323 | config FEATURE_MDEV_RENAME |
324 | bool "Support subdirs/symlinks" |
325 | default n |
326 | depends on FEATURE_MDEV_CONF |
327 | help |
328 | Add support for renaming devices and creating symlinks. |
329 | |
330 | For more information, please see docs/mdev.txt |
331 | |
332 | config FEATURE_MDEV_RENAME_REGEXP |
333 | bool "Support regular expressions substitutions when renaming device" |
334 | default n |
335 | depends on FEATURE_MDEV_RENAME |
336 | help |
337 | Add support for regular expressions substitutions when renaming |
338 | device. |
339 | |
340 | config FEATURE_MDEV_EXEC |
341 | bool "Support command execution at device addition/removal" |
342 | default n |
343 | depends on FEATURE_MDEV_CONF |
344 | help |
345 | This adds support for an optional field to /etc/mdev.conf for |
346 | executing commands when devices are created/removed. |
347 | |
348 | For more information, please see docs/mdev.txt |
349 | |
350 | config FEATURE_MDEV_LOAD_FIRMWARE |
351 | bool "Support loading of firmwares" |
352 | default n |
353 | depends on MDEV |
354 | help |
355 | Some devices need to load firmware before they can be usable. |
356 | |
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. |
360 | |
361 | config MKSWAP |
362 | bool "mkswap" |
363 | default n |
364 | help |
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. |
373 | |
374 | config FEATURE_MKSWAP_V0 |
375 | bool "Version 0 support" |
376 | default n |
377 | depends on MKSWAP |
378 | # depends on MKSWAP && DEPRECATED |
379 | help |
380 | Enable support for the old v0 style. |
381 | If your kernel is older than 2.1.117, then v0 support is the |
382 | only option. |
383 | |
384 | config MORE |
385 | bool "more" |
386 | default n |
387 | help |
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. |
393 | |
394 | config FEATURE_USE_TERMIOS |
395 | bool "Use termios to manipulate the screen" |
396 | default y |
397 | depends on MORE || TOP |
398 | help |
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. |
404 | |
405 | config VOLUMEID |
406 | bool #No description makes it a hidden option |
407 | default n |
408 | |
409 | config FEATURE_VOLUMEID_EXT |
410 | bool "Ext filesystem" |
411 | default n |
412 | depends on VOLUMEID |
413 | help |
414 | TODO |
415 | |
416 | config FEATURE_VOLUMEID_REISERFS |
417 | bool "Reiser filesystem" |
418 | default n |
419 | depends on VOLUMEID |
420 | help |
421 | TODO |
422 | |
423 | config FEATURE_VOLUMEID_FAT |
424 | bool "fat filesystem" |
425 | default n |
426 | depends on VOLUMEID |
427 | help |
428 | TODO |
429 | |
430 | config FEATURE_VOLUMEID_HFS |
431 | bool "hfs filesystem" |
432 | default n |
433 | depends on VOLUMEID |
434 | help |
435 | TODO |
436 | |
437 | config FEATURE_VOLUMEID_JFS |
438 | bool "jfs filesystem" |
439 | default n |
440 | depends on VOLUMEID |
441 | help |
442 | TODO |
443 | |
444 | ### config FEATURE_VOLUMEID_UFS |
445 | ### bool "ufs filesystem" |
446 | ### default n |
447 | ### depends on VOLUMEID |
448 | ### help |
449 | ### TODO |
450 | |
451 | config FEATURE_VOLUMEID_XFS |
452 | bool "xfs filesystem" |
453 | default n |
454 | depends on VOLUMEID |
455 | help |
456 | TODO |
457 | |
458 | config FEATURE_VOLUMEID_NTFS |
459 | bool "ntfs filesystem" |
460 | default n |
461 | depends on VOLUMEID |
462 | help |
463 | TODO |
464 | |
465 | config FEATURE_VOLUMEID_ISO9660 |
466 | bool "iso9660 filesystem" |
467 | default n |
468 | depends on VOLUMEID |
469 | help |
470 | TODO |
471 | |
472 | config FEATURE_VOLUMEID_UDF |
473 | bool "udf filesystem" |
474 | default n |
475 | depends on VOLUMEID |
476 | help |
477 | TODO |
478 | |
479 | config FEATURE_VOLUMEID_LUKS |
480 | bool "luks filesystem" |
481 | default n |
482 | depends on VOLUMEID |
483 | help |
484 | TODO |
485 | |
486 | config FEATURE_VOLUMEID_LINUXSWAP |
487 | bool "linux swap filesystem" |
488 | default n |
489 | depends on VOLUMEID |
490 | help |
491 | TODO |
492 | |
493 | ### config FEATURE_VOLUMEID_LVM |
494 | ### bool "lvm" |
495 | ### default n |
496 | ### depends on VOLUMEID |
497 | ### help |
498 | ### TODO |
499 | |
500 | config FEATURE_VOLUMEID_CRAMFS |
501 | bool "cramfs filesystem" |
502 | default n |
503 | depends on VOLUMEID |
504 | help |
505 | TODO |
506 | |
507 | ### config FEATURE_VOLUMEID_HPFS |
508 | ### bool "hpfs filesystem" |
509 | ### default n |
510 | ### depends on VOLUMEID |
511 | ### help |
512 | ### TODO |
513 | |
514 | config FEATURE_VOLUMEID_ROMFS |
515 | bool "romfs filesystem" |
516 | default n |
517 | depends on VOLUMEID |
518 | help |
519 | TODO |
520 | |
521 | config FEATURE_VOLUMEID_SYSV |
522 | bool "sysv filesystem" |
523 | default n |
524 | depends on VOLUMEID |
525 | help |
526 | TODO |
527 | |
528 | ### config FEATURE_VOLUMEID_MINIX |
529 | ### bool "minix filesystem" |
530 | ### default n |
531 | ### depends on VOLUMEID |
532 | ### help |
533 | ### TODO |
534 | |
535 | ### These only detect partition tables - not used (yet?) |
536 | ### config FEATURE_VOLUMEID_MAC |
537 | ### bool "mac filesystem" |
538 | ### default n |
539 | ### depends on VOLUMEID |
540 | ### help |
541 | ### TODO |
542 | ### |
543 | ### config FEATURE_VOLUMEID_MSDOS |
544 | ### bool "msdos filesystem" |
545 | ### default n |
546 | ### depends on VOLUMEID |
547 | ### help |
548 | ### TODO |
549 | |
550 | config FEATURE_VOLUMEID_OCFS2 |
551 | bool "ocfs2 filesystem" |
552 | default n |
553 | depends on VOLUMEID |
554 | help |
555 | TODO |
556 | |
557 | ### config FEATURE_VOLUMEID_HIGHPOINTRAID |
558 | ### bool "highpoint raid" |
559 | ### default n |
560 | ### depends on VOLUMEID |
561 | ### help |
562 | ### TODO |
563 | |
564 | ### config FEATURE_VOLUMEID_ISWRAID |
565 | ### bool "intel raid" |
566 | ### default n |
567 | ### depends on VOLUMEID |
568 | ### help |
569 | ### TODO |
570 | |
571 | ### config FEATURE_VOLUMEID_LSIRAID |
572 | ### bool "lsi raid" |
573 | ### default n |
574 | ### depends on VOLUMEID |
575 | ### help |
576 | ### TODO |
577 | |
578 | ### config FEATURE_VOLUMEID_VIARAID |
579 | ### bool "via raid" |
580 | ### default n |
581 | ### depends on VOLUMEID |
582 | ### help |
583 | ### TODO |
584 | |
585 | ### config FEATURE_VOLUMEID_SILICONRAID |
586 | ### bool "silicon raid" |
587 | ### default n |
588 | ### depends on VOLUMEID |
589 | ### help |
590 | ### TODO |
591 | |
592 | ### config FEATURE_VOLUMEID_NVIDIARAID |
593 | ### bool "nvidia raid" |
594 | ### default n |
595 | ### depends on VOLUMEID |
596 | ### help |
597 | ### TODO |
598 | |
599 | ### config FEATURE_VOLUMEID_PROMISERAID |
600 | ### bool "promise raid" |
601 | ### default n |
602 | ### depends on VOLUMEID |
603 | ### help |
604 | ### TODO |
605 | |
606 | config FEATURE_VOLUMEID_LINUXRAID |
607 | bool "linuxraid" |
608 | default n |
609 | depends on VOLUMEID |
610 | help |
611 | TODO |
612 | |
613 | config MOUNT |
614 | bool "mount" |
615 | default n |
616 | help |
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 |
622 | the 'mount' utility. |
623 | |
624 | config FEATURE_MOUNT_FAKE |
625 | bool "Support option -f" |
626 | default n |
627 | depends on MOUNT |
628 | help |
629 | Enable support for faking a file system mount. |
630 | |
631 | config FEATURE_MOUNT_VERBOSE |
632 | bool "Support option -v" |
633 | default n |
634 | depends on MOUNT |
635 | help |
636 | Enable multi-level -v[vv...] verbose messages. Useful if you |
637 | debug mount problems and want to see what is exactly passed |
638 | to the kernel. |
639 | |
640 | config FEATURE_MOUNT_HELPERS |
641 | bool "Support mount helpers" |
642 | default n |
643 | depends on MOUNT |
644 | help |
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. |
651 | |
652 | config FEATURE_MOUNT_LABEL |
653 | bool "Support specifiying devices by label or UUID" |
654 | default n |
655 | depends on MOUNT |
656 | select VOLUMEID |
657 | help |
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. |
660 | |
661 | config FEATURE_MOUNT_NFS |
662 | bool "Support mounting NFS file systems" |
663 | default n |
664 | depends on MOUNT |
665 | select FEATURE_HAVE_RPC |
666 | select FEATURE_SYSLOG |
667 | help |
668 | Enable mounting of NFS file systems. |
669 | |
670 | config FEATURE_MOUNT_CIFS |
671 | bool "Support mounting CIFS/SMB file systems" |
672 | default n |
673 | depends on MOUNT |
674 | help |
675 | Enable support for samba mounts. |
676 | |
677 | config FEATURE_MOUNT_FLAGS |
678 | depends on MOUNT |
679 | bool "Support lots of -o flags in mount" |
680 | default y |
681 | help |
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. |
686 | |
687 | config FEATURE_MOUNT_FSTAB |
688 | depends on MOUNT |
689 | bool "Support /etc/fstab and -a" |
690 | default y |
691 | help |
692 | Support mount all and looking for files in /etc/fstab. |
693 | |
694 | config PIVOT_ROOT |
695 | bool "pivot_root" |
696 | default n |
697 | help |
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'. |
702 | |
703 | Note: This is for initrd in linux 2.4. Under initramfs (introduced |
704 | in linux 2.6) use switch_root instead. |
705 | |
706 | config RDATE |
707 | bool "rdate" |
708 | default n |
709 | help |
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 |
713 | systems. |
714 | |
715 | config RDEV |
716 | bool "rdev" |
717 | default n |
718 | help |
719 | Print the device node associated with the filesystem mounted at '/'. |
720 | |
721 | config READPROFILE |
722 | bool "readprofile" |
723 | default n |
724 | help |
725 | This allows you to parse /proc/profile for basic profiling. |
726 | |
727 | config RTCWAKE |
728 | bool "rtcwake" |
729 | default n |
730 | help |
731 | Enter a system sleep state until specified wakeup time. |
732 | |
733 | config SCRIPT |
734 | bool "script" |
735 | default n |
736 | help |
737 | The script makes typescript of terminal session. |
738 | |
739 | config SETARCH |
740 | bool "setarch" |
741 | default n |
742 | help |
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...). |
747 | |
748 | config SWAPONOFF |
749 | bool "swaponoff" |
750 | default n |
751 | help |
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 |
757 | option disabled. |
758 | |
759 | config FEATURE_SWAPON_PRI |
760 | bool "Support priority option -p" |
761 | default n |
762 | depends on SWAPONOFF |
763 | help |
764 | Enable support for setting swap device priority in swapon. |
765 | |
766 | config SWITCH_ROOT |
767 | bool "switch_root" |
768 | default n |
769 | help |
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.) |
773 | |
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. |
780 | |
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. |
784 | |
785 | config UMOUNT |
786 | bool "umount" |
787 | default n |
788 | help |
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'. |
793 | |
794 | config FEATURE_UMOUNT_ALL |
795 | bool "Support option -a" |
796 | default n |
797 | depends on UMOUNT |
798 | help |
799 | Support -a option to unmount all currently mounted filesystems. |
800 | |
801 | comment "Common options for mount/umount" |
802 | depends on MOUNT || UMOUNT |
803 | |
804 | config FEATURE_MOUNT_LOOP |
805 | bool "Support loopback mounts" |
806 | default n |
807 | depends on MOUNT || UMOUNT |
808 | help |
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 |
814 | device. |
815 | |
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".) |
820 | |
821 | config FEATURE_MTAB_SUPPORT |
822 | bool "Support for the old /etc/mtab file" |
823 | default n |
824 | depends on MOUNT || UMOUNT |
825 | select FEATURE_MOUNT_FAKE |
826 | help |
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.) |
832 | |
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.) |
841 | |
842 | About the only reason to use this is if you've removed /proc from |
843 | your kernel. |
844 | |
845 | endmenu |