807185eb3e
Given that CUSE depends on FUSE, it only makes sense to move its Kconfig entry into the FUSE Kconfig file. Also, add a few grammatical and semantic touchups. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
27 lines
956 B
Text
27 lines
956 B
Text
config FUSE_FS
|
|
tristate "FUSE (Filesystem in Userspace) support"
|
|
help
|
|
With FUSE it is possible to implement a fully functional filesystem
|
|
in a userspace program.
|
|
|
|
There's also a companion library: libfuse2. This library is available
|
|
from the FUSE homepage:
|
|
<http://fuse.sourceforge.net/>
|
|
although chances are your distribution already has that library
|
|
installed if you've installed the "fuse" package itself.
|
|
|
|
See <file:Documentation/filesystems/fuse.txt> for more information.
|
|
See <file:Documentation/Changes> for needed library/utility version.
|
|
|
|
If you want to develop a userspace FS, or if you want to use
|
|
a filesystem based on FUSE, answer Y or M.
|
|
|
|
config CUSE
|
|
tristate "Character device in Userspace support"
|
|
depends on FUSE_FS
|
|
help
|
|
This FUSE extension allows character devices to be
|
|
implemented in userspace.
|
|
|
|
If you want to develop or use a userspace character device
|
|
based on CUSE, answer Y or M.
|