Subversion Repositories or1k_soc_on_altera_embedded_dev_kit

#

# File system configuration

#

menu "File systems"

if BLOCK

config EXT2_FS

        tristate "Second extended fs support"

        help

          Ext2 is a standard Linux file system for hard disks.

          To compile this file system support as a module, choose M here: the

          module will be called ext2.

          If unsure, say Y.

config EXT2_FS_XATTR

        bool "Ext2 extended attributes"

        depends on EXT2_FS

        help

          Extended attributes are name:value pairs associated with inodes by

          the kernel or by users (see the attr(5) manual page, or visit

           for details).

          If unsure, say N.

config EXT2_FS_POSIX_ACL

        bool "Ext2 POSIX Access Control Lists"

        depends on EXT2_FS_XATTR

        select FS_POSIX_ACL

        help

          Posix Access Control Lists (ACLs) support permissions for users and

          groups beyond the owner/group/world scheme.

          To learn more about Access Control Lists, visit the Posix ACLs for

          Linux website .

          If you don't know what Access Control Lists are, say N

config EXT2_FS_SECURITY

        bool "Ext2 Security Labels"

        depends on EXT2_FS_XATTR

        help

          Security labels support alternative access control models

          implemented by security modules like SELinux.  This option

          enables an extended attribute handler for file security

          labels in the ext2 filesystem.

          If you are not using a security module that requires using

          extended attributes for file security labels, say N.

config EXT2_FS_XIP

        bool "Ext2 execute in place support"

        depends on EXT2_FS && MMU

        help

          Execute in place can be used on memory-backed block devices. If you

          enable this option, you can select to mount block devices which are

          capable of this feature without using the page cache.

          If you do not use a block device that is capable of using this,

          or if unsure, say N.

config FS_XIP

# execute in place

        bool

        depends on EXT2_FS_XIP

        default y

