nuttx/fs/Kconfig

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#

comment "File system configuration"

config DISABLE_MOUNTPOINT
	bool "Disable support for mount points"
	default n

config FS_AUTOMOUNTER
	bool "Auto-mounter"
	default n
	depends on !DISABLE_MOUNTPOINT
	select SCHED_LPWORK
	---help---
		The automounter provides an OS-internal mechanism for automatically
		mounting and unmounting removable media as the media is inserted and
		removed.  See include/nuttx/fs/automout.h for interfacing details.

config FS_AUTOMOUNTER_DEBUG
	bool "Auto-mounter debug"
	default n
	depends on FS_AUTOMOUNTER && DEBUG_FEATURES
	---help---
		Normally, the auto-mounter will generate debug output when sub-system
		level file system debug is enabled.  This option will select debug
		output from the logic related to the auto-mount feature even when file
		system debug is not enable.  This is useful primarily for in vivo
		unit testing of the auto-mount feature.

config DISABLE_PSEUDOFS_OPERATIONS
	bool "Disable pseudo-filesystem operations"
	default y if DEFAULT_SMALL
	default n if !DEFAULT_SMALL
	---help---
		Disable certain operations on pseudo-file systems include mkdir,
		rmdir, unlink, and rename.  These are necessary for the logical
		completeness of the illusion created by the pseudo-filesystem.
		However, in practical embedded system, they are seldom needed and
		you can save a little FLASH space by disabling the capability.

config PSEUDOFS_SOFTLINKS
	bool "Pseudo-filesystem soft links"
	default n
	depends on !DISABLE_PSEUDOFS_OPERATIONS
	---help---
		Enable support for soft links in the pseudeo file system.  Soft
		links are not supported within mounted volumes by any NuttX file
		system.  However, if this option is selected, then soft links
		may be add in the pseudo file system.  This might be useful, for
		to link a directory in the pseudo-file system, such as /bin, to
		to a directory in a mounted volume, say /mnt/sdcard/bin.

config FS_READABLE
	bool
	default n
	---help---
		Automatically selected if any readable file system is selected

config FS_WRITABLE
	bool "Writable file system"
	default n
	---help---
		Automatically selected if any writable file system is selected.  If
		not selected, support for writing will be disabled in all block
		drivers and also the block-to-character (BCH) layer and the MTD FTL
		layer.

		This selection can also be manually selected.  You might want to do
		this if there are no writable file systems enabled, but you still
		want support for write access in block drivers and/or FTL.

source fs/aio/Kconfig
source fs/semaphore/Kconfig
source fs/mqueue/Kconfig
source fs/shm/Kconfig
source fs/mmap/Kconfig
source fs/fat/Kconfig
source fs/nfs/Kconfig
source fs/nxffs/Kconfig
source fs/romfs/Kconfig
source fs/cromfs/Kconfig
source fs/tmpfs/Kconfig
source fs/smartfs/Kconfig
source fs/binfs/Kconfig
source fs/procfs/Kconfig
source fs/unionfs/Kconfig
source fs/userfs/Kconfig
source fs/hostfs/Kconfig
Adding skeleton Kconfig files (part 1 of 2) git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4564 42af7a65-404d-4744-a932-0658087f49c3 2012-04-06 17:49:35 +02:00			`#`
			`# For a description of the syntax of this configuration file,`
Fix references to the no-longer-existent misc/ directory in comments, README files, and documentation 2015-06-28 16:08:57 +02:00			`# see the file kconfig-language.txt in the NuttX tools repository.`
Adding skeleton Kconfig files (part 1 of 2) git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4564 42af7a65-404d-4744-a932-0658087f49c3 2012-04-06 17:49:35 +02:00			`#`
A little bit of file system configuration logic git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4586 42af7a65-404d-4744-a932-0658087f49c3 2012-04-11 01:01:40 +02:00
			`comment "File system configuration"`
Kconfig updates git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4608 42af7a65-404d-4744-a932-0658087f49c3 2012-04-14 20:01:45 +02:00
apps/examples/nettest and poll: Complete Kconfig files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5556 42af7a65-404d-4744-a932-0658087f49c3 2013-01-24 17:28:15 +01:00			`config DISABLE_MOUNTPOINT`
			`bool "Disable support for mount points"`
			`default n`

Add support for an automounter that will automatically mount and unmount a file system a media is inserted and removed 2014-07-29 20:50:08 +02:00			`config FS_AUTOMOUNTER`
			`bool "Auto-mounter"`
			`default n`
			`depends on !DISABLE_MOUNTPOINT`
