11.ile systems

kevinislinuxer

       
       
       
       
       
       
       
       

File
        systems
       
       

Second
                extended fs support EXT2_FS
       
        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.  Be aware however that the file system
of
your root partition (the one containing the directory /) cannot
be
compiled as a module, and so this could be dangerous.
                If
unsure, say Y.

Ext2
                        extended attributes EXT2_FS_XATTR
               
                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.

Ext2
                                POSIX Access Control Lists EXT2_FS_POSIX_ACL
                       
                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

Ext2
                                Security Labels EXT2_FS_SECURITY
                       
                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.

Ext2
                        execute in place support EXT2_FS_XIP
               
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.

Ext3
                journalling file system support EXT3_FS
       
        This
is the journaling 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
journaling 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
[color="#008080"]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.  Be aware however that the file system
of
your root partition (the one containing the directory /) cannot
be
compiled as a module, and so this may be dangerous.

Ext3
                        extended attributes EXT3_FS_XATTR
               
                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.

Ext3
                                POSIX Access Control Lists EXT3_FS_POSIX_ACL
                       
        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 .
Choose
Y here if you have one of these FM radio cards, and then fill
in
the port address below.
In
order to control your radio card, you will need to use programs
that
are compatible with the Video For Linux API.  Information on
this
API and pointers to "v4l" programs may be found at
[color="#008080"].
To
compile this driver as a module, choose M here: the
module
will be called radio-zoltrix.
Choose
Y here if you have one of these FM radio cards, and then fill
in
the port address and the frequency used for muting below.
In
order to control your radio card, you will need to use programs
that
are compatible with the Video For Linux API.  Information on
this
API and pointers to "v4l" programs may be found at
[color="#008080"].
To
compile this driver as a module, choose M here: the
module
will be called radio-typhoon.This is a driver for the Trust FM radio
cards. Say Y if you have
such
a card and want to use it under Linux.
To
compile this driver as a module, choose M here: the
module
will be called radio-trust.Choose Y here if you have this FM radio
card, and then fill in the
port
address below. (TODO)
Note:
This driver is in its early stages.  Right now volume and
frequency
control and muting works at least for me, but
unfortunately
I have not found anybody who wants to use this card
with
Linux.  So if it is this what YOU are trying to do right now,
PLEASE
DROP ME A NOTE!!  Rolf Offermanns .
In
order to control your radio card, you will need to use programs
that
are compatible with the Video For Linux API.  Information on
this
API and pointers to "v4l" programs may be found at
[color="#008080"].
To
compile this driver as a module, choose M here: the
module
will be called radio-terratec.Choose Y here if you have one of these
FM radio cards.
In
order to control your radio card, you will need to use programs
that
are compatible with the Video For Linux API.  Information on
this
API and pointers to "v4l" programs may be found on the WWW
at
[color="#008080"].
To
compile this driver as a module, choose M here: the
module
will be called radio-sf16fmr2.
If
you don't know what Access Control Lists are, say N

Ext3
                                Security Labels EXT3_FS_SECURITY
                       
                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.

JBD
                (ext3) debugging support JBD_DEBUG
       
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 > /proc/sys/fs/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 > /proc/sys/fs/jbd-debug".

Reiserfs
                support REISERFS_FS
       
        Stores
not just filenames but the files themselves in a balanced
tree.
Uses journaling.
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.

Enable
                        reiserfs debug mode REISERFS_CHECK
               
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.

Stats
                        in /proc/fs/reiserfs REISERFS_PROC_INFO
               
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.

ReiserFS
                        extended attributes REISERFS_FS_XATTR
               
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.

ReiserFS
                                POSIX Access Control Lists REISERFS_FS_POSIX_ACL
                       
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

ReiserFS
                                Security Labels REISERFS_FS_SECURITY
                       
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.

JFS
                filesystem support JFS_FS
       
        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.

JFS
                        POSIX Access Control Lists JFS_POSIX_ACL
               
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

JFS
                        Security Labels JFS_SECURITY
               
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.

JFS
                        debugging JFS_DEBUG
               
               
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.

JFS
                        statistics JFS_STATISTICS
               
Enabling
this option will cause statistics from the JFS file system
to
be made available to the user in the /proc/fs/jfs/ directory.

XFS
                filesystem support XFS_FS
       
XFS
is a high performance journaling filesystem which originated
on
the SGI IRIX platform.  It is completely multi-threaded, can
support
large files and large filesystems, extended attributes,
variable
block sizes, is extent based, and makes extensive use of
Btrees
(directories, extents, free space) to aid both performance
and
scalability.
Refer
to the documentation at
for
complete details.  This implementation is on-disk compatible
with
the IRIX version of XFS.
To
compile this file system support as a module, choose M here: the
module
will be called xfs.  Be aware, however, that if the file
system
of your root partition is compiled as a module, you'll need
to
use an initial ramdisk (initrd) to boot.

XFS
                        Quota support XFS_QUOTA
               