config EXT3_FS

        tristate "Ext3 journalling file system support"

        select JBD

        help

          This is the journalling version of the Second extended file system

          (often called ext3), the de facto standard Linux file system

          (method to organize files on a storage device) for hard disks.

          The journalling code included in this driver means you do not have

          to run e2fsck (file system checker) on your file systems after a

          crash.  The journal keeps track of any changes that were being made

          at the time the system crashed, and can ensure that your file system

          is consistent without the need for a lengthy check.

          Other than adding the journal to the file system, the on-disk format

          of ext3 is identical to ext2.  It is possible to freely switch

          between using the ext3 driver and the ext2 driver, as long as the

          file system has been cleanly unmounted, or e2fsck is run on the file

          system.

          To add a journal on an existing ext2 file system or change the

          behavior of ext3 file systems, you can use the tune2fs utility ("man

          tune2fs").  To modify attributes of files and directories on ext3

          file systems, use chattr ("man chattr").  You need to be using

          e2fsprogs version 1.20 or later in order to create ext3 journals

          (available at ).

          To compile this file system support as a module, choose M here: the

          module will be called ext3.

config EXT3_FS_XATTR

        bool "Ext3 extended attributes"

        depends on EXT3_FS

        default y

        help

          Extended attributes are name:value pairs associated with inodes by

          the kernel or by users (see the attr(5) manual page, or visit

           for details).

          If unsure, say N.

          You need this for POSIX ACL support on ext3.

config EXT3_FS_POSIX_ACL

        bool "Ext3 POSIX Access Control Lists"

        depends on EXT3_FS_XATTR

        select FS_POSIX_ACL

        help

          Posix Access Control Lists (ACLs) support permissions for users and

          groups beyond the owner/group/world scheme.

          To learn more about Access Control Lists, visit the Posix ACLs for

          Linux website .

          If you don't know what Access Control Lists are, say N

config EXT3_FS_SECURITY

        bool "Ext3 Security Labels"

        depends on EXT3_FS_XATTR

        help

          Security labels support alternative access control models

          implemented by security modules like SELinux.  This option

          enables an extended attribute handler for file security

          labels in the ext3 filesystem.

          If you are not using a security module that requires using

          extended attributes for file security labels, say N.

config EXT4DEV_FS

        tristate "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)"

        depends on EXPERIMENTAL

        select JBD2

        select CRC16

        help

          Ext4dev is a predecessor filesystem of the next generation

          extended fs ext4, based on ext3 filesystem code. It will be

          renamed ext4 fs later, once ext4dev is mature and stabilized.

          Unlike the change from ext2 filesystem to ext3 filesystem,

          the on-disk format of ext4dev is not the same as ext3 any more:

          it is based on extent maps and it supports 48-bit physical block

          numbers. These combined on-disk format changes will allow

          ext4dev/ext4 to handle more than 16 TB filesystem volumes --

          a hard limit that ext3 cannot overcome without changing the

          on-disk format.

          Other than extent maps and 48-bit block numbers, ext4dev also is

          likely to have other new features such as persistent preallocation,

          high resolution time stamps, and larger file support etc.  These

          features will be added to ext4dev gradually.

          To compile this file system support as a module, choose M here. The

          module will be called ext4dev.

          If unsure, say N.

config EXT4DEV_FS_XATTR

        bool "Ext4dev extended attributes"

        depends on EXT4DEV_FS

        default y

        help

          Extended attributes are name:value pairs associated with inodes by

          the kernel or by users (see the attr(5) manual page, or visit

           for details).

          If unsure, say N.

          You need this for POSIX ACL support on ext4dev/ext4.

config EXT4DEV_FS_POSIX_ACL

        bool "Ext4dev POSIX Access Control Lists"

        depends on EXT4DEV_FS_XATTR

        select FS_POSIX_ACL

        help

          POSIX Access Control Lists (ACLs) support permissions for users and

          groups beyond the owner/group/world scheme.

          To learn more about Access Control Lists, visit the POSIX ACLs for

          Linux website .

          If you don't know what Access Control Lists are, say N

config EXT4DEV_FS_SECURITY

        bool "Ext4dev Security Labels"

        depends on EXT4DEV_FS_XATTR

        help

          Security labels support alternative access control models

          implemented by security modules like SELinux.  This option

          enables an extended attribute handler for file security

          labels in the ext4dev/ext4 filesystem.

          If you are not using a security module that requires using

          extended attributes for file security labels, say N.

config JBD

        tristate

        help

          This is a generic journalling layer for block devices.  It is

          currently used by the ext3 and OCFS2 file systems, but it could

          also be used to add journal support to other file systems or block

          devices such as RAID or LVM.

          If you are using the ext3 or OCFS2 file systems, you need to

          say Y here. If you are not using ext3 OCFS2 then you will probably

          want to say N.

          To compile this device as a module, choose M here: the module will be

          called jbd.  If you are compiling ext3 or OCFS2 into the kernel,

          you cannot compile this code as a module.

config JBD_DEBUG

        bool "JBD (ext3) debugging support"

        depends on JBD && DEBUG_FS

        help

          If you are using the ext3 journaled file system (or potentially any

          other file system/device using JBD), this option allows you to

          enable debugging output while the system is running, in order to

          help track down any problems you are having.  By default the

          debugging output will be turned off.

          If you select Y here, then you will be able to turn on debugging

          with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a

          number between 1 and 5, the higher the number, the more debugging

          output is generated.  To turn debugging off again, do

          "echo 0 > /sys/kernel/debug/jbd/jbd-debug".

config JBD2

        tristate

        help

          This is a generic journaling layer for block devices that support

          both 32-bit and 64-bit block numbers.  It is currently used by

          the ext4dev/ext4 filesystem, but it could also be used to add

          journal support to other file systems or block devices such

          as RAID or LVM.

          If you are using ext4dev/ext4, you need to say Y here. If you are not

          using ext4dev/ext4 then you will probably want to say N.

          To compile this device as a module, choose M here. The module will be

          called jbd2.  If you are compiling ext4dev/ext4 into the kernel,

          you cannot compile this code as a module.

config JBD2_DEBUG

        bool "JBD2 (ext4dev/ext4) debugging support"

        depends on JBD2 && DEBUG_FS

        help

          If you are using the ext4dev/ext4 journaled file system (or

          potentially any other filesystem/device using JBD2), this option

          allows you to enable debugging output while the system is running,

          in order to help track down any problems you are having.

          By default, the debugging output will be turned off.

          If you select Y here, then you will be able to turn on debugging

          with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a

          number between 1 and 5. The higher the number, the more debugging

          output is generated.  To turn debugging off again, do

          "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug".

config FS_MBCACHE

# Meta block cache for Extended Attributes (ext2/ext3/ext4)

        tristate

        depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4DEV_FS_XATTR

        default y if EXT2_FS=y || EXT3_FS=y || EXT4DEV_FS=y

        default m if EXT2_FS=m || EXT3_FS=m || EXT4DEV_FS=m

config REISERFS_FS

        tristate "Reiserfs support"

        help

          Stores not just filenames but the files themselves in a balanced

          tree.  Uses journalling.

          Balanced trees are more efficient than traditional file system

          architectural foundations.

          In general, ReiserFS is as fast as ext2, but is very efficient with

          large directories and small files.  Additional patches are needed

          for NFS and quotas, please see  for links.

          It is more easily extended to have features currently found in

          database and keyword search systems than block allocation based file

          systems are.  The next version will be so extended, and will support

          plugins consistent with our motto ``It takes more than a license to

          make source code open.''

          Read  to learn more about reiserfs.

          Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.

          If you like it, you can pay us to add new features to it that you

          need, buy a support contract, or pay us to port it to another OS.

config REISERFS_CHECK

        bool "Enable reiserfs debug mode"

        depends on REISERFS_FS

        help

          If you set this to Y, then ReiserFS will perform every check it can

          possibly imagine of its internal consistency throughout its

          operation.  It will also go substantially slower.  More than once we

          have forgotten that this was on, and then gone despondent over the

          latest benchmarks.:-) Use of this option allows our team to go all

          out in checking for consistency when debugging without fear of its

          effect on end users.  If you are on the verge of sending in a bug

          report, say Y and you might get a useful error message.  Almost

          everyone should say N.

