| Linus Torvalds | a2225d9 | 2018-06-11 08:22:34 -0700 | [diff] [blame^] | 1 | config AUTOFS4_FS |
| 2 | tristate "Old Kconfig name for Kernel automounter support" |
| 3 | select AUTOFS_FS |
| 4 | help |
| 5 | This name exists for people to just automatically pick up the |
| 6 | new name of the autofs Kconfig option. All it does is select |
| 7 | thenew new option name. |
| 8 | |
| 9 | It will go away in a release or two as people have |
| 10 | transitioned to just plain AUTOFS_FS. |
| 11 | |
| Ian Kent | 2a3ae0a | 2018-06-07 17:11:31 -0700 | [diff] [blame] | 12 | config AUTOFS_FS |
| 13 | tristate "Kernel automounter support (supports v3, v4 and v5)" |
| 14 | default n |
| 15 | help |
| 16 | The automounter is a tool to automatically mount remote file systems |
| 17 | on demand. This implementation is partially kernel-based to reduce |
| 18 | overhead in the already-mounted case; this is unlike the BSD |
| 19 | automounter (amd), which is a pure user space daemon. |
| 20 | |
| 21 | To use the automounter you need the user-space tools from |
| 22 | <https://www.kernel.org/pub/linux/daemons/autofs/>; you also want |
| 23 | to answer Y to "NFS file system support", below. |
| 24 | |
| 25 | To compile this support as a module, choose M here: the module will be |
| 26 | called autofs. |
| 27 | |
| 28 | If you are not a part of a fairly large, distributed network or |
| 29 | don't have a laptop which needs to dynamically reconfigure to the |
| 30 | local network, you probably do not need an automounter, and can say |
| 31 | N here. |