If
you say Y here, you will be able to set limits for disk usage on
a
per user and/or a per group basis under XFS.  XFS considers quota
information
as filesystem metadata and uses journaling to provide a
higher
level guarantee of consistency.  The on-disk data format for
quota
is also compatible with the IRIX version of XFS, allowing a
filesystem
to be migrated between Linux and IRIX without any need
for
conversion.
If
unsure, say N.  More comprehensive documentation can be found in
README.quota
in the xfsprogs package.  XFS quota can be used either
with
or without the generic quota support enabled (CONFIG_QUOTA) -
they
are completely independent subsystems.

XFS
                        Security Label support XFS_SECURITY
               
Security
labels support alternative access control models
implemented
by security modules like SELinux.  This option
enables
an extended attribute namespace for inode security
labels
in the XFS filesystem.
If
you are not using a security module that requires using
extended
attributes for inode security labels, say N.

XFS
                        POSIX ACL support XFS_POSIX_ACL
               
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.

XFS
                        Realtime support (EXPERIMENTAL) XFS_RT
               
If
you say Y here you will be able to mount and use XFS filesystems
which
contain a realtime subvolume. The realtime subvolume is a
separate
area of disk space where only file data is stored. The
realtime
subvolume is designed to provide very deterministic
data
rates suitable for media streaming applications.
See
the xfs man page in section 5 for a bit more information.
This
feature is unsupported at this time, is not yet fully
functional,
and may cause serious problems.
If
unsure, say N.

OCFS2
                file system support (EXPERIMENTAL) OCFS2_FS
       
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
       - shared writeable
mmap
       - loopback is
supported, but data written will not
         be cluster
coherent.
       - quotas
       - cluster aware flock
       - Directory change
notification (F_NOTIFY)
       - Distributed Caching
(F_SETLEASE/F_GETLEASE/break_lease)
       - POSIX ACLs

• readpages
          / writepages (not user visible)
         
• 
  

Minix
                fs support MINIX_FS
       
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.

ROM
                file system support ROMFS_FS
       
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
[color="#008080"]module.
If
you don't know whether you need it, then you don't need it:
answer
N.

Inotify
                file change notification support INOTIFY
       
Say
Y here to enable inotify support and the associated system
calls.
Inotify is a file change notification system and a
replacement
for dnotify.  Inotify fixes numerous shortcomings in
dnotify
and introduces several new features.  It allows monitoring
of
both files and directories via a single open fd.  Other features
include
multiple file events, one-shot support, and unmount
[color="#008080"]notification.
For
more information, see Documentation/filesystems/inotify.txt
If
unsure, say Y.

Quota
                support QUOTA
       
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
[color="#008080"]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.

Old
                        quota format support QFMT_V1
               
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.

Quota
                        format v2 support QFMT_V2
               
This
quota format allows using quotas with 32-bit UIDs/GIDs. If you
need
this functionality say Y here.

Kernel
                automounter support AUTOFS_FS
       
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",
[color="#008080"]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.

Kernel
                automounter version 4 support (also supports v3) AUTOFS4_FS
       
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.

Filesystem
                in Userspace support FUSE_FS
       
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:
[color="#008080"]
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.

CD-ROM/DVD
                Filesystems
               
               

ISO
                        9660 CDROM file system support ISO9660_FS
               
       
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.

Microsoft
                                Joliet CDROM extensions JOLIET
                       
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.

Transparent
                                decompression extension ZISOFS
                       
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.

UDF
                        file system support UDF_FS
               
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.

DOS/FAT/NT
                Filesystems
               
               

MSDOS
                        fs support MSDOS_FS
               
       
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.

VFAT
                        (Windows-95) fs support VFAT_FS
               
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
[color="#008080"]vfat.

Default
                                codepage for FAT FAT_DEFAULT_CODEPAGE
                       
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.

Default
                                iocharset for FAT FAT_DEFAULT_IOCHARSET
                       
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.

NTFS
                        file system support NTFS_FS
               
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.

Pseudo
                filesystems
               
               

/proc
                        file system support PROC_FS
               
       
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").
This
option will enlarge your kernel by about 67 KB. Several
programs
depend on this, so everyone should say Y here.

/proc/kcore
                                support PROC_KCORE
                       

Virtual
                        memory file system support (former shm fs) TMPFS
               
Tmpfs
is a file system which keeps all files in virtual memory.
Everything
in tmpfs is temporary in the sense that no files will be
created
on your hard drive. The files live in memory and swap
space.
If you unmount a tmpfs instance, everything stored therein is
[color="#008080"]lost.
See
for details.

HugeTLB
                        file system support HUGETLBFS
               

Relayfs
                        file system support RELAYFS_FS
               
Relayfs
is a high-speed data relay filesystem designed to provide
an
efficient mechanism for tools and facilities to relay large
amounts
of data from kernel space to user space.
To
compile this code as a module, choose M here: the module will be
called
relayfs.
If
unsure, say N.

Userspace-driven
                        configuration filesystem (EXPERIMENTAL) CONFIGFS_FS
               
configfs
is a ram-based filesystem that provides the converse
of
sysfs's functionality. Where sysfs is a filesystem-based
view
of kernel objects, configfs is a filesystem-based manager
of
kernel objects, or config_items.
Both
sysfs and configfs can and should exist together on the
same
system. One is not a replacement for the other.