config REISERFS_PROC_INFO

        bool "Stats in /proc/fs/reiserfs"

        depends on REISERFS_FS && PROC_FS

        help

          Create under /proc/fs/reiserfs a hierarchy of files, displaying

          various ReiserFS statistics and internal data at the expense of

          making your kernel or module slightly larger (+8 KB). This also

          increases the amount of kernel memory required for each mount.

          Almost everyone but ReiserFS developers and people fine-tuning

          reiserfs or tracing problems should say N.

config REISERFS_FS_XATTR

        bool "ReiserFS extended attributes"

        depends on REISERFS_FS

        help

          Extended attributes are name:value pairs associated with inodes by

          the kernel or by users (see the attr(5) manual page, or visit

           for details).

          If unsure, say N.

config REISERFS_FS_POSIX_ACL

        bool "ReiserFS POSIX Access Control Lists"

        depends on REISERFS_FS_XATTR

        select FS_POSIX_ACL

        help

          Posix Access Control Lists (ACLs) support permissions for users and

          groups beyond the owner/group/world scheme.

          To learn more about Access Control Lists, visit the Posix ACLs for

          Linux website .

          If you don't know what Access Control Lists are, say N

config REISERFS_FS_SECURITY

        bool "ReiserFS Security Labels"

        depends on REISERFS_FS_XATTR

        help

          Security labels support alternative access control models

          implemented by security modules like SELinux.  This option

          enables an extended attribute handler for file security

          labels in the ReiserFS filesystem.

          If you are not using a security module that requires using

          extended attributes for file security labels, say N.

config JFS_FS

        tristate "JFS filesystem support"

        select NLS

        help

          This is a port of IBM's Journaled Filesystem .  More information is

          available in the file .

          If you do not intend to use the JFS filesystem, say N.

config JFS_POSIX_ACL

        bool "JFS POSIX Access Control Lists"

        depends on JFS_FS

        select FS_POSIX_ACL

        help

          Posix Access Control Lists (ACLs) support permissions for users and

          groups beyond the owner/group/world scheme.

          To learn more about Access Control Lists, visit the Posix ACLs for

          Linux website .

          If you don't know what Access Control Lists are, say N

config JFS_SECURITY

        bool "JFS Security Labels"

        depends on JFS_FS

        help

          Security labels support alternative access control models

          implemented by security modules like SELinux.  This option

          enables an extended attribute handler for file security

          labels in the jfs filesystem.

          If you are not using a security module that requires using

          extended attributes for file security labels, say N.

config JFS_DEBUG

        bool "JFS debugging"

        depends on JFS_FS

        help

          If you are experiencing any problems with the JFS filesystem, say

          Y here.  This will result in additional debugging messages to be

          written to the system log.  Under normal circumstances, this

          results in very little overhead.

