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