Miscellaneous
                filesystems
               
               

ADFS
                        file system support (EXPERIMENTAL) ADFS_FS
               
       
The
Acorn Disc Filing System is the standard file system of the
RiscOS
operating system which runs on Acorn's ARM-based Risc PC
systems
and the Acorn Archimedes range of machines. If you say Y
here,
Linux will be able to read from ADFS partitions on hard drives
and
from ADFS-formatted floppy discs. If you also want to be able to
write
to those devices, say Y to "ADFS write support" below.
The
ADFS partition should be the first partition (i.e.,
/dev/[hs]d?1)
on each of your drives. Please read the file
for further details.
To
compile this code as a module, choose M here: the module will be
called
adfs.
If
unsure, say N.

Amiga
                        FFS file system support (EXPERIMENTAL) AFFS_FS
               
The
Fast File System (FFS) is the common file system used on hard
disks
by Amiga(tm) systems since AmigaOS Version 1.3 (34.20).  Say Y
if
you want to be able to read and write files from and to an Amiga
FFS
partition on your hard drive.  Amiga floppies however cannot be
read
with this driver due to an incompatibility of the floppy
controller
used in an Amiga and the standard floppy controller in
PCs
and workstations. Read
and
.
With
this driver you can also mount disk files used by Bernd
Schmidt's
Un*X Amiga Emulator
[color="#008080"]().
If
you want to do this, you will also need to say Y or M to "Loop
device
support", above.
To
compile this file system support as a module, choose M here: the
module
will be called affs.  If unsure, say N.

Apple
                        Macintosh file system support (EXPERIMENTAL) HFS_FS
               
If
you say Y here, you will be able to mount Macintosh-formatted
floppy
disks and hard drive partitions with full read-write access.
Please
read  to learn about the available mount
[color="#008080"]options.
To
compile this file system support as a module, choose M here: the
module will be called hfs.

Apple
                        Extended HFS file system support HFSPLUS_FS
               
If
you say Y here, you will be able to mount extended format
Macintosh-formatted
hard drive partitions with full read-write access.
This
file system is often called HFS+ and was introduced with
MacOS
8. It includes all Mac specific filesystem data such as
data
forks and creator codes, but it also has several UNIX
style
features such as file ownership and permissions.

BeOS
                        file system (BeFS) support (read only) (EXPERIMENTAL) BEFS_FS
               
The
BeOS File System (BeFS) is the native file system of Be, Inc's
BeOS.
Notable features include support for arbitrary attributes
on
files and directories, and database-like indeces on selected
attributes.
(Also note that this driver doesn't make those features
available
at this time). It is a 64 bit filesystem, so it supports
extremly
large volumes and files.
If
you use this filesystem, you should also say Y to at least one
of
the NLS (native language support) options below.
If
you don't know what this is about, say N.
To
compile this as a module, choose M here: the module will be
called
befs.

Debug
                                BeFS BEFS_DEBUG
                       
If
you say Y here, you can use the 'debug' mount option to enable
debugging
output from the driver.

BFS
                        file system support (EXPERIMENTAL) BFS_FS
               
Boot
File System (BFS) is a file system used under SCO UnixWare to
allow
the bootloader access to the kernel image and other important
files
during the boot process.  It is usually mounted under /stand
and
corresponds to the slice marked as "STAND" in the UnixWare
partition.
You should say Y if you want to read or write the files
on
your /stand slice from within Linux.  You then also need to say Y
to
"UnixWare slices support", below.  More information about
the BFS
file
system is contained in the file
[color="#008080"].
If
you don't know what this is about, say N.
To
compile this as a module, choose M here: the module will be called
bfs.
Note that the file system of your root partition (the one
containing
the directory /) cannot be compiled as a module.

EFS
                        file system support (read only) (EXPERIMENTAL) EFS_FS
               
EFS
is an older file system used for non-ISO9660 CD-ROMs and hard
disk
partitions by SGI's IRIX operating system (IRIX 6.0 and newer
uses
the XFS file system for hard disk partitions however).
This
implementation only offers read-only access. If you don't know
what
all this is about, it's safe to say N. For more information
about
EFS see its home page at .
To
compile the EFS file system support as a module, choose M here: the
module
will be called efs.

Journalling
                        Flash File System (JFFS) support JFFS_FS
               
JFFS
is the Journaling Flash File System developed by Axis
Communications
in Sweden, aimed at providing a crash/powerdown-safe
file
system for disk-less embedded devices. Further information is
available
at (
[color="#008080"]http://developer.axis.com/software/jffs/
[color="#008080"]>).

Journalling
                        Flash File System v2 (JFFS2) support JFFS2_FS
               
JFFS2
is the second generation of the Journalling Flash File System
for
use on diskless embedded devices. It provides improved wear
levelling,
compression and support for hard links. You cannot use
this
on normal block devices, only on 'MTD' devices.
Further
information on the design and implementation of JFFS2 is
available
at .