config JFS_STATISTICS

        bool "JFS statistics"

        depends on JFS_FS

        help

          Enabling this option will cause statistics from the JFS file system

          to be made available to the user in the /proc/fs/jfs/ directory.

config FS_POSIX_ACL

# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)

#

# NOTE: you can implement Posix ACLs without these helpers (XFS does).

#       Never use this symbol for ifdefs.

#

        bool

        default n

source "fs/xfs/Kconfig"

source "fs/gfs2/Kconfig"

config OCFS2_FS

        tristate "OCFS2 file system support"

        depends on NET && SYSFS

        select CONFIGFS_FS

        select JBD

        select CRC32

        help

          OCFS2 is a general purpose extent based shared disk cluster file

          system with many similarities to ext3. It supports 64 bit inode

          numbers, and has automatically extending metadata groups which may

          also make it attractive for non-clustered use.

          You'll want to install the ocfs2-tools package in order to at least

          get "mount.ocfs2".

          Project web page:    http://oss.oracle.com/projects/ocfs2

          Tools web page:      http://oss.oracle.com/projects/ocfs2-tools

          OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/

          Note: Features which OCFS2 does not support yet:

                  - extended attributes

                  - quotas

                  - cluster aware flock

                  - Directory change notification (F_NOTIFY)

                  - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)

                  - POSIX ACLs

                  - readpages / writepages (not user visible)

config OCFS2_DEBUG_MASKLOG

        bool "OCFS2 logging support"

        depends on OCFS2_FS

        default y

        help

          The ocfs2 filesystem has an extensive logging system.  The system

          allows selection of events to log via files in /sys/o2cb/logmask/.

          This option will enlarge your kernel, but it allows debugging of

          ocfs2 filesystem issues.

config OCFS2_DEBUG_FS

        bool "OCFS2 expensive checks"

        depends on OCFS2_FS

        default n

        help

          This option will enable expensive consistency checks. Enable

          this option for debugging only as it is likely to decrease

          performance of the filesystem.

config MINIX_FS

        tristate "Minix fs support"

        help

          Minix is a simple operating system used in many classes about OS's.

          The minix file system (method to organize files on a hard disk

          partition or a floppy disk) was the original file system for Linux,

          but has been superseded by the second extended file system ext2fs.

          You don't want to use the minix file system on your hard disk

          because of certain built-in restrictions, but it is sometimes found

          on older Linux floppy disks.  This option will enlarge your kernel

          by about 28 KB. If unsure, say N.

          To compile this file system support as a module, choose M here: the

          module will be called minix.  Note that the file system of your root

          partition (the one containing the directory /) cannot be compiled as

          a module.

config ROMFS_FS

        tristate "ROM file system support"

        ---help---

          This is a very small read-only file system mainly intended for

          initial ram disks of installation disks, but it could be used for

          other read-only media as well.  Read

           for details.

          To compile this file system support as a module, choose M here: the

          module will be called romfs.  Note that the file system of your

          root partition (the one containing the directory /) cannot be a

          module.

          If you don't know whether you need it, then you don't need it:

          answer N.

endif

config INOTIFY

        bool "Inotify file change notification support"

        default y

        ---help---

          Say Y here to enable inotify support.  Inotify is a file change

          notification system and a replacement for dnotify.  Inotify fixes

          numerous shortcomings in dnotify and introduces several new features

          including multiple file events, one-shot support, and unmount

          notification.

          For more information, see 

          If unsure, say Y.

config INOTIFY_USER

        bool "Inotify support for userspace"

        depends on INOTIFY

        default y

        ---help---

          Say Y here to enable inotify support for userspace, including the

          associated system calls.  Inotify allows monitoring of both files and

          directories via a single open fd.  Events are read from the file

          descriptor, which is also select()- and poll()-able.

          For more information, see 

          If unsure, say Y.

config QUOTA

        bool "Quota support"

        help

          If you say Y here, you will be able to set per user limits for disk

          usage (also called disk quotas). Currently, it works for the

          ext2, ext3, and reiserfs file system. ext3 also supports journalled

          quotas for which you don't need to run quotacheck(8) after an unclean

          shutdown.

          For further details, read the Quota mini-HOWTO, available from

          , or the documentation provided

          with the quota tools. Probably the quota support is only useful for

          multi user systems. If unsure, say N.