FS_AUTOMOUNTER should depend on SCHED_LPWORK 2017-08-26 19:54:03 +02:00			`select SCHED_LPWORK`
Add support for an automounter that will automatically mount and unmount a file system a media is inserted and removed 2014-07-29 20:50:08 +02:00			`---help---`
			`The automounter provides an OS-internal mechanism for automatically`
			`mounting and unmounting removable media as the media is inserted and`
			`removed. See include/nuttx/fs/automout.h for interfacing details.`

			`config FS_AUTOMOUNTER_DEBUG`
			`bool "Auto-mounter debug"`
			`default n`
Rename CONFIG_DEBUG to CONFIG_DEBUG_FEATURES 2016-06-11 22:14:08 +02:00			`depends on FS_AUTOMOUNTER && DEBUG_FEATURES`
Add support for an automounter that will automatically mount and unmount a file system a media is inserted and removed 2014-07-29 20:50:08 +02:00			`---help---`
			`Normally, the auto-mounter will generate debug output when sub-system`
			`level file system debug is enabled. This option will select debug`
			`output from the logic related to the auto-mount feature even when file`
			`system debug is not enable. This is useful primarily for in vivo`
			`unit testing of the auto-mount feature.`

unlink/rm can now be used on nodes in the pseudo-filesystem. There is new configuration option to suppress these costly and mostly useless operations on the pseudo-filesystem 2014-02-21 01:14:02 +01:00			`config DISABLE_PSEUDOFS_OPERATIONS`
Add CONFIG_DEFAULT_SMALL that will select default values for configuration settings based upon either more features or smaller footprint. Turns out not be be useful for modifying existing defconfig files because the defaults do not apply in that case 2014-02-21 01:49:45 +01:00			`bool "Disable pseudo-filesystem operations"`
			`default y if DEFAULT_SMALL`
			`default n if !DEFAULT_SMALL`
unlink/rm can now be used on nodes in the pseudo-filesystem. There is new configuration option to suppress these costly and mostly useless operations on the pseudo-filesystem 2014-02-21 01:14:02 +01:00			`---help---`
			`Disable certain operations on pseudo-file systems include mkdir,`
			`rmdir, unlink, and rename. These are necessary for the logical`
			`completeness of the illusion created by the pseudo-filesystem.`
			`However, in practical embedded system, they are seldom needed and`
			`you can save a little FLASH space by disabling the capability.`

Soft links: Initial, incompete implementation 2017-02-02 17:39:41 +01:00			`config PSEUDOFS_SOFTLINKS`
			`bool "Pseudo-filesystem soft links"`
Soft links: Fix compile problems on first build with soft links enabled. 2017-02-02 22:24:39 +01:00			`default n`
Soft links: Eliminate in-stack allocation of path working buffer needed for traversal fo paths with soft links. 2017-02-05 21:57:38 +01:00			`depends on !DISABLE_PSEUDOFS_OPERATIONS`
Soft links: Initial, incompete implementation 2017-02-02 17:39:41 +01:00			`---help---`
			`Enable support for soft links in the pseudeo file system. Soft`
			`links are not supported within mounted volumes by any NuttX file`
			`system. However, if this option is selected, then soft links`
			`may be add in the pseudo file system. This might be useful, for`
			`to link a directory in the pseudo-file system, such as /bin, to`
			`to a directory in a mounted volume, say /mnt/sdcard/bin.`

Alloc CONFIG_FS_READABLE/WRITABLE to be defined in Kconfig files while preserving backward compatibility with legacy configurations (for the time being) 2013-11-15 16:49:27 +01:00			`config FS_READABLE`
			`bool`
			`default n`
fs/Kconfig: Allow CONFIG_FS_WRITABLE to be manually selected 2016-05-11 17:52:32 +02:00			`---help---`
			`Automatically selected if any readable file system is selected`
Alloc CONFIG_FS_READABLE/WRITABLE to be defined in Kconfig files while preserving backward compatibility with legacy configurations (for the time being) 2013-11-15 16:49:27 +01:00
			`config FS_WRITABLE`
fs/Kconfig: Allow CONFIG_FS_WRITABLE to be manually selected 2016-05-11 17:52:32 +02:00			`bool "Writable file system"`
Alloc CONFIG_FS_READABLE/WRITABLE to be defined in Kconfig files while preserving backward compatibility with legacy configurations (for the time being) 2013-11-15 16:49:27 +01:00			`default n`
fs/Kconfig: Allow CONFIG_FS_WRITABLE to be manually selected 2016-05-11 17:52:32 +02:00			`---help---`
Improve some Kconfig help comments 2016-05-11 17:54:33 +02:00			`Automatically selected if any writable file system is selected. If`
Remove CONFIG_FS_READABLE/WRITABLE logic from tools/mkconfig.c. This logic has been replaced with proper logic in the Kconfig files, it is out of date and an ongoing maintenance problem, and it shoulw not be necessary. 2016-05-11 18:01:43 +02:00			`not selected, support for writing will be disabled in all block`
			`drivers and also the block-to-character (BCH) layer and the MTD FTL`
			`layer.`
