]>
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 | 29 | |
b16ecfe2 | 30 | source "fs/reiserfs/Kconfig" |
f5c77969 | 31 | source "fs/jfs/Kconfig" |
1da177e4 LT |
32 | |
33 | config FS_POSIX_ACL | |
89206955 | 34 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4) |
1da177e4 LT |
35 | # |
36 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). | |
37 | # Never use this symbol for ifdefs. | |
38 | # | |
39 | bool | |
b84c2157 | 40 | default n |
1da177e4 | 41 | |
bfcd17a6 TP |
42 | config FILE_LOCKING |
43 | bool "Enable POSIX file locking API" if EMBEDDED | |
44 | default y | |
45 | help | |
46 | This option enables standard file locking support, required | |
47 | for filesystems like NFS and for the flock() system | |
48 | call. Disabling this option saves about 11k. | |
49 | ||
1da177e4 | 50 | source "fs/xfs/Kconfig" |
f7825dcf | 51 | source "fs/gfs2/Kconfig" |
2fe4371d | 52 | source "fs/ocfs2/Kconfig" |
335debee | 53 | source "fs/btrfs/Kconfig" |
60582d1e | 54 | |
25fad945 | 55 | endif # BLOCK |
1da177e4 | 56 | |
272eb014 | 57 | source "fs/notify/Kconfig" |
0eeca283 | 58 | |
1da177e4 LT |
59 | config QUOTA |
60 | bool "Quota support" | |
61 | help | |
62 | If you say Y here, you will be able to set per user limits for disk | |
63 | usage (also called disk quotas). Currently, it works for the | |
64 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
65 | quotas for which you don't need to run quotacheck(8) after an unclean | |
919532a5 AB |
66 | shutdown. |
67 | For further details, read the Quota mini-HOWTO, available from | |
1da177e4 LT |
68 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
69 | with the quota tools. Probably the quota support is only useful for | |
70 | multi user systems. If unsure, say N. | |
71 | ||
8e893469 JK |
72 | config QUOTA_NETLINK_INTERFACE |
73 | bool "Report quota messages through netlink interface" | |
74 | depends on QUOTA && NET | |
75 | help | |
76 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
77 | hardlimit, etc.) will be reported through netlink interface. If unsure, | |
78 | say Y. | |
79 | ||
80 | config PRINT_QUOTA_WARNING | |
81 | bool "Print quota warnings to console (OBSOLETE)" | |
82 | depends on QUOTA | |
83 | default y | |
84 | help | |
85 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
86 | hardlimit, etc.) will be printed to the process' controlling terminal. | |
87 | Note that this behavior is currently deprecated and may go away in | |
88 | future. Please use notification via netlink socket instead. | |
89 | ||
1ccd14b9 JK |
90 | # Generic support for tree structured quota files. Seleted when needed. |
91 | config QUOTA_TREE | |
92 | tristate | |
93 | ||
1da177e4 LT |
94 | config QFMT_V1 |
95 | tristate "Old quota format support" | |
96 | depends on QUOTA | |
97 | help | |
98 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
99 | you have quota working and you don't want to convert to new quota | |
100 | format say Y here. | |
101 | ||
102 | config QFMT_V2 | |
103 | tristate "Quota format v2 support" | |
104 | depends on QUOTA | |
1ccd14b9 | 105 | select QUOTA_TREE |
1da177e4 LT |
106 | help |
107 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
919532a5 | 108 | need this functionality say Y here. |
1da177e4 LT |
109 | |
110 | config QUOTACTL | |
111 | bool | |
112 | depends on XFS_QUOTA || QUOTA | |
113 | default y | |
114 | ||
90ffd467 AD |
115 | source "fs/autofs/Kconfig" |
116 | source "fs/autofs4/Kconfig" | |
3ef7784e | 117 | source "fs/fuse/Kconfig" |
04578f17 | 118 | |
f2fbc6c2 RD |
119 | config GENERIC_ACL |
120 | bool | |
121 | select FS_POSIX_ACL | |
122 | ||
9361401e | 123 | if BLOCK |
1da177e4 LT |
124 | menu "CD-ROM/DVD Filesystems" |
125 | ||
ddfaccd9 AD |
126 | source "fs/isofs/Kconfig" |
127 | source "fs/udf/Kconfig" | |
1da177e4 LT |
128 | |
129 | endmenu | |
25fad945 | 130 | endif # BLOCK |
1da177e4 | 131 | |
9361401e | 132 | if BLOCK |
1da177e4 LT |
133 | menu "DOS/FAT/NT Filesystems" |
134 | ||
1c6ace01 | 135 | source "fs/fat/Kconfig" |
1da177e4 LT |
136 | |
137 | config NTFS_FS | |
138 | tristate "NTFS file system support" | |
139 | select NLS | |
140 | help | |
141 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
142 | ||
143 | Saying Y or M here enables read support. There is partial, but | |
144 | safe, write support available. For write support you must also | |
145 | say Y to "NTFS write support" below. | |
146 | ||
147 | There are also a number of user-space tools available, called | |
148 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
149 | without NTFS support enabled in the kernel. | |
150 | ||
151 | This is a rewrite from scratch of Linux NTFS support and replaced | |
152 | the old NTFS code starting with Linux 2.5.11. A backport to | |
153 | the Linux 2.4 kernel series is separately available as a patch | |
154 | from the project web site. | |
155 | ||
156 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
337e2ab5 | 157 | and <http://www.linux-ntfs.org/>. |
1da177e4 LT |
158 | |
159 | To compile this file system support as a module, choose M here: the | |
160 | module will be called ntfs. | |
161 | ||
162 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
163 | Linux on your computer it is safe to say N. | |
164 | ||
165 | config NTFS_DEBUG | |
166 | bool "NTFS debugging support" | |
167 | depends on NTFS_FS | |
168 | help | |
169 | If you are experiencing any problems with the NTFS file system, say | |
170 | Y here. This will result in additional consistency checks to be | |
171 | performed by the driver as well as additional debugging messages to | |
172 | be written to the system log. Note that debugging messages are | |
173 | disabled by default. To enable them, supply the option debug_msgs=1 | |
174 | at the kernel command line when booting the kernel or as an option | |
175 | to insmod when loading the ntfs module. Once the driver is active, | |
176 | you can enable debugging messages by doing (as root): | |
177 | echo 1 > /proc/sys/fs/ntfs-debug | |
178 | Replacing the "1" with "0" would disable debug messages. | |
179 | ||
180 | If you leave debugging messages disabled, this results in little | |
181 | overhead, but enabling debug messages results in very significant | |
182 | slowdown of the system. | |
183 | ||
184 | When reporting bugs, please try to have available a full dump of | |
185 | debugging messages while the misbehaviour was occurring. | |
186 | ||
187 | config NTFS_RW | |
188 | bool "NTFS write support" | |
189 | depends on NTFS_FS | |
190 | help | |
191 | This enables the partial, but safe, write support in the NTFS driver. | |
192 | ||
193 | The only supported operation is overwriting existing files, without | |
194 | changing the file length. No file or directory creation, deletion or | |
195 | renaming is possible. Note only non-resident files can be written to | |
196 | so you may find that some very small files (<500 bytes or so) cannot | |
197 | be written to. | |
198 | ||
199 | While we cannot guarantee that it will not damage any data, we have | |
200 | so far not received a single report where the driver would have | |
201 | damaged someones data so we assume it is perfectly safe to use. | |
202 | ||
203 | Note: While write support is safe in this version (a rewrite from | |
204 | scratch of the NTFS support), it should be noted that the old NTFS | |
205 | write support, included in Linux 2.5.10 and before (since 1997), | |
206 | is not safe. | |
207 | ||
208 | This is currently useful with TopologiLinux. TopologiLinux is run | |
209 | on top of any DOS/Microsoft Windows system without partitioning your | |
210 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
211 | need its own partition. For more information see | |
212 | <http://topologi-linux.sourceforge.net/> | |
213 | ||
214 | It is perfectly safe to say N here. | |
215 | ||
216 | endmenu | |
25fad945 | 217 | endif # BLOCK |
1da177e4 LT |
218 | |
219 | menu "Pseudo filesystems" | |
220 | ||
6eedf8d3 | 221 | source "fs/proc/Kconfig" |
b89a8171 | 222 | |
1da177e4 LT |
223 | config SYSFS |
224 | bool "sysfs file system support" if EMBEDDED | |
225 | default y | |
226 | help | |
227 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
228 | export internal kernel objects, their attributes, and their | |
229 | relationships to one another. | |
230 | ||
231 | Users can use sysfs to ascertain useful information about the running | |
232 | kernel, such as the devices the kernel has discovered on each bus and | |
233 | which driver each is bound to. sysfs can also be used to tune devices | |
234 | and other kernel subsystems. | |
235 | ||
236 | Some system agents rely on the information in sysfs to operate. | |
237 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
03a67a46 | 238 | delegating policy decisions, like persistently naming devices. |
1da177e4 LT |
239 | |
240 | sysfs is currently used by the block subsystem to mount the root | |
241 | partition. If sysfs is disabled you must specify the boot device on | |
242 | the kernel boot command line via its major and minor numbers. For | |
243 | example, "root=03:01" for /dev/hda1. | |
244 | ||
245 | Designers of embedded systems may wish to say N here to conserve space. | |
246 | ||
1da177e4 LT |
247 | config TMPFS |
248 | bool "Virtual memory file system support (former shm fs)" | |
249 | help | |
250 | Tmpfs is a file system which keeps all files in virtual memory. | |
251 | ||
252 | Everything in tmpfs is temporary in the sense that no files will be | |
253 | created on your hard drive. The files live in memory and swap | |
254 | space. If you unmount a tmpfs instance, everything stored therein is | |
255 | lost. | |
256 | ||
257 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
258 | ||
39f0247d AG |
259 | config TMPFS_POSIX_ACL |
260 | bool "Tmpfs POSIX Access Control Lists" | |
261 | depends on TMPFS | |
262 | select GENERIC_ACL | |
263 | help | |
264 | POSIX Access Control Lists (ACLs) support permissions for users and | |
265 | groups beyond the owner/group/world scheme. | |
266 | ||
267 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
268 | Linux website <http://acl.bestbits.at/>. | |
269 | ||
270 | If you don't know what Access Control Lists are, say N. | |
271 | ||
1da177e4 LT |
272 | config HUGETLBFS |
273 | bool "HugeTLB file system support" | |
53492b1d GS |
274 | depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \ |
275 | (S390 && 64BIT) || BROKEN | |
dda27d1a AO |
276 | help |
277 | hugetlbfs is a filesystem backing for HugeTLB pages, based on | |
278 | ramfs. For architectures that support it, say Y here and read | |
279 | <file:Documentation/vm/hugetlbpage.txt> for details. | |
280 | ||
281 | If unsure, say N. | |
1da177e4 LT |
282 | |
283 | config HUGETLB_PAGE | |
284 | def_bool HUGETLBFS | |
285 | ||
7063fbf2 | 286 | config CONFIGFS_FS |
02ac0499 JB |
287 | tristate "Userspace-driven configuration filesystem" |
288 | depends on SYSFS | |
7063fbf2 JB |
289 | help |
290 | configfs is a ram-based filesystem that provides the converse | |
291 | of sysfs's functionality. Where sysfs is a filesystem-based | |
292 | view of kernel objects, configfs is a filesystem-based manager | |
293 | of kernel objects, or config_items. | |
294 | ||
295 | Both sysfs and configfs can and should exist together on the | |
296 | same system. One is not a replacement for the other. | |
297 | ||
1da177e4 LT |
298 | endmenu |
299 | ||
67ec7d3a RD |
300 | menuconfig MISC_FILESYSTEMS |
301 | bool "Miscellaneous filesystems" | |
302 | default y | |
303 | ---help--- | |
304 | Say Y here to get to see options for various miscellaneous | |
305 | filesystems, such as filesystems that came from other | |
306 | operating systems. | |
307 | ||
308 | This option alone does not add any kernel code. | |
309 | ||
310 | If you say N, all options in this submenu will be skipped and | |
311 | disabled; if unsure, say Y here. | |
312 | ||
313 | if MISC_FILESYSTEMS | |
1da177e4 LT |
314 | |
315 | config ADFS_FS | |
316 | tristate "ADFS file system support (EXPERIMENTAL)" | |
9361401e | 317 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
318 | help |
319 | The Acorn Disc Filing System is the standard file system of the | |
320 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
321 | systems and the Acorn Archimedes range of machines. If you say Y | |
322 | here, Linux will be able to read from ADFS partitions on hard drives | |
323 | and from ADFS-formatted floppy discs. If you also want to be able to | |
324 | write to those devices, say Y to "ADFS write support" below. | |
325 | ||
326 | The ADFS partition should be the first partition (i.e., | |
327 | /dev/[hs]d?1) on each of your drives. Please read the file | |
328 | <file:Documentation/filesystems/adfs.txt> for further details. | |
329 | ||
330 | To compile this code as a module, choose M here: the module will be | |
331 | called adfs. | |
332 | ||
333 | If unsure, say N. | |
334 | ||
335 | config ADFS_FS_RW | |
336 | bool "ADFS write support (DANGEROUS)" | |
337 | depends on ADFS_FS | |
338 | help | |
339 | If you say Y here, you will be able to write to ADFS partitions on | |
340 | hard drives and ADFS-formatted floppy disks. This is experimental | |
341 | codes, so if you're unsure, say N. | |
342 | ||
343 | config AFFS_FS | |
344 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
9361401e | 345 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
346 | help |
347 | The Fast File System (FFS) is the common file system used on hard | |
348 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
349 | if you want to be able to read and write files from and to an Amiga | |
350 | FFS partition on your hard drive. Amiga floppies however cannot be | |
351 | read with this driver due to an incompatibility of the floppy | |
352 | controller used in an Amiga and the standard floppy controller in | |
353 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
354 | and <file:fs/affs/Changes>. | |
355 | ||
356 | With this driver you can also mount disk files used by Bernd | |
357 | Schmidt's Un*X Amiga Emulator | |
358 | (<http://www.freiburg.linux.de/~uae/>). | |
359 | If you want to do this, you will also need to say Y or M to "Loop | |
360 | device support", above. | |
361 | ||
362 | To compile this file system support as a module, choose M here: the | |
363 | module will be called affs. If unsure, say N. | |
364 | ||
237fead6 MH |
365 | config ECRYPT_FS |
366 | tristate "eCrypt filesystem layer support (EXPERIMENTAL)" | |
88b4a07e | 367 | depends on EXPERIMENTAL && KEYS && CRYPTO && NET |
237fead6 MH |
368 | help |
369 | Encrypted filesystem that operates on the VFS layer. See | |
e403149c | 370 | <file:Documentation/filesystems/ecryptfs.txt> to learn more about |
237fead6 MH |
371 | eCryptfs. Userspace components are required and can be |
372 | obtained from <http://ecryptfs.sf.net>. | |
373 | ||
374 | To compile this file system support as a module, choose M here: the | |
375 | module will be called ecryptfs. | |
376 | ||
1da177e4 LT |
377 | config HFS_FS |
378 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
9361401e | 379 | depends on BLOCK && EXPERIMENTAL |
878129a3 | 380 | select NLS |
1da177e4 LT |
381 | help |
382 | If you say Y here, you will be able to mount Macintosh-formatted | |
383 | floppy disks and hard drive partitions with full read-write access. | |
889c94a1 JFS |
384 | Please read <file:Documentation/filesystems/hfs.txt> to learn about |
385 | the available mount options. | |
1da177e4 LT |
386 | |
387 | To compile this file system support as a module, choose M here: the | |
388 | module will be called hfs. | |
389 | ||
390 | config HFSPLUS_FS | |
391 | tristate "Apple Extended HFS file system support" | |
9361401e | 392 | depends on BLOCK |
1da177e4 LT |
393 | select NLS |
394 | select NLS_UTF8 | |
395 | help | |
396 | If you say Y here, you will be able to mount extended format | |
397 | Macintosh-formatted hard drive partitions with full read-write access. | |
398 | ||
399 | This file system is often called HFS+ and was introduced with | |
400 | MacOS 8. It includes all Mac specific filesystem data such as | |
401 | data forks and creator codes, but it also has several UNIX | |
402 | style features such as file ownership and permissions. | |
403 | ||
404 | config BEFS_FS | |
405 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
9361401e | 406 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
407 | select NLS |
408 | help | |
409 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
410 | BeOS. Notable features include support for arbitrary attributes | |
3cb2fccc | 411 | on files and directories, and database-like indices on selected |
1da177e4 LT |
412 | attributes. (Also note that this driver doesn't make those features |
413 | available at this time). It is a 64 bit filesystem, so it supports | |
44c09201 | 414 | extremely large volumes and files. |
1da177e4 LT |
415 | |
416 | If you use this filesystem, you should also say Y to at least one | |
417 | of the NLS (native language support) options below. | |
418 | ||
419 | If you don't know what this is about, say N. | |
420 | ||
421 | To compile this as a module, choose M here: the module will be | |
422 | called befs. | |
423 | ||
424 | config BEFS_DEBUG | |
425 | bool "Debug BeFS" | |
426 | depends on BEFS_FS | |
427 | help | |
428 | If you say Y here, you can use the 'debug' mount option to enable | |
c7736339 | 429 | debugging output from the driver. |
1da177e4 LT |
430 | |
431 | config BFS_FS | |
432 | tristate "BFS file system support (EXPERIMENTAL)" | |
9361401e | 433 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
434 | help |
435 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
436 | allow the bootloader access to the kernel image and other important | |
437 | files during the boot process. It is usually mounted under /stand | |
438 | and corresponds to the slice marked as "STAND" in the UnixWare | |
439 | partition. You should say Y if you want to read or write the files | |
440 | on your /stand slice from within Linux. You then also need to say Y | |
441 | to "UnixWare slices support", below. More information about the BFS | |
442 | file system is contained in the file | |
443 | <file:Documentation/filesystems/bfs.txt>. | |
444 | ||
445 | If you don't know what this is about, say N. | |
446 | ||
447 | To compile this as a module, choose M here: the module will be called | |
448 | bfs. Note that the file system of your root partition (the one | |
449 | containing the directory /) cannot be compiled as a module. | |
450 | ||
451 | ||
452 | ||
453 | config EFS_FS | |
454 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
9361401e | 455 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
456 | help |
457 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
458 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
459 | uses the XFS file system for hard disk partitions however). | |
460 | ||
461 | This implementation only offers read-only access. If you don't know | |
462 | what all this is about, it's safe to say N. For more information | |
463 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
464 | ||
465 | To compile the EFS file system support as a module, choose M here: the | |
466 | module will be called efs. | |
467 | ||
31db6e9e | 468 | source "fs/jffs2/Kconfig" |
0d7eff87 AB |
469 | # UBIFS File system configuration |
470 | source "fs/ubifs/Kconfig" | |
471 | ||
1da177e4 LT |
472 | config CRAMFS |
473 | tristate "Compressed ROM file system support (cramfs)" | |
9361401e | 474 | depends on BLOCK |
1da177e4 LT |
475 | select ZLIB_INFLATE |
476 | help | |
477 | Saying Y here includes support for CramFs (Compressed ROM File | |
478 | System). CramFs is designed to be a simple, small, and compressed | |
479 | file system for ROM based embedded systems. CramFs is read-only, | |
480 | limited to 256MB file systems (with 16MB files), and doesn't support | |
481 | 16/32 bits uid/gid, hard links and timestamps. | |
482 | ||
483 | See <file:Documentation/filesystems/cramfs.txt> and | |
484 | <file:fs/cramfs/README> for further information. | |
485 | ||
486 | To compile this as a module, choose M here: the module will be called | |
487 | cramfs. Note that the root file system (the one containing the | |
488 | directory /) cannot be compiled as a module. | |
489 | ||
490 | If unsure, say N. | |
491 | ||
6ab5c1ca PL |
492 | config SQUASHFS |
493 | tristate "SquashFS 4.0 - Squashed file system support" | |
494 | depends on BLOCK | |
495 | select ZLIB_INFLATE | |
496 | help | |
497 | Saying Y here includes support for SquashFS 4.0 (a Compressed | |
498 | Read-Only File System). Squashfs is a highly compressed read-only | |
499 | filesystem for Linux. It uses zlib compression to compress both | |
500 | files, inodes and directories. Inodes in the system are very small | |
501 | and all blocks are packed to minimise data overhead. Block sizes | |
502 | greater than 4K are supported up to a maximum of 1 Mbytes (default | |
503 | block size 128K). SquashFS 4.0 supports 64 bit filesystems and files | |
504 | (larger than 4GB), full uid/gid information, hard links and | |
505 | timestamps. | |
506 | ||
507 | Squashfs is intended for general read-only filesystem use, for | |
508 | archival use (i.e. in cases where a .tar.gz file may be used), and in | |
509 | embedded systems where low overhead is needed. Further information | |
510 | and tools are available from http://squashfs.sourceforge.net. | |
511 | ||
512 | If you want to compile this as a module ( = code which can be | |
513 | inserted in and removed from the running kernel whenever you want), | |
514 | say M here and read <file:Documentation/modules.txt>. The module | |
515 | will be called squashfs. Note that the root file system (the one | |
516 | containing the directory /) cannot be compiled as a module. | |
517 | ||
518 | If unsure, say N. | |
519 | ||
520 | config SQUASHFS_EMBEDDED | |
521 | ||
522 | bool "Additional option for memory-constrained systems" | |
523 | depends on SQUASHFS | |
524 | default n | |
525 | help | |
526 | Saying Y here allows you to specify cache size. | |
527 | ||
528 | If unsure, say N. | |
529 | ||
530 | config SQUASHFS_FRAGMENT_CACHE_SIZE | |
531 | int "Number of fragments cached" if SQUASHFS_EMBEDDED | |
532 | depends on SQUASHFS | |
533 | default "3" | |
534 | help | |
535 | By default SquashFS caches the last 3 fragments read from | |
536 | the filesystem. Increasing this amount may mean SquashFS | |
537 | has to re-read fragments less often from disk, at the expense | |
538 | of extra system memory. Decreasing this amount will mean | |
539 | SquashFS uses less memory at the expense of extra reads from disk. | |
540 | ||
541 | Note there must be at least one cached fragment. Anything | |
542 | much more than three will probably not make much difference. | |
543 | ||
1da177e4 LT |
544 | config VXFS_FS |
545 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
9361401e | 546 | depends on BLOCK |
1da177e4 LT |
547 | help |
548 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
549 | file system format. VERITAS VxFS(TM) is the standard file system | |
550 | of SCO UnixWare (and possibly others) and optionally available | |
551 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
552 | Currently only readonly access is supported. | |
553 | ||
554 | NOTE: the file system type as used by mount(1), mount(2) and | |
555 | fstab(5) is 'vxfs' as it describes the file system format, not | |
556 | the actual driver. | |
557 | ||
558 | To compile this as a module, choose M here: the module will be | |
559 | called freevxfs. If unsure, say N. | |
560 | ||
25fad945 RD |
561 | config MINIX_FS |
562 | tristate "Minix file system support" | |
563 | depends on BLOCK | |
564 | help | |
565 | Minix is a simple operating system used in many classes about OS's. | |
566 | The minix file system (method to organize files on a hard disk | |
567 | partition or a floppy disk) was the original file system for Linux, | |
568 | but has been superseded by the second extended file system ext2fs. | |
569 | You don't want to use the minix file system on your hard disk | |
570 | because of certain built-in restrictions, but it is sometimes found | |
571 | on older Linux floppy disks. This option will enlarge your kernel | |
572 | by about 28 KB. If unsure, say N. | |
573 | ||
574 | To compile this file system support as a module, choose M here: the | |
575 | module will be called minix. Note that the file system of your root | |
576 | partition (the one containing the directory /) cannot be compiled as | |
577 | a module. | |
578 | ||
63ca8ce2 BC |
579 | config OMFS_FS |
580 | tristate "SonicBlue Optimized MPEG File System support" | |
581 | depends on BLOCK | |
582 | select CRC_ITU_T | |
583 | help | |
584 | This is the proprietary file system used by the Rio Karma music | |
585 | player and ReplayTV DVR. Despite the name, this filesystem is not | |
586 | more efficient than a standard FS for MPEG files, in fact likely | |
587 | the opposite is true. Say Y if you have either of these devices | |
588 | and wish to mount its disk. | |
589 | ||
590 | To compile this file system support as a module, choose M here: the | |
591 | module will be called omfs. If unsure, say N. | |
1da177e4 LT |
592 | |
593 | config HPFS_FS | |
594 | tristate "OS/2 HPFS file system support" | |
9361401e | 595 | depends on BLOCK |
1da177e4 LT |
596 | help |
597 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
598 | is the file system used for organizing files on OS/2 hard disk | |
599 | partitions. Say Y if you want to be able to read files from and | |
600 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
601 | floppies however are in regular MSDOS format, so you don't need this | |
602 | option in order to be able to read them. Read | |
603 | <file:Documentation/filesystems/hpfs.txt>. | |
604 | ||
605 | To compile this file system support as a module, choose M here: the | |
606 | module will be called hpfs. If unsure, say N. | |
607 | ||
608 | ||
1da177e4 LT |
609 | config QNX4FS_FS |
610 | tristate "QNX4 file system support (read only)" | |
9361401e | 611 | depends on BLOCK |
1da177e4 LT |
612 | help |
613 | This is the file system used by the real-time operating systems | |
614 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
615 | Further information is available at <http://www.qnx.com/>. | |
616 | Say Y if you intend to mount QNX hard disks or floppies. | |
617 | Unless you say Y to "QNX4FS read-write support" below, you will | |
618 | only be able to read these file systems. | |
619 | ||
620 | To compile this file system support as a module, choose M here: the | |
621 | module will be called qnx4. | |
622 | ||
623 | If you don't know whether you need it, then you don't need it: | |
624 | answer N. | |
625 | ||
626 | config QNX4FS_RW | |
627 | bool "QNX4FS write support (DANGEROUS)" | |
628 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
629 | help | |
630 | Say Y if you want to test write support for QNX4 file systems. | |
631 | ||
632 | It's currently broken, so for now: | |
633 | answer N. | |
634 | ||
25fad945 RD |
635 | config ROMFS_FS |
636 | tristate "ROM file system support" | |
637 | depends on BLOCK | |
638 | ---help--- | |
639 | This is a very small read-only file system mainly intended for | |
640 | initial ram disks of installation disks, but it could be used for | |
641 | other read-only media as well. Read | |
642 | <file:Documentation/filesystems/romfs.txt> for details. | |
643 | ||
644 | To compile this file system support as a module, choose M here: the | |
645 | module will be called romfs. Note that the file system of your | |
646 | root partition (the one containing the directory /) cannot be a | |
647 | module. | |
648 | ||
649 | If you don't know whether you need it, then you don't need it: | |
650 | answer N. | |
1da177e4 LT |
651 | |
652 | ||
653 | config SYSV_FS | |
654 | tristate "System V/Xenix/V7/Coherent file system support" | |
9361401e | 655 | depends on BLOCK |
1da177e4 LT |
656 | help |
657 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
658 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
659 | here would allow you to read from their floppies and hard disk | |
660 | partitions. | |
661 | ||
662 | If you have floppies or hard disk partitions like that, it is likely | |
663 | that they contain binaries from those other Unix systems; in order | |
cab00891 | 664 | to run these binaries, you will want to install linux-abi which is |
1da177e4 LT |
665 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
666 | UnixWare, Dell Unix and System V programs under Linux. It is | |
667 | available via FTP (user: ftp) from | |
668 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
669 | NOTE: that will work only for binaries from Intel-based systems; | |
670 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
671 | ||
672 | If you only intend to mount files from some other Unix over the | |
673 | network using NFS, you don't need the System V file system support | |
674 | (but you need NFS file system support obviously). | |
675 | ||
676 | Note that this option is generally not needed for floppies, since a | |
677 | good portable way to transport files and directories between unixes | |
678 | (and even other operating systems) is given by the tar program ("man | |
679 | tar" or preferably "info tar"). Note also that this option has | |
680 | nothing whatsoever to do with the option "System V IPC". Read about | |
681 | the System V file system in | |
682 | <file:Documentation/filesystems/sysv-fs.txt>. | |
683 | Saying Y here will enlarge your kernel by about 27 KB. | |
684 | ||
685 | To compile this as a module, choose M here: the module will be called | |
686 | sysv. | |
687 | ||
688 | If you haven't heard about all of this before, it's safe to say N. | |
689 | ||
690 | ||
1da177e4 LT |
691 | config UFS_FS |
692 | tristate "UFS file system support (read only)" | |
9361401e | 693 | depends on BLOCK |
1da177e4 LT |
694 | help |
695 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
696 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
697 | Unixes can create and mount hard disk partitions and diskettes using | |
698 | this file system as well. Saying Y here will allow you to read from | |
699 | these partitions; if you also want to write to them, say Y to the | |
700 | experimental "UFS file system write support", below. Please read the | |
701 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
702 | ||
703 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
704 | READ-ONLY supported. | |
705 | ||
1da177e4 LT |
706 | Note that this option is generally not needed for floppies, since a |
707 | good portable way to transport files and directories between unixes | |
708 | (and even other operating systems) is given by the tar program ("man | |
709 | tar" or preferably "info tar"). | |
710 | ||
711 | When accessing NeXTstep files, you may need to convert them from the | |
712 | NeXT character set to the Latin1 character set; use the program | |
713 | recode ("info recode") for this purpose. | |
714 | ||
715 | To compile the UFS file system support as a module, choose M here: the | |
716 | module will be called ufs. | |
717 | ||
718 | If you haven't heard about all of this before, it's safe to say N. | |
719 | ||
720 | config UFS_FS_WRITE | |
721 | bool "UFS file system write support (DANGEROUS)" | |
5afb3145 | 722 | depends on UFS_FS && EXPERIMENTAL |
1da177e4 LT |
723 | help |
724 | Say Y here if you want to try writing to UFS partitions. This is | |
725 | experimental, so you should back up your UFS partitions beforehand. | |
726 | ||
abf5d15f ED |
727 | config UFS_DEBUG |
728 | bool "UFS debugging" | |
729 | depends on UFS_FS | |
730 | help | |
731 | If you are experiencing any problems with the UFS filesystem, say | |
732 | Y here. This will result in _many_ additional debugging messages to be | |
733 | written to the system log. | |
734 | ||
67ec7d3a | 735 | endif # MISC_FILESYSTEMS |
1da177e4 | 736 | |
ea0985ad JE |
737 | menuconfig NETWORK_FILESYSTEMS |
738 | bool "Network File Systems" | |
739 | default y | |
1da177e4 | 740 | depends on NET |
ea0985ad JE |
741 | ---help--- |
742 | Say Y here to get to see options for network filesystems and | |
743 | filesystem-related networking code, such as NFS daemon and | |
744 | RPCSEC security modules. | |
6fb1bc10 | 745 | |
ea0985ad JE |
746 | This option alone does not add any kernel code. |
747 | ||
748 | If you say N, all options in this submenu will be skipped and | |
749 | disabled; if unsure, say Y here. | |
750 | ||
751 | if NETWORK_FILESYSTEMS | |
1da177e4 LT |
752 | |
753 | config NFS_FS | |
6fb1bc10 | 754 | tristate "NFS client support" |
1da177e4 LT |
755 | depends on INET |
756 | select LOCKD | |
757 | select SUNRPC | |
b7fa0554 | 758 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 | 759 | help |
6fb1bc10 CL |
760 | Choose Y here if you want to access files residing on other |
761 | computers using Sun's Network File System protocol. To compile | |
762 | this file system support as a module, choose M here: the module | |
763 | will be called nfs. | |
1da177e4 | 764 | |
6fb1bc10 CL |
765 | To mount file systems exported by NFS servers, you also need to |
766 | install the user space mount.nfs command which can be found in | |
767 | the Linux nfs-utils package, available from http://linux-nfs.org/. | |
768 | Information about using the mount command is available in the | |
769 | mount(8) man page. More detail about the Linux NFS client | |
770 | implementation is available via the nfs(5) man page. | |
1da177e4 | 771 | |
6fb1bc10 CL |
772 | Below you can choose which versions of the NFS protocol are |
773 | available in the kernel to mount NFS servers. Support for NFS | |
774 | version 2 (RFC 1094) is always available when NFS_FS is selected. | |
1da177e4 | 775 | |
6fb1bc10 CL |
776 | To configure a system which mounts its root file system via NFS |
777 | at boot time, say Y here, select "Kernel level IP | |
778 | autoconfiguration" in the NETWORK menu, and select "Root file | |
779 | system on NFS" below. You cannot compile this file system as a | |
780 | module in this case. | |
1da177e4 | 781 | |
6fb1bc10 | 782 | If unsure, say N. |
1da177e4 LT |
783 | |
784 | config NFS_V3 | |
6fb1bc10 | 785 | bool "NFS client support for NFS version 3" |
1da177e4 LT |
786 | depends on NFS_FS |
787 | help | |
6fb1bc10 CL |
788 | This option enables support for version 3 of the NFS protocol |
789 | (RFC 1813) in the kernel's NFS client. | |
1da177e4 LT |
790 | |
791 | If unsure, say Y. | |
792 | ||
b7fa0554 | 793 | config NFS_V3_ACL |
6fb1bc10 | 794 | bool "NFS client support for the NFSv3 ACL protocol extension" |
b7fa0554 AG |
795 | depends on NFS_V3 |
796 | help | |
6fb1bc10 CL |
797 | Some NFS servers support an auxiliary NFSv3 ACL protocol that |
798 | Sun added to Solaris but never became an official part of the | |
799 | NFS version 3 protocol. This protocol extension allows | |
800 | applications on NFS clients to manipulate POSIX Access Control | |
801 | Lists on files residing on NFS servers. NFS servers enforce | |
802 | ACLs on local files whether this protocol is available or not. | |
803 | ||
804 | Choose Y here if your NFS server supports the Solaris NFSv3 ACL | |
805 | protocol extension and you want your NFS client to allow | |
806 | applications to access and modify ACLs on files on the server. | |
807 | ||
808 | Most NFS servers don't support the Solaris NFSv3 ACL protocol | |
809 | extension. You can choose N here or specify the "noacl" mount | |
810 | option to prevent your NFS client from trying to use the NFSv3 | |
811 | ACL protocol. | |
b7fa0554 AG |
812 | |
813 | If unsure, say N. | |
814 | ||
1da177e4 | 815 | config NFS_V4 |
6fb1bc10 | 816 | bool "NFS client support for NFS version 4 (EXPERIMENTAL)" |
1da177e4 LT |
817 | depends on NFS_FS && EXPERIMENTAL |
818 | select RPCSEC_GSS_KRB5 | |
819 | help | |
6fb1bc10 CL |
820 | This option enables support for version 4 of the NFS protocol |
821 | (RFC 3530) in the kernel's NFS client. | |
1da177e4 | 822 | |
6fb1bc10 CL |
823 | To mount NFS servers using NFSv4, you also need to install user |
824 | space programs which can be found in the Linux nfs-utils package, | |
825 | available from http://linux-nfs.org/. | |
1da177e4 LT |
826 | |
827 | If unsure, say N. | |
828 | ||
6fb1bc10 CL |
829 | config ROOT_NFS |
830 | bool "Root file system on NFS" | |
831 | depends on NFS_FS=y && IP_PNP | |
832 | help | |
833 | If you want your system to mount its root file system via NFS, | |
834 | choose Y here. This is common practice for managing systems | |
835 | without local permanent storage. For details, read | |
836 | <file:Documentation/filesystems/nfsroot.txt>. | |
837 | ||
838 | Most people say N here. | |
839 | ||
1da177e4 LT |
840 | config NFSD |
841 | tristate "NFS server support" | |
842 | depends on INET | |
843 | select LOCKD | |
844 | select SUNRPC | |
845 | select EXPORTFS | |
f05e15b5 | 846 | select NFS_ACL_SUPPORT if NFSD_V2_ACL |
1da177e4 | 847 | help |
d24455b5 CL |
848 | Choose Y here if you want to allow other computers to access |
849 | files residing on this system using Sun's Network File System | |
850 | protocol. To compile the NFS server support as a module, | |
851 | choose M here: the module will be called nfsd. | |
1da177e4 | 852 | |
d24455b5 CL |
853 | You may choose to use a user-space NFS server instead, in which |
854 | case you can choose N here. | |
1da177e4 | 855 | |
d24455b5 CL |
856 | To export local file systems using NFS, you also need to install |
857 | user space programs which can be found in the Linux nfs-utils | |
858 | package, available from http://linux-nfs.org/. More detail about | |
859 | the Linux NFS server implementation is available via the | |
860 | exports(5) man page. | |
1da177e4 | 861 | |
d24455b5 CL |
862 | Below you can choose which versions of the NFS protocol are |
863 | available to clients mounting the NFS server on this system. | |
864 | Support for NFS version 2 (RFC 1094) is always available when | |
865 | CONFIG_NFSD is selected. | |
1da177e4 | 866 | |
d24455b5 | 867 | If unsure, say N. |
1da177e4 | 868 | |
a257cdd0 AG |
869 | config NFSD_V2_ACL |
870 | bool | |
871 | depends on NFSD | |
872 | ||
1da177e4 | 873 | config NFSD_V3 |
d24455b5 | 874 | bool "NFS server support for NFS version 3" |
1da177e4 LT |
875 | depends on NFSD |
876 | help | |
d24455b5 CL |
877 | This option enables support in your system's NFS server for |
878 | version 3 of the NFS protocol (RFC 1813). | |
879 | ||
880 | If unsure, say Y. | |
1da177e4 | 881 | |
a257cdd0 | 882 | config NFSD_V3_ACL |
d24455b5 | 883 | bool "NFS server support for the NFSv3 ACL protocol extension" |
a257cdd0 | 884 | depends on NFSD_V3 |
78dd0992 | 885 | select NFSD_V2_ACL |
a257cdd0 | 886 | help |
d24455b5 CL |
887 | Solaris NFS servers support an auxiliary NFSv3 ACL protocol that |
888 | never became an official part of the NFS version 3 protocol. | |
889 | This protocol extension allows applications on NFS clients to | |
890 | manipulate POSIX Access Control Lists on files residing on NFS | |
891 | servers. NFS servers enforce POSIX ACLs on local files whether | |
892 | this protocol is available or not. | |
893 | ||
894 | This option enables support in your system's NFS server for the | |
895 | NFSv3 ACL protocol extension allowing NFS clients to manipulate | |
896 | POSIX ACLs on files exported by your system's NFS server. NFS | |
897 | clients which support the Solaris NFSv3 ACL protocol can then | |
898 | access and modify ACLs on your NFS server. | |
899 | ||
900 | To store ACLs on your NFS server, you also need to enable ACL- | |
901 | related CONFIG options for your local file systems of choice. | |
902 | ||
903 | If unsure, say N. | |
a257cdd0 | 904 | |
1da177e4 | 905 | config NFSD_V4 |
d24455b5 | 906 | bool "NFS server support for NFS version 4 (EXPERIMENTAL)" |
1a448fdb CL |
907 | depends on NFSD && PROC_FS && EXPERIMENTAL |
908 | select NFSD_V3 | |
89206955 | 909 | select FS_POSIX_ACL |
42ed95c4 | 910 | select RPCSEC_GSS_KRB5 |
1da177e4 | 911 | help |
d24455b5 CL |
912 | This option enables support in your system's NFS server for |
913 | version 4 of the NFS protocol (RFC 3530). | |
914 | ||
915 | To export files using NFSv4, you need to install additional user | |
916 | space programs which can be found in the Linux nfs-utils package, | |
917 | available from http://linux-nfs.org/. | |
918 | ||
1da177e4 LT |
919 | If unsure, say N. |
920 | ||
1da177e4 LT |
921 | config LOCKD |
922 | tristate | |
923 | ||
924 | config LOCKD_V4 | |
925 | bool | |
926 | depends on NFSD_V3 || NFS_V3 | |
927 | default y | |
928 | ||
929 | config EXPORTFS | |
930 | tristate | |
931 | ||
a257cdd0 AG |
932 | config NFS_ACL_SUPPORT |
933 | tristate | |
934 | select FS_POSIX_ACL | |
935 | ||
936 | config NFS_COMMON | |
937 | bool | |
938 | depends on NFSD || NFS_FS | |
939 | default y | |
940 | ||
1da177e4 LT |
941 | config SUNRPC |
942 | tristate | |
943 | ||
944 | config SUNRPC_GSS | |
945 | tristate | |
946 | ||
c3a57ed7 | 947 | config SUNRPC_XPRT_RDMA |
3211e4eb | 948 | tristate |
113632d0 | 949 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL |
3211e4eb | 950 | default SUNRPC && INFINIBAND |
327a299d CL |
951 | help |
952 | This option enables an RPC client transport capability that | |
953 | allows the NFS client to mount servers via an RDMA-enabled | |
954 | transport. | |
955 | ||
956 | To compile RPC client RDMA transport support as a module, | |
957 | choose M here: the module will be called xprtrdma. | |
958 | ||
959 | If unsure, say N. | |
c3a57ed7 | 960 | |
a26cfad6 CL |
961 | config SUNRPC_REGISTER_V4 |
962 | bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)" | |
963 | depends on SUNRPC && EXPERIMENTAL | |
964 | default n | |
965 | help | |
966 | Sun added support for registering RPC services at an IPv6 | |
967 | address by creating two new versions of the rpcbind protocol | |
968 | (RFC 1833). | |
969 | ||
970 | This option enables support in the kernel RPC server for | |
971 | registering kernel RPC services via version 4 of the rpcbind | |
972 | protocol. If you enable this option, you must run a portmapper | |
973 | daemon that supports rpcbind protocol version 4. | |
974 | ||
975 | Serving NFS over IPv6 from knfsd (the kernel's NFS server) | |
976 | requires that you enable this option and use a portmapper that | |
977 | supports rpcbind version 4. | |
978 | ||
979 | If unsure, say N to get traditional behavior (register kernel | |
980 | RPC services using only rpcbind version 2). Distributions | |
981 | using the legacy Linux portmapper daemon must say N here. | |
982 | ||
1da177e4 LT |
983 | config RPCSEC_GSS_KRB5 |
984 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
985 | depends on SUNRPC && EXPERIMENTAL | |
986 | select SUNRPC_GSS | |
987 | select CRYPTO | |
988 | select CRYPTO_MD5 | |
989 | select CRYPTO_DES | |
bcbaecbb | 990 | select CRYPTO_CBC |
1da177e4 | 991 | help |
327a299d CL |
992 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
993 | GSS-API mechanism (RFC 1964). | |
1da177e4 | 994 | |
327a299d CL |
995 | Secure RPC calls with Kerberos require an auxiliary user-space |
996 | daemon which may be found in the Linux nfs-utils package | |
997 | available from http://linux-nfs.org/. In addition, user-space | |
998 | Kerberos support should be installed. | |
1da177e4 LT |
999 | |
1000 | If unsure, say N. | |
1001 | ||
1002 | config RPCSEC_GSS_SPKM3 | |
1003 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1004 | depends on SUNRPC && EXPERIMENTAL | |
1005 | select SUNRPC_GSS | |
1006 | select CRYPTO | |
1007 | select CRYPTO_MD5 | |
1008 | select CRYPTO_DES | |
df6db302 | 1009 | select CRYPTO_CAST5 |
bcbaecbb | 1010 | select CRYPTO_CBC |
1da177e4 | 1011 | help |
327a299d CL |
1012 | Choose Y here to enable Secure RPC using the SPKM3 public key |
1013 | GSS-API mechansim (RFC 2025). | |
1da177e4 | 1014 | |
327a299d CL |
1015 | Secure RPC calls with SPKM3 require an auxiliary userspace |
1016 | daemon which may be found in the Linux nfs-utils package | |
1017 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1018 | |
1019 | If unsure, say N. | |
1020 | ||
1021 | config SMB_FS | |
c7736339 | 1022 | tristate "SMB file system support (OBSOLETE, please use CIFS)" |
1da177e4 LT |
1023 | depends on INET |
1024 | select NLS | |
1025 | help | |
1026 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1027 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1028 | files and printers over local networks. Saying Y here allows you to | |
1029 | mount their file systems (often called "shares" in this context) and | |
1030 | access them just like any other Unix directory. Currently, this | |
1031 | works only if the Windows machines use TCP/IP as the underlying | |
1032 | transport protocol, and not NetBEUI. For details, read | |
1033 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1034 | available from <http://www.tldp.org/docs.html#howto>. | |
1035 | ||
1036 | Note: if you just want your box to act as an SMB *server* and make | |
1037 | files and printing services available to Windows clients (which need | |
1038 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1039 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1040 | for that. | |
1041 | ||
1042 | General information about how to connect Linux, Windows machines and | |
1043 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1044 | ||
c7736339 AM |
1045 | To compile the SMB support as a module, choose M here: |
1046 | the module will be called smbfs. Most people say N, however. | |
1da177e4 LT |
1047 | |
1048 | config SMB_NLS_DEFAULT | |
1049 | bool "Use a default NLS" | |
1050 | depends on SMB_FS | |
1051 | help | |
1052 | Enabling this will make smbfs use nls translations by default. You | |
1053 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1054 | settings and you need to give the default nls for the SMB server as | |
1055 | CONFIG_SMB_NLS_REMOTE. | |
1056 | ||
1057 | The nls settings can be changed at mount time, if your smbmount | |
1058 | supports that, using the codepage and iocharset parameters. | |
1059 | ||
1060 | smbmount from samba 2.2.0 or later supports this. | |
1061 | ||
1062 | config SMB_NLS_REMOTE | |
1063 | string "Default Remote NLS Option" | |
1064 | depends on SMB_NLS_DEFAULT | |
1065 | default "cp437" | |
1066 | help | |
1067 | This setting allows you to specify a default value for which | |
1068 | codepage the server uses. If this field is left blank no | |
1069 | translations will be done by default. The local codepage/charset | |
1070 | default to CONFIG_NLS_DEFAULT. | |
1071 | ||
1072 | The nls settings can be changed at mount time, if your smbmount | |
1073 | supports that, using the codepage and iocharset parameters. | |
1074 | ||
1075 | smbmount from samba 2.2.0 or later supports this. | |
1076 | ||
bb26b963 | 1077 | source "fs/cifs/Kconfig" |
6103335d | 1078 | |
1da177e4 LT |
1079 | config NCP_FS |
1080 | tristate "NCP file system support (to mount NetWare volumes)" | |
1081 | depends on IPX!=n || INET | |
1082 | help | |
1083 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1084 | used by Novell NetWare clients to talk to file servers. It is to | |
1085 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1086 | to mount NetWare file server volumes and to access them just like | |
1087 | any other Unix directory. For details, please read the file | |
1088 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1089 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1090 | ||
1091 | You do not have to say Y here if you want your Linux box to act as a | |
1092 | file *server* for Novell NetWare clients. | |
1093 | ||
1094 | General information about how to connect Linux, Windows machines and | |
1095 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1096 | ||
1097 | To compile this as a module, choose M here: the module will be called | |
1098 | ncpfs. Say N unless you are connected to a Novell network. | |
1099 | ||
1100 | source "fs/ncpfs/Kconfig" | |
1101 | ||
1102 | config CODA_FS | |
1103 | tristate "Coda file system support (advanced network fs)" | |
1104 | depends on INET | |
1105 | help | |
1106 | Coda is an advanced network file system, similar to NFS in that it | |
1107 | enables you to mount file systems of a remote server and access them | |
1108 | with regular Unix commands as if they were sitting on your hard | |
1109 | disk. Coda has several advantages over NFS: support for | |
1110 | disconnected operation (e.g. for laptops), read/write server | |
1111 | replication, security model for authentication and encryption, | |
1112 | persistent client caches and write back caching. | |
1113 | ||
1114 | If you say Y here, your Linux box will be able to act as a Coda | |
1115 | *client*. You will need user level code as well, both for the | |
1116 | client and server. Servers are currently user level, i.e. they need | |
1117 | no kernel support. Please read | |
1118 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1119 | home page <http://www.coda.cs.cmu.edu/>. | |
1120 | ||
1121 | To compile the coda client support as a module, choose M here: the | |
1122 | module will be called coda. | |
1123 | ||
1da177e4 | 1124 | config AFS_FS |
64aaa4f8 | 1125 | tristate "Andrew File System support (AFS) (EXPERIMENTAL)" |
1da177e4 | 1126 | depends on INET && EXPERIMENTAL |
08e0e7c8 | 1127 | select AF_RXRPC |
1da177e4 LT |
1128 | help |
1129 | If you say Y here, you will get an experimental Andrew File System | |
1130 | driver. It currently only supports unsecured read-only AFS access. | |
1131 | ||
cc2e2767 | 1132 | See <file:Documentation/filesystems/afs.txt> for more information. |
1da177e4 LT |
1133 | |
1134 | If unsure, say N. | |
1135 | ||
08e0e7c8 DH |
1136 | config AFS_DEBUG |
1137 | bool "AFS dynamic debugging" | |
1138 | depends on AFS_FS | |
1139 | help | |
1140 | Say Y here to make runtime controllable debugging messages appear. | |
1141 | ||
1142 | See <file:Documentation/filesystems/afs.txt> for more information. | |
1143 | ||
1144 | If unsure, say N. | |
1145 | ||
93fa58cb EVH |
1146 | config 9P_FS |
1147 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" | |
bd238fb4 | 1148 | depends on INET && NET_9P && EXPERIMENTAL |
93fa58cb EVH |
1149 | help |
1150 | If you say Y here, you will get experimental support for | |
1151 | Plan 9 resource sharing via the 9P2000 protocol. | |
1152 | ||
1153 | See <http://v9fs.sf.net> for more information. | |
1154 | ||
1155 | If unsure, say N. | |
1156 | ||
ea0985ad | 1157 | endif # NETWORK_FILESYSTEMS |
1da177e4 | 1158 | |
9361401e | 1159 | if BLOCK |
1da177e4 LT |
1160 | menu "Partition Types" |
1161 | ||
1162 | source "fs/partitions/Kconfig" | |
1163 | ||
1164 | endmenu | |
9361401e | 1165 | endif |
1da177e4 LT |
1166 | |
1167 | source "fs/nls/Kconfig" | |
e7fd4179 | 1168 | source "fs/dlm/Kconfig" |
1da177e4 LT |
1169 | |
1170 | endmenu |