config QUOTA_NETLINK_INTERFACE

        bool "Report quota messages through netlink interface"

        depends on QUOTA && NET

        help

          If you say Y here, quota warnings (about exceeding softlimit, reaching

          hardlimit, etc.) will be reported through netlink interface. If unsure,

          say Y.

config PRINT_QUOTA_WARNING

        bool "Print quota warnings to console (OBSOLETE)"

        depends on QUOTA

        default y

        help

          If you say Y here, quota warnings (about exceeding softlimit, reaching

          hardlimit, etc.) will be printed to the process' controlling terminal.

          Note that this behavior is currently deprecated and may go away in

          future. Please use notification via netlink socket instead.

config QFMT_V1

        tristate "Old quota format support"

        depends on QUOTA

        help

          This quota format was (is) used by kernels earlier than 2.4.22. If

          you have quota working and you don't want to convert to new quota

          format say Y here.

config QFMT_V2

        tristate "Quota format v2 support"

        depends on QUOTA

        help

          This quota format allows using quotas with 32-bit UIDs/GIDs. If you

          need this functionality say Y here.

config QUOTACTL

        bool

        depends on XFS_QUOTA || QUOTA

        default y

config DNOTIFY

        bool "Dnotify support"

        default y

        help

          Dnotify is a directory-based per-fd file change notification system

          that uses signals to communicate events to user-space.  There exist

          superior alternatives, but some applications may still rely on

          dnotify.

          If unsure, say Y.

config AUTOFS_FS

        tristate "Kernel automounter support"

        help

          The automounter is a tool to automatically mount remote file systems

          on demand. This implementation is partially kernel-based to reduce

          overhead in the already-mounted case; this is unlike the BSD

          automounter (amd), which is a pure user space daemon.

          To use the automounter you need the user-space tools from the autofs

          package; you can find the location in .

          You also want to answer Y to "NFS file system support", below.

          If you want to use the newer version of the automounter with more

          features, say N here and say Y to "Kernel automounter v4 support",

          below.

          To compile this support as a module, choose M here: the module will be

          called autofs.

          If you are not a part of a fairly large, distributed network, you

          probably do not need an automounter, and can say N here.

config AUTOFS4_FS

        tristate "Kernel automounter version 4 support (also supports v3)"

        help

          The automounter is a tool to automatically mount remote file systems

          on demand. This implementation is partially kernel-based to reduce

          overhead in the already-mounted case; this is unlike the BSD

          automounter (amd), which is a pure user space daemon.

          To use the automounter you need the user-space tools from

          ; you also

          want to answer Y to "NFS file system support", below.

          To compile this support as a module, choose M here: the module will be

          called autofs4.  You will need to add "alias autofs autofs4" to your

          modules configuration file.

          If you are not a part of a fairly large, distributed network or

          don't have a laptop which needs to dynamically reconfigure to the

          local network, you probably do not need an automounter, and can say

          N here.

config FUSE_FS

        tristate "Filesystem in Userspace support"

        help

          With FUSE it is possible to implement a fully functional filesystem

          in a userspace program.

          There's also companion library: libfuse.  This library along with

          utilities is available from the FUSE homepage:

          See  for more information.

          See  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 GENERIC_ACL

        bool

        select FS_POSIX_ACL

if BLOCK

menu "CD-ROM/DVD Filesystems"

config ISO9660_FS

        tristate "ISO 9660 CDROM file system support"

        help

          This is the standard file system used on CD-ROMs.  It was previously

          known as "High Sierra File System" and is called "hsfs" on other

          Unix systems.  The so-called Rock-Ridge extensions which allow for

          long Unix filenames and symbolic links are also supported by this

          driver.  If you have a CD-ROM drive and want to do more with it than

          just listen to audio CDs and watch its LEDs, say Y (and read

           and the CD-ROM-HOWTO,

          available from ), thereby

          enlarging your kernel by about 27 KB; otherwise say N.

          To compile this file system support as a module, choose M here: the

          module will be called isofs.

