menu "Ubuntu added filesystem drivers"

config ASFS_FS
	tristate "Amiga SFS file system support (EXPERIMENTAL)"
	select NLS
	depends on EXPERIMENTAL
	help

	  The Amiga Smart FileSystem (SFS) is the file system used on hard 
	  disks by Amiga(tm) and MorphOS(tm) systems.  Say Y if you want 
	  to be able to read files from an Amiga SFS partition on your hard 
	  drive.

	  For more information read <file:Documentation/filesystems/asfs.txt>

	  To compile this file system support as a module, choose M here: the
	  module will be called asfs.

	  If unsure, say N.

config ASFS_DEFAULT_CODEPAGE
	string "Default codepage for SFS"
	depends on ASFS_FS
	default ""
	help
	  This option should be set to the codepage of your SFS filesystems.
	  It can be overridden with the 'codepage' mount option. Leave it blank 
	  or enter 'none' to disable filename converting.

	  Use full codepage name (for example 'cp1251' instead of '1251') here, 
	  this allows to specify any character set, not only numbered one (like 
	  'iso8859-2').

	  If unsure, leave it blank.

config ASFS_RW
	bool "Amiga SFS write support (DANGEROUS)"
	depends on ASFS_FS
	help

	  If you say Y here, you will be able to write to ASFS file
	  systems as well as read from them. The read-write support in ASFS
	  is in beta stage. This means that useing it to write files to SFS 
	  partitions is DANGEROUS and COULD corrupt the filesystem.

	  For more information read <file:Documentation/filesystems/asfs.txt>

	  If unsure, say N.

config DAZUKO
	tristate "Dazuko File Access Control"
	default n
	---help---
	  This project provides a device driver allowing 3rd-party
	  (userland) applications to execute file access control. It was
	  originally developed by Avira GmbH (formerly known as H+BEDV
	  Datentechnik GmbH) to allow on-access virus scanning. Other uses
	  include a file-access monitor/logger or external security
	  implementations. It operates by intercepting file access calls
	  and passing the file information to a 3rd-party application. The
	  3rd-party application then has the opportunity to tell the
	  device driver to allow or deny the file access. The 3rd-party
	  application also receives information about the access event,
	  such as accessed file, type of access, process id, and user id.

	  If unsure, say N. Compiling this as a module is a good idea though.

config SQUASHFS
	tristate "SquashFS 3.2 - Squashed file system support"
	select ZLIB_INFLATE
	help

	  Saying Y here includes support for SquashFS 3.2 (a Compressed
	  Read-Only File System).  Squashfs is a highly compressed read-only
	  filesystem for Linux.  It uses zlib compression to compress both
	  files, inodes and directories.  Inodes in the system are very small
	  and all blocks are packed to minimise data overhead. Block sizes
	  greater than 4K are supported up to a maximum of 64K.  SquashFS 3.2
	  supports 64 bit filesystems and files (larger than 4GB), full uid/gid
	  information, hard links and timestamps.

	  Squashfs is intended for general read-only filesystem use, for
	  archival use (i.e. in cases where a .tar.gz file may be used), and
	  in embedded systems where low overhead is needed.  Further
	  information and filesystem tools are available from
	  http://squashfs.sourceforge.net.

	  If you want to compile this as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/modules.txt>.  The module
	  will be called squashfs.  Note that the root file system (the one
	  containing the directory /) cannot be compiled as a module.

	  If unsure, say N.

config SQUASHFS_EMBEDDED

	bool "Additional options for memory-constrained systems" 
	depends on SQUASHFS
	default n
	help
	  Saying Y here allows you to specify cache sizes and how Squashfs
	  allocates memory.  This is only intended for memory constrained
	  systems.

	  If unsure, say N.

config SQUASHFS_FRAGMENT_CACHE_SIZE
	int "Number of fragments cached" if SQUASHFS_EMBEDDED
	depends on SQUASHFS
	default "3"
	help
	  By default SquashFS caches the last 3 fragments read from
	  the filesystem.  Increasing this amount may mean SquashFS
	  has to re-read fragments less often from disk, at the expense
	  of extra system memory.  Decreasing this amount will mean
	  SquashFS uses less memory at the expense of extra reads from disk.

	  Note there must be at least one cached fragment.  Anything
	  much more than three will probably not make much difference.

config SQUASHFS_VMALLOC
	bool "Use Vmalloc rather than Kmalloc" if SQUASHFS_EMBEDDED
	depends on SQUASHFS
	default n
	help
	  By default SquashFS uses kmalloc to obtain fragment cache memory.
	  Kmalloc memory is the standard kernel allocator, but it can fail
	  on memory constrained systems.  Because of the way Vmalloc works,
	  Vmalloc can succeed when kmalloc fails.  Specifying this option
	  will make SquashFS always use Vmalloc to allocate the
	  fragment cache memory.

	  If unsure, say N.

config UNION_FS
	tristate "Union fs support"
	depends on EXPERIMENTAL
	help
	  Unionfs is a stackable unification file system, which can
	  appear to merge the contents of several directories (branches),
	  while keeping their physical content separate.

	  see <http://www.fsl.cs.sunysb.edu/project-unionfs.html> for details

source "ubuntu/fs/gfs/Kconfig"

endmenu