JFFS2
                                debugging verbosity (0 = quiet, 2 = noisy) JFFS2_FS_DEBUG
                       
This
controls the amount of debugging messages produced by the JFFS2
code.
Set it to zero for use in production systems. For evaluation,
testing
and debugging, it's advisable to set it to one. This will
enable
a few assertions and will print debugging messages at the
KERN_DEBUG
loglevel, where they won't normally be visible. Level 2
is
unlikely to be useful - it enables extra debugging in certain
areas
which at one point needed debugging, but when the bugs were
located
and fixed, the detailed messages were relegated to level 2.
If
reporting bugs, please try to have available a full dump of the
messages
at debug level 1 while the misbehaviour was occurring.

JFFS2
                                write-buffering support JFFS2_FS_WRITEBUFFER
                       
This
enables the write-buffering support in JFFS2.
This
functionality is required to support JFFS2 on the following
types
of flash devices:
- NAND flash
- NOR flash with
transparent ECC
- DataFlash

JFFS2
                                summary support (EXPERIMENTAL) JFFS2_SUMMARY
                       
This
feature makes it possible to use summary information
for
faster filesystem mount.
The
summary information can be inserted into a filesystem image
by
the utility 'sumtool'.
If
unsure, say 'N'.

Advanced
                                compression options for JFFS2 JFFS2_COMPRESSION_OPTIONS
                       
Enabling
this option allows you to explicitly choose which
compression
modules, if any, are enabled in JFFS2. Removing
compressors
and mean you cannot read existing file systems,
and
enabling experimental compressors can mean that you
write
a file system which cannot be read by a standard kernel.
If
unsure, you should _definitely_ say 'N'.

Compressed
                        ROM file system support (cramfs) CRAMFS
               
Saying
Y here includes support for CramFs (Compressed ROM File
System).
CramFs is designed to be a simple, small, and compressed
file
system for ROM based embedded systems.  CramFs is read-only,
limited
to 256MB file systems (with 16MB files), and doesn't support
16/32
bits uid/gid, hard links and timestamps.
See
and
for further information.
To
compile this as a module, choose M here: the module will be called
cramfs.
Note that the root file system (the one containing the
directory
/) cannot be compiled as a module.
If
unsure, say N.

FreeVxFS
                        file system support (VERITAS VxFS(TM) compatible) VXFS_FS
               
FreeVxFS
is a file system driver that support the VERITAS VxFS(TM)
file
system format.  VERITAS VxFS(TM) is the standard file system
of
SCO UnixWare (and possibly others) and optionally available
for
Sunsoft Solaris, HP-UX and many other operating systems.
Currently
only readonly access is supported.
NOTE:
the file system type as used by mount(1), mount(2) and
fstab(5)
is 'vxfs' as it describes the file system format, not
the
actual driver.
To
compile this as a module, choose M here: the module will be
called
freevxfs.  If unsure, say N.

OS/2
                        HPFS file system support HPFS_FS
               
OS/2
is IBM's operating system for PC's, the same as Warp, and HPFS
is
the file system used for organizing files on OS/2 hard disk
partitions.
Say Y if you want to be able to read files from and
write
files to an OS/2 HPFS partition on your hard drive. OS/2
floppies
however are in regular MSDOS format, so you don't need this
option
in order to be able to read them. Read
[color="#008080"].
To
compile this file system support as a module, choose M here: the
module
will be called hpfs.  If unsure, say N.

QNX4
                        file system support (read only) QNX4FS_FS
               
This
is the file system used by the real-time operating systems
QNX
4 and QNX 6 (the latter is also called QNX RTP).
Further
information is available at .
Say
Y if you intend to mount QNX hard disks or floppies.
Unless
you say Y to "QNX4FS read-write support" below, you will
only
be able to read these file systems.
To
compile this file system support as a module, choose M here: the
module
will be called qnx4.
If
you don't know whether you need it, then you don't need it:
answer
N.

System
                        V/Xenix/V7/Coherent file system support SYSV_FS
               
SCO,
Xenix and Coherent are commercial Unix systems for Intel
machines,
and Version 7 was used on the DEC PDP-11. Saying Y
here
would allow you to read from their floppies and hard disk
[color="#008080"]partitions.
If
you have floppies or hard disk partitions like that, it is likely
that
they contain binaries from those other Unix systems; in order
to
run these binaries, you will want to install linux-abi which is a
a
set of kernel modules that lets you run SCO, Xenix, Wyse,
UnixWare,
Dell Unix and System V programs under Linux.  It is
available
via FTP (user: ftp) from
[color="#008080"]).
NOTE:
that will work only for binaries from Intel-based systems;
PDP
ones will have to wait until somebody ports Linux to -11 ;-)
If
you only intend to mount files from some other Unix over the
network
using NFS, you don't need the System V file system support
(but
you need NFS file system support obviously).
Note
that this option is generally not needed for floppies, since a
good
portable way to transport files and directories between unixes
(and
even other operating systems) is given by the tar program ("man
tar"
or preferably "info tar").  Note also that this option has
nothing
whatsoever to do with the option "System V IPC". Read about
the
System V file system in
[color="#008080"].
Saying
Y here will enlarge your kernel by about 27 KB.
To
compile this as a module, choose M here: the module will be called
[color="#008080"]sysv.
If
you haven't heard about all of this before, it's safe to say N.

