Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # File system configuration | |
3 | # | |
4 | ||
5 | menu "File systems" | |
6 | ||
7 | config EXT2_FS | |
8 | tristate "Second extended fs support" | |
9 | help | |
10 | Ext2 is a standard Linux file system for hard disks. | |
11 | ||
12 | To compile this file system support as a module, choose M here: the | |
13 | module will be called ext2. Be aware however that the file system | |
14 | of your root partition (the one containing the directory /) cannot | |
15 | be compiled as a module, and so this could be dangerous. | |
16 | ||
17 | If unsure, say Y. | |
18 | ||
19 | config EXT2_FS_XATTR | |
20 | bool "Ext2 extended attributes" | |
21 | depends on EXT2_FS | |
22 | help | |
23 | Extended attributes are name:value pairs associated with inodes by | |
24 | the kernel or by users (see the attr(5) manual page, or visit | |
25 | <http://acl.bestbits.at/> for details). | |
26 | ||
27 | If unsure, say N. | |
28 | ||
29 | config EXT2_FS_POSIX_ACL | |
30 | bool "Ext2 POSIX Access Control Lists" | |
31 | depends on EXT2_FS_XATTR | |
b84c2157 | 32 | select FS_POSIX_ACL |
1da177e4 LT |
33 | help |
34 | Posix Access Control Lists (ACLs) support permissions for users and | |
35 | groups beyond the owner/group/world scheme. | |
36 | ||
37 | To learn more about Access Control Lists, visit the Posix ACLs for | |
38 | Linux website <http://acl.bestbits.at/>. | |
39 | ||
40 | If you don't know what Access Control Lists are, say N | |
41 | ||
42 | config EXT2_FS_SECURITY | |
43 | bool "Ext2 Security Labels" | |
44 | depends on EXT2_FS_XATTR | |
45 | help | |
46 | Security labels support alternative access control models | |
47 | implemented by security modules like SELinux. This option | |
48 | enables an extended attribute handler for file security | |
49 | labels in the ext2 filesystem. | |
50 | ||
51 | If you are not using a security module that requires using | |
52 | extended attributes for file security labels, say N. | |
53 | ||
6d79125b CO |
54 | config EXT2_FS_XIP |
55 | bool "Ext2 execute in place support" | |
56 | depends on EXT2_FS | |
57 | help | |
58 | Execute in place can be used on memory-backed block devices. If you | |
59 | enable this option, you can select to mount block devices which are | |
60 | capable of this feature without using the page cache. | |
61 | ||
62 | If you do not use a block device that is capable of using this, | |
63 | or if unsure, say N. | |
64 | ||
65 | config FS_XIP | |
66 | # execute in place | |
67 | bool | |
68 | depends on EXT2_FS_XIP | |
69 | default y | |
70 | ||
1da177e4 LT |
71 | config EXT3_FS |
72 | tristate "Ext3 journalling file system support" | |
73 | help | |
74 | This is the journaling version of the Second extended file system | |
75 | (often called ext3), the de facto standard Linux file system | |
76 | (method to organize files on a storage device) for hard disks. | |
77 | ||
78 | The journaling code included in this driver means you do not have | |
79 | to run e2fsck (file system checker) on your file systems after a | |
80 | crash. The journal keeps track of any changes that were being made | |
81 | at the time the system crashed, and can ensure that your file system | |
82 | is consistent without the need for a lengthy check. | |
83 | ||
84 | Other than adding the journal to the file system, the on-disk format | |
85 | of ext3 is identical to ext2. It is possible to freely switch | |
86 | between using the ext3 driver and the ext2 driver, as long as the | |
87 | file system has been cleanly unmounted, or e2fsck is run on the file | |
88 | system. | |
89 | ||
90 | To add a journal on an existing ext2 file system or change the | |
91 | behavior of ext3 file systems, you can use the tune2fs utility ("man | |
92 | tune2fs"). To modify attributes of files and directories on ext3 | |
93 | file systems, use chattr ("man chattr"). You need to be using | |
94 | e2fsprogs version 1.20 or later in order to create ext3 journals | |
95 | (available at <http://sourceforge.net/projects/e2fsprogs/>). | |
96 | ||
97 | To compile this file system support as a module, choose M here: the | |
98 | module will be called ext3. Be aware however that the file system | |
99 | of your root partition (the one containing the directory /) cannot | |
100 | be compiled as a module, and so this may be dangerous. | |
101 | ||
102 | config EXT3_FS_XATTR | |
103 | bool "Ext3 extended attributes" | |
104 | depends on EXT3_FS | |
105 | default y | |
106 | help | |
107 | Extended attributes are name:value pairs associated with inodes by | |
108 | the kernel or by users (see the attr(5) manual page, or visit | |
109 | <http://acl.bestbits.at/> for details). | |
110 | ||
111 | If unsure, say N. | |
112 | ||
113 | You need this for POSIX ACL support on ext3. | |
114 | ||
115 | config EXT3_FS_POSIX_ACL | |
116 | bool "Ext3 POSIX Access Control Lists" | |
117 | depends on EXT3_FS_XATTR | |
b84c2157 | 118 | select FS_POSIX_ACL |
1da177e4 LT |
119 | help |
120 | Posix Access Control Lists (ACLs) support permissions for users and | |
121 | groups beyond the owner/group/world scheme. | |
122 | ||
123 | To learn more about Access Control Lists, visit the Posix ACLs for | |
124 | Linux website <http://acl.bestbits.at/>. | |
125 | ||
126 | If you don't know what Access Control Lists are, say N | |
127 | ||
128 | config EXT3_FS_SECURITY | |
129 | bool "Ext3 Security Labels" | |
130 | depends on EXT3_FS_XATTR | |
131 | help | |
132 | Security labels support alternative access control models | |
133 | implemented by security modules like SELinux. This option | |
134 | enables an extended attribute handler for file security | |
135 | labels in the ext3 filesystem. | |
136 | ||
137 | If you are not using a security module that requires using | |
138 | extended attributes for file security labels, say N. | |
139 | ||
140 | config JBD | |
141 | # CONFIG_JBD could be its own option (even modular), but until there are | |
142 | # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS | |
143 | # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS | |
144 | tristate | |
145 | default EXT3_FS | |
146 | help | |
147 | This is a generic journaling layer for block devices. It is | |
148 | currently used by the ext3 file system, but it could also be used to | |
149 | add journal support to other file systems or block devices such as | |
150 | RAID or LVM. | |
151 | ||
152 | If you are using the ext3 file system, you need to say Y here. If | |
153 | you are not using ext3 then you will probably want to say N. | |
154 | ||
155 | To compile this device as a module, choose M here: the module will be | |
156 | called jbd. If you are compiling ext3 into the kernel, you cannot | |
157 | compile this code as a module. | |
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 | |
186 | tree. Uses journaling. | |
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" | |
328 | ||
329 | config MINIX_FS | |
330 | tristate "Minix fs support" | |
331 | help | |
332 | Minix is a simple operating system used in many classes about OS's. | |
333 | The minix file system (method to organize files on a hard disk | |
334 | partition or a floppy disk) was the original file system for Linux, | |
335 | but has been superseded by the second extended file system ext2fs. | |
336 | You don't want to use the minix file system on your hard disk | |
337 | because of certain built-in restrictions, but it is sometimes found | |
338 | on older Linux floppy disks. This option will enlarge your kernel | |
339 | by about 28 KB. If unsure, say N. | |
340 | ||
341 | To compile this file system support as a module, choose M here: the | |
342 | module will be called minix. Note that the file system of your root | |
343 | partition (the one containing the directory /) cannot be compiled as | |
344 | a module. | |
345 | ||
346 | config ROMFS_FS | |
347 | tristate "ROM file system support" | |
348 | ---help--- | |
349 | This is a very small read-only file system mainly intended for | |
350 | initial ram disks of installation disks, but it could be used for | |
351 | other read-only media as well. Read | |
352 | <file:Documentation/filesystems/romfs.txt> for details. | |
353 | ||
354 | To compile this file system support as a module, choose M here: the | |
355 | module will be called romfs. Note that the file system of your | |
356 | root partition (the one containing the directory /) cannot be a | |
357 | module. | |
358 | ||
359 | If you don't know whether you need it, then you don't need it: | |
360 | answer N. | |
361 | ||
362 | config QUOTA | |
363 | bool "Quota support" | |
364 | help | |
365 | If you say Y here, you will be able to set per user limits for disk | |
366 | usage (also called disk quotas). Currently, it works for the | |
367 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
368 | quotas for which you don't need to run quotacheck(8) after an unclean | |
369 | shutdown. You need additional software in order to use quota support | |
370 | (you can download sources from | |
371 | <http://www.sf.net/projects/linuxquota/>). For further details, read | |
372 | the Quota mini-HOWTO, available from | |
373 | <http://www.tldp.org/docs.html#howto>, or the documentation provided | |
374 | with the quota tools. Probably the quota support is only useful for | |
375 | multi user systems. If unsure, say N. | |
376 | ||
377 | config QFMT_V1 | |
378 | tristate "Old quota format support" | |
379 | depends on QUOTA | |
380 | help | |
381 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
382 | you have quota working and you don't want to convert to new quota | |
383 | format say Y here. | |
384 | ||
385 | config QFMT_V2 | |
386 | tristate "Quota format v2 support" | |
387 | depends on QUOTA | |
388 | help | |
389 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
390 | need this functionality say Y here. Note that you will need recent | |
391 | quota utilities (>= 3.01) for new quota format with this kernel. | |
392 | ||
393 | config QUOTACTL | |
394 | bool | |
395 | depends on XFS_QUOTA || QUOTA | |
396 | default y | |
397 | ||
398 | config DNOTIFY | |
399 | bool "Dnotify support" if EMBEDDED | |
400 | default y | |
401 | help | |
402 | Dnotify is a directory-based per-fd file change notification system | |
403 | that uses signals to communicate events to user-space. There exist | |
404 | superior alternatives, but some applications may still rely on | |
405 | dnotify. | |
406 | ||
407 | Because of this, if unsure, say Y. | |
408 | ||
409 | config AUTOFS_FS | |
410 | tristate "Kernel automounter support" | |
411 | help | |
412 | The automounter is a tool to automatically mount remote file systems | |
413 | on demand. This implementation is partially kernel-based to reduce | |
414 | overhead in the already-mounted case; this is unlike the BSD | |
415 | automounter (amd), which is a pure user space daemon. | |
416 | ||
417 | To use the automounter you need the user-space tools from the autofs | |
418 | package; you can find the location in <file:Documentation/Changes>. | |
419 | You also want to answer Y to "NFS file system support", below. | |
420 | ||
421 | If you want to use the newer version of the automounter with more | |
422 | features, say N here and say Y to "Kernel automounter v4 support", | |
423 | below. | |
424 | ||
425 | To compile this support as a module, choose M here: the module will be | |
426 | called autofs. | |
427 | ||
428 | If you are not a part of a fairly large, distributed network, you | |
429 | probably do not need an automounter, and can say N here. | |
430 | ||
431 | config AUTOFS4_FS | |
432 | tristate "Kernel automounter version 4 support (also supports v3)" | |
433 | help | |
434 | The automounter is a tool to automatically mount remote file systems | |
435 | on demand. This implementation is partially kernel-based to reduce | |
436 | overhead in the already-mounted case; this is unlike the BSD | |
437 | automounter (amd), which is a pure user space daemon. | |
438 | ||
439 | To use the automounter you need the user-space tools from | |
440 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also | |
441 | want to answer Y to "NFS file system support", below. | |
442 | ||
443 | To compile this support as a module, choose M here: the module will be | |
444 | called autofs4. You will need to add "alias autofs autofs4" to your | |
445 | modules configuration file. | |
446 | ||
447 | If you are not a part of a fairly large, distributed network or | |
448 | don't have a laptop which needs to dynamically reconfigure to the | |
449 | local network, you probably do not need an automounter, and can say | |
450 | N here. | |
451 | ||
452 | menu "CD-ROM/DVD Filesystems" | |
453 | ||
454 | config ISO9660_FS | |
455 | tristate "ISO 9660 CDROM file system support" | |
456 | help | |
457 | This is the standard file system used on CD-ROMs. It was previously | |
458 | known as "High Sierra File System" and is called "hsfs" on other | |
459 | Unix systems. The so-called Rock-Ridge extensions which allow for | |
460 | long Unix filenames and symbolic links are also supported by this | |
461 | driver. If you have a CD-ROM drive and want to do more with it than | |
462 | just listen to audio CDs and watch its LEDs, say Y (and read | |
463 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, | |
464 | available from <http://www.tldp.org/docs.html#howto>), thereby | |
465 | enlarging your kernel by about 27 KB; otherwise say N. | |
466 | ||
467 | To compile this file system support as a module, choose M here: the | |
468 | module will be called isofs. | |
469 | ||
470 | config JOLIET | |
471 | bool "Microsoft Joliet CDROM extensions" | |
472 | depends on ISO9660_FS | |
473 | select NLS | |
474 | help | |
475 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system | |
476 | which allows for long filenames in unicode format (unicode is the | |
477 | new 16 bit character code, successor to ASCII, which encodes the | |
478 | characters of almost all languages of the world; see | |
479 | <http://www.unicode.org/> for more information). Say Y here if you | |
480 | want to be able to read Joliet CD-ROMs under Linux. | |
481 | ||
482 | config ZISOFS | |
483 | bool "Transparent decompression extension" | |
484 | depends on ISO9660_FS | |
485 | select ZLIB_INFLATE | |
486 | help | |
487 | This is a Linux-specific extension to RockRidge which lets you store | |
488 | data in compressed form on a CD-ROM and have it transparently | |
489 | decompressed when the CD-ROM is accessed. See | |
490 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools | |
491 | necessary to create such a filesystem. Say Y here if you want to be | |
492 | able to read such compressed CD-ROMs. | |
493 | ||
494 | config ZISOFS_FS | |
495 | # for fs/nls/Config.in | |
496 | tristate | |
497 | depends on ZISOFS | |
498 | default ISO9660_FS | |
499 | ||
500 | config UDF_FS | |
501 | tristate "UDF file system support" | |
502 | help | |
503 | This is the new file system used on some CD-ROMs and DVDs. Say Y if | |
504 | you intend to mount DVD discs or CDRW's written in packet mode, or | |
505 | if written to by other UDF utilities, such as DirectCD. | |
506 | Please read <file:Documentation/filesystems/udf.txt>. | |
507 | ||
508 | To compile this file system support as a module, choose M here: the | |
509 | module will be called udf. | |
510 | ||
511 | If unsure, say N. | |
512 | ||
513 | config UDF_NLS | |
514 | bool | |
515 | default y | |
516 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) | |
517 | ||
518 | endmenu | |
519 | ||
520 | menu "DOS/FAT/NT Filesystems" | |
521 | ||
522 | config FAT_FS | |
523 | tristate | |
524 | select NLS | |
525 | help | |
526 | If you want to use one of the FAT-based file systems (the MS-DOS and | |
527 | VFAT (Windows 95) file systems), then you must say Y or M here | |
528 | to include FAT support. You will then be able to mount partitions or | |
529 | diskettes with FAT-based file systems and transparently access the | |
530 | files on them, i.e. MSDOS files will look and behave just like all | |
531 | other Unix files. | |
532 | ||
533 | This FAT support is not a file system in itself, it only provides | |
534 | the foundation for the other file systems. You will have to say Y or | |
535 | M to at least one of "MSDOS fs support" or "VFAT fs support" in | |
536 | order to make use of it. | |
537 | ||
538 | Another way to read and write MSDOS floppies and hard drive | |
539 | partitions from within Linux (but not transparently) is with the | |
540 | mtools ("man mtools") program suite. You don't need to say Y here in | |
541 | order to do that. | |
542 | ||
543 | If you need to move large files on floppies between a DOS and a | |
544 | Linux box, say Y here, mount the floppy under Linux with an MSDOS | |
545 | file system and use GNU tar's M option. GNU tar is a program | |
546 | available for Unix and DOS ("man tar" or "info tar"). | |
547 | ||
548 | It is now also becoming possible to read and write compressed FAT | |
549 | file systems; read <file:Documentation/filesystems/fat_cvf.txt> for | |
550 | details. | |
551 | ||
552 | The FAT support will enlarge your kernel by about 37 KB. If unsure, | |
553 | say Y. | |
554 | ||
555 | To compile this as a module, choose M here: the module will be called | |
556 | fat. Note that if you compile the FAT support as a module, you | |
557 | cannot compile any of the FAT-based file systems into the kernel | |
558 | -- they will have to be modules as well. | |
559 | ||
560 | config MSDOS_FS | |
561 | tristate "MSDOS fs support" | |
562 | select FAT_FS | |
563 | help | |
564 | This allows you to mount MSDOS partitions of your hard drive (unless | |
565 | they are compressed; to access compressed MSDOS partitions under | |
566 | Linux, you can either use the DOS emulator DOSEMU, described in the | |
567 | DOSEMU-HOWTO, available from | |
568 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in | |
569 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you | |
570 | intend to use dosemu with a non-compressed MSDOS partition, say Y | |
571 | here) and MSDOS floppies. This means that file access becomes | |
572 | transparent, i.e. the MSDOS files look and behave just like all | |
573 | other Unix files. | |
574 | ||
575 | If you have Windows 95 or Windows NT installed on your MSDOS | |
576 | partitions, you should use the VFAT file system (say Y to "VFAT fs | |
577 | support" below), or you will not be able to see the long filenames | |
578 | generated by Windows 95 / Windows NT. | |
579 | ||
580 | This option will enlarge your kernel by about 7 KB. If unsure, | |
581 | answer Y. This will only work if you said Y to "DOS FAT fs support" | |
582 | as well. To compile this as a module, choose M here: the module will | |
583 | be called msdos. | |
584 | ||
585 | config VFAT_FS | |
586 | tristate "VFAT (Windows-95) fs support" | |
587 | select FAT_FS | |
588 | help | |
589 | This option provides support for normal Windows file systems with | |
590 | long filenames. That includes non-compressed FAT-based file systems | |
591 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix | |
592 | programs from the mtools package. | |
593 | ||
594 | The VFAT support enlarges your kernel by about 10 KB and it only | |
595 | works if you said Y to the "DOS FAT fs support" above. Please read | |
596 | the file <file:Documentation/filesystems/vfat.txt> for details. If | |
597 | unsure, say Y. | |
598 | ||
599 | To compile this as a module, choose M here: the module will be called | |
600 | vfat. | |
601 | ||
602 | config FAT_DEFAULT_CODEPAGE | |
603 | int "Default codepage for FAT" | |
604 | depends on MSDOS_FS || VFAT_FS | |
605 | default 437 | |
606 | help | |
607 | This option should be set to the codepage of your FAT filesystems. | |
608 | It can be overridden with the "codepage" mount option. | |
609 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
610 | ||
611 | config FAT_DEFAULT_IOCHARSET | |
612 | string "Default iocharset for FAT" | |
613 | depends on VFAT_FS | |
614 | default "iso8859-1" | |
615 | help | |
616 | Set this to the default input/output character set you'd | |
617 | like FAT to use. It should probably match the character set | |
618 | that most of your FAT filesystems use, and can be overridden | |
619 | with the "iocharset" mount option for FAT filesystems. | |
620 | Note that "utf8" is not recommended for FAT filesystems. | |
621 | If unsure, you shouldn't set "utf8" here. | |
622 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
623 | ||
624 | config NTFS_FS | |
625 | tristate "NTFS file system support" | |
626 | select NLS | |
627 | help | |
628 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
629 | ||
630 | Saying Y or M here enables read support. There is partial, but | |
631 | safe, write support available. For write support you must also | |
632 | say Y to "NTFS write support" below. | |
633 | ||
634 | There are also a number of user-space tools available, called | |
635 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
636 | without NTFS support enabled in the kernel. | |
637 | ||
638 | This is a rewrite from scratch of Linux NTFS support and replaced | |
639 | the old NTFS code starting with Linux 2.5.11. A backport to | |
640 | the Linux 2.4 kernel series is separately available as a patch | |
641 | from the project web site. | |
642 | ||
643 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
644 | and <http://linux-ntfs.sourceforge.net/>. | |
645 | ||
646 | To compile this file system support as a module, choose M here: the | |
647 | module will be called ntfs. | |
648 | ||
649 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
650 | Linux on your computer it is safe to say N. | |
651 | ||
652 | config NTFS_DEBUG | |
653 | bool "NTFS debugging support" | |
654 | depends on NTFS_FS | |
655 | help | |
656 | If you are experiencing any problems with the NTFS file system, say | |
657 | Y here. This will result in additional consistency checks to be | |
658 | performed by the driver as well as additional debugging messages to | |
659 | be written to the system log. Note that debugging messages are | |
660 | disabled by default. To enable them, supply the option debug_msgs=1 | |
661 | at the kernel command line when booting the kernel or as an option | |
662 | to insmod when loading the ntfs module. Once the driver is active, | |
663 | you can enable debugging messages by doing (as root): | |
664 | echo 1 > /proc/sys/fs/ntfs-debug | |
665 | Replacing the "1" with "0" would disable debug messages. | |
666 | ||
667 | If you leave debugging messages disabled, this results in little | |
668 | overhead, but enabling debug messages results in very significant | |
669 | slowdown of the system. | |
670 | ||
671 | When reporting bugs, please try to have available a full dump of | |
672 | debugging messages while the misbehaviour was occurring. | |
673 | ||
674 | config NTFS_RW | |
675 | bool "NTFS write support" | |
676 | depends on NTFS_FS | |
677 | help | |
678 | This enables the partial, but safe, write support in the NTFS driver. | |
679 | ||
680 | The only supported operation is overwriting existing files, without | |
681 | changing the file length. No file or directory creation, deletion or | |
682 | renaming is possible. Note only non-resident files can be written to | |
683 | so you may find that some very small files (<500 bytes or so) cannot | |
684 | be written to. | |
685 | ||
686 | While we cannot guarantee that it will not damage any data, we have | |
687 | so far not received a single report where the driver would have | |
688 | damaged someones data so we assume it is perfectly safe to use. | |
689 | ||
690 | Note: While write support is safe in this version (a rewrite from | |
691 | scratch of the NTFS support), it should be noted that the old NTFS | |
692 | write support, included in Linux 2.5.10 and before (since 1997), | |
693 | is not safe. | |
694 | ||
695 | This is currently useful with TopologiLinux. TopologiLinux is run | |
696 | on top of any DOS/Microsoft Windows system without partitioning your | |
697 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
698 | need its own partition. For more information see | |
699 | <http://topologi-linux.sourceforge.net/> | |
700 | ||
701 | It is perfectly safe to say N here. | |
702 | ||
703 | endmenu | |
704 | ||
705 | menu "Pseudo filesystems" | |
706 | ||
707 | config PROC_FS | |
708 | bool "/proc file system support" | |
709 | help | |
710 | This is a virtual file system providing information about the status | |
711 | of the system. "Virtual" means that it doesn't take up any space on | |
712 | your hard disk: the files are created on the fly by the kernel when | |
713 | you try to access them. Also, you cannot read the files with older | |
714 | version of the program less: you need to use more or cat. | |
715 | ||
716 | It's totally cool; for example, "cat /proc/interrupts" gives | |
717 | information about what the different IRQs are used for at the moment | |
718 | (there is a small number of Interrupt ReQuest lines in your computer | |
719 | that are used by the attached devices to gain the CPU's attention -- | |
720 | often a source of trouble if two devices are mistakenly configured | |
721 | to use the same IRQ). The program procinfo to display some | |
722 | information about your system gathered from the /proc file system. | |
723 | ||
724 | Before you can use the /proc file system, it has to be mounted, | |
725 | meaning it has to be given a location in the directory hierarchy. | |
726 | That location should be /proc. A command such as "mount -t proc proc | |
727 | /proc" or the equivalent line in /etc/fstab does the job. | |
728 | ||
729 | The /proc file system is explained in the file | |
730 | <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage | |
731 | ("man 5 proc"). | |
732 | ||
733 | This option will enlarge your kernel by about 67 KB. Several | |
734 | programs depend on this, so everyone should say Y here. | |
735 | ||
736 | config PROC_KCORE | |
737 | bool "/proc/kcore support" if !ARM | |
738 | depends on PROC_FS && MMU | |
739 | ||
666bfddb VG |
740 | config PROC_VMCORE |
741 | bool "/proc/vmcore support (EXPERIMENTAL)" | |
742 | depends on PROC_FS && EMBEDDED && EXPERIMENTAL && CRASH_DUMP | |
743 | help | |
744 | Exports the dump image of crashed kernel in ELF format. | |
745 | ||
1da177e4 LT |
746 | config SYSFS |
747 | bool "sysfs file system support" if EMBEDDED | |
748 | default y | |
749 | help | |
750 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
751 | export internal kernel objects, their attributes, and their | |
752 | relationships to one another. | |
753 | ||
754 | Users can use sysfs to ascertain useful information about the running | |
755 | kernel, such as the devices the kernel has discovered on each bus and | |
756 | which driver each is bound to. sysfs can also be used to tune devices | |
757 | and other kernel subsystems. | |
758 | ||
759 | Some system agents rely on the information in sysfs to operate. | |
760 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
761 | delegating policy decisions, like persistantly naming devices. | |
762 | ||
763 | sysfs is currently used by the block subsystem to mount the root | |
764 | partition. If sysfs is disabled you must specify the boot device on | |
765 | the kernel boot command line via its major and minor numbers. For | |
766 | example, "root=03:01" for /dev/hda1. | |
767 | ||
768 | Designers of embedded systems may wish to say N here to conserve space. | |
769 | ||
1da177e4 LT |
770 | config DEVPTS_FS_XATTR |
771 | bool "/dev/pts Extended Attributes" | |
772 | depends on UNIX98_PTYS | |
773 | help | |
774 | Extended attributes are name:value pairs associated with inodes by | |
775 | the kernel or by users (see the attr(5) manual page, or visit | |
776 | <http://acl.bestbits.at/> for details). | |
777 | ||
778 | If unsure, say N. | |
779 | ||
780 | config DEVPTS_FS_SECURITY | |
781 | bool "/dev/pts Security Labels" | |
782 | depends on DEVPTS_FS_XATTR | |
783 | help | |
784 | Security labels support alternative access control models | |
785 | implemented by security modules like SELinux. This option | |
786 | enables an extended attribute handler for file security | |
787 | labels in the /dev/pts filesystem. | |
788 | ||
789 | If you are not using a security module that requires using | |
790 | extended attributes for file security labels, say N. | |
791 | ||
792 | config TMPFS | |
793 | bool "Virtual memory file system support (former shm fs)" | |
794 | help | |
795 | Tmpfs is a file system which keeps all files in virtual memory. | |
796 | ||
797 | Everything in tmpfs is temporary in the sense that no files will be | |
798 | created on your hard drive. The files live in memory and swap | |
799 | space. If you unmount a tmpfs instance, everything stored therein is | |
800 | lost. | |
801 | ||
802 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
803 | ||
804 | config TMPFS_XATTR | |
805 | bool "tmpfs Extended Attributes" | |
806 | depends on TMPFS | |
807 | help | |
808 | Extended attributes are name:value pairs associated with inodes by | |
809 | the kernel or by users (see the attr(5) manual page, or visit | |
810 | <http://acl.bestbits.at/> for details). | |
811 | ||
812 | If unsure, say N. | |
813 | ||
814 | config TMPFS_SECURITY | |
815 | bool "tmpfs Security Labels" | |
816 | depends on TMPFS_XATTR | |
817 | help | |
818 | Security labels support alternative access control models | |
819 | implemented by security modules like SELinux. This option | |
820 | enables an extended attribute handler for file security | |
821 | labels in the tmpfs filesystem. | |
822 | If you are not using a security module that requires using | |
823 | extended attributes for file security labels, say N. | |
824 | ||
825 | config HUGETLBFS | |
826 | bool "HugeTLB file system support" | |
827 | depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN | |
828 | ||
829 | config HUGETLB_PAGE | |
830 | def_bool HUGETLBFS | |
831 | ||
832 | config RAMFS | |
833 | bool | |
834 | default y | |
835 | ---help--- | |
836 | Ramfs is a file system which keeps all files in RAM. It allows | |
837 | read and write access. | |
838 | ||
839 | It is more of an programming example than a useable file system. If | |
840 | you need a file system which lives in RAM with limit checking use | |
841 | tmpfs. | |
842 | ||
843 | To compile this as a module, choose M here: the module will be called | |
844 | ramfs. | |
845 | ||
846 | endmenu | |
847 | ||
848 | menu "Miscellaneous filesystems" | |
849 | ||
850 | config ADFS_FS | |
851 | tristate "ADFS file system support (EXPERIMENTAL)" | |
852 | depends on EXPERIMENTAL | |
853 | help | |
854 | The Acorn Disc Filing System is the standard file system of the | |
855 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
856 | systems and the Acorn Archimedes range of machines. If you say Y | |
857 | here, Linux will be able to read from ADFS partitions on hard drives | |
858 | and from ADFS-formatted floppy discs. If you also want to be able to | |
859 | write to those devices, say Y to "ADFS write support" below. | |
860 | ||
861 | The ADFS partition should be the first partition (i.e., | |
862 | /dev/[hs]d?1) on each of your drives. Please read the file | |
863 | <file:Documentation/filesystems/adfs.txt> for further details. | |
864 | ||
865 | To compile this code as a module, choose M here: the module will be | |
866 | called adfs. | |
867 | ||
868 | If unsure, say N. | |
869 | ||
870 | config ADFS_FS_RW | |
871 | bool "ADFS write support (DANGEROUS)" | |
872 | depends on ADFS_FS | |
873 | help | |
874 | If you say Y here, you will be able to write to ADFS partitions on | |
875 | hard drives and ADFS-formatted floppy disks. This is experimental | |
876 | codes, so if you're unsure, say N. | |
877 | ||
878 | config AFFS_FS | |
879 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
880 | depends on EXPERIMENTAL | |
881 | help | |
882 | The Fast File System (FFS) is the common file system used on hard | |
883 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
884 | if you want to be able to read and write files from and to an Amiga | |
885 | FFS partition on your hard drive. Amiga floppies however cannot be | |
886 | read with this driver due to an incompatibility of the floppy | |
887 | controller used in an Amiga and the standard floppy controller in | |
888 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
889 | and <file:fs/affs/Changes>. | |
890 | ||
891 | With this driver you can also mount disk files used by Bernd | |
892 | Schmidt's Un*X Amiga Emulator | |
893 | (<http://www.freiburg.linux.de/~uae/>). | |
894 | If you want to do this, you will also need to say Y or M to "Loop | |
895 | device support", above. | |
896 | ||
897 | To compile this file system support as a module, choose M here: the | |
898 | module will be called affs. If unsure, say N. | |
899 | ||
900 | config HFS_FS | |
901 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
902 | depends on EXPERIMENTAL | |
903 | help | |
904 | If you say Y here, you will be able to mount Macintosh-formatted | |
905 | floppy disks and hard drive partitions with full read-write access. | |
906 | Please read <file:fs/hfs/HFS.txt> to learn about the available mount | |
907 | options. | |
908 | ||
909 | To compile this file system support as a module, choose M here: the | |
910 | module will be called hfs. | |
911 | ||
912 | config HFSPLUS_FS | |
913 | tristate "Apple Extended HFS file system support" | |
914 | select NLS | |
915 | select NLS_UTF8 | |
916 | help | |
917 | If you say Y here, you will be able to mount extended format | |
918 | Macintosh-formatted hard drive partitions with full read-write access. | |
919 | ||
920 | This file system is often called HFS+ and was introduced with | |
921 | MacOS 8. It includes all Mac specific filesystem data such as | |
922 | data forks and creator codes, but it also has several UNIX | |
923 | style features such as file ownership and permissions. | |
924 | ||
925 | config BEFS_FS | |
926 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
927 | depends on EXPERIMENTAL | |
928 | select NLS | |
929 | help | |
930 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
931 | BeOS. Notable features include support for arbitrary attributes | |
932 | on files and directories, and database-like indeces on selected | |
933 | attributes. (Also note that this driver doesn't make those features | |
934 | available at this time). It is a 64 bit filesystem, so it supports | |
935 | extremly large volumes and files. | |
936 | ||
937 | If you use this filesystem, you should also say Y to at least one | |
938 | of the NLS (native language support) options below. | |
939 | ||
940 | If you don't know what this is about, say N. | |
941 | ||
942 | To compile this as a module, choose M here: the module will be | |
943 | called befs. | |
944 | ||
945 | config BEFS_DEBUG | |
946 | bool "Debug BeFS" | |
947 | depends on BEFS_FS | |
948 | help | |
949 | If you say Y here, you can use the 'debug' mount option to enable | |
950 | debugging output from the driver. | |
951 | ||
952 | config BFS_FS | |
953 | tristate "BFS file system support (EXPERIMENTAL)" | |
954 | depends on EXPERIMENTAL | |
955 | help | |
956 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
957 | allow the bootloader access to the kernel image and other important | |
958 | files during the boot process. It is usually mounted under /stand | |
959 | and corresponds to the slice marked as "STAND" in the UnixWare | |
960 | partition. You should say Y if you want to read or write the files | |
961 | on your /stand slice from within Linux. You then also need to say Y | |
962 | to "UnixWare slices support", below. More information about the BFS | |
963 | file system is contained in the file | |
964 | <file:Documentation/filesystems/bfs.txt>. | |
965 | ||
966 | If you don't know what this is about, say N. | |
967 | ||
968 | To compile this as a module, choose M here: the module will be called | |
969 | bfs. Note that the file system of your root partition (the one | |
970 | containing the directory /) cannot be compiled as a module. | |
971 | ||
972 | ||
973 | ||
974 | config EFS_FS | |
975 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
976 | depends on EXPERIMENTAL | |
977 | help | |
978 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
979 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
980 | uses the XFS file system for hard disk partitions however). | |
981 | ||
982 | This implementation only offers read-only access. If you don't know | |
983 | what all this is about, it's safe to say N. For more information | |
984 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
985 | ||
986 | To compile the EFS file system support as a module, choose M here: the | |
987 | module will be called efs. | |
988 | ||
989 | config JFFS_FS | |
990 | tristate "Journalling Flash File System (JFFS) support" | |
991 | depends on MTD | |
992 | help | |
993 | JFFS is the Journaling Flash File System developed by Axis | |
994 | Communications in Sweden, aimed at providing a crash/powerdown-safe | |
995 | file system for disk-less embedded devices. Further information is | |
996 | available at (<http://developer.axis.com/software/jffs/>). | |
997 | ||
998 | config JFFS_FS_VERBOSE | |
999 | int "JFFS debugging verbosity (0 = quiet, 3 = noisy)" | |
1000 | depends on JFFS_FS | |
1001 | default "0" | |
1002 | help | |
1003 | Determines the verbosity level of the JFFS debugging messages. | |
1004 | ||
1005 | config JFFS_PROC_FS | |
1006 | bool "JFFS stats available in /proc filesystem" | |
1007 | depends on JFFS_FS && PROC_FS | |
1008 | help | |
1009 | Enabling this option will cause statistics from mounted JFFS file systems | |
1010 | to be made available to the user in the /proc/fs/jffs/ directory. | |
1011 | ||
1012 | config JFFS2_FS | |
1013 | tristate "Journalling Flash File System v2 (JFFS2) support" | |
1014 | select CRC32 | |
1015 | depends on MTD | |
1016 | help | |
1017 | JFFS2 is the second generation of the Journalling Flash File System | |
1018 | for use on diskless embedded devices. It provides improved wear | |
1019 | levelling, compression and support for hard links. You cannot use | |
1020 | this on normal block devices, only on 'MTD' devices. | |
1021 | ||
1022 | Further information on the design and implementation of JFFS2 is | |
1023 | available at <http://sources.redhat.com/jffs2/>. | |
1024 | ||
1025 | config JFFS2_FS_DEBUG | |
1026 | int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" | |
1027 | depends on JFFS2_FS | |
1028 | default "0" | |
1029 | help | |
1030 | This controls the amount of debugging messages produced by the JFFS2 | |
1031 | code. Set it to zero for use in production systems. For evaluation, | |
1032 | testing and debugging, it's advisable to set it to one. This will | |
1033 | enable a few assertions and will print debugging messages at the | |
1034 | KERN_DEBUG loglevel, where they won't normally be visible. Level 2 | |
1035 | is unlikely to be useful - it enables extra debugging in certain | |
1036 | areas which at one point needed debugging, but when the bugs were | |
1037 | located and fixed, the detailed messages were relegated to level 2. | |
1038 | ||
1039 | If reporting bugs, please try to have available a full dump of the | |
1040 | messages at debug level 1 while the misbehaviour was occurring. | |
1041 | ||
1042 | config JFFS2_FS_NAND | |
1043 | bool "JFFS2 support for NAND flash" | |
1044 | depends on JFFS2_FS | |
1045 | default n | |
1046 | help | |
1047 | This enables the support for NAND flash in JFFS2. NAND is a newer | |
1048 | type of flash chip design than the traditional NOR flash, with | |
1049 | higher density but a handful of characteristics which make it more | |
1050 | interesting for the file system to use. | |
1051 | ||
1052 | Say 'N' unless you have NAND flash. | |
1053 | ||
1054 | config JFFS2_FS_NOR_ECC | |
1055 | bool "JFFS2 support for ECC'd NOR flash (EXPERIMENTAL)" | |
1056 | depends on JFFS2_FS && EXPERIMENTAL | |
1057 | default n | |
1058 | help | |
1059 | This enables the experimental support for NOR flash with transparent | |
1060 | ECC for JFFS2. This type of flash chip is not common, however it is | |
1061 | available from ST Microelectronics. | |
1062 | ||
1063 | config JFFS2_COMPRESSION_OPTIONS | |
1064 | bool "Advanced compression options for JFFS2" | |
1065 | depends on JFFS2_FS | |
1066 | default n | |
1067 | help | |
1068 | Enabling this option allows you to explicitly choose which | |
1069 | compression modules, if any, are enabled in JFFS2. Removing | |
1070 | compressors and mean you cannot read existing file systems, | |
1071 | and enabling experimental compressors can mean that you | |
1072 | write a file system which cannot be read by a standard kernel. | |
1073 | ||
1074 | If unsure, you should _definitely_ say 'N'. | |
1075 | ||
1076 | config JFFS2_ZLIB | |
1077 | bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS | |
1078 | select ZLIB_INFLATE | |
1079 | select ZLIB_DEFLATE | |
1080 | depends on JFFS2_FS | |
1081 | default y | |
1082 | help | |
1083 | Zlib is designed to be a free, general-purpose, legally unencumbered, | |
1084 | lossless data-compression library for use on virtually any computer | |
1085 | hardware and operating system. See <http://www.gzip.org/zlib/> for | |
1086 | further information. | |
1087 | ||
1088 | Say 'Y' if unsure. | |
1089 | ||
1090 | config JFFS2_RTIME | |
1091 | bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS | |
1092 | depends on JFFS2_FS | |
1093 | default y | |
1094 | help | |
1095 | Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. | |
1096 | ||
1097 | config JFFS2_RUBIN | |
1098 | bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS | |
1099 | depends on JFFS2_FS | |
1100 | default n | |
1101 | help | |
1102 | RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. | |
1103 | ||
1104 | choice | |
1105 | prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS | |
1106 | default JFFS2_CMODE_PRIORITY | |
1107 | depends on JFFS2_FS | |
1108 | help | |
1109 | You can set here the default compression mode of JFFS2 from | |
1110 | the available compression modes. Don't touch if unsure. | |
1111 | ||
1112 | config JFFS2_CMODE_NONE | |
1113 | bool "no compression" | |
1114 | help | |
1115 | Uses no compression. | |
1116 | ||
1117 | config JFFS2_CMODE_PRIORITY | |
1118 | bool "priority" | |
1119 | help | |
1120 | Tries the compressors in a predefinied order and chooses the first | |
1121 | successful one. | |
1122 | ||
1123 | config JFFS2_CMODE_SIZE | |
1124 | bool "size (EXPERIMENTAL)" | |
1125 | help | |
1126 | Tries all compressors and chooses the one which has the smallest | |
1127 | result. | |
1128 | ||
1129 | endchoice | |
1130 | ||
1131 | config CRAMFS | |
1132 | tristate "Compressed ROM file system support (cramfs)" | |
1133 | select ZLIB_INFLATE | |
1134 | help | |
1135 | Saying Y here includes support for CramFs (Compressed ROM File | |
1136 | System). CramFs is designed to be a simple, small, and compressed | |
1137 | file system for ROM based embedded systems. CramFs is read-only, | |
1138 | limited to 256MB file systems (with 16MB files), and doesn't support | |
1139 | 16/32 bits uid/gid, hard links and timestamps. | |
1140 | ||
1141 | See <file:Documentation/filesystems/cramfs.txt> and | |
1142 | <file:fs/cramfs/README> for further information. | |
1143 | ||
1144 | To compile this as a module, choose M here: the module will be called | |
1145 | cramfs. Note that the root file system (the one containing the | |
1146 | directory /) cannot be compiled as a module. | |
1147 | ||
1148 | If unsure, say N. | |
1149 | ||
1150 | config VXFS_FS | |
1151 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
1152 | help | |
1153 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
1154 | file system format. VERITAS VxFS(TM) is the standard file system | |
1155 | of SCO UnixWare (and possibly others) and optionally available | |
1156 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
1157 | Currently only readonly access is supported. | |
1158 | ||
1159 | NOTE: the file system type as used by mount(1), mount(2) and | |
1160 | fstab(5) is 'vxfs' as it describes the file system format, not | |
1161 | the actual driver. | |
1162 | ||
1163 | To compile this as a module, choose M here: the module will be | |
1164 | called freevxfs. If unsure, say N. | |
1165 | ||
1166 | ||
1167 | config HPFS_FS | |
1168 | tristate "OS/2 HPFS file system support" | |
1169 | help | |
1170 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
1171 | is the file system used for organizing files on OS/2 hard disk | |
1172 | partitions. Say Y if you want to be able to read files from and | |
1173 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
1174 | floppies however are in regular MSDOS format, so you don't need this | |
1175 | option in order to be able to read them. Read | |
1176 | <file:Documentation/filesystems/hpfs.txt>. | |
1177 | ||
1178 | To compile this file system support as a module, choose M here: the | |
1179 | module will be called hpfs. If unsure, say N. | |
1180 | ||
1181 | ||
1182 | ||
1183 | config QNX4FS_FS | |
1184 | tristate "QNX4 file system support (read only)" | |
1185 | help | |
1186 | This is the file system used by the real-time operating systems | |
1187 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
1188 | Further information is available at <http://www.qnx.com/>. | |
1189 | Say Y if you intend to mount QNX hard disks or floppies. | |
1190 | Unless you say Y to "QNX4FS read-write support" below, you will | |
1191 | only be able to read these file systems. | |
1192 | ||
1193 | To compile this file system support as a module, choose M here: the | |
1194 | module will be called qnx4. | |
1195 | ||
1196 | If you don't know whether you need it, then you don't need it: | |
1197 | answer N. | |
1198 | ||
1199 | config QNX4FS_RW | |
1200 | bool "QNX4FS write support (DANGEROUS)" | |
1201 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
1202 | help | |
1203 | Say Y if you want to test write support for QNX4 file systems. | |
1204 | ||
1205 | It's currently broken, so for now: | |
1206 | answer N. | |
1207 | ||
1208 | ||
1209 | ||
1210 | config SYSV_FS | |
1211 | tristate "System V/Xenix/V7/Coherent file system support" | |
1212 | help | |
1213 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
1214 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
1215 | here would allow you to read from their floppies and hard disk | |
1216 | partitions. | |
1217 | ||
1218 | If you have floppies or hard disk partitions like that, it is likely | |
1219 | that they contain binaries from those other Unix systems; in order | |
1220 | to run these binaries, you will want to install linux-abi which is a | |
1221 | a set of kernel modules that lets you run SCO, Xenix, Wyse, | |
1222 | UnixWare, Dell Unix and System V programs under Linux. It is | |
1223 | available via FTP (user: ftp) from | |
1224 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
1225 | NOTE: that will work only for binaries from Intel-based systems; | |
1226 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
1227 | ||
1228 | If you only intend to mount files from some other Unix over the | |
1229 | network using NFS, you don't need the System V file system support | |
1230 | (but you need NFS file system support obviously). | |
1231 | ||
1232 | Note that this option is generally not needed for floppies, since a | |
1233 | good portable way to transport files and directories between unixes | |
1234 | (and even other operating systems) is given by the tar program ("man | |
1235 | tar" or preferably "info tar"). Note also that this option has | |
1236 | nothing whatsoever to do with the option "System V IPC". Read about | |
1237 | the System V file system in | |
1238 | <file:Documentation/filesystems/sysv-fs.txt>. | |
1239 | Saying Y here will enlarge your kernel by about 27 KB. | |
1240 | ||
1241 | To compile this as a module, choose M here: the module will be called | |
1242 | sysv. | |
1243 | ||
1244 | If you haven't heard about all of this before, it's safe to say N. | |
1245 | ||
1246 | ||
1247 | ||
1248 | config UFS_FS | |
1249 | tristate "UFS file system support (read only)" | |
1250 | help | |
1251 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
1252 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
1253 | Unixes can create and mount hard disk partitions and diskettes using | |
1254 | this file system as well. Saying Y here will allow you to read from | |
1255 | these partitions; if you also want to write to them, say Y to the | |
1256 | experimental "UFS file system write support", below. Please read the | |
1257 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
1258 | ||
1259 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
1260 | READ-ONLY supported. | |
1261 | ||
1262 | If you only intend to mount files from some other Unix over the | |
1263 | network using NFS, you don't need the UFS file system support (but | |
1264 | you need NFS file system support obviously). | |
1265 | ||
1266 | Note that this option is generally not needed for floppies, since a | |
1267 | good portable way to transport files and directories between unixes | |
1268 | (and even other operating systems) is given by the tar program ("man | |
1269 | tar" or preferably "info tar"). | |
1270 | ||
1271 | When accessing NeXTstep files, you may need to convert them from the | |
1272 | NeXT character set to the Latin1 character set; use the program | |
1273 | recode ("info recode") for this purpose. | |
1274 | ||
1275 | To compile the UFS file system support as a module, choose M here: the | |
1276 | module will be called ufs. | |
1277 | ||
1278 | If you haven't heard about all of this before, it's safe to say N. | |
1279 | ||
1280 | config UFS_FS_WRITE | |
1281 | bool "UFS file system write support (DANGEROUS)" | |
1282 | depends on UFS_FS && EXPERIMENTAL | |
1283 | help | |
1284 | Say Y here if you want to try writing to UFS partitions. This is | |
1285 | experimental, so you should back up your UFS partitions beforehand. | |
1286 | ||
1287 | endmenu | |
1288 | ||
1289 | menu "Network File Systems" | |
1290 | depends on NET | |
1291 | ||
1292 | config NFS_FS | |
1293 | tristate "NFS file system support" | |
1294 | depends on INET | |
1295 | select LOCKD | |
1296 | select SUNRPC | |
b7fa0554 | 1297 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 LT |
1298 | help |
1299 | If you are connected to some other (usually local) Unix computer | |
1300 | (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing | |
1301 | on that computer (the NFS server) using the Network File Sharing | |
1302 | protocol, say Y. "Mounting files" means that the client can access | |
1303 | the files with usual UNIX commands as if they were sitting on the | |
1304 | client's hard disk. For this to work, the server must run the | |
1305 | programs nfsd and mountd (but does not need to have NFS file system | |
1306 | support enabled in its kernel). NFS is explained in the Network | |
1307 | Administrator's Guide, available from | |
1308 | <http://www.tldp.org/docs.html#guide>, on its man page: "man | |
1309 | nfs", and in the NFS-HOWTO. | |
1310 | ||
1311 | A superior but less widely used alternative to NFS is provided by | |
1312 | the Coda file system; see "Coda file system support" below. | |
1313 | ||
1314 | If you say Y here, you should have said Y to TCP/IP networking also. | |
1315 | This option would enlarge your kernel by about 27 KB. | |
1316 | ||
1317 | To compile this file system support as a module, choose M here: the | |
1318 | module will be called nfs. | |
1319 | ||
1320 | If you are configuring a diskless machine which will mount its root | |
1321 | file system over NFS at boot time, say Y here and to "Kernel | |
1322 | level IP autoconfiguration" above and to "Root file system on NFS" | |
1323 | below. You cannot compile this driver as a module in this case. | |
1324 | There are two packages designed for booting diskless machines over | |
1325 | the net: netboot, available from | |
1326 | <http://ftp1.sourceforge.net/netboot/>, and Etherboot, | |
1327 | available from <http://ftp1.sourceforge.net/etherboot/>. | |
1328 | ||
1329 | If you don't know what all this is about, say N. | |
1330 | ||
1331 | config NFS_V3 | |
1332 | bool "Provide NFSv3 client support" | |
1333 | depends on NFS_FS | |
1334 | help | |
1335 | Say Y here if you want your NFS client to be able to speak version | |
1336 | 3 of the NFS protocol. | |
1337 | ||
1338 | If unsure, say Y. | |
1339 | ||
b7fa0554 AG |
1340 | config NFS_V3_ACL |
1341 | bool "Provide client support for the NFSv3 ACL protocol extension" | |
1342 | depends on NFS_V3 | |
1343 | help | |
1344 | Implement the NFSv3 ACL protocol extension for manipulating POSIX | |
1345 | Access Control Lists. The server should also be compiled with | |
1346 | the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option. | |
1347 | ||
1348 | If unsure, say N. | |
1349 | ||
1da177e4 LT |
1350 | config NFS_V4 |
1351 | bool "Provide NFSv4 client support (EXPERIMENTAL)" | |
1352 | depends on NFS_FS && EXPERIMENTAL | |
1353 | select RPCSEC_GSS_KRB5 | |
1354 | help | |
1355 | Say Y here if you want your NFS client to be able to speak the newer | |
1356 | version 4 of the NFS protocol. | |
1357 | ||
1358 | Note: Requires auxiliary userspace daemons which may be found on | |
1359 | http://www.citi.umich.edu/projects/nfsv4/ | |
1360 | ||
1361 | If unsure, say N. | |
1362 | ||
1363 | config NFS_DIRECTIO | |
1364 | bool "Allow direct I/O on NFS files (EXPERIMENTAL)" | |
1365 | depends on NFS_FS && EXPERIMENTAL | |
1366 | help | |
1367 | This option enables applications to perform uncached I/O on files | |
1368 | in NFS file systems using the O_DIRECT open() flag. When O_DIRECT | |
1369 | is set for a file, its data is not cached in the system's page | |
1370 | cache. Data is moved to and from user-level application buffers | |
1371 | directly. Unlike local disk-based file systems, NFS O_DIRECT has | |
1372 | no alignment restrictions. | |
1373 | ||
1374 | Unless your program is designed to use O_DIRECT properly, you are | |
1375 | much better off allowing the NFS client to manage data caching for | |
1376 | you. Misusing O_DIRECT can cause poor server performance or network | |
1377 | storms. This kernel build option defaults OFF to avoid exposing | |
1378 | system administrators unwittingly to a potentially hazardous | |
1379 | feature. | |
1380 | ||
1381 | For more details on NFS O_DIRECT, see fs/nfs/direct.c. | |
1382 | ||
1383 | If unsure, say N. This reduces the size of the NFS client, and | |
1384 | causes open() to return EINVAL if a file residing in NFS is | |
1385 | opened with the O_DIRECT flag. | |
1386 | ||
1387 | config NFSD | |
1388 | tristate "NFS server support" | |
1389 | depends on INET | |
1390 | select LOCKD | |
1391 | select SUNRPC | |
1392 | select EXPORTFS | |
a257cdd0 | 1393 | select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL |
1da177e4 LT |
1394 | help |
1395 | If you want your Linux box to act as an NFS *server*, so that other | |
1396 | computers on your local network which support NFS can access certain | |
1397 | directories on your box transparently, you have two options: you can | |
1398 | use the self-contained user space program nfsd, in which case you | |
1399 | should say N here, or you can say Y and use the kernel based NFS | |
1400 | server. The advantage of the kernel based solution is that it is | |
1401 | faster. | |
1402 | ||
1403 | In either case, you will need support software; the respective | |
1404 | locations are given in the file <file:Documentation/Changes> in the | |
1405 | NFS section. | |
1406 | ||
1407 | If you say Y here, you will get support for version 2 of the NFS | |
1408 | protocol (NFSv2). If you also want NFSv3, say Y to the next question | |
1409 | as well. | |
1410 | ||
1411 | Please read the NFS-HOWTO, available from | |
1412 | <http://www.tldp.org/docs.html#howto>. | |
1413 | ||
1414 | To compile the NFS server support as a module, choose M here: the | |
1415 | module will be called nfsd. If unsure, say N. | |
1416 | ||
a257cdd0 AG |
1417 | config NFSD_V2_ACL |
1418 | bool | |
1419 | depends on NFSD | |
1420 | ||
1da177e4 LT |
1421 | config NFSD_V3 |
1422 | bool "Provide NFSv3 server support" | |
1423 | depends on NFSD | |
1424 | help | |
1425 | If you would like to include the NFSv3 server as well as the NFSv2 | |
1426 | server, say Y here. If unsure, say Y. | |
1427 | ||
a257cdd0 AG |
1428 | config NFSD_V3_ACL |
1429 | bool "Provide server support for the NFSv3 ACL protocol extension" | |
1430 | depends on NFSD_V3 | |
1431 | select NFSD_V2_ACL | |
1432 | help | |
1433 | Implement the NFSv3 ACL protocol extension for manipulating POSIX | |
1434 | Access Control Lists on exported file systems. NFS clients should | |
1435 | be compiled with the NFSv3 ACL protocol extension; see the | |
1436 | CONFIG_NFS_V3_ACL option. If unsure, say N. | |
1437 | ||
1da177e4 LT |
1438 | config NFSD_V4 |
1439 | bool "Provide NFSv4 server support (EXPERIMENTAL)" | |
1440 | depends on NFSD_V3 && EXPERIMENTAL | |
1441 | select NFSD_TCP | |
a55370a3 N |
1442 | select CRYPTO_MD5 |
1443 | select CRYPTO | |
b84c2157 | 1444 | select FS_POSIX_ACL |
1da177e4 LT |
1445 | help |
1446 | If you would like to include the NFSv4 server as well as the NFSv2 | |
1447 | and NFSv3 servers, say Y here. This feature is experimental, and | |
1448 | should only be used if you are interested in helping to test NFSv4. | |
1449 | If unsure, say N. | |
1450 | ||
1451 | config NFSD_TCP | |
1452 | bool "Provide NFS server over TCP support" | |
1453 | depends on NFSD | |
1454 | default y | |
1455 | help | |
1456 | If you want your NFS server to support TCP connections, say Y here. | |
1457 | TCP connections usually perform better than the default UDP when | |
1458 | the network is lossy or congested. If unsure, say Y. | |
1459 | ||
1460 | config ROOT_NFS | |
1461 | bool "Root file system on NFS" | |
1462 | depends on NFS_FS=y && IP_PNP | |
1463 | help | |
1464 | If you want your Linux box to mount its whole root file system (the | |
1465 | one containing the directory /) from some other computer over the | |
1466 | net via NFS (presumably because your box doesn't have a hard disk), | |
1467 | say Y. Read <file:Documentation/nfsroot.txt> for details. It is | |
1468 | likely that in this case, you also want to say Y to "Kernel level IP | |
1469 | autoconfiguration" so that your box can discover its network address | |
1470 | at boot time. | |
1471 | ||
1472 | Most people say N here. | |
1473 | ||
1474 | config LOCKD | |
1475 | tristate | |
1476 | ||
1477 | config LOCKD_V4 | |
1478 | bool | |
1479 | depends on NFSD_V3 || NFS_V3 | |
1480 | default y | |
1481 | ||
1482 | config EXPORTFS | |
1483 | tristate | |
1484 | ||
a257cdd0 AG |
1485 | config NFS_ACL_SUPPORT |
1486 | tristate | |
1487 | select FS_POSIX_ACL | |
1488 | ||
1489 | config NFS_COMMON | |
1490 | bool | |
1491 | depends on NFSD || NFS_FS | |
1492 | default y | |
1493 | ||
1da177e4 LT |
1494 | config SUNRPC |
1495 | tristate | |
1496 | ||
1497 | config SUNRPC_GSS | |
1498 | tristate | |
1499 | ||
1500 | config RPCSEC_GSS_KRB5 | |
1501 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
1502 | depends on SUNRPC && EXPERIMENTAL | |
1503 | select SUNRPC_GSS | |
1504 | select CRYPTO | |
1505 | select CRYPTO_MD5 | |
1506 | select CRYPTO_DES | |
1507 | help | |
1508 | Provides for secure RPC calls by means of a gss-api | |
1509 | mechanism based on Kerberos V5. This is required for | |
1510 | NFSv4. | |
1511 | ||
1512 | Note: Requires an auxiliary userspace daemon which may be found on | |
1513 | http://www.citi.umich.edu/projects/nfsv4/ | |
1514 | ||
1515 | If unsure, say N. | |
1516 | ||
1517 | config RPCSEC_GSS_SPKM3 | |
1518 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1519 | depends on SUNRPC && EXPERIMENTAL | |
1520 | select SUNRPC_GSS | |
1521 | select CRYPTO | |
1522 | select CRYPTO_MD5 | |
1523 | select CRYPTO_DES | |
1524 | help | |
1525 | Provides for secure RPC calls by means of a gss-api | |
1526 | mechanism based on the SPKM3 public-key mechanism. | |
1527 | ||
1528 | Note: Requires an auxiliary userspace daemon which may be found on | |
1529 | http://www.citi.umich.edu/projects/nfsv4/ | |
1530 | ||
1531 | If unsure, say N. | |
1532 | ||
1533 | config SMB_FS | |
1534 | tristate "SMB file system support (to mount Windows shares etc.)" | |
1535 | depends on INET | |
1536 | select NLS | |
1537 | help | |
1538 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1539 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1540 | files and printers over local networks. Saying Y here allows you to | |
1541 | mount their file systems (often called "shares" in this context) and | |
1542 | access them just like any other Unix directory. Currently, this | |
1543 | works only if the Windows machines use TCP/IP as the underlying | |
1544 | transport protocol, and not NetBEUI. For details, read | |
1545 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1546 | available from <http://www.tldp.org/docs.html#howto>. | |
1547 | ||
1548 | Note: if you just want your box to act as an SMB *server* and make | |
1549 | files and printing services available to Windows clients (which need | |
1550 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1551 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1552 | for that. | |
1553 | ||
1554 | General information about how to connect Linux, Windows machines and | |
1555 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1556 | ||
1557 | To compile the SMB support as a module, choose M here: the module will | |
1558 | be called smbfs. Most people say N, however. | |
1559 | ||
1560 | config SMB_NLS_DEFAULT | |
1561 | bool "Use a default NLS" | |
1562 | depends on SMB_FS | |
1563 | help | |
1564 | Enabling this will make smbfs use nls translations by default. You | |
1565 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1566 | settings and you need to give the default nls for the SMB server as | |
1567 | CONFIG_SMB_NLS_REMOTE. | |
1568 | ||
1569 | The nls settings can be changed at mount time, if your smbmount | |
1570 | supports that, using the codepage and iocharset parameters. | |
1571 | ||
1572 | smbmount from samba 2.2.0 or later supports this. | |
1573 | ||
1574 | config SMB_NLS_REMOTE | |
1575 | string "Default Remote NLS Option" | |
1576 | depends on SMB_NLS_DEFAULT | |
1577 | default "cp437" | |
1578 | help | |
1579 | This setting allows you to specify a default value for which | |
1580 | codepage the server uses. If this field is left blank no | |
1581 | translations will be done by default. The local codepage/charset | |
1582 | default to CONFIG_NLS_DEFAULT. | |
1583 | ||
1584 | The nls settings can be changed at mount time, if your smbmount | |
1585 | supports that, using the codepage and iocharset parameters. | |
1586 | ||
1587 | smbmount from samba 2.2.0 or later supports this. | |
1588 | ||
1589 | config CIFS | |
1590 | tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)" | |
1591 | depends on INET | |
1592 | select NLS | |
1593 | help | |
1594 | This is the client VFS module for the Common Internet File System | |
1595 | (CIFS) protocol which is the successor to the Server Message Block | |
1596 | (SMB) protocol, the native file sharing mechanism for most early | |
1597 | PC operating systems. The CIFS protocol is fully supported by | |
1598 | file servers such as Windows 2000 (including Windows 2003, NT 4 | |
1599 | and Windows XP) as well by Samba (which provides excellent CIFS | |
1600 | server support for Linux and many other operating systems). Currently | |
1601 | you must use the smbfs client filesystem to access older SMB servers | |
1602 | such as Windows 9x and OS/2. | |
1603 | ||
1604 | The intent of the cifs module is to provide an advanced | |
1605 | network file system client for mounting to CIFS compliant servers, | |
1606 | including support for dfs (hierarchical name space), secure per-user | |
1607 | session establishment, safe distributed caching (oplock), optional | |
1608 | packet signing, Unicode and other internationalization improvements, | |
1609 | and optional Winbind (nsswitch) integration. You do not need to enable | |
1610 | cifs if running only a (Samba) server. It is possible to enable both | |
1611 | smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003 | |
1612 | and Samba 3 servers, and smbfs for accessing old servers). If you need | |
1613 | to mount to Samba or Windows 2003 servers from this machine, say Y. | |
1614 | ||
1615 | config CIFS_STATS | |
1616 | bool "CIFS statistics" | |
1617 | depends on CIFS | |
1618 | help | |
1619 | Enabling this option will cause statistics for each server share | |
1620 | mounted by the cifs client to be displayed in /proc/fs/cifs/Stats | |
1621 | ||
1622 | config CIFS_XATTR | |
1623 | bool "CIFS extended attributes (EXPERIMENTAL)" | |
1624 | depends on CIFS | |
1625 | help | |
1626 | Extended attributes are name:value pairs associated with inodes by | |
1627 | the kernel or by users (see the attr(5) manual page, or visit | |
1628 | <http://acl.bestbits.at/> for details). CIFS maps the name of | |
1629 | extended attributes beginning with the user namespace prefix | |
1630 | to SMB/CIFS EAs. EAs are stored on Windows servers without the | |
1631 | user namespace prefix, but their names are seen by Linux cifs clients | |
1632 | prefaced by the user namespace prefix. The system namespace | |
1633 | (used by some filesystems to store ACLs) is not supported at | |
1634 | this time. | |
1635 | ||
1636 | If unsure, say N. | |
1637 | ||
1638 | config CIFS_POSIX | |
1639 | bool "CIFS POSIX Extensions (EXPERIMENTAL)" | |
1640 | depends on CIFS_XATTR | |
1641 | help | |
1642 | Enabling this option will cause the cifs client to attempt to | |
1643 | negotiate a newer dialect with servers, such as Samba 3.0.5 | |
1644 | or later, that optionally can handle more POSIX like (rather | |
1645 | than Windows like) file behavior. It also enables | |
1646 | support for POSIX ACLs (getfacl and setfacl) to servers | |
1647 | (such as Samba 3.10 and later) which can negotiate | |
1648 | CIFS POSIX ACL support. If unsure, say N. | |
1649 | ||
1650 | config CIFS_EXPERIMENTAL | |
1651 | bool "CIFS Experimental Features (EXPERIMENTAL)" | |
1652 | depends on CIFS | |
1653 | help | |
1654 | Enables cifs features under testing. These features | |
1655 | are highly experimental. If unsure, say N. | |
1656 | ||
1657 | config NCP_FS | |
1658 | tristate "NCP file system support (to mount NetWare volumes)" | |
1659 | depends on IPX!=n || INET | |
1660 | help | |
1661 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1662 | used by Novell NetWare clients to talk to file servers. It is to | |
1663 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1664 | to mount NetWare file server volumes and to access them just like | |
1665 | any other Unix directory. For details, please read the file | |
1666 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1667 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1668 | ||
1669 | You do not have to say Y here if you want your Linux box to act as a | |
1670 | file *server* for Novell NetWare clients. | |
1671 | ||
1672 | General information about how to connect Linux, Windows machines and | |
1673 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1674 | ||
1675 | To compile this as a module, choose M here: the module will be called | |
1676 | ncpfs. Say N unless you are connected to a Novell network. | |
1677 | ||
1678 | source "fs/ncpfs/Kconfig" | |
1679 | ||
1680 | config CODA_FS | |
1681 | tristate "Coda file system support (advanced network fs)" | |
1682 | depends on INET | |
1683 | help | |
1684 | Coda is an advanced network file system, similar to NFS in that it | |
1685 | enables you to mount file systems of a remote server and access them | |
1686 | with regular Unix commands as if they were sitting on your hard | |
1687 | disk. Coda has several advantages over NFS: support for | |
1688 | disconnected operation (e.g. for laptops), read/write server | |
1689 | replication, security model for authentication and encryption, | |
1690 | persistent client caches and write back caching. | |
1691 | ||
1692 | If you say Y here, your Linux box will be able to act as a Coda | |
1693 | *client*. You will need user level code as well, both for the | |
1694 | client and server. Servers are currently user level, i.e. they need | |
1695 | no kernel support. Please read | |
1696 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1697 | home page <http://www.coda.cs.cmu.edu/>. | |
1698 | ||
1699 | To compile the coda client support as a module, choose M here: the | |
1700 | module will be called coda. | |
1701 | ||
1702 | config CODA_FS_OLD_API | |
1703 | bool "Use 96-bit Coda file identifiers" | |
1704 | depends on CODA_FS | |
1705 | help | |
1706 | A new kernel-userspace API had to be introduced for Coda v6.0 | |
1707 | to support larger 128-bit file identifiers as needed by the | |
1708 | new realms implementation. | |
1709 | ||
1710 | However this new API is not backward compatible with older | |
1711 | clients. If you really need to run the old Coda userspace | |
1712 | cache manager then say Y. | |
1713 | ||
1714 | For most cases you probably want to say N. | |
1715 | ||
1716 | config AFS_FS | |
1717 | # for fs/nls/Config.in | |
1718 | tristate "Andrew File System support (AFS) (Experimental)" | |
1719 | depends on INET && EXPERIMENTAL | |
1720 | select RXRPC | |
1721 | help | |
1722 | If you say Y here, you will get an experimental Andrew File System | |
1723 | driver. It currently only supports unsecured read-only AFS access. | |
1724 | ||
1725 | See <file:Documentation/filesystems/afs.txt> for more intormation. | |
1726 | ||
1727 | If unsure, say N. | |
1728 | ||
1729 | config RXRPC | |
1730 | tristate | |
1731 | ||
1732 | endmenu | |
1733 | ||
1734 | menu "Partition Types" | |
1735 | ||
1736 | source "fs/partitions/Kconfig" | |
1737 | ||
1738 | endmenu | |
1739 | ||
1740 | source "fs/nls/Kconfig" | |
1741 | ||
1742 | endmenu | |
1743 |