config JOLIET

        bool "Microsoft Joliet CDROM extensions"

        depends on ISO9660_FS

        select NLS

        help

          Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system

          which allows for long filenames in unicode format (unicode is the

          new 16 bit character code, successor to ASCII, which encodes the

          characters of almost all languages of the world; see

           for more information).  Say Y here if you

          want to be able to read Joliet CD-ROMs under Linux.

config ZISOFS

        bool "Transparent decompression extension"

        depends on ISO9660_FS

        select ZLIB_INFLATE

        help

          This is a Linux-specific extension to RockRidge which lets you store

          data in compressed form on a CD-ROM and have it transparently

          decompressed when the CD-ROM is accessed.  See

           for the tools

          necessary to create such a filesystem.  Say Y here if you want to be

          able to read such compressed CD-ROMs.

config UDF_FS

        tristate "UDF file system support"

        help

          This is the new file system used on some CD-ROMs and DVDs. Say Y if

          you intend to mount DVD discs or CDRW's written in packet mode, or

          if written to by other UDF utilities, such as DirectCD.

          Please read .

          To compile this file system support as a module, choose M here: the

          module will be called udf.

          If unsure, say N.

config UDF_NLS

        bool

        default y

        depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)

endmenu

endif

if BLOCK

menu "DOS/FAT/NT Filesystems"

config FAT_FS

        tristate

        select NLS

        help

          If you want to use one of the FAT-based file systems (the MS-DOS and

          VFAT (Windows 95) file systems), then you must say Y or M here

          to include FAT support. You will then be able to mount partitions or

          diskettes with FAT-based file systems and transparently access the

          files on them, i.e. MSDOS files will look and behave just like all

          other Unix files.

          This FAT support is not a file system in itself, it only provides

          the foundation for the other file systems. You will have to say Y or

          M to at least one of "MSDOS fs support" or "VFAT fs support" in

          order to make use of it.

          Another way to read and write MSDOS floppies and hard drive

          partitions from within Linux (but not transparently) is with the

          mtools ("man mtools") program suite. You don't need to say Y here in

          order to do that.

          If you need to move large files on floppies between a DOS and a

          Linux box, say Y here, mount the floppy under Linux with an MSDOS

          file system and use GNU tar's M option. GNU tar is a program

          available for Unix and DOS ("man tar" or "info tar").

          The FAT support will enlarge your kernel by about 37 KB. If unsure,

          say Y.

          To compile this as a module, choose M here: the module will be called

          fat.  Note that if you compile the FAT support as a module, you

          cannot compile any of the FAT-based file systems into the kernel

          -- they will have to be modules as well.