fs/Kconfig: Allow CONFIG_FS_WRITABLE to be manually selected 2016-05-11 17:52:32 +02:00
			`This selection can also be manually selected. You might want to do`
			`this if there are no writable file systems enabled, but you still`
			`want support for write access in block drivers and/or FTL.`
Alloc CONFIG_FS_READABLE/WRITABLE to be defined in Kconfig files while preserving backward compatibility with legacy configurations (for the time being) 2013-11-15 16:49:27 +01:00
Move all file operations from libc/aio to fs/aio. These will need to be kernel routines in order to handler issues with using file descriptors on worker thread 2014-10-05 23:33:31 +02:00			`source fs/aio/Kconfig`
Create a build structure that will (eventually) support using the VFS to manage named semaphores 2014-09-28 20:19:01 +02:00			`source fs/semaphore/Kconfig`
Add a framework that may someday support shared memory objects in the VFS 2014-09-30 00:46:31 +02:00			`source fs/mqueue/Kconfig`
			`source fs/shm/Kconfig`
A little bit of file system configuration logic git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4586 42af7a65-404d-4744-a932-0658087f49c3 2012-04-11 01:01:40 +02:00			`source fs/mmap/Kconfig`
apps/builtin/binfs.c moved to nuttx/fs/binfs/fs_binfs.c git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5523 42af7a65-404d-4744-a932-0658087f49c3 2013-01-16 16:41:27 +01:00			`source fs/fat/Kconfig`
A little bit of file system configuration logic git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4586 42af7a65-404d-4744-a932-0658087f49c3 2012-04-11 01:01:40 +02:00			`source fs/nfs/Kconfig`
			`source fs/nxffs/Kconfig`
The initial SYLOG device logic was valiant but yet still not enough git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4998 42af7a65-404d-4744-a932-0658087f49c3 2012-08-02 19:09:25 +02:00			`source fs/romfs/Kconfig`
Addes CROMFS prototype. CROMFS is a commpressed, in-memory read-only file system based on LZF. Squashed commit of the following: fs/cromfs: Now depends on EXPERIMENTAL because it is not yet verified. fs/cromfs: This commit brings the CROMFS file system to code complete. Still completely untested. Next steps: Need a tool to generate CROMFS file system images and a test case under apps/ fs/cromfs: Add logic to traverse the in-memory file system nodes. fs/cromfs: Add initial support for an in-memory, compressed, read-only file system. 2018-03-19 14:08:40 +01:00			`source fs/cromfs/Kconfig`
TMPFS: Code complete, but not yet functional 2015-10-09 19:02:59 +02:00			`source fs/tmpfs/Kconfig`
Add Ken Pettit's SMART FS 2013-05-01 04:13:30 +02:00			`source fs/smartfs/Kconfig`
apps/builtin/binfs.c moved to nuttx/fs/binfs/fs_binfs.c git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5523 42af7a65-404d-4744-a932-0658087f49c3 2013-01-16 16:41:27 +01:00			`source fs/binfs/Kconfig`
fs/procfs: Add a tiny, primitive procfs file system. Might get more interesting in the future 2013-11-13 22:59:14 +01:00			`source fs/procfs/Kconfig`
Add support for a union file system that can be used to overlay and merge the content of two mounted file systems. 2015-06-05 21:18:06 +02:00			`source fs/unionfs/Kconfig`
Squashed commit of the following: fs/userfs: This completes coding of the UserFS client and of the UserFS feature in general. This feature is being merged to main now because I believe it is innocuous. It is, however, untesed. The next step will be to develop a test case to verify the feature. fs/userfs: Completes the request logic for the UserFS client. Still need the logic that receives the responses. fs/userfs: Completes coding for most of the server side of the user filesystem logic. fs/userfs: Big design changes, simplications. Use Unix domain local sockets instead of message queues. Easier to transfer big data in local sockets than message queues. Remove character drvier 'factory' it is not necessary. fs/userfs: Minor reparitioning; volume private info does not need to be held on the OS client side. libc/userfs: Add some of the server side logic. fs/userfs: Add some UserFS initialization logic. fs/userfs: Add frame work for the UserFS proxy. Remove all references to a block driver. There is no block dricer... what was I thinking? fs/userfs: Add some initialization of the character driver, 'factory' device. fs/userfs: Rename from fusefs to userfs to that we don't stomp on someone else's cool name. Add a header file describing the fusefs interface. 2017-10-31 01:04:28 +01:00			`source fs/userfs/Kconfig`
fs/hostfs: Add a special file system for use with simulator that supports access to the host file system from the simulation. From Ken Petit 2015-11-25 15:26:26 +01:00			`source fs/hostfs/Kconfig`