Linux/Unix编程

开发平台：

Unix_Linux

Configure.help：源码内容

multiple hosts), Ethertap (to network with the host and the
outside world), and/or the Daemon transport (to network multiple
UMLs on a single host). You may choose more than one without
conflict. If you don't need UML networking, say N.
Microtek USB scanner support
CONFIG_USB_MICROTEK
Say Y here if you want support for the Microtek X6USB and
possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L.
Support for anything but the X6 is experimental.
Please report failures and successes.
The scanner will appear as a scsi generic device to the rest
of the system. Scsi support is required for this driver to compile
and work. SANE 1.0.4 or newer is needed to make use of your scanner.
This driver can be compiled as a module.
HP53xx and Minolta Dual Scanner support
CONFIG_USB_HPUSBSCSI
Say Y here if you want support for the HP 53xx series of scanners
and the Minolta Scan Dual. This driver is experimental.
The scanner will be accessible as a SCSI device.
USB Bluetooth support
CONFIG_USB_BLUETOOTH
Say Y here if you want to connect a USB Bluetooth device to your
computer's USB port. You will need the Bluetooth stack (available
at <http://developer.axis.com/software/index.shtml>) to fully use
the device.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called bluetooth.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
USB MIDI support
CONFIG_USB_MIDI
Say Y here if you want to connect a USB MIDI device to your
computer's USB port. This driver is for devices that comply with
'Universal Serial Bus Device Class Definition for MIDI Device'.
The following devices are known to work:
* Steinberg USB2MIDI
* Roland MPU64
* Roland PC-300
* Roland SC8850
* Roland UM-1
* Roland UM-2
* Roland UA-100
* Yamaha MU1000
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-midi.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Minix fs support
CONFIG_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.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called minix.o. Note that the file system of your root
partition (the one containing the directory /) cannot be compiled as
a module.
Reiserfs support
CONFIG_REISERFS_FS
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 <http://www.reiserfs.org/> 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 <http://www.reiserfs.org/> 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 extra Reiserfs consistency checks
CONFIG_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.
Publish some reiserfs-specific info under /proc/fs/reiserfs
CONFIG_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 by 440 bytes.
It isn't useful to average persons, and you probably can't measure the
performance cost of it. If you are fine-tuning reiserfs, say Y,
otherwise say N.
Second extended fs support
CONFIG_EXT2_FS
This is the de facto standard Linux file system (method to organize
files on a storage device) for hard disks.
You want to say Y here, unless you intend to use Linux exclusively
from inside a DOS partition using the UMSDOS file system. The
advantage of the latter is that you can get away without
repartitioning your hard drive (which often implies backing
everything up and restoring afterwards); the disadvantage is that
Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
slower than ext2fs. Even if you want to run Linux in this fashion,
it might be a good idea to have ext2fs around: it enables you to
read more floppy disks and facilitates the transition to a *real*
Linux partition later. Another (rare) case which doesn't require
ext2fs is a diskless Linux box which mounts all files over the
network using NFS (in this case it's sufficient to say Y to "NFS
file system support" below). Saying Y here will enlarge your kernel
by about 44 KB.
The Ext2fs-Undeletion mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, gives information about
how to retrieve deleted files on ext2fs file systems.
To change the behaviour of ext2 file systems, you can use the tune2fs
utility ("man tune2fs"). To modify attributes of files and
directories on ext2 file systems, use chattr ("man chattr").
Ext2fs partitions can be read from within DOS using the ext2tool
command line tool package (available from
<ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
within Windows NT using the ext2nt command line tool package from
<ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
graphical explorer for ext2fs partitions which runs on Windows 95
and Windows NT and includes experimental write support; it is
available from
<http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
If you want to compile this file system as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called ext2.o. 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. Most
everyone wants to say Y here.
Ext3 journalling file system support (EXPERIMENTAL)
CONFIG_EXT3_FS
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
behaviour 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 <http://sourceforge.net/projects/e2fsprogs/>).
If you want to compile this file system as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called ext3.o. 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.
Journal Block Device support (JBD for ext3) (EXPERIMENTAL)
CONFIG_JBD
This is a generic journalling layer for block devices. It is
currently used by the ext3 file system, 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 file system, you need to say Y here. If
you are not using ext3 then you will probably want to say N.
If you want to compile this device as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called jbd.o. If you are compiling ext3 into the kernel,
you cannot compile this code as a module.
JBD (ext3) debugging support
CONFIG_JBD_DEBUG
If you are using the ext3 journalling 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".
Buffer Head tracing (DEBUG)
CONFIG_BUFFER_DEBUG
If you are a kernel developer working with file systems or in the
block device layer, this buffer head tracing may help you to track
down bugs in your code. This enables some debugging macros
(BUFFER_TRACE, etc.) which allow you to track the state of a buffer
through various layers of code. The debugging code is used
primarily by ext3 and JBD code.
Because this option adds considerably to the size of each buffer,
most people will want to say N here.
BeOS filesystem support (BeFS) (read only)
CONFIG_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 indices 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
extremely 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.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read Documentation/modules.txt. The module will be
called befs.o.
Debug BeFS
CONFIG_BEFS_DEBUG
If you say Y here, you can use the 'debug' mount option to enable
debugging output from the driver. This is unlike previous versions
of the driver, where enabling this option would turn on debugging
output automatically.
Example:
mount -t befs /dev/hda2 /mnt -o debug
BFS file system support
CONFIG_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
<file:Documentation/filesystems/bfs.txt>.
If you don't know what this is about, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called bfs.o. Note that the file system of your root
partition (the one containing the directory /) cannot be compiled as
a module.
Compressed ROM file system support
CONFIG_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 <file:Documentation/filesystems/cramfs.txt> and
<file:fs/cramfs/README> for further information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called cramfs.o. Note that the root file system (the one
containing the directory /) cannot be compiled as a module.
If unsure, say N.
CMS file system support
CONFIG_CMS_FS
Read only support for CMS minidisk file systems found on IBM
mainframe systems. Only the basic format is supported so far. If
you don't know what CMS is you probably don't want to know any more.
# When the 2.5 version of configure.help goes away, the part of this that
# duplicates Documentation/filesystems/tmpfs.txt can drop out.
Virtual memory file system support
CONFIG_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. If you reboot, everything in tmpfs will
be lost.
In contrast to RAM disks, which get allocated a fixed amount of
physical RAM, tmpfs grows and shrinks to accommodate the files it
contains and is able to swap unneeded pages out to swap space.
Everything is "virtual" in the sense that no files will be created
on your hard drive; if you reboot, everything in tmpfs will be
lost.
You should mount the file system somewhere to be able to use
POSIX shared memory. Adding the following line to /etc/fstab should
take care of things:
tmpfs /dev/shm tmpfs defaults 0 0
Remember to create the directory that you intend to mount tmpfs on
if necessary (/dev/shm is automagically created if you use devfs).
You can set limits for the number of blocks and inodes used by the
file system with the mount options "size", "nr_blocks" and
"nr_inodes". These parameters accept a suffix k, m or g for kilo,
mega and giga and can be changed on remount.
The initial permissions of the root directory can be set with the
mount option "mode".
See <file:Documentation/filesystems/tmpfs.txt> for details.
Simple RAM-based file system support
CONFIG_RAMFS
Ramfs is a file system which keeps all files in RAM. It allows
read and write access.
It is more of an programming example than a usable file system. If
you need a file system which lives in RAM with limit checking use
tmpfs.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ramfs.o.
ISO 9660 CD-ROM file system support
CONFIG_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
<file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
available from <http://www.tldp.org/docs.html#howto>), thereby
enlarging your kernel by about 27 KB; otherwise say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called isofs.o.
Microsoft Joliet CD-ROM extensions
CONFIG_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
<http://www.unicode.org/> for more information). Say Y here if you
want to be able to read Joliet CD-ROMs under Linux.
Transparent decompression extension
CONFIG_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
<http://www.kernel.org/pub/linux/utils/fs/zisofs/> 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 (read-only)
CONFIG_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. This UDF
file system support is read-only. If you want to write to UDF
file systems on some media, you need to say Y to "UDF read-write
support" below in addition. Please read
<file:Documentation/filesystems/udf.txt>.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want). The module is called udf.o. If you want to
compile it as a module, say M here and read
<file:Documentation/modules.txt>.
If unsure, say N.
UDF write support (DANGEROUS)
CONFIG_UDF_RW
Say Y if you want to test write support for UDF file systems.
Due to lack of support for writing to CDR/CDRW's, this option
is only supported for hard discs, DVD-RAM, and loopback files.
DOS FAT fs support
CONFIG_FAT_FS
If you want to use one of the FAT-based file systems (the MS-DOS,
VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
ordinary DOS partition) 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").
It is now also becoming possible to read and write compressed FAT
file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
details.
The FAT support will enlarge your kernel by about 37 KB. If unsure,
say Y.
If you want to compile this as a module however ( = code which can
be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called fat.o. 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.
The file system of your root partition (the one containing the
directory /) cannot be a module, so don't say M here if you intend
to use UMSDOS as your root file system.
MSDOS fs support
CONFIG_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
<http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
<ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. 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 want to use UMSDOS, the Unix-like file system on top of a
DOS file system, which allows you to run Linux from within a DOS
partition without repartitioning, you'll have to say Y or M here.
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. If you want to compile this as a module however ( = code
which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>.
The module will be called msdos.o.
VFAT (Windows-95) fs support
CONFIG_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.
You cannot use the VFAT file system for your Linux root partition
(the one containing the directory /); use UMSDOS instead if you
want to run Linux from within a DOS partition (i.e. say Y to
"Unix like fs on top of std MSDOS fs", below).
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 <file:Documentation/filesystems/vfat.txt> for details. If
unsure, say Y.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called vfat.o.
Unix-like file system on top of standard MSDOS fs
CONFIG_UMSDOS_FS
Say Y here if you want to run Linux from within an existing DOS
partition of your hard drive. The advantage of this is that you can
get away without repartitioning your hard drive (which often implies
backing everything up and restoring afterwards) and hence you're
able to quickly try out Linux or show it to your friends; the
disadvantage is that Linux becomes susceptible to DOS viruses and
that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
is to write files with long unix filenames to MSDOS floppies; it
also allows Unix-style soft-links and owner/permissions of files on
MSDOS floppies. You will need a program called umssync in order to
make use of UMSDOS; read
<file:Documentation/filesystems/umsdos.txt>.
To get utilities for initializing/checking UMSDOS file system, or
latest patches and/or information, visit the UMSDOS home page at
<http://www.voyager.hr/~mnalis/umsdos/>.
This option enlarges your kernel by about 28 KB and it only works if
you said Y to both "DOS FAT fs support" and "MSDOS fs support"
above. If you want to compile this as a module ( = code which can
be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called umsdos.o. Note that the file system of your
root partition (the one containing the directory /) cannot be a
module, so saying M could be dangerous. If unsure, say N.
/proc file system support
CONFIG_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
<file:Documentation/filesystems/proc.txt> 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.
Support for PReP Residual Data
CONFIG_PREP_RESIDUAL
Some PReP systems have residual data passed to the kernel by the
firmware. This allows detection of memory size, devices present and
other useful pieces of information. Sometimes this information is
not present or incorrect.
Unless you expect to boot on a PReP system, there is no need to
select Y.
PReP residual data available in /proc/residual
CONFIG_PROC_PREPRESIDUAL
Enabling this option will create a /proc/residual file which allows
you to get at the residual data on PReP systems. You will need a tool
(lsresidual) to parse it. If you aren't on a PReP system, you don't
want this.
/dev file system support
CONFIG_DEVFS_FS
This is support for devfs, a virtual file system (like /proc) which
provides the file system interface to device drivers, normally found
in /dev. Devfs does not depend on major and minor number
allocations. Device drivers register entries in /dev which then
appear automatically, which means that the system administrator does
not have to create character and block special device files in the
/dev directory using the mknod command (or MAKEDEV script) anymore.
This is work in progress. If you want to use this, you *must* read
the material in <file:Documentation/filesystems/devfs/>, especially
the file README there.
If unsure, say N.
Automatically mount devfs at boot time
CONFIG_DEVFS_MOUNT
This option appears if you have CONFIG_DEVFS_FS enabled. Setting
this to 'Y' will make the kernel automatically mount devfs onto /dev
when the system is booted, before the init thread is started.
You can override this with the "devfs=nomount" boot option.
If unsure, say N.
Debug devfs
CONFIG_DEVFS_DEBUG
If you say Y here, then the /dev file system code will generate
debugging messages. See the file
<file:Documentation/filesystems/devfs/boot-options> for more
details.
If unsure, say N.
NFS file system support
CONFIG_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
<http://www.tldp.org/docs.html#guide>, 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.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called nfs.o. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>.
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
<http://ftp1.sourceforge.net/netboot/>, and Etherboot,
available from <http://ftp1.sourceforge.net/etherboot/>.
If you don't know what all this is about, say N.
Provide NFSv3 client support
CONFIG_NFS_V3
Say Y here if you want your NFS client to be able to speak the newer
version 3 of the NFS protocol.
If unsure, say N.
Root file system on NFS
CONFIG_ROOT_NFS
If you want your Linux box to mount its whole root file system (the
one containing the directory /) from some other computer over the
net via NFS (presumably because your box doesn't have a hard disk),
say Y. Read <file:Documentation/nfsroot.txt> for details. It is
likely that in this case, you also want to say Y to "Kernel level IP
autoconfiguration" so that your box can discover its network address
at boot time.
Most people say N here.
NFS server support
CONFIG_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
faster.
In either case, you will need support software; the respective
locations are given in the file <file:Documentation/Changes> 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
<http://www.tldp.org/docs.html#howto>.
The NFS server is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called nfsd.o. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>. If unsure,
say N.
Provide NFSv3 server support
CONFIG_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 NFS over TCP server support EXPERIMENTAL
CONFIG_NFSD_TCP
Enable NFS service over TCP connections. This the officially
still experimental, but seems to work well.
OS/2 HPFS file system support
CONFIG_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
<file:Documentation/filesystems/hpfs.txt>.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called hpfs.o. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>. If unsure,
say N.
NTFS file system support (read-only)
CONFIG_NTFS_FS
NTFS is the file system of Microsoft Windows NT. Say Y if you want
to get read access to files on NTFS partitions of your hard drive.
The Linux NTFS driver supports most of the mount options of the VFAT
driver, see <file:Documentation/filesystems/ntfs.txt>. Saying Y here
will give you read-only access to NTFS partitions.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ntfs.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
NTFS write support (DANGEROUS)
CONFIG_NTFS_RW
If you say Y here, you will (maybe) be able to write to NTFS file
systems as well as read from them. The read-write support in NTFS
is far from being complete and is not well tested. If you say Y
here, back up your NTFS volume first, since it will probably get
damaged. Also, download the Linux-NTFS project distribution from
Sourceforge at <http://linux-ntfs.sf.net/> and always run the
included ntfsfix utility after writing to an NTFS partition from
Linux to fix some of the damage done by the driver. You should run
ntfsfix _after_ unmounting the partition in Linux but _before_
rebooting into Windows. When Windows next boots, chkdsk will be
run automatically to fix the remaining damage.
Please note that write support is limited to Windows NT4 and
earlier versions.
If unsure, say N.
System V/Xenix/V7/Coherent file system support
CONFIG_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
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
<ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
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
<file:Documentation/filesystems/sysv-fs.txt>.
Saying Y here will enlarge your kernel by about 27 KB.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called sysv.o.
If you haven't heard about all of this before, it's safe to say N.
Amiga FFS file system support
CONFIG_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 <file:Documentation/filesystems/affs.txt>
and <file:fs/affs/Changes>.
With this driver you can also mount disk files used by Bernd
Schmidt's Un*X Amiga Emulator
(<http://www.freiburg.linux.de/~uae/>).
If you want to do this, you will also need to say Y or M to "Loop
device support", above.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called affs.o. If you want to compile it as a module,
say M here and read <file:Documentation/modules.txt>. If unsure,
say N.
Apple Macintosh file system support
CONFIG_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 <file:fs/hfs/HFS.txt> to learn about the available mount
options.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want). The module is called hfs.o. If you want to
compile it as a module, say M here and read
<file:Documentation/modules.txt>.
ROM file system support
CONFIG_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
<file:Documentation/filesystems/romfs.txt> for details.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want). The module is called romfs.o. If you want to
compile it as a module, say M here and read
<file:Documentation/modules.txt>. 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.
QNX4 file system support (read only)
CONFIG_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 <http://www.qnx.com/>.
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.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want). The module is called qnx4.o. If you want to
compile it as a module, say M here and read
<file:Documentation/modules.txt>.
If you don't know whether you need it, then you don't need it:
answer N.
QNX4FS write support (DANGEROUS)
CONFIG_QNX4FS_RW
Say Y if you want to test write support for QNX4 file systems.
It's currently broken, so for now:
answer N.
Kernel automounter support
CONFIG_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 <file:Documentation/Changes>.
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.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called autofs.o.
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)
CONFIG_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
<ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
want to answer Y to "NFS file system support", below.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called autofs4.o. 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.
EFS file system support (read-only)
CONFIG_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 <http://aeschi.ch.eu.org/efs/>.
If you want to compile the EFS file system support as a module ( =
code which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called efs.o.
Journalling Flash File System (JFFS) support
CONFIG_JFFS_FS
JFFS is the Journalling 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 (<http://developer.axis.com/software/jffs/>).
JFFS debugging verbosity (0 = quiet, 3 = noisy)
CONFIG_JFFS_FS_VERBOSE
Determines the verbosity level of the JFFS debugging messages.
Journalling Flash File System v2 (JFFS2) support
CONFIG_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 should be made available soon at
<http://sources.redhat.com/jffs2/>.
JFFS2 debugging verbosity (0 = quiet, 2 = noisy)
CONFIG_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.
JFFS stats available in /proc filesystem
CONFIG_JFFS_PROC_FS
Enabling this option will cause statistics from mounted JFFS file systems
to be made available to the user in the /proc/fs/jffs/ directory.
UFS file system support (read-only)
CONFIG_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 <file:Documentation/filesystems/ufs.txt> for more information.
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.
If you want to compile the UFS file system support as a module ( =
code which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called ufs.o.
If you haven't heard about all of this before, it's safe to say N.
UFS file system write support (DANGEROUS)
CONFIG_UFS_FS_WRITE
Say Y here if you want to try writing to UFS partitions. This is
experimental, so you should back up your UFS partitions beforehand.
Advanced partition selection
CONFIG_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
CONFIG_ACORN_PARTITION
Support hard disks partitioned under Acorn operating systems.
Native filecore partition support
CONFIG_ACORN_PARTITION_ADFS
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 support disk partitions created under ADFS.
PowerTec partition support
CONFIG_ACORN_PARTITION_POWERTEC
Support reading partition tables created on Acorn machines using
the PowerTec SCSI drive.
RISCiX partition support
CONFIG_ACORN_PARTITION_RISCIX
Once upon a time, there was a native Unix port for the Acorn series
of machines called RISCiX. If you say 'Y' here, Linux will be able
to read disks partitioned under RISCiX.
ICS partition support
CONFIG_ACORN_PARTITION_ICS
Say Y here if you would like to use hard disks under Linux which
were partitioned using the ICS interface on Acorn machines.
Alpha OSF partition support
CONFIG_OSF_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned on an Alpha machine.
Macintosh partition map support
CONFIG_MAC_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned on a Macintosh.
Windows Logical Disk Manager (Dynamic Disk) support (EXPERIMENTAL)
CONFIG_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
rebooting.
Normal partitions are now called Basic Disks under Windows 2000 and
XP.
Technical documentation to accompany this driver is available from:
<http://linux-ntfs.sf.net/ldm/>.
If unsure, say N.
Windows LDM extra logging
CONFIG_LDM_DEBUG
Say Y here if you would like LDM to log verbosely. This could be
helpful if the driver doesn't work as expected and you'd like to
report a bug.
If unsure, say N.
PC BIOS (MSDOS partition tables) support
CONFIG_MSDOS_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned on an x86 PC (not necessarily by DOS).
Amiga partition table support
CONFIG_AMIGA_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned under AmigaOS.
Atari partition table support
CONFIG_ATARI_PARTITION
Say Y here if you would like to use hard disks under Linux which
were partitioned under the Atari OS.
BSD disklabel (FreeBSD partition tables) support
CONFIG_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 its
first sector a new partition table in BSD disklabel format. Saying Y
here 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
CONFIG_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
subpartitions.
Sun partition table support
CONFIG_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.
Solaris (x86) partition table support
CONFIG_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.
SGI partition support
CONFIG_SGI_PARTITION
Say Y here if you would like to be able to read the hard disk
partition table format used by SGI machines.
Intel EFI GUID partition support
CONFIG_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.
Ultrix partition table support
CONFIG_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.
IBM disk label and partition support
CONFIG_IBM_PARTITION
You have to say Y here if you would like to be able to read volume
labels of IBM DASD disks. These can be ECKD DASD disks with
compatible disk layout (cdl) and standard Linux disk layout (ldl),
FBA DASD disks and CMS reserved minidisks.
Otherwise, say N and you will not be able to access these disks.
ADFS file system support
CONFIG_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
<file:Documentation/filesystems/adfs.txt> for further details.
This code is also available as a module called adfs.o ( = code which
can be inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
<file:Documentation/modules.txt>.
If unsure, say N.
ADFS write support (DANGEROUS)
CONFIG_ADFS_FS_RW
If you say Y here, you will be able to write to ADFS partitions on
hard drives and ADFS-formatted floppy disks. This is experimental
codes, so if you're unsure, say N.
JFS filesystem support
CONFIG_JFS_FS
This is a port of IBM's Journalling Filesystem . More information is
available in the file Documentation/filesystems/jfs.txt.
If you do not intend to use the JFS filesystem, say N.
JFS Debugging
CONFIG_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
CONFIG_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.
/dev/pts file system for Unix98 PTYs
CONFIG_DEVPTS_FS
You should say Y here if you said Y to "Unix98 PTY support" above.
You'll then get a virtual file system which can be mounted on
/dev/pts with "mount -t devpts". This, together with the pseudo
terminal master multiplexer /dev/ptmx, is used for pseudo terminal
support as described in The Open Group's Unix98 standard: in order
to acquire a pseudo terminal, a process opens /dev/ptmx; the number
of the pseudo terminal is then made available to the process and the
pseudo terminal slave can be accessed as /dev/pts/<number>. What was
traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
The GNU C library glibc 2.1 contains the requisite support for this
mode of operation; you also need client programs that use the Unix98
API. Please read <file:Documentation/Changes> for more information
about the Unix98 pty devices.
Note that the experimental "/dev file system support"
(CONFIG_DEVFS_FS) is a more general facility.
FreeVxFS file system support (VERITAS VxFS(TM) compatible)
CONFIG_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.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called freevxfs.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. If
unsure, say N.
UnixWare slices support
CONFIG_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.
SMB file system support (to mount Windows shares etc.)
CONFIG_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
<file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
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 <ftp://ftp.samba.org/pub/samba/>)
for that.
General information about how to connect Linux, Windows machines and
Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
If you want to compile the SMB support as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want), say M here and read <file:Documentation/modules.txt>. The
module will be called smbfs.o. Most people say N, however.
Use a default NLS
CONFIG_SMB_NLS_DEFAULT
Enabling this will make smbfs use nls translations by default. You
need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
settings and you need to give the default nls for the SMB server as
CONFIG_SMB_NLS_REMOTE.
The nls settings can be changed at mount time, if your smbmount
supports that, using the codepage and iocharset parameters.
smbmount from samba 2.2.0 or later supports this.
Default Remote NLS Option
CONFIG_SMB_NLS_REMOTE
This setting allows you to specify a default value for which
codepage the server uses. If this field is left blank no
translations will be done by default. The local codepage/charset
default to CONFIG_NLS_DEFAULT.
The nls settings can be changed at mount time, if your smbmount
supports that, using the codepage and iocharset parameters.
smbmount from samba 2.2.0 or later supports this.
Coda file system support (advanced network fs)
CONFIG_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
<file:Documentation/filesystems/coda.txt> and check out the Coda
home page <http://www.coda.cs.cmu.edu/>.
If you want to compile the coda client support as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want), say M here and read
<file:Documentation/modules.txt>. The module will be called coda.o.
InterMezzo file system support (replicating fs)
CONFIG_INTERMEZZO_FS
InterMezzo is a networked file system with disconnected operation
and kernel level write back caching. It is most often used for
replicating potentially large trees or keeping laptop/desktop copies
in sync.
If you say Y or M your kernel or module will provide InterMezzo
support. You will also need a file server daemon, which you can get
from <http://www.inter-mezzo.org/>.
NCP file system support (to mount NetWare volumes)
CONFIG_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
<file:Documentation/filesystems/ncpfs.txt> in the kernel source and
the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
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 <http://www.eats.com/linux_mac_win.html>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called ncpfs.o. Say N unless you are connected to a Novell
network.
Packet signatures
CONFIG_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
CONFIG_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
CONFIG_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
CONFIG_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
CONFIG_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 on LONG namespace volume
CONFIG_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"
below.
Use Native Language Support
CONFIG_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.
Symbolic links and mode permission bits
CONFIG_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.
Default NLS Option
CONFIG_NLS_DEFAULT
The default NLS used when mounting file system. Note, that this is
the NLS used by your console, not the NLS used by a specific file
system (if different) to store data (filenames) on a disk.
Currently, the valid values are:
big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
cp949, cp950, cp1250, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1,
iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7,
iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15,
koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8.
If you specify a wrong value, it will use the built-in NLS;
compatible with iso8859-1.
If unsure, specify it as "iso8859-1".
Codepage 437 (United States, Canada)
CONFIG_NLS_CODEPAGE_437
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
in so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used in
the United States and parts of Canada. This is recommended.
Codepage 737 (Greek)
CONFIG_NLS_CODEPAGE_737
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
in so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used for
Greek. If unsure, say N.
Codepage 775 (Baltic Rim)
CONFIG_NLS_CODEPAGE_775
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
in so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used
for the Baltic Rim Languages (Latvian and Lithuanian). If unsure,
say N.
Codepage 850 (Europe)
CONFIG_NLS_CODEPAGE_850
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used for
much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
more countries here]. It has some characters useful to many European
languages that are not part of the US codepage 437.
If unsure, say Y.
Codepage 852 (Central/Eastern Europe)
CONFIG_NLS_CODEPAGE_852
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the Latin 2 codepage used by DOS
for much of Central and Eastern Europe. It has all the required
characters for these languages: Albanian, Croatian, Czech, English,
Finnish, Hungarian, Irish, German, Polish, Rumanian, Serbian (Latin
transcription), Slovak, Slovenian, and Serbian.
Codepage 855 (Cyrillic)
CONFIG_NLS_CODEPAGE_855
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Cyrillic.
Codepage 857 (Turkish)
CONFIG_NLS_CODEPAGE_857
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Turkish.
Codepage 860 (Portuguese)
CONFIG_NLS_CODEPAGE_860
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Portuguese.
Codepage 861 (Icelandic)
CONFIG_NLS_CODEPAGE_861
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Icelandic.
Codepage 862 (Hebrew)
CONFIG_NLS_CODEPAGE_862
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Hebrew.
Codepage 863 (Canadian French)
CONFIG_NLS_CODEPAGE_863
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Canadian
French.
Codepage 864 (Arabic)
CONFIG_NLS_CODEPAGE_864
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Arabic.
Codepage 865 (Norwegian, Danish)
CONFIG_NLS_CODEPAGE_865
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for the Nordic
European countries.
Codepage 866 (Cyrillic/Russian)
CONFIG_NLS_CODEPAGE_866
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for
Cyrillic/Russian.
Codepage 869 (Greek)
CONFIG_NLS_CODEPAGE_869
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Greek.
Thai charset (CP874, TIS-620)
CONFIG_NLS_CODEPAGE_874
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Thai.
Windows CP1251 (Bulgarian, Belarusian)
CONFIG_NLS_CODEPAGE_1251
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Russian and
Bulgarian and Belarusian.
Japanese charsets (Shift-JIS, EUC-JP)
CONFIG_NLS_CODEPAGE_932
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Shift-JIS
or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
NLS Default value during kernel configuration, instead of 'cp932'.
Simplified Chinese charset (CP936, GB2312)
CONFIG_NLS_CODEPAGE_936
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Simplified
Chinese(GBK).
Korean charset (CP949, EUC-KR)
CONFIG_NLS_CODEPAGE_949
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for UHC.
Traditional Chinese charset (Big5)
CONFIG_NLS_CODEPAGE_950
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Traditional
Chinese(Big5).
Central European (Codepage 1250)
CONFIG_NLS_CODEPAGE_1250
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CDROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Windows CP-1250
character set, which works for most Latin-written Slavic and Central
European languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
Slovak, Slovene.
NLS ISO 8859-1 (Latin 1; Western European Languages)
CONFIG_NLS_ISO8859_1
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 1 character
set, which covers most West European languages such as Albanian,
Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
and Swedish. It is also the default for the US. If unsure, say Y.
NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)
CONFIG_NLS_ISO8859_2
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 2 character
set, which works for most Latin-written Slavic and Central European
languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
Slovak, Slovene.
NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)
CONFIG_NLS_ISO8859_3
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 3 character
set, which is popular with authors of Esperanto, Galician, Maltese,
and Turkish.
NLS ISO 8859-4 (Latin 4; old Baltic charset)
CONFIG_NLS_ISO8859_4
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 4 character
set which introduces letters for Estonian, Latvian, and
Lithuanian. It is an incomplete predecessor of Latin 7.
NLS ISO 8859-5 (Cyrillic)
CONFIG_NLS_ISO8859_5
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-5, a Cyrillic
character set with which you can type Bulgarian, Belarusian,
Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
KOI8-R is preferred in Russia.
NLS ISO 8859-6 (Arabic)
CONFIG_NLS_ISO8859_6
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-6, the Arabic
character set.
NLS ISO 8859-7 (Modern Greek)
CONFIG_NLS_ISO8859_7
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-7, the Modern
Greek character set.
Hebrew charsets (ISO-8859-8, CP1255)
CONFIG_NLS_ISO8859_8
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-8, the Hebrew
character set.
NLS ISO 8859-9 (Latin 5; Turkish)
CONFIG_NLS_ISO8859_9
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 5 character
set, and it replaces the rarely needed Icelandic letters in Latin 1
with the Turkish ones. Useful in Turkey.
NLS ISO 8859-10 (Latin 6; Nordic)
CONFIG_NLS_ISO8859_10
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 6 character
set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
letters that were missing in Latin 4 to cover the entire Nordic
area.
NLS ISO 8859-13 (Latin 7; Baltic)
CONFIG_NLS_ISO8859_13
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 7 character
set, which supports modern Baltic languages including Latvian
and Lithuanian.
NLS ISO 8859-14 (Latin 8; Celtic)
CONFIG_NLS_ISO8859_14
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 8 character
set, which adds the last accented vowels for Welsh (aka Cymraeg)
(and Manx Gaelic) that were missing in Latin 1.
<http://linux.speech.cymru.org/> has further information.
NLS ISO 8859-15 (Latin 9; Western European languages with Euro)
CONFIG_NLS_ISO8859_15
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 9 character
set, which covers most West European languages such as Albanian,
Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
French, German, Galician, Irish, Icelandic, Italian, Norwegian,
Portuguese, Spanish, and Swedish. Latin 9 is an update to
Latin 1 (ISO 8859-1) that removes a handful of rarely used
characters and instead adds support for Estonian, corrects the
support for French and Finnish, and adds the new Euro character.
If unsure, say Y.
NLS KOI8-R (Russian)
CONFIG_NLS_KOI8_R
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the preferred Russian
character set.
NLS KOI8-U/RU (Ukrainian, Belarusian)
CONFIG_NLS_KOI8_U
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the preferred Ukrainian
(koi8-u) and Belarusian (koi8-ru) character sets.
NLS UTF8
CONFIG_NLS_UTF8
If you want to display filenames with native language characters
from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the UTF-8 encoding of
the Unicode/ISO9646 universal character set.
Virtual terminal
CONFIG_VT
If you say Y here, you will get support for terminal devices with
display and keyboard devices. These are called "virtual" because you
can run several virtual terminals (also called virtual consoles) on
one physical terminal. This is rather useful, for example one
virtual terminal can collect system messages and warnings, another
one can be used for a text-mode user session, and a third could run
an X session, all in parallel. Switching between virtual terminals
is done with certain key combinations, usually Alt-<function key>.
The setterm command ("man setterm") can be used to change the
properties (such as colors or beeping) of a virtual terminal. The
man page console_codes(4) ("man console_codes") contains the special
character sequences that can be used to change those properties
directly. The fonts used on virtual terminals can be changed with
the setfont ("man setfont") command and the key bindings are defined
with the loadkeys ("man loadkeys") command.
You need at least one virtual terminal device in order to make use
of your keyboard and monitor. Therefore, only people configuring an
embedded system would want to say N here in order to save some
memory; the only way to log into such a system is then via a serial
or network connection.
If unsure, say Y, or else you won't be able to do much with your new
shiny Linux system :-)
Support for console on virtual terminal
CONFIG_VT_CONSOLE
The system console is the device which receives all kernel messages
and warnings and which allows logins in single user mode. If you
answer Y here, a virtual terminal (the device used to interact with
a physical terminal) can be used as system console. This is the most
common mode of operations, so you should say Y here unless you want
the kernel messages be output only to a serial port (in which case
you should say Y to "Console on serial port", below).
If you do say Y here, by default the currently visible virtual
terminal (/dev/tty0) will be used as system console. You can change
that with a kernel command line option such as "console=tty3" which
would use the third virtual terminal as system console. (Try "man
bootparam" or see the documentation of your boot loader (lilo or
loadlin) about how to pass options to the kernel at boot time.)
If unsure, say Y.
STI console
CONFIG_STI_CONSOLE
The STI console is the builtin display/keyboard on HP-PARISC
machines. Say Y here to build support for it into your kernel.
The alternative is to use your primary serial port as a console.
Use MDIO for PHY configuration
CONFIG_USE_MDIO
On some boards the hardware configuration of the ethernet PHY can be
used without any software interaction over the MDIO interface, so
all MII code can be omitted. Say N here if unsure or if you don't
need link status reports.
860T FEC Ethernet
CONFIG_FEC_ENET
Enable Ethernet support via the Fast Ethernet Controller (FCC) on
the Motorola MPC8260.
Ethernet on FCC1
CONFIG_FCC1_ENET
Use MPC8260 fast Ethernet controller 1 to drive Ethernet (default).
Ethernet on FCC2
CONFIG_FCC2_ENET
Use MPC8260 fast Ethernet controller 2 to drive Ethernet.
Ethernet on FCC3
CONFIG_FCC3_ENET
Use MPC8260 fast Ethernet controller 3 to drive Ethernet.
CPM SCC Ethernet
CONFIG_SCC_ENET
Enable Ethernet support via the Motorola MPC8xx serial
communications controller.
# Choice: scc_ethernet
Ethernet on SCC1
CONFIG_SCC1_ENET
Use MPC8xx serial communications controller 1 to drive Ethernet
(default).
Ethernet on SCC2
CONFIG_SCC2_ENET
Use MPC8xx serial communications controller 2 to drive Ethernet.
Ethernet on SCC3
CONFIG_SCC3_ENET
Use MPC8xx serial communications controller 3 to drive Ethernet.
Use Big CPM Ethernet Buffers
CONFIG_ENET_BIG_BUFFERS
Allocate large buffers for MPC8xx Ethernet. Increases throughput
and decreases the likelihood of dropped packets, but costs memory.
Apple Desktop Bus (ADB) support
CONFIG_ADB
Apple Desktop Bus (ADB) support is for support of devices which
are connected to an ADB port. ADB devices tend to have 4 pins.
If you have an Apple Macintosh prior to the iMac, or a
"Blue and White G3", you probably want to say Y here. Otherwise
say N.
Support for CUDA based PowerMacs
CONFIG_ADB_CUDA
This provides support for CUDA based Power Macintosh systems. This
includes most OldWorld PowerMacs, the first generation iMacs, the
Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
should use CONFIG_ADB_PMU instead.
If unsure say Y.
Support for PMU-based PowerMacs
CONFIG_ADB_PMU
This provides support for PMU based Power Macintosh systems. This
includes all PowerBooks and all AGP-based machines.
If unsure say Y.
Include MacIO ADB driver
CONFIG_ADB_MACIO
Say Y here to include direct support for the ADB controller in the
Hydra chip used on PowerPC Macintoshes of the CHRP type. (The Hydra
also includes a MESH II SCSI controller, DBDMA controller, VIA chip,
OpenPIC controller and two RS422/Geoports.)
Support for ADB keyboard (old driver)
CONFIG_ADB_KEYBOARD
This option allows you to use an ADB keyboard attached to your
machine. Note that this disables any other (ie. PS/2) keyboard
support, even if your machine is physically capable of using both at
the same time.
If you use an ADB keyboard (4 pin connector), say Y here.
If you use a PS/2 keyboard (6 pin connector), say N here.
HIL keyboard support
CONFIG_HIL
The "Human Interface Loop" is a older, 8-channel USB-like controller
used in Hewlett Packard PA-RISC based machines. There are a few
cases where it is seen on PC/MAC architectures as well, usually also
manufactured by HP. This driver is based off MACH and BSD drivers,
and implements support for a keyboard attached to the HIL port.
Full support for the USB-like functions and non-keyboard channels of
the HIL is not provided for in this driver. There are vestiges of
mouse support in the driver, but it is probably not working. The
necessary hardware documentation to fully support the HIL controller
and interface it to the linux-input API is lacking.
Enable this option if you intend to use a HIL keyboard.
Include IOP (IIfx/Quadra 9x0) ADB driver
CONFIG_ADB_IOP
The I/O Processor (IOP) is an Apple custom IC designed to provide
intelligent support for I/O controllers. It is described at
<http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
support for it, say 'Y' here.
Mac II style Apple Desktop Bus support
CONFIG_ADB_MACII
Say Y here if want your kernel to support Macintosh systems that use
the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
Centris 650.
Mac IIsi style Apple Desktop Bus support
CONFIG_ADB_MACIISI
Say Y here if want your kernel to support Macintosh systems that use
the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
II, LC, LC II, LC III, Performa 460, and the Performa 600.
Apple 68K PowerBook Power Management and Desktop Bus support
CONFIG_ADB_PMU68K
Say Y here if want your kernel to support the m68k based Powerbooks.
This includes the PowerBook 140, PowerBook 145, PowerBook 150,
PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
Macintosh IIfx/Quadra 900/Quadra 950 floppy support
CONFIG_BLK_DEV_SWIM_IOP
Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
floppy controller on the Macintosh IIfx and Quadra 900/950.
Macintosh NS8390 based Ethernet support
CONFIG_MAC8390
If you want to include a driver to support Nubus or LC-PDS
Ethernet cards using an NS8390 chipset or its equivalent, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Macintosh CS89x0 based Ethernet support
CONFIG_MAC89x0
Support for CS89x0 chipset based Ethernet cards. If you have a
Nubus or LC-PDS network (Ethernet) card of this type, say Y and
read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt> as well as
<file:Documentation/networking/net-modules.txt>. This module will
be called mac89x0.o.
Macintosh onboard AMD 79C940 MACE based Ethernet support
CONFIG_MACMACE
Support for the onboard AMD 79C940 MACE Ethernet controller used in
the 660AV and 840AV Macintosh. If you have one of these Macintoshes
say Y and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Macintosh SONIC based Ethernet support (onboard, NuBus, LC, CS)
CONFIG_MACSONIC
Support for NatSemi SONIC based Ethernet devices. This includes
the onboard Ethernet in many Quadras as well as some LC-PDS,
a few Nubus and all known Comm Slot Ethernet cards. If you have
one of these say Y and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt> as well as
<file:Documentation/networking/net-modules.txt>. This module will
be called macsonic.o.
Macintosh NCR5380 SCSI support
CONFIG_MAC_SCSI
This is the NCR 5380 SCSI controller included on most of the 68030
based Macintoshes. If you have one of these say Y and read the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Macintosh NCR53c9[46] SCSI support
CONFIG_SCSI_MAC_ESP
This is the NCR 53c9x SCSI controller found on most of the 68040
based Macintoshes. If you have one of these say Y and read the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mac_esp.o. If you want to compile it as
a module, say M here and read <file:Documentation/modules.txt>.
Standard/generic (8250/16550 and compatible UARTs) serial support
CONFIG_SERIAL
This selects whether you want to include the driver for the standard
serial ports. The standard answer is Y. People who might say N
here are those that are setting up dedicated Ethernet WWW/FTP
servers, or users that have one of the various bus mice instead of a
serial mouse and don't intend to use their machine's standard serial
port for anything. (Note that the Cyclades and Stallion multi
serial port drivers do not need this driver built in for them to
work.)
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
serial.o.
[WARNING: Do not compile this driver as a module if you are using
non-standard serial ports, since the configuration information will
be lost when the driver is unloaded. This limitation may be lifted
in the future.]
BTW1: If you have a mouseman serial mouse which is not recognized by
the X window system, try running gpm first.
BTW2: If you intend to use a software modem (also called Winmodem)
under Linux, forget it. These modems are crippled and require
proprietary drivers which are only available under Windows.
Most people will say Y or M here, so that they can use serial mice,
modems and similar devices connecting to the standard serial ports.
Support for console on serial port
CONFIG_SERIAL_CONSOLE
If you say Y here, it will be possible to use a serial port as the
system console (the system console is the device which receives all
kernel messages and warnings and which allows logins in single user
mode). This could be useful if some terminal or printer is connected
to that serial port.
Even if you say Y here, the currently visible virtual console
(/dev/tty0) will still be used as the system console by default, but
you can alter that using a kernel command line option such as
"console=ttyS1". (Try "man bootparam" or see the documentation of
your boot loader (lilo or loadlin) about how to pass options to the
kernel at boot time.)
If you don't have a VGA card installed and you say Y here, the
kernel will automatically use the first serial line, /dev/ttyS0, as
system console.
If unsure, say N.
Support for PowerMac serial ports
CONFIG_MAC_SERIAL
If you have Macintosh style serial ports (8 pin mini-DIN), say Y
here. If you also have regular serial ports and enable the driver
for them, you can't currently use the serial console feature.
Comtrol Rocketport support
CONFIG_ROCKETPORT
This is a driver for the Comtrol Rocketport cards which provide
multiple serial ports. You would need something like this to connect
more than two modems to your Linux box, for instance in order to
become a dial-in server.
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
rocket.o.
Digiboard Intelligent async support
CONFIG_DIGIEPCA
This is a driver for Digi International's Xx, Xeve, and Xem series
of cards which provide multiple serial ports. You would need
something like this to connect more than two modems to your Linux
box, for instance in order to become a dial-in server. This driver
supports the original PC (ISA) boards as well as PCI, and EISA. If
you have a card like this, say Y here and read the file
<file:Documentation/digiepca.txt>.
NOTE: There is another, separate driver for the Digiboard PC boards:
"Digiboard PC/Xx Support" below. You should (and can) only select
one of the two drivers.
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called epca.o.
Digiboard PC/Xx Support
CONFIG_DIGI
This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
that give you many serial ports. You would need something like this
to connect more than two modems to your Linux box, for instance in
order to become a dial-in server. If you have a card like that, say
Y here and read the file <file:Documentation/digiboard.txt>.
If you want to compile this driver as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called pcxx.o.
SDL RISCom/8 card support
CONFIG_RISCOM8
This is a driver for the SDL Communications RISCom/8 multiport card,
which gives you many serial ports. You would need something like
this to connect more than two modems to your Linux box, for instance
in order to become a dial-in server. If you have a card like that,
say Y here and read the file <file:Documentation/riscom8.txt>.
Also it's possible to say M here and compile this driver as kernel
loadable module; the module will be called riscom8.o.
Computone IntelliPort Plus serial support
CONFIG_COMPUTONE
This driver supports the entire family of Intelliport II/Plus
controllers with the exception of the MicroChannel controllers and
products previous to the Intelliport II. These are multiport cards,
which give you many serial ports. You would need something like this
to connect more than two modems to your Linux box, for instance in
order to become a dial-in server. If you have a card like that, say
Y here and read <file:Documentation/computone.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. You will get
two modules called ip2.o and ip2main.o.
Specialix IO8+ card support
CONFIG_SPECIALIX
This is a driver for the Specialix IO8+ multiport card (both the
ISA and the PCI version) which gives you many serial ports. You
would need something like this to connect more than two modems to
your Linux box, for instance in order to become a dial-in server.
If you have a card like that, say Y here and read the file
<file:Documentation/specialix.txt>. Also it's possible to say M here
and compile this driver as kernel loadable module which will be
called specialix.o.
Specialix DTR/RTS pin is RTS
CONFIG_SPECIALIX_RTSCTS
The Specialix IO8+ card can only support either RTS or DTR. If you
say N here, the driver will use the pin as "DTR" when the tty is in
software handshake mode. If you say Y here or hardware handshake is
on, it will always be RTS. Read the file
<file:Documentation/specialix.txt> for more information.
Specialix RIO system support
CONFIG_RIO
This is a driver for the Specialix RIO, a smart serial card which
drives an outboard box that can support up to 128 ports. Product
information is at <http://www.sphinxcst.co.uk/perle/multi.htm>.
There are both ISA and PCI versions.
Support really old RIO/PCI cards
CONFIG_RIO_OLDPCI
Older RIO PCI cards need some initialization-time configuration to
determine the IRQ and some control addresses. If you have a RIO and
this doesn't seem to work, try setting this to Y.
Cyclades async mux support
CONFIG_CYCLADES
This is a driver for a card that gives you many serial ports. You
would need something like this to connect more than two modems to
your Linux box, for instance in order to become a dial-in server.
For information about the Cyclades-Z card, read
<file:drivers/char/README.cycladesZ>.
As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
of 32.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called cyclades.o.
If you haven't heard about it, it's safe to say N.
Cyclades-Z interrupt mode operation
CONFIG_CYZ_INTR
The Cyclades-Z family of multiport cards allows 2 (two) driver op
modes: polling and interrupt. In polling mode, the driver will check
the status of the Cyclades-Z ports every certain amount of time
(which is called polling cycle and is configurable). In interrupt
mode, it will use an interrupt line (IRQ) in order to check the
status of the Cyclades-Z ports. The default op mode is polling. If
unsure, say N.
Stallion multiport serial support
CONFIG_STALDRV
Stallion cards give you many serial ports. You would need something
like this to connect more than two modems to your Linux box, for
instance in order to become a dial-in server. If you say Y here,
you will be asked for your specific card model in the next
questions. Make sure to read <file:Documentation/stallion.txt> in
this case. If you have never heard about all this, it's safe to
say N.
Stallion EasyIO or EC8/32 support
CONFIG_STALLION
If you have an EasyIO or EasyConnection 8/32 multiport Stallion
card, then this is for you; say Y. Make sure to read
<file:Documentation/stallion.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called stallion.o.
Stallion EC8/64, ONboard, Brumby support
CONFIG_ISTALLION
If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
serial multiport card, say Y here. Make sure to read
<file:Documentation/stallion.txt>.
To compile it as a module ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt>. The module will be called
istallion.o.
Microgate SyncLink adapter support
CONFIG_SYNCLINK
Provides support for the SyncLink ISA and PCI multiprotocol serial
adapters. These adapters support asynchronous and HDLC bit
synchronous communication up to 10Mbps (PCI adapter).
This driver can only be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called synclink.o. If you want to do that, say M
here.
CONFIG_SYNCLINKMP
Enable support for the SyncLink Multiport (2 or 4 ports)
serial adapter, running asynchronous and HDLC communications up
to 2.048Mbps. Each ports is independently selectable for
RS-232, V.35, RS-449, RS-530, and X.21
This driver may be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called synclinkmp.o. If you want to do that, say M
here.
Synchronous HDLC line discipline support
CONFIG_N_HDLC
Allows synchronous HDLC communications with tty device drivers that
support synchronous HDLC such as the Microgate SyncLink adapter.
This driver can only be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called n_hdlc.o. If you want to do that, say M
here.
Specialix SX (and SI) card support
CONFIG_SX
This is a driver for the SX and SI multiport serial cards.
Please read the file <file:Documentation/sx.txt> for details.
This driver can only be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sx.o. If you want to do that, say M here.
Hayes ESP serial port support
CONFIG_ESPSERIAL
This is a driver which supports Hayes ESP serial ports. Both single
port cards and multiport cards are supported. Make sure to read
<file:Documentation/hayes-esp.txt>.
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
and read <file:Documentation/modules.txt>. The module will be
called esp.o. If unsure, say N.
Moxa Intellio support
CONFIG_MOXA_INTELLIO
Say Y here if you have a Moxa Intellio multiport serial card.
This driver can also be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called moxa.o. If you want to do that, say M
here.
Moxa SmartIO support
CONFIG_MOXA_SMARTIO
Say Y here if you have a Moxa SmartIO multiport serial card.
This driver can also be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mxser.o. If you want to do that, say M
here.
Multi-Tech multiport card support
CONFIG_ISI
This is a driver for the Multi-Tech cards which provide several
serial ports. The driver is experimental and can currently only be
built as a module ( = code which can be inserted in and removed from
the running kernel whenever you want). Please read
<file:Documentation/modules.txt>. The module will be called
isicom.o.
Unix98 PTY support
CONFIG_UNIX98_PTYS
A pseudo terminal (PTY) is a software device consisting of two
halves: a master and a slave. The slave device behaves identical to
a physical terminal; the master device is used by a process to
read data from and write data to the slave, thereby emulating a
terminal. Typical programs for the master side are telnet servers
and xterms.
Linux has traditionally used the BSD-like names /dev/ptyxx for
masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
has a number of problems. The GNU C library glibc 2.1 and later,
however, supports the Unix98 naming standard: in order to acquire a
pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
terminal is then made available to the process and the pseudo
terminal slave can be accessed as /dev/pts/<number>. What was
traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
The entries in /dev/pts/ are created on the fly by a virtual
file system; therefore, if you say Y here you should say Y to
"/dev/pts file system for Unix98 PTYs" as well.
If you want to say Y here, you need to have the C library glibc 2.1
or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
Read the instructions in <file:Documentation/Changes> pertaining to
pseudo terminals. It's safe to say N.
Maximum number of Unix98 PTYs in use (0-2048)
CONFIG_UNIX98_PTY_COUNT
The maximum number of Unix98 PTYs that can be used at any one time.
The default is 256, and should be enough for desktop systems. Server
machines which support incoming telnet/rlogin/ssh connections and/or
serve several X terminals may want to increase this: every incoming
connection and every xterm uses up one PTY.
When not in use, each additional set of 256 PTYs occupy
approximately 8 KB of kernel memory on 32-bit architectures.
Parallel printer support
CONFIG_PRINTER
If you intend to attach a printer to the parallel port of your Linux
box (as opposed to using a serial printer; if the connector at the
printer has 9 or 25 holes ["female"], then it's serial), say Y.
Also read the Printing-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
read <file:Documentation/modules.txt> and
<file:Documentation/parport.txt>. The module will be called lp.o.
If you have several parallel ports, you can specify which ports to
use with the "lp" kernel command line option. (Try "man bootparam"
or see the documentation of your boot loader (lilo or loadlin) about
how to pass options to the kernel at boot time.) The syntax of the
"lp" command line option can be found in <file:drivers/char/lp.c>.
If you have more than 8 printers, you need to increase the LP_NO
macro in lp.c and the PARPORT_MAX macro in parport.h.
Support for console on line printer
CONFIG_LP_CONSOLE
If you want kernel messages to be printed out as they occur, you
can have a console on the printer. This option adds support for
doing that; to actually get it to happen you need to pass the
option "console=lp0" to the kernel at boot time.
If the printer is out of paper (or off, or unplugged, or too
busy..) the kernel will stall until the printer is ready again.
By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
can make the kernel continue when this happens,
but it'll lose the kernel messages.
If unsure, say N.
Support for user-space parallel port device drivers
CONFIG_PPDEV
Saying Y to this adds support for /dev/parport device nodes. This
is needed for programs that want portable access to the parallel
port, for instance deviceid (which displays Plug-and-Play device
IDs).
This is the parallel port equivalent of SCSI generic support (sg).
It is safe to say N to this -- it is not needed for normal printing
or parallel port CD-ROM/disk support.
This support is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>. The module will be called
ppdev.o.
If unsure, say N.
Cobalt Networks support
CONFIG_COBALT
Support for Cobalt Networks x86-based servers.
Gen III (3000 series) system support
CONFIG_COBALT_GEN_III
This option enables support for the 3000 series of Cobalt Networks
systems. This includes the RaQ 3, RaQ 4, and Qube 3 product lines.
This platform uses an AMD K6-2 processor, an ALI M1541/1533 chipset,
an optional NCR 53c875 SCSI controller, and two Intel 82559ER or
National Semiconductor DP83815 NICs.
Getting this option wrong will likely result in a kernel that does
not boot. Selecting support for more than 1 system series will add
bloat to your kernel, but will not cause anything bad to happen.
If you have a Cobalt Networks System, but aren't sure what kind,
say Y here.
Gen V (5000 series) system support
CONFIG_COBALT_GEN_V
This option enables support for the 5000 series of Cobalt Networks
systems. This includes the RaQ XTR product line.
This platform uses Intel Pentium III Coppermine FCPGA CPUs, the
ServerWorks LE chipset (with registered ECC DIMMs only!), two
HighPoint HPT370 IDE controllers, and two National Semiconductor
DP83815 NICs.
Getting this option wrong will likely result in a kernel that does
not boot. Selecting support for more than 1 system series will add
bloat to your kernel, but will not cause anything bad to happen.
If you have a Cobalt Networks System, but aren't sure what kind,
say Y here.
Create legacy /proc files
CONFIG_COBALT_OLDPROC
This option forces some Cobalt Networks drivers to support legacy
files in /proc. Older versions of these drivers exported files
directly in /proc, as opposed to the newer /proc/cobalt. If you say
N to this option, the old filenames will no longer be exported.
Regardless of your selection here, files in /proc/cobalt will be
exported. Of course, you have to include support for /proc fs, too.
It is safe to say Y here.
Front panel LCD support
CONFIG_COBALT_LCD
This enables support for the Cobalt Networks front panel. This is
for the LCD panel and buttons. The primary method for connection is
via the parallel port (IO base 0x370), but newer systems use an
I2C bus.
If you have a Cobalt Networks system, you should say Y here.
Software controlled LED support
CONFIG_COBALT_LED
This enables support for the software-controlled LEDs on Cobalt
Networks systems. This includes the fault light and front panel
LEDs on the RaQ XTR, the lightbar on the Qube 3, and others.
If you have a Cobalt Networks system, you should say Y here.
Silicon serial number support
CONFIG_COBALT_SERNUM
This enables support for the on-board serial number on Cobalt
Networks systems. This is a universally-unique 64-bit serial
number. Some systems use a Dallas DS2401 chip, others have an I2C
based EEPROM.
If you select Y here, the files /proc/cobalt/hostid and
/proc/cobalt/serialnumber will be created. The hostid file contains
a 32 bit integer generated from the serial number, in binary form.
The serialnumber file contains the hexadecimal representation of the
serial number, in ASCII.
If you have a Cobalt Networks system, you should say Y here.
Chipset watchdog timer support
CONFIG_COBALT_WDT
This enables support for the watchdog timer built into Cobalt
chipsets. The timer wakes up periodically, to make find out if
system has hung, or disabled interrupts too long. The result of
detecting a hang is a hard reboot.
If you have a Cobalt Networks system, you should say Y here.
Thermal sensor support
CONFIG_COBALT_THERMAL
This enables support for the thermal sensor(s) built into Cobalt
Networks systems. This driver exports /proc/cobalt/thermal_sensors.
If you have a Cobalt Networks system, you should say Y here.
Fan tachometer support
CONFIG_COBALT_FANS
This enables support for the fan tachometers built into some Cobalt
Networks systems. This driver exports /proc/cobalt/faninfo. Some
Cobalt software depends on this feature, and enabling it does not
cause any risks.
If you have a Cobalt Networks system, you should say Y here, unless
you are absolutely sure.
Disk drive ruler support
CONFIG_COBALT_RULER
This enables support for the cobalt hard drive ruler, found on some
Cobalt systems, including the RaQ XTR. This is the device that
enables swapping of drives. It is not needed for basic disk
operation. Enabling this on a system with no ruler will have no
adverse effects.
If you have a Cobalt Networks system, you should say Y here,
unless you are absolutely sure.
IT8172G Sound
CONFIG_SOUND_IT8172
Say Y here to support the on-board sound generator on the Integrated
Technology Express, Inc. ITE8172 SBC. Vendor page at
<http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
board at <http://www.mvista.com/allies/semiconductor/ite.html>.
I2C support
CONFIG_I2C
I2C (pronounce: I-square-C) is a slow serial bus protocol used in
many micro controller applications and developed by Philips. SMBus,
or System Management Bus is a subset of the I2C protocol. More
information is contained in the directory <file:Documentation/i2c/>,
especially in the file called "summary" there.
Both I2C and SMBus are supported here. You will need this for
hardware sensors support, and also for Video For Linux support.
Specifically, if you want to use a BT848 based frame grabber/overlay
boards under Linux, say Y here and also to "I2C bit-banging
interfaces", below.
If you want I2C support, you should say Y here and also to the
specific driver for your bus adapter(s) below. If you say Y to
"/proc file system" below, you will then get a /proc interface which
is documented in <file:Documentation/i2c/proc-interface>.
This I2C support is also available as a module. If you want to
compile it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-core.o.
UltraSPARC-III bootbus i2c controller driver
CONFIG_BBC_I2C
The BBC devices on the UltraSPARC III have two I2C controllers. The
first I2C controller connects mainly to configuration PROMs (NVRAM,
CPU configuration, DIMM types, etc.). The second I2C controller
connects to environmental control devices such as fans and
temperature sensors. The second controller also connects to the
smartcard reader, if present. Say Y to enable support for these.
I2C bit-banging interfaces
CONFIG_I2C_ALGOBIT
This allows you to use a range of I2C adapters called bit-banging
adapters. Say Y if you own an I2C adapter belonging to this class
and then say Y to the specific driver for you adapter below.
This support is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-algo-bit.o.
Philips style parallel port adapter
CONFIG_I2C_PHILIPSPAR
This supports parallel-port I2C adapters made by Philips. Say Y if
you own such an adapter.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-philips-par.o.
Note that if you want support for different parallel port devices,
life will be much easier if you compile them all as modules.
ELV adapter
CONFIG_I2C_ELV
This supports parallel-port I2C adapters called ELV. Say Y if you
own such an adapter.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-elv.o.
Velleman K9000 adapter
CONFIG_I2C_VELLEMAN
This supports the Velleman K9000 parallel-port I2C adapter. Say Y
if you own such an adapter.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-velleman.o.
I2C PCF 8584 interfaces
CONFIG_I2C_ALGOPCF
This allows you to use a range of I2C adapters called PCF adapters.
Say Y if you own an I2C adapter belonging to this class and then say
Y to the specific driver for you adapter below.
This support is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-algo-pcf.o.
Elektor ISA card
CONFIG_I2C_ELEKTOR
This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
such an adapter.
This driver is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-elektor.o.
ITE I2C Algorithm
CONFIG_ITE_I2C_ALGO
This supports the use the ITE8172 I2C interface found on some MIPS
systems. Say Y if you have one of these. You should also say Y for
the ITE I2C peripheral driver support below.
This support is also available as a module. If you want to compile
it as a modules, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-algo-ite.o.
ITE I2C Adapter
CONFIG_ITE_I2C_ADAP
This supports the ITE8172 I2C peripheral found on some MIPS
systems. Say Y if you have one of these. You should also say Y for
the ITE I2C driver algorithm support above.
This support is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-adap-ite.o.
I2C device interface
CONFIG_I2C_CHARDEV
Say Y here to use i2c-* device files, usually found in the /dev
directory on your system. They make it possible to have user-space
programs use the I2C bus. Information on how to do this is
contained in the file <file:Documentation/i2c/dev-interface>.
This code is also available as a module. If you want to compile
it as a module, say M here and read
<file:Documentation/modules.txt>.
The module will be called i2c-dev.o.
I2C /proc interface (required for hardware sensors)
CONFIG_I2C_PROC
This provides support for i2c device entries in the /proc filesystem.
The entries will be found in /proc/sys/dev/sensors.
This code is also available as a module. If you want to compile
it as a module, say M here and read <file:Documentation/modules.txt>.
The module will be called i2c-proc.o.
Bus Mouse Support
CONFIG_BUSMOUSE
Say Y here if your machine has a bus mouse as opposed to a serial
mouse. Most people have a regular serial MouseSystem or
Microsoft mouse (made by Logitech) that plugs into a COM port
(rectangular with 9 or 25 pins). These people say N here.
If you have a laptop, you either have to check the documentation or
experiment a bit to find out whether the trackball is a serial mouse
or not; it's best to say Y here for you.
This is the generic bus mouse driver code. If you have a bus mouse,
you will have to say Y here and also to the specific driver for your
mouse below.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called busmouse.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
Mouse Support (not serial and bus mice)
CONFIG_MOUSE
This is for machines with a mouse which is neither a serial nor a
bus mouse. Examples are PS/2 mice (such as the track balls on some
laptops) and some digitizer pads. Most people have a regular serial
MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
COM port (rectangular with 9 or 25 pins). These people say N here.
If you have something else, read the Busmouse-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This HOWTO contains
information about all non-serial mice, not just bus mice.
If you have a laptop, you either have to check the documentation or
experiment a bit to find out whether the trackball is a serial mouse
or not; it's best to say Y here for you.
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 non-serial mice. If unsure, say Y.
Logitech busmouse support
CONFIG_LOGIBUSMOUSE
Logitech mouse connected to a proprietary interface card. It's
generally a round connector with 9 pins. Note that the newer mice
made by Logitech don't use the Logitech protocol anymore; for those,
you don't need this option. You want to read the Busmouse-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called busmouse.o. If you are unsure, say N and read the
HOWTO nevertheless: it will tell you what you have.
PS/2 mouse (aka "auxiliary device") support
CONFIG_PSMOUSE
The PS/2 mouse connects to a special mouse port that looks much like
the keyboard port (small circular connector with 6 pins). This way,
the mouse does not use any serial ports. This port can also be used
for other input devices like light pens, tablets, keypads. Compaq,
AST and IBM all use this as their mouse port on currently shipping
machines. The trackballs of some laptops are PS/2 mice also. In
particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
Although PS/2 mice are not technically bus mice, they are explained
in detail in the Busmouse-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
When using a PS/2 mouse, you can get problems if you want to use the
mouse both on the Linux console and under X. Using the "-R" option
of the Linux mouse managing program gpm (available from
<ftp://gnu.systemy.it/pub/gpm/>) solves this problem, or you can get
the "mconv2" utility from <ftp://ibiblio.org/pub/Linux/system/mouse/>.
C&T 82C710 mouse port support (as on TI Travelmate)
CONFIG_82C710_MOUSE
This is a certain kind of PS/2 mouse used on the TI Travelmate. If
you are unsure, try first to say N here and come back if the mouse
doesn't work. Read the Busmouse-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
PC110 digitizer pad support
CONFIG_PC110_PAD
This drives the digitizer pad on the IBM PC110 palmtop. It can turn
the digitizer pad into a PS/2 mouse emulation with tap gestures or
into an absolute pad.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called pc110pad.o.
Microsoft busmouse support
CONFIG_MS_BUSMOUSE
These animals (also called Inport mice) are connected to an
expansion board using a round connector with 9 pins. If this is what
you have, say Y and read the Busmouse-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you are unsure, say N and read the HOWTO nevertheless: it will
tell you what you have. Also be aware that several vendors talk
about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
count the pins on the connector.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called msbusmouse.o.
Apple Desktop Bus mouse support
CONFIG_ADBMOUSE
Say Y here if you have this type of bus mouse (4 pin connector) as
is common on Macintoshes. You may want to read the Busmouse-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called adbmouse.o.
ATIXL busmouse support
CONFIG_ATIXL_BUSMOUSE
This is a rare type of busmouse that is connected to the back of an
ATI video card. Say Y if you have one of those. Note however that
most mice by ATI are actually Microsoft busmice; you should say Y to
"Microsoft busmouse support" above if you have one of those. Read
the Busmouse-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/modules.txt>. The module
will be called atixlmouse.o.
If you are unsure, say N and read the HOWTO nevertheless: it will
tell you what you have.
QIC-02 tape support
CONFIG_QIC02_TAPE
If you have a non-SCSI tape drive like that, say Y. Or, if you want
to compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
and read <file:Documentation/modules.txt>. The module will be called
tpqic02.o.
iSeries Virtual Tape Support
CONFIG_VIOTAPE
If you are running Linux on an iSeries system and you want Linux
to read and/or write a tape drive owned by OS/400, say Y here.
Do you want runtime configuration for QIC-02
CONFIG_QIC02_DYNCONF
You can either configure this driver once and for all by editing a
header file (<file:include/linux/tpqic02.h>), in which case you
should say N, or you can fetch a program via anonymous FTP which is
able to configure this driver during runtime. The program to do
this is called 'qic02conf' and it is part of the
tpqic02-support-X.Y.tar.gz support package.
If you want to use the qic02conf program, say Y.
Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
CONFIG_FTAPE
If you have a tape drive that is connected to your floppy
controller, say Y here.
Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
"Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
controller of their own. These drives (and their companion
controllers) are also supported if you say Y here.
If you have a special controller (such as the CMS FC-10, FC-20,
Mountain Mach-II, or any controller that is based on the Intel 82078
FDC like the high speed controllers by Seagate and Exabyte and
Iomega's "Ditto Dash") you must configure it by selecting the
appropriate entries from the "Floppy tape controllers" sub-menu
below and possibly modify the default values for the IRQ and DMA
channel and the IO base in ftape's configuration menu.
If you want to use your floppy tape drive on a PCI-bus based system,
please read the file <file:drivers/char/ftape/README.PCI>.
The ftape kernel driver is also available as a runtime loadable
module ( = code which can be inserted in and removed from the
running kernel whenever you want). If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>. The
module will be called ftape.o.
Note that the Ftape-HOWTO is out of date (sorry) and documents the
older version 2.08 of this software but still contains useful
information. There is a web page with more recent documentation at
<http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page
always contains the latest release of the ftape driver and useful
information (backup software, ftape related patches and
documentation, FAQ). Note that the file system interface has
changed quite a bit compared to previous versions of ftape. Please
read <file:Documentation/ftape.txt>.
VFS interface for ftape
CONFIG_ZFTAPE
Normally, you want to say Y or M. DON'T say N here or you
WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
The ftape module itself no longer contains the routines necessary
to interface with the kernel VFS layer (i.e. to actually write data
to and read data from the tape drive). Instead the file system
interface (i.e. the hardware independent part of the driver) has
been moved to a separate module.
If you say M zftape will be compiled as a runtime loadable
module ( = code which can be inserted in and removed from the
running kernel whenever you want). In this case you should read
<file:Documentation/modules.txt>. The module will be called
zftape.o.
Regardless of whether you say Y or M here, an additional runtime
loadable module called `zft-compressor.o' which contains code to
support user transparent on-the-fly compression based on Ross
William's lzrw3 algorithm will be produced. If you have enabled the
kernel module loader (i.e. have said Y to "Kernel module loader
support", above) then `zft-compressor.o' will be loaded
automatically by zftape when needed.
Despite its name, zftape does NOT use compression by default. The
file <file:Documentation/ftape.txt> contains a short description of
the most important changes in the file system interface compared to
previous versions of ftape. The ftape home page
<http://www.instmath.rwth-aachen.de/~heine/ftape/> contains
further information.