config MSDOS_FS

        tristate "MSDOS fs support"

        select FAT_FS

        help

          This allows you to mount MSDOS partitions of your hard drive (unless

          they are compressed; to access compressed MSDOS partitions under

          Linux, you can either use the DOS emulator DOSEMU, described in the

          DOSEMU-HOWTO, available from

          , or try dmsdosfs in

          . If you

          intend to use dosemu with a non-compressed MSDOS partition, say Y

          here) and MSDOS floppies. This means that file access becomes

          transparent, i.e. the MSDOS files look and behave just like all

          other Unix files.

          If you have Windows 95 or Windows NT installed on your MSDOS

          partitions, you should use the VFAT file system (say Y to "VFAT fs

          support" below), or you will not be able to see the long filenames

          generated by Windows 95 / Windows NT.

          This option will enlarge your kernel by about 7 KB. If unsure,

          answer Y. This will only work if you said Y to "DOS FAT fs support"

          as well. To compile this as a module, choose M here: the module will

          be called msdos.

config VFAT_FS

        tristate "VFAT (Windows-95) fs support"

        select FAT_FS

        help

          This option provides support for normal Windows file systems with

          long filenames.  That includes non-compressed FAT-based file systems

          used by Windows 95, Windows 98, Windows NT 4.0, and the Unix

          programs from the mtools package.

          The VFAT support enlarges your kernel by about 10 KB and it only

          works if you said Y to the "DOS FAT fs support" above.  Please read

          the file  for details.  If

          unsure, say Y.

          To compile this as a module, choose M here: the module will be called

          vfat.

config FAT_DEFAULT_CODEPAGE

        int "Default codepage for FAT"

        depends on MSDOS_FS || VFAT_FS

        default 437

        help

          This option should be set to the codepage of your FAT filesystems.

          It can be overridden with the "codepage" mount option.

          See  for more information.

config FAT_DEFAULT_IOCHARSET

        string "Default iocharset for FAT"

        depends on VFAT_FS

        default "iso8859-1"

        help

          Set this to the default input/output character set you'd

          like FAT to use. It should probably match the character set

          that most of your FAT filesystems use, and can be overridden

          with the "iocharset" mount option for FAT filesystems.

          Note that "utf8" is not recommended for FAT filesystems.

          If unsure, you shouldn't set "utf8" here.

          See  for more information.

config NTFS_FS

        tristate "NTFS file system support"

        select NLS

        help

          NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.

          Saying Y or M here enables read support.  There is partial, but

          safe, write support available.  For write support you must also

          say Y to "NTFS write support" below.

          There are also a number of user-space tools available, called

          ntfsprogs.  These include ntfsundelete and ntfsresize, that work

          without NTFS support enabled in the kernel.

          This is a rewrite from scratch of Linux NTFS support and replaced

          the old NTFS code starting with Linux 2.5.11.  A backport to

          the Linux 2.4 kernel series is separately available as a patch

          from the project web site.

          For more information see 

          and .

          To compile this file system support as a module, choose M here: the

          module will be called ntfs.

          If you are not using Windows NT, 2000, XP or 2003 in addition to

          Linux on your computer it is safe to say N.

config NTFS_DEBUG

        bool "NTFS debugging support"

        depends on NTFS_FS

        help

          If you are experiencing any problems with the NTFS file system, say

          Y here.  This will result in additional consistency checks to be

          performed by the driver as well as additional debugging messages to

          be written to the system log.  Note that debugging messages are

          disabled by default.  To enable them, supply the option debug_msgs=1

          at the kernel command line when booting the kernel or as an option

          to insmod when loading the ntfs module.  Once the driver is active,

          you can enable debugging messages by doing (as root):

          echo 1 > /proc/sys/fs/ntfs-debug

          Replacing the "1" with "0" would disable debug messages.

          If you leave debugging messages disabled, this results in little

          overhead, but enabling debug messages results in very significant

          slowdown of the system.

          When reporting bugs, please try to have available a full dump of

          debugging messages while the misbehaviour was occurring.

config NTFS_RW

        bool "NTFS write support"

        depends on NTFS_FS

        help

          This enables the partial, but safe, write support in the NTFS driver.

          The only supported operation is overwriting existing files, without

          changing the file length.  No file or directory creation, deletion or

          renaming is possible.  Note only non-resident files can be written to

          so you may find that some very small files (<500 bytes or so) cannot

          be written to.

          While we cannot guarantee that it will not damage any data, we have

          so far not received a single report where the driver would have

          damaged someones data so we assume it is perfectly safe to use.

          Note:  While write support is safe in this version (a rewrite from

          scratch of the NTFS support), it should be noted that the old NTFS

          write support, included in Linux 2.5.10 and before (since 1997),

          is not safe.

          This is currently useful with TopologiLinux.  TopologiLinux is run

          on top of any DOS/Microsoft Windows system without partitioning your

          hard disk.  Unlike other Linux distributions TopologiLinux does not

          need its own partition.  For more information see

          It is perfectly safe to say N here.

endmenu

endif

menu "Pseudo filesystems"

config PROC_FS

        bool "/proc file system support" if EMBEDDED

        default y

        help

          This is a virtual file system providing information about the status

          of the system. "Virtual" means that it doesn't take up any space on

          your hard disk: the files are created on the fly by the kernel when

          you try to access them. Also, you cannot read the files with older

          version of the program less: you need to use more or cat.

          It's totally cool; for example, "cat /proc/interrupts" gives

          information about what the different IRQs are used for at the moment

          (there is a small number of Interrupt ReQuest lines in your computer

          that are used by the attached devices to gain the CPU's attention --

          often a source of trouble if two devices are mistakenly configured

          to use the same IRQ). The program procinfo to display some

          information about your system gathered from the /proc file system.

          Before you can use the /proc file system, it has to be mounted,

          meaning it has to be given a location in the directory hierarchy.

          That location should be /proc. A command such as "mount -t proc proc

          /proc" or the equivalent line in /etc/fstab does the job.

          The /proc file system is explained in the file

           and on the proc(5) manpage

          ("man 5 proc").