1 # This file is part of the OpenADK project. OpenADK is copyrighted
2 # material, please see the LICENCE file in the top-level directory.
4 menu "Network filesystems"
6 config ADK_KERNEL_FS_POSIX_ACL
10 tristate "CIFS support"
11 select ADK_KERNEL_NETWORK_FILESYSTEMS
12 select ADK_KERNEL_CRYPTO_MD4
13 select ADK_KERNEL_CRYPTO_MD5
14 select ADK_KERNEL_CRYPTO_HMAC
15 select ADK_KERNEL_CRYPTO_ARC4
16 select ADK_KERNEL_CRYPTO_ECB
17 select ADK_KERNEL_CRYPTO_DES
18 select ADK_KERNEL_CRYPTO_SHA256
19 select ADK_KERNEL_NLS_UTF8
21 This is the client VFS module for the Common Internet File System
22 (CIFS) protocol which is the successor to the Server Message Block
23 (SMB) protocol, the native file sharing mechanism for most early
24 PC operating systems. The CIFS protocol is fully supported by
25 file servers such as Windows 2000 (including Windows 2003, NT 4
26 and Windows XP) as well by Samba (which provides excellent CIFS
27 server support for Linux and many other operating systems). Limited
28 support for Windows ME and similar servers is provided as well.
29 You must use the smbfs client filesystem to access older SMB servers
32 The intent of the cifs module is to provide an advanced
33 network file system client for mounting to CIFS compliant servers,
34 including support for dfs (hierarchical name space), secure per-user
35 session establishment, safe distributed caching (oplock), optional
36 packet signing, Unicode and other internationalization improvements,
37 and optional Winbind (nsswitch) integration. You do not need to enable
38 cifs if running only a (Samba) server. It is possible to enable both
39 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
40 and Samba 3 servers, and smbfs for accessing old servers). If you need
41 to mount to Samba or Windows from this machine, say Y.
43 config ADK_KERNEL_CODA_FS
44 tristate "Support for CODA filesystem"
45 select ADK_KERNEL_NETWORK_FILESYSTEMS
47 This is the kernel part of the client for the CODA filesystem.
49 config ADK_KERNEL_NFS_V3
51 select ADK_KERNEL_NETWORK_FILESYSTEMS
53 config ADK_KERNEL_NFS_V4
55 select ADK_KERNEL_NETWORK_FILESYSTEMS
57 config ADK_KERNEL_NFS_FS
58 tristate "NFS client support"
59 select ADK_KERNEL_NFS_V3
60 select ADK_KERNEL_FILE_LOCKING
61 select ADK_KERNEL_DNOTIFY
62 select ADK_KERNEL_SUNRPC
63 select ADK_KERNEL_LOCKD
64 select ADK_KERNEL_NETWORK_FILESYSTEMS
66 If you are connected to some other (usually local) Unix computer
67 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
68 on that computer (the NFS server) using the Network File Sharing
69 protocol, say Y. "Mounting files" means that the client can access
70 the files with usual UNIX commands as if they were sitting on the
71 client's hard disk. For this to work, the server must run the
72 programs nfsd and mountd (but does not need to have NFS file system
73 support enabled in its kernel). NFS is explained in the Network
74 Administrator's Guide, available from
75 <http://www.tldp.org/docs.html#guide>, on its man page: "man
76 nfs", and in the NFS-HOWTO.
78 A superior but less widely used alternative to NFS is provided by
79 the Coda file system; see "Coda file system support" below.
81 If you say Y here, you should have said Y to TCP/IP networking also.
82 This option would enlarge your kernel by about 27 KB.
84 To compile this file system support as a module, choose M here: the
85 module will be called nfs.
87 If you are configuring a diskless machine which will mount its root
88 file system over NFS at boot time, say Y here and to "Kernel
89 level IP autoconfiguration" above and to "Root file system on NFS"
90 below. You cannot compile this driver as a module in this case.
91 There are two packages designed for booting diskless machines over
92 the net: netboot, available from
93 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
94 available from <http://ftp1.sourceforge.net/etherboot/>.
96 If you don't know what all this is about, say N.
97 Kernel modules for NFS client support
99 config ADK_KERNEL_NFSD_V3
102 config ADK_KERNEL_NFSD_V4
104 select ADK_KERNEL_SUNRPC_GSS
105 default y if ADK_PACKAGE_NFS_UTILS_V4
108 config ADK_KERNEL_NFSD
109 tristate "NFS server support"
110 select ADK_KERNEL_EXPORTFS
111 select ADK_KERNEL_NFSD_V3
112 select ADK_KERNEL_DNOTIFY
113 select ADK_KERNEL_FILE_LOCKING
114 select ADK_KERNEL_SUNRPC
115 select ADK_KERNEL_LOCKD
116 select ADK_KERNEL_NETWORK_FILESYSTEMS
118 If you want your Linux box to act as an NFS *server*, so that other
119 computers on your local network which support NFS can access certain
120 directories on your box transparently, you have two options: you can
121 use the self-contained user space program nfsd, in which case you
122 should say N here, or you can say Y and use the kernel based NFS
123 server. The advantage of the kernel based solution is that it is
126 In either case, you will need support software; the respective
127 locations are given in the file <file:Documentation/Changes> in the
130 If you say Y here, you will get support for version 2 of the NFS
131 protocol (NFSv2). If you also want NFSv3, say Y to the next question
134 Please read the NFS-HOWTO, available from
135 <http://www.tldp.org/docs.html#howto>.
137 config ADK_KERNEL_LOCKD
140 config ADK_KERNEL_SUNRPC
143 config ADK_KERNEL_SUNRPC_GSS
145 select ADK_KERNEL_SUNRPC
147 config ADK_KERNEL_RPCSEC_GSS_KRB5
148 tristate "RPC security support"
149 select ADK_KERNEL_NETWORK_FILESYSTEMS
150 select ADK_KERNEL_SUNRPC_GSS
151 select ADK_KERNEL_SUNRPC
152 select ADK_KERNEL_CRYPTO
153 select ADK_KERNEL_CRYPTO_MD5
154 select ADK_KERNEL_CRYPTO_DES
155 select ADK_KERNEL_CRYPTO_CBC
156 select ADK_KERNEL_CRYPTO_CTS
157 select ADK_KERNEL_CRYPTO_ECB
158 select ADK_KERNEL_CRYPTO_HMAC
159 select ADK_KERNEL_CRYPTO_SHA1
160 select ADK_KERNEL_CRYPTO_AES
161 select ADK_KERNEL_CRYPTO_ARC4