diff options
Diffstat (limited to 'fs/Kconfig')
-rw-r--r-- | fs/Kconfig | 607 |
1 files changed, 8 insertions, 599 deletions
diff --git a/fs/Kconfig b/fs/Kconfig index d0a1174fb516..e46297f020c1 100644 --- a/fs/Kconfig +++ b/fs/Kconfig | |||
@@ -6,61 +6,9 @@ menu "File systems" | |||
6 | 6 | ||
7 | if BLOCK | 7 | if BLOCK |
8 | 8 | ||
9 | config EXT2_FS | 9 | source "fs/ext2/Kconfig" |
10 | tristate "Second extended fs support" | 10 | source "fs/ext3/Kconfig" |
11 | help | 11 | source "fs/ext4/Kconfig" |
12 | Ext2 is a standard Linux file system for hard disks. | ||
13 | |||
14 | To compile this file system support as a module, choose M here: the | ||
15 | module will be called ext2. | ||
16 | |||
17 | If unsure, say Y. | ||
18 | |||
19 | config EXT2_FS_XATTR | ||
20 | bool "Ext2 extended attributes" | ||
21 | depends on EXT2_FS | ||
22 | help | ||
23 | Extended attributes are name:value pairs associated with inodes by | ||
24 | the kernel or by users (see the attr(5) manual page, or visit | ||
25 | <http://acl.bestbits.at/> for details). | ||
26 | |||
27 | If unsure, say N. | ||
28 | |||
29 | config EXT2_FS_POSIX_ACL | ||
30 | bool "Ext2 POSIX Access Control Lists" | ||
31 | depends on EXT2_FS_XATTR | ||
32 | select FS_POSIX_ACL | ||
33 | help | ||
34 | Posix Access Control Lists (ACLs) support permissions for users and | ||
35 | groups beyond the owner/group/world scheme. | ||
36 | |||
37 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
38 | Linux website <http://acl.bestbits.at/>. | ||
39 | |||
40 | If you don't know what Access Control Lists are, say N | ||
41 | |||
42 | config EXT2_FS_SECURITY | ||
43 | bool "Ext2 Security Labels" | ||
44 | depends on EXT2_FS_XATTR | ||
45 | help | ||
46 | Security labels support alternative access control models | ||
47 | implemented by security modules like SELinux. This option | ||
48 | enables an extended attribute handler for file security | ||
49 | labels in the ext2 filesystem. | ||
50 | |||
51 | If you are not using a security module that requires using | ||
52 | extended attributes for file security labels, say N. | ||
53 | |||
54 | config EXT2_FS_XIP | ||
55 | bool "Ext2 execute in place support" | ||
56 | depends on EXT2_FS && MMU | ||
57 | help | ||
58 | Execute in place can be used on memory-backed block devices. If you | ||
59 | enable this option, you can select to mount block devices which are | ||
60 | capable of this feature without using the page cache. | ||
61 | |||
62 | If you do not use a block device that is capable of using this, | ||
63 | or if unsure, say N. | ||
64 | 12 | ||
65 | config FS_XIP | 13 | config FS_XIP |
66 | # execute in place | 14 | # execute in place |
@@ -68,218 +16,8 @@ config FS_XIP | |||
68 | depends on EXT2_FS_XIP | 16 | depends on EXT2_FS_XIP |
69 | default y | 17 | default y |
70 | 18 | ||
71 | config EXT3_FS | 19 | source "fs/jbd/Kconfig" |
72 | tristate "Ext3 journalling file system support" | 20 | source "fs/jbd2/Kconfig" |
73 | select JBD | ||
74 | help | ||
75 | This is the journalling version of the Second extended file system | ||
76 | (often called ext3), the de facto standard Linux file system | ||
77 | (method to organize files on a storage device) for hard disks. | ||
78 | |||
79 | The journalling code included in this driver means you do not have | ||
80 | to run e2fsck (file system checker) on your file systems after a | ||
81 | crash. The journal keeps track of any changes that were being made | ||
82 | at the time the system crashed, and can ensure that your file system | ||
83 | is consistent without the need for a lengthy check. | ||
84 | |||
85 | Other than adding the journal to the file system, the on-disk format | ||
86 | of ext3 is identical to ext2. It is possible to freely switch | ||
87 | between using the ext3 driver and the ext2 driver, as long as the | ||
88 | file system has been cleanly unmounted, or e2fsck is run on the file | ||
89 | system. | ||
90 | |||
91 | To add a journal on an existing ext2 file system or change the | ||
92 | behavior of ext3 file systems, you can use the tune2fs utility ("man | ||
93 | tune2fs"). To modify attributes of files and directories on ext3 | ||
94 | file systems, use chattr ("man chattr"). You need to be using | ||
95 | e2fsprogs version 1.20 or later in order to create ext3 journals | ||
96 | (available at <http://sourceforge.net/projects/e2fsprogs/>). | ||
97 | |||
98 | To compile this file system support as a module, choose M here: the | ||
99 | module will be called ext3. | ||
100 | |||
101 | config EXT3_FS_XATTR | ||
102 | bool "Ext3 extended attributes" | ||
103 | depends on EXT3_FS | ||
104 | default y | ||
105 | help | ||
106 | Extended attributes are name:value pairs associated with inodes by | ||
107 | the kernel or by users (see the attr(5) manual page, or visit | ||
108 | <http://acl.bestbits.at/> for details). | ||
109 | |||
110 | If unsure, say N. | ||
111 | |||
112 | You need this for POSIX ACL support on ext3. | ||
113 | |||
114 | config EXT3_FS_POSIX_ACL | ||
115 | bool "Ext3 POSIX Access Control Lists" | ||
116 | depends on EXT3_FS_XATTR | ||
117 | select FS_POSIX_ACL | ||
118 | help | ||
119 | Posix Access Control Lists (ACLs) support permissions for users and | ||
120 | groups beyond the owner/group/world scheme. | ||
121 | |||
122 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
123 | Linux website <http://acl.bestbits.at/>. | ||
124 | |||
125 | If you don't know what Access Control Lists are, say N | ||
126 | |||
127 | config EXT3_FS_SECURITY | ||
128 | bool "Ext3 Security Labels" | ||
129 | depends on EXT3_FS_XATTR | ||
130 | help | ||
131 | Security labels support alternative access control models | ||
132 | implemented by security modules like SELinux. This option | ||
133 | enables an extended attribute handler for file security | ||
134 | labels in the ext3 filesystem. | ||
135 | |||
136 | If you are not using a security module that requires using | ||
137 | extended attributes for file security labels, say N. | ||
138 | |||
139 | config EXT4_FS | ||
140 | tristate "The Extended 4 (ext4) filesystem" | ||
141 | select JBD2 | ||
142 | select CRC16 | ||
143 | help | ||
144 | This is the next generation of the ext3 filesystem. | ||
145 | |||
146 | Unlike the change from ext2 filesystem to ext3 filesystem, | ||
147 | the on-disk format of ext4 is not forwards compatible with | ||
148 | ext3; it is based on extent maps and it supports 48-bit | ||
149 | physical block numbers. The ext4 filesystem also supports delayed | ||
150 | allocation, persistent preallocation, high resolution time stamps, | ||
151 | and a number of other features to improve performance and speed | ||
152 | up fsck time. For more information, please see the web pages at | ||
153 | http://ext4.wiki.kernel.org. | ||
154 | |||
155 | The ext4 filesystem will support mounting an ext3 | ||
156 | filesystem; while there will be some performance gains from | ||
157 | the delayed allocation and inode table readahead, the best | ||
158 | performance gains will require enabling ext4 features in the | ||
159 | filesystem, or formating a new filesystem as an ext4 | ||
160 | filesystem initially. | ||
161 | |||
162 | To compile this file system support as a module, choose M here. The | ||
163 | module will be called ext4. | ||
164 | |||
165 | If unsure, say N. | ||
166 | |||
167 | config EXT4DEV_COMPAT | ||
168 | bool "Enable ext4dev compatibility" | ||
169 | depends on EXT4_FS | ||
170 | help | ||
171 | Starting with 2.6.28, the name of the ext4 filesystem was | ||
172 | renamed from ext4dev to ext4. Unfortunately there are some | ||
173 | legacy userspace programs (such as klibc's fstype) have | ||
174 | "ext4dev" hardcoded. | ||
175 | |||
176 | To enable backwards compatibility so that systems that are | ||
177 | still expecting to mount ext4 filesystems using ext4dev, | ||
178 | chose Y here. This feature will go away by 2.6.31, so | ||
179 | please arrange to get your userspace programs fixed! | ||
180 | |||
181 | config EXT4_FS_XATTR | ||
182 | bool "Ext4 extended attributes" | ||
183 | depends on EXT4_FS | ||
184 | default y | ||
185 | help | ||
186 | Extended attributes are name:value pairs associated with inodes by | ||
187 | the kernel or by users (see the attr(5) manual page, or visit | ||
188 | <http://acl.bestbits.at/> for details). | ||
189 | |||
190 | If unsure, say N. | ||
191 | |||
192 | You need this for POSIX ACL support on ext4. | ||
193 | |||
194 | config EXT4_FS_POSIX_ACL | ||
195 | bool "Ext4 POSIX Access Control Lists" | ||
196 | depends on EXT4_FS_XATTR | ||
197 | select FS_POSIX_ACL | ||
198 | help | ||
199 | POSIX Access Control Lists (ACLs) support permissions for users and | ||
200 | groups beyond the owner/group/world scheme. | ||
201 | |||
202 | To learn more about Access Control Lists, visit the POSIX ACLs for | ||
203 | Linux website <http://acl.bestbits.at/>. | ||
204 | |||
205 | If you don't know what Access Control Lists are, say N | ||
206 | |||
207 | config EXT4_FS_SECURITY | ||
208 | bool "Ext4 Security Labels" | ||
209 | depends on EXT4_FS_XATTR | ||
210 | help | ||
211 | Security labels support alternative access control models | ||
212 | implemented by security modules like SELinux. This option | ||
213 | enables an extended attribute handler for file security | ||
214 | labels in the ext4 filesystem. | ||
215 | |||
216 | If you are not using a security module that requires using | ||
217 | extended attributes for file security labels, say N. | ||
218 | |||
219 | config JBD | ||
220 | tristate | ||
221 | help | ||
222 | This is a generic journalling layer for block devices. It is | ||
223 | currently used by the ext3 file system, but it could also be | ||
224 | used to add journal support to other file systems or block | ||
225 | devices such as RAID or LVM. | ||
226 | |||
227 | If you are using the ext3 file system, you need to say Y here. | ||
228 | If you are not using ext3 then you will probably want to say N. | ||
229 | |||
230 | To compile this device as a module, choose M here: the module will be | ||
231 | called jbd. If you are compiling ext3 into the kernel, you | ||
232 | cannot compile this code as a module. | ||
233 | |||
234 | config JBD_DEBUG | ||
235 | bool "JBD (ext3) debugging support" | ||
236 | depends on JBD && DEBUG_FS | ||
237 | help | ||
238 | If you are using the ext3 journaled file system (or potentially any | ||
239 | other file system/device using JBD), this option allows you to | ||
240 | enable debugging output while the system is running, in order to | ||
241 | help track down any problems you are having. By default the | ||
242 | debugging output will be turned off. | ||
243 | |||
244 | If you select Y here, then you will be able to turn on debugging | ||
245 | with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a | ||
246 | number between 1 and 5, the higher the number, the more debugging | ||
247 | output is generated. To turn debugging off again, do | ||
248 | "echo 0 > /sys/kernel/debug/jbd/jbd-debug". | ||
249 | |||
250 | config JBD2 | ||
251 | tristate | ||
252 | select CRC32 | ||
253 | help | ||
254 | This is a generic journaling layer for block devices that support | ||
255 | both 32-bit and 64-bit block numbers. It is currently used by | ||
256 | the ext4 and OCFS2 filesystems, but it could also be used to add | ||
257 | journal support to other file systems or block devices such | ||
258 | as RAID or LVM. | ||
259 | |||
260 | If you are using ext4 or OCFS2, you need to say Y here. | ||
261 | If you are not using ext4 or OCFS2 then you will | ||
262 | probably want to say N. | ||
263 | |||
264 | To compile this device as a module, choose M here. The module will be | ||
265 | called jbd2. If you are compiling ext4 or OCFS2 into the kernel, | ||
266 | you cannot compile this code as a module. | ||
267 | |||
268 | config JBD2_DEBUG | ||
269 | bool "JBD2 (ext4) debugging support" | ||
270 | depends on JBD2 && DEBUG_FS | ||
271 | help | ||
272 | If you are using the ext4 journaled file system (or | ||
273 | potentially any other filesystem/device using JBD2), this option | ||
274 | allows you to enable debugging output while the system is running, | ||
275 | in order to help track down any problems you are having. | ||
276 | By default, the debugging output will be turned off. | ||
277 | |||
278 | If you select Y here, then you will be able to turn on debugging | ||
279 | with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a | ||
280 | number between 1 and 5. The higher the number, the more debugging | ||
281 | output is generated. To turn debugging off again, do | ||
282 | "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". | ||
283 | 21 | ||
284 | config FS_MBCACHE | 22 | config FS_MBCACHE |
285 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) | 23 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) |
@@ -665,7 +403,7 @@ config AUTOFS4_FS | |||
665 | N here. | 403 | N here. |
666 | 404 | ||
667 | config FUSE_FS | 405 | config FUSE_FS |
668 | tristate "Filesystem in Userspace support" | 406 | tristate "FUSE (Filesystem in Userspace) support" |
669 | help | 407 | help |
670 | With FUSE it is possible to implement a fully functional filesystem | 408 | With FUSE it is possible to implement a fully functional filesystem |
671 | in a userspace program. | 409 | in a userspace program. |
@@ -1168,195 +906,7 @@ config EFS_FS | |||
1168 | To compile the EFS file system support as a module, choose M here: the | 906 | To compile the EFS file system support as a module, choose M here: the |
1169 | module will be called efs. | 907 | module will be called efs. |
1170 | 908 | ||
1171 | config JFFS2_FS | 909 | source "fs/jffs2/Kconfig" |
1172 | tristate "Journalling Flash File System v2 (JFFS2) support" | ||
1173 | select CRC32 | ||
1174 | depends on MTD | ||
1175 | help | ||
1176 | JFFS2 is the second generation of the Journalling Flash File System | ||
1177 | for use on diskless embedded devices. It provides improved wear | ||
1178 | levelling, compression and support for hard links. You cannot use | ||
1179 | this on normal block devices, only on 'MTD' devices. | ||
1180 | |||
1181 | Further information on the design and implementation of JFFS2 is | ||
1182 | available at <http://sources.redhat.com/jffs2/>. | ||
1183 | |||
1184 | config JFFS2_FS_DEBUG | ||
1185 | int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" | ||
1186 | depends on JFFS2_FS | ||
1187 | default "0" | ||
1188 | help | ||
1189 | This controls the amount of debugging messages produced by the JFFS2 | ||
1190 | code. Set it to zero for use in production systems. For evaluation, | ||
1191 | testing and debugging, it's advisable to set it to one. This will | ||
1192 | enable a few assertions and will print debugging messages at the | ||
1193 | KERN_DEBUG loglevel, where they won't normally be visible. Level 2 | ||
1194 | is unlikely to be useful - it enables extra debugging in certain | ||
1195 | areas which at one point needed debugging, but when the bugs were | ||
1196 | located and fixed, the detailed messages were relegated to level 2. | ||
1197 | |||
1198 | If reporting bugs, please try to have available a full dump of the | ||
1199 | messages at debug level 1 while the misbehaviour was occurring. | ||
1200 | |||
1201 | config JFFS2_FS_WRITEBUFFER | ||
1202 | bool "JFFS2 write-buffering support" | ||
1203 | depends on JFFS2_FS | ||
1204 | default y | ||
1205 | help | ||
1206 | This enables the write-buffering support in JFFS2. | ||
1207 | |||
1208 | This functionality is required to support JFFS2 on the following | ||
1209 | types of flash devices: | ||
1210 | - NAND flash | ||
1211 | - NOR flash with transparent ECC | ||
1212 | - DataFlash | ||
1213 | |||
1214 | config JFFS2_FS_WBUF_VERIFY | ||
1215 | bool "Verify JFFS2 write-buffer reads" | ||
1216 | depends on JFFS2_FS_WRITEBUFFER | ||
1217 | default n | ||
1218 | help | ||
1219 | This causes JFFS2 to read back every page written through the | ||
1220 | write-buffer, and check for errors. | ||
1221 | |||
1222 | config JFFS2_SUMMARY | ||
1223 | bool "JFFS2 summary support (EXPERIMENTAL)" | ||
1224 | depends on JFFS2_FS && EXPERIMENTAL | ||
1225 | default n | ||
1226 | help | ||
1227 | This feature makes it possible to use summary information | ||
1228 | for faster filesystem mount. | ||
1229 | |||
1230 | The summary information can be inserted into a filesystem image | ||
1231 | by the utility 'sumtool'. | ||
1232 | |||
1233 | If unsure, say 'N'. | ||
1234 | |||
1235 | config JFFS2_FS_XATTR | ||
1236 | bool "JFFS2 XATTR support (EXPERIMENTAL)" | ||
1237 | depends on JFFS2_FS && EXPERIMENTAL | ||
1238 | default n | ||
1239 | help | ||
1240 | Extended attributes are name:value pairs associated with inodes by | ||
1241 | the kernel or by users (see the attr(5) manual page, or visit | ||
1242 | <http://acl.bestbits.at/> for details). | ||
1243 | |||
1244 | If unsure, say N. | ||
1245 | |||
1246 | config JFFS2_FS_POSIX_ACL | ||
1247 | bool "JFFS2 POSIX Access Control Lists" | ||
1248 | depends on JFFS2_FS_XATTR | ||
1249 | default y | ||
1250 | select FS_POSIX_ACL | ||
1251 | help | ||
1252 | Posix Access Control Lists (ACLs) support permissions for users and | ||
1253 | groups beyond the owner/group/world scheme. | ||
1254 | |||
1255 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
1256 | Linux website <http://acl.bestbits.at/>. | ||
1257 | |||
1258 | If you don't know what Access Control Lists are, say N | ||
1259 | |||
1260 | config JFFS2_FS_SECURITY | ||
1261 | bool "JFFS2 Security Labels" | ||
1262 | depends on JFFS2_FS_XATTR | ||
1263 | default y | ||
1264 | help | ||
1265 | Security labels support alternative access control models | ||
1266 | implemented by security modules like SELinux. This option | ||
1267 | enables an extended attribute handler for file security | ||
1268 | labels in the jffs2 filesystem. | ||
1269 | |||
1270 | If you are not using a security module that requires using | ||
1271 | extended attributes for file security labels, say N. | ||
1272 | |||
1273 | config JFFS2_COMPRESSION_OPTIONS | ||
1274 | bool "Advanced compression options for JFFS2" | ||
1275 | depends on JFFS2_FS | ||
1276 | default n | ||
1277 | help | ||
1278 | Enabling this option allows you to explicitly choose which | ||
1279 | compression modules, if any, are enabled in JFFS2. Removing | ||
1280 | compressors can mean you cannot read existing file systems, | ||
1281 | and enabling experimental compressors can mean that you | ||
1282 | write a file system which cannot be read by a standard kernel. | ||
1283 | |||
1284 | If unsure, you should _definitely_ say 'N'. | ||
1285 | |||
1286 | config JFFS2_ZLIB | ||
1287 | bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS | ||
1288 | select ZLIB_INFLATE | ||
1289 | select ZLIB_DEFLATE | ||
1290 | depends on JFFS2_FS | ||
1291 | default y | ||
1292 | help | ||
1293 | Zlib is designed to be a free, general-purpose, legally unencumbered, | ||
1294 | lossless data-compression library for use on virtually any computer | ||
1295 | hardware and operating system. See <http://www.gzip.org/zlib/> for | ||
1296 | further information. | ||
1297 | |||
1298 | Say 'Y' if unsure. | ||
1299 | |||
1300 | config JFFS2_LZO | ||
1301 | bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS | ||
1302 | select LZO_COMPRESS | ||
1303 | select LZO_DECOMPRESS | ||
1304 | depends on JFFS2_FS | ||
1305 | default n | ||
1306 | help | ||
1307 | minilzo-based compression. Generally works better than Zlib. | ||
1308 | |||
1309 | This feature was added in July, 2007. Say 'N' if you need | ||
1310 | compatibility with older bootloaders or kernels. | ||
1311 | |||
1312 | config JFFS2_RTIME | ||
1313 | bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS | ||
1314 | depends on JFFS2_FS | ||
1315 | default y | ||
1316 | help | ||
1317 | Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. | ||
1318 | |||
1319 | config JFFS2_RUBIN | ||
1320 | bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS | ||
1321 | depends on JFFS2_FS | ||
1322 | default n | ||
1323 | help | ||
1324 | RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. | ||
1325 | |||
1326 | choice | ||
1327 | prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS | ||
1328 | default JFFS2_CMODE_PRIORITY | ||
1329 | depends on JFFS2_FS | ||
1330 | help | ||
1331 | You can set here the default compression mode of JFFS2 from | ||
1332 | the available compression modes. Don't touch if unsure. | ||
1333 | |||
1334 | config JFFS2_CMODE_NONE | ||
1335 | bool "no compression" | ||
1336 | help | ||
1337 | Uses no compression. | ||
1338 | |||
1339 | config JFFS2_CMODE_PRIORITY | ||
1340 | bool "priority" | ||
1341 | help | ||
1342 | Tries the compressors in a predefined order and chooses the first | ||
1343 | successful one. | ||
1344 | |||
1345 | config JFFS2_CMODE_SIZE | ||
1346 | bool "size (EXPERIMENTAL)" | ||
1347 | help | ||
1348 | Tries all compressors and chooses the one which has the smallest | ||
1349 | result. | ||
1350 | |||
1351 | config JFFS2_CMODE_FAVOURLZO | ||
1352 | bool "Favour LZO" | ||
1353 | help | ||
1354 | Tries all compressors and chooses the one which has the smallest | ||
1355 | result but gives some preference to LZO (which has faster | ||
1356 | decompression) at the expense of size. | ||
1357 | |||
1358 | endchoice | ||
1359 | |||
1360 | # UBIFS File system configuration | 910 | # UBIFS File system configuration |
1361 | source "fs/ubifs/Kconfig" | 911 | source "fs/ubifs/Kconfig" |
1362 | 912 | ||
@@ -1913,148 +1463,7 @@ config SMB_NLS_REMOTE | |||
1913 | 1463 | ||
1914 | smbmount from samba 2.2.0 or later supports this. | 1464 | smbmount from samba 2.2.0 or later supports this. |
1915 | 1465 | ||
1916 | config CIFS | 1466 | source "fs/cifs/Kconfig" |
1917 | tristate "CIFS support (advanced network filesystem, SMBFS successor)" | ||
1918 | depends on INET | ||
1919 | select NLS | ||
1920 | help | ||
1921 | This is the client VFS module for the Common Internet File System | ||
1922 | (CIFS) protocol which is the successor to the Server Message Block | ||
1923 | (SMB) protocol, the native file sharing mechanism for most early | ||
1924 | PC operating systems. The CIFS protocol is fully supported by | ||
1925 | file servers such as Windows 2000 (including Windows 2003, NT 4 | ||
1926 | and Windows XP) as well by Samba (which provides excellent CIFS | ||
1927 | server support for Linux and many other operating systems). Limited | ||
1928 | support for OS/2 and Windows ME and similar servers is provided as | ||
1929 | well. | ||
1930 | |||
1931 | The cifs module provides an advanced network file system | ||
1932 | client for mounting to CIFS compliant servers. It includes | ||
1933 | support for DFS (hierarchical name space), secure per-user | ||
1934 | session establishment via Kerberos or NTLM or NTLMv2, | ||
1935 | safe distributed caching (oplock), optional packet | ||
1936 | signing, Unicode and other internationalization improvements. | ||
1937 | If you need to mount to Samba or Windows from this machine, say Y. | ||
1938 | |||
1939 | config CIFS_STATS | ||
1940 | bool "CIFS statistics" | ||
1941 | depends on CIFS | ||
1942 | help | ||
1943 | Enabling this option will cause statistics for each server share | ||
1944 | mounted by the cifs client to be displayed in /proc/fs/cifs/Stats | ||
1945 | |||
1946 | config CIFS_STATS2 | ||
1947 | bool "Extended statistics" | ||
1948 | depends on CIFS_STATS | ||
1949 | help | ||
1950 | Enabling this option will allow more detailed statistics on SMB | ||
1951 | request timing to be displayed in /proc/fs/cifs/DebugData and also | ||
1952 | allow optional logging of slow responses to dmesg (depending on the | ||
1953 | value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details). | ||
1954 | These additional statistics may have a minor effect on performance | ||
1955 | and memory utilization. | ||
1956 | |||
1957 | Unless you are a developer or are doing network performance analysis | ||
1958 | or tuning, say N. | ||
1959 | |||
1960 | config CIFS_WEAK_PW_HASH | ||
1961 | bool "Support legacy servers which use weaker LANMAN security" | ||
1962 | depends on CIFS | ||
1963 | help | ||
1964 | Modern CIFS servers including Samba and most Windows versions | ||
1965 | (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos) | ||
1966 | security mechanisms. These hash the password more securely | ||
1967 | than the mechanisms used in the older LANMAN version of the | ||
1968 | SMB protocol but LANMAN based authentication is needed to | ||
1969 | establish sessions with some old SMB servers. | ||
1970 | |||
1971 | Enabling this option allows the cifs module to mount to older | ||
1972 | LANMAN based servers such as OS/2 and Windows 95, but such | ||
1973 | mounts may be less secure than mounts using NTLM or more recent | ||
1974 | security mechanisms if you are on a public network. Unless you | ||
1975 | have a need to access old SMB servers (and are on a private | ||
1976 | network) you probably want to say N. Even if this support | ||
1977 | is enabled in the kernel build, LANMAN authentication will not be | ||
1978 | used automatically. At runtime LANMAN mounts are disabled but | ||
1979 | can be set to required (or optional) either in | ||
1980 | /proc/fs/cifs (see fs/cifs/README for more detail) or via an | ||
1981 | option on the mount command. This support is disabled by | ||
1982 | default in order to reduce the possibility of a downgrade | ||
1983 | attack. | ||
1984 | |||
1985 | If unsure, say N. | ||
1986 | |||
1987 | config CIFS_UPCALL | ||
1988 | bool "Kerberos/SPNEGO advanced session setup" | ||
1989 | depends on CIFS && KEYS | ||
1990 | help | ||
1991 | Enables an upcall mechanism for CIFS which accesses | ||
1992 | userspace helper utilities to provide SPNEGO packaged (RFC 4178) | ||
1993 | Kerberos tickets which are needed to mount to certain secure servers | ||
1994 | (for which more secure Kerberos authentication is required). If | ||
1995 | unsure, say N. | ||
1996 | |||
1997 | config CIFS_XATTR | ||
1998 | bool "CIFS extended attributes" | ||
1999 | depends on CIFS | ||
2000 | help | ||
2001 | Extended attributes are name:value pairs associated with inodes by | ||
2002 | the kernel or by users (see the attr(5) manual page, or visit | ||
2003 | <http://acl.bestbits.at/> for details). CIFS maps the name of | ||
2004 | extended attributes beginning with the user namespace prefix | ||
2005 | to SMB/CIFS EAs. EAs are stored on Windows servers without the | ||
2006 | user namespace prefix, but their names are seen by Linux cifs clients | ||
2007 | prefaced by the user namespace prefix. The system namespace | ||
2008 | (used by some filesystems to store ACLs) is not supported at | ||
2009 | this time. | ||
2010 | |||
2011 | If unsure, say N. | ||
2012 | |||
2013 | config CIFS_POSIX | ||
2014 | bool "CIFS POSIX Extensions" | ||
2015 | depends on CIFS_XATTR | ||
2016 | help | ||
2017 | Enabling this option will cause the cifs client to attempt to | ||
2018 | negotiate a newer dialect with servers, such as Samba 3.0.5 | ||
2019 | or later, that optionally can handle more POSIX like (rather | ||
2020 | than Windows like) file behavior. It also enables | ||
2021 | support for POSIX ACLs (getfacl and setfacl) to servers | ||
2022 | (such as Samba 3.10 and later) which can negotiate | ||
2023 | CIFS POSIX ACL support. If unsure, say N. | ||
2024 | |||
2025 | config CIFS_DEBUG2 | ||
2026 | bool "Enable additional CIFS debugging routines" | ||
2027 | depends on CIFS | ||
2028 | help | ||
2029 | Enabling this option adds a few more debugging routines | ||
2030 | to the cifs code which slightly increases the size of | ||
2031 | the cifs module and can cause additional logging of debug | ||
2032 | messages in some error paths, slowing performance. This | ||
2033 | option can be turned off unless you are debugging | ||
2034 | cifs problems. If unsure, say N. | ||
2035 | |||
2036 | config CIFS_EXPERIMENTAL | ||
2037 | bool "CIFS Experimental Features (EXPERIMENTAL)" | ||
2038 | depends on CIFS && EXPERIMENTAL | ||
2039 | help | ||
2040 | Enables cifs features under testing. These features are | ||
2041 | experimental and currently include DFS support and directory | ||
2042 | change notification ie fcntl(F_DNOTIFY), as well as the upcall | ||
2043 | mechanism which will be used for Kerberos session negotiation | ||
2044 | and uid remapping. Some of these features also may depend on | ||
2045 | setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental | ||
2046 | (which is disabled by default). See the file fs/cifs/README | ||
2047 | for more details. If unsure, say N. | ||
2048 | |||
2049 | config CIFS_DFS_UPCALL | ||
2050 | bool "DFS feature support (EXPERIMENTAL)" | ||
2051 | depends on CIFS_EXPERIMENTAL | ||
2052 | depends on KEYS | ||
2053 | help | ||
2054 | Enables an upcall mechanism for CIFS which contacts userspace | ||
2055 | helper utilities to provide server name resolution (host names to | ||
2056 | IP addresses) which is needed for implicit mounts of DFS junction | ||
2057 | points. If unsure, say N. | ||
2058 | 1467 | ||
2059 | config NCP_FS | 1468 | config NCP_FS |
2060 | tristate "NCP file system support (to mount NetWare volumes)" | 1469 | tristate "NCP file system support (to mount NetWare volumes)" |