UFS
                        file system support (read only) UFS_FS
               
BSD
and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
OpenBSD
and NeXTstep) use a file system called UFS. Some System V
Unixes
can create and mount hard disk partitions and diskettes using
this
file system as well. Saying Y here will allow you to read from
these
partitions; if you also want to write to them, say Y to the
experimental
"UFS file system write support", below. Please read the
file
for more information.
The
recently released UFS2 variant (used in FreeBSD 5.x) is
READ-ONLY
supported.
If
you only intend to mount files from some other Unix over the
network
using NFS, you don't need the UFS file system support (but
you
need NFS file system support obviously).
Note
that this option is generally not needed for floppies, since a
good
portable way to transport files and directories between unixes
(and
even other operating systems) is given by the tar program ("man
tar"
or preferably "info tar").
When
accessing NeXTstep files, you may need to convert them from the
NeXT
character set to the Latin1 character set; use the program
recode
("info recode") for this purpose.
To
compile the UFS file system support as a module, choose M here: the
module
will be called ufs.
If
you haven't heard about all of this before, it's safe to say N.

Network
                File Systems
               

NFS
                        file system support NFS_FS
               
       
If
you are connected to some other (usually local) Unix computer
(using
SLIP, PLIP, PPP or Ethernet) and want to mount files residing
on
that computer (the NFS server) using the Network File Sharing
protocol,
say Y. "Mounting files" means that the client can access
the
files with usual UNIX commands as if they were sitting on the
client's
hard disk. For this to work, the server must run the
programs
nfsd and mountd (but does not need to have NFS file system
support
enabled in its kernel). NFS is explained in the Network
Administrator's
Guide, available from
,
on its man page: "man
nfs",
and in the NFS-HOWTO.
A
superior but less widely used alternative to NFS is provided by
the
Coda file system; see "Coda file system support" below.
If
you say Y here, you should have said Y to TCP/IP networking also.
This
option would enlarge your kernel by about 27 KB.
To
compile this file system support as a module, choose M here: the
module
will be called nfs.
If
you are configuring a diskless machine which will mount its root
file
system over NFS at boot time, say Y here and to "Kernel
level
IP autoconfiguration" above and to "Root file system on
NFS"
below.
You cannot compile this driver as a module in this case.
There
are two packages designed for booting diskless machines over
the
net: netboot, available from
,
and Etherboot,
available
from .
If
you don't know what all this is about, say N.

Provide
                                NFSv3 client support NFS_V3
                       
Say
Y here if you want your NFS client to be able to speak version
3
of the NFS protocol.
If
unsure, say Y.

Provide
                                        client support for the NFSv3 ACL protocol extension NFS_V3_ACL
                               
Implement
the NFSv3 ACL protocol extension for manipulating POSIX
Access
Control Lists.  The server should also be compiled with
the
NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
If
unsure, say N.

Provide
                                NFSv4 client support (EXPERIMENTAL) NFS_V4
                       
Say
Y here if you want your NFS client to be able to speak the newer
version
4 of the NFS protocol.
Note:
Requires auxiliary userspace daemons which may be found on
     http://www.citi.umich.edu/projects/nfsv4/
If
unsure, say N.

Allow
                                direct I/O on NFS files (EXPERIMENTAL) NFS_DIRECTIO
                       
This
option enables applications to perform uncached I/O on files
in
NFS file systems using the O_DIRECT open() flag.  When O_DIRECT
is
set for a file, its data is not cached in the system's page
cache.
Data is moved to and from user-level application buffers
directly.
Unlike local disk-based file systems, NFS O_DIRECT has
no
alignment restrictions.
Unless
your program is designed to use O_DIRECT properly, you are
much
better off allowing the NFS client to manage data caching for
you.
Misusing O_DIRECT can cause poor server performance or network
storms.
This kernel build option defaults OFF to avoid exposing
system
administrators unwittingly to a potentially hazardous
[color="#008080"]feature.
For
more details on NFS O_DIRECT, see fs/nfs/direct.c.
If
unsure, say N.  This reduces the size of the NFS client, and
causes
open() to return EINVAL if a file residing in NFS is
opened
with the O_DIRECT flag.

NFS
                        server support NFSD
               
If
you want your Linux box to act as an NFS *server*, so that other
computers
on your local network which support NFS can access certain
directories
on your box transparently, you have two options: you can
use
the self-contained user space program nfsd, in which case you
should
say N here, or you can say Y and use the kernel based NFS
server.
The advantage of the kernel based solution is that it is
[color="#008080"]faster.
In
either case, you will need support software; the respective
locations
are given in the file  in the
NFS
section.
If
you say Y here, you will get support for version 2 of the NFS
protocol
(NFSv2). If you also want NFSv3, say Y to the next question
as
well.
Please
read the NFS-HOWTO, available from
[color="#008080"].
To
compile the NFS server support as a module, choose M here: the
module
will be called nfsd.  If unsure, say N.

Provide
                                NFSv3 server support NFSD_V3
                       
If
you would like to include the NFSv3 server as well as the NFSv2
server,
say Y here.  If unsure, say Y.

Provide
                                        server support for the NFSv3 ACL protocol extension NFSD_V3_ACL
                               
Implement
the NFSv3 ACL protocol extension for manipulating POSIX
Access
Control Lists on exported file systems. NFS clients should
be
compiled with the NFSv3 ACL protocol extension; see the
CONFIG_NFS_V3_ACL
option.  If unsure, say N.

Provide
                                        NFSv4 server support (EXPERIMENTAL) NFSD_V4
                               
If
you would like to include the NFSv4 server as well as the NFSv2
and
NFSv3 servers, say Y here.  This feature is experimental, and
should
only be used if you are interested in helping to test NFSv4.
If
unsure, say N.

Provide
                                NFS server over TCP support NFSD_TCP
                       
If
you want your NFS server to support TCP connections, say Y here.
TCP
connections usually perform better than the default UDP when
the
network is lossy or congested.  If unsure, say Y.

Secure
                        RPC: Kerberos V mechanism (EXPERIMENTAL) RPCSEC_GSS_KRB5
               
Provides
for secure RPC calls by means of a gss-api
mechanism
based on Kerberos V5. This is required for
[color="#008080"]NFSv4.
Note:
Requires an auxiliary userspace daemon which may be found on
     http://www.citi.umich.edu/projects/nfsv4/
If
unsure, say N.

Secure
                        RPC: SPKM3 mechanism (EXPERIMENTAL) RPCSEC_GSS_SPKM3
               
Provides
for secure RPC calls by means of a gss-api
mechanism
based on the SPKM3 public-key mechanism.
Note:
Requires an auxiliary userspace daemon which may be found on
     http://www.citi.umich.edu/projects/nfsv4/
If
unsure, say N.

SMB
                        file system support (to mount Windows shares etc.) SMB_FS
               
SMB
(Server Message Block) is the protocol Windows for Workgroups
(WfW),
Windows 95/98, Windows NT and OS/2 Lan Manager use to share
files
and printers over local networks.  Saying Y here allows you to
mount
their file systems (often called "shares" in this context)
and
access
them just like any other Unix directory.  Currently, this
works
only if the Windows machines use TCP/IP as the underlying
transport
protocol, and not NetBEUI.  For details, read
and the SMB-HOWTO,
available
from .
Note:
if you just want your box to act as an SMB *server* and make
files
and printing services available to Windows clients (which need
to
have a TCP/IP stack), you don't need to say Y here; you can use
the
program SAMBA (available from )
for
that.
General
information about how to connect Linux, Windows machines and
Macs
is on the WWW at .
To
compile the SMB support as a module, choose M here: the module will
be
called smbfs.  Most people say N, however.

CIFS
                        support (advanced network filesystem for Samba, Window and other
                        CIFS compliant servers) CIFS
               
This
is the client VFS module for the Common Internet File System
(CIFS)
protocol which is the successor to the Server Message Block
(SMB)
protocol, the native file sharing mechanism for most early
PC
operating systems.  The CIFS protocol is fully supported by
file
servers such as Windows 2000 (including Windows 2003, NT 4  
and
Windows XP) as well by Samba (which provides excellent CIFS
server
support for Linux and many other operating systems). Limited
support
for Windows ME and similar servers is provided as well.
You
must use the smbfs client filesystem to access older SMB servers
such
as OS/2 and DOS.
The
intent of the cifs module is to provide an advanced
network
file system client for mounting to CIFS compliant servers,
including
support for dfs (hierarchical name space), secure per-user
session
establishment, safe distributed caching (oplock), optional
packet
signing, Unicode and other internationalization improvements,
and
optional Winbind (nsswitch) integration. You do not need to enable
cifs
if running only a (Samba) server. It is possible to enable both
smbfs
and cifs (e.g. if you are using CIFS for accessing Windows 2003
and
Samba 3 servers, and smbfs for accessing old servers). If you need
to
mount to Samba or Windows from this machine, say Y.

CIFS
                                statistics CIFS_STATS
                       
Enabling
this option will cause statistics for each server share
mounted
by the cifs client to be displayed in /proc/fs/cifs/Stats

CIFS
                                extended attributes CIFS_XATTR
                       
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).  CIFS maps the name of
extended
attributes beginning with the user namespace prefix
to
SMB/CIFS EAs. EAs are stored on Windows servers without the
user
namespace prefix, but their names are seen by Linux cifs clients
prefaced
by the user namespace prefix. The system namespace
(used
by some filesystems to store ACLs) is not supported at
this
time.
If
unsure, say N.

CIFS
                                        POSIX Extensions CIFS_POSIX
                               
Enabling
this option will cause the cifs client to attempt to
negotiate
a newer dialect with servers, such as Samba 3.0.5
or
later, that optionally can handle more POSIX like (rather
than
Windows like) file behavior.  It also enables
support
for POSIX ACLs (getfacl and setfacl) to servers
(such
as Samba 3.10 and later) which can negotiate
CIFS
POSIX ACL support.  If unsure, say N.

CIFS
                                Experimental Features (EXPERIMENTAL) CIFS_EXPERIMENTAL
                       
Enables
cifs features under testing. These features are
experimental
and currently include support for writepages
(multipage
writebehind performance improvements) and directory
change
notification ie fcntl(F_DNOTIFY) as well as some security
improvements.
Some also depend on setting at runtime the
pseudo-file
/proc/fs/cifs/Experimental (which is disabled by
default).
See the file fs/cifs/README for more details.
If
unsure, say N.

NCP
                        file system support (to mount NetWare volumes) NCP_FS
               
NCP
(NetWare Core Protocol) is a protocol that runs over IPX and is
used
by Novell NetWare clients to talk to file servers.  It is to
IPX
what NFS is to TCP/IP, if that helps.  Saying Y here allows you
to
mount NetWare file server volumes and to access them just like
any
other Unix directory.  For details, please read the file
in the kernel source and
the
IPX-HOWTO from .
You
do not have to say Y here if you want your Linux box to act as a
file
*server* for Novell NetWare clients.
General
information about how to connect Linux, Windows machines and
Macs
is on the WWW at .
To
compile this as a module, choose M here: the module will be called
ncpfs.
Say N unless you are connected to a Novell network.

Packet
                                signatures NCPFS_PACKET_SIGNING
                       
NCP
allows packets to be signed for stronger security. If you want
security,
say Y.  Normal users can leave it off.  To be able to use
packet
signing you must use ncpfs > 2.0.12.

Proprietary
                                file locking NCPFS_IOCTL_LOCKING
                       
Allows
locking of records on remote volumes.  Say N unless you have
special
applications which are able to utilize this locking scheme.

Clear
                                remove/delete inhibit when needed NCPFS_STRONG
                       
Allows
manipulation of files flagged as Delete or Rename Inhibit.
To
use this feature you must mount volumes with the ncpmount
parameter
"-s" (ncpfs-2.0.12 and newer).  Say Y unless you are not
mounting
volumes with -f 444.

Use
                                NFS namespace if available NCPFS_NFS_NS
                       
Allows
you to utilize NFS namespace on NetWare servers.  It brings
you
case sensitive filenames.  Say Y.  You can disable it at
mount-time
with the `-N nfs' parameter of ncpmount.

Use
                                LONG (OS/2) namespace if available NCPFS_OS2_NS
                       
Allows
you to utilize OS2/LONG namespace on NetWare servers.
Filenames
in this namespace are limited to 255 characters, they are
case
insensitive, and case in names is preserved.  Say Y.  You can
disable
it at mount time with the -N os2 parameter of ncpmount.

Lowercase
                                DOS filenames NCPFS_SMALLDOS
                       
If
you say Y here, every filename on a NetWare server volume using
the
OS2/LONG namespace and created under DOS or on a volume using
DOS
namespace will be converted to lowercase characters.
Saying
N here will give you these filenames in uppercase.
This
is only a cosmetic option since the OS2/LONG namespace is case
insensitive.
The only major reason for this option is backward
compatibility
when moving from DOS to OS2/LONG namespace support.
Long
filenames (created by Win95) will not be affected.
This
option does not solve the problem that filenames appear
differently
under Linux and under Windows, since Windows does an
additional
conversions on the client side. You can achieve similar
effects
by saying Y to "Allow using of Native Language Support"
[color="#008080"]below.

Use
                                Native Language Support NCPFS_NLS
                       
Allows
you to use codepages and I/O charsets for file name
translation
between the server file system and input/output. This
may
be useful, if you want to access the server with other operating
systems,
e.g. Windows 95. See also NLS for more Information.
To
select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.

Enable
                                symbolic links and execute flags NCPFS_EXTRAS
                       
This
enables the use of symbolic links and an execute permission
bit
on NCPFS. The file server need not have long name space or NFS
name
space loaded for these to work.
To
use the new attributes, it is recommended to use the flags
'-f
600 -d 755' on the ncpmount command line.

Coda
                        file system support (advanced network fs) CODA_FS
               
Coda
is an advanced network file system, similar to NFS in that it
enables
you to mount file systems of a remote server and access them
with
regular Unix commands as if they were sitting on your hard
disk.
Coda has several advantages over NFS: support for
disconnected
operation (e.g. for laptops), read/write server
replication,
security model for authentication and encryption,
persistent
client caches and write back caching.
If
you say Y here, your Linux box will be able to act as a Coda
*client*.
You will need user level code as well, both for the
client
and server.  Servers are currently user level, i.e. they need
no
kernel support.  Please read
and check out the Coda
home
page .
To
compile the coda client support as a module, choose M here: the
module
will be called coda.

Use
                                96-bit Coda file identifiers CODA_FS_OLD_API
                       
A
new kernel-userspace API had to be introduced for Coda v6.0
to
support larger 128-bit file identifiers as needed by the
new
realms implementation.
However
this new API is not backward compatible with older
clients.
If you really need to run the old Coda userspace
cache
manager then say Y.
For
most cases you probably want to say N.

Andrew
                        File System support (AFS) (Experimental) AFS_FS
               
If
you say Y here, you will get an experimental Andrew File System
driver.
It currently only supports unsecured read-only AFS access.
See
for more intormation.
If
unsure, say N.

Plan
                        9 Resource Sharing Support (9P2000) (Experimental) 9P_FS
               
If
you say Y here, you will get experimental support for
Plan
9 resource sharing via the 9P2000 protocol.
See
for more information.
If
unsure, say N.

Partition
                Types
               
               

Advanced
                        partition selection PARTITION_ADVANCED
               
       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned under an operating system running on a different
architecture
than your Linux system.
Note
that the answer to this question won't directly affect the
kernel:
saying N will just cause the configurator to skip all
the
questions about foreign partitioning schemes.
If
unsure, say N.

Acorn
                                partition support ACORN_PARTITION
                       
Support
hard disks partitioned under Acorn operating systems.

Alpha
                                OSF partition support OSF_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned on an Alpha machine.

Amiga
                                partition table support AMIGA_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned under AmigaOS.

Atari
                                partition table support ATARI_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned under the Atari OS.

Macintosh
                                partition map support MAC_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned on a Macintosh.

PC
                                BIOS (MSDOS partition tables) support MSDOS_PARTITION
                       
Say
Y here.

BSD
                                        disklabel (FreeBSD partition tables) support BSD_DISKLABEL
                               
FreeBSD
uses its own hard disk partition scheme on your PC. It
requires
only one entry in the primary partition table of your disk and
manages it similarly to DOS extended partitions, putting in itsfirst
sector a new partition table in BSD disklabel format. Saying Y ere
allows you to read these disklabels and further mount FreeBSD
partitions from within Linux if you have also said Y to "UFS
file system support", above. If you don't know what all this is
about,
say N.

Minix
                                        subpartition support MINIX_SUBPARTITION
                               
Minix
2.0.0/2.0.2 subpartition table support for Linux.
Say
Y here if you want to mount and use Minix 2.0.0/2.0.2
[color="#008080"]subpartitions.

Solaris
                                        (x86) partition table support SOLARIS_X86_PARTITION
                               
Like
most systems, Solaris x86 uses its own hard disk partition
table
format, incompatible with all others. Saying Y here allows you
to
read these partition tables and further mount Solaris x86
partitions
from within Linux if you have also said Y to "UFS
file
system support", above.

Unixware
                                        slices support UNIXWARE_DISKLABEL
                               
Like
some systems, UnixWare uses its own slice table inside a
partition
(VTOC - Virtual Table of Contents). Its format is
incompatible
with all other OSes. Saying Y here allows you to read VTOC and
further mount UnixWare partitions read-only from within Linux if you
have also said Y to "UFS file system support" or "System
V and Coherent file system support", above.
This
is mainly used to carry data from a UnixWare box to your
Linux
box via a removable medium like magneto-optical, ZIP or
removable
IDE drives. Note, however, that a good portable way to
transport
files and directories between unixes (and even other
operating
systems) is given by the tar program ("man tar" or
preferably
"info tar").
If
you don't know what all this is about, say N.

Windows
                                Logical Disk Manager (Dynamic Disk) support LDM_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned using Windows 2000's or XP's Logical Disk Manager.
They
are also known as "Dynamic Disks".
Windows
2000 introduced the concept of Dynamic Disks to get around
the
limitations of the PC's partitioning scheme.  The Logical Disk
Manager
allows the user to repartition a disk and create spanned,
mirrored,
striped or RAID volumes, all without the need for
[color="#008080"]rebooting.

SGI
                                partition support SGI_PARTITION
                       
Say
Y here if you would like to be able to read the hard disk
partition
table format used by SGI machines.

Ultrix
                                partition table support ULTRIX_PARTITION
                       
Say
Y here if you would like to be able to read the hard disk
partition
table format used by DEC (now Compaq) Ultrix machines.
Otherwise,
say N.

Sun
                                partition tables support SUN_PARTITION
                       
Like
most systems, SunOS uses its own hard disk partition table
format,
incompatible with all others. Saying Y here allows you to
read
these partition tables and further mount SunOS partitions from
within
Linux if you have also said Y to "UFS file system support",
above.
This is mainly used to carry data from a SPARC under SunOS to
your
Linux box via a removable medium like magneto-optical or ZIP
drives;
note however that a good portable way to transport files and
directories
between unixes (and even other operating systems) is
given
by the tar program ("man tar" or preferably "info
tar"). If
you
don't know what all this is about, say N.

Karma
                                Partition support KARMA_PARTITION
                       
Say
Y here if you would like to mount the Rio Karma MP3 player, as it
uses
a proprietary partition table.

EFI
                                GUID Partition support EFI_PARTITION
                       
Say
Y here if you would like to use hard disks under Linux which
were
partitioned using EFI GPT.  Presently only useful on the
IA-64
platform.

Native
                Language Support
               
               

Base
                        native language support NLS
               
       

本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u/17431/showart_137800.html