]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # File system configuration | |
3 | # | |
4 | ||
5 | menu "File systems" | |
6 | ||
9361401e DH |
7 | if BLOCK |
8 | ||
1da177e4 LT |
9 | config EXT2_FS |
10 | tristate "Second extended fs support" | |
11 | help | |
12 | Ext2 is a standard Linux file system for hard disks. | |
13 | ||
14 | To compile this file system support as a module, choose M here: the | |
15 | module will be called ext2. Be aware however that the file system | |
16 | of your root partition (the one containing the directory /) cannot | |
17 | be compiled as a module, and so this could be dangerous. | |
18 | ||
19 | If unsure, say Y. | |
20 | ||
21 | config EXT2_FS_XATTR | |
22 | bool "Ext2 extended attributes" | |
23 | depends on EXT2_FS | |
24 | help | |
25 | Extended attributes are name:value pairs associated with inodes by | |
26 | the kernel or by users (see the attr(5) manual page, or visit | |
27 | <http://acl.bestbits.at/> for details). | |
28 | ||
29 | If unsure, say N. | |
30 | ||
31 | config EXT2_FS_POSIX_ACL | |
32 | bool "Ext2 POSIX Access Control Lists" | |
33 | depends on EXT2_FS_XATTR | |
b84c2157 | 34 | select FS_POSIX_ACL |
1da177e4 LT |
35 | help |
36 | Posix Access Control Lists (ACLs) support permissions for users and | |
37 | groups beyond the owner/group/world scheme. | |
38 | ||
39 | To learn more about Access Control Lists, visit the Posix ACLs for | |
40 | Linux website <http://acl.bestbits.at/>. | |
41 | ||
42 | If you don't know what Access Control Lists are, say N | |
43 | ||
44 | config EXT2_FS_SECURITY | |
45 | bool "Ext2 Security Labels" | |
46 | depends on EXT2_FS_XATTR | |
47 | help | |
48 | Security labels support alternative access control models | |
49 | implemented by security modules like SELinux. This option | |
50 | enables an extended attribute handler for file security | |
51 | labels in the ext2 filesystem. | |
52 | ||
53 | If you are not using a security module that requires using | |
54 | extended attributes for file security labels, say N. | |
55 | ||
6d79125b CO |
56 | config EXT2_FS_XIP |
57 | bool "Ext2 execute in place support" | |
0c426f26 | 58 | depends on EXT2_FS && MMU |
6d79125b CO |
59 | help |
60 | Execute in place can be used on memory-backed block devices. If you | |
61 | enable this option, you can select to mount block devices which are | |
62 | capable of this feature without using the page cache. | |
63 | ||
64 | If you do not use a block device that is capable of using this, | |
65 | or if unsure, say N. | |
66 | ||
67 | config FS_XIP | |
68 | # execute in place | |
69 | bool | |
70 | depends on EXT2_FS_XIP | |
71 | default y | |
72 | ||
1da177e4 LT |
73 | config EXT3_FS |
74 | tristate "Ext3 journalling file system support" | |
b4e40a51 | 75 | select JBD |
1da177e4 | 76 | help |
cc2e2767 | 77 | This is the journalling version of the Second extended file system |
1da177e4 LT |
78 | (often called ext3), the de facto standard Linux file system |
79 | (method to organize files on a storage device) for hard disks. | |
80 | ||
cc2e2767 | 81 | The journalling code included in this driver means you do not have |
1da177e4 LT |
82 | to run e2fsck (file system checker) on your file systems after a |
83 | crash. The journal keeps track of any changes that were being made | |
84 | at the time the system crashed, and can ensure that your file system | |
85 | is consistent without the need for a lengthy check. | |
86 | ||
87 | Other than adding the journal to the file system, the on-disk format | |
88 | of ext3 is identical to ext2. It is possible to freely switch | |
89 | between using the ext3 driver and the ext2 driver, as long as the | |
90 | file system has been cleanly unmounted, or e2fsck is run on the file | |
91 | system. | |
92 | ||
93 | To add a journal on an existing ext2 file system or change the | |
94 | behavior of ext3 file systems, you can use the tune2fs utility ("man | |
95 | tune2fs"). To modify attributes of files and directories on ext3 | |
96 | file systems, use chattr ("man chattr"). You need to be using | |
97 | e2fsprogs version 1.20 or later in order to create ext3 journals | |
98 | (available at <http://sourceforge.net/projects/e2fsprogs/>). | |
99 | ||
100 | To compile this file system support as a module, choose M here: the | |
101 | module will be called ext3. Be aware however that the file system | |
102 | of your root partition (the one containing the directory /) cannot | |
103 | be compiled as a module, and so this may be dangerous. | |
104 | ||
105 | config EXT3_FS_XATTR | |
106 | bool "Ext3 extended attributes" | |
107 | depends on EXT3_FS | |
108 | default y | |
109 | help | |
110 | Extended attributes are name:value pairs associated with inodes by | |
111 | the kernel or by users (see the attr(5) manual page, or visit | |
112 | <http://acl.bestbits.at/> for details). | |
113 | ||
114 | If unsure, say N. | |
115 | ||
116 | You need this for POSIX ACL support on ext3. | |
117 | ||
118 | config EXT3_FS_POSIX_ACL | |
119 | bool "Ext3 POSIX Access Control Lists" | |
120 | depends on EXT3_FS_XATTR | |
b84c2157 | 121 | select FS_POSIX_ACL |
1da177e4 LT |
122 | help |
123 | Posix Access Control Lists (ACLs) support permissions for users and | |
124 | groups beyond the owner/group/world scheme. | |
125 | ||
126 | To learn more about Access Control Lists, visit the Posix ACLs for | |
127 | Linux website <http://acl.bestbits.at/>. | |
128 | ||
129 | If you don't know what Access Control Lists are, say N | |
130 | ||
131 | config EXT3_FS_SECURITY | |
132 | bool "Ext3 Security Labels" | |
133 | depends on EXT3_FS_XATTR | |
134 | help | |
135 | Security labels support alternative access control models | |
136 | implemented by security modules like SELinux. This option | |
137 | enables an extended attribute handler for file security | |
138 | labels in the ext3 filesystem. | |
139 | ||
140 | If you are not using a security module that requires using | |
141 | extended attributes for file security labels, say N. | |
142 | ||
143 | config JBD | |
1da177e4 | 144 | tristate |
1da177e4 | 145 | help |
cc2e2767 | 146 | This is a generic journalling layer for block devices. It is |
b4e40a51 MF |
147 | currently used by the ext3 and OCFS2 file systems, but it could |
148 | also be used to add journal support to other file systems or block | |
149 | devices such as RAID or LVM. | |
1da177e4 | 150 | |
b4e40a51 MF |
151 | If you are using the ext3 or OCFS2 file systems, you need to |
152 | say Y here. If you are not using ext3 OCFS2 then you will probably | |
153 | want to say N. | |
1da177e4 LT |
154 | |
155 | To compile this device as a module, choose M here: the module will be | |
b4e40a51 MF |
156 | called jbd. If you are compiling ext3 or OCFS2 into the kernel, |
157 | you cannot compile this code as a module. | |
1da177e4 LT |
158 | |
159 | config JBD_DEBUG | |
160 | bool "JBD (ext3) debugging support" | |
161 | depends on JBD | |
162 | help | |
163 | If you are using the ext3 journaled file system (or potentially any | |
164 | other file system/device using JBD), this option allows you to | |
165 | enable debugging output while the system is running, in order to | |
166 | help track down any problems you are having. By default the | |
167 | debugging output will be turned off. | |
168 | ||
169 | If you select Y here, then you will be able to turn on debugging | |
170 | with "echo N > /proc/sys/fs/jbd-debug", where N is a number between | |
171 | 1 and 5, the higher the number, the more debugging output is | |
172 | generated. To turn debugging off again, do | |
173 | "echo 0 > /proc/sys/fs/jbd-debug". | |
174 | ||
175 | config FS_MBCACHE | |
176 | # Meta block cache for Extended Attributes (ext2/ext3) | |
177 | tristate | |
178 | depends on EXT2_FS_XATTR || EXT3_FS_XATTR | |
179 | default y if EXT2_FS=y || EXT3_FS=y | |
180 | default m if EXT2_FS=m || EXT3_FS=m | |
181 | ||
182 | config REISERFS_FS | |
183 | tristate "Reiserfs support" | |
184 | help | |
185 | Stores not just filenames but the files themselves in a balanced | |
cc2e2767 | 186 | tree. Uses journalling. |
1da177e4 LT |
187 | |
188 | Balanced trees are more efficient than traditional file system | |
189 | architectural foundations. | |
190 | ||
191 | In general, ReiserFS is as fast as ext2, but is very efficient with | |
192 | large directories and small files. Additional patches are needed | |
193 | for NFS and quotas, please see <http://www.namesys.com/> for links. | |
194 | ||
195 | It is more easily extended to have features currently found in | |
196 | database and keyword search systems than block allocation based file | |
197 | systems are. The next version will be so extended, and will support | |
198 | plugins consistent with our motto ``It takes more than a license to | |
199 | make source code open.'' | |
200 | ||
201 | Read <http://www.namesys.com/> to learn more about reiserfs. | |
202 | ||
203 | Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. | |
204 | ||
205 | If you like it, you can pay us to add new features to it that you | |
206 | need, buy a support contract, or pay us to port it to another OS. | |
207 | ||
208 | config REISERFS_CHECK | |
209 | bool "Enable reiserfs debug mode" | |
210 | depends on REISERFS_FS | |
211 | help | |
212 | If you set this to Y, then ReiserFS will perform every check it can | |
213 | possibly imagine of its internal consistency throughout its | |
214 | operation. It will also go substantially slower. More than once we | |
215 | have forgotten that this was on, and then gone despondent over the | |
216 | latest benchmarks.:-) Use of this option allows our team to go all | |
217 | out in checking for consistency when debugging without fear of its | |
218 | effect on end users. If you are on the verge of sending in a bug | |
219 | report, say Y and you might get a useful error message. Almost | |
220 | everyone should say N. | |
221 | ||
222 | config REISERFS_PROC_INFO | |
223 | bool "Stats in /proc/fs/reiserfs" | |
224 | depends on REISERFS_FS | |
225 | help | |
226 | Create under /proc/fs/reiserfs a hierarchy of files, displaying | |
227 | various ReiserFS statistics and internal data at the expense of | |
228 | making your kernel or module slightly larger (+8 KB). This also | |
229 | increases the amount of kernel memory required for each mount. | |
230 | Almost everyone but ReiserFS developers and people fine-tuning | |
231 | reiserfs or tracing problems should say N. | |
232 | ||
233 | config REISERFS_FS_XATTR | |
234 | bool "ReiserFS extended attributes" | |
235 | depends on REISERFS_FS | |
236 | help | |
237 | Extended attributes are name:value pairs associated with inodes by | |
238 | the kernel or by users (see the attr(5) manual page, or visit | |
239 | <http://acl.bestbits.at/> for details). | |
240 | ||
241 | If unsure, say N. | |
242 | ||
243 | config REISERFS_FS_POSIX_ACL | |
244 | bool "ReiserFS POSIX Access Control Lists" | |
245 | depends on REISERFS_FS_XATTR | |
b84c2157 | 246 | select FS_POSIX_ACL |
1da177e4 LT |
247 | help |
248 | Posix Access Control Lists (ACLs) support permissions for users and | |
249 | groups beyond the owner/group/world scheme. | |
250 | ||
251 | To learn more about Access Control Lists, visit the Posix ACLs for | |
252 | Linux website <http://acl.bestbits.at/>. | |
253 | ||
254 | If you don't know what Access Control Lists are, say N | |
255 | ||
256 | config REISERFS_FS_SECURITY | |
257 | bool "ReiserFS Security Labels" | |
258 | depends on REISERFS_FS_XATTR | |
259 | help | |
260 | Security labels support alternative access control models | |
261 | implemented by security modules like SELinux. This option | |
262 | enables an extended attribute handler for file security | |
263 | labels in the ReiserFS filesystem. | |
264 | ||
265 | If you are not using a security module that requires using | |
266 | extended attributes for file security labels, say N. | |
267 | ||
268 | config JFS_FS | |
269 | tristate "JFS filesystem support" | |
270 | select NLS | |
271 | help | |
272 | This is a port of IBM's Journaled Filesystem . More information is | |
273 | available in the file <file:Documentation/filesystems/jfs.txt>. | |
274 | ||
275 | If you do not intend to use the JFS filesystem, say N. | |
276 | ||
277 | config JFS_POSIX_ACL | |
278 | bool "JFS POSIX Access Control Lists" | |
279 | depends on JFS_FS | |
b84c2157 | 280 | select FS_POSIX_ACL |
1da177e4 LT |
281 | help |
282 | Posix Access Control Lists (ACLs) support permissions for users and | |
283 | groups beyond the owner/group/world scheme. | |
284 | ||
285 | To learn more about Access Control Lists, visit the Posix ACLs for | |
286 | Linux website <http://acl.bestbits.at/>. | |
287 | ||
288 | If you don't know what Access Control Lists are, say N | |
289 | ||
290 | config JFS_SECURITY | |
291 | bool "JFS Security Labels" | |
292 | depends on JFS_FS | |
293 | help | |
294 | Security labels support alternative access control models | |
295 | implemented by security modules like SELinux. This option | |
296 | enables an extended attribute handler for file security | |
297 | labels in the jfs filesystem. | |
298 | ||
299 | If you are not using a security module that requires using | |
300 | extended attributes for file security labels, say N. | |
301 | ||
302 | config JFS_DEBUG | |
303 | bool "JFS debugging" | |
304 | depends on JFS_FS | |
305 | help | |
306 | If you are experiencing any problems with the JFS filesystem, say | |
307 | Y here. This will result in additional debugging messages to be | |
308 | written to the system log. Under normal circumstances, this | |
309 | results in very little overhead. | |
310 | ||
311 | config JFS_STATISTICS | |
312 | bool "JFS statistics" | |
313 | depends on JFS_FS | |
314 | help | |
315 | Enabling this option will cause statistics from the JFS file system | |
316 | to be made available to the user in the /proc/fs/jfs/ directory. | |
317 | ||
318 | config FS_POSIX_ACL | |
319 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs) | |
320 | # | |
321 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). | |
322 | # Never use this symbol for ifdefs. | |
323 | # | |
324 | bool | |
b84c2157 | 325 | default n |
1da177e4 LT |
326 | |
327 | source "fs/xfs/Kconfig" | |
f7825dcf | 328 | source "fs/gfs2/Kconfig" |
1da177e4 | 329 | |
b4e40a51 | 330 | config OCFS2_FS |
02ed8416 MF |
331 | tristate "OCFS2 file system support" |
332 | depends on NET && SYSFS | |
b4e40a51 MF |
333 | select CONFIGFS_FS |
334 | select JBD | |
335 | select CRC32 | |
336 | select INET | |
337 | help | |
338 | OCFS2 is a general purpose extent based shared disk cluster file | |
339 | system with many similarities to ext3. It supports 64 bit inode | |
340 | numbers, and has automatically extending metadata groups which may | |
341 | also make it attractive for non-clustered use. | |
342 | ||
343 | You'll want to install the ocfs2-tools package in order to at least | |
344 | get "mount.ocfs2". | |
345 | ||
346 | Project web page: http://oss.oracle.com/projects/ocfs2 | |
347 | Tools web page: http://oss.oracle.com/projects/ocfs2-tools | |
348 | OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ | |
349 | ||
350 | Note: Features which OCFS2 does not support yet: | |
351 | - extended attributes | |
b4e40a51 MF |
352 | - shared writeable mmap |
353 | - loopback is supported, but data written will not | |
354 | be cluster coherent. | |
355 | - quotas | |
356 | - cluster aware flock | |
357 | - Directory change notification (F_NOTIFY) | |
358 | - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease) | |
359 | - POSIX ACLs | |
360 | - readpages / writepages (not user visible) | |
361 | ||
2b388c67 JB |
362 | config OCFS2_DEBUG_MASKLOG |
363 | bool "OCFS2 logging support" | |
364 | depends on OCFS2_FS | |
365 | default y | |
366 | help | |
367 | The ocfs2 filesystem has an extensive logging system. The system | |
368 | allows selection of events to log via files in /sys/o2cb/logmask/. | |
369 | This option will enlarge your kernel, but it allows debugging of | |
370 | ocfs2 filesystem issues. | |
371 | ||
1da177e4 LT |
372 | config MINIX_FS |
373 | tristate "Minix fs support" | |
374 | help | |
375 | Minix is a simple operating system used in many classes about OS's. | |
376 | The minix file system (method to organize files on a hard disk | |
377 | partition or a floppy disk) was the original file system for Linux, | |
378 | but has been superseded by the second extended file system ext2fs. | |
379 | You don't want to use the minix file system on your hard disk | |
380 | because of certain built-in restrictions, but it is sometimes found | |
381 | on older Linux floppy disks. This option will enlarge your kernel | |
382 | by about 28 KB. If unsure, say N. | |
383 | ||
384 | To compile this file system support as a module, choose M here: the | |
385 | module will be called minix. Note that the file system of your root | |
386 | partition (the one containing the directory /) cannot be compiled as | |
387 | a module. | |
388 | ||
389 | config ROMFS_FS | |
390 | tristate "ROM file system support" | |
391 | ---help--- | |
392 | This is a very small read-only file system mainly intended for | |
393 | initial ram disks of installation disks, but it could be used for | |
394 | other read-only media as well. Read | |
395 | <file:Documentation/filesystems/romfs.txt> for details. | |
396 | ||
397 | To compile this file system support as a module, choose M here: the | |
398 | module will be called romfs. Note that the file system of your | |
399 | root partition (the one containing the directory /) cannot be a | |
400 | module. | |
401 | ||
402 | If you don't know whether you need it, then you don't need it: | |
403 | answer N. | |
404 | ||
9361401e DH |
405 | endif |
406 | ||
0eeca283 RL |
407 | config INOTIFY |
408 | bool "Inotify file change notification support" | |
409 | default y | |
410 | ---help--- | |
2d9048e2 AG |
411 | Say Y here to enable inotify support. Inotify is a file change |
412 | notification system and a replacement for dnotify. Inotify fixes | |
413 | numerous shortcomings in dnotify and introduces several new features | |
414 | including multiple file events, one-shot support, and unmount | |
3de11748 RL |
415 | notification. |
416 | ||
417 | For more information, see Documentation/filesystems/inotify.txt | |
0eeca283 RL |
418 | |
419 | If unsure, say Y. | |
420 | ||
2d9048e2 AG |
421 | config INOTIFY_USER |
422 | bool "Inotify support for userspace" | |
423 | depends on INOTIFY | |
424 | default y | |
425 | ---help--- | |
426 | Say Y here to enable inotify support for userspace, including the | |
427 | associated system calls. Inotify allows monitoring of both files and | |
428 | directories via a single open fd. Events are read from the file | |
429 | descriptor, which is also select()- and poll()-able. | |
430 | ||
431 | For more information, see Documentation/filesystems/inotify.txt | |
432 | ||
0eeca283 RL |
433 | If unsure, say Y. |
434 | ||
1da177e4 LT |
435 | config QUOTA |
436 | bool "Quota support" | |
437 | help | |
438 | If you say Y here, you will be able to set per user limits for disk | |
439 | usage (also called disk quotas). Currently, it works for the | |
440 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
441 | quotas for which you don't need to run quotacheck(8) after an unclean | |
919532a5 AB |
442 | shutdown. |
443 | For further details, read the Quota mini-HOWTO, available from | |
1da177e4 LT |
444 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
445 | with the quota tools. Probably the quota support is only useful for | |
446 | multi user systems. If unsure, say N. | |
447 | ||
448 | config QFMT_V1 | |
449 | tristate "Old quota format support" | |
450 | depends on QUOTA | |
451 | help | |
452 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
453 | you have quota working and you don't want to convert to new quota | |
454 | format say Y here. | |
455 | ||
456 | config QFMT_V2 | |
457 | tristate "Quota format v2 support" | |
458 | depends on QUOTA | |
459 | help | |
460 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
919532a5 | 461 | need this functionality say Y here. |
1da177e4 LT |
462 | |
463 | config QUOTACTL | |
464 | bool | |
465 | depends on XFS_QUOTA || QUOTA | |
466 | default y | |
467 | ||
468 | config DNOTIFY | |
469 | bool "Dnotify support" if EMBEDDED | |
470 | default y | |
471 | help | |
472 | Dnotify is a directory-based per-fd file change notification system | |
473 | that uses signals to communicate events to user-space. There exist | |
474 | superior alternatives, but some applications may still rely on | |
475 | dnotify. | |
476 | ||
477 | Because of this, if unsure, say Y. | |
478 | ||
479 | config AUTOFS_FS | |
480 | tristate "Kernel automounter support" | |
481 | help | |
482 | The automounter is a tool to automatically mount remote file systems | |
483 | on demand. This implementation is partially kernel-based to reduce | |
484 | overhead in the already-mounted case; this is unlike the BSD | |
485 | automounter (amd), which is a pure user space daemon. | |
486 | ||
487 | To use the automounter you need the user-space tools from the autofs | |
488 | package; you can find the location in <file:Documentation/Changes>. | |
489 | You also want to answer Y to "NFS file system support", below. | |
490 | ||
491 | If you want to use the newer version of the automounter with more | |
492 | features, say N here and say Y to "Kernel automounter v4 support", | |
493 | below. | |
494 | ||
495 | To compile this support as a module, choose M here: the module will be | |
496 | called autofs. | |
497 | ||
498 | If you are not a part of a fairly large, distributed network, you | |
499 | probably do not need an automounter, and can say N here. | |
500 | ||
501 | config AUTOFS4_FS | |
502 | tristate "Kernel automounter version 4 support (also supports v3)" | |
503 | help | |
504 | The automounter is a tool to automatically mount remote file systems | |
505 | on demand. This implementation is partially kernel-based to reduce | |
506 | overhead in the already-mounted case; this is unlike the BSD | |
507 | automounter (amd), which is a pure user space daemon. | |
508 | ||
509 | To use the automounter you need the user-space tools from | |
510 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also | |
511 | want to answer Y to "NFS file system support", below. | |
512 | ||
513 | To compile this support as a module, choose M here: the module will be | |
514 | called autofs4. You will need to add "alias autofs autofs4" to your | |
515 | modules configuration file. | |
516 | ||
517 | If you are not a part of a fairly large, distributed network or | |
518 | don't have a laptop which needs to dynamically reconfigure to the | |
519 | local network, you probably do not need an automounter, and can say | |
520 | N here. | |
521 | ||
04578f17 MS |
522 | config FUSE_FS |
523 | tristate "Filesystem in Userspace support" | |
524 | help | |
525 | With FUSE it is possible to implement a fully functional filesystem | |
526 | in a userspace program. | |
527 | ||
528 | There's also companion library: libfuse. This library along with | |
529 | utilities is available from the FUSE homepage: | |
530 | <http://fuse.sourceforge.net/> | |
531 | ||
909021ea MS |
532 | See <file:Documentation/filesystems/fuse.txt> for more information. |
533 | See <file:Documentation/Changes> for needed library/utility version. | |
534 | ||
04578f17 MS |
535 | If you want to develop a userspace FS, or if you want to use |
536 | a filesystem based on FUSE, answer Y or M. | |
537 | ||
9361401e | 538 | if BLOCK |
1da177e4 LT |
539 | menu "CD-ROM/DVD Filesystems" |
540 | ||
541 | config ISO9660_FS | |
542 | tristate "ISO 9660 CDROM file system support" | |
543 | help | |
544 | This is the standard file system used on CD-ROMs. It was previously | |
545 | known as "High Sierra File System" and is called "hsfs" on other | |
546 | Unix systems. The so-called Rock-Ridge extensions which allow for | |
547 | long Unix filenames and symbolic links are also supported by this | |
548 | driver. If you have a CD-ROM drive and want to do more with it than | |
549 | just listen to audio CDs and watch its LEDs, say Y (and read | |
550 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, | |
551 | available from <http://www.tldp.org/docs.html#howto>), thereby | |
552 | enlarging your kernel by about 27 KB; otherwise say N. | |
553 | ||
554 | To compile this file system support as a module, choose M here: the | |
555 | module will be called isofs. | |
556 | ||
557 | config JOLIET | |
558 | bool "Microsoft Joliet CDROM extensions" | |
559 | depends on ISO9660_FS | |
560 | select NLS | |
561 | help | |
562 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system | |
563 | which allows for long filenames in unicode format (unicode is the | |
564 | new 16 bit character code, successor to ASCII, which encodes the | |
565 | characters of almost all languages of the world; see | |
566 | <http://www.unicode.org/> for more information). Say Y here if you | |
567 | want to be able to read Joliet CD-ROMs under Linux. | |
568 | ||
569 | config ZISOFS | |
570 | bool "Transparent decompression extension" | |
571 | depends on ISO9660_FS | |
572 | select ZLIB_INFLATE | |
573 | help | |
574 | This is a Linux-specific extension to RockRidge which lets you store | |
575 | data in compressed form on a CD-ROM and have it transparently | |
576 | decompressed when the CD-ROM is accessed. See | |
577 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools | |
578 | necessary to create such a filesystem. Say Y here if you want to be | |
579 | able to read such compressed CD-ROMs. | |
580 | ||
581 | config ZISOFS_FS | |
582 | # for fs/nls/Config.in | |
583 | tristate | |
584 | depends on ZISOFS | |
585 | default ISO9660_FS | |
586 | ||
587 | config UDF_FS | |
588 | tristate "UDF file system support" | |
589 | help | |
590 | This is the new file system used on some CD-ROMs and DVDs. Say Y if | |
591 | you intend to mount DVD discs or CDRW's written in packet mode, or | |
592 | if written to by other UDF utilities, such as DirectCD. | |
593 | Please read <file:Documentation/filesystems/udf.txt>. | |
594 | ||
595 | To compile this file system support as a module, choose M here: the | |
596 | module will be called udf. | |
597 | ||
598 | If unsure, say N. | |
599 | ||
600 | config UDF_NLS | |
601 | bool | |
602 | default y | |
603 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) | |
604 | ||
605 | endmenu | |
9361401e | 606 | endif |
1da177e4 | 607 | |
9361401e | 608 | if BLOCK |
1da177e4 LT |
609 | menu "DOS/FAT/NT Filesystems" |
610 | ||
611 | config FAT_FS | |
612 | tristate | |
613 | select NLS | |
614 | help | |
615 | If you want to use one of the FAT-based file systems (the MS-DOS and | |
616 | VFAT (Windows 95) file systems), then you must say Y or M here | |
617 | to include FAT support. You will then be able to mount partitions or | |
618 | diskettes with FAT-based file systems and transparently access the | |
619 | files on them, i.e. MSDOS files will look and behave just like all | |
620 | other Unix files. | |
621 | ||
622 | This FAT support is not a file system in itself, it only provides | |
623 | the foundation for the other file systems. You will have to say Y or | |
624 | M to at least one of "MSDOS fs support" or "VFAT fs support" in | |
625 | order to make use of it. | |
626 | ||
627 | Another way to read and write MSDOS floppies and hard drive | |
628 | partitions from within Linux (but not transparently) is with the | |
629 | mtools ("man mtools") program suite. You don't need to say Y here in | |
630 | order to do that. | |
631 | ||
632 | If you need to move large files on floppies between a DOS and a | |
633 | Linux box, say Y here, mount the floppy under Linux with an MSDOS | |
634 | file system and use GNU tar's M option. GNU tar is a program | |
635 | available for Unix and DOS ("man tar" or "info tar"). | |
636 | ||
637 | It is now also becoming possible to read and write compressed FAT | |
638 | file systems; read <file:Documentation/filesystems/fat_cvf.txt> for | |
639 | details. | |
640 | ||
641 | The FAT support will enlarge your kernel by about 37 KB. If unsure, | |
642 | say Y. | |
643 | ||
644 | To compile this as a module, choose M here: the module will be called | |
645 | fat. Note that if you compile the FAT support as a module, you | |
646 | cannot compile any of the FAT-based file systems into the kernel | |
647 | -- they will have to be modules as well. | |
648 | ||
649 | config MSDOS_FS | |
650 | tristate "MSDOS fs support" | |
651 | select FAT_FS | |
652 | help | |
653 | This allows you to mount MSDOS partitions of your hard drive (unless | |
654 | they are compressed; to access compressed MSDOS partitions under | |
655 | Linux, you can either use the DOS emulator DOSEMU, described in the | |
656 | DOSEMU-HOWTO, available from | |
657 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in | |
658 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you | |
659 | intend to use dosemu with a non-compressed MSDOS partition, say Y | |
660 | here) and MSDOS floppies. This means that file access becomes | |
661 | transparent, i.e. the MSDOS files look and behave just like all | |
662 | other Unix files. | |
663 | ||
664 | If you have Windows 95 or Windows NT installed on your MSDOS | |
665 | partitions, you should use the VFAT file system (say Y to "VFAT fs | |
666 | support" below), or you will not be able to see the long filenames | |
667 | generated by Windows 95 / Windows NT. | |
668 | ||
669 | This option will enlarge your kernel by about 7 KB. If unsure, | |
670 | answer Y. This will only work if you said Y to "DOS FAT fs support" | |
671 | as well. To compile this as a module, choose M here: the module will | |
672 | be called msdos. | |
673 | ||
674 | config VFAT_FS | |
675 | tristate "VFAT (Windows-95) fs support" | |
676 | select FAT_FS | |
677 | help | |
678 | This option provides support for normal Windows file systems with | |
679 | long filenames. That includes non-compressed FAT-based file systems | |
680 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix | |
681 | programs from the mtools package. | |
682 | ||
683 | The VFAT support enlarges your kernel by about 10 KB and it only | |
684 | works if you said Y to the "DOS FAT fs support" above. Please read | |
685 | the file <file:Documentation/filesystems/vfat.txt> for details. If | |
686 | unsure, say Y. | |
687 | ||
688 | To compile this as a module, choose M here: the module will be called | |
689 | vfat. | |
690 | ||
691 | config FAT_DEFAULT_CODEPAGE | |
692 | int "Default codepage for FAT" | |
693 | depends on MSDOS_FS || VFAT_FS | |
694 | default 437 | |
695 | help | |
696 | This option should be set to the codepage of your FAT filesystems. | |
697 | It can be overridden with the "codepage" mount option. | |
698 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
699 | ||
700 | config FAT_DEFAULT_IOCHARSET | |
701 | string "Default iocharset for FAT" | |
702 | depends on VFAT_FS | |
703 | default "iso8859-1" | |
704 | help | |
705 | Set this to the default input/output character set you'd | |
706 | like FAT to use. It should probably match the character set | |
707 | that most of your FAT filesystems use, and can be overridden | |
708 | with the "iocharset" mount option for FAT filesystems. | |
709 | Note that "utf8" is not recommended for FAT filesystems. | |
710 | If unsure, you shouldn't set "utf8" here. | |
711 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
712 | ||
713 | config NTFS_FS | |
714 | tristate "NTFS file system support" | |
715 | select NLS | |
716 | help | |
717 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
718 | ||
719 | Saying Y or M here enables read support. There is partial, but | |
720 | safe, write support available. For write support you must also | |
721 | say Y to "NTFS write support" below. | |
722 | ||
723 | There are also a number of user-space tools available, called | |
724 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
725 | without NTFS support enabled in the kernel. | |
726 | ||
727 | This is a rewrite from scratch of Linux NTFS support and replaced | |
728 | the old NTFS code starting with Linux 2.5.11. A backport to | |
729 | the Linux 2.4 kernel series is separately available as a patch | |
730 | from the project web site. | |
731 | ||
732 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
733 | and <http://linux-ntfs.sourceforge.net/>. | |
734 | ||
735 | To compile this file system support as a module, choose M here: the | |
736 | module will be called ntfs. | |
737 | ||
738 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
739 | Linux on your computer it is safe to say N. | |
740 | ||
741 | config NTFS_DEBUG | |
742 | bool "NTFS debugging support" | |
743 | depends on NTFS_FS | |
744 | help | |
745 | If you are experiencing any problems with the NTFS file system, say | |
746 | Y here. This will result in additional consistency checks to be | |
747 | performed by the driver as well as additional debugging messages to | |
748 | be written to the system log. Note that debugging messages are | |
749 | disabled by default. To enable them, supply the option debug_msgs=1 | |
750 | at the kernel command line when booting the kernel or as an option | |
751 | to insmod when loading the ntfs module. Once the driver is active, | |
752 | you can enable debugging messages by doing (as root): | |
753 | echo 1 > /proc/sys/fs/ntfs-debug | |
754 | Replacing the "1" with "0" would disable debug messages. | |
755 | ||
756 | If you leave debugging messages disabled, this results in little | |
757 | overhead, but enabling debug messages results in very significant | |
758 | slowdown of the system. | |
759 | ||
760 | When reporting bugs, please try to have available a full dump of | |
761 | debugging messages while the misbehaviour was occurring. | |
762 | ||
763 | config NTFS_RW | |
764 | bool "NTFS write support" | |
765 | depends on NTFS_FS | |
766 | help | |
767 | This enables the partial, but safe, write support in the NTFS driver. | |
768 | ||
769 | The only supported operation is overwriting existing files, without | |
770 | changing the file length. No file or directory creation, deletion or | |
771 | renaming is possible. Note only non-resident files can be written to | |
772 | so you may find that some very small files (<500 bytes or so) cannot | |
773 | be written to. | |
774 | ||
775 | While we cannot guarantee that it will not damage any data, we have | |
776 | so far not received a single report where the driver would have | |
777 | damaged someones data so we assume it is perfectly safe to use. | |
778 | ||
779 | Note: While write support is safe in this version (a rewrite from | |
780 | scratch of the NTFS support), it should be noted that the old NTFS | |
781 | write support, included in Linux 2.5.10 and before (since 1997), | |
782 | is not safe. | |
783 | ||
784 | This is currently useful with TopologiLinux. TopologiLinux is run | |
785 | on top of any DOS/Microsoft Windows system without partitioning your | |
786 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
787 | need its own partition. For more information see | |
788 | <http://topologi-linux.sourceforge.net/> | |
789 | ||
790 | It is perfectly safe to say N here. | |
791 | ||
792 | endmenu | |
9361401e | 793 | endif |
1da177e4 LT |
794 | |
795 | menu "Pseudo filesystems" | |
796 | ||
797 | config PROC_FS | |
69755652 PA |
798 | bool "/proc file system support" if EMBEDDED |
799 | default y | |
1da177e4 LT |
800 | help |
801 | This is a virtual file system providing information about the status | |
802 | of the system. "Virtual" means that it doesn't take up any space on | |
803 | your hard disk: the files are created on the fly by the kernel when | |
804 | you try to access them. Also, you cannot read the files with older | |
805 | version of the program less: you need to use more or cat. | |
806 | ||
807 | It's totally cool; for example, "cat /proc/interrupts" gives | |
808 | information about what the different IRQs are used for at the moment | |
809 | (there is a small number of Interrupt ReQuest lines in your computer | |
810 | that are used by the attached devices to gain the CPU's attention -- | |
811 | often a source of trouble if two devices are mistakenly configured | |
812 | to use the same IRQ). The program procinfo to display some | |
813 | information about your system gathered from the /proc file system. | |
814 | ||
815 | Before you can use the /proc file system, it has to be mounted, | |
816 | meaning it has to be given a location in the directory hierarchy. | |
817 | That location should be /proc. A command such as "mount -t proc proc | |
818 | /proc" or the equivalent line in /etc/fstab does the job. | |
819 | ||
820 | The /proc file system is explained in the file | |
821 | <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage | |
822 | ("man 5 proc"). | |
823 | ||
824 | This option will enlarge your kernel by about 67 KB. Several | |
825 | programs depend on this, so everyone should say Y here. | |
826 | ||
827 | config PROC_KCORE | |
828 | bool "/proc/kcore support" if !ARM | |
829 | depends on PROC_FS && MMU | |
830 | ||
666bfddb VG |
831 | config PROC_VMCORE |
832 | bool "/proc/vmcore support (EXPERIMENTAL)" | |
05970d47 | 833 | depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP |
68250ba5 | 834 | default y |
666bfddb VG |
835 | help |
836 | Exports the dump image of crashed kernel in ELF format. | |
837 | ||
b89a8171 EB |
838 | config PROC_SYSCTL |
839 | bool "Sysctl support (/proc/sys)" if EMBEDDED | |
840 | depends on PROC_FS | |
841 | select SYSCTL | |
842 | default y | |
843 | ---help--- | |
844 | The sysctl interface provides a means of dynamically changing | |
845 | certain kernel parameters and variables on the fly without requiring | |
846 | a recompile of the kernel or reboot of the system. The primary | |
847 | interface is through /proc/sys. If you say Y here a tree of | |
848 | modifiable sysctl entries will be generated beneath the | |
849 | /proc/sys directory. They are explained in the files | |
850 | in <file:Documentation/sysctl/>. Note that enabling this | |
851 | option will enlarge the kernel by at least 8 KB. | |
852 | ||
853 | As it is generally a good thing, you should say Y here unless | |
854 | building a kernel for install/rescue disks or your system is very | |
855 | limited in memory. | |
856 | ||
1da177e4 LT |
857 | config SYSFS |
858 | bool "sysfs file system support" if EMBEDDED | |
859 | default y | |
860 | help | |
861 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
862 | export internal kernel objects, their attributes, and their | |
863 | relationships to one another. | |
864 | ||
865 | Users can use sysfs to ascertain useful information about the running | |
866 | kernel, such as the devices the kernel has discovered on each bus and | |
867 | which driver each is bound to. sysfs can also be used to tune devices | |
868 | and other kernel subsystems. | |
869 | ||
870 | Some system agents rely on the information in sysfs to operate. | |
871 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
872 | delegating policy decisions, like persistantly naming devices. | |
873 | ||
874 | sysfs is currently used by the block subsystem to mount the root | |
875 | partition. If sysfs is disabled you must specify the boot device on | |
876 | the kernel boot command line via its major and minor numbers. For | |
877 | example, "root=03:01" for /dev/hda1. | |
878 | ||
879 | Designers of embedded systems may wish to say N here to conserve space. | |
880 | ||
1da177e4 LT |
881 | config TMPFS |
882 | bool "Virtual memory file system support (former shm fs)" | |
883 | help | |
884 | Tmpfs is a file system which keeps all files in virtual memory. | |
885 | ||
886 | Everything in tmpfs is temporary in the sense that no files will be | |
887 | created on your hard drive. The files live in memory and swap | |
888 | space. If you unmount a tmpfs instance, everything stored therein is | |
889 | lost. | |
890 | ||
891 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
892 | ||
39f0247d AG |
893 | config TMPFS_POSIX_ACL |
894 | bool "Tmpfs POSIX Access Control Lists" | |
895 | depends on TMPFS | |
896 | select GENERIC_ACL | |
897 | help | |
898 | POSIX Access Control Lists (ACLs) support permissions for users and | |
899 | groups beyond the owner/group/world scheme. | |
900 | ||
901 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
902 | Linux website <http://acl.bestbits.at/>. | |
903 | ||
904 | If you don't know what Access Control Lists are, say N. | |
905 | ||
1da177e4 LT |
906 | config HUGETLBFS |
907 | bool "HugeTLB file system support" | |
0d078f6f | 908 | depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN |
dda27d1a AO |
909 | help |
910 | hugetlbfs is a filesystem backing for HugeTLB pages, based on | |
911 | ramfs. For architectures that support it, say Y here and read | |
912 | <file:Documentation/vm/hugetlbpage.txt> for details. | |
913 | ||
914 | If unsure, say N. | |
1da177e4 LT |
915 | |
916 | config HUGETLB_PAGE | |
917 | def_bool HUGETLBFS | |
918 | ||
919 | config RAMFS | |
920 | bool | |
921 | default y | |
922 | ---help--- | |
923 | Ramfs is a file system which keeps all files in RAM. It allows | |
924 | read and write access. | |
925 | ||
926 | It is more of an programming example than a useable file system. If | |
927 | you need a file system which lives in RAM with limit checking use | |
928 | tmpfs. | |
929 | ||
930 | To compile this as a module, choose M here: the module will be called | |
931 | ramfs. | |
932 | ||
7063fbf2 JB |
933 | config CONFIGFS_FS |
934 | tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)" | |
65714b91 | 935 | depends on SYSFS && EXPERIMENTAL |
7063fbf2 JB |
936 | help |
937 | configfs is a ram-based filesystem that provides the converse | |
938 | of sysfs's functionality. Where sysfs is a filesystem-based | |
939 | view of kernel objects, configfs is a filesystem-based manager | |
940 | of kernel objects, or config_items. | |
941 | ||
942 | Both sysfs and configfs can and should exist together on the | |
943 | same system. One is not a replacement for the other. | |
944 | ||
1da177e4 LT |
945 | endmenu |
946 | ||
947 | menu "Miscellaneous filesystems" | |
948 | ||
949 | config ADFS_FS | |
950 | tristate "ADFS file system support (EXPERIMENTAL)" | |
9361401e | 951 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
952 | help |
953 | The Acorn Disc Filing System is the standard file system of the | |
954 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
955 | systems and the Acorn Archimedes range of machines. If you say Y | |
956 | here, Linux will be able to read from ADFS partitions on hard drives | |
957 | and from ADFS-formatted floppy discs. If you also want to be able to | |
958 | write to those devices, say Y to "ADFS write support" below. | |
959 | ||
960 | The ADFS partition should be the first partition (i.e., | |
961 | /dev/[hs]d?1) on each of your drives. Please read the file | |
962 | <file:Documentation/filesystems/adfs.txt> for further details. | |
963 | ||
964 | To compile this code as a module, choose M here: the module will be | |
965 | called adfs. | |
966 | ||
967 | If unsure, say N. | |
968 | ||
969 | config ADFS_FS_RW | |
970 | bool "ADFS write support (DANGEROUS)" | |
971 | depends on ADFS_FS | |
972 | help | |
973 | If you say Y here, you will be able to write to ADFS partitions on | |
974 | hard drives and ADFS-formatted floppy disks. This is experimental | |
975 | codes, so if you're unsure, say N. | |
976 | ||
977 | config AFFS_FS | |
978 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
9361401e | 979 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
980 | help |
981 | The Fast File System (FFS) is the common file system used on hard | |
982 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
983 | if you want to be able to read and write files from and to an Amiga | |
984 | FFS partition on your hard drive. Amiga floppies however cannot be | |
985 | read with this driver due to an incompatibility of the floppy | |
986 | controller used in an Amiga and the standard floppy controller in | |
987 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
988 | and <file:fs/affs/Changes>. | |
989 | ||
990 | With this driver you can also mount disk files used by Bernd | |
991 | Schmidt's Un*X Amiga Emulator | |
992 | (<http://www.freiburg.linux.de/~uae/>). | |
993 | If you want to do this, you will also need to say Y or M to "Loop | |
994 | device support", above. | |
995 | ||
996 | To compile this file system support as a module, choose M here: the | |
997 | module will be called affs. If unsure, say N. | |
998 | ||
237fead6 MH |
999 | config ECRYPT_FS |
1000 | tristate "eCrypt filesystem layer support (EXPERIMENTAL)" | |
1001 | depends on EXPERIMENTAL && KEYS && CRYPTO | |
1002 | help | |
1003 | Encrypted filesystem that operates on the VFS layer. See | |
1004 | <file:Documentation/ecryptfs.txt> to learn more about | |
1005 | eCryptfs. Userspace components are required and can be | |
1006 | obtained from <http://ecryptfs.sf.net>. | |
1007 | ||
1008 | To compile this file system support as a module, choose M here: the | |
1009 | module will be called ecryptfs. | |
1010 | ||
1da177e4 LT |
1011 | config HFS_FS |
1012 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
9361401e | 1013 | depends on BLOCK && EXPERIMENTAL |
878129a3 | 1014 | select NLS |
1da177e4 LT |
1015 | help |
1016 | If you say Y here, you will be able to mount Macintosh-formatted | |
1017 | floppy disks and hard drive partitions with full read-write access. | |
1018 | Please read <file:fs/hfs/HFS.txt> to learn about the available mount | |
1019 | options. | |
1020 | ||
1021 | To compile this file system support as a module, choose M here: the | |
1022 | module will be called hfs. | |
1023 | ||
1024 | config HFSPLUS_FS | |
1025 | tristate "Apple Extended HFS file system support" | |
9361401e | 1026 | depends on BLOCK |
1da177e4 LT |
1027 | select NLS |
1028 | select NLS_UTF8 | |
1029 | help | |
1030 | If you say Y here, you will be able to mount extended format | |
1031 | Macintosh-formatted hard drive partitions with full read-write access. | |
1032 | ||
1033 | This file system is often called HFS+ and was introduced with | |
1034 | MacOS 8. It includes all Mac specific filesystem data such as | |
1035 | data forks and creator codes, but it also has several UNIX | |
1036 | style features such as file ownership and permissions. | |
1037 | ||
1038 | config BEFS_FS | |
1039 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
9361401e | 1040 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1041 | select NLS |
1042 | help | |
1043 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
1044 | BeOS. Notable features include support for arbitrary attributes | |
1045 | on files and directories, and database-like indeces on selected | |
1046 | attributes. (Also note that this driver doesn't make those features | |
1047 | available at this time). It is a 64 bit filesystem, so it supports | |
44c09201 | 1048 | extremely large volumes and files. |
1da177e4 LT |
1049 | |
1050 | If you use this filesystem, you should also say Y to at least one | |
1051 | of the NLS (native language support) options below. | |
1052 | ||
1053 | If you don't know what this is about, say N. | |
1054 | ||
1055 | To compile this as a module, choose M here: the module will be | |
1056 | called befs. | |
1057 | ||
1058 | config BEFS_DEBUG | |
1059 | bool "Debug BeFS" | |
1060 | depends on BEFS_FS | |
1061 | help | |
1062 | If you say Y here, you can use the 'debug' mount option to enable | |
1063 | debugging output from the driver. | |
1064 | ||
1065 | config BFS_FS | |
1066 | tristate "BFS file system support (EXPERIMENTAL)" | |
9361401e | 1067 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1068 | help |
1069 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
1070 | allow the bootloader access to the kernel image and other important | |
1071 | files during the boot process. It is usually mounted under /stand | |
1072 | and corresponds to the slice marked as "STAND" in the UnixWare | |
1073 | partition. You should say Y if you want to read or write the files | |
1074 | on your /stand slice from within Linux. You then also need to say Y | |
1075 | to "UnixWare slices support", below. More information about the BFS | |
1076 | file system is contained in the file | |
1077 | <file:Documentation/filesystems/bfs.txt>. | |
1078 | ||
1079 | If you don't know what this is about, say N. | |
1080 | ||
1081 | To compile this as a module, choose M here: the module will be called | |
1082 | bfs. Note that the file system of your root partition (the one | |
1083 | containing the directory /) cannot be compiled as a module. | |
1084 | ||
1085 | ||
1086 | ||
1087 | config EFS_FS | |
1088 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
9361401e | 1089 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1090 | help |
1091 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
1092 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
1093 | uses the XFS file system for hard disk partitions however). | |
1094 | ||
1095 | This implementation only offers read-only access. If you don't know | |
1096 | what all this is about, it's safe to say N. For more information | |
1097 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
1098 | ||
1099 | To compile the EFS file system support as a module, choose M here: the | |
1100 | module will be called efs. | |
1101 | ||
1102 | config JFFS_FS | |
1103 | tristate "Journalling Flash File System (JFFS) support" | |
9361401e | 1104 | depends on MTD && BLOCK |
1da177e4 | 1105 | help |
cc2e2767 | 1106 | JFFS is the Journalling Flash File System developed by Axis |
1da177e4 LT |
1107 | Communications in Sweden, aimed at providing a crash/powerdown-safe |
1108 | file system for disk-less embedded devices. Further information is | |
1109 | available at (<http://developer.axis.com/software/jffs/>). | |
1110 | ||
1111 | config JFFS_FS_VERBOSE | |
1112 | int "JFFS debugging verbosity (0 = quiet, 3 = noisy)" | |
1113 | depends on JFFS_FS | |
1114 | default "0" | |
1115 | help | |
1116 | Determines the verbosity level of the JFFS debugging messages. | |
1117 | ||
1118 | config JFFS_PROC_FS | |
1119 | bool "JFFS stats available in /proc filesystem" | |
1120 | depends on JFFS_FS && PROC_FS | |
1121 | help | |
1122 | Enabling this option will cause statistics from mounted JFFS file systems | |
1123 | to be made available to the user in the /proc/fs/jffs/ directory. | |
1124 | ||
1125 | config JFFS2_FS | |
1126 | tristate "Journalling Flash File System v2 (JFFS2) support" | |
1127 | select CRC32 | |
1128 | depends on MTD | |
1129 | help | |
1130 | JFFS2 is the second generation of the Journalling Flash File System | |
1131 | for use on diskless embedded devices. It provides improved wear | |
1132 | levelling, compression and support for hard links. You cannot use | |
1133 | this on normal block devices, only on 'MTD' devices. | |
1134 | ||
1135 | Further information on the design and implementation of JFFS2 is | |
1136 | available at <http://sources.redhat.com/jffs2/>. | |
1137 | ||
1138 | config JFFS2_FS_DEBUG | |
1139 | int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" | |
1140 | depends on JFFS2_FS | |
1141 | default "0" | |
1142 | help | |
1143 | This controls the amount of debugging messages produced by the JFFS2 | |
1144 | code. Set it to zero for use in production systems. For evaluation, | |
1145 | testing and debugging, it's advisable to set it to one. This will | |
1146 | enable a few assertions and will print debugging messages at the | |
1147 | KERN_DEBUG loglevel, where they won't normally be visible. Level 2 | |
1148 | is unlikely to be useful - it enables extra debugging in certain | |
1149 | areas which at one point needed debugging, but when the bugs were | |
1150 | located and fixed, the detailed messages were relegated to level 2. | |
1151 | ||
1152 | If reporting bugs, please try to have available a full dump of the | |
1153 | messages at debug level 1 while the misbehaviour was occurring. | |
1154 | ||
2ba72cb7 DW |
1155 | config JFFS2_FS_WRITEBUFFER |
1156 | bool "JFFS2 write-buffering support" | |
aa98d7cf | 1157 | depends on JFFS2_FS |
2ba72cb7 DW |
1158 | default y |
1159 | help | |
1160 | This enables the write-buffering support in JFFS2. | |
1161 | ||
1162 | This functionality is required to support JFFS2 on the following | |
1163 | types of flash devices: | |
1164 | - NAND flash | |
1165 | - NOR flash with transparent ECC | |
1166 | - DataFlash | |
1167 | ||
1168 | config JFFS2_SUMMARY | |
1169 | bool "JFFS2 summary support (EXPERIMENTAL)" | |
1170 | depends on JFFS2_FS && EXPERIMENTAL | |
1171 | default n | |
1172 | help | |
1173 | This feature makes it possible to use summary information | |
1174 | for faster filesystem mount. | |
1175 | ||
1176 | The summary information can be inserted into a filesystem image | |
1177 | by the utility 'sumtool'. | |
1178 | ||
1179 | If unsure, say 'N'. | |
1180 | ||
1181 | config JFFS2_FS_XATTR | |
1182 | bool "JFFS2 XATTR support (EXPERIMENTAL)" | |
04510dee | 1183 | depends on JFFS2_FS && EXPERIMENTAL |
aa98d7cf KK |
1184 | default n |
1185 | help | |
1186 | Extended attributes are name:value pairs associated with inodes by | |
1187 | the kernel or by users (see the attr(5) manual page, or visit | |
1188 | <http://acl.bestbits.at/> for details). | |
1189 | ||
1190 | If unsure, say N. | |
1191 | ||
1192 | config JFFS2_FS_POSIX_ACL | |
1193 | bool "JFFS2 POSIX Access Control Lists" | |
1194 | depends on JFFS2_FS_XATTR | |
1195 | default y | |
1196 | select FS_POSIX_ACL | |
1197 | help | |
1198 | Posix Access Control Lists (ACLs) support permissions for users and | |
1199 | groups beyond the owner/group/world scheme. | |
1200 | ||
1201 | To learn more about Access Control Lists, visit the Posix ACLs for | |
1202 | Linux website <http://acl.bestbits.at/>. | |
1203 | ||
1204 | If you don't know what Access Control Lists are, say N | |
1205 | ||
1206 | config JFFS2_FS_SECURITY | |
1207 | bool "JFFS2 Security Labels" | |
1208 | depends on JFFS2_FS_XATTR | |
1209 | default y | |
1210 | help | |
1211 | Security labels support alternative access control models | |
1212 | implemented by security modules like SELinux. This option | |
1213 | enables an extended attribute handler for file security | |
1214 | labels in the jffs2 filesystem. | |
1215 | ||
1216 | If you are not using a security module that requires using | |
1217 | extended attributes for file security labels, say N. | |
1218 | ||
1da177e4 LT |
1219 | config JFFS2_COMPRESSION_OPTIONS |
1220 | bool "Advanced compression options for JFFS2" | |
1221 | depends on JFFS2_FS | |
1222 | default n | |
1223 | help | |
1224 | Enabling this option allows you to explicitly choose which | |
1225 | compression modules, if any, are enabled in JFFS2. Removing | |
1226 | compressors and mean you cannot read existing file systems, | |
1227 | and enabling experimental compressors can mean that you | |
1228 | write a file system which cannot be read by a standard kernel. | |
1229 | ||
1230 | If unsure, you should _definitely_ say 'N'. | |
1231 | ||
1232 | config JFFS2_ZLIB | |
1233 | bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS | |
1234 | select ZLIB_INFLATE | |
1235 | select ZLIB_DEFLATE | |
1236 | depends on JFFS2_FS | |
1237 | default y | |
1238 | help | |
1239 | Zlib is designed to be a free, general-purpose, legally unencumbered, | |
182ec4ee | 1240 | lossless data-compression library for use on virtually any computer |
1da177e4 LT |
1241 | hardware and operating system. See <http://www.gzip.org/zlib/> for |
1242 | further information. | |
182ec4ee | 1243 | |
1da177e4 LT |
1244 | Say 'Y' if unsure. |
1245 | ||
1246 | config JFFS2_RTIME | |
1247 | bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS | |
1248 | depends on JFFS2_FS | |
1249 | default y | |
1250 | help | |
1251 | Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. | |
1252 | ||
1253 | config JFFS2_RUBIN | |
1254 | bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS | |
1255 | depends on JFFS2_FS | |
1256 | default n | |
1257 | help | |
1258 | RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. | |
1259 | ||
1260 | choice | |
1261 | prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS | |
1262 | default JFFS2_CMODE_PRIORITY | |
1263 | depends on JFFS2_FS | |
1264 | help | |
182ec4ee | 1265 | You can set here the default compression mode of JFFS2 from |
1da177e4 LT |
1266 | the available compression modes. Don't touch if unsure. |
1267 | ||
1268 | config JFFS2_CMODE_NONE | |
1269 | bool "no compression" | |
1270 | help | |
1271 | Uses no compression. | |
1272 | ||
1273 | config JFFS2_CMODE_PRIORITY | |
1274 | bool "priority" | |
1275 | help | |
cc2e2767 | 1276 | Tries the compressors in a predefined order and chooses the first |
1da177e4 LT |
1277 | successful one. |
1278 | ||
1279 | config JFFS2_CMODE_SIZE | |
1280 | bool "size (EXPERIMENTAL)" | |
1281 | help | |
182ec4ee | 1282 | Tries all compressors and chooses the one which has the smallest |
1da177e4 LT |
1283 | result. |
1284 | ||
1285 | endchoice | |
1286 | ||
1287 | config CRAMFS | |
1288 | tristate "Compressed ROM file system support (cramfs)" | |
9361401e | 1289 | depends on BLOCK |
1da177e4 LT |
1290 | select ZLIB_INFLATE |
1291 | help | |
1292 | Saying Y here includes support for CramFs (Compressed ROM File | |
1293 | System). CramFs is designed to be a simple, small, and compressed | |
1294 | file system for ROM based embedded systems. CramFs is read-only, | |
1295 | limited to 256MB file systems (with 16MB files), and doesn't support | |
1296 | 16/32 bits uid/gid, hard links and timestamps. | |
1297 | ||
1298 | See <file:Documentation/filesystems/cramfs.txt> and | |
1299 | <file:fs/cramfs/README> for further information. | |
1300 | ||
1301 | To compile this as a module, choose M here: the module will be called | |
1302 | cramfs. Note that the root file system (the one containing the | |
1303 | directory /) cannot be compiled as a module. | |
1304 | ||
1305 | If unsure, say N. | |
1306 | ||
1307 | config VXFS_FS | |
1308 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
9361401e | 1309 | depends on BLOCK |
1da177e4 LT |
1310 | help |
1311 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
1312 | file system format. VERITAS VxFS(TM) is the standard file system | |
1313 | of SCO UnixWare (and possibly others) and optionally available | |
1314 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
1315 | Currently only readonly access is supported. | |
1316 | ||
1317 | NOTE: the file system type as used by mount(1), mount(2) and | |
1318 | fstab(5) is 'vxfs' as it describes the file system format, not | |
1319 | the actual driver. | |
1320 | ||
1321 | To compile this as a module, choose M here: the module will be | |
1322 | called freevxfs. If unsure, say N. | |
1323 | ||
1324 | ||
1325 | config HPFS_FS | |
1326 | tristate "OS/2 HPFS file system support" | |
9361401e | 1327 | depends on BLOCK |
1da177e4 LT |
1328 | help |
1329 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
1330 | is the file system used for organizing files on OS/2 hard disk | |
1331 | partitions. Say Y if you want to be able to read files from and | |
1332 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
1333 | floppies however are in regular MSDOS format, so you don't need this | |
1334 | option in order to be able to read them. Read | |
1335 | <file:Documentation/filesystems/hpfs.txt>. | |
1336 | ||
1337 | To compile this file system support as a module, choose M here: the | |
1338 | module will be called hpfs. If unsure, say N. | |
1339 | ||
1340 | ||
1341 | ||
1342 | config QNX4FS_FS | |
1343 | tristate "QNX4 file system support (read only)" | |
9361401e | 1344 | depends on BLOCK |
1da177e4 LT |
1345 | help |
1346 | This is the file system used by the real-time operating systems | |
1347 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
1348 | Further information is available at <http://www.qnx.com/>. | |
1349 | Say Y if you intend to mount QNX hard disks or floppies. | |
1350 | Unless you say Y to "QNX4FS read-write support" below, you will | |
1351 | only be able to read these file systems. | |
1352 | ||
1353 | To compile this file system support as a module, choose M here: the | |
1354 | module will be called qnx4. | |
1355 | ||
1356 | If you don't know whether you need it, then you don't need it: | |
1357 | answer N. | |
1358 | ||
1359 | config QNX4FS_RW | |
1360 | bool "QNX4FS write support (DANGEROUS)" | |
1361 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
1362 | help | |
1363 | Say Y if you want to test write support for QNX4 file systems. | |
1364 | ||
1365 | It's currently broken, so for now: | |
1366 | answer N. | |
1367 | ||
1368 | ||
1369 | ||
1370 | config SYSV_FS | |
1371 | tristate "System V/Xenix/V7/Coherent file system support" | |
9361401e | 1372 | depends on BLOCK |
1da177e4 LT |
1373 | help |
1374 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
1375 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
1376 | here would allow you to read from their floppies and hard disk | |
1377 | partitions. | |
1378 | ||
1379 | If you have floppies or hard disk partitions like that, it is likely | |
1380 | that they contain binaries from those other Unix systems; in order | |
cab00891 | 1381 | to run these binaries, you will want to install linux-abi which is |
1da177e4 LT |
1382 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
1383 | UnixWare, Dell Unix and System V programs under Linux. It is | |
1384 | available via FTP (user: ftp) from | |
1385 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
1386 | NOTE: that will work only for binaries from Intel-based systems; | |
1387 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
1388 | ||
1389 | If you only intend to mount files from some other Unix over the | |
1390 | network using NFS, you don't need the System V file system support | |
1391 | (but you need NFS file system support obviously). | |
1392 | ||
1393 | Note that this option is generally not needed for floppies, since a | |
1394 | good portable way to transport files and directories between unixes | |
1395 | (and even other operating systems) is given by the tar program ("man | |
1396 | tar" or preferably "info tar"). Note also that this option has | |
1397 | nothing whatsoever to do with the option "System V IPC". Read about | |
1398 | the System V file system in | |
1399 | <file:Documentation/filesystems/sysv-fs.txt>. | |
1400 | Saying Y here will enlarge your kernel by about 27 KB. | |
1401 | ||
1402 | To compile this as a module, choose M here: the module will be called | |
1403 | sysv. | |
1404 | ||
1405 | If you haven't heard about all of this before, it's safe to say N. | |
1406 | ||
1407 | ||
1408 | ||
1409 | config UFS_FS | |
1410 | tristate "UFS file system support (read only)" | |
9361401e | 1411 | depends on BLOCK |
1da177e4 LT |
1412 | help |
1413 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
1414 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
1415 | Unixes can create and mount hard disk partitions and diskettes using | |
1416 | this file system as well. Saying Y here will allow you to read from | |
1417 | these partitions; if you also want to write to them, say Y to the | |
1418 | experimental "UFS file system write support", below. Please read the | |
1419 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
1420 | ||
1421 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
1422 | READ-ONLY supported. | |
1423 | ||
1424 | If you only intend to mount files from some other Unix over the | |
1425 | network using NFS, you don't need the UFS file system support (but | |
1426 | you need NFS file system support obviously). | |
1427 | ||
1428 | Note that this option is generally not needed for floppies, since a | |
1429 | good portable way to transport files and directories between unixes | |
1430 | (and even other operating systems) is given by the tar program ("man | |
1431 | tar" or preferably "info tar"). | |
1432 | ||
1433 | When accessing NeXTstep files, you may need to convert them from the | |
1434 | NeXT character set to the Latin1 character set; use the program | |
1435 | recode ("info recode") for this purpose. | |
1436 | ||
1437 | To compile the UFS file system support as a module, choose M here: the | |
1438 | module will be called ufs. | |
1439 | ||
1440 | If you haven't heard about all of this before, it's safe to say N. | |
1441 | ||
1442 | config UFS_FS_WRITE | |
1443 | bool "UFS file system write support (DANGEROUS)" | |
5afb3145 | 1444 | depends on UFS_FS && EXPERIMENTAL |
1da177e4 LT |
1445 | help |
1446 | Say Y here if you want to try writing to UFS partitions. This is | |
1447 | experimental, so you should back up your UFS partitions beforehand. | |
1448 | ||
abf5d15f ED |
1449 | config UFS_DEBUG |
1450 | bool "UFS debugging" | |
1451 | depends on UFS_FS | |
1452 | help | |
1453 | If you are experiencing any problems with the UFS filesystem, say | |
1454 | Y here. This will result in _many_ additional debugging messages to be | |
1455 | written to the system log. | |
1456 | ||
1da177e4 LT |
1457 | endmenu |
1458 | ||
1459 | menu "Network File Systems" | |
1460 | depends on NET | |
1461 | ||
1462 | config NFS_FS | |
1463 | tristate "NFS file system support" | |
1464 | depends on INET | |
1465 | select LOCKD | |
1466 | select SUNRPC | |
b7fa0554 | 1467 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 LT |
1468 | help |
1469 | If you are connected to some other (usually local) Unix computer | |
1470 | (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing | |
1471 | on that computer (the NFS server) using the Network File Sharing | |
1472 | protocol, say Y. "Mounting files" means that the client can access | |
1473 | the files with usual UNIX commands as if they were sitting on the | |
1474 | client's hard disk. For this to work, the server must run the | |
1475 | programs nfsd and mountd (but does not need to have NFS file system | |
1476 | support enabled in its kernel). NFS is explained in the Network | |
1477 | Administrator's Guide, available from | |
1478 | <http://www.tldp.org/docs.html#guide>, on its man page: "man | |
1479 | nfs", and in the NFS-HOWTO. | |
1480 | ||
1481 | A superior but less widely used alternative to NFS is provided by | |
1482 | the Coda file system; see "Coda file system support" below. | |
1483 | ||
1484 | If you say Y here, you should have said Y to TCP/IP networking also. | |
1485 | This option would enlarge your kernel by about 27 KB. | |
1486 | ||
1487 | To compile this file system support as a module, choose M here: the | |
1488 | module will be called nfs. | |
1489 | ||
1490 | If you are configuring a diskless machine which will mount its root | |
1491 | file system over NFS at boot time, say Y here and to "Kernel | |
1492 | level IP autoconfiguration" above and to "Root file system on NFS" | |
1493 | below. You cannot compile this driver as a module in this case. | |
1494 | There are two packages designed for booting diskless machines over | |
1495 | the net: netboot, available from | |
1496 | <http://ftp1.sourceforge.net/netboot/>, and Etherboot, | |
1497 | available from <http://ftp1.sourceforge.net/etherboot/>. | |
1498 | ||
1499 | If you don't know what all this is about, say N. | |
1500 | ||
1501 | config NFS_V3 | |
1502 | bool "Provide NFSv3 client support" | |
1503 | depends on NFS_FS | |
1504 | help | |
1505 | Say Y here if you want your NFS client to be able to speak version | |
1506 | 3 of the NFS protocol. | |
1507 | ||
1508 | If unsure, say Y. | |
1509 | ||
b7fa0554 AG |
1510 | config NFS_V3_ACL |
1511 | bool "Provide client support for the NFSv3 ACL protocol extension" | |
1512 | depends on NFS_V3 | |
1513 | help | |
1514 | Implement the NFSv3 ACL protocol extension for manipulating POSIX | |
1515 | Access Control Lists. The server should also be compiled with | |
1516 | the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option. | |
1517 | ||
1518 | If unsure, say N. | |
1519 | ||
1da177e4 LT |
1520 | config NFS_V4 |
1521 | bool "Provide NFSv4 client support (EXPERIMENTAL)" | |
1522 | depends on NFS_FS && EXPERIMENTAL | |
1523 | select RPCSEC_GSS_KRB5 | |
1524 | help | |
1525 | Say Y here if you want your NFS client to be able to speak the newer | |
1526 | version 4 of the NFS protocol. | |
1527 | ||
1528 | Note: Requires auxiliary userspace daemons which may be found on | |
1529 | http://www.citi.umich.edu/projects/nfsv4/ | |
1530 | ||
1531 | If unsure, say N. | |
1532 | ||
1533 | config NFS_DIRECTIO | |
026ed5c9 CL |
1534 | bool "Allow direct I/O on NFS files" |
1535 | depends on NFS_FS | |
1da177e4 LT |
1536 | help |
1537 | This option enables applications to perform uncached I/O on files | |
1538 | in NFS file systems using the O_DIRECT open() flag. When O_DIRECT | |
1539 | is set for a file, its data is not cached in the system's page | |
1540 | cache. Data is moved to and from user-level application buffers | |
1541 | directly. Unlike local disk-based file systems, NFS O_DIRECT has | |
1542 | no alignment restrictions. | |
1543 | ||
1544 | Unless your program is designed to use O_DIRECT properly, you are | |
1545 | much better off allowing the NFS client to manage data caching for | |
1546 | you. Misusing O_DIRECT can cause poor server performance or network | |
1547 | storms. This kernel build option defaults OFF to avoid exposing | |
1548 | system administrators unwittingly to a potentially hazardous | |
1549 | feature. | |
1550 | ||
1551 | For more details on NFS O_DIRECT, see fs/nfs/direct.c. | |
1552 | ||
1553 | If unsure, say N. This reduces the size of the NFS client, and | |
1554 | causes open() to return EINVAL if a file residing in NFS is | |
1555 | opened with the O_DIRECT flag. | |
1556 | ||
1557 | config NFSD | |
1558 | tristate "NFS server support" | |
1559 | depends on INET | |
1560 | select LOCKD | |
1561 | select SUNRPC | |
1562 | select EXPORTFS | |
f05e15b5 HX |
1563 | select NFSD_V2_ACL if NFSD_V3_ACL |
1564 | select NFS_ACL_SUPPORT if NFSD_V2_ACL | |
1565 | select NFSD_TCP if NFSD_V4 | |
1566 | select CRYPTO_MD5 if NFSD_V4 | |
1567 | select CRYPTO if NFSD_V4 | |
1568 | select FS_POSIX_ACL if NFSD_V4 | |
1da177e4 LT |
1569 | help |
1570 | If you want your Linux box to act as an NFS *server*, so that other | |
1571 | computers on your local network which support NFS can access certain | |
1572 | directories on your box transparently, you have two options: you can | |
1573 | use the self-contained user space program nfsd, in which case you | |
1574 | should say N here, or you can say Y and use the kernel based NFS | |
1575 | server. The advantage of the kernel based solution is that it is | |
1576 | faster. | |
1577 | ||
1578 | In either case, you will need support software; the respective | |
1579 | locations are given in the file <file:Documentation/Changes> in the | |
1580 | NFS section. | |
1581 | ||
1582 | If you say Y here, you will get support for version 2 of the NFS | |
1583 | protocol (NFSv2). If you also want NFSv3, say Y to the next question | |
1584 | as well. | |
1585 | ||
1586 | Please read the NFS-HOWTO, available from | |
1587 | <http://www.tldp.org/docs.html#howto>. | |
1588 | ||
1589 | To compile the NFS server support as a module, choose M here: the | |
1590 | module will be called nfsd. If unsure, say N. | |
1591 | ||
a257cdd0 AG |
1592 | config NFSD_V2_ACL |
1593 | bool | |
1594 | depends on NFSD | |
1595 | ||
1da177e4 LT |
1596 | config NFSD_V3 |
1597 | bool "Provide NFSv3 server support" | |
1598 | depends on NFSD | |
1599 | help | |
1600 | If you would like to include the NFSv3 server as well as the NFSv2 | |
1601 | server, say Y here. If unsure, say Y. | |
1602 | ||
a257cdd0 AG |
1603 | config NFSD_V3_ACL |
1604 | bool "Provide server support for the NFSv3 ACL protocol extension" | |
1605 | depends on NFSD_V3 | |
a257cdd0 AG |
1606 | help |
1607 | Implement the NFSv3 ACL protocol extension for manipulating POSIX | |
1608 | Access Control Lists on exported file systems. NFS clients should | |
1609 | be compiled with the NFSv3 ACL protocol extension; see the | |
1610 | CONFIG_NFS_V3_ACL option. If unsure, say N. | |
1611 | ||
1da177e4 LT |
1612 | config NFSD_V4 |
1613 | bool "Provide NFSv4 server support (EXPERIMENTAL)" | |
1614 | depends on NFSD_V3 && EXPERIMENTAL | |
1da177e4 LT |
1615 | help |
1616 | If you would like to include the NFSv4 server as well as the NFSv2 | |
1617 | and NFSv3 servers, say Y here. This feature is experimental, and | |
1618 | should only be used if you are interested in helping to test NFSv4. | |
1619 | If unsure, say N. | |
1620 | ||
1621 | config NFSD_TCP | |
1622 | bool "Provide NFS server over TCP support" | |
1623 | depends on NFSD | |
1624 | default y | |
1625 | help | |
1626 | If you want your NFS server to support TCP connections, say Y here. | |
1627 | TCP connections usually perform better than the default UDP when | |
1628 | the network is lossy or congested. If unsure, say Y. | |
1629 | ||
1630 | config ROOT_NFS | |
1631 | bool "Root file system on NFS" | |
1632 | depends on NFS_FS=y && IP_PNP | |
1633 | help | |
1634 | If you want your Linux box to mount its whole root file system (the | |
1635 | one containing the directory /) from some other computer over the | |
1636 | net via NFS (presumably because your box doesn't have a hard disk), | |
1637 | say Y. Read <file:Documentation/nfsroot.txt> for details. It is | |
1638 | likely that in this case, you also want to say Y to "Kernel level IP | |
1639 | autoconfiguration" so that your box can discover its network address | |
1640 | at boot time. | |
1641 | ||
1642 | Most people say N here. | |
1643 | ||
1644 | config LOCKD | |
1645 | tristate | |
1646 | ||
1647 | config LOCKD_V4 | |
1648 | bool | |
1649 | depends on NFSD_V3 || NFS_V3 | |
1650 | default y | |
1651 | ||
1652 | config EXPORTFS | |
1653 | tristate | |
1654 | ||
a257cdd0 AG |
1655 | config NFS_ACL_SUPPORT |
1656 | tristate | |
1657 | select FS_POSIX_ACL | |
1658 | ||
1659 | config NFS_COMMON | |
1660 | bool | |
1661 | depends on NFSD || NFS_FS | |
1662 | default y | |
1663 | ||
1da177e4 LT |
1664 | config SUNRPC |
1665 | tristate | |
1666 | ||
1667 | config SUNRPC_GSS | |
1668 | tristate | |
1669 | ||
1670 | config RPCSEC_GSS_KRB5 | |
1671 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
1672 | depends on SUNRPC && EXPERIMENTAL | |
1673 | select SUNRPC_GSS | |
1674 | select CRYPTO | |
1675 | select CRYPTO_MD5 | |
1676 | select CRYPTO_DES | |
1677 | help | |
1678 | Provides for secure RPC calls by means of a gss-api | |
1679 | mechanism based on Kerberos V5. This is required for | |
1680 | NFSv4. | |
1681 | ||
1682 | Note: Requires an auxiliary userspace daemon which may be found on | |
1683 | http://www.citi.umich.edu/projects/nfsv4/ | |
1684 | ||
1685 | If unsure, say N. | |
1686 | ||
1687 | config RPCSEC_GSS_SPKM3 | |
1688 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1689 | depends on SUNRPC && EXPERIMENTAL | |
1690 | select SUNRPC_GSS | |
1691 | select CRYPTO | |
1692 | select CRYPTO_MD5 | |
1693 | select CRYPTO_DES | |
df6db302 | 1694 | select CRYPTO_CAST5 |
1da177e4 LT |
1695 | help |
1696 | Provides for secure RPC calls by means of a gss-api | |
1697 | mechanism based on the SPKM3 public-key mechanism. | |
1698 | ||
1699 | Note: Requires an auxiliary userspace daemon which may be found on | |
1700 | http://www.citi.umich.edu/projects/nfsv4/ | |
1701 | ||
1702 | If unsure, say N. | |
1703 | ||
1704 | config SMB_FS | |
1705 | tristate "SMB file system support (to mount Windows shares etc.)" | |
1706 | depends on INET | |
1707 | select NLS | |
1708 | help | |
1709 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1710 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1711 | files and printers over local networks. Saying Y here allows you to | |
1712 | mount their file systems (often called "shares" in this context) and | |
1713 | access them just like any other Unix directory. Currently, this | |
1714 | works only if the Windows machines use TCP/IP as the underlying | |
1715 | transport protocol, and not NetBEUI. For details, read | |
1716 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1717 | available from <http://www.tldp.org/docs.html#howto>. | |
1718 | ||
1719 | Note: if you just want your box to act as an SMB *server* and make | |
1720 | files and printing services available to Windows clients (which need | |
1721 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1722 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1723 | for that. | |
1724 | ||
1725 | General information about how to connect Linux, Windows machines and | |
1726 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1727 | ||
1728 | To compile the SMB support as a module, choose M here: the module will | |
1729 | be called smbfs. Most people say N, however. | |
1730 | ||
1731 | config SMB_NLS_DEFAULT | |
1732 | bool "Use a default NLS" | |
1733 | depends on SMB_FS | |
1734 | help | |
1735 | Enabling this will make smbfs use nls translations by default. You | |
1736 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1737 | settings and you need to give the default nls for the SMB server as | |
1738 | CONFIG_SMB_NLS_REMOTE. | |
1739 | ||
1740 | The nls settings can be changed at mount time, if your smbmount | |
1741 | supports that, using the codepage and iocharset parameters. | |
1742 | ||
1743 | smbmount from samba 2.2.0 or later supports this. | |
1744 | ||
1745 | config SMB_NLS_REMOTE | |
1746 | string "Default Remote NLS Option" | |
1747 | depends on SMB_NLS_DEFAULT | |
1748 | default "cp437" | |
1749 | help | |
1750 | This setting allows you to specify a default value for which | |
1751 | codepage the server uses. If this field is left blank no | |
1752 | translations will be done by default. The local codepage/charset | |
1753 | default to CONFIG_NLS_DEFAULT. | |
1754 | ||
1755 | The nls settings can be changed at mount time, if your smbmount | |
1756 | supports that, using the codepage and iocharset parameters. | |
1757 | ||
1758 | smbmount from samba 2.2.0 or later supports this. | |
1759 | ||
1760 | config CIFS | |
1761 | tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)" | |
1762 | depends on INET | |
1763 | select NLS | |
1764 | help | |
1765 | This is the client VFS module for the Common Internet File System | |
1766 | (CIFS) protocol which is the successor to the Server Message Block | |
1767 | (SMB) protocol, the native file sharing mechanism for most early | |
1768 | PC operating systems. The CIFS protocol is fully supported by | |
1769 | file servers such as Windows 2000 (including Windows 2003, NT 4 | |
1770 | and Windows XP) as well by Samba (which provides excellent CIFS | |
ec58ef03 SF |
1771 | server support for Linux and many other operating systems). Limited |
1772 | support for Windows ME and similar servers is provided as well. | |
1773 | You must use the smbfs client filesystem to access older SMB servers | |
1774 | such as OS/2 and DOS. | |
1da177e4 LT |
1775 | |
1776 | The intent of the cifs module is to provide an advanced | |
1777 | network file system client for mounting to CIFS compliant servers, | |
1778 | including support for dfs (hierarchical name space), secure per-user | |
1779 | session establishment, safe distributed caching (oplock), optional | |
1780 | packet signing, Unicode and other internationalization improvements, | |
1781 | and optional Winbind (nsswitch) integration. You do not need to enable | |
1782 | cifs if running only a (Samba) server. It is possible to enable both | |
1783 | smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003 | |
1784 | and Samba 3 servers, and smbfs for accessing old servers). If you need | |
ec58ef03 | 1785 | to mount to Samba or Windows from this machine, say Y. |
1da177e4 LT |
1786 | |
1787 | config CIFS_STATS | |
1788 | bool "CIFS statistics" | |
1789 | depends on CIFS | |
1790 | help | |
1791 | Enabling this option will cause statistics for each server share | |
1792 | mounted by the cifs client to be displayed in /proc/fs/cifs/Stats | |
1793 | ||
ec58ef03 | 1794 | config CIFS_STATS2 |
3979877e | 1795 | bool "Extended statistics" |
ec58ef03 SF |
1796 | depends on CIFS_STATS |
1797 | help | |
1798 | Enabling this option will allow more detailed statistics on SMB | |
1799 | request timing to be displayed in /proc/fs/cifs/DebugData and also | |
1800 | allow optional logging of slow responses to dmesg (depending on the | |
1801 | value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details). | |
1802 | These additional statistics may have a minor effect on performance | |
1803 | and memory utilization. | |
1804 | ||
1805 | Unless you are a developer or are doing network performance analysis | |
1806 | or tuning, say N. | |
1807 | ||
3979877e SF |
1808 | config CIFS_WEAK_PW_HASH |
1809 | bool "Support legacy servers which use weaker LANMAN security" | |
1810 | depends on CIFS | |
1811 | help | |
1812 | Modern CIFS servers including Samba and most Windows versions | |
1813 | (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos) | |
1814 | security mechanisms. These hash the password more securely | |
1815 | than the mechanisms used in the older LANMAN version of the | |
1816 | SMB protocol needed to establish sessions with old SMB servers. | |
1817 | ||
1818 | Enabling this option allows the cifs module to mount to older | |
1819 | LANMAN based servers such as OS/2 and Windows 95, but such | |
1820 | mounts may be less secure than mounts using NTLM or more recent | |
1821 | security mechanisms if you are on a public network. Unless you | |
1822 | have a need to access old SMB servers (and are on a private | |
1823 | network) you probably want to say N. Even if this support | |
1824 | is enabled in the kernel build, they will not be used | |
1825 | automatically. At runtime LANMAN mounts are disabled but | |
1826 | can be set to required (or optional) either in | |
1827 | /proc/fs/cifs (see fs/cifs/README for more detail) or via an | |
1828 | option on the mount command. This support is disabled by | |
1829 | default in order to reduce the possibility of a downgrade | |
1830 | attack. | |
1831 | ||
1832 | If unsure, say N. | |
1833 | ||
1da177e4 | 1834 | config CIFS_XATTR |
ec58ef03 | 1835 | bool "CIFS extended attributes" |
1da177e4 LT |
1836 | depends on CIFS |
1837 | help | |
1838 | Extended attributes are name:value pairs associated with inodes by | |
1839 | the kernel or by users (see the attr(5) manual page, or visit | |
1840 | <http://acl.bestbits.at/> for details). CIFS maps the name of | |
1841 | extended attributes beginning with the user namespace prefix | |
1842 | to SMB/CIFS EAs. EAs are stored on Windows servers without the | |
1843 | user namespace prefix, but their names are seen by Linux cifs clients | |
1844 | prefaced by the user namespace prefix. The system namespace | |
1845 | (used by some filesystems to store ACLs) is not supported at | |
1846 | this time. | |
ec58ef03 | 1847 | |
1da177e4 LT |
1848 | If unsure, say N. |
1849 | ||
1850 | config CIFS_POSIX | |
ec58ef03 | 1851 | bool "CIFS POSIX Extensions" |
1da177e4 LT |
1852 | depends on CIFS_XATTR |
1853 | help | |
1854 | Enabling this option will cause the cifs client to attempt to | |
1855 | negotiate a newer dialect with servers, such as Samba 3.0.5 | |
1856 | or later, that optionally can handle more POSIX like (rather | |
1857 | than Windows like) file behavior. It also enables | |
1858 | support for POSIX ACLs (getfacl and setfacl) to servers | |
1859 | (such as Samba 3.10 and later) which can negotiate | |
1860 | CIFS POSIX ACL support. If unsure, say N. | |
1861 | ||
3979877e | 1862 | config CIFS_DEBUG2 |
3856a9d4 | 1863 | bool "Enable additional CIFS debugging routines" |
8ba10ab1 | 1864 | depends on CIFS |
3979877e SF |
1865 | help |
1866 | Enabling this option adds a few more debugging routines | |
1867 | to the cifs code which slightly increases the size of | |
1868 | the cifs module and can cause additional logging of debug | |
1869 | messages in some error paths, slowing performance. This | |
1870 | option can be turned off unless you are debugging | |
1871 | cifs problems. If unsure, say N. | |
1872 | ||
1da177e4 LT |
1873 | config CIFS_EXPERIMENTAL |
1874 | bool "CIFS Experimental Features (EXPERIMENTAL)" | |
cb9dbff9 | 1875 | depends on CIFS && EXPERIMENTAL |
1da177e4 | 1876 | help |
ec58ef03 SF |
1877 | Enables cifs features under testing. These features are |
1878 | experimental and currently include support for writepages | |
1879 | (multipage writebehind performance improvements) and directory | |
1880 | change notification ie fcntl(F_DNOTIFY) as well as some security | |
1881 | improvements. Some also depend on setting at runtime the | |
1882 | pseudo-file /proc/fs/cifs/Experimental (which is disabled by | |
1883 | default). See the file fs/cifs/README for more details. | |
1884 | ||
1885 | If unsure, say N. | |
1da177e4 | 1886 | |
a2653eba | 1887 | config CIFS_UPCALL |
3979877e | 1888 | bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)" |
a2653eba SF |
1889 | depends on CIFS_EXPERIMENTAL |
1890 | select CONNECTOR | |
1891 | help | |
1892 | Enables an upcall mechanism for CIFS which will be used to contact | |
1893 | userspace helper utilities to provide SPNEGO packaged Kerberos | |
1894 | tickets which are needed to mount to certain secure servers | |
1b397f4f SF |
1895 | (for which more secure Kerberos authentication is required). If |
1896 | unsure, say N. | |
a2653eba | 1897 | |
1da177e4 LT |
1898 | config NCP_FS |
1899 | tristate "NCP file system support (to mount NetWare volumes)" | |
1900 | depends on IPX!=n || INET | |
1901 | help | |
1902 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1903 | used by Novell NetWare clients to talk to file servers. It is to | |
1904 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1905 | to mount NetWare file server volumes and to access them just like | |
1906 | any other Unix directory. For details, please read the file | |
1907 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1908 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1909 | ||
1910 | You do not have to say Y here if you want your Linux box to act as a | |
1911 | file *server* for Novell NetWare clients. | |
1912 | ||
1913 | General information about how to connect Linux, Windows machines and | |
1914 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1915 | ||
1916 | To compile this as a module, choose M here: the module will be called | |
1917 | ncpfs. Say N unless you are connected to a Novell network. | |
1918 | ||
1919 | source "fs/ncpfs/Kconfig" | |
1920 | ||
1921 | config CODA_FS | |
1922 | tristate "Coda file system support (advanced network fs)" | |
1923 | depends on INET | |
1924 | help | |
1925 | Coda is an advanced network file system, similar to NFS in that it | |
1926 | enables you to mount file systems of a remote server and access them | |
1927 | with regular Unix commands as if they were sitting on your hard | |
1928 | disk. Coda has several advantages over NFS: support for | |
1929 | disconnected operation (e.g. for laptops), read/write server | |
1930 | replication, security model for authentication and encryption, | |
1931 | persistent client caches and write back caching. | |
1932 | ||
1933 | If you say Y here, your Linux box will be able to act as a Coda | |
1934 | *client*. You will need user level code as well, both for the | |
1935 | client and server. Servers are currently user level, i.e. they need | |
1936 | no kernel support. Please read | |
1937 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1938 | home page <http://www.coda.cs.cmu.edu/>. | |
1939 | ||
1940 | To compile the coda client support as a module, choose M here: the | |
1941 | module will be called coda. | |
1942 | ||
1943 | config CODA_FS_OLD_API | |
1944 | bool "Use 96-bit Coda file identifiers" | |
1945 | depends on CODA_FS | |
1946 | help | |
1947 | A new kernel-userspace API had to be introduced for Coda v6.0 | |
1948 | to support larger 128-bit file identifiers as needed by the | |
1949 | new realms implementation. | |
1950 | ||
1951 | However this new API is not backward compatible with older | |
1952 | clients. If you really need to run the old Coda userspace | |
1953 | cache manager then say Y. | |
1954 | ||
1955 | For most cases you probably want to say N. | |
1956 | ||
1957 | config AFS_FS | |
1958 | # for fs/nls/Config.in | |
1959 | tristate "Andrew File System support (AFS) (Experimental)" | |
1960 | depends on INET && EXPERIMENTAL | |
1961 | select RXRPC | |
1962 | help | |
1963 | If you say Y here, you will get an experimental Andrew File System | |
1964 | driver. It currently only supports unsecured read-only AFS access. | |
1965 | ||
cc2e2767 | 1966 | See <file:Documentation/filesystems/afs.txt> for more information. |
1da177e4 LT |
1967 | |
1968 | If unsure, say N. | |
1969 | ||
1970 | config RXRPC | |
1971 | tristate | |
1972 | ||
93fa58cb EVH |
1973 | config 9P_FS |
1974 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" | |
1975 | depends on INET && EXPERIMENTAL | |
1976 | help | |
1977 | If you say Y here, you will get experimental support for | |
1978 | Plan 9 resource sharing via the 9P2000 protocol. | |
1979 | ||
1980 | See <http://v9fs.sf.net> for more information. | |
1981 | ||
1982 | If unsure, say N. | |
1983 | ||
f0c8bd16 AG |
1984 | config GENERIC_ACL |
1985 | bool | |
1986 | select FS_POSIX_ACL | |
1987 | ||
1da177e4 LT |
1988 | endmenu |
1989 | ||
9361401e | 1990 | if BLOCK |
1da177e4 LT |
1991 | menu "Partition Types" |
1992 | ||
1993 | source "fs/partitions/Kconfig" | |
1994 | ||
1995 | endmenu | |
9361401e | 1996 | endif |
1da177e4 LT |
1997 | |
1998 | source "fs/nls/Kconfig" | |
e7fd4179 | 1999 | source "fs/dlm/Kconfig" |
1da177e4 LT |
2000 | |
2001 | endmenu | |
2002 |