]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # File system configuration | |
3 | # | |
4 | ||
5 | menu "File systems" | |
6 | ||
9361401e DH |
7 | if BLOCK |
8 | ||
6da0b38f AD |
9 | source "fs/ext2/Kconfig" |
10 | source "fs/ext3/Kconfig" | |
11 | source "fs/ext4/Kconfig" | |
6d79125b CO |
12 | |
13 | config FS_XIP | |
14 | # execute in place | |
15 | bool | |
16 | depends on EXT2_FS_XIP | |
17 | default y | |
18 | ||
6da0b38f AD |
19 | source "fs/jbd/Kconfig" |
20 | source "fs/jbd2/Kconfig" | |
dab291af | 21 | |
1da177e4 | 22 | config FS_MBCACHE |
02ea2104 | 23 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) |
1da177e4 | 24 | tristate |
2c512397 AB |
25 | default y if EXT2_FS=y && EXT2_FS_XATTR |
26 | default y if EXT3_FS=y && EXT3_FS_XATTR | |
27 | default y if EXT4_FS=y && EXT4_FS_XATTR | |
28 | default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR | |
1da177e4 LT |
29 | |
30 | config REISERFS_FS | |
31 | tristate "Reiserfs support" | |
32 | help | |
33 | Stores not just filenames but the files themselves in a balanced | |
cc2e2767 | 34 | tree. Uses journalling. |
1da177e4 LT |
35 | |
36 | Balanced trees are more efficient than traditional file system | |
37 | architectural foundations. | |
38 | ||
39 | In general, ReiserFS is as fast as ext2, but is very efficient with | |
40 | large directories and small files. Additional patches are needed | |
41 | for NFS and quotas, please see <http://www.namesys.com/> for links. | |
42 | ||
43 | It is more easily extended to have features currently found in | |
44 | database and keyword search systems than block allocation based file | |
45 | systems are. The next version will be so extended, and will support | |
46 | plugins consistent with our motto ``It takes more than a license to | |
47 | make source code open.'' | |
48 | ||
49 | Read <http://www.namesys.com/> to learn more about reiserfs. | |
50 | ||
51 | Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. | |
52 | ||
53 | If you like it, you can pay us to add new features to it that you | |
54 | need, buy a support contract, or pay us to port it to another OS. | |
55 | ||
56 | config REISERFS_CHECK | |
57 | bool "Enable reiserfs debug mode" | |
58 | depends on REISERFS_FS | |
59 | help | |
60 | If you set this to Y, then ReiserFS will perform every check it can | |
61 | possibly imagine of its internal consistency throughout its | |
62 | operation. It will also go substantially slower. More than once we | |
63 | have forgotten that this was on, and then gone despondent over the | |
64 | latest benchmarks.:-) Use of this option allows our team to go all | |
65 | out in checking for consistency when debugging without fear of its | |
66 | effect on end users. If you are on the verge of sending in a bug | |
67 | report, say Y and you might get a useful error message. Almost | |
68 | everyone should say N. | |
69 | ||
70 | config REISERFS_PROC_INFO | |
71 | bool "Stats in /proc/fs/reiserfs" | |
880ebdc5 | 72 | depends on REISERFS_FS && PROC_FS |
1da177e4 LT |
73 | help |
74 | Create under /proc/fs/reiserfs a hierarchy of files, displaying | |
75 | various ReiserFS statistics and internal data at the expense of | |
76 | making your kernel or module slightly larger (+8 KB). This also | |
77 | increases the amount of kernel memory required for each mount. | |
78 | Almost everyone but ReiserFS developers and people fine-tuning | |
79 | reiserfs or tracing problems should say N. | |
80 | ||
81 | config REISERFS_FS_XATTR | |
82 | bool "ReiserFS extended attributes" | |
83 | depends on REISERFS_FS | |
84 | help | |
85 | Extended attributes are name:value pairs associated with inodes by | |
86 | the kernel or by users (see the attr(5) manual page, or visit | |
87 | <http://acl.bestbits.at/> for details). | |
88 | ||
89 | If unsure, say N. | |
90 | ||
91 | config REISERFS_FS_POSIX_ACL | |
92 | bool "ReiserFS POSIX Access Control Lists" | |
93 | depends on REISERFS_FS_XATTR | |
b84c2157 | 94 | select FS_POSIX_ACL |
1da177e4 LT |
95 | help |
96 | Posix Access Control Lists (ACLs) support permissions for users and | |
97 | groups beyond the owner/group/world scheme. | |
98 | ||
99 | To learn more about Access Control Lists, visit the Posix ACLs for | |
100 | Linux website <http://acl.bestbits.at/>. | |
101 | ||
102 | If you don't know what Access Control Lists are, say N | |
103 | ||
104 | config REISERFS_FS_SECURITY | |
105 | bool "ReiserFS Security Labels" | |
106 | depends on REISERFS_FS_XATTR | |
107 | help | |
108 | Security labels support alternative access control models | |
109 | implemented by security modules like SELinux. This option | |
110 | enables an extended attribute handler for file security | |
111 | labels in the ReiserFS filesystem. | |
112 | ||
113 | If you are not using a security module that requires using | |
114 | extended attributes for file security labels, say N. | |
115 | ||
116 | config JFS_FS | |
117 | tristate "JFS filesystem support" | |
118 | select NLS | |
119 | help | |
120 | This is a port of IBM's Journaled Filesystem . More information is | |
121 | available in the file <file:Documentation/filesystems/jfs.txt>. | |
122 | ||
123 | If you do not intend to use the JFS filesystem, say N. | |
124 | ||
125 | config JFS_POSIX_ACL | |
126 | bool "JFS POSIX Access Control Lists" | |
127 | depends on JFS_FS | |
b84c2157 | 128 | select FS_POSIX_ACL |
1da177e4 LT |
129 | help |
130 | Posix Access Control Lists (ACLs) support permissions for users and | |
131 | groups beyond the owner/group/world scheme. | |
132 | ||
133 | To learn more about Access Control Lists, visit the Posix ACLs for | |
134 | Linux website <http://acl.bestbits.at/>. | |
135 | ||
136 | If you don't know what Access Control Lists are, say N | |
137 | ||
138 | config JFS_SECURITY | |
139 | bool "JFS Security Labels" | |
140 | depends on JFS_FS | |
141 | help | |
142 | Security labels support alternative access control models | |
143 | implemented by security modules like SELinux. This option | |
144 | enables an extended attribute handler for file security | |
145 | labels in the jfs filesystem. | |
146 | ||
147 | If you are not using a security module that requires using | |
148 | extended attributes for file security labels, say N. | |
149 | ||
150 | config JFS_DEBUG | |
151 | bool "JFS debugging" | |
152 | depends on JFS_FS | |
153 | help | |
154 | If you are experiencing any problems with the JFS filesystem, say | |
155 | Y here. This will result in additional debugging messages to be | |
156 | written to the system log. Under normal circumstances, this | |
157 | results in very little overhead. | |
158 | ||
159 | config JFS_STATISTICS | |
160 | bool "JFS statistics" | |
161 | depends on JFS_FS | |
162 | help | |
163 | Enabling this option will cause statistics from the JFS file system | |
164 | to be made available to the user in the /proc/fs/jfs/ directory. | |
165 | ||
166 | config FS_POSIX_ACL | |
89206955 | 167 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4) |
1da177e4 LT |
168 | # |
169 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). | |
170 | # Never use this symbol for ifdefs. | |
171 | # | |
172 | bool | |
b84c2157 | 173 | default n |
1da177e4 | 174 | |
bfcd17a6 TP |
175 | config FILE_LOCKING |
176 | bool "Enable POSIX file locking API" if EMBEDDED | |
177 | default y | |
178 | help | |
179 | This option enables standard file locking support, required | |
180 | for filesystems like NFS and for the flock() system | |
181 | call. Disabling this option saves about 11k. | |
182 | ||
1da177e4 | 183 | source "fs/xfs/Kconfig" |
f7825dcf | 184 | source "fs/gfs2/Kconfig" |
1da177e4 | 185 | |
b4e40a51 | 186 | config OCFS2_FS |
02ed8416 MF |
187 | tristate "OCFS2 file system support" |
188 | depends on NET && SYSFS | |
b4e40a51 | 189 | select CONFIGFS_FS |
2b4e30fb | 190 | select JBD2 |
b4e40a51 | 191 | select CRC32 |
1a224ad1 JK |
192 | select QUOTA |
193 | select QUOTA_TREE | |
b4e40a51 MF |
194 | help |
195 | OCFS2 is a general purpose extent based shared disk cluster file | |
196 | system with many similarities to ext3. It supports 64 bit inode | |
197 | numbers, and has automatically extending metadata groups which may | |
198 | also make it attractive for non-clustered use. | |
199 | ||
200 | You'll want to install the ocfs2-tools package in order to at least | |
201 | get "mount.ocfs2". | |
202 | ||
203 | Project web page: http://oss.oracle.com/projects/ocfs2 | |
204 | Tools web page: http://oss.oracle.com/projects/ocfs2-tools | |
205 | OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ | |
206 | ||
1252c434 MF |
207 | For more information on OCFS2, see the file |
208 | <file:Documentation/filesystems/ocfs2.txt>. | |
b4e40a51 | 209 | |
9341d229 JB |
210 | config OCFS2_FS_O2CB |
211 | tristate "O2CB Kernelspace Clustering" | |
212 | depends on OCFS2_FS | |
213 | default y | |
214 | help | |
215 | OCFS2 includes a simple kernelspace clustering package, the OCFS2 | |
216 | Cluster Base. It only requires a very small userspace component | |
217 | to configure it. This comes with the standard ocfs2-tools package. | |
218 | O2CB is limited to maintaining a cluster for OCFS2 file systems. | |
219 | It cannot manage any other cluster applications. | |
220 | ||
221 | It is always safe to say Y here, as the clustering method is | |
222 | run-time selectable. | |
223 | ||
224 | config OCFS2_FS_USERSPACE_CLUSTER | |
225 | tristate "OCFS2 Userspace Clustering" | |
226 | depends on OCFS2_FS && DLM | |
227 | default y | |
228 | help | |
229 | This option will allow OCFS2 to use userspace clustering services | |
230 | in conjunction with the DLM in fs/dlm. If you are using a | |
231 | userspace cluster manager, say Y here. | |
232 | ||
233 | It is safe to say Y, as the clustering method is run-time | |
234 | selectable. | |
235 | ||
ce7231e9 SM |
236 | config OCFS2_FS_STATS |
237 | bool "OCFS2 statistics" | |
238 | depends on OCFS2_FS | |
239 | default y | |
240 | help | |
241 | This option allows some fs statistics to be captured. Enabling | |
242 | this option may increase the memory consumption. | |
243 | ||
2b388c67 JB |
244 | config OCFS2_DEBUG_MASKLOG |
245 | bool "OCFS2 logging support" | |
246 | depends on OCFS2_FS | |
247 | default y | |
248 | help | |
249 | The ocfs2 filesystem has an extensive logging system. The system | |
250 | allows selection of events to log via files in /sys/o2cb/logmask/. | |
251 | This option will enlarge your kernel, but it allows debugging of | |
252 | ocfs2 filesystem issues. | |
253 | ||
5a58c3ef JK |
254 | config OCFS2_DEBUG_FS |
255 | bool "OCFS2 expensive checks" | |
256 | depends on OCFS2_FS | |
257 | default n | |
258 | help | |
259 | This option will enable expensive consistency checks. Enable | |
260 | this option for debugging only as it is likely to decrease | |
261 | performance of the filesystem. | |
2b4e30fb | 262 | |
a68979b8 TY |
263 | config OCFS2_FS_POSIX_ACL |
264 | bool "OCFS2 POSIX Access Control Lists" | |
265 | depends on OCFS2_FS | |
266 | select FS_POSIX_ACL | |
267 | default n | |
268 | help | |
269 | Posix Access Control Lists (ACLs) support permissions for users and | |
270 | groups beyond the owner/group/world scheme. | |
271 | ||
60582d1e CM |
272 | config BTRFS_FS |
273 | tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format" | |
274 | depends on EXPERIMENTAL | |
275 | select LIBCRC32C | |
c8b97818 CM |
276 | select ZLIB_INFLATE |
277 | select ZLIB_DEFLATE | |
60582d1e CM |
278 | help |
279 | Btrfs is a new filesystem with extents, writable snapshotting, | |
280 | support for multiple devices and many more features. | |
281 | ||
282 | Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET | |
283 | FINALIZED. You should say N here unless you are interested in | |
284 | testing Btrfs with non-critical data. | |
285 | ||
286 | To compile this file system support as a module, choose M here. The | |
287 | module will be called btrfs. | |
288 | ||
289 | If unsure, say N. | |
290 | ||
25fad945 | 291 | endif # BLOCK |
1da177e4 | 292 | |
272eb014 | 293 | source "fs/notify/Kconfig" |
0eeca283 | 294 | |
1da177e4 LT |
295 | config QUOTA |
296 | bool "Quota support" | |
297 | help | |
298 | If you say Y here, you will be able to set per user limits for disk | |
299 | usage (also called disk quotas). Currently, it works for the | |
300 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
301 | quotas for which you don't need to run quotacheck(8) after an unclean | |
919532a5 AB |
302 | shutdown. |
303 | For further details, read the Quota mini-HOWTO, available from | |
1da177e4 LT |
304 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
305 | with the quota tools. Probably the quota support is only useful for | |
306 | multi user systems. If unsure, say N. | |
307 | ||
8e893469 JK |
308 | config QUOTA_NETLINK_INTERFACE |
309 | bool "Report quota messages through netlink interface" | |
310 | depends on QUOTA && NET | |
311 | help | |
312 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
313 | hardlimit, etc.) will be reported through netlink interface. If unsure, | |
314 | say Y. | |
315 | ||
316 | config PRINT_QUOTA_WARNING | |
317 | bool "Print quota warnings to console (OBSOLETE)" | |
318 | depends on QUOTA | |
319 | default y | |
320 | help | |
321 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
322 | hardlimit, etc.) will be printed to the process' controlling terminal. | |
323 | Note that this behavior is currently deprecated and may go away in | |
324 | future. Please use notification via netlink socket instead. | |
325 | ||
1ccd14b9 JK |
326 | # Generic support for tree structured quota files. Seleted when needed. |
327 | config QUOTA_TREE | |
328 | tristate | |
329 | ||
1da177e4 LT |
330 | config QFMT_V1 |
331 | tristate "Old quota format support" | |
332 | depends on QUOTA | |
333 | help | |
334 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
335 | you have quota working and you don't want to convert to new quota | |
336 | format say Y here. | |
337 | ||
338 | config QFMT_V2 | |
339 | tristate "Quota format v2 support" | |
340 | depends on QUOTA | |
1ccd14b9 | 341 | select QUOTA_TREE |
1da177e4 LT |
342 | help |
343 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
919532a5 | 344 | need this functionality say Y here. |
1da177e4 LT |
345 | |
346 | config QUOTACTL | |
347 | bool | |
348 | depends on XFS_QUOTA || QUOTA | |
349 | default y | |
350 | ||
1da177e4 LT |
351 | config AUTOFS_FS |
352 | tristate "Kernel automounter support" | |
353 | help | |
354 | The automounter is a tool to automatically mount remote file systems | |
355 | on demand. This implementation is partially kernel-based to reduce | |
356 | overhead in the already-mounted case; this is unlike the BSD | |
357 | automounter (amd), which is a pure user space daemon. | |
358 | ||
359 | To use the automounter you need the user-space tools from the autofs | |
360 | package; you can find the location in <file:Documentation/Changes>. | |
361 | You also want to answer Y to "NFS file system support", below. | |
362 | ||
363 | If you want to use the newer version of the automounter with more | |
364 | features, say N here and say Y to "Kernel automounter v4 support", | |
365 | below. | |
366 | ||
367 | To compile this support as a module, choose M here: the module will be | |
368 | called autofs. | |
369 | ||
370 | If you are not a part of a fairly large, distributed network, you | |
371 | probably do not need an automounter, and can say N here. | |
372 | ||
373 | config AUTOFS4_FS | |
374 | tristate "Kernel automounter version 4 support (also supports v3)" | |
375 | help | |
376 | The automounter is a tool to automatically mount remote file systems | |
377 | on demand. This implementation is partially kernel-based to reduce | |
378 | overhead in the already-mounted case; this is unlike the BSD | |
379 | automounter (amd), which is a pure user space daemon. | |
380 | ||
381 | To use the automounter you need the user-space tools from | |
382 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also | |
383 | want to answer Y to "NFS file system support", below. | |
384 | ||
385 | To compile this support as a module, choose M here: the module will be | |
386 | called autofs4. You will need to add "alias autofs autofs4" to your | |
387 | modules configuration file. | |
388 | ||
389 | If you are not a part of a fairly large, distributed network or | |
390 | don't have a laptop which needs to dynamically reconfigure to the | |
391 | local network, you probably do not need an automounter, and can say | |
392 | N here. | |
393 | ||
04578f17 | 394 | config FUSE_FS |
37194d07 | 395 | tristate "FUSE (Filesystem in Userspace) support" |
04578f17 MS |
396 | help |
397 | With FUSE it is possible to implement a fully functional filesystem | |
398 | in a userspace program. | |
399 | ||
400 | There's also companion library: libfuse. This library along with | |
401 | utilities is available from the FUSE homepage: | |
402 | <http://fuse.sourceforge.net/> | |
403 | ||
909021ea MS |
404 | See <file:Documentation/filesystems/fuse.txt> for more information. |
405 | See <file:Documentation/Changes> for needed library/utility version. | |
406 | ||
04578f17 MS |
407 | If you want to develop a userspace FS, or if you want to use |
408 | a filesystem based on FUSE, answer Y or M. | |
409 | ||
f2fbc6c2 RD |
410 | config GENERIC_ACL |
411 | bool | |
412 | select FS_POSIX_ACL | |
413 | ||
9361401e | 414 | if BLOCK |
1da177e4 LT |
415 | menu "CD-ROM/DVD Filesystems" |
416 | ||
417 | config ISO9660_FS | |
418 | tristate "ISO 9660 CDROM file system support" | |
419 | help | |
420 | This is the standard file system used on CD-ROMs. It was previously | |
421 | known as "High Sierra File System" and is called "hsfs" on other | |
422 | Unix systems. The so-called Rock-Ridge extensions which allow for | |
423 | long Unix filenames and symbolic links are also supported by this | |
424 | driver. If you have a CD-ROM drive and want to do more with it than | |
425 | just listen to audio CDs and watch its LEDs, say Y (and read | |
426 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, | |
427 | available from <http://www.tldp.org/docs.html#howto>), thereby | |
428 | enlarging your kernel by about 27 KB; otherwise say N. | |
429 | ||
430 | To compile this file system support as a module, choose M here: the | |
431 | module will be called isofs. | |
432 | ||
433 | config JOLIET | |
434 | bool "Microsoft Joliet CDROM extensions" | |
435 | depends on ISO9660_FS | |
436 | select NLS | |
437 | help | |
438 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system | |
439 | which allows for long filenames in unicode format (unicode is the | |
440 | new 16 bit character code, successor to ASCII, which encodes the | |
441 | characters of almost all languages of the world; see | |
442 | <http://www.unicode.org/> for more information). Say Y here if you | |
443 | want to be able to read Joliet CD-ROMs under Linux. | |
444 | ||
445 | config ZISOFS | |
446 | bool "Transparent decompression extension" | |
447 | depends on ISO9660_FS | |
448 | select ZLIB_INFLATE | |
449 | help | |
450 | This is a Linux-specific extension to RockRidge which lets you store | |
451 | data in compressed form on a CD-ROM and have it transparently | |
452 | decompressed when the CD-ROM is accessed. See | |
453 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools | |
454 | necessary to create such a filesystem. Say Y here if you want to be | |
455 | able to read such compressed CD-ROMs. | |
456 | ||
1da177e4 LT |
457 | config UDF_FS |
458 | tristate "UDF file system support" | |
f845fced | 459 | select CRC_ITU_T |
1da177e4 LT |
460 | help |
461 | This is the new file system used on some CD-ROMs and DVDs. Say Y if | |
462 | you intend to mount DVD discs or CDRW's written in packet mode, or | |
463 | if written to by other UDF utilities, such as DirectCD. | |
464 | Please read <file:Documentation/filesystems/udf.txt>. | |
465 | ||
466 | To compile this file system support as a module, choose M here: the | |
467 | module will be called udf. | |
468 | ||
469 | If unsure, say N. | |
470 | ||
471 | config UDF_NLS | |
472 | bool | |
473 | default y | |
474 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) | |
475 | ||
476 | endmenu | |
25fad945 | 477 | endif # BLOCK |
1da177e4 | 478 | |
9361401e | 479 | if BLOCK |
1da177e4 LT |
480 | menu "DOS/FAT/NT Filesystems" |
481 | ||
482 | config FAT_FS | |
483 | tristate | |
484 | select NLS | |
485 | help | |
486 | If you want to use one of the FAT-based file systems (the MS-DOS and | |
487 | VFAT (Windows 95) file systems), then you must say Y or M here | |
488 | to include FAT support. You will then be able to mount partitions or | |
489 | diskettes with FAT-based file systems and transparently access the | |
490 | files on them, i.e. MSDOS files will look and behave just like all | |
491 | other Unix files. | |
492 | ||
493 | This FAT support is not a file system in itself, it only provides | |
494 | the foundation for the other file systems. You will have to say Y or | |
495 | M to at least one of "MSDOS fs support" or "VFAT fs support" in | |
496 | order to make use of it. | |
497 | ||
498 | Another way to read and write MSDOS floppies and hard drive | |
499 | partitions from within Linux (but not transparently) is with the | |
500 | mtools ("man mtools") program suite. You don't need to say Y here in | |
501 | order to do that. | |
502 | ||
503 | If you need to move large files on floppies between a DOS and a | |
504 | Linux box, say Y here, mount the floppy under Linux with an MSDOS | |
505 | file system and use GNU tar's M option. GNU tar is a program | |
506 | available for Unix and DOS ("man tar" or "info tar"). | |
507 | ||
1da177e4 LT |
508 | The FAT support will enlarge your kernel by about 37 KB. If unsure, |
509 | say Y. | |
510 | ||
511 | To compile this as a module, choose M here: the module will be called | |
512 | fat. Note that if you compile the FAT support as a module, you | |
513 | cannot compile any of the FAT-based file systems into the kernel | |
514 | -- they will have to be modules as well. | |
515 | ||
516 | config MSDOS_FS | |
517 | tristate "MSDOS fs support" | |
518 | select FAT_FS | |
519 | help | |
520 | This allows you to mount MSDOS partitions of your hard drive (unless | |
521 | they are compressed; to access compressed MSDOS partitions under | |
522 | Linux, you can either use the DOS emulator DOSEMU, described in the | |
523 | DOSEMU-HOWTO, available from | |
524 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in | |
525 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you | |
526 | intend to use dosemu with a non-compressed MSDOS partition, say Y | |
527 | here) and MSDOS floppies. This means that file access becomes | |
528 | transparent, i.e. the MSDOS files look and behave just like all | |
529 | other Unix files. | |
530 | ||
531 | If you have Windows 95 or Windows NT installed on your MSDOS | |
532 | partitions, you should use the VFAT file system (say Y to "VFAT fs | |
533 | support" below), or you will not be able to see the long filenames | |
534 | generated by Windows 95 / Windows NT. | |
535 | ||
536 | This option will enlarge your kernel by about 7 KB. If unsure, | |
537 | answer Y. This will only work if you said Y to "DOS FAT fs support" | |
538 | as well. To compile this as a module, choose M here: the module will | |
539 | be called msdos. | |
540 | ||
541 | config VFAT_FS | |
542 | tristate "VFAT (Windows-95) fs support" | |
543 | select FAT_FS | |
544 | help | |
545 | This option provides support for normal Windows file systems with | |
546 | long filenames. That includes non-compressed FAT-based file systems | |
547 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix | |
548 | programs from the mtools package. | |
549 | ||
550 | The VFAT support enlarges your kernel by about 10 KB and it only | |
551 | works if you said Y to the "DOS FAT fs support" above. Please read | |
552 | the file <file:Documentation/filesystems/vfat.txt> for details. If | |
553 | unsure, say Y. | |
554 | ||
555 | To compile this as a module, choose M here: the module will be called | |
556 | vfat. | |
557 | ||
558 | config FAT_DEFAULT_CODEPAGE | |
559 | int "Default codepage for FAT" | |
560 | depends on MSDOS_FS || VFAT_FS | |
561 | default 437 | |
562 | help | |
563 | This option should be set to the codepage of your FAT filesystems. | |
564 | It can be overridden with the "codepage" mount option. | |
565 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
566 | ||
567 | config FAT_DEFAULT_IOCHARSET | |
568 | string "Default iocharset for FAT" | |
569 | depends on VFAT_FS | |
570 | default "iso8859-1" | |
571 | help | |
572 | Set this to the default input/output character set you'd | |
573 | like FAT to use. It should probably match the character set | |
574 | that most of your FAT filesystems use, and can be overridden | |
575 | with the "iocharset" mount option for FAT filesystems. | |
576 | Note that "utf8" is not recommended for FAT filesystems. | |
577 | If unsure, you shouldn't set "utf8" here. | |
578 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
579 | ||
580 | config NTFS_FS | |
581 | tristate "NTFS file system support" | |
582 | select NLS | |
583 | help | |
584 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
585 | ||
586 | Saying Y or M here enables read support. There is partial, but | |
587 | safe, write support available. For write support you must also | |
588 | say Y to "NTFS write support" below. | |
589 | ||
590 | There are also a number of user-space tools available, called | |
591 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
592 | without NTFS support enabled in the kernel. | |
593 | ||
594 | This is a rewrite from scratch of Linux NTFS support and replaced | |
595 | the old NTFS code starting with Linux 2.5.11. A backport to | |
596 | the Linux 2.4 kernel series is separately available as a patch | |
597 | from the project web site. | |
598 | ||
599 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
337e2ab5 | 600 | and <http://www.linux-ntfs.org/>. |
1da177e4 LT |
601 | |
602 | To compile this file system support as a module, choose M here: the | |
603 | module will be called ntfs. | |
604 | ||
605 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
606 | Linux on your computer it is safe to say N. | |
607 | ||
608 | config NTFS_DEBUG | |
609 | bool "NTFS debugging support" | |
610 | depends on NTFS_FS | |
611 | help | |
612 | If you are experiencing any problems with the NTFS file system, say | |
613 | Y here. This will result in additional consistency checks to be | |
614 | performed by the driver as well as additional debugging messages to | |
615 | be written to the system log. Note that debugging messages are | |
616 | disabled by default. To enable them, supply the option debug_msgs=1 | |
617 | at the kernel command line when booting the kernel or as an option | |
618 | to insmod when loading the ntfs module. Once the driver is active, | |
619 | you can enable debugging messages by doing (as root): | |
620 | echo 1 > /proc/sys/fs/ntfs-debug | |
621 | Replacing the "1" with "0" would disable debug messages. | |
622 | ||
623 | If you leave debugging messages disabled, this results in little | |
624 | overhead, but enabling debug messages results in very significant | |
625 | slowdown of the system. | |
626 | ||
627 | When reporting bugs, please try to have available a full dump of | |
628 | debugging messages while the misbehaviour was occurring. | |
629 | ||
630 | config NTFS_RW | |
631 | bool "NTFS write support" | |
632 | depends on NTFS_FS | |
633 | help | |
634 | This enables the partial, but safe, write support in the NTFS driver. | |
635 | ||
636 | The only supported operation is overwriting existing files, without | |
637 | changing the file length. No file or directory creation, deletion or | |
638 | renaming is possible. Note only non-resident files can be written to | |
639 | so you may find that some very small files (<500 bytes or so) cannot | |
640 | be written to. | |
641 | ||
642 | While we cannot guarantee that it will not damage any data, we have | |
643 | so far not received a single report where the driver would have | |
644 | damaged someones data so we assume it is perfectly safe to use. | |
645 | ||
646 | Note: While write support is safe in this version (a rewrite from | |
647 | scratch of the NTFS support), it should be noted that the old NTFS | |
648 | write support, included in Linux 2.5.10 and before (since 1997), | |
649 | is not safe. | |
650 | ||
651 | This is currently useful with TopologiLinux. TopologiLinux is run | |
652 | on top of any DOS/Microsoft Windows system without partitioning your | |
653 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
654 | need its own partition. For more information see | |
655 | <http://topologi-linux.sourceforge.net/> | |
656 | ||
657 | It is perfectly safe to say N here. | |
658 | ||
659 | endmenu | |
25fad945 | 660 | endif # BLOCK |
1da177e4 LT |
661 | |
662 | menu "Pseudo filesystems" | |
663 | ||
6eedf8d3 | 664 | source "fs/proc/Kconfig" |
b89a8171 | 665 | |
1da177e4 LT |
666 | config SYSFS |
667 | bool "sysfs file system support" if EMBEDDED | |
668 | default y | |
669 | help | |
670 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
671 | export internal kernel objects, their attributes, and their | |
672 | relationships to one another. | |
673 | ||
674 | Users can use sysfs to ascertain useful information about the running | |
675 | kernel, such as the devices the kernel has discovered on each bus and | |
676 | which driver each is bound to. sysfs can also be used to tune devices | |
677 | and other kernel subsystems. | |
678 | ||
679 | Some system agents rely on the information in sysfs to operate. | |
680 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
03a67a46 | 681 | delegating policy decisions, like persistently naming devices. |
1da177e4 LT |
682 | |
683 | sysfs is currently used by the block subsystem to mount the root | |
684 | partition. If sysfs is disabled you must specify the boot device on | |
685 | the kernel boot command line via its major and minor numbers. For | |
686 | example, "root=03:01" for /dev/hda1. | |
687 | ||
688 | Designers of embedded systems may wish to say N here to conserve space. | |
689 | ||
1da177e4 LT |
690 | config TMPFS |
691 | bool "Virtual memory file system support (former shm fs)" | |
692 | help | |
693 | Tmpfs is a file system which keeps all files in virtual memory. | |
694 | ||
695 | Everything in tmpfs is temporary in the sense that no files will be | |
696 | created on your hard drive. The files live in memory and swap | |
697 | space. If you unmount a tmpfs instance, everything stored therein is | |
698 | lost. | |
699 | ||
700 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
701 | ||
39f0247d AG |
702 | config TMPFS_POSIX_ACL |
703 | bool "Tmpfs POSIX Access Control Lists" | |
704 | depends on TMPFS | |
705 | select GENERIC_ACL | |
706 | help | |
707 | POSIX Access Control Lists (ACLs) support permissions for users and | |
708 | groups beyond the owner/group/world scheme. | |
709 | ||
710 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
711 | Linux website <http://acl.bestbits.at/>. | |
712 | ||
713 | If you don't know what Access Control Lists are, say N. | |
714 | ||
1da177e4 LT |
715 | config HUGETLBFS |
716 | bool "HugeTLB file system support" | |
53492b1d GS |
717 | depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \ |
718 | (S390 && 64BIT) || BROKEN | |
dda27d1a AO |
719 | help |
720 | hugetlbfs is a filesystem backing for HugeTLB pages, based on | |
721 | ramfs. For architectures that support it, say Y here and read | |
722 | <file:Documentation/vm/hugetlbpage.txt> for details. | |
723 | ||
724 | If unsure, say N. | |
1da177e4 LT |
725 | |
726 | config HUGETLB_PAGE | |
727 | def_bool HUGETLBFS | |
728 | ||
7063fbf2 | 729 | config CONFIGFS_FS |
02ac0499 JB |
730 | tristate "Userspace-driven configuration filesystem" |
731 | depends on SYSFS | |
7063fbf2 JB |
732 | help |
733 | configfs is a ram-based filesystem that provides the converse | |
734 | of sysfs's functionality. Where sysfs is a filesystem-based | |
735 | view of kernel objects, configfs is a filesystem-based manager | |
736 | of kernel objects, or config_items. | |
737 | ||
738 | Both sysfs and configfs can and should exist together on the | |
739 | same system. One is not a replacement for the other. | |
740 | ||
1da177e4 LT |
741 | endmenu |
742 | ||
67ec7d3a RD |
743 | menuconfig MISC_FILESYSTEMS |
744 | bool "Miscellaneous filesystems" | |
745 | default y | |
746 | ---help--- | |
747 | Say Y here to get to see options for various miscellaneous | |
748 | filesystems, such as filesystems that came from other | |
749 | operating systems. | |
750 | ||
751 | This option alone does not add any kernel code. | |
752 | ||
753 | If you say N, all options in this submenu will be skipped and | |
754 | disabled; if unsure, say Y here. | |
755 | ||
756 | if MISC_FILESYSTEMS | |
1da177e4 LT |
757 | |
758 | config ADFS_FS | |
759 | tristate "ADFS file system support (EXPERIMENTAL)" | |
9361401e | 760 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
761 | help |
762 | The Acorn Disc Filing System is the standard file system of the | |
763 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
764 | systems and the Acorn Archimedes range of machines. If you say Y | |
765 | here, Linux will be able to read from ADFS partitions on hard drives | |
766 | and from ADFS-formatted floppy discs. If you also want to be able to | |
767 | write to those devices, say Y to "ADFS write support" below. | |
768 | ||
769 | The ADFS partition should be the first partition (i.e., | |
770 | /dev/[hs]d?1) on each of your drives. Please read the file | |
771 | <file:Documentation/filesystems/adfs.txt> for further details. | |
772 | ||
773 | To compile this code as a module, choose M here: the module will be | |
774 | called adfs. | |
775 | ||
776 | If unsure, say N. | |
777 | ||
778 | config ADFS_FS_RW | |
779 | bool "ADFS write support (DANGEROUS)" | |
780 | depends on ADFS_FS | |
781 | help | |
782 | If you say Y here, you will be able to write to ADFS partitions on | |
783 | hard drives and ADFS-formatted floppy disks. This is experimental | |
784 | codes, so if you're unsure, say N. | |
785 | ||
786 | config AFFS_FS | |
787 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
9361401e | 788 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
789 | help |
790 | The Fast File System (FFS) is the common file system used on hard | |
791 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
792 | if you want to be able to read and write files from and to an Amiga | |
793 | FFS partition on your hard drive. Amiga floppies however cannot be | |
794 | read with this driver due to an incompatibility of the floppy | |
795 | controller used in an Amiga and the standard floppy controller in | |
796 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
797 | and <file:fs/affs/Changes>. | |
798 | ||
799 | With this driver you can also mount disk files used by Bernd | |
800 | Schmidt's Un*X Amiga Emulator | |
801 | (<http://www.freiburg.linux.de/~uae/>). | |
802 | If you want to do this, you will also need to say Y or M to "Loop | |
803 | device support", above. | |
804 | ||
805 | To compile this file system support as a module, choose M here: the | |
806 | module will be called affs. If unsure, say N. | |
807 | ||
237fead6 MH |
808 | config ECRYPT_FS |
809 | tristate "eCrypt filesystem layer support (EXPERIMENTAL)" | |
88b4a07e | 810 | depends on EXPERIMENTAL && KEYS && CRYPTO && NET |
237fead6 MH |
811 | help |
812 | Encrypted filesystem that operates on the VFS layer. See | |
e403149c | 813 | <file:Documentation/filesystems/ecryptfs.txt> to learn more about |
237fead6 MH |
814 | eCryptfs. Userspace components are required and can be |
815 | obtained from <http://ecryptfs.sf.net>. | |
816 | ||
817 | To compile this file system support as a module, choose M here: the | |
818 | module will be called ecryptfs. | |
819 | ||
1da177e4 LT |
820 | config HFS_FS |
821 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
9361401e | 822 | depends on BLOCK && EXPERIMENTAL |
878129a3 | 823 | select NLS |
1da177e4 LT |
824 | help |
825 | If you say Y here, you will be able to mount Macintosh-formatted | |
826 | floppy disks and hard drive partitions with full read-write access. | |
889c94a1 JFS |
827 | Please read <file:Documentation/filesystems/hfs.txt> to learn about |
828 | the available mount options. | |
1da177e4 LT |
829 | |
830 | To compile this file system support as a module, choose M here: the | |
831 | module will be called hfs. | |
832 | ||
833 | config HFSPLUS_FS | |
834 | tristate "Apple Extended HFS file system support" | |
9361401e | 835 | depends on BLOCK |
1da177e4 LT |
836 | select NLS |
837 | select NLS_UTF8 | |
838 | help | |
839 | If you say Y here, you will be able to mount extended format | |
840 | Macintosh-formatted hard drive partitions with full read-write access. | |
841 | ||
842 | This file system is often called HFS+ and was introduced with | |
843 | MacOS 8. It includes all Mac specific filesystem data such as | |
844 | data forks and creator codes, but it also has several UNIX | |
845 | style features such as file ownership and permissions. | |
846 | ||
847 | config BEFS_FS | |
848 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
9361401e | 849 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
850 | select NLS |
851 | help | |
852 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
853 | BeOS. Notable features include support for arbitrary attributes | |
3cb2fccc | 854 | on files and directories, and database-like indices on selected |
1da177e4 LT |
855 | attributes. (Also note that this driver doesn't make those features |
856 | available at this time). It is a 64 bit filesystem, so it supports | |
44c09201 | 857 | extremely large volumes and files. |
1da177e4 LT |
858 | |
859 | If you use this filesystem, you should also say Y to at least one | |
860 | of the NLS (native language support) options below. | |
861 | ||
862 | If you don't know what this is about, say N. | |
863 | ||
864 | To compile this as a module, choose M here: the module will be | |
865 | called befs. | |
866 | ||
867 | config BEFS_DEBUG | |
868 | bool "Debug BeFS" | |
869 | depends on BEFS_FS | |
870 | help | |
871 | If you say Y here, you can use the 'debug' mount option to enable | |
c7736339 | 872 | debugging output from the driver. |
1da177e4 LT |
873 | |
874 | config BFS_FS | |
875 | tristate "BFS file system support (EXPERIMENTAL)" | |
9361401e | 876 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
877 | help |
878 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
879 | allow the bootloader access to the kernel image and other important | |
880 | files during the boot process. It is usually mounted under /stand | |
881 | and corresponds to the slice marked as "STAND" in the UnixWare | |
882 | partition. You should say Y if you want to read or write the files | |
883 | on your /stand slice from within Linux. You then also need to say Y | |
884 | to "UnixWare slices support", below. More information about the BFS | |
885 | file system is contained in the file | |
886 | <file:Documentation/filesystems/bfs.txt>. | |
887 | ||
888 | If you don't know what this is about, say N. | |
889 | ||
890 | To compile this as a module, choose M here: the module will be called | |
891 | bfs. Note that the file system of your root partition (the one | |
892 | containing the directory /) cannot be compiled as a module. | |
893 | ||
894 | ||
895 | ||
896 | config EFS_FS | |
897 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
9361401e | 898 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
899 | help |
900 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
901 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
902 | uses the XFS file system for hard disk partitions however). | |
903 | ||
904 | This implementation only offers read-only access. If you don't know | |
905 | what all this is about, it's safe to say N. For more information | |
906 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
907 | ||
908 | To compile the EFS file system support as a module, choose M here: the | |
909 | module will be called efs. | |
910 | ||
31db6e9e | 911 | source "fs/jffs2/Kconfig" |
0d7eff87 AB |
912 | # UBIFS File system configuration |
913 | source "fs/ubifs/Kconfig" | |
914 | ||
1da177e4 LT |
915 | config CRAMFS |
916 | tristate "Compressed ROM file system support (cramfs)" | |
9361401e | 917 | depends on BLOCK |
1da177e4 LT |
918 | select ZLIB_INFLATE |
919 | help | |
920 | Saying Y here includes support for CramFs (Compressed ROM File | |
921 | System). CramFs is designed to be a simple, small, and compressed | |
922 | file system for ROM based embedded systems. CramFs is read-only, | |
923 | limited to 256MB file systems (with 16MB files), and doesn't support | |
924 | 16/32 bits uid/gid, hard links and timestamps. | |
925 | ||
926 | See <file:Documentation/filesystems/cramfs.txt> and | |
927 | <file:fs/cramfs/README> for further information. | |
928 | ||
929 | To compile this as a module, choose M here: the module will be called | |
930 | cramfs. Note that the root file system (the one containing the | |
931 | directory /) cannot be compiled as a module. | |
932 | ||
933 | If unsure, say N. | |
934 | ||
6ab5c1ca PL |
935 | config SQUASHFS |
936 | tristate "SquashFS 4.0 - Squashed file system support" | |
937 | depends on BLOCK | |
938 | select ZLIB_INFLATE | |
939 | help | |
940 | Saying Y here includes support for SquashFS 4.0 (a Compressed | |
941 | Read-Only File System). Squashfs is a highly compressed read-only | |
942 | filesystem for Linux. It uses zlib compression to compress both | |
943 | files, inodes and directories. Inodes in the system are very small | |
944 | and all blocks are packed to minimise data overhead. Block sizes | |
945 | greater than 4K are supported up to a maximum of 1 Mbytes (default | |
946 | block size 128K). SquashFS 4.0 supports 64 bit filesystems and files | |
947 | (larger than 4GB), full uid/gid information, hard links and | |
948 | timestamps. | |
949 | ||
950 | Squashfs is intended for general read-only filesystem use, for | |
951 | archival use (i.e. in cases where a .tar.gz file may be used), and in | |
952 | embedded systems where low overhead is needed. Further information | |
953 | and tools are available from http://squashfs.sourceforge.net. | |
954 | ||
955 | If you want to compile this as a module ( = code which can be | |
956 | inserted in and removed from the running kernel whenever you want), | |
957 | say M here and read <file:Documentation/modules.txt>. The module | |
958 | will be called squashfs. Note that the root file system (the one | |
959 | containing the directory /) cannot be compiled as a module. | |
960 | ||
961 | If unsure, say N. | |
962 | ||
963 | config SQUASHFS_EMBEDDED | |
964 | ||
965 | bool "Additional option for memory-constrained systems" | |
966 | depends on SQUASHFS | |
967 | default n | |
968 | help | |
969 | Saying Y here allows you to specify cache size. | |
970 | ||
971 | If unsure, say N. | |
972 | ||
973 | config SQUASHFS_FRAGMENT_CACHE_SIZE | |
974 | int "Number of fragments cached" if SQUASHFS_EMBEDDED | |
975 | depends on SQUASHFS | |
976 | default "3" | |
977 | help | |
978 | By default SquashFS caches the last 3 fragments read from | |
979 | the filesystem. Increasing this amount may mean SquashFS | |
980 | has to re-read fragments less often from disk, at the expense | |
981 | of extra system memory. Decreasing this amount will mean | |
982 | SquashFS uses less memory at the expense of extra reads from disk. | |
983 | ||
984 | Note there must be at least one cached fragment. Anything | |
985 | much more than three will probably not make much difference. | |
986 | ||
1da177e4 LT |
987 | config VXFS_FS |
988 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
9361401e | 989 | depends on BLOCK |
1da177e4 LT |
990 | help |
991 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
992 | file system format. VERITAS VxFS(TM) is the standard file system | |
993 | of SCO UnixWare (and possibly others) and optionally available | |
994 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
995 | Currently only readonly access is supported. | |
996 | ||
997 | NOTE: the file system type as used by mount(1), mount(2) and | |
998 | fstab(5) is 'vxfs' as it describes the file system format, not | |
999 | the actual driver. | |
1000 | ||
1001 | To compile this as a module, choose M here: the module will be | |
1002 | called freevxfs. If unsure, say N. | |
1003 | ||
25fad945 RD |
1004 | config MINIX_FS |
1005 | tristate "Minix file system support" | |
1006 | depends on BLOCK | |
1007 | help | |
1008 | Minix is a simple operating system used in many classes about OS's. | |
1009 | The minix file system (method to organize files on a hard disk | |
1010 | partition or a floppy disk) was the original file system for Linux, | |
1011 | but has been superseded by the second extended file system ext2fs. | |
1012 | You don't want to use the minix file system on your hard disk | |
1013 | because of certain built-in restrictions, but it is sometimes found | |
1014 | on older Linux floppy disks. This option will enlarge your kernel | |
1015 | by about 28 KB. If unsure, say N. | |
1016 | ||
1017 | To compile this file system support as a module, choose M here: the | |
1018 | module will be called minix. Note that the file system of your root | |
1019 | partition (the one containing the directory /) cannot be compiled as | |
1020 | a module. | |
1021 | ||
63ca8ce2 BC |
1022 | config OMFS_FS |
1023 | tristate "SonicBlue Optimized MPEG File System support" | |
1024 | depends on BLOCK | |
1025 | select CRC_ITU_T | |
1026 | help | |
1027 | This is the proprietary file system used by the Rio Karma music | |
1028 | player and ReplayTV DVR. Despite the name, this filesystem is not | |
1029 | more efficient than a standard FS for MPEG files, in fact likely | |
1030 | the opposite is true. Say Y if you have either of these devices | |
1031 | and wish to mount its disk. | |
1032 | ||
1033 | To compile this file system support as a module, choose M here: the | |
1034 | module will be called omfs. If unsure, say N. | |
1da177e4 LT |
1035 | |
1036 | config HPFS_FS | |
1037 | tristate "OS/2 HPFS file system support" | |
9361401e | 1038 | depends on BLOCK |
1da177e4 LT |
1039 | help |
1040 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
1041 | is the file system used for organizing files on OS/2 hard disk | |
1042 | partitions. Say Y if you want to be able to read files from and | |
1043 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
1044 | floppies however are in regular MSDOS format, so you don't need this | |
1045 | option in order to be able to read them. Read | |
1046 | <file:Documentation/filesystems/hpfs.txt>. | |
1047 | ||
1048 | To compile this file system support as a module, choose M here: the | |
1049 | module will be called hpfs. If unsure, say N. | |
1050 | ||
1051 | ||
1da177e4 LT |
1052 | config QNX4FS_FS |
1053 | tristate "QNX4 file system support (read only)" | |
9361401e | 1054 | depends on BLOCK |
1da177e4 LT |
1055 | help |
1056 | This is the file system used by the real-time operating systems | |
1057 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
1058 | Further information is available at <http://www.qnx.com/>. | |
1059 | Say Y if you intend to mount QNX hard disks or floppies. | |
1060 | Unless you say Y to "QNX4FS read-write support" below, you will | |
1061 | only be able to read these file systems. | |
1062 | ||
1063 | To compile this file system support as a module, choose M here: the | |
1064 | module will be called qnx4. | |
1065 | ||
1066 | If you don't know whether you need it, then you don't need it: | |
1067 | answer N. | |
1068 | ||
1069 | config QNX4FS_RW | |
1070 | bool "QNX4FS write support (DANGEROUS)" | |
1071 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
1072 | help | |
1073 | Say Y if you want to test write support for QNX4 file systems. | |
1074 | ||
1075 | It's currently broken, so for now: | |
1076 | answer N. | |
1077 | ||
25fad945 RD |
1078 | config ROMFS_FS |
1079 | tristate "ROM file system support" | |
1080 | depends on BLOCK | |
1081 | ---help--- | |
1082 | This is a very small read-only file system mainly intended for | |
1083 | initial ram disks of installation disks, but it could be used for | |
1084 | other read-only media as well. Read | |
1085 | <file:Documentation/filesystems/romfs.txt> for details. | |
1086 | ||
1087 | To compile this file system support as a module, choose M here: the | |
1088 | module will be called romfs. Note that the file system of your | |
1089 | root partition (the one containing the directory /) cannot be a | |
1090 | module. | |
1091 | ||
1092 | If you don't know whether you need it, then you don't need it: | |
1093 | answer N. | |
1da177e4 LT |
1094 | |
1095 | ||
1096 | config SYSV_FS | |
1097 | tristate "System V/Xenix/V7/Coherent file system support" | |
9361401e | 1098 | depends on BLOCK |
1da177e4 LT |
1099 | help |
1100 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
1101 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
1102 | here would allow you to read from their floppies and hard disk | |
1103 | partitions. | |
1104 | ||
1105 | If you have floppies or hard disk partitions like that, it is likely | |
1106 | that they contain binaries from those other Unix systems; in order | |
cab00891 | 1107 | to run these binaries, you will want to install linux-abi which is |
1da177e4 LT |
1108 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
1109 | UnixWare, Dell Unix and System V programs under Linux. It is | |
1110 | available via FTP (user: ftp) from | |
1111 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
1112 | NOTE: that will work only for binaries from Intel-based systems; | |
1113 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
1114 | ||
1115 | If you only intend to mount files from some other Unix over the | |
1116 | network using NFS, you don't need the System V file system support | |
1117 | (but you need NFS file system support obviously). | |
1118 | ||
1119 | Note that this option is generally not needed for floppies, since a | |
1120 | good portable way to transport files and directories between unixes | |
1121 | (and even other operating systems) is given by the tar program ("man | |
1122 | tar" or preferably "info tar"). Note also that this option has | |
1123 | nothing whatsoever to do with the option "System V IPC". Read about | |
1124 | the System V file system in | |
1125 | <file:Documentation/filesystems/sysv-fs.txt>. | |
1126 | Saying Y here will enlarge your kernel by about 27 KB. | |
1127 | ||
1128 | To compile this as a module, choose M here: the module will be called | |
1129 | sysv. | |
1130 | ||
1131 | If you haven't heard about all of this before, it's safe to say N. | |
1132 | ||
1133 | ||
1da177e4 LT |
1134 | config UFS_FS |
1135 | tristate "UFS file system support (read only)" | |
9361401e | 1136 | depends on BLOCK |
1da177e4 LT |
1137 | help |
1138 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
1139 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
1140 | Unixes can create and mount hard disk partitions and diskettes using | |
1141 | this file system as well. Saying Y here will allow you to read from | |
1142 | these partitions; if you also want to write to them, say Y to the | |
1143 | experimental "UFS file system write support", below. Please read the | |
1144 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
1145 | ||
1146 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
1147 | READ-ONLY supported. | |
1148 | ||
1da177e4 LT |
1149 | Note that this option is generally not needed for floppies, since a |
1150 | good portable way to transport files and directories between unixes | |
1151 | (and even other operating systems) is given by the tar program ("man | |
1152 | tar" or preferably "info tar"). | |
1153 | ||
1154 | When accessing NeXTstep files, you may need to convert them from the | |
1155 | NeXT character set to the Latin1 character set; use the program | |
1156 | recode ("info recode") for this purpose. | |
1157 | ||
1158 | To compile the UFS file system support as a module, choose M here: the | |
1159 | module will be called ufs. | |
1160 | ||
1161 | If you haven't heard about all of this before, it's safe to say N. | |
1162 | ||
1163 | config UFS_FS_WRITE | |
1164 | bool "UFS file system write support (DANGEROUS)" | |
5afb3145 | 1165 | depends on UFS_FS && EXPERIMENTAL |
1da177e4 LT |
1166 | help |
1167 | Say Y here if you want to try writing to UFS partitions. This is | |
1168 | experimental, so you should back up your UFS partitions beforehand. | |
1169 | ||
abf5d15f ED |
1170 | config UFS_DEBUG |
1171 | bool "UFS debugging" | |
1172 | depends on UFS_FS | |
1173 | help | |
1174 | If you are experiencing any problems with the UFS filesystem, say | |
1175 | Y here. This will result in _many_ additional debugging messages to be | |
1176 | written to the system log. | |
1177 | ||
67ec7d3a | 1178 | endif # MISC_FILESYSTEMS |
1da177e4 | 1179 | |
ea0985ad JE |
1180 | menuconfig NETWORK_FILESYSTEMS |
1181 | bool "Network File Systems" | |
1182 | default y | |
1da177e4 | 1183 | depends on NET |
ea0985ad JE |
1184 | ---help--- |
1185 | Say Y here to get to see options for network filesystems and | |
1186 | filesystem-related networking code, such as NFS daemon and | |
1187 | RPCSEC security modules. | |
6fb1bc10 | 1188 | |
ea0985ad JE |
1189 | This option alone does not add any kernel code. |
1190 | ||
1191 | If you say N, all options in this submenu will be skipped and | |
1192 | disabled; if unsure, say Y here. | |
1193 | ||
1194 | if NETWORK_FILESYSTEMS | |
1da177e4 LT |
1195 | |
1196 | config NFS_FS | |
6fb1bc10 | 1197 | tristate "NFS client support" |
1da177e4 LT |
1198 | depends on INET |
1199 | select LOCKD | |
1200 | select SUNRPC | |
b7fa0554 | 1201 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 | 1202 | help |
6fb1bc10 CL |
1203 | Choose Y here if you want to access files residing on other |
1204 | computers using Sun's Network File System protocol. To compile | |
1205 | this file system support as a module, choose M here: the module | |
1206 | will be called nfs. | |
1da177e4 | 1207 | |
6fb1bc10 CL |
1208 | To mount file systems exported by NFS servers, you also need to |
1209 | install the user space mount.nfs command which can be found in | |
1210 | the Linux nfs-utils package, available from http://linux-nfs.org/. | |
1211 | Information about using the mount command is available in the | |
1212 | mount(8) man page. More detail about the Linux NFS client | |
1213 | implementation is available via the nfs(5) man page. | |
1da177e4 | 1214 | |
6fb1bc10 CL |
1215 | Below you can choose which versions of the NFS protocol are |
1216 | available in the kernel to mount NFS servers. Support for NFS | |
1217 | version 2 (RFC 1094) is always available when NFS_FS is selected. | |
1da177e4 | 1218 | |
6fb1bc10 CL |
1219 | To configure a system which mounts its root file system via NFS |
1220 | at boot time, say Y here, select "Kernel level IP | |
1221 | autoconfiguration" in the NETWORK menu, and select "Root file | |
1222 | system on NFS" below. You cannot compile this file system as a | |
1223 | module in this case. | |
1da177e4 | 1224 | |
6fb1bc10 | 1225 | If unsure, say N. |
1da177e4 LT |
1226 | |
1227 | config NFS_V3 | |
6fb1bc10 | 1228 | bool "NFS client support for NFS version 3" |
1da177e4 LT |
1229 | depends on NFS_FS |
1230 | help | |
6fb1bc10 CL |
1231 | This option enables support for version 3 of the NFS protocol |
1232 | (RFC 1813) in the kernel's NFS client. | |
1da177e4 LT |
1233 | |
1234 | If unsure, say Y. | |
1235 | ||
b7fa0554 | 1236 | config NFS_V3_ACL |
6fb1bc10 | 1237 | bool "NFS client support for the NFSv3 ACL protocol extension" |
b7fa0554 AG |
1238 | depends on NFS_V3 |
1239 | help | |
6fb1bc10 CL |
1240 | Some NFS servers support an auxiliary NFSv3 ACL protocol that |
1241 | Sun added to Solaris but never became an official part of the | |
1242 | NFS version 3 protocol. This protocol extension allows | |
1243 | applications on NFS clients to manipulate POSIX Access Control | |
1244 | Lists on files residing on NFS servers. NFS servers enforce | |
1245 | ACLs on local files whether this protocol is available or not. | |
1246 | ||
1247 | Choose Y here if your NFS server supports the Solaris NFSv3 ACL | |
1248 | protocol extension and you want your NFS client to allow | |
1249 | applications to access and modify ACLs on files on the server. | |
1250 | ||
1251 | Most NFS servers don't support the Solaris NFSv3 ACL protocol | |
1252 | extension. You can choose N here or specify the "noacl" mount | |
1253 | option to prevent your NFS client from trying to use the NFSv3 | |
1254 | ACL protocol. | |
b7fa0554 AG |
1255 | |
1256 | If unsure, say N. | |
1257 | ||
1da177e4 | 1258 | config NFS_V4 |
6fb1bc10 | 1259 | bool "NFS client support for NFS version 4 (EXPERIMENTAL)" |
1da177e4 LT |
1260 | depends on NFS_FS && EXPERIMENTAL |
1261 | select RPCSEC_GSS_KRB5 | |
1262 | help | |
6fb1bc10 CL |
1263 | This option enables support for version 4 of the NFS protocol |
1264 | (RFC 3530) in the kernel's NFS client. | |
1da177e4 | 1265 | |
6fb1bc10 CL |
1266 | To mount NFS servers using NFSv4, you also need to install user |
1267 | space programs which can be found in the Linux nfs-utils package, | |
1268 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1269 | |
1270 | If unsure, say N. | |
1271 | ||
6fb1bc10 CL |
1272 | config ROOT_NFS |
1273 | bool "Root file system on NFS" | |
1274 | depends on NFS_FS=y && IP_PNP | |
1275 | help | |
1276 | If you want your system to mount its root file system via NFS, | |
1277 | choose Y here. This is common practice for managing systems | |
1278 | without local permanent storage. For details, read | |
1279 | <file:Documentation/filesystems/nfsroot.txt>. | |
1280 | ||
1281 | Most people say N here. | |
1282 | ||
1da177e4 LT |
1283 | config NFSD |
1284 | tristate "NFS server support" | |
1285 | depends on INET | |
1286 | select LOCKD | |
1287 | select SUNRPC | |
1288 | select EXPORTFS | |
f05e15b5 | 1289 | select NFS_ACL_SUPPORT if NFSD_V2_ACL |
1da177e4 | 1290 | help |
d24455b5 CL |
1291 | Choose Y here if you want to allow other computers to access |
1292 | files residing on this system using Sun's Network File System | |
1293 | protocol. To compile the NFS server support as a module, | |
1294 | choose M here: the module will be called nfsd. | |
1da177e4 | 1295 | |
d24455b5 CL |
1296 | You may choose to use a user-space NFS server instead, in which |
1297 | case you can choose N here. | |
1da177e4 | 1298 | |
d24455b5 CL |
1299 | To export local file systems using NFS, you also need to install |
1300 | user space programs which can be found in the Linux nfs-utils | |
1301 | package, available from http://linux-nfs.org/. More detail about | |
1302 | the Linux NFS server implementation is available via the | |
1303 | exports(5) man page. | |
1da177e4 | 1304 | |
d24455b5 CL |
1305 | Below you can choose which versions of the NFS protocol are |
1306 | available to clients mounting the NFS server on this system. | |
1307 | Support for NFS version 2 (RFC 1094) is always available when | |
1308 | CONFIG_NFSD is selected. | |
1da177e4 | 1309 | |
d24455b5 | 1310 | If unsure, say N. |
1da177e4 | 1311 | |
a257cdd0 AG |
1312 | config NFSD_V2_ACL |
1313 | bool | |
1314 | depends on NFSD | |
1315 | ||
1da177e4 | 1316 | config NFSD_V3 |
d24455b5 | 1317 | bool "NFS server support for NFS version 3" |
1da177e4 LT |
1318 | depends on NFSD |
1319 | help | |
d24455b5 CL |
1320 | This option enables support in your system's NFS server for |
1321 | version 3 of the NFS protocol (RFC 1813). | |
1322 | ||
1323 | If unsure, say Y. | |
1da177e4 | 1324 | |
a257cdd0 | 1325 | config NFSD_V3_ACL |
d24455b5 | 1326 | bool "NFS server support for the NFSv3 ACL protocol extension" |
a257cdd0 | 1327 | depends on NFSD_V3 |
78dd0992 | 1328 | select NFSD_V2_ACL |
a257cdd0 | 1329 | help |
d24455b5 CL |
1330 | Solaris NFS servers support an auxiliary NFSv3 ACL protocol that |
1331 | never became an official part of the NFS version 3 protocol. | |
1332 | This protocol extension allows applications on NFS clients to | |
1333 | manipulate POSIX Access Control Lists on files residing on NFS | |
1334 | servers. NFS servers enforce POSIX ACLs on local files whether | |
1335 | this protocol is available or not. | |
1336 | ||
1337 | This option enables support in your system's NFS server for the | |
1338 | NFSv3 ACL protocol extension allowing NFS clients to manipulate | |
1339 | POSIX ACLs on files exported by your system's NFS server. NFS | |
1340 | clients which support the Solaris NFSv3 ACL protocol can then | |
1341 | access and modify ACLs on your NFS server. | |
1342 | ||
1343 | To store ACLs on your NFS server, you also need to enable ACL- | |
1344 | related CONFIG options for your local file systems of choice. | |
1345 | ||
1346 | If unsure, say N. | |
a257cdd0 | 1347 | |
1da177e4 | 1348 | config NFSD_V4 |
d24455b5 | 1349 | bool "NFS server support for NFS version 4 (EXPERIMENTAL)" |
1a448fdb CL |
1350 | depends on NFSD && PROC_FS && EXPERIMENTAL |
1351 | select NFSD_V3 | |
89206955 | 1352 | select FS_POSIX_ACL |
42ed95c4 | 1353 | select RPCSEC_GSS_KRB5 |
1da177e4 | 1354 | help |
d24455b5 CL |
1355 | This option enables support in your system's NFS server for |
1356 | version 4 of the NFS protocol (RFC 3530). | |
1357 | ||
1358 | To export files using NFSv4, you need to install additional user | |
1359 | space programs which can be found in the Linux nfs-utils package, | |
1360 | available from http://linux-nfs.org/. | |
1361 | ||
1da177e4 LT |
1362 | If unsure, say N. |
1363 | ||
1da177e4 LT |
1364 | config LOCKD |
1365 | tristate | |
1366 | ||
1367 | config LOCKD_V4 | |
1368 | bool | |
1369 | depends on NFSD_V3 || NFS_V3 | |
1370 | default y | |
1371 | ||
1372 | config EXPORTFS | |
1373 | tristate | |
1374 | ||
a257cdd0 AG |
1375 | config NFS_ACL_SUPPORT |
1376 | tristate | |
1377 | select FS_POSIX_ACL | |
1378 | ||
1379 | config NFS_COMMON | |
1380 | bool | |
1381 | depends on NFSD || NFS_FS | |
1382 | default y | |
1383 | ||
1da177e4 LT |
1384 | config SUNRPC |
1385 | tristate | |
1386 | ||
1387 | config SUNRPC_GSS | |
1388 | tristate | |
1389 | ||
c3a57ed7 | 1390 | config SUNRPC_XPRT_RDMA |
3211e4eb | 1391 | tristate |
113632d0 | 1392 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL |
3211e4eb | 1393 | default SUNRPC && INFINIBAND |
327a299d CL |
1394 | help |
1395 | This option enables an RPC client transport capability that | |
1396 | allows the NFS client to mount servers via an RDMA-enabled | |
1397 | transport. | |
1398 | ||
1399 | To compile RPC client RDMA transport support as a module, | |
1400 | choose M here: the module will be called xprtrdma. | |
1401 | ||
1402 | If unsure, say N. | |
c3a57ed7 | 1403 | |
a26cfad6 CL |
1404 | config SUNRPC_REGISTER_V4 |
1405 | bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)" | |
1406 | depends on SUNRPC && EXPERIMENTAL | |
1407 | default n | |
1408 | help | |
1409 | Sun added support for registering RPC services at an IPv6 | |
1410 | address by creating two new versions of the rpcbind protocol | |
1411 | (RFC 1833). | |
1412 | ||
1413 | This option enables support in the kernel RPC server for | |
1414 | registering kernel RPC services via version 4 of the rpcbind | |
1415 | protocol. If you enable this option, you must run a portmapper | |
1416 | daemon that supports rpcbind protocol version 4. | |
1417 | ||
1418 | Serving NFS over IPv6 from knfsd (the kernel's NFS server) | |
1419 | requires that you enable this option and use a portmapper that | |
1420 | supports rpcbind version 4. | |
1421 | ||
1422 | If unsure, say N to get traditional behavior (register kernel | |
1423 | RPC services using only rpcbind version 2). Distributions | |
1424 | using the legacy Linux portmapper daemon must say N here. | |
1425 | ||
1da177e4 LT |
1426 | config RPCSEC_GSS_KRB5 |
1427 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
1428 | depends on SUNRPC && EXPERIMENTAL | |
1429 | select SUNRPC_GSS | |
1430 | select CRYPTO | |
1431 | select CRYPTO_MD5 | |
1432 | select CRYPTO_DES | |
bcbaecbb | 1433 | select CRYPTO_CBC |
1da177e4 | 1434 | help |
327a299d CL |
1435 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
1436 | GSS-API mechanism (RFC 1964). | |
1da177e4 | 1437 | |
327a299d CL |
1438 | Secure RPC calls with Kerberos require an auxiliary user-space |
1439 | daemon which may be found in the Linux nfs-utils package | |
1440 | available from http://linux-nfs.org/. In addition, user-space | |
1441 | Kerberos support should be installed. | |
1da177e4 LT |
1442 | |
1443 | If unsure, say N. | |
1444 | ||
1445 | config RPCSEC_GSS_SPKM3 | |
1446 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1447 | depends on SUNRPC && EXPERIMENTAL | |
1448 | select SUNRPC_GSS | |
1449 | select CRYPTO | |
1450 | select CRYPTO_MD5 | |
1451 | select CRYPTO_DES | |
df6db302 | 1452 | select CRYPTO_CAST5 |
bcbaecbb | 1453 | select CRYPTO_CBC |
1da177e4 | 1454 | help |
327a299d CL |
1455 | Choose Y here to enable Secure RPC using the SPKM3 public key |
1456 | GSS-API mechansim (RFC 2025). | |
1da177e4 | 1457 | |
327a299d CL |
1458 | Secure RPC calls with SPKM3 require an auxiliary userspace |
1459 | daemon which may be found in the Linux nfs-utils package | |
1460 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1461 | |
1462 | If unsure, say N. | |
1463 | ||
1464 | config SMB_FS | |
c7736339 | 1465 | tristate "SMB file system support (OBSOLETE, please use CIFS)" |
1da177e4 LT |
1466 | depends on INET |
1467 | select NLS | |
1468 | help | |
1469 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1470 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1471 | files and printers over local networks. Saying Y here allows you to | |
1472 | mount their file systems (often called "shares" in this context) and | |
1473 | access them just like any other Unix directory. Currently, this | |
1474 | works only if the Windows machines use TCP/IP as the underlying | |
1475 | transport protocol, and not NetBEUI. For details, read | |
1476 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1477 | available from <http://www.tldp.org/docs.html#howto>. | |
1478 | ||
1479 | Note: if you just want your box to act as an SMB *server* and make | |
1480 | files and printing services available to Windows clients (which need | |
1481 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1482 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1483 | for that. | |
1484 | ||
1485 | General information about how to connect Linux, Windows machines and | |
1486 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1487 | ||
c7736339 AM |
1488 | To compile the SMB support as a module, choose M here: |
1489 | the module will be called smbfs. Most people say N, however. | |
1da177e4 LT |
1490 | |
1491 | config SMB_NLS_DEFAULT | |
1492 | bool "Use a default NLS" | |
1493 | depends on SMB_FS | |
1494 | help | |
1495 | Enabling this will make smbfs use nls translations by default. You | |
1496 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1497 | settings and you need to give the default nls for the SMB server as | |
1498 | CONFIG_SMB_NLS_REMOTE. | |
1499 | ||
1500 | The nls settings can be changed at mount time, if your smbmount | |
1501 | supports that, using the codepage and iocharset parameters. | |
1502 | ||
1503 | smbmount from samba 2.2.0 or later supports this. | |
1504 | ||
1505 | config SMB_NLS_REMOTE | |
1506 | string "Default Remote NLS Option" | |
1507 | depends on SMB_NLS_DEFAULT | |
1508 | default "cp437" | |
1509 | help | |
1510 | This setting allows you to specify a default value for which | |
1511 | codepage the server uses. If this field is left blank no | |
1512 | translations will be done by default. The local codepage/charset | |
1513 | default to CONFIG_NLS_DEFAULT. | |
1514 | ||
1515 | The nls settings can be changed at mount time, if your smbmount | |
1516 | supports that, using the codepage and iocharset parameters. | |
1517 | ||
1518 | smbmount from samba 2.2.0 or later supports this. | |
1519 | ||
bb26b963 | 1520 | source "fs/cifs/Kconfig" |
6103335d | 1521 | |
1da177e4 LT |
1522 | config NCP_FS |
1523 | tristate "NCP file system support (to mount NetWare volumes)" | |
1524 | depends on IPX!=n || INET | |
1525 | help | |
1526 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1527 | used by Novell NetWare clients to talk to file servers. It is to | |
1528 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1529 | to mount NetWare file server volumes and to access them just like | |
1530 | any other Unix directory. For details, please read the file | |
1531 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1532 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1533 | ||
1534 | You do not have to say Y here if you want your Linux box to act as a | |
1535 | file *server* for Novell NetWare clients. | |
1536 | ||
1537 | General information about how to connect Linux, Windows machines and | |
1538 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1539 | ||
1540 | To compile this as a module, choose M here: the module will be called | |
1541 | ncpfs. Say N unless you are connected to a Novell network. | |
1542 | ||
1543 | source "fs/ncpfs/Kconfig" | |
1544 | ||
1545 | config CODA_FS | |
1546 | tristate "Coda file system support (advanced network fs)" | |
1547 | depends on INET | |
1548 | help | |
1549 | Coda is an advanced network file system, similar to NFS in that it | |
1550 | enables you to mount file systems of a remote server and access them | |
1551 | with regular Unix commands as if they were sitting on your hard | |
1552 | disk. Coda has several advantages over NFS: support for | |
1553 | disconnected operation (e.g. for laptops), read/write server | |
1554 | replication, security model for authentication and encryption, | |
1555 | persistent client caches and write back caching. | |
1556 | ||
1557 | If you say Y here, your Linux box will be able to act as a Coda | |
1558 | *client*. You will need user level code as well, both for the | |
1559 | client and server. Servers are currently user level, i.e. they need | |
1560 | no kernel support. Please read | |
1561 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1562 | home page <http://www.coda.cs.cmu.edu/>. | |
1563 | ||
1564 | To compile the coda client support as a module, choose M here: the | |
1565 | module will be called coda. | |
1566 | ||
1da177e4 | 1567 | config AFS_FS |
64aaa4f8 | 1568 | tristate "Andrew File System support (AFS) (EXPERIMENTAL)" |
1da177e4 | 1569 | depends on INET && EXPERIMENTAL |
08e0e7c8 | 1570 | select AF_RXRPC |
1da177e4 LT |
1571 | help |
1572 | If you say Y here, you will get an experimental Andrew File System | |
1573 | driver. It currently only supports unsecured read-only AFS access. | |
1574 | ||
cc2e2767 | 1575 | See <file:Documentation/filesystems/afs.txt> for more information. |
1da177e4 LT |
1576 | |
1577 | If unsure, say N. | |
1578 | ||
08e0e7c8 DH |
1579 | config AFS_DEBUG |
1580 | bool "AFS dynamic debugging" | |
1581 | depends on AFS_FS | |
1582 | help | |
1583 | Say Y here to make runtime controllable debugging messages appear. | |
1584 | ||
1585 | See <file:Documentation/filesystems/afs.txt> for more information. | |
1586 | ||
1587 | If unsure, say N. | |
1588 | ||
93fa58cb EVH |
1589 | config 9P_FS |
1590 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" | |
bd238fb4 | 1591 | depends on INET && NET_9P && EXPERIMENTAL |
93fa58cb EVH |
1592 | help |
1593 | If you say Y here, you will get experimental support for | |
1594 | Plan 9 resource sharing via the 9P2000 protocol. | |
1595 | ||
1596 | See <http://v9fs.sf.net> for more information. | |
1597 | ||
1598 | If unsure, say N. | |
1599 | ||
ea0985ad | 1600 | endif # NETWORK_FILESYSTEMS |
1da177e4 | 1601 | |
9361401e | 1602 | if BLOCK |
1da177e4 LT |
1603 | menu "Partition Types" |
1604 | ||
1605 | source "fs/partitions/Kconfig" | |
1606 | ||
1607 | endmenu | |
9361401e | 1608 | endif |
1da177e4 LT |
1609 | |
1610 | source "fs/nls/Kconfig" | |
e7fd4179 | 1611 | source "fs/dlm/Kconfig" |
1da177e4 LT |
1612 | |
1613 | endmenu |