patch-2.1.77 linux/Documentation/Configure.help
Next file: linux/Documentation/cdrom/00-INDEX
Previous file: linux/Documentation/00-INDEX
Back to the patch index
Back to the overall index
- Lines: 4377
- Date:
Wed Dec 31 11:38:59 1997
- Orig file:
v2.1.76/linux/Documentation/Configure.help
- Orig date:
Sun Dec 21 22:36:11 1997
diff -u --recursive --new-file v2.1.76/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -18,6 +18,9 @@
# is a work-in-progress effort of the Italian translation team,
# currently only for the 2.0 version of this file, maintained
# by rubini@linux.it.
+# - http://www.cs.net.pl/~cezar/Kernel is the beginning of a Polish
+# translation of the 2.0 version of this file, maintained by Cezar
+# Cichocki (cezar@cs.net.pl).
#
# Information about what a kernel is, what it does, how to patch and
# compile it and much more is contained in the Kernel-HOWTO, available
@@ -112,7 +115,7 @@
running kernel whenever you want). The module will be called
floppy.o. If you want to compile it as a module, say M here and read
Documentation/modules.txt.
-
+
RAM disk support
CONFIG_BLK_DEV_RAM
Saying Y here will allow you to use a portion of your RAM memory as
@@ -150,12 +153,18 @@
Network Block Device support
CONFIG_BLK_DEV_NBD
- Saying Y here will allow computer to serve as client for network
- block device - it will be able to use block devices exported by
- servers (mount filesystems on them etc.). It also allows you to run
- a block-device in userland (making server and client physicaly the same
- computer, communicating using loopback). Normal users say N
- here. Read Documentation/nbd.txt.
+ Saying Y here will allow your computer to serve as a client for
+ network block devices - it will be able to use block devices
+ exported by servers (mount filesystems on them etc.). Communication
+ between client and server works over TCP/IP networking, but to the
+ client program this is hidden: it looks like a regular local file
+ access to a special file such as /dev/nd0. It also allows you to run
+ a block-device in userland (making server and client physically the
+ same computer, communicating using loopback). 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 Documentation/modules.txt. The module will be called
+ nbd.o. Normal users say N here. Read Documentation/nbd.txt.
Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
CONFIG_BLK_DEV_IDE
@@ -163,11 +172,11 @@
interfaces, each being able to serve a "master" and a "slave"
device, for a combination of up to eight IDE disk/cdrom/tape/floppy
drives. Useful information about large (>540MB) IDE disks,
- soundcard IDE ports, module support, and other topics, is all
+ soundcard IDE ports, module support, and other topics, is
contained in Documentation/ide.txt. If you have one or more IDE
drives, say Y here. If your system has no IDE drives, or if memory
requirements are really tight, you could say N here, and select the
- Old harddisk driver instead to save about 13kB of memory in the
+ "Old harddisk driver" instead to save about 13kB of memory in the
kernel. To fine-tune IDE drive/interface parameters for improved
performance, look for the hdparm package at
sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/
@@ -248,18 +257,18 @@
Include IDE/ATAPI FLOPPY support
CONFIG_BLK_DEV_IDEFLOPPY
- If you have an IDE floppy drive which uses the ATAPI protocol, say Y.
- ATAPI is a new protocol used by IDE CDROM/tape/floppy drives,
- similar to the SCSI protocol. IDE floppy drives include the
- LS-120 and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported
- by this driver; support for PD-CD/CDR drives is available through
- the SCSI emulation). At boot time, the FLOPPY drive will be
- identified along with other IDE devices, as "hdb" or "hdc", or
- something similar. If you want to compile the driver 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 ide-floppy.o.
-
+ If you have an IDE floppy drive which uses the ATAPI protocol, say
+ Y. ATAPI is a new protocol used by IDE CDROM/tape/floppy drives,
+ similar to the SCSI protocol. IDE floppy drives include the LS-120
+ and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported by this
+ driver; support for PD-CD/CDR drives is available through the SCSI
+ emulation). At boot time, the FLOPPY drive will be identified along
+ with other IDE devices, as "hdb" or "hdc", or something similar. If
+ you want to compile the driver 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 ide-floppy.o.
+
SCSI emulation support
CONFIG_BLK_DEV_IDESCSI
This will provide SCSI host adapter emulation for IDE ATAPI devices,
@@ -316,14 +325,25 @@
Generic PCI bus-master DMA support
CONFIG_BLK_DEV_IDEDMA
If your PCI IDE controller is capable of bus-master DMA
- (Direct Memory Access) transfers (most newer systems),
- then you will want to enable this option to reduce CPU overhead.
+ (Direct Memory Access) transfers (most newer systems are),
+ then you will want to say Y here to reduce CPU overhead.
With this option, Linux will automatically enable DMA transfers
in most cases, noting this with "DMA" appended to the drive
identification info. You can also use the "hdparm" utility to
enable DMA for drives which were not enabled automatically.
You can get the latest version of the hdparm utility via anonymous
FTP from sunsite.unc.edu/pub/Linux/system/hardware/
+ It is safe to say Y to this question.
+
+ If your PCI system uses IDE drive(s) (as opposed to SCSI, say)
+ and is capable of bus-master DMA operation (most Pentium PCI
+ systems), you will want to enable this option to allow use of
+ bus-mastering DMA data transfers. Read the comments at the
+ beginning of drivers/block/idedma.c and Documentation/ide.txt.
+ You can get the latest version of the hdparm utility via
+ ftp (user: anonymous) from
+ sunsite.unc.edu/pub/Linux/kernel/patches/diskdrives/; it is
+ used to tune your harddisk.
It is safe to say Y to this question.
Other IDE chipset support
@@ -341,8 +361,9 @@
Certain older chipsets, including the Tekram 690CD, use a
single set of I/O ports at 0x1f0 to control up to four drives,
instead of the customary two drives per port. Support for this
- is enabled at runtime using the "ide0=four" kernel boot parameter.
-
+ can be enabled at runtime using the "ide0=four" kernel boot
+ parameter if you say Y here.
+
DTC-2278 support
CONFIG_BLK_DEV_DTC2278
This driver is enabled at runtime using the "ide0=dtc2278" kernel
@@ -368,17 +389,15 @@
"ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
and drivers/block/pdc4030.c files for more info.
-Tekram TRM290 support (EXPERIMENTAL)
CONFIG_BLK_DEV_TRM290
This driver adds support for bus master DMA transfers
using the Tekram TRM290 PCI IDE chip. Volunteers are
needed for further tweaking and development.
Please read the comments at the top of drivers/block/trm290.c.
-OPTi 82C621 support (EXPERIMENTAL)
+OPTi 82C621 enhanced support (EXPERIMENTAL)
CONFIG_BLK_DEV_OPTI621
- This driver allows use of hdparm to change the PIO timings
- for drives attached to an OPTi MIDE controller.
+ This is a driver for the OPTi 82C621 EIDE controller.
Please read the comments at the top of drivers/block/opti621.c.
NS87415 support (EXPERIMENTAL)
@@ -417,22 +436,166 @@
Documentation/modules.txt. The module will be called xd.o. It's
pretty unlikely that you have one of these: say N.
-SyQuest EZ parallel port disk support
-CONFIG_BLK_DEV_EZ
- If you have a parallel port version of SyQuest's EZ135 or EZ230
- removable media devices you can use this driver. Answer Y to build
- the driver into the kernel, or M if you would like to build it as a
- loadable module. The module will be called ez.o. Read the file
- linux/Documentation/ez.txt. It is possible to use several devices
- with a single common parallel port (e.g. printer and EZ135); it is
- safe to compile both drivers into the kernel.
+Parallel port IDE device support
+CONFIG_PARIDE
+ There are many external CD-ROM and disk devices that connect
+ through your computer's parallel port. Most of them are actually
+ IDE devices using a parallel port IDE adapter. This option enables
+ the PARIDE subsystem which contains drivers for many of these
+ external drives. Read linux/Documentation/paride.txt for more
+ information. If you have enabled the parallel port support general
+ configuration option, you may share a single port between your
+ printer and other parallel port devices. Answer Y to build PARIDE
+ support into your kernel, or M if you would like to build it as a
+ loadable module. If your parallel port support is in a loadable
+ module, you must build PARIDE as a module. If you built PARIDE
+ support into your kernel, you may still build the individual
+ protocol modules and high-level drivers as loadable modules. To
+ use the PARIDE support, you must have this module as well as at
+ least one protocol module and one high-level driver. If you build
+ this support as a module, it will be called paride.o.
+
+Parallel port IDE disks
+CONFIG_PARIDE_PD
+ This option enables the high-level driver for IDE-type disk devices
+ connected through a parallel port. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ parallel port IDE driver, otherwise you should answer M to build
+ it as a loadable module. The module will be called pd.o. You
+ must also have at least one parallel port protocol driver in your
+ system. Among the devices supported by this driver are the SyQuest
+ EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
+ hardrives from MicroSolutions.
+
+Parallel port ATAPI CD-ROMs
+CONFIG_PARIDE_PCD
+ This option enables the high-level driver for ATAPI CD-ROM devices
+ connected through a parallel port. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ parallel port ATAPI CD-ROM driver, otherwise you should answer M
+ to build it as a loadable module. The module will be called pcd.o.
+ You must also have at least one parallel port protocol driver in
+ your system. Among the devices supported by this driver are the
+ MicroSolutions backpack CD-ROM drives and the Freecom Power CD.
+
+Parallel port ATAPI disks
+CONFIG_PARIDE_PF
+ This option enable the high-level driver for ATAPI disk devices
+ connected through a parallel port. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ parallel port ATAPI disk driver, otherwise you should answer M
+ to build it as a loadable module. The module will be called pf.o.
+ You must also have at least one parallel port protocol driver in
+ your system. Among the devices supported by this driver are the
+ MicroSolutions backpack PD/CD drive and the Imation Superdisk
+ LS-120 drive.
+
+ATEN EH-100 protocol
+CONFIG_PARIDE_ATEN
+ This option enables support for the ATEN EH-100 parallel port IDE
+ protocol. This protocol is used in some inexpensive low performance
+ parallel port kits made in Hong Kong. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ protocol driver, otherwise you should answer M to build it as a
+ loadable module. The module will be called aten.o. You must also
+ have a high-level driver for the type of device that you want to
+ support.
+
+MicroSolutions backpack protocol
+CONFIG_PARIDE_BPCK
+ This option enables support for the MicroSolutions backpack
+ parallel port IDE protocol. If you chose to build PARIDE support
+ into your kernel, you may answer Y here to build in the protocol
+ driver, otherwise you should answer M to build it as a loadable
+ module. The module will be called bpck.o. You must also have
+ a high-level driver for the type of device that you want to support.
+
+DataStor Commuter protocol
+CONFIG_PARIDE_COMM
+ This option enables support for the Commuter parallel port IDE
+ protocol from DataStor. If you chose to build PARIDE support
+ into your kernel, you may answer Y here to build in the protocol
+ driver, otherwise you should answer M to build it as a loadable
+ module. The module will be called comm.o. You must also have
+ a high-level driver for the type of device that you want to support.
+
+DataStor EP-2000 protocol
+CONFIG_PARIDE_DSTR
+ This option enables support for the EP-2000 parallel port IDE
+ protocol from DataStor. If you chose to build PARIDE support
+ into your kernel, you may answer Y here to build in the protocol
+ driver, otherwise you should answer M to build it as a loadable
+ module. The module will be called dstr.o. You must also have
+ a high-level driver for the type of device that you want to support.
+
+Shuttle EPAT/EPEZ protocol
+CONFIG_PARIDE_EPAT
+ This option enables support for the EPAT parallel port IDE
+ protocol. EPAT is a parallel port IDE adapter manufactured by
+ Shuttle Technology and widely used in devices from major vendors
+ such as Hewlett-Packard, SyQuest, Imation and Avatar. If you
+ chose to build PARIDE support into your kernel, you may answer Y
+ here to build in the protocol driver, otherwise you should answer M
+ to build it as a loadable module. The module will be called epat.o.
+ You must also have a high-level driver for the type of device that
+ you want to support.
+
+Shuttle EPIA protocol
+CONFIG_PARIDE_EPIA
+ This option enables support for the (obsolete) EPIA parallel port
+ IDE protocol from Shuttle Technology. This adapter can still be found
+ in some no-name kits. If you chose to build PARIDE support into your
+ kernel, you may answer Y here to build in the protocol driver,
+ otherwise you should answer M to build it as a loadable module.
+ The module will be called epia.o. You must also have a high-level
+ driver for the type of device that you want to support.
+
+FreeCom power protocol
+CONFIG_PARIDE_FRPW
+ This option enables support for the Freecom power parallel port IDE
+ protocol. If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will be
+ called frpw.o. You must also have a high-level driver for the type
+ of device that you want to support.
+
+KingByte KBIC-951A/971A protocols
+CONFIG_PARIDE_KBIC
+ This option enables support for the KBIC-951A and KBIC-971A parallel
+ port IDE protocols from KingByte Information Corp. KingByte's adapters
+ appear in many no-name portable disk and CD-ROM products, especially
+ in Europe. If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you should
+ answer M to build it as a loadable module. The module will be called
+ kbic.o. You must also have a high-level driver for the type of device
+ that you want to support.
+
+OnSpec 90c20 protocol
+CONFIG_PARIDE_ON20
+ This option enables support for the (obsolete) 90c20 parallel port
+ IDE protocol from OnSpec (often marketted under the ValuStore brand
+ name). If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will
+ be called on20.o. You must also have a high-level driver for the
+ type of device that you want to support.
+
+OnSpec 90c26 protocol
+CONFIG_PARIDE_ON26
+ This option enables support for the 90c26 parallel port IDE protocol
+ from OnSpec Electronics (often marketted under the ValuStore brand
+ name). If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will
+ be called on26.o. You must also have a high-level driver for the
+ type of device that you want to support.
Multiple devices driver support
CONFIG_BLK_DEV_MD
This driver lets you combine several harddisk partitions into one
logical block device. Information about how and why to use it and the
necessary tools are available over ftp (user: anonymous) from
- sweet-smoke.ufr-info-p7.ibp.fr/pub/public/Linux in the md package
+ sweet-smoke.ufr-info-p7.ibp.fr/pub/Linux in the md package
and the md-FAQ. Please read drivers/block/README.md. If unsure, say
N.
@@ -463,13 +626,18 @@
A RAID-1 set consists of several disk drives which are exact copies
of each other. In the event of a mirror failure, the RAID driver
will continue to use the operational mirrors in the set, providing
- an error free MD device to the higher levels of the kernel. In
- a set with N drives, the available space is the capacity of a single
- drive, and the set protects against a failure of (N - 1) drives.
- raidtools, a set of user-space tools which create and maintain
- RAID1/4/5 sets, is available at:
+ an error free MD (multiple device) to the higher levels of the
+ kernel. In a set with N drives, the available space is the capacity
+ of a single drive, and the set protects against a failure of (N - 1)
+ drives. raidtools, a set of user-space tools which create and
+ maintain RAID1/4/5 sets, is available at:
ftp://ftp.kernel.org/pub/linux/daemons/raid
http://luthien.nuclecu.unam.mx/~miguel/raid
+ If you want to use such a RAID-1 set say Y. This code is also
+ available as a module called raid1.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
+ Documentation/modules.txt. If unsure, say Y.
RAID-4/RAID-5 mode
CONFIG_MD_RAID5
@@ -478,12 +646,17 @@
of a single drive. For a given sector (row) number, (N - 1) drives
contain data sectors, and one drive contains the parity protection.
For a RAID-4 set, the parity blocks are present on a single drive,
- while a RAID-5 set distributes the parity accross the drives in one
+ while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
raidtools, a set of user-space tools which create and maintain
RAID1/4/5 sets, is available at:
ftp://ftp.kernel.org/pub/linux/daemons/raid
http://luthien.nuclecu.unam.mx/~miguel/raid
+ If you want to use such a RAID-5 set, say Y. This code is also
+ available as a module called raid5.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
+ Documentation/modules.txt. If unsure, say Y.
Support for Deskstation RPC44
CONFIG_DESKSTATION_RPC44
@@ -561,30 +734,7 @@
kernel, you should consider updating your networking tools too
because changes in the kernel and the tools often go hand in hand;
see http://www.inka.de/sites/lina/linux/NetTools/index_en.html for
- details.
-
-Packet socket
-CONFIG_PACKET
- Packet protocol is used by applications directly communicating
- to network devices f.e. tcpdump. You want them to work, choose Y.
- If you run kerneld, you might want to choose M.
-
-Kernel/User netlink socket
-CONFIG_NETLINK
- This protocol family is used for bi-directional communication
- between kernel and user level daemons. This option is unlikely to
- be useful for common workstation, but if you configure router or
- firewall, do not hesitate: press Y.
-
-Routing messages
-CONFIG_RTNETLINK
- One of netlink protocols used by kernel routing engine.
- You will need it to use advanced routing features.
-
-Netlink device emulation
-CONFIG_NETLINK_DEV
- It is backward compatibility option, choose Y for now.
- This option will be removed soon.
+ details.
Network aliasing
CONFIG_NET_ALIAS
@@ -603,7 +753,7 @@
Socket filtering
CONFIG_FILTER
- The Linux Socket Filter is a deviation of the Berkely Packet Filter.
+ The Linux Socket Filter is derived from the Berkeley Packet Filter.
Through Socket Filtering you can have the kernel decide whether the
data is good and to continue processing it. Linux Socket Filtering
works on all socket types except TCP for now. See the text file
@@ -642,7 +792,7 @@
to continue to connect, even when your machine is under attack.
There is no need for the legitimate users to change their TCP/IP
software; SYN cookies work transparently to them. For technical
- information about syn cookies, check out
+ information about SYN cookies, check out
ftp://koobera.math.uic.edu/pub/docs/syncookies-archive.
If you say Y here, note that SYN cookies aren't enabled by default:
you need to add the command
@@ -781,11 +931,12 @@
PCI BIOS support
CONFIG_PCI_BIOS
- If you have enabled PCI bus support above, you probably want to allow
- Linux to use your PCI BIOS to detect the PCI devices and determine
- their configuration. Note: some old PCI motherboards have BIOS bugs
- and may crash if this switch is enabled -- for such motherboards,
- you should disable PCI BIOS support and use direct PCI access instead.
+ If you have enabled PCI bus support above, you probably want to
+ allow Linux to use your PCI BIOS to detect the PCI devices and
+ determine their configuration. Note: some old PCI motherboards have
+ BIOS bugs and may crash if this switch is enabled -- for such
+ motherboards, you should say N here and say Y to "PCI direct access
+ support" instead.
Except for some special cases (embedded systems with no BIOS), you
probably should say Y here.
@@ -801,9 +952,9 @@
PCI bridge optimization (experimental)
CONFIG_PCI_OPTIMIZE
This can improve access times for some hardware devices if you have
- a really broken BIOS and your computer uses a PCI bus system. Set to Y
- if you think it might help, but try turning it off if you experience
- any problems with the PCI bus.
+ a really broken BIOS and your computer uses a PCI bus system. Set to
+ Y if you think it might help, but try turning it off if you
+ experience any problems with the PCI bus. N is the safe answer.
MCA support
CONFIG_MCA
@@ -856,7 +1007,7 @@
http://www.sjc.ox.ac.uk/users/barlow/elf-howto.html (To browse the
WWW, you need to have access to a machine on the Internet that has a
programs like lynx or netscape). If you find that after upgrading
- to Linux kernel 1.3 and saying Y here, you still can't run any ELF
+ from Linux kernel 1.2 and saying Y here, you still can't run any ELF
binaries (they just crash), then you'll have to install the newest
ELF runtime libraries, including ld.so (check the file
Documentation/Changes for location and latest version). If you want
@@ -886,18 +1037,45 @@
because some crucial programs on your system might still be in A.OUT
format.
-Kernel support for JAVA binaries
+Kernel support for JAVA binaries (obsolete)
CONFIG_BINFMT_JAVA
- This option is obsolete. Use binfmt_misc instead. It is more
- flexible.
+ JAVA(tm) is an object oriented programming language developed by
+ SUN; JAVA programs are compiled into "JAVA bytecode" binaries which
+ can then be interpreted by run time systems on many different
+ operating systems. These JAVA binaries are becoming a universal
+ executable format. If you want to execute JAVA binaries, read the
+ Java on Linux HOWTO, available via ftp (user: anonymous) at
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. You will then need to install
+ the run time system contained in the Java Developers Kit (JDK) as
+ described in the HOWTO. This is completely independent of the Linux
+ kernel and you do NOT need to say Y here for this to work.
+ Saying Y here allows you to execute a JAVA bytecode binary just like
+ any other Linux program: by simply typing in its name. (You also
+ need to have the JDK installed for this to work). As more and more
+ Java programs become available, the use for this will gradually
+ increase. You can even execute HTML files containing JAVA applets (=
+ JAVA binaries) if those files start with the string
+ "<!--applet-->". If you want to use this, say Y here and read
+ Documentation/java.txt. If you disable this option it will reduce
+ your kernel by about 4kB. This is not much and by itself does not
+ warrant removing support. However its removal is a good idea if you
+ do not have the JDK installed. You may answer M for module support
+ and later load the module when you install the JDK or find an
+ interesting Java program that you can't live without. The module
+ will be called binfmt_java.o.
+ The complete functionality of this Java support is also provided by
+ the more general option "Kernel support for MISC binaries",
+ below. This option is therefore considered obsolete and you probably
+ want to say N here and Y to "Kernel support for MISC binaries" if
+ you're interested in Java.
Kernel support for Linux/Intel ELF binaries
CONFIG_BINFMT_EM86
Say Y here if you want to be able to execute Linux/Intel ELF
- binaries just like native Alpha binaries on your machine. For this
- to work, you need to have the emulator /usr/bin/em86 in place. You
- may answer M to compile the emulation support as a module and later
- load the module when you want to use a Linux/Intel binary. The
+ binaries just like native Alpha binaries on your Alpha machine. For
+ this to work, you need to have the emulator /usr/bin/em86 in place.
+ You may answer M to compile the emulation support as a module and
+ later load the module when you want to use a Linux/Intel binary. The
module will be called binfmt_em86.o. If unsure, say Y.
Kernel support for MISC binaries
@@ -919,6 +1097,15 @@
you have use for it.
If you don't know what to answer at this point, say Y.
+Solaris binary emulation
+CONFIG_SOLARIS_EMUL
+ This is experimental code which will enable you to run (many)
+ Solaris binaries on your Sparc Linux machine. 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 solaris.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt.
+
Processor family
CONFIG_M386
This is the processor type of your CPU. This information is used for
@@ -928,7 +1115,11 @@
then the kernel will run on all of these CPUs: 486 and Pentium
(=586) and Pentium Pro (=686). In rare cases, it can make sense to
specify "Pentium" even if running on a 486: the kernel will be
- smaller but slower. If you don't know what to do, say "386".
+ smaller but slower.
+ If you have a multiple processor machine and want Linux to use all
+ the processors in parallel, set the SMP variable in the toplevel
+ kernel Makefile.
+ If you don't know what to do, say "386".
Video mode selection support
CONFIG_VIDEO_SELECT
@@ -950,23 +1141,34 @@
If you want to use devices connected to your parallel port (the
connector at the computers with 25 holes), e.g. printer, Zip drive,
PLIP link etc., then you need to enable this option; please read
- Documentation/parport.txt and drivers/misc/BUGS-parport. It
- is possible to share a single parallel port among several devices
- and it is safe to compile all the corresponding drivers into the
- kernel. If you want to compile parallel port support 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 parport.o. If
- you have more than one parallel port and want to specify which port
- and IRQ to use by this driver at module load time, read
- Documentation/networking/net-modules.txt.
+ Documentation/parport.txt and drivers/misc/BUGS-parport. For
+ extensive information about drivers for many devices attaching to
+ the parallel port see http://www.torque.net/linux-pp.html on the WWW
+ (To browse the WWW, you need to have access to a machine on the
+ Internet that has a programs like lynx or netscape). It is possible
+ to share a single parallel port among several devices and it is safe
+ to compile all the corresponding drivers into the kernel. If you
+ want to compile parallel port support 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 parport.o. If you have more than one parallel port
+ and want to specify which port and IRQ to use by this driver at
+ module load time, read Documentation/networking/net-modules.txt.
PC-style hardware
CONFIG_PARPORT_PC
You should enable this option if you have a PC-style parallel
port. All IBM PC compatible computers and some Alphas have PC-style
- parallel ports. This driver is also available as a module which
- will be called parport_pc.o.
+ parallel ports. This code is also available as a module. If you
+ want to it 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 parport_pc.o.
+
+Sun Ultra/AX-style hardware
+CONFIG_PARPORT_AX
+ Say Y here if you need support for the parallel port hardware on Sun
+ Ultra/AX machines. This code is also available as a module (say M),
+ called parport_ax.o. If in doubt, saying N is the safe plan.
Compile the kernel into the ELF object format
CONFIG_ELF_KERNEL
@@ -996,9 +1198,9 @@
Auto-probe for parallel devices
CONFIG_PNP_PARPORT
- Some IEEE-1284 conformant parallel-port devices can identify themselves
- when requested. If this option is enabled the kernel will probe to see
- what devices are connected at boot time.
+ Some IEEE-1284 conformant parallel-port devices can identify
+ themselves when requested. Say Y to enable this feature, or M to
+ compile it as a module (parport_ieee1284.o). If in doubt, say N.
Plug and Play subsystem (EXPERIMENTAL)
CONFIG_PNP_DRV
@@ -1031,7 +1233,7 @@
Plug and Play ISA devices. This includes full support for PnP ISA,
including the I/O range check feature.
-PnP ISA backwards-compatiblity support
+PnP ISA backwards-compatibility support
CONFIG_PNP_ISA_COMPAT
This option will enable partial backwards compatibility with drivers
written using older versions (up to the last 0.2.x) of the PnP driver
@@ -1044,18 +1246,18 @@
These cards used somewhat proprietary mechanisms for configuring
IRQs, DMAs, IO addresses, and memory ranges. These devices (mainly
network cards, but also some sound card) can be configured as any
- other PnP device can by enabling this option, if appropriate drivers
+ other PnP device can by saying Y here, if appropriate drivers
for these devices are available.
PnP sysctl support (RECOMMENDED)
CONFIG_PNP_SYSCTL
This option enables support for the user-mode interface to the
- kernel-mode PnP systems. It requires that you enable CONFIG_SYSCTL.
- The only reason you might want to switch this off is if you aren't
- going to use user-mode utilities to configure PnP, and you want to
- save a couple of kilobytes of kernel space. Answer Y unless you know
- what you are doing. User-mode utilities and a library for accessing
- this interface may be found at
+ kernel-mode PnP systems. It requires that you said Y to "Sysctl
+ support" above. The only reason you might want to switch this off
+ is if you aren't going to use user-mode utilities to configure PnP,
+ and you want to save a couple of kilobytes of kernel space. Answer Y
+ unless you know what you are doing. User-mode utilities and a
+ library for accessing this interface may be found at
http://www.lpsg.demon.co.uk/pnp-linux.html.
PnP auto-configures all devices on startup
@@ -1082,10 +1284,10 @@
kernel. Saying Y here makes it possible, and safe, to use the
same modules even after compiling a new kernel; this requires the
program modprobe. All the software needed for module support is in
- the modules package (check the file Documentation/Changes for
+ the modutils package (check the file Documentation/Changes for
location and latest version). NOTE: if you say Y here but don't
have the program genksyms (which is also contained in the above
- mentioned modules package), then the building of your kernel will
+ mentioned modutils package), then the building of your kernel will
fail. If you are going to use modules that are generated from
non-kernel sources, you would benefit from this option. Otherwise
it's not that important. So, N ought to be a safe bet.
@@ -1100,7 +1302,7 @@
"kerneld" will also automatically unload all unused modules, so you
don't have to use "rmmod" either. kerneld will also provide support
for different user-level beeper and screen blanker programs later
- on. The "kerneld" daemon is included in the modules package (check
+ on. The "kerneld" daemon is included in the modutils package (check
Documentation/Changes for latest version and location). You will
probably want to read the kerneld mini-HOWTO, available via ftp
(user: anonymous) from
@@ -1150,17 +1352,80 @@
you need to have access to a machine on the Internet that has a
program like lynx or netscape). Information about the multicast
capabilities of the various network cards is contained in
- drivers/net/README.multicast. For most people, it's safe to say N.
+ Documentation/networking/multicast.txt. For most people, it's safe
+ to say N.
+
+IP: advanced router
+CONFIG_IP_ADVANCED_ROUTER
+ If you intend to run your Linux box mostly as a router, i.e. as a
+ computer that forwards and redistributes network packets, say Y; you
+ will then be presented with several options that allow more precise
+ control about the routing process.
+ The answer to this question won't directly affect the kernel: saying
+ N will just cause this configure script to skip all the questions
+ about advanced routing.
+ Note that your box can only act as a router if you say Y to "/proc
+ filesystem support" below and if you enable IP forwarding in your
+ kernel; you can do this from within a boot-time script like so:
+ echo "1" > /proc/sys/net/ipv4/ip_forwarding
+ after the /proc filesystem has been mounted.
+ If unsure, say N here.
+
+IP: policy routing
+CONFIG_IP_MULTIPLE_TABLES
+ Normally, a router decides what to do with a received packet based
+ solely on the packet's final destination address. If you say Y here,
+ routing can also take into account the originating address and the
+ network device from which the packet reached us.
+
+IP: equal cost multipath
+CONFIG_IP_ROUTE_MULTIPATH
+ Normally, the routing tables specify a single action to be taken in
+ a deterministic manner for a given packet. If you say Y here
+ however, it becomes possible to attach several actions to a packet
+ pattern, in effect specifying several alternative paths to travel
+ for those packets. The router considers all these paths to be of
+ equal "cost" and chooses one of them in a non-deterministic fashion
+ if a matching packet arrives.
+
+IP: use TOS value as routing key
+CONFIG_IP_ROUTE_TOS
+ The header of every IP packet carries a TOS (Type of Service) value
+ with which the packet requests a certain treatment, e.g. low latency
+ (for interactive traffic), high throughput, or high
+ reliability. Normally, these values are ignored, but if you say Y
+ here, you will be able to specify different routes for packets with
+ different TOS values.
+
+IP: verbose route monitoring
+CONFIG_IP_ROUTE_VERBOSE
+ If you say Y here, which is recommended, then the kernel will print
+ verbose messages regarding the routing, for example warnings about
+ received packets which look strange and could be evidence of an
+ attack or a misconfigured system somewhere. The information is
+ handled by the klogd demon which is responsible for kernel messages
+ ("man klogd").
+
+IP: large routing tables
+CONFIG_IP_ROUTE_LARGE_TABLES
+ If you have routing zones that grow to more than about 64 entries,
+ you may want to say Y here to speed up the routing process.
+
+IP: fast network address translation
+CONFIG_IP_ROUTE_NAT
+ If you say Y here, your router will be able to modify source and
+ destination addresses of packets that pass through it.
IP: optimize as router not host
CONFIG_IP_ROUTER
Some Linux network drivers use a technique called copy and checksum
- to optimize host performance. For a machine which is forwarding most
- packets to another host this is however a loss. This parameter turns
- off copy and checksum from devices. It may make other changes in the
- future.
+ to optimize host performance. For a machine which acts a router most
+ of the time and is forwarding most packets to another host this is
+ however a loss. If you say Y here, copy and checksum will be
+ switched off. In the future, it may make other changes which
+ optimize for router operation.
Note that your box can only act as a router if you say Y to "/proc
- filesystem support" below and you enable IP forwarding in your
+ filesystem support" below and if you enable IP forwarding in your
kernel; you can do this from within a boot-time script like so:
echo "1" > /proc/sys/net/ipv4/ip_forwarding
after the /proc filesystem has been mounted. If unsure, say N here.
@@ -1179,21 +1444,22 @@
support" below and IP forwarding is enabled in your kernel; do this
from within a boot-time script like so:
echo "1" > /proc/sys/net/ipv4/ip_forwarding
- after the /proc filesystem has been mounted. You need to say Y to
- "IP firewalling" in order to be able to use IP masquerading
- (i.e. local computers can chat with an outside host, but that
- outside host is made to think that it is talking to the firewall box
- -- makes the local network completely invisible and avoids the need
- to allocate valid IP host addresses for the machines on the local
- net) and IP packet accounting (keeping track of what is using all
- your network bandwidth) and IP transparent proxying (makes the
- computers on the local network think they're talking to a remote
- computer, while in reality the traffic is redirected by your Linux
- firewall to a local proxy server). If unsure, say N.
+ after the /proc filesystem has been mounted.
+ You need to say Y to "IP firewalling" in order to be able to use IP
+ masquerading (masquerading means that local computers can chat with
+ an outside host, but that outside host is made to think that it is
+ talking to the firewall box -- makes the local network completely
+ invisible and avoids the need to allocate valid IP host addresses
+ for the machines on the local net) and IP packet accounting (keeping
+ track of what is using all your network bandwidth) and IP
+ transparent proxying (makes the computers on the local network think
+ they're talking to a remote computer, while in reality the traffic
+ is redirected by your Linux firewall to a local proxy server). If
+ unsure, say N.
IP: firewall packet netlink device
CONFIG_IP_FIREWALL_NETLINK
- If you say Y here and when packets hit your Linux firewall and are
+ If you say Y here and then packets hit your Linux firewall and are
blocked, the first 128 bytes of each such packet are passed on to
optional user space monitoring software that can then look for
attacks and take actions such as paging the administrator of the
@@ -1219,8 +1485,8 @@
of the routing table during kernel boot, based on either information
supplied at the kernel command line or by BOOTP or RARP protocols.
You need to say Y only for diskless machines requiring network access
- to boot (see CONFIG_ROOT_NFS for more information about root volume
- mounted via NFS), because all other machines configure the network in
+ to boot (in which case you want to say Y to "Root file system on
+ NFS" as well), because all other machines configure the network in
their startup scripts.
BOOTP support
@@ -1265,18 +1531,22 @@
IP: GRE tunnels over IP
CONFIG_NET_IPGRE
- Another kind of tunneling protocol - "Generic Routing Encapsulation".
- It allows to tunnel any networking protocol over existing IPv4
- infrastructure. At the moment only IPv4 and IPv6 are supported.
- It is useful, if another endpoint is Cisco router: it likes
- GRE much more than IPIP and, particularly, allows multicasts
- redistribution over GRE tunnels.
+ Tunneling means encapsulating data of one protocol type within
+ another protocol and sending it over a channel that understands the
+ encapsulating protocol. This particular tunneling driver implements
+ GRE (Generic Routing Encapsulation) and at this time allows
+ encapsulating of IPv4 or IPv6 over existing IPv4
+ infrastructure. This driver is useful if the other endpoint is a
+ Cisco router: Cisco likes GRE much better than the other Linux
+ tunneling driver ("IP: tunneling" above). In addition, GRE allows
+ multicast redistribution through the tunnel.
IP: broadcast GRE over IP
CONFIG_NET_IPGRE_BROADCAST
- One application of GRE/IP, allowing to construct broadcast LAN,
- looking like ethernet network, distributed over the Internet.
- It requires, that your domain supported multicast routing.
+ One application of GRE/IP is to construct a broadcast WAN (Wide Area
+ Network), which looks like a normal1 ethernet LAN (Local Area
+ Network), but can be distributed all over the Internet. If you want
+ to do that, say Y here and to "IP: multicast routing" below.
IP: firewall packet logging
CONFIG_IP_FIREWALL_VERBOSE
@@ -1312,7 +1582,7 @@
Linux box to the Internet using SLiRP [SLiRP is a SLIP/PPP emulator
that works if you have a regular dial up shell account on some UNIX
computer; get it via ftp (user: anonymous) from
- ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/].) Details
+ ftp://sunsite.unc.edu/pub/Linux/system/network/serial/].) Details
on how to set things up are contained in the IP Masquerading FAQ,
available at http://www.indyramp.com/masq/. If you say Y here, then
the modules ip_masq_ftp.o (for ftp transfers through the firewall),
@@ -1324,23 +1594,27 @@
IP: ICMP masquerading
CONFIG_IP_MASQUERADE_ICMP
- The basic masquerade code described for CONFIG_IP_MASQUERADE only
+ The basic masquerade code described for "IP: masquerading" above only
handles TCP or UDP packets (and ICMP errors for existing
connections). This option adds additional support for masquerading
ICMP packets, such as ping or the probes used by the Windows 95
tracert program.
- If you want this, say Y.
+ If you want this, say Y.
IP: ipautofw masquerade support
CONFIG_IP_MASQUERADE_IPAUTOFW (Experimental)
- ipautofw is a program by Richard Lynch allowing additional
- support for masquerading protocols which do not (as yet)
- have additional protocol helpers.
- Information and source for ipautofw is available from
+ ipautofw is a program by Richard Lynch allowing additional support
+ for masquerading protocols which do not (as yet) have their own
+ additional protocol helpers. Information and source for ipautofw is
+ available via ftp (user: anonymous) from
ftp://ftp.netis.com/pub/members/rlynch/
The ipautofw code is still under development and so is currently
marked EXPERIMENTAL.
- If you want this, say Y.
+ If you want this, say Y. 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 ip_masq_autofw.o. If
+ you want to compile it as a module, say M here and read
+ Documentation/modules.txt.
IP: ipportfw masquerade support
CONFIG_IP_MASQUERADE_IPPORTFW
@@ -1348,10 +1622,16 @@
to allow some forwarding of packets from outside to inside a
firewall on given ports. Information and source for ipportfw is
available from
- http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html
+ http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to
+ browse the WWW, you need to have access to a machine on the Internet
+ that has a program like lynx or netscape).
The portfw code is still under development and so is currently
marked EXPERIMENTAL.
- If you want this, say Y.
+ If you want this, say Y. 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 ip_masq_portfw.o. If
+ you want to compile it as a module, say M here and read
+ Documentation/modules.txt.
IP: always defragment
CONFIG_IP_ALWAYS_DEFRAG
@@ -1397,23 +1677,26 @@
audio and video broadcasts. In order to do that, you would most
likely run the program mrouted. Information about the multicast
capabilities of the various network cards is contained in
- drivers/net/README.multicast. If you haven't heard about it, you
- don't need it.
+ Documentation/networking/multicast.txt. If you haven't heard about
+ it, you don't need it.
IP: PIM-SM version 1 support
CONFIG_IP_PIMSM_V1
- Kernel side support for Sparse Mode PIM version 1. This multicast
- routing protocol is used widely due to Cisco supports it.
- You need special software to use it (pimd-v1). Press N, if
- you do not want to use PIM-SM v1. Note, that Dense Mode PIM
- need not this option.
+ Kernel side support for Sparse Mode PIM (Protocol Independent
+ Multicast) version 1. This multicast routing protocol is used widely
+ because Cisco supports it. You need special software to use it
+ (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
+ information about PIM (to browse the WWW, you need to have access to
+ a machine on the Internet that has a program like lynx or
+ netscape). Say Y if you want to use PIM-SM v1. Note that you can say
+ N here if you just want to use Dense Mode PIM.
IP: PIM-SM version 2 support
CONFIG_IP_PIMSM_V2
- Kernel side support for Sparse Mode PIM version 2. You need
- experimental routing daemon supporting it (pimd or gated-5).
- This protocol is not used widely, so that press Y, if you
- do not want play with it.
+ Kernel side support for Sparse Mode PIM version 2. In order to use
+ this, you need an experimental routing daemon supporting it (pimd or
+ gated-5). This routing protocol is not used widely, so say N unless
+ you want to play with it.
PC/TCP compatibility mode
CONFIG_INET_PCTCP
@@ -1435,16 +1718,18 @@
rarp ("man rarp") on your box. If you actually want to use a
diskless Sun 3 machine as an Xterminal to Linux, say Y here and
fetch Linux-Xkernel from
- ftp://sunsite.unc.edu/pub/Linux/system/Network/boot.net/. Superior
+ ftp://sunsite.unc.edu/pub/Linux/system/network/boot.net/. Superior
solutions to the problem of booting and configuring machines over a
net connection are given by the protocol BOOTP and its successor
DHCP. See the DHCP FAQ
- http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details. If
- you want to compile RARP support 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 rarp.o. If you don't understand a word of the above, say N
- and rest in peace.
+ http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details (to
+ browse the WWW, you need to have access to a machine on the Internet
+ that has a program like lynx or netscape). If you want to compile
+ RARP support 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 rarp.o.
+ If you don't understand a word of the above, say N and rest in
+ peace.
Assume subnets are local
CONFIG_INET_SNARL
@@ -1517,10 +1802,16 @@
Unix domain sockets
CONFIG_UNIX
- Y if you want Unix domain sockets. Unless you are working on an
- embedded system or somthing, you probably want to say Y. If you try
- building this as a module and you are running kerneld, you need to make
- sure and add 'alias net-pf-1 unix' to your /etc/conf.module file.
+ This includes Unix domain sockets, the standard Unix mechanism for
+ establishing and accessing network connections. Unless you are
+ working on an embedded system or something, you probably want to say
+ Y. The socket support 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 unix.o. If you want to compile it
+ as a module, say M here and read Documentation/modules.txt. If you
+ try building this as a module and you are running kerneld, be sure
+ to add 'alias net-pf-1 unix' to your /etc/conf.module file. If
+ unsure, say Y.
The IPv6 protocol
CONFIG_IPV6
@@ -1528,31 +1819,35 @@
Protocol IP version 6 (also called IPng "IP next
generation"). Features of this new protocol include: expanded
address space, authentication and privacy, and seamless
- interoperability with the current version of IP. For general
- information about IPv6, see
- http://playground.sun.com/pub/ipng/html/ipng-main.html; for specific
- information about IPv6 under Linux read the HOWTO at
- http://www.terra.net/ipv6/ and the file net/ipv6/README in the
- kernel source. If you want to use IPv6, please upgrade to the newest
- net-tools as given in Documentation/Changes. The IPv6 support 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 ipv6.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. It's safe to say N for now.
+ interoperability with the current version of IP (IP version 4). For
+ general information about IPv6, see
+ http://playground.sun.com/pub/ipng/html/ipng-main.html (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape); for specific information about
+ IPv6 under Linux read the HOWTO at http://www.terra.net/ipv6/ and
+ the file net/ipv6/README in the kernel source. If you want to use
+ IPv6, please upgrade to the newest net-tools as given in
+ Documentation/Changes. The IPv6 support 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
+ ipv6.o. If you want to compile it as a module, say M here and read
+ Documentation/modules.txt. It's safe to say N for now.
IPv6: enable EUI-64 token format
CONFIG_IPV6_EUI64
- 6bone is moving to new aggregatable address format and new link local
- address assignment (EUI-64). Say Y, if your site already upgraded, or
- started upgrade.
+ 6bone, the network of computers using the IPv6 protocol, is moving
+ to a new aggregatable address format and a new link local address
+ assignment (EUI-64). Say Y, if your site has upgraded already, or
+ has started to upgrade.
IPv6: disable provider based addresses
CONFIG_IPV6_NO_PB
- Linux tries to operate correctly, when site is moved to EUI-64
- only partially. Unfortunately, these two formats ("provider based"
- and "aggregatable") are incompatible. Say Y, if your site finished
- upgrade, and/or you encountered some problems caused by presense of
- two link-local addresses on an interface.
+ Linux tries to operate correctly when your site is moved to EUI-64
+ only partially. Unfortunately, the two address formats (old:
+ "provider based" and new: "aggregatable") are incompatible. Say Y,
+ if your site finished the upgrade to EUI-64, and/or you encountered
+ some problems caused by the presence of two link-local addresses on
+ an interface.
The IPX protocol
CONFIG_IPX
@@ -1560,13 +1855,13 @@
used for local networks of Windows machines. You need it if you want
to access Novell Netware file or print servers using the Linux
Novell client ncpfs (available via ftp (user: anonymous) from
- sunsite.unc.edu:/pub/Linux/system/Filesystems/) or from within the
+ sunsite.unc.edu:/pub/Linux/system/filesystems/) or from within the
Linux DOS emulator dosemu (read the DOSEMU-HOWTO, available in
sunsite.unc.edu:/pub/Linux/docs/HOWTO). In order to do the former,
you'll also have to say Y to "NCP filesystem support", below. To
turn your Linux box into a fully featured Netware file server and
IPX router, say Y here and fetch either lwared from
- sunsite.unc.edu:/pub/Linux/system/Network/daemons/ or mars_nwe from
+ sunsite.unc.edu:/pub/Linux/system/network/daemons/ or mars_nwe from
ftp.gwdg.de:/pub/linux/misc/ncpfs. For more information, read the
IPX-HOWTO in sunsite.unc.edu:/pub/Linux/docs/howto. The IPX driver
would enlarge your kernel by about 5 kB. This driver is also
@@ -1624,39 +1919,49 @@
machine on the Internet that has a program like lynx or
netscape). EtherTalk is the name used for appletalk over ethernet
and the cheaper and slower LocalTalk is appletalk over a proprietary
- apple network using serial links. Ethertalk and Localtalk is fully
+ apple network using serial links. Ethertalk and Localtalk are fully
supported by Linux. The NET-2-HOWTO, available via ftp (user: anonymous)
in sunsite.unc.edu:/pub/Linux/docs/HOWTO contains valuable information
as well. 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 appletalk.o. If you want to compile
+ want). The module is called appletalk.o. If you want to compile
it as a module, say M here and read Documentation/modules.txt. I
hear that the GNU boycott of Apple is over, so even politically
correct people are allowed to say Y here.
Appletalk-IP driver support
CONFIG_IPDDP
- Appletalk-IP is a method Macintosh users use IP services. This driver
- allows you to either send your IP traffic over an Appletalk network to
- an Appletalk-IP router, or you can have your machine act as an Appletalk-IP
- router and route Appletalk-IP traffic for your Macintosh users. Both
- modes require seperate user-space support software, please see each
- individual options help to get the correct URL of the software.
+ This allows IP networking for users who only have Appletalk
+ networking available. This feature is experimental. With this
+ driver, you can either encapsulate IP inside Appletalk (e.g. if your
+ Linux box is stuck on an appletalk only network) or decapsulate
+ (e.g. if you want your Linux box to act as a internet gateway for a
+ zoo of appletalk connected Macs). You decide which one of the two
+ you want in the following two questions; you can say Y to only one
+ of them. Please see Documentation/networking/ipddp.txt for more
+ information. 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 is called ipddp.o. If you want to
+ compile it as a module, say M here and read
+ Documentation/modules.txt.
-Appletalk-IP Encapsulation support
+IP to Appletalk-IP Encapsulation support
CONFIG_IPDDP_ENCAP
- This allows IP networking for users who only have Appletalk
- networking available. This feature is experimental. Please see
- http://www.maths.unm.edu/~bradford/ltpc.html for support software.
+ If you say Y here, the kernel will be able to encapsulate IP packets
+ inside Appletalk frames; this is useful if your Linux box is stuck
+ on an appletalk network (which hopefully contains a decapsulator
+ somewhere). Please see Documentation/networking/ipddp.txt for more
+ information. If you say Y here, you cannot say Y to "Appletalk-IP to
+ IP Decapsulation support", below.
-Appletalk-IP Decapsulation support
+Appletalk-IP to IP Decapsulation support
CONFIG_IPDDP_DECAP
- This allows you to provide IP services to your Appletalk users.
- It does not matter what interface the Macs are comming into your
- Linux box on, be it Localtalk, Ethertalk, PPPtalk, etc. The only
- dependent variable is if the Appletalk layer supports the protocol
- you need. User space software is required to run this driver, you
- can pick it up at http://spacs1.spacs.k12.wi.us/~jschlst/MacGate.html
+ If you say Y here, the kernel will be able to decapsulate
+ Appletalk-IP frames to IP packets; this is useful if you want your
+ Linux box to act as an Internet gateway for an appletalk
+ network. Please see Documentation/networking/ipddp.txt for more
+ information. If you say Y here, you cannot say Y to "IP to
+ Appletalk-IP Encapsulation support", above.
Apple/Farallon LocalTalk PC card support
CONFIG_LTPC
@@ -1665,8 +1970,7 @@
If you are in doubt, this card is the one with the 65C02 chip on it.
You also need version 1.3.3 or later of the netatalk package.
This driver is experimental, which means that it may not work.
- See README.ltpc in the drivers/net directory, and the web site
- http://www.math.unm.edu/~bradford/ltpc.html
+ See the file Documentation/networking/ltpc.txt.
COPS LocalTalk PC card support
CONFIG_COPS
@@ -1675,9 +1979,7 @@
package. This driver is experimental, which means that it may not
work. This driver will only work if you choose "Appletalk DDP"
networking support, above.
- Please read the file Documentation/networking/README.cops. See the
- web site http://www.math.unm.edu/~bradford/ltpc.html for localtalk
- IP tools.
+ Please read the file Documentation/networking/cops.txt.
Dayna firmware support
CONFIG_COPS_DAYNA
@@ -1690,6 +1992,17 @@
Support COPS compatible cards with Tangent style firmware (Tangent
ATB_II, Novell NL-1000, Daystar Digital LT-200.
+Amateur Radio support
+CONFIG_HAMRADIO
+ If you want to connect your Linux computer to an amateur radio, say
+ Y here. You want to read http://www.tapr.org/tapr/html/pkthome.html
+ (to browse the WWW, you need to have access to a machine on the
+ Internet that has a program like lynx or netscape) and the HAM-HOWTO
+ and the AX25-HOWTO, both available via ftp (user: anonymous) from
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the answer to this
+ question won't directly affect the kernel: saying N will just cause
+ this configure script to skip all the questions about amateur radio.
+
Amateur Radio AX.25 Level 2
CONFIG_AX25
This is the protocol used for computer communication over amateur
@@ -1783,19 +2096,20 @@
CCITT X.25 Packet Layer
CONFIG_X25
X.25 is a set of standardized network protocols, similar in scope to
- frame relay; the one physical line from your box to the entry point
- to the X.25 network can carry several logical point-to-point
- connections (called "virtual circuits") to other computers connected
- to the X.25 network. Governments, banks, and other organizations
- tend to use it to connect to each other or to form Wide Area
- Networks. Many countries have public X.25 networks. X.25 consists
- of two protocols: the higher level Packet Layer Protocol (PLP) (say
- Y here if you want that) and the lower level data link layer
- protocol LAPB (say Y to "LAPB Data Link Driver" below if you want
- that). You can read more about X.25 at
- http://www.sangoma.com/x25.html and
- http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm.
- Information about X.25 for Linux is contained in the files
+ frame relay; the one physical line from your box to the X.25 network
+ entry point can carry several logical point-to-point connections
+ (called "virtual circuits") to other computers connected to the X.25
+ network. Governments, banks, and other organizations tend to use it
+ to connect to each other or to form Wide Area Networks (WAN's). Many
+ countries have public X.25 networks. X.25 consists of two
+ protocols: the higher level Packet Layer Protocol (PLP) (say Y here
+ if you want that) and the lower level data link layer protocol LAPB
+ (say Y to "LAPB Data Link Driver" below if you want that). You can
+ read more about X.25 at http://www.sangoma.com/x25.html and
+ http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm
+ (to browse the WWW, you need to have access to a machine on the
+ Internet that has a program like lynx or netscape). Information
+ about X.25 for Linux is contained in the files
Documentation/networking/x25.txt and
Documentation/networking/x25-iface.txt. One connects to an X.25
network either with a dedicated network card using the X.21 protocol
@@ -1831,7 +2145,7 @@
CONFIG_LLC
This is a Logical Link Layer protocol used for X.25 connections over
ethernet, using ordinary ethernet cards.
-
+
Bridging (EXPERIMENTAL)
CONFIG_BRIDGE
If you say Y here, then your Linux box will be able to act as an
@@ -1842,14 +2156,25 @@
algorithm. As this is a standard, Linux bridges will interwork
properly with other third party bridge products. In order to use
this, you'll need the bridge configuration tools available via ftp
- (user: anonymous) from shadow.cabi.net. Note that if your box acts
- as a bridge, it probably contains several ethernet devices, but the
- kernel is not able to recognize more than one at boot time without
- help; for details read the Multiple-Ethernet-mini-HOWTO, available
- via ftp (user: anonymous) in
+ (user: anonymous) from shadow.cabi.net in /pub/Linux. Note that if
+ your box acts as a bridge, it probably contains several ethernet
+ devices, but the kernel is not able to recognize more than one at
+ boot time without help; for details read the
+ Multiple-Ethernet-mini-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The Bridging code is
still in test. If unsure, say N.
+Packet socket
+CONFIG_PACKET
+ The Packet protocol is used by applications which communicate
+ directly with network devices without an intermediate network
+ protocol implemented in the kernel, e.g. tcpdump. If you want that
+ they work, choose Y. This driver is also available as a module
+ called af_packet.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 Documentation/modules.txt. If
+ unsure, say Y.
+
Kernel/User network link driver
CONFIG_NETLINK
This driver allows for two-way communication between certain parts
@@ -1861,7 +2186,9 @@
to "Kernel/User network link driver" further down. You also need to
say Y here if you want to use arpd, a daemon that helps keep the
internal ARP cache (a mapping between IP addresses and hardware
- addresses on the local network) small. If unsure, say N.
+ addresses on the local network) small. The ethertap device, which
+ lets user space programs read and write raw ethernet frames, also
+ needs the network link driver. If unsure, say Y.
Routing messages
CONFIG_RTNETLINK
@@ -1870,6 +2197,11 @@
you can read some network related routing information from that
file. Everything you write to that file will be discarded.
+Netlink device emulation
+CONFIG_NETLINK_DEV
+ This is a backward compatibility option, choose Y for now.
+ This option will be removed soon.
+
SCSI support?
CONFIG_SCSI
If you want to use a SCSI harddisk, SCSI tapedrive, SCSI CDROM or
@@ -1902,7 +2234,7 @@
your root filesystem (the one containing the directory /) is located
on a SCSI disk. In this case, do not compile the driver for your
SCSI host adapter (below) as a module either.
-
+
SCSI tape support
CONFIG_CHR_DEV_ST
If you want to use a SCSI tapedrive under Linux, say Y and read the
@@ -1930,8 +2262,7 @@
This enables the usage of vendor specific SCSI commands. This is
required to support multisession CD's on with old NEC/TOSHIBA
cdrom drives (and HP Writers). If you have such a drive and get
- the first session only, try to turn this on. Most drives should
- work fine without this.
+ the first session only, try to say Y here; everybody else says N.
SCSI generic support
CONFIG_CHR_DEV_SG
@@ -1972,14 +2303,14 @@
This turns on a logging facility that can be used to debug a number
of problems. Normally no logging output will appear, but you can
enable logging with a shell command like:
- 'echo "scsi log token [level]" > /proc/scsi/scsi'
- There are a number of things that can be used for 'token', and this
- allows you to select the types of information you want, and the level
- allows you to select the level of verbosity. If you say 'N' here,
- it may be harder to track down some types of scsi problems. If
- you say 'Y' here your kernel will be somewhat larger, but there
- should be no noticable performance impact as long as you have logging
- turned off.
+ echo "scsi log token [level]" > /proc/scsi/scsi
+ There are a number of things that can be used for 'token' (you can
+ find them in the source: drivers/scsi/scsi.c), and this allows you
+ to select the types of information you want, and the level allows
+ you to select the level of verbosity. If you say 'N' here, it may
+ be harder to track down some types of scsi problems. If you say 'Y'
+ here your kernel will be somewhat larger, but there should be no
+ noticeable performance impact as long as you have logging turned off.
AdvanSys SCSI support
CONFIG_SCSI_ADVANSYS
@@ -2015,7 +2346,7 @@
inserted in and removed from the running kernel whenever you want),
say M here and read Documentation/modules.txt. The module will be
called aha1542.o.
-
+
Adaptec AHA1740 support
CONFIG_SCSI_AHA1740
This is support for a SCSI host adapter. It is explained in section
@@ -2057,21 +2388,22 @@
Maximum number of commands per LUN
CONFIG_AIC7XXX_CMDS_PER_LUN
- If tagged queueing is enabled, then you may want to try increasing
- the number of SCSI commands per LUN to more than 2. By default, we
- limit the commands per LUN to 2 with or without tagged queueing
- enabled. If tagged queueing is disabled, the sequencer in the host
- adapter will keep the 2nd command in the input queue until the first
- one completes - so it is OK to have more than 1 command queued. If
- tagged queueing is enabled, then the sequencer will attempt to send
- the 2nd command block to the device while the first command block is
- executing and the device is disconnected. For adapters limited to 4
- command blocks (SCB's), you may want to actually decrease the
- commands per LUN to 1, if you often have more than 2 devices active
- at the same time. This will ensure that there will always be a free
- SCB for up to 4 devices active at the same time. When SCB paging is
- enabled, set the commands per LUN to 8 or higher (see "SCB paging
- support" below). If unsure, go with the default for now.
+ By default, we limit the commands per LUN to 2 with or without
+ tagged queueing enabled. If tagged queueing is enabled, the
+ sequencer in the host adapter will attempt to send the 2nd command
+ block to the device while the first command block is still executing
+ and the device is disconnected. If the devices don't complain, you
+ can thus try to increase the number of SCSI commands per LUN to more
+ than 2 in this case. If tagged queueing is disabled, the sequencer
+ in the host adapter will keep the 2nd command in its input queue
+ until the first one completes - so it is OK to have more than 1
+ command queued. However, for host adapters limited to 4 command
+ blocks (SCB's), you may want to actually decrease the commands per
+ LUN to 1, if you often have more than 2 devices active at the same
+ time. This will ensure that there will always be a free SCB for up
+ to 4 devices active at the same time. When SCB paging is enabled,
+ set the commands per LUN to 8 or higher (see "SCB paging support"
+ below). If unsure, go with the default for now.
Enable SCB paging
CONFIG_AIC7XXX_PAGE_ENABLE
@@ -2171,7 +2503,7 @@
want). The module will be called u14-34f.o. If you want to compile
it as a module, say M here and read Documentation/modules.txt.
-enable linked commands
+enable elevator sorting
CONFIG_SCSI_U14_34F_LINKED_COMMANDS
This is a feature of SCSI-2 which improves performance: the host
adapter can send a whole list of commands to a device in one
@@ -2209,7 +2541,7 @@
kernel whenever you want). The module will be called g_NCR5380.o. If
you want to compile it as a module, say M here and read
Documentation/modules.txt.
-
+
Enable NCR53c400 extensions
CONFIG_SCSI_GENERIC_NCR53C400
This enables certain optimizations for the NCR53c400 scsi cards. You
@@ -2249,7 +2581,7 @@
This will enable 10MHz FAST-SCSI transfers with your host
adapter. Some systems have problems with that speed, so it's safest
to say N here.
-
+
allow DISCONNECT
CONFIG_SCSI_NCR53C7xx_DISCONNECT
This enables the disconnect/reconnect feature of the NCR SCSI
@@ -2394,6 +2726,12 @@
say M here and read Documentation/modules.txt. The module will be
called ibmmca.o.
+reset SCSI-devices while booting
+CONFIG_SCSI_IBMMCA_DEV_RESET
+ If you say Y here, each connected SCSI device will get a reset
+ command at boot time. This can be necessary for some special SCSI
+ devices. If unsure, say N.
+
Always IN2000 SCSI support
CONFIG_SCSI_IN2000
This is support for an ISA bus SCSI host adapter. You'll find more
@@ -2416,6 +2754,36 @@
pas16.o. If you want to compile it as a module, say M here and read
Documentation/modules.txt.
+PCI2000 support
+CONFIG_SCSI_PCI2000
+ This is support for the PCI2000I EIDE interface card which acts as a
+ SCSI host adapter. Please read the SCSI-HOWTO, available via ftp
+ (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This
+ driver is also available as a module called pci2000.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
+ Documentation/modules.txt.
+
+PCI2220i support
+CONFIG_SCSI_PCI2220I
+ This is support for the PCI2220i EIDE interface card which acts as a
+ SCSI host adapter. Please read the SCSI-HOWTO, available via ftp
+ (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This
+ driver is also available as a module called pci2220i.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 Documentation/modules.txt.
+
+PSI240i support
+CONFIG_SCSI_PSI240I
+ This is support for the PSI240i EIDE interface card which acts as a
+ SCSI host adapter. Please read the SCSI-HOWTO, available via ftp
+ (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This
+ driver is also available as a module called psi240i.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
+ Documentation/modules.txt.
+
Qlogic FAS SCSI support
CONFIG_SCSI_QLOGIC_FAS
This driver works only with the ISA, VLB, and PCMCIA versions of the
@@ -2484,15 +2852,15 @@
Documentation/modules.txt. The module will be called ultrastor.o.
Note that there is also another driver for the same hardware:
"UltraStor 14F/34F support", above.
-
+
7000FASST SCSI support
CONFIG_SCSI_7000FASST
- This driver supports the Western Digital 7000 SCSI host adapter.
- Some information is in the source: drivers/scsi/wd7000.c. 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 wd7000.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ This driver supports the Western Digital 7000 SCSI host adapter
+ family. Some information is in the source: drivers/scsi/wd7000.c.
+ 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 wd7000.o. If you want to compile it
+ as a module, say M here and read Documentation/modules.txt.
EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
CONFIG_SCSI_EATA
@@ -2517,7 +2885,7 @@
previous commands haven't finished yet. Some SCSI devices don't
implement this properly, so the save answer is N.
-enable linked commands
+enable elevator sorting
CONFIG_SCSI_EATA_LINKED_COMMANDS
This is a feature of SCSI-2 which improves performance: the host
adapter can send a whole list of commands to a device in one
@@ -2542,25 +2910,12 @@
and read Documentation/modules.txt. The module will be called
NCR53c406.o.
-Tekram DC390W/U/F (T) SCSI support
-CONFIG_SCSI_DC390W
- This driver supports the Tekram DC390W/U/F (T) PCI SCSI host
- adapters with the NCR/Symbios 53c825/875 chips. Say Y here if you
- have one of those. If however you have a DC390 (T) adaptor with the
- Am53C974A chip, use the DC390(T) driver "Tekram DC390(T) (AMD
- PCscsi) SCSI support", below.
- 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 Documentation/modules.txt. The module will be
- called ???.o.
-
Tekram DC390(T) (AMD PCscsi) SCSI support
CONFIG_SCSI_DC390T
This driver supports the Tekram DC390(T) PCI SCSI host adapter with
the Am53C974A chip, and perhaps other cards using the same chip.
- This driver does _not_ support the DC390W/U/F adaptor with the
- NCR/Symbios chips; use "Tekram DC390W/U/F (T) SCSI support" for that
- one.
+ This driver does _not_ support the DC390W/U/F adaptor with the
+ NCR/Symbios chips; use "NCR53C8XX SCSI support" for that one.
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 Documentation/modules.txt. The module will be
@@ -2622,7 +2977,7 @@
is that many hard to reproduce problems can be tested in a controlled
environment where there is reduced risk of losing important data.
This is primarily of use to people trying to debug the middle and upper
- layers of the scsi subsystem.
+ layers of the scsi subsystem. If unsure, say N.
Network device support?
CONFIG_NETDEVICES
@@ -2634,20 +2989,21 @@
shell account or a BBS, even using term (term is a program which
gives you almost full Internet connectivity if you have a regular
dial up shell account on some Internet connected Unix computer. Read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). You'll
- have to say Y if your computer contains a network card that you want
- to use under linux (make sure you know its name because you will be
- asked for it and read the Ethernet-HOWTO; also, if you plan to use
- more than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to use
- SLIP (Serial Line Internet Protocol is the protocol used to send
- Internet traffic over telephone lines or nullmodem cables) or CSLIP
- (compressed SLIP) or PPP (Point to Point Protocol, a better and
- newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol
- is mainly used to create a mini network by connecting the parallel
- ports of two local machines) or AX.25/KISS (protocol for sending
- internet traffic over radio links). Make sure to read the
+ http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape)). You'll have to say Y if your
+ computer contains a network card that you want to use under linux
+ (make sure you know its name because you will be asked for it and
+ read the Ethernet-HOWTO; also, if you plan to use more than one
+ network card under linux, read the Multiple-Ethernet-mini-HOWTO,
+ available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you
+ want to use SLIP (Serial Line Internet Protocol is the protocol used
+ to send Internet traffic over telephone lines or nullmodem cables)
+ or CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
+ and newer replacement for SLIP) or PLIP (Parallel Line Internet
+ Protocol is mainly used to create a mini network by connecting the
+ parallel ports of two local machines) or AX.25/KISS (protocol for
+ sending internet traffic over radio links). Make sure to read the
NET-2-HOWTO. Eventually, you will have to read Olaf Kirch's
excellent book "Network Administrator's Guide", to be found in
sunsite.unc.edu:/pub/Linux/docs/LDP. If unsure, say Y.
@@ -2669,7 +3025,7 @@
want to use more than one dummy device at a time, you need to
compile this driver as a module. Instead of 'dummy', the devices
will then be called 'dummy0', 'dummy1' etc.
-
+
SLIP (serial line) support
CONFIG_SLIP
Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
@@ -2681,7 +3037,7 @@
nullmodems). Normally, your access provider has to support SLIP in
order for you to be able to use it, but there is now a SLIP emulator
called SLiRP around (available via ftp (user: anonymous) from
- sunsite.unc.edu:/pub/Linux/system/Network/serial/) which allows you
+ sunsite.unc.edu:/pub/Linux/system/network/serial/) which allows you
to use SLIP over a regular dial up shell connection. If you plan to
use SLiRP, make sure to say Y to CSLIP, below. The NET-2-HOWTO,
available via ftp (user: anonymous) in
@@ -2690,14 +3046,16 @@
term (term is a program which gives you almost full Internet
connectivity if you have a regular dial up shell account on some
Internet connected Unix computer. Read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). SLIP
- support will enlarge your kernel by about 4kB. 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 Documentation/modules.txt as well as
+ http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape)). SLIP support will enlarge
+ your kernel by about 4kB. 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
+ Documentation/modules.txt as well as
Documentation/networking/net-modules.txt. The module will be called
slip.o.
-
+
CSLIP compressed headers
CONFIG_SLIP_COMPRESSED
This protocol is faster than SLIP because it uses compression on the
@@ -2705,7 +3063,7 @@
on both ends. Ask your access provider if you are not sure and say
Y, just in case. You will still be able to use plain SLIP. If you
plan to use SLiRP, the SLIP emulator (available via ftp (user:
- anonymous) from sunsite.unc.edu:/pub/Linux/system/Network/serial/)
+ anonymous) from sunsite.unc.edu:/pub/Linux/system/network/serial/)
which allows you to use SLIP over a regular dial up shell
connection, you definitely want to say Y here. The NET-2-HOWTO,
available via ftp (user: anonymous) in
@@ -2728,27 +3086,15 @@
end of the link as well. It's good enough, for example, to run IP
over the async ports of a Camtec JNT Pad. If unsure, say N.
-Radio network interfaces
+Wireless LAN (non-hamradio)
CONFIG_NET_RADIO
- Radio based interfaces for Linux. This includes amateur radio
- (AX.25), support for wireless ethernet and other systems. Note that
- the answer to this question won't directly affect the kernel: saying
- N will just cause this configure script to skip all the questions
- about radio interfaces. Some user-level drivers for scarab devices
- which don't require special kernel support are available via ftp
- (user: anonymous) from shadow.cabi.net.
- If unsure, say N.
-
-AX.25 network interfaces
-CONFIG_NET_HAM
- Say Y here if you want support for a device that connects your Linux
- box to your amateur radio (HAM). AX.25 is the protocol used for
- digital traffic over amateur radio connections. You might want to
- read the HAM-HOWTO and the AX25-HOWTO, both available via ftp (user:
- anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the
- answer to this question won't directly affect the kernel: saying N
- will just cause this configure script to skip all the questions
- about amateur radio interfaces.
+ Support for wireless LAN's and everything having to do with radio,
+ but not with amateur radio. Note that the answer to this question
+ won't directly affect the kernel: saying N will just cause this
+ configure script to skip all the questions about radio
+ interfaces. Some user-level drivers for scarab devices which don't
+ require special kernel support are available via ftp (user:
+ anonymous) from shadow.cabi.net in /pub/Linux.
PPP (point-to-point) support
CONFIG_PPP
@@ -2758,7 +3104,7 @@
otherwise you can't use it (not quite true any more: the free
program SLiRP can emulate a PPP line if you just have a regular dial
up shell account on some UNIX computer; get it via ftp (user:
- anonymous) from sunsite.unc.edu:/pub/Linux/system/Network/serial/).
+ anonymous) from sunsite.unc.edu:/pub/Linux/system/network/serial/).
To use PPP, you need an additional program called pppd as described
in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
from sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you upgrade from an
@@ -2767,20 +3113,22 @@
program which gives you almost full Internet connectivity if you
have a regular dial up shell account on some Internet connected UNIX
computer. Read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). The PPP
- option enlarges your kernel by about 16kB. This driver is also
- available as a module ( = code which can be inserted in and removed
- from the running kernel whenever you want). If you said Y to
- "Version information on all symbols" above, then you cannot compile
- the PPP driver into the kernel; you can then only compile it as a
- module. The module will be called ppp.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt as well
- as Documentation/networking/net-modules.txt. Note that, no matter
- what you do, the BSD compression code (used to compress the IP
- packets sent over the serial line; has to be supported at the other
- end as well) will always be compiled as a module; it is called
- bsd_comp.o and will show up in the directory modules once you have
- said "make modules". If unsure, say N.
+ http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape)). The PPP option enlarges your
+ kernel by about 16kB. This driver is also available as a module ( =
+ code which can be inserted in and removed from the running kernel
+ whenever you want). If you said Y to "Version information on all
+ symbols" above, then you cannot compile the PPP driver into the
+ kernel; you can then only compile it as a module. The module will be
+ called ppp.o. If you want to compile it as a module, say M here and
+ read Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt. Note that, no matter what
+ you do, the BSD compression code (used to compress the IP packets
+ sent over the serial line; has to be supported at the other end as
+ well) will always be compiled as a module; it is called bsd_comp.o
+ and will show up in the directory modules once you have said "make
+ modules". If unsure, say N.
Shortwave radio modem driver
CONFIG_HFMODEM
@@ -2806,7 +3154,9 @@
CONFIG_STRIP
Say Y if you have a Metricom radio and intend to use Starmode Radio
IP. STRIP is a radio protocol developed for the MosquitoNet project
- (http://mosquitonet.stanford.edu/) to send Internet traffic using
+ (On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW,
+ you need to have access to a machine on the Internet that has a
+ program like lynx or netscape) to send Internet traffic using
Metricom radios. Metricom radios are small, battery powered,
100kbit/sec packet radio transceivers, about the size and weight of
a cellular telephone. (You may also have heard them called
@@ -2821,6 +3171,26 @@
the running kernel whenever you want), say M here and read
Documentation/modules.txt. The module will be called strip.o.
+Radio support
+CONFIG_MISC_RADIO
+ If you have a radio card (which enables your computer to receive
+ regular radio broadcasts), then you will want to say "y" here and
+ make a character device file (usually /dev/radio) with major number
+ 10 and minor 152 using mknod ("man mknod"). And then, don't forget
+ to pick up some useful tools to use said device (you _might_ find
+ something at ftp.lmh.ox.ac.uk: /users/weejock/linux/, but I haven't
+ written anything too useful yet...)
+
+AIMSlab RadioTrack card
+CONFIG_RADIO_RTRACK
+ Choose Y here if you have one of these, and then fill in the port
+ address below.
+
+RadioTrack i/o port
+CONFIG_RADIO_RTRACK_PORT
+ Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
+ haven't changed the jumper setting on the card.
+
LAPB over Ethernet driver
CONFIG_LAPBETHER
This is a driver for a pseudo device (typically called /dev/lapb0)
@@ -2857,36 +3227,52 @@
running kernel whenever you want), say M here and read
Documentation/modules.txt. The module will be called scc.o.
+additional delay for PA0HZP OptoSCC compatible boards
+CONFIG_SCC_DELAY
+
+support for TRX that feedback the tx signal to rx
+CONFIG_SCC_TRXECHO
+###
+### Don't know what's going on here.
+###
+
High-speed (DMA) SCC driver for AX.25
CONFIG_DMASCC
- This is a driver for high-speed SCC boards, i.e. those supporting
- DMA on one port. Currently, only Ottawa PI/PI2 boards (see
- http://hydra.carleton.ca/info/pi2.html) and Gracilis PackeTwin
- boards (see http://www.paccomm.com/) are supported and detected
- automatically. Multiple boards are operated simultaneously. If
- you compile this driver as a module, it will be called dmascc.o.
- If you don't give any parameter to the driver, all possible I/O
- addresses are probed. This could irritate other devices that are
- currently not in use. You may specify the list of addresses to be
- probed by "dmascc=addr1,addr2,..." (when compiled into the kernel
- image) or "io=addr1,addr2,..." (when loaded as a module).
- The network interfaces will be called dmascc0 and dmascc1 for the
- board detected first, dmascc2 and dmascc3 for the second one, and
- so on. Before you configure each interface with ifconfig, you MUST
- set certain parameters, such as channel access timing, clock mode,
- and DMA channel. This is accomplished with a small utility program
- called dmascc_cfg, which is part of the ax25-utils package.
- Alternatively, you may download the utility from
+ This is a driver for high-speed SCC boards (used to connect your
+ computer to your amateur radio and send internet traffic over the
+ radio), i.e. those supporting DMA on one port. Currently, only
+ Ottawa PI/PI2 boards (see http://hydra.carleton.ca/info/pi2.html)
+ and Gracilis PackeTwin boards (see http://www.paccomm.com/; to
+ browse the WWW, you need to have access to a machine on the Internet
+ that has a program like lynx or netscape) are supported and detected
+ automatically. If you have one of these cards, you can say Y here
+ and should read the HAM-HOWTO, available via ftp (user: anonymous)
+ in sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+ This driver operates multiple boards simultaneously. If you compile
+ this driver as a module, it will be called dmascc.o. If you don't
+ give any parameter to the driver, all possible I/O addresses are
+ probed. This could irritate other devices that are currently not in
+ use. You may specify the list of addresses to be probed by
+ "dmascc=addr1,addr2,..." (when compiled into the kernel image) or
+ "io=addr1,addr2,..." (when loaded as a module). The network
+ interfaces will be called dmascc0 and dmascc1 for the board detected
+ first, dmascc2 and dmascc3 for the second one, and so on. Before you
+ configure each interface with ifconfig, you MUST set certain
+ parameters, such as channel access timing, clock mode, and DMA
+ channel. This is accomplished with a small utility program called
+ dmascc_cfg, which is part of the ax25-utils package. Alternatively,
+ you may download the utility from
http://www.oevsv.at/~oe1kib/Linux.html.
BAYCOM picpar and par96 driver for AX.25
CONFIG_BAYCOM_PAR
- This is a driver for Baycom style simple amateur radio
- modems that connect to a parallel interface. The driver
- supports the picpar and par96 designs. To configure the
- driver, use the sethdlc utility available in the standard
- ax25 utilities package. For information on the modems, see
- http://www.baycom.de and Documentation/networking/baycom.txt. If you
+ This is a driver for Baycom style simple amateur radio modems that
+ connect to a parallel interface. The driver supports the picpar and
+ par96 designs. To configure the driver, use the sethdlc utility
+ available in the standard ax25 utilities package. For information on
+ the modems, see http://www.baycom.de (to browse the WWW, you need to
+ have access to a machine on the Internet that has a program like
+ lynx or netscape) and Documentation/networking/baycom.txt. 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 Documentation/modules.txt. This is
@@ -2895,45 +3281,51 @@
BAYCOM ser12 full duplex driver for AX.25
CONFIG_BAYCOM_SER_FDX
This is one of two drivers for Baycom style simple amateur radio
- modems that connect to a serial interface. The driver supports
- the ser12 design in full duplex mode. In addition, it allows the
+ modems that connect to a serial interface. The driver supports the
+ ser12 design in full duplex mode. In addition, it allows the
baudrate to be set between 300 and 4800 baud (however not all modems
- support all baudrates). This is the preferred driver. baycom_ser_hdx.o
- is the old driver and still provided in case this driver does not work
- with your serial interface chip. To configure the driver, use the
- sethdlc utility available in the standard ax25 utilities package.
- For information on the modems, see http://www.baycom.de and
- Documentation/networking/baycom.txt. 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 Documentation/modules.txt. This is
- recommended. The module will be called baycom_ser_fdx.o.
+ support all baudrates). This is the preferred driver. The next
+ driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
+ driver and still provided in case this driver does not work with
+ your serial interface chip. To configure the driver, use the sethdlc
+ utility available in the standard ax25 utilities package. For
+ information on the modems, see http://www.baycom.de (to browse the
+ WWW, you need to have access to a machine on the Internet that has a
+ program like lynx or netscape) and
+ Documentation/networking/baycom.txt. 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
+ Documentation/modules.txt. This is recommended. The module will be
+ called baycom_ser_fdx.o.
BAYCOM ser12 half duplex driver for AX.25
CONFIG_BAYCOM_SER_HDX
This is one of two drivers for Baycom style simple amateur radio
- modems that connect to a serial interface. The driver supports
- the ser12 design in full duplex mode. This is the old driver.
- It is still provided in case your serial interface chip does
- not work with the full duplex driver. This driver is depreciated.
- To configure the driver, use the sethdlc utility available
- in the standard ax25 utilities package. For information
- on the modems, see http://www.baycom.de and
- Documentation/networking/baycom.txt. 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 Documentation/modules.txt. This is
- recommended. The module will be called baycom_ser_hdx.o.
+ modems that connect to a serial interface. The driver supports the
+ ser12 design in full duplex mode. This is the old driver. It is
+ still provided in case your serial interface chip does not work with
+ the full duplex driver. This driver is depreciated. To configure
+ the driver, use the sethdlc utility available in the standard ax25
+ utilities package. For information on the modems, see
+ http://www.baycom.de (to browse the WWW, you need to have access to
+ a machine on the Internet that has a program like lynx or netscape)
+ and Documentation/networking/baycom.txt. 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
+ Documentation/modules.txt. This is recommended. The module will be
+ called baycom_ser_hdx.o.
Soundcard modem driver for AX.25
CONFIG_SOUNDMODEM
This experimental driver allows a standard SoundBlaster or
WindowsSoundSystem compatible soundcard to be used as a packet radio
- modem, to send digital traffic over amateur radio. To configure the
- driver, use the sethdlc, smdiag and smmixer utilities available in
- the standard ax25 utilities package. For information on how to key
- the transmitter, see
- http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
+ modem (NOT as a telephone modem!), to send digital traffic over
+ amateur radio. To configure the driver, use the sethdlc, smdiag and
+ smmixer utilities available in the standard ax25 utilities
+ package. For information on how to key the transmitter, see
+ http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape) and
Documentation/networking/soundmodem.txt. 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
@@ -3015,26 +3407,6 @@
can only use one protocol at a time, depending on what the other end
can understand).
-Shortwave radio modem driver
-CONFIG_HFMODEM
- This experimental driver is used by a package (to be released)
- that implements the shortwave radio protocols RTTY, Sitor (Amtor),
- Pactor 1 and GTOR using a standard PC soundcard. If unsure,
- say N.
-
-Shortwave radio modem driver support for SoundBlaster and compatible cards
-CONFIG_HFMODEM_SBC
- This option enables the hfmodem driver to use SoundBlaster and
- compatible cards. It requires a 16bit capable card, i.e.
- SB16 or better, or ESS1688 or newer.
-
-Shortwave radio modem driver support for WSS and Crystal cards
-CONFIG_HFMODEM_WSS
- This option enables the hfmodem driver to use WindowsSoundSystem
- compatible cards. These cards feature a codec chip from either
- Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
- Semiconductors (such as CS4248, CS423x).
-
Serial port KISS driver for AX.25
CONFIG_MKISS
KISS is the protocol used to send IP traffic over AX.25 radio
@@ -3049,28 +3421,31 @@
PLIP (parallel port) support
CONFIG_PLIP
- PLIP (Parallel Line Internet Protocol) is used to create a mini
- network consisting of two (or, rarely, more) local machines. The
- parallel ports (the connectors at the computers with 25 holes) are
- connected using "null printer" or "Turbo Laplink" cables which can
- transmit 4 bits at a time or using special PLIP cables, to be used
- on bidirectional parallel ports only, which can transmit 8 bits at a
- time (you can find the wiring of these cables in
- drivers/net/README?.plip). The cables can be up to 15m long. This
- works also if one of the machines runs DOS/Windows and has some PLIP
- software installed, e.g. the Crynwr PLIP packet driver
- (http://sunsite.cnam.fr/packages/Telnet/PC/msdos/misc/pktdrvr.txt)
- and winsock or NCSA's telnet. If you want to use this, say Y and
- read the PLIP mini-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini as well as the
- NET-2-HOWTO in sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the
- PLIP protocol was changed and this PLIP driver won't work together
- with the PLIP support in Linux versions 1.0.x. This option enlarges
- your kernel by about 8kB. 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 as
- well as Documentation/networking/net-modules.txt. The module will be
- called plip.o.
+ PLIP (Parallel Line Internet Protocol) is used to create a
+ reasonably fast mini network consisting of two (or, rarely, more)
+ local machines. The PLIP driver has two modes, mode 0 and mode
+ 1. The parallel ports (the connectors at the computers with 25
+ holes) are connected with "null printer" or "Turbo Laplink" cables
+ which can transmit 4 bits at a time (mode 0) or with special PLIP
+ cables, to be used on bidirectional parallel ports only, which can
+ transmit 8 bits at a time (mode 1); you can find the wiring of these
+ cables in Documentation/networking/PLIP.txt. The cables can be up to
+ 15m long. Mode 0 works also if one of the machines runs DOS/Windows
+ and has some PLIP software installed, e.g. the Crynwr PLIP packet
+ driver (http://www.kanren.net/pktdrvr-info.html; to browse the WWW,
+ you need to have access to a machine on the Internet that has a
+ program like lynx or netscape) and winsock or NCSA's telnet. If you
+ want to use PLIP, say Y and read the PLIP mini-HOWTO, available via
+ ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini
+ as well as the NET-2-HOWTO in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the PLIP protocol
+ was changed and this PLIP driver won't work together with the PLIP
+ support in Linux versions 1.0.x. This option enlarges your kernel
+ by about 8kB. 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 as well as
+ Documentation/networking/net-modules.txt. The module will be called
+ plip.o. If unsure, say Y or M, in case you buy a laptop later.
EQL (serial line load balancing) support
CONFIG_EQUALIZER
@@ -3081,11 +3456,32 @@
like one double speed connection using this driver. Naturally, this
has to be supported at the other end as well, either with a similar
EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you
- want this and read drivers/net/README.eql. 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 eql.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt.
+ want this and read Documentation/networking/eql.txt. 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 eql.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt. If unsure, say N.
+
+Ethertap network tap
+CONFIG_ETHERTAP
+ If you say Y here (and have said Y to "Kernel/User network link
+ driver", above) and create a character special file /dev/tap0 with
+ major number 36 and minor number 16 using mknod ("man mknod"), you
+ will be able to have a user space program read and write raw
+ ethernet frames from/to that special file. tap0 can be configured
+ with ifconfig and route like any other ethernet device but it is not
+ connected to any physical LAN; everything written by the user to
+ /dev/tap0 is treated by the kernel as if it had come in from a LAN
+ to the device tap0; everything the kernel wants to send out over the
+ device tap0 can instead be read by the user from /dev/tap0: the user
+ mode program replaces the LAN that would be attached to an ordinary
+ ethernet device. Please read the file
+ Documentation/networking/ethertap.txt for more information. 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 ethertap.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt. If you don't
+ know what to use this for, you don't need it.
Frame Relay (DLCI) support
CONFIG_DLCI
@@ -3096,16 +3492,15 @@
network, usually at the phone company) can carry several logical
point-to-point connections to other computers connected to the frame
relay network. For a general explanation of the protocol, check out
- http://frame-relay.indiana.edu/4000/4000index.html on the WWW. (To
- browse the WWW, you need to have access to a machine on the Internet
- that has a program like lynx or netscape.) To use frame relay, you
- need supporting hardware (FRAD) and certain programs from the
- net-tools package as explained in
- Documentation/networking/framerelay.txt. This driver is also
+ http://www.frforum.com/ on the WWW. (To browse the WWW, you need to
+ have access to a machine on the Internet that has a program like
+ lynx or netscape.) To use frame relay, you need supporting hardware
+ (FRAD) and certain programs from the net-tools package as explained
+ in Documentation/networking/framerelay.txt. 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 dlci.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt.
+ called dlci.o. If you want to compile it as a module, say M here and
+ read Documentation/modules.txt.
Max open DLCI
CONFIG_DLCI_COUNT
@@ -3133,13 +3528,13 @@
WAN Router
CONFIG_WAN_ROUTER
- Wide Area Networks (WANs), such as X.25, frame relay and leased
+ Wide Area Networks (WANs), such as X.25, frame relay and leased
lines, are used to interconnect Local Area Networks (LANs) over vast
distances with data transfer rates significantly higher than those
achievable with commonly used asynchronous modem connections.
Usually, a quite expensive external device called `WAN router' is
needed to connect to a WAN.
- As an alternative, WAN routing can be built into the Linux
+ As an alternative, WAN routing can be built into the Linux
kernel. With relatively inexpensive WAN interface cards available
on the market, a perfectly usable router can be built for less than
half the price of an external router. If you have one of those
@@ -3148,38 +3543,147 @@
need a wan-tools package available via FTP (user: anonymous) from
ftp.sangoma.com. Read Documentation/networking/wan-router.txt for
more information.
- WAN routing is always built as a module ( = code which can be
+ WAN routing is always built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called wanrouter.o. For general information about
modules read Documentation/modules.txt.
+CPU is too slow to handle full bandwidth
+CONFIG_CPU_IS_SLOW
+###
+### How to know when the CPU is too slow?
+###
+
+QoS and/or fair queueing
+CONFIG_NET_SCHED
+ When the kernel has several packets to send out over the network
+ devices, it has to make a decision which one to send first. This is
+ especially important if some of the network devices are real time
+ devices that need a certain minimum data flow rate. There are
+ several different algorithms how to do this "fairly"; they are
+ called packet schedulers. You can attach different schedulers to
+ different network devices. If you want to stick to the default
+ scheduling algorithm, say N here. If you want to experiment with a
+ couple of different algorithms, say Y. The available schedulers are
+ listed in the following questions; you can say Y to as many as you
+ like. If unsure, say N now.
+
+CBQ packet scheduler
+CONFIG_NET_SCH_CBQ
+ Say Y here if you want to use the Class-Based Queueing (CBQ) packet
+ scheduling algorithm for some of your network devices. This
+ algorithm classifies the waiting packets into a tree-like hierarchy
+ of classes; the leaves of this tree are in turn scheduled by
+ separate algorithms (called "disciplines" in this context) which you
+ can choose below from among the "auxiliary disciplines". See the top
+ of net/sched/sch_cbq.c for references about the CBQ algorithm.
+ This code is also available as a
+ module called sch_cbq.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
+ Documentation/modules.txt.
+
+CSZ packet scheduler
+CONFIG_NET_SCH_CSZ
+ Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
+ scheduling algorithm for some of your network devices. At the
+ moment, this is the only algorithm that can guarantee service for
+ real-time applications (see the top of net/sched/sch_csz.c for
+ details and references about the algorithm). This code is also
+ available as a module called sch_csz.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
+ Documentation/modules.txt.
+
+RED queueing discipline
+CONFIG_NET_SCH_RED
+ Say Y here if you want to use the Random Early Detection (RED)
+ packet scheduling algorithm for some of your network devices (see
+ the top of net/sched/sch_red.c for details and references about the
+ algorithm). This code is also available as a module called sch_red.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 Documentation/modules.txt.
+
+SFQ queueing discipline
+CONFIG_NET_SCH_SFQ
+ Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
+ packet scheduling algorithm for some of your network devices or as a
+ leaf discipline for the CBQ scheduling algorithm (see the top of
+ net/sched/sch_sfq.c for details and references about the SFQ
+ algorithm). This code is also available as a module called sch_sfq.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 Documentation/modules.txt.
+
+auxiliary TBF queue
+CONFIG_NET_SCH_TBF
+ Say Y here if you want to use the Simple Token Bucket Filter (TBF)
+ packet scheduling algorithm for some of your network devices or as a
+ leaf discipline for the CBQ scheduling algorithm (see the top of
+ net/sched/sch_tbf.c for a description of the TBF algorithm). This code
+ is also available as a module called sch_tbf.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
+ Documentation/modules.txt.
+
+auxiliary FIFO queue
+CONFIG_NET_SCH_PFIFO
+ Say Y here if you want to use a simple FIFO (first in - first out)
+ packet "scheduler" for some of your network devices or as a leaf
+ discipline for the CBQ scheduling algorithm. This code is also
+ available as a module called sch_fifo.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
+ Documentation/modules.txt.
+
+auxiliary PRIO queue
+CONFIG_NET_SCH_PRIO
+ Say Y here if you want to use an n-band priority queue packet
+ "scheduler" for some of your network devices or as a leaf discipline
+ for the CBQ scheduling algorithm. This code is also available as a
+ module called sch_prio.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
+ Documentation/modules.txt.
+###
+### what user level programs are needed to administrate these packet
+### schedulers?
+###
+
WAN Drivers
CONFIG_WAN_DRIVERS
- Say 'Y' to this option if you are planning to use your Linux box
- as a WAN router ( = device used to interconnect local area networks
- over wide area communication links, such as leased lines and public
- data networks, e.g. X.25 and frame relay) and you will be offered a
- list of WAN drivers currently available. For more information, read
- Documentation/networking/wan-router.txt.
+ Say Y to this option if you are planning to use your Linux box as a
+ WAN ( = Wide Area Network) router ( = device used to interconnect
+ local area networks over wide area communication links, such as
+ leased lines and public data networks, e.g. X.25 and frame relay)
+ and you will be offered a list of WAN drivers currently available.
+ For more information, read
+ Documentation/networking/wan-router.txt. Note that the answer to
+ this question won't directly affect the kernel: saying N will just
+ cause this configure script to skip all the questions about WAN
+ drivers. If unsure, say N.
Sangoma WANPIPE(tm) multiprotocol cards
CONFIG_VENDOR_SANGOMA
- WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com)
- is a family of intelligent multiprotocol WAN adapters with data
- transfer rates up to T1 (1.544 Mbps). They are also known as
- Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
- or S508. These cards support the X.25, Frame Relay, and PPP
- protocols. If you have one or more of these cards, say 'Y' to this
- option. The next questions will ask you about the protocols you
- want the driver to support. The driver will be compiled as a module
- ( = code which can be inserted in and removed from the running
- kernel whenever you want). The module will be called wanpipe.o.
- For general information about modules read
+ WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com; to
+ browse the WWW, you need to have access to a machine on the Internet
+ that has a program like lynx or netscape) is a family of intelligent
+ multiprotocol WAN adapters with data transfer rates up to T1 (1.544
+ Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
+ and designated S502E(A), S503 or S508. These cards support the X.25,
+ Frame Relay, and PPP protocols. If you have one or more of these
+ cards, say Y to this option and read
+ Documentation/networking/wanpipe.txt. The next questions will ask
+ you about the protocols you want the driver to support. The driver
+ will be compiled as a module ( = code which can be inserted in and
+ removed from the running kernel whenever you want). The module will
+ be called wanpipe.o. For general information about modules read
Documentation/modules.txt.
Maximum number of cards
CONFIG_WANPIPE_CARDS
- Enter number of WANPIPE adapters installed in your machine. The
+ Enter number of WANPIPE adapters installed in your machine. The
driver can support up to 8 cards. You may enter more than you
actually have if you plan to add more cards in the future without
re-compiling the driver, but remember that in this case you'll waste
@@ -3187,22 +3691,26 @@
WANPIPE X.25 support
CONFIG_WANPIPE_X25
- Say 'Y' to this option, if you are planning to connect a WANPIPE
- card to an X.25 network. If you say 'N', the X.25 support will not
- be included in the driver (saves about 16K of kernel memory).
+ Say Y to this option, if you are planning to connect a WANPIPE card
+ to an X.25 network. You should then also have said Y to "CCITT X.25
+ Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
+ X.25 support will not be included in the driver (saves about 16K of
+ kernel memory).
WANPIPE Frame Relay support
CONFIG_WANPIPE_FR
- Say 'Y' to this option, if you are planning to connect a WANPIPE
- card to a frame relay network. If you say 'N', the frame relay
+ Say Y to this option, if you are planning to connect a WANPIPE card
+ to a frame relay network. You should then also have said Y to "Frame
+ Relay (DLCI) support", above. If you say N, the frame relay
support will not be included in the driver (saves about 16K of
kernel memory).
WANPIPE PPP support
CONFIG_WANPIPE_PPP
- Say 'Y' to this option, if you are planning to connect a WANPIPE
- card to a leased line using Point-to-Point protocol (PPP). If you
- say 'N', the PPP support will not be included in the driver (saves
+ Say Y to this option, if you are planning to connect a WANPIPE card
+ to a leased line using Point-to-Point protocol (PPP). You should
+ then also have said Y to "PPP (point-to-point) support", above. If
+ you say N, the PPP support will not be included in the driver (saves
about 16K of kernel memory).
Sun LANCE Ethernet support
@@ -3246,10 +3754,7 @@
the answer to this question doesn't directly affect the kernel:
saying N will just cause this configure script to skip all the
questions about Western Digital cards. If you say Y, you will be
- asked for your specific card in the following questions. If you plan
- to use more than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+ asked for your specific card in the following questions.
WD80*3 support
CONFIG_WD80x3
@@ -3287,20 +3792,76 @@
This is support for the SMC9xxx based Ethernet cards. Choose this
option if you have a DELL laptop with the docking station, or
another SMC9192/9194 based chipset. Say Y if you want it compiled
- into the kernel, and read the the file drivers/net/README.smc9 and
- the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/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 smc9194.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. If you plan to use more
- than one network card under linux, read the
+ into the kernel, and read the the file
+ Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
+ via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/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 smc9194.o. If you want to compile
+ it as a module, say M here and read Documentation/modules.txt as
+ well as Documentation/networking/net-modules.txt. If you plan to use
+ more than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-AMD LANCE and PCnet (AT1500 and NE2100) support
-CONFIG_LANCE
+Racal-Interlan (Micom) NI cards
+CONFIG_NET_VENDOR_RACAL
+ If you have a network (ethernet) card belonging to this class, such
+ as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
+ available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than
+ one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
+ available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Note that
+ the answer to this question doesn't directly affect the kernel:
+ saying N will just cause this configure script to skip all the
+ questions about NI cards. If you say Y, you will be asked for your
+ specific card in the following questions.
+
+NI5010 support
+CONFIG_NI5010
+ If you have a network (ethernet) card of this type, say Y and read
+ the Ethernet-HOWTO, available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that this is still
+ experimental code. 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
+ ni5010.o. If you want to compile it as a module, say M here and read
+ Documentation/modules.txt as well as
+xIO Documentation/networking/net-modules.txt. If you plan to use more
+ than one network card under linux, read the
+ Multiple-Ethernet-mini-HOWTO, available from
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+
+NI5210 support
+CONFIG_NI52
+ If you have a network (ethernet) card of this type, say Y and read
+ the Ethernet-HOWTO, available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/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
+ ni52.o. If you want to compile it as a module, say M here and read
+ Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt. If you plan to use more
+ than one network card under linux, read the
+ Multiple-Ethernet-mini-HOWTO, available from
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+
+NI6510 support
+CONFIG_NI65
+ If you have a network (ethernet) card of this type, say Y and read
+ the Ethernet-HOWTO, available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/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
+ ni65.o. If you want to compile it as a module, say M here and read
+ Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt. If you plan to use more
+ than one network card under linux, read the
+ Multiple-Ethernet-mini-HOWTO, available from
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+
+AMD LANCE and PCnet (AT1500 and NE2100) support
+CONFIG_LANCE
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. Some LinkSys cards are of
@@ -3444,7 +4005,7 @@
(arguably) beautiful poetry in Documentation/networking/arcnet.txt.
You need both this driver, and the driver for the particular ARCnet
chipset of your card. If you don't know, then it's probably a
- COM90xx type card, so say Y (or M) to ARCnet COM90xx chipset support
+ COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset support"
below.
You might also want to have a look at the Ethernet-HOWTO, available
via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO
@@ -3457,7 +4018,7 @@
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-
+
Enable arc0e (ARCnet "ether-encap" packet format)
CONFIG_ARCNET_ETH
This allows you to use "ethernet encapsulation" with your ARCnet
@@ -3483,30 +4044,50 @@
documentation in Documentation/networking/arcnet.txt for more
information about using arc0e and arc0s.
-ARCnet COM90xx chipset support
+ARCnet COM90xx (normal) chipset driver
CONFIG_ARCNET_COM90xx
- This is the chipset driver for the standard COM90xx cards. If you always
- used the old arcnet driver without knowing what type of card you had,
- this is probably the one for you.
-
-ARCnet COM90xx IO mapped mode chipset support
-CONFIG_ARCNET_COM90xxIO
- This is the chipset driver for the COM90xx cards, using them in IO-mapped
- mode instead of memory-mapped mode. This is slower than the normal driver.
- Only use it if your card doesn't support shared memory.
+ This is the chipset driver for the standard COM90xx cards. If you
+ have always used the old arcnet driver without knowing what type of
+ card you had, this is probably the one for you. 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 com90xx.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt.
-ARCnet RIM I chipset support
+ARCnet COM90xx (IO mapped) chipset driver
+CONFIG_ARCNET_COM90x
+ This is the chipset driver for the COM90xx cards, using them in
+ IO-mapped mode instead of memory-mapped mode. This is slower than
+ the normal driver. Only use it if your card doesn't support shared
+ memory. 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 com90io.o. If you want to compile
+ it as a module, say M here and read Documentation/modules.txt as
+ well as Documentation/networking/net-modules.txt.
+
+ARCnet COM90xx (RIM I) chipset driver
CONFIG_ARCNET_RIM_I
- This is yet another chipset driver for the COM90xx cards, but this time
- only using memory-mapped mode, and no IO ports at all. This driver is
- completely untested, so if you have one of these cards, please mail
- dwmw2@cam.ac.uk, especially if it works!
+ This is yet another chipset driver for the COM90xx cards, but this
+ time only using memory-mapped mode, and no IO ports at all. This
+ driver is completely untested, so if you have one of these cards,
+ please mail dwmw2@cam.ac.uk, especially if it works!
+ 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 arc-rimi.o. If you want to compile
+ it as a module, say M here and read Documentation/modules.txt as
+ well as Documentation/networking/net-modules.txt.
-ARCnet COM20020 chipset support
+ARCnet COM20020 chipset driver
CONFIG_ARCNET_COM20020
- This is the driver for the new COM20020 chipset. It supports such things
- as promiscuous mode, so packet sniffing is possible, and extra diagnostic
- information.
+ This is the driver for the new COM20020 chipset. It supports such
+ things as promiscuous mode, so packet sniffing is possible, and
+ extra diagnostic information. 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
+ com20020.o. If you want to compile it as a module, say M here and
+ read Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt.
Cabletron E21xx support
CONFIG_E2100
@@ -3553,12 +4134,13 @@
EtherWorks 3 support
CONFIG_EWRK3
This driver supports the DE203, DE204 and DE205 network (ethernet)
- cards. If this is for you, say Y and read drivers/net/README.ewrk3
- in the kernel source as well as the Ethernet-HOWTO, available via
- ftp (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/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 Documentation/modules.txt as well as
+ cards. If this is for you, say Y and read
+ Documentation/networking/ewrk3.txt in the kernel source as well as
+ the Ethernet-HOWTO, available via ftp (user: anonymous) from
+ sunsite.unc.edu:/pub/Linux/docs/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
+ Documentation/modules.txt as well as
Documentation/networking/net-modules.txt. The module will be called
ewrk3.o. If you plan to use more than one network card under linux,
read the Multiple-Ethernet-mini-HOWTO, available from
@@ -3633,40 +4215,6 @@
linux, read the Multiple-Ethernet-mini-HOWTO, available from
sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-NI5010 support
-CONFIG_NI5010
- If you have a network (ethernet) card of this type, say Y and read
- the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than
- one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
- available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
- Note that this is still experimental code. If you use this driver,
- please contact the authors to join the development team.
-
-NI5210 support
-CONFIG_NI52
- If you have a network (ethernet) card of this type, say Y and read
- the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/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
- ni52.o. If you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. If you plan to use more than
- one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
- available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-
-NI6510 support
-CONFIG_NI65
- If you have a network (ethernet) card of this type, say Y and read
- the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you want to compile it as
- a module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- ni65.o. If you plan to use more than one network card under linux,
- read the Multiple-Ethernet-mini-HOWTO, available from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-
AT&T WaveLAN & DEC RoamAbout DS support
CONFIG_WAVELAN
The Lucent Wavelan (formerly NCR and AT&T ; or DEC RoamAbout DS) is
@@ -3678,8 +4226,9 @@
If you want to use a card of this type under Linux, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. Some more specific
- information is contained in drivers/net/README.wavelan. You will
- also need the wireless tools package available from
+ information is contained in
+ Documentation/networking/wavelan.txt. You will also need the
+ wireless tools package available from
ftp://ftp.inka.de/pub/comp/Linux/networking/NetTools/contrib/.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
@@ -3759,18 +4308,18 @@
This is another class of network cards which attach directly to the
bus. If you have one of those, say Y and read the Ethernet-HOWTO,
available via ftp (user: anonymous) from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO; if you are unsure, say
- Y. Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
- the questions about this class of network cards. If you say Y, you
- will be asked for your specific card in the following questions. If
- you plan to use more than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than
+ one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
+ available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. If you
+ are unsure, say Y. Note that the answer to this question doesn't
+ directly affect the kernel: saying N will just cause this configure
+ script to skip all the questions about this class of network
+ cards. If you say Y, you will be asked for your specific card in the
+ following questions.
AMD PCnet32 (VLB and PCI) support
CONFIG_PCNET32
- if you have a PCnet32 or PCnetPCI based network (ethernet) card, say
+ If you have a PCnet32 or PCnetPCI based network (ethernet) card, say
Y here and read the Ethernet-HOWTO, available via ftp (user:
anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to
use more than one network card under linux, read the
@@ -3825,11 +4374,11 @@
models. If you have a network card of this type, say Y and read the
Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
- contained in drivers/net/README.de4x5. 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
- de4x5.o. If you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
+ contained in Documentation/networking/de4x5.txt. 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 de4x5.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt as well as
Documentation/networking/net-modules.txt. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
@@ -3860,11 +4409,11 @@
models. If you have a network card of this type, say Y and read the
Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
- contained in drivers/net/README.dgrs. 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
- dgrs.o. If you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
+ contained in Documentation/networking/dgrs.txt. 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 dgrs.o. If you want to compile it as a module, say M here and
+ read Documentation/modules.txt as well as
Documentation/networking/net-modules.txt. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
@@ -3948,8 +4497,8 @@
D-Link DE600 pocket adapter support
CONFIG_DE600
This is a network (ethernet) device which attaches to your parallel
- port. Read drivers/net/README.DLINK as well as the Ethernet-HOWTO,
- available via ftp (user: anonymous) from
+ port. Read Documentation/networking/DLINK.txt as well as the
+ Ethernet-HOWTO, available via ftp (user: anonymous) from
sunsite.unc.edu:/pub/Linux/docs/HOWTO if you want to use this. It is
possible to have several devices share a single parallel port and it
is safe to compile the corresponding drivers into the kernel. If you
@@ -3963,8 +4512,8 @@
D-Link DE620 pocket adapter support
CONFIG_DE620
This is a network (ethernet) device which attaches to your parallel
- port. Read drivers/net/README.DLINK as well as the Ethernet-HOWTO,
- available via ftp (user: anonymous) from
+ port. Read Documentation/networking/DLINK.txt as well as the
+ Ethernet-HOWTO, available via ftp (user: anonymous) from
sunsite.unc.edu:/pub/Linux/docs/HOWTO if you want to use this. It is
possible to have several devices share a single parallel port and it
is safe to compile the corresponding drivers into the kernel. If you
@@ -3974,7 +4523,7 @@
will be called de620.o. If you plan to use more than one network
card under linux, read the Multiple-Ethernet-mini-HOWTO, available
from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
-
+
Token Ring driver support
CONFIG_TR
Token Ring is IBM's way of communication on a local network; the
@@ -4031,9 +4580,9 @@
For each of these drivers, a file Documentation/cdrom/<driver_name>
exists. Especially in cases where you do not know exactly which kind
of drive you have you should read there.
- Most of these drivers use a file drivers/cdrom/<driver_name>.h where
- you can define your interface parameters and switch some internal
- goodies.
+ Most of these drivers use a file drivers/cdrom/<driver_name>.h
+ where you can define your interface parameters and switch some
+ internal goodies.
All these CDROM drivers are also usable as a module (= code which can
be inserted in and removed from the running kernel whenever you want).
If you want to compile them as module, say M instead of Y and read
@@ -4049,7 +4598,7 @@
will not be auto detected by the kernel at boot time; you have to
provide the interface address as an option to the kernel at boot
time as described in Documentation/cdrom/cdu31a or fill in your
- parameters into linux/drivers/cdrom/cdu31a.c. Try "man bootparam" or
+ parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
see the documentation of your boot loader (lilo or loadlin) about
how to pass options to the kernel. The lilo procedure is also
explained in the SCSI-HOWTO. If you say Y here, you should also say
@@ -4072,7 +4621,7 @@
(PhotoCDs). There is a new driver (next question) which can do
this. If you want that one, say N here.
If the driver doesn't work out of the box, you might want to have a
- look at linux/drivers/cdrom/mcd.h. If you say Y here, you should
+ look at drivers/cdrom/mcd.h. If you say Y here, you should
also say Y to "ISO9660 cdrom filesystem support" below, because
that's the filesystem used on CDROMs. Please also read the file
Documentation/cdrom/mcd. This driver is also available as a module (
@@ -4116,7 +4665,7 @@
are not sure, but can consume some time during the boot process if
none of the supported drives gets found.
Once your drive got found, you should enter the reported parameters
- into linux/drivers/cdrom/sbpcd.h and set "DISTRIBUTION 0" there.
+ into drivers/cdrom/sbpcd.h and set "DISTRIBUTION 0" there.
This driver can support up to four CDROM interface cards, and each
card can support up to four CDROM drives; if you say Y here, you
will be asked how many controllers you have. If compiled as a
@@ -4135,7 +4684,7 @@
Say Y here only if you have two CDROM controller boards of this type
(usually only if you have more than four drives). You should enter
the parameters for the second, third and fourth interface card into
- linux/drivers/cdrom/sbpcd.h before compiling the new kernel. Read
+ linux/include/linux/sbpcd.h before compiling the new kernel. Read
the file Documentation/cdrom/sbpcd.
Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
@@ -4167,29 +4716,14 @@
CONFIG_GSCD
If this is your CDROM drive, say Y here. As described in
linux/Documentation/cdrom/gscd, you might have to change a setting
- in the file linux/drivers/cdrom/gscd.h before compiling the kernel.
- Please read the file Documentation/cdrom/gscd. If you say Y here,
- you should also say Y to "ISO9660 cdrom filesystem support" below,
- because that's the filesystem used on CDROMs. 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 gscd.o. If you want to compile it as a module, say M here and
- read Documentation/modules.txt.
-
-MicroSolutions backpack CDROM support
-CONFIG_BPCD
- MicroSolutions backpack CDROM is an external drive that connects to
- the parallel port. This driver supports model 164550 (and perhaps
- other models). Say Y if you have one of these, and read the file
- Documentation/cdrom/bpcd. If you say Y here, you should also say Y
- to "ISO9660 cdrom filesystem support" below, because that's the
- filesystem used on CDROMs. It is possible for several devices to
- share a parallel port and it is safe to compile the corresponding
- drivers all into the kernel. 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
- bpcd.o. If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ in the file linux/drivers/cdrom/gscd.h before compiling the
+ kernel. Please read the file Documentation/cdrom/gscd. If you say Y
+ here, you should also say Y to "ISO9660 cdrom filesystem support"
+ below, because that's the filesystem used on CDROMs. 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 gscd.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt.
Philips/LMS CM206 CDROM support
CONFIG_CM206
@@ -4263,10 +4797,10 @@
If you say Y here, you will be able to set per user limits for disk
usage (also called diskquotas). Currently, it works only for the
ext2 filesystem. You need additional software in order to use quota
- support; it is available via ftp (user: anonymous) from
- ftp.funet.fi/pub/Linux/kernel/src/subsystems/quota/. Probably the
- quota support is only useful for multi user systems. If unsure, say
- N.
+ support; for details, read the Quota mini-HOWTO, available via ftp
+ (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Probably the quota
+ support is only useful for multi user systems. If unsure, say N.
Online mirror support
CONFIG_OMIRR
@@ -4461,6 +4995,33 @@
compiled as a module, and so this could be dangerous. Most everyone
wants to say Y here.
+ISO9660 cdrom filesystem support
+CONFIG_ISO9660_FS
+ This is the standard filesystem used on CDROMs. It was previously
+ known as "High Sierra Filesystem" 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 CDROM drive and want to do more with it than
+ just listen to audio CDs and watch its LEDs, say Y (and read
+ Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
+ via ftp (user: anonymous) from
+ sunsite.unc.edu:/pub/Linux/docs/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
+ Documentation/modules.txt. The module will be called isofs.o.
+
+Microsoft Joliet cdrom extensions
+CONFIG_JOLIET
+ Joliet is a Microsoft extension for the ISO9660 CDROM filesystem
+ 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; to browse the WWW, you
+ need to have access to a machine on the Internet that has a program
+ like lynx or netscape). Say Y here if you want to be able to read
+ Joliet CDROMs under Linux.
+
fat fs support
CONFIG_FAT_FS
If you want to use one of the FAT-based filesystems (the MS-DOS,
@@ -4485,7 +5046,7 @@
Linux, you can either use the DOS emulator DOSEMU, described in the
DOSEMU-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/HOWTO, or try dmsdosfs in
- sunsite.unc.edu:/pub/Linux/system/Filesystems/dosfs. If you intend
+ sunsite.unc.edu:/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.
@@ -4541,154 +5102,6 @@
umsdos.o. Note that the filesystem of your root partition cannot be
a module, so this could be dangerous. If unsure, say N.
-nls: Native language codepages and Unicode support
-CONFIG_NLS
- This is required by the FAT filesystems and by the ISO9660 filesystem
- when it is compiled with Joliet support. Joliet is a Microsoft
- extension for CDROMs that supports Unicode. This allows translation
- between different character sets. When dealing with the FAT based
- filesystems, there are two character sets that are important. The
- first is the codepage. Codepages are character sets that are used by
- DOS to allow filenames to have native language characters when
- character sets were limited to 256 characters. The codepage is the
- character set that is used to store native language characters on
- disk. The two most common codepages are 437 in the United States and
- 850 in much of Europe. The second important character set is the
- input/output character set. This is the character set that is
- displayed on the screen. In the United States, this will almost always
- be the ISO 8859-1 character set. This is the default. Linux will only
- do a translation of the FAT filenames, not the contents of the files.
-
-nls iso8859-1
-CONFIG_NLS_ISO8859_1
- ISO8859-1 is the Latin 1 character set, and it covers most West
- European languages such as Albanian, Catalan, Danish, Dutch, English,
- Faeroese, Finnish, French, German, Galician, Irish, Icelandic, Italian,
- Norwegian, Portuguese, Spanish, Swedish, and Valencian.
-
-nls iso8859-2
-CONFIG_NLS_ISO8859_2
- ISO8859-2 is the Latin 2 character set, and it works for most
- Latin-written Slavic and Central European languages: Czech, German,
- Hungarian, Polish, Rumanian, Croatian, Slovak, Slovene.
-
-nls iso8859-3
-CONFIG_NLS_ISO8859_3
- ISO8859-3 is the Latin 3 character set, and it s popular with authors
- of Esperanto, Galician, Maltese, and Turkish.
-
-nls iso8859-4
-CONFIG_NLS_ISO8859_4
- ISO8859-4 is the Latin 4 character set, and it introduces letters
- for Estonian, Latvian, and Lithuanian. It is an incomplete predecessor of
- Latin 6.
-
-nls iso8859-5
-CONFIG_NLS_ISO8859_5
- ISO8859-5 is a Cyrillic character set, and you can type Bulgarian,
- Byelorussian, Macedonian, Russian, Serbian, and Ukrainian.
- Note that the charset KOI8-R is preferred in Russia.
-
-nls iso8859-6
-CONFIG_NLS_ISO8859_6
- ISO8859-6 is the Arabic character set.
-
-nls iso8859-7
-CONFIG_NLS_ISO8859_7
- ISO8859-7 is the Modern Greek character set.
-
-nls iso8859-8
-CONFIG_NLS_ISO8859_8
- ISO8859-8 is the Hebrew character set.
-
-nls iso8859-9
-CONFIG_NLS_ISO8859_9
- ISO8859-9 is the Latin 5 character set, and it replaces the rarely
- needed Icelandic letters in Latin 1 with the Turkish ones. Useful in
- Turkey.
-
-nls iso8859-10
-CONFIG_NLS_ISO8859_10
- ISO8859-10 is the Latin 6 character set, and it adds the last Inuit
- (Greenlandic) and Sami (Lappish) letters that were missing in Latin 4 to
- cover the entire Nordic area.
-
-nls koi8-r
-CONFIG_NLS_KOI8_R
- This is the preferred Russian character set.
-
-nls codepage 437
-CONFIG_NLS_CODEPAGE_437
- This is the DOS codepage that is used in the United States and parts of
- Canada.
-
-nls codepage 737
-CONFIG_NLS_CODEPAGE_737
- This is the codepage used by DOS for Greek.
-
-nls codepage 775
-CONFIG_NLS_CODEPAGE_775
- This is the codepage used by DOS for the Baltic Rim Languages.
-
-nls codepage 850
-CONFIG_NLS_CODEPAGE_850
- This is the DOS codepage that is used in 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
- codepage 437.
-
-nls codepage 852
-CONFIG_NLS_CODEPAGE_852
- This is 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, Romanian, Serbian (Latin transcription), Slovak, Slovenian, and
- Sorbian.
-
-nls codepage 855
-CONFIG_NLS_CODEPAGE_855
- This is the DOS codepage that is used for Cyrillic.
-
-nls codepage 857
-CONFIG_NLS_CODEPAGE_857
- This is the DOS codepage that is used for Turkish.
-
-nls codepage 860
-CONFIG_NLS_CODEPAGE_860
- This is the DOS codepage that is used for Portuguese.
-
-nls codepage 861
-CONFIG_NLS_CODEPAGE_861
- This is the DOS codepage that is used for Icelandic.
-
-nls codepage 862
-CONFIG_NLS_CODEPAGE_862
- This is the DOS codepage that is used for Hebrew.
-
-nls codepage 863
-CONFIG_NLS_CODEPAGE_863
- This is the DOS codepage that is used for Canadian French.
-
-nls codepage 864
-CONFIG_NLS_CODEPAGE_864
- This is the DOS codepage that is used for Arabic.
-
-nls codepage 865
-CONFIG_NLS_CODEPAGE_865
- This is the DOS codepage that is used in the Nordic European countries.
-
-nls codepage 866
-CONFIG_NLS_CODEPAGE_866
- This is the DOS codepage that is used for Cyrillic/Russian.
-
-nls codepage 869
-CONFIG_NLS_CODEPAGE_869
- This is the DOS codepage that is used for Greek.
-
-nls codepage 874
-CONFIG_NLS_CODEPAGE_874
- This is the DOS codepage that is used for Thai.
-
/proc filesystem support
CONFIG_PROC_FS
This is a virtual filesystem providing information about the status
@@ -4697,16 +5110,17 @@
them. Also, you cannot read the files with less: you need to use
more or cat. The filesystem is explained in the Kernel Hacker's
Guide at http://www.redhat.com:8080/HyperNews/get/khg.html on the
- Web, and also on the proc(8) manpage ("man 8 proc"). This option
- will enlarge your kernel by about 18 kB. 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). Several programs depend on this, so everyone should say Y
- here.
-
+ WWW (to browse the WWW, you need to have access to a machine on the
+ Internet that has a program like lynx or netscape), and also on the
+ proc(8) manpage ("man 8 proc"). This option will enlarge your
+ kernel by about 18 kB. 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). Several
+ programs depend on this, so everyone should say Y here.
+
NFS filesystem support
CONFIG_NFS_FS
If you are connected to some other (usually local) Unix computer
@@ -4730,7 +5144,7 @@
Documentation/modules.txt. If you configure a diskless machine which
will mount its root filesystem over nfs (in order to do that, check
out the netboot package, available via ftp (user: anonymous) from
- sunsite.unc.edu in /pub/Linux/system/Linux-boot/, extract with "tar
+ sunsite.unc.edu in /pub/Linux/system/boot/ethernet/, extract with "tar
xzvf filename", and say Y to "Root file system on NFS" below), then
you cannot compile this driver as a module. If you don't know what
all this is about, say N.
@@ -4759,20 +5173,28 @@
module, say M here and read Documentation/modules.txt. If unsure,
say N.
-ISO9660 cdrom filesystem support
-CONFIG_ISO9660_FS
- This is the standard filesystem used on CDROMs. It was previously
- known as "High Sierra Filesystem" and is called "hsfs" on other Unix
- systems. The so-called Rock-Ridge extensions which allow for long
- Unix filenames are also supported by this driver. If you have a
- CDROM drive and want to do more with it than just listen to audio
- CDs and watch its LEDs, say Y (and read the CDROM-HOWTO, available
- via ftp (user: anonymous) from
- sunsite.unc.edu:/pub/Linux/docs/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
- Documentation/modules.txt. The module will be called isofs.o.
+BOOTP support
+CONFIG_RNFS_BOOTP
+ If you want your Linux box to mount its whole root filesystem from
+ some other computer over the net via NFS and you want the IP address
+ of your computer to be discovered automatically at boot time using
+ the BOOTP protocol (a special protocol designed for doing this job),
+ say Y here. In case the boot ROM of your network card was designed
+ for booting Linux and does BOOTP itself, providing all necessary
+ information on the kernel command line, you can say N here. If
+ unsure, say Y. Note that in case you want to use BOOTP, a BOOTP
+ server must be operating on your network. Read
+ Documentation/nfsroot.txt for details.
+
+RARP support
+CONFIG_RNFS_RARP
+ If you want your Linux box to mount its whole root filesystem from
+ some other computer over the net via NFS and you want the IP address
+ of your computer to be discovered automatically at boot time using
+ the RARP protocol (an older protocol which is being obsoleted by
+ BOOTP and DHCP), say Y here. Note that in case you want to use RARP,
+ a RARP server must be operating on your network. Read
+ Documentation/nfsroot.txt for details.
OS/2 HPFS filesystem support (read only)
CONFIG_HPFS_FS
@@ -4793,15 +5215,21 @@
NTFS is the file system of Microsoft Windows NT. Say Y if you want
to access partitions using this file system. The Linux NTFS driver
supports most of the mount options of the VFAT driver, see
- Documentation/filesystems/ntfs.txt. There is an experimental
- write support available; use at your own risk.
+ 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 Documentation/modules.txt.
NTFS read-write support (experimental)
CONFIG_NTFS_RW
- The read-write support in NTFS is far from being complete and well
- tested. If you enable this, be prepared to recover the NTFS volume
- from tape.
-
+ If you say Y here, you will (hopefully) be able to write to NTFS
+ file systems as well as to read from them. The read-write support
+ in NTFS is far from being complete and is not well tested. If you
+ enable this, be prepared to recover the NTFS volume from tape. If
+ unsure, say N.
+
System V and Coherent filesystem support
CONFIG_SYSV_FS
SCO, Xenix and Coherent are commercial Unix systems for intel
@@ -4819,15 +5247,15 @@
nfs filesystem 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"). Note
- also that this option has nothing whatsoever to do with the option
- "System V IPC". Read about the System V filesystem in
- Documentation/filesystems/sysv-fs.txt. This option will enlarge your
- kernel by about 34 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
- 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.
+ 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 filesystem in Documentation/filesystems/sysv-fs.txt. This
+ option will enlarge your kernel by about 34 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 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.
Kernel automounter support (experimental)
CONFIG_AUTOFS_FS
@@ -4848,42 +5276,54 @@
CONFIG_UFS_FS
BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD
and NeXTstep) use a filesystem called UFS. Some System V Unixes can
- create and mount partitions and diskettes using this filesystem as
- well. Saying Y here allows you to mount these partitions and
- diskettes read-only. If you only intend to mount files from some
- other Unix over the network using NFS, you don't need the UFS
- filesystem support (but you need nfs filesystem support
+ create and mount harddisk partitions and diskettes using this
+ filesystem as well. Saying Y here allows you to mount these
+ partitions and diskettes read-only. If you only intend to mount
+ files from some other Unix over the network using NFS, you don't
+ need the UFS filesystem support (but you need nfs filesystem 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"). When accessing NeXTstep files,
- you may need to convert them from the NeXT character set to the
- Latin1 character set; use GNU recode for this purpose. Say Y to
- build UFS support into your kernel. 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 ufs.o. If you
- haven't heard about all of this before, it's safe to say N.
+ 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
+ for this purpose. Say Y to build UFS read support into your
+ kernel. 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 ufs.o. If you haven't heard about all of this before,
+ it's safe to say N.
BSD disklabel (FreeBSD partition tables) support
CONFIG_BSD_DISKLABEL
- FreeBSD uses its own 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 disklabel format. Saying Y here allows you to
- read these disklabels and further mount FreeBSD partitions on your
- Linux box if you also have configured BSD ufs filesystem support. If
- you don't know what all this is about, say N.
+ FreeBSD uses its own harddisk 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 disklabel format. Saying Y
+ here allows you to read these disklabels and further mount FreeBSD
+ partitions read-only from within Linux if you have also said Y to
+ "BSD ufs filesystem support", above. If you don't know what all this
+ is about, say N.
SMD disklabel (Sun partition tables) support
CONFIG_SMD_DISKLABEL
- Like most systems, SunOS uses its own partition table format,
- incompatible with all others. Saying Y here allows you to read these
- partition tables and further mount SunOS disks on your Linux box if
- you also have configured BSD ufs filesystem support. 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. If you don't
- know what all this is about, say N.
+ Like most systems, SunOS uses its own harddisk partition table
+ format, incompatible with all others. Saying Y here allows you to
+ read these partition tables and further mount SunOS disks read-only
+ from within Linux if you have also said Y to "BSD ufs filesystem
+ 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.
+
+Macintosh partition map support
+CONFIG_MAC_PARTITION
+ Say Y here if you want your Linux system to be able to read
+ the partition tables of Macintosh hard drives, and thus use
+ partitions on those drives.
SMB filesystem support (to mount WfW shares etc..)
CONFIG_SMB_FS
@@ -4899,7 +5339,7 @@
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 via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/system/Network/samba) for that. General
+ sunsite.unc.edu:/pub/Linux/system/network/samba) for that. General
information about how to connect Linux, Windows machines and Macs is
on the WWW at http://eats.com/linux_mac_win.html (to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -4911,15 +5351,22 @@
Coda filesystem support
CONFIG_CODA_FS
- CODA is an advanced network filesystem. It has support for disconnected
- operation for laptops, read/write server replication, persistent client
- caches and write back caching.
- By choosing this option you are compiling kernel support for Coda clients
- into the Linux kernel. You will need user level code as well, both for
- the client and server. Server's are currently user level, i.e. need
- no kernel support. For further information see
- http://www.coda.cs.cmu.edu or contact Peter Braam <braam@cs.cmu.edu>.
-
+ CODA is an advanced network filesystem. It has support for
+ disconnected operation for laptops, read/write server replication,
+ persistent client caches and write back caching.
+ By saying Y here you are compiling kernel support for Coda clients
+ into the Linux kernel. You will need user level code as well, both
+ for the client and server. Servers are currently user level,
+ i.e. need no kernel support. For technical information, read
+ Documentation/filesystems/coda.txt.
+ 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
+ Documentation/modules.txt. The module will be called coda.o.
+ For further information see http://www.coda.cs.cmu.edu (to browse
+ the WWW, you need to have access to a machine on the Internet that
+ has a program like lynx or netscape) or contact Peter Braam
+ <braam@cs.cmu.edu>.
SMB Win95 bug work-around
CONFIG_SMB_WIN95
@@ -4946,20 +5393,21 @@
CONFIG_AFFS_FS
The Fast File System (FFS) is the common filesystem used on
harddisks by Amiga(tm) Systems since AmigaOS Version 1.3
- (34.20). With this driver you can also mount diskfiles used by the
- Un*X Amiga Emulator by Bernd Schmidt
- (http://www-users.informatik.rwth-aachen.de/~crux/uae.html). If you
- want to do the latter, you will also need to say Y to "Loop device
- support", above. Say Y if you want to be able to read and write
- files from and to an Amiga FFS partition on your harddrive. 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
- Documentation/filesystems/affs.txt and fs/affs/Changes. This
- filesystem 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 Documentation/modules.txt. If unsure, say N.
+ (34.20). With this driver you can also mount diskfiles used by Bernd
+ Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/;
+ to browse the WWW, you need to have access to a machine on the
+ Internet that has a program like lynx or netscape). If you want to
+ do the latter, you will also need to say Y to "Loop device support",
+ above. Say Y if you want to be able to read and write files from and
+ to an Amiga FFS partition on your harddrive. 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
+ Documentation/filesystems/affs.txt and fs/affs/Changes. This filesystem 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
+ Documentation/modules.txt. If unsure, say N.
ROM filesystem support
CONFIG_ROMFS_FS
@@ -4973,23 +5421,323 @@
and read Documentation/modules.txt. If you don't know whether you
need it, then you don't need it: say N.
+nls: Native language codepages and Unicode support
+CONFIG_NLS
+ This is required by the FAT and NTFS filesystems and by the ISO9660
+ filesystem when it is compiled with Joliet support. Joliet is a
+ Microsoft extension for CDROMs that supports Unicode. This allows
+ translation between different character sets. When dealing with the
+ FAT based filesystems, there are two character sets that are
+ important. The first is the codepage. Codepages are character sets
+ that are used by DOS to allow filenames to have native language
+ characters when character sets were limited to 256 characters. The
+ codepage is the character set that is used to store native language
+ characters on disk. The two most common codepages are 437 in the
+ United States and 850 in much of Europe. The second important
+ character set is the input/output character set. This is the
+ character set that is displayed on the screen. In the United States,
+ this will almost always be the ISO 8859-1 character set. This is the
+ default. Linux will only do a translation of the FAT filenames, not
+ the contents of the files.
+
+nls codepage 437
+CONFIG_NLS_CODEPAGE_437
+ The Microsoft fat filesystem 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.
+
+nls codepage 737
+CONFIG_NLS_CODEPAGE_737
+ The Microsoft fat filesystem 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.
+
+nls codepage 775
+CONFIG_NLS_CODEPAGE_775
+ The Microsoft fat filesystem 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
+ for the Baltic Rim Languages. If unsure, say N.
+
+nls codepage 850
+CONFIG_NLS_CODEPAGE_850
+ The Microsoft fat filesystem 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.
+
+nls codepage 852
+CONFIG_NLS_CODEPAGE_852
+ The Microsoft fat filesystem 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, Romanian, Serbian (Latin
+ transcription), Slovak, Slovenian, and Sorbian.
+
+nls codepage 855
+CONFIG_NLS_CODEPAGE_855
+ The Microsoft fat filesystem 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.
+
+nls codepage 857
+CONFIG_NLS_CODEPAGE_857
+ The Microsoft fat filesystem 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.
+
+nls codepage 860
+CONFIG_NLS_CODEPAGE_860
+ The Microsoft fat filesystem 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.
+
+nls codepage 861
+CONFIG_NLS_CODEPAGE_861
+ The Microsoft fat filesystem 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.
+
+nls codepage 862
+CONFIG_NLS_CODEPAGE_862
+ The Microsoft fat filesystem 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.
+
+nls codepage 863
+CONFIG_NLS_CODEPAGE_863
+ The Microsoft fat filesystem 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.
+
+nls codepage 864
+CONFIG_NLS_CODEPAGE_864
+ The Microsoft fat filesystem 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.
+
+nls codepage 865
+CONFIG_NLS_CODEPAGE_865
+ The Microsoft fat filesystem 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.
+
+nls codepage 866
+CONFIG_NLS_CODEPAGE_866
+ The Microsoft fat filesystem 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.
+
+nls codepage 869
+CONFIG_NLS_CODEPAGE_869
+ The Microsoft fat filesystem 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.
+###
+### Why do we have two codepages for Greek and Cyrillic?
+###
+
+nls codepage 874
+CONFIG_NLS_CODEPAGE_874
+ The Microsoft fat filesystem 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.
+
+nls iso8859-1
+CONFIG_NLS_ISO8859_1
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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,
+ Swedish, and Valencian. It is also the default for the US. If
+ unsure, say Y.
+
+nls iso8859-2
+CONFIG_NLS_ISO8859_2
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the 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 iso8859-3
+CONFIG_NLS_ISO8859_3
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 iso8859-4
+CONFIG_NLS_ISO8859_4
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 6.
+
+nls iso8859-5
+CONFIG_NLS_ISO8859_5
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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, Byelorussian,
+ Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
+ KOI8-R is preferred in Russia.
+
+nls iso8859-6
+CONFIG_NLS_ISO8859_6
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 iso8859-7
+CONFIG_NLS_ISO8859_7
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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.
+
+nls iso8859-8
+CONFIG_NLS_ISO8859_8
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 iso8859-9
+CONFIG_NLS_ISO8859_9
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 iso8859-10
+CONFIG_NLS_ISO8859_10
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ 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 koi8-r
+CONFIG_NLS_KOI8_R
+ If you want to display filenames with native language characters
+ from the Microsoft fat filesystem family or from JOLIET CDROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the preferred Russian
+ character set.
+
Virtual terminal
CONFIG_VT
- This includes support for a terminal device using display and
+ This includes support for a terminal device with display and
keyboard devices. Only people using embedded systems want to say N
- here; most everybody says Y.
+ here; most everybody else says Y. If unsure, say Y, or else you
+ won't be able to do much with your new shiny Linux system :-)
-Console on virtual terminal
+Support for console on virtual terminal
CONFIG_VT_CONSOLE
- If you enable this option, by default all kernel messages will be sent
- to the device /dev/tty0 which corresponds to the virtual terminal you
+ If you say Y here, by default all kernel messages will be sent to
+ the device /dev/tty0 which corresponds to the virtual terminal you
have visible on your display. You should say Y here unless you only
- want to have the kernel messages output on a serial port.
+ want to have the kernel messages output on a serial port (in which
+ case you probably want to say Y to "Console on serial port", below).
Software generated cursor
CONFIG_SOFTCURSOR
- If you enable this option, you'll be able to do lots of nice things
- with your cursor -- for example to turn it into a non-blinking one.
+ If you say Y here, you'll be able to do lots of nice things with the
+ cursors of your virtual consoles -- for example to turn them into
+ non-blinking block cursors which are more visible on laptop screens.
See Documentation/VGA-softcursor.txt for more information.
Standard/generic serial support
@@ -5011,14 +5759,14 @@
that they can use serial mice, modems and similar devices connecting
to the standard serial ports.
-Console on serial port
+Support for console on serial port
CONFIG_SERIAL_CONSOLE
- If you enable this option, it is possible to use a serial port as the
- console. By default still the virtual console will be used at the
- system console but you can alter that using a kernel command line
- option. If you don't have a VGA card installed the kernel will
- automatically use /dev/ttyS0 as system console if this option is
- enabled.
+ If you say Y here, it is possible to use a serial port as the
+ console. By default still the currently visible virtual console will
+ be used as the system console but you can alter that using a kernel
+ command line option. If you don't have a VGA card installed and you
+ say Y here, the kernel will automatically use /dev/ttyS0 as system
+ console.
Comtrol Rocketport support
CONFIG_ROCKETPORT
@@ -5070,27 +5818,29 @@
connect more than two modems to your linux box, for instance in
order to become a BBS. If you have a card like that, say Y here and
read the file Documentation/specialix.txt. Also it's possible to say
- M here and compile this driver as kernel loadable module.
+ 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 card can only support either RTS or DTR. When this
- option is off, the driver will use the pin as "DTR" when the tty is
- in software handshake mode. When this option is on or hardware
- handshake is on, it will always be RTS. Read the file
- Documentation/specialix.txt for more information.
+ The Specialix card can only support either RTS or DTR. When you say
+ N here, the driver will use the pin as "DTR" when the tty is in
+ software handshake mode. When you say Y here or hardware handshake
+ is on, it will always be RTS. Read the file
+ Documentation/specialix.txt for more information.
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 BBS. 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
- cyclades.o. If you haven't heard about it, it's safe to say N. (As
- of 1.3.9x kernels, this driver's minor numbers start at 0 instead of
- 32.)
+ your linux box, for instance in order to become a BBS. For
+ information about the Cyclades-Z card, read
+ drivers/char/README.cycladesZ. 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 cyclades.o. If
+ you haven't heard about it, it's safe to say N. (As of 1.3.9x
+ kernels, this driver's minor numbers start at 0 instead of 32.)
Stallion multiport serial support
CONFIG_STALDRV
@@ -5100,7 +5850,7 @@
asked for your specific card model in the next questions. Make sure
to read drivers/char/README.stallion 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
@@ -5260,12 +6010,13 @@
PC110 digitizer pad support
CONFIG_PC110_PAD
This drives the digitizer pad on the IBM PC110 palmtop (see
- http://toy.cabi.net). 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 Documentation/modules.txt. The module will be called
- pc110pad.o.
+ http://toy.cabi.net; to browse the WWW, you need to have access to a
+ machine on the Internet that has a program like lynx or
+ netscape). 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
+ Documentation/modules.txt. The module will be called pc110pad.o.
Microsoft busmouse support
CONFIG_MS_BUSMOUSE
@@ -5321,97 +6072,90 @@
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
+ 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 have a special controller (such as the CMS FC-10, FC-20,
+ 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 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
- `./drivers/char/ftape/README.PCI'.
- The ftape kernel driver is also available as a runtime loadable
+ 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 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 `./Documentation/modules.txt'.
- Note that the `Ftape-HOWTO' is out of date (sorry), but there is a
- web page with more recent documentation at
- `http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/'. This page
+ module, say M here and read 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-math.math.rwth-aachen.de/~LBFM/claus/ftape/ . This page
always contains the latest release of the ftape driver and useful
information (backup software, ftape related patches and
- documentation, FAQ). The Ftape-HOWTO still contains useful
- information, though, but documents the older 2.08 version of ftape,
- whereas this version of ftape is 3.04.
- Note that the file system interface has changed quite a lot
- compared to previous versions of ftape. Please read
- `./Documentation/ftape.txt'
+ documentation, FAQ). (To browse the WWW, you need to have access to
+ a machine on the Internet that has a program like lynx or netscape.)
+ Note that the file system interface has changed quite a bit compared
+ to previous versions of ftape. Please read Documentation/ftape.txt.
The file system interface for ftape
CONFIG_ZFTAPE
- Normally, you want to say `Y' or `M'. DON'T say `N' here or you
+ 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
+ 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 as a runtime loadable
+ 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
- `./Documentation/modules.txt'.
- There will also be another module called `zft-compressor.o' which
- contains code to support user transparent on-the-fly compression
- based on Ross William's lzrw3 algorithm. `zft-compressor.o' will be
- compiled as a runtime loadable module only. If you have enabled
+ 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
auto-loading of kernel modules via `kerneld' (i.e. have said `Y' to
CONFIG_KERNELD) then `zft-compressor.o' will be loaded automatically
by zftape when needed.
- Despite of its name zftape does NOT use compression by
- default. The 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-math.math.rwth-aachen.de/~LBFM/claus/ftape/'
- contains further information. IMPORTANT NOTE: zftape can read
- archives created by previous versions of ftape and provide file mark
- support (i.e. fast skipping between tape archives) but previous
- version of ftape will lack file mark support when reading archives
- produced by zftape.
-
-Builtin on-the-fly compression for zftape, based on lzrw3
-CONFIG_ZFT_COMPRESSOR
- This module implements builtin on-the-fly compression for ftape's
- file system interface zftape. `zft-compressor.o' is compiled as a
- runtime loadable module only and will be loaded by zftape on demand
- if support for auto-loading of modules via `kerneld' has been
- enabled (CONFIG_KERNELD).
+ Despite of its name zftape does NOT use compression by default. The
+ 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-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
+ further information (to browse the WWW, you need to have access to a
+ machine on the Internet that has a program like lynx or netscape).
+ IMPORTANT NOTE: zftape can read archives created by previous
+ versions of ftape and provide file mark support (i.e. fast skipping
+ between tape archives) but previous version of ftape will lack file
+ mark support when reading archives produced by zftape.
Default block size for zftape
CONFIG_ZFT_DFLT_BLK_SZ
- If unsure leave this at its default value, i.e. 10240. Note that
+ If unsure leave this at its default value, i.e. 10240. Note that
you specify only the default block size here. The block size can be
changed at run time using the MTSETBLK tape operation with the
MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
shell command line).
- The probably most striking difference between zftape and previous
+ The probably most striking difference between zftape and previous
versions of ftape is the fact that all data must be written or read
in multiples of a fixed block size. The block size defaults to
10240 which is what GNU tar uses. The values for the block size
should be either 1 or multiples of 1024 up to a maximum value of
63488 (i.e. 62k). If you specify `1' then zftape's builtin
compression will be disabled.
- Reasonable values are `10240' (GNU tar's default block size),
+ Reasonable values are `10240' (GNU tar's default block size),
`5120' (afio's default block size), `32768' (default block size some
backup programs assume for SCSI tape drives) or `1' (no restriction
on block size, but disables builtin compression).
Number of DMA buffers
CONFIG_FT_NR_BUFFERS
- Please leave this at `3"' unless you REALLY know what you are
+ Please leave this at `3' unless you REALLY know what you are
doing. It is not necessary to change this value. Values below 3 make
the proper use of ftape impossible, values greater than 3 are waste
of memory. You can change the amount of DMA memory used by ftape at
@@ -5421,7 +6165,7 @@
Procfs entry for ftape
CONFIG_FT_PROC_FS
- Optional. Saying `Y' will result in creation of a file
+ Optional. Saying `Y' will result in creation of a file
`/proc/ftape' under the proc file system. This files can be viewed
with your favorite pager (i.e. use "more /proc/ftape/history" or
"less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
@@ -5431,21 +6175,21 @@
kernel driver. Saying `Y' will enlarge the size of the ftape driver
by approximately 2k.
WARNING: When compiling ftape as a module (i.e. saying `M' to
- `CONFIG_FTAPE') it is dangerous to use ftape's proc file system
+ "Floppy tape drive") it is dangerous to use ftape's proc file system
interface. Accessing `/proc/ftape' while the module is unloaded will
result in a kernel Oops. This cannot be fixed from inside ftape.
Controlling the amount of debugging output of ftape
CONFIG_FT_NORMAL_DEBUG
- This option controls the amount of debugging output the ftape driver
+ This option controls the amount of debugging output the ftape driver
is ABLE to produce; it does not increase or diminish the debugging
level itself. If unsure, leave this at its default setting,
i.e. choose "Normal".
- Ftape can print lots of debugging messages to the system console
+ Ftape can print lots of debugging messages to the system console
resp. kernel log files. Reducing the amount of possible debugging
output reduces the size of the kernel module by some kb, so it might
be a good idea to use "None" for emergency boot floppies.
- If you want to save memory then the following strategy is
+ If you want to save memory then the following strategy is
recommended: leave this option at its default setting "Normal" until
you know that the driver works as expected, afterwards reconfigure
the kernel, this time specifying "Reduced" or "None" and recompile
@@ -5453,12 +6197,12 @@
debugging output does not increase the amount of debugging output
printed to the console but only makes it possible to produce
"Excessive" debugging output.
- Please read `./Documentation/ftape.txt' for a short description
+ Please read Documentation/ftape.txt for a short description
how to control the amount of debugging output.
The floppy drive controller for ftape
CONFIG_FT_STD_FDC
- Only change this setting if you have a special controller. If you
+ Only change this setting if you have a special controller. If you
didn't plug any add-on card into your computer system but just
plugged the floppy tape cable into the already existing floppy drive
controller then you don't want to change the default setting,
@@ -5473,115 +6217,115 @@
`2'. This is necessary for any controller card that is based on
Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
speed" controllers.
- If you choose something other than "Standard" then please make
+ If you choose something other than "Standard" then please make
sure that the settings for the IO base address and the IRQ and DMA
channel in the configuration menus below are correct. Use the manual
of your tape drive to determine the correct settings!
- If you are already successfully using your tape drive with another
+ If you are already successfully using your tape drive with another
operating system then you definitely should use the same settings
for the IO base, the IRQ and DMA channel that have proven to work
with that other OS.
- Note that this menu lets you specify only the default setting for
+ Note that this menu lets you specify only the default setting for
the hardware setup. The hardware configuration can be changed at
boot time (when ftape is compiled into the kernel, i.e. if you
- have said `Y' to `CONFIG_FTAPE') or module load time (i.e. if you
- have said `M' to `CONFIG_FTAPE').
- Please read also the file `./Documentation/ftape.txt' which
+ have said Y to "Floppy tape drive") or module load time (i.e. if you
+ have said M to "Floppy tape drive").
+ Please read also the file Documentation/ftape.txt which
contains a short description of the parameters that can be set at
boot or load time. If you want to use your floppy tape drive on a
PCI-bus based system, please read the file
- `./drivers/char/ftape/README.PCI'.
+ drivers/char/ftape/README.PCI.
IO base of the floppy disk controller used with Ftape
CONFIG_FT_FDC_BASE
- You don't need to specify a value if the following default
+ You don't need to specify a value if the following default
settings for the base IO address are correct:
<<< MACH-2 : 0x1E0 >>>
<<< FC-10/FC-20: 0x180 >>>
<<< Secondary : 0x370 >>>
Secondary refers to a secondary FDC controller like the "high speed"
controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
- Please make sure that the setting for the IO base address
+ Please make sure that the setting for the IO base address
specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
successfully using the tape drive with another operating system then
you definitely should use the same settings for the IO base that has
proven to work with that other OS.
- Note that this menu lets you specify only the default setting for
+ Note that this menu lets you specify only the default setting for
the IO base. The hardware configuration can be changed at boot time
- (when ftape is compiled into the kernel, i.e. if you specify `Y' to
- `CONFIG_FTAPE') or module load time (i.e. if you have say `M' to
- `CONFIG_FTAPE').
- Please read also the file `./Documentation/ftape.txt' which
- contains a short description of the parameters that can be set at
- boot or load time.
-
+ (when ftape is compiled into the kernel, i.e. if you specified Y to
+ "Floppy tape drive") or module load time (i.e. if you have said M to
+ "Floppy tape drive").
+ Please read also the file Documentation/ftape.txt which contains a
+ short description of the parameters that can be set at boot or load
+ time.
+
IRQ channel for the floppy disk controller used with Ftape
CONFIG_FT_FDC_IRQ
- You don't need to specify a value if the following default
+ You don't need to specify a value if the following default
settings for the interrupt channel are correct:
<<< MACH-2 : 6 >>>
<<< FC-10/FC-20: 9 >>>
<<< Secondary : 6 >>>
Secondary refers to secondary a FDC controller like the "high speed"
controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
- Please make sure that the setting for the IO base address
+ Please make sure that the setting for the IO base address
specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
successfully using the tape drive with another operating system then
you definitely should use the same settings for the IO base that has
proven to work with that other OS.
- Note that this menu lets you specify only the default setting for
+ Note that this menu lets you specify only the default setting for
the IRQ channel. The hardware configuration can be changed at boot
- time (when ftape is compiled into the kernel, i.e. if you specify
- `Y' to `CONFIG_FTAPE') or module load time (i.e. if you have say `M'
- to `CONFIG_FTAPE').
- Please read also the file `./Documentation/ftape.txt' which
- contains a short description of the parameters that can be set at
- boot or load time.
-
+ time (when ftape is compiled into the kernel, i.e. if you specified
+ Y to "Floppy tape drive") or module load time (i.e. if you have said M
+ to "Floppy tape drive").
+ Please read also the file Documentation/ftape.txt which contains a
+ short description of the parameters that can be set at boot or load
+ time.
+
DMA channel for the floppy disk controller used with Ftape
CONFIG_FT_FDC_DMA
- You don't need to specify a value if the following default
+ You don't need to specify a value if the following default
settings for the DMA channel are correct:
<<< MACH-2 : 2 >>>
<<< FC-10/FC-20: 3 >>>
<<< Secondary : 2 >>>
Secondary refers to a secondary FDC controller like the "high speed"
controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
- Please make sure that the setting for the IO base address
+ Please make sure that the setting for the IO base address
specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
successfully using the tape drive with another operating system then
you definitely should use the same settings for the IO base that has
proven to work with that other OS.
- Note that this menu lets you specify only the default setting for
+ Note that this menu lets you specify only the default setting for
the DMA channel. The hardware configuration can be changed at boot
- time (when ftape is compiled into the kernel, i.e. if you specify
- `Y' to `CONFIG_FTAPE') or module load time (i.e. if you have say `M'
- to `CONFIG_FTAPE').
- Please read also the file `./Documentation/ftape.txt' which
- contains a short description of the parameters that can be set at
- boot or load time.
+ time (when ftape is compiled into the kernel, i.e. if you specified
+ Y to "Floppy tape drive") or module load time (i.e. if you have said M
+ to "Floppy tape drive").
+ Please read also the file Documentation/ftape.txt which contains a
+ short description of the parameters that can be set at boot or load
+ time.
FDC FIFO Threshold before requesting DMA service
CONFIG_FT_FDC_THR
- Set the FIFO threshold of the FDC. If this is higher the DMA
+ Set the FIFO threshold of the FDC. If this is higher the DMA
controller may serve the FCD after a higher latency time. If this is
lower, less DMA transfers occur leading to less bus contention.
- You may try to tune this if ftape annoys you with "reduced data
+ You may try to tune this if ftape annoys you with "reduced data
rate because of excessive overrun errors" messages. However, this
doesn't seem to have too much an effect.
If unsure, don't touch the initial value, i.e. leave it at "8".
FDC maximum data rate
CONFIG_FT_FDC_MAX_RATE
- With some mother board/FDC combinations ftape will not be able to
+ With some mother board/FDC combinations ftape will not be able to
run your FDC/tape drive combination at the highest available
speed. If this is the case you'll encounter "reduced data rate
because of excessive overrun errors" messages and lots of retries
before ftape finally decides to reduce the data rate.
- In this case it might be desirable to tell ftape beforehand that
+ In this case it might be desirable to tell ftape beforehand that
it need not try to run the tape drive at the highest available
speed. If unsure, leave this disabled, i.e. leave it at 2000
bits/sec.
@@ -5605,20 +6349,22 @@
USER RESUME operation, the /proc/apm device will provide battery
status information, and user-space programs will receive
notification of APM "events" (e.g., battery status
- change). Supporting software can be gotten via ftp (user: anonymous)
- from tsx-11.mit.edu/pub/linux/packages/laptops/apm/. This driver
- does not spin down disk drives (see hdparm(8) for that); and it
- doesn't turn off VESA-compliant "green" monitors. This driver does
- not support the TI 4000M TravelMate and the ACER 486/DX4/75 because
- they don't have compliant BIOSes. Many "green" desktop machines
- also don't have compliant BIOSes, and this driver will cause those
- machines to panic during the boot phase (typically, these machines
- are using a data segment of 0040, which is reserved for the Linux
- kernel). Generally, if you don't have a battery in your machine,
- there isn't much point in using this driver and you should say N.
- If you get random kernel OOPSes or reboots that don't seem to be
- related to anything, try disabling/enabling this option. Some other
- things to try when experiencing seemingly random, "weird" problems:
+ change). Supporting software is available; for more information,
+ read the Battery Powered Linux mini-HOWTO available via ftp (user:
+ anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.
+ This driver does not spin down disk drives (see hdparm(8) for that);
+ and it doesn't turn off VESA-compliant "green" monitors. This
+ driver does not support the TI 4000M TravelMate and the ACER
+ 486/DX4/75 because they don't have compliant BIOSes. Many "green"
+ desktop machines also don't have compliant BIOSes, and this driver
+ will cause those machines to panic during the boot phase (typically,
+ these machines are using a data segment of 0040, which is reserved
+ for the Linux kernel). Generally, if you don't have a battery in
+ your machine, there isn't much point in using this driver and you
+ should say N. If you get random kernel OOPSes or reboots that don't
+ seem to be related to anything, try disabling/enabling this
+ option. Some other things to try when experiencing seemingly random,
+ "weird" problems:
1) passing the "no-hlt" option to the kernel
2) passing the "no-387" option to the kernel
3) passing the "floppy=nodma" option to the kernel
@@ -5674,8 +6420,13 @@
Power off on shutdown
CONFIG_APM_POWER_OFF
- This option will power off the computer after the Linux kernel is halted
- (e.g., with the halt(8) command). As with the other APM options, this
+ Enable the ability to power off the computer after the Linux kernel
+ is halted. You will need software (e.g., a suitable version of the
+ halt(8) command) to cause the computer to power down. Recent
+ versions of the sysvinit package available from
+ ftp://sunsite.unc.edu/pub/Linux/system/daemons/init/ (user:
+ anonymous) contain support for this ("halt -p" shuts down Linux and
+ powers off the computer). As with the other APM options, this
option may not work reliably with some APM BIOS implementations.
Watchdog Timer Support
@@ -5766,7 +6517,7 @@
inserted in and removed from the running kernel whenever you want).
The module is called pscwdt.o. If you want to compile it as a module,
say M here and read Documentation/modules.txt. Most people will say N.
-
+
Enhanced Real Time Clock Support
CONFIG_RTC
If you say Y here and create a character special file /dev/rtc with
@@ -5782,6 +6533,13 @@
have a use for such a device (such as periodic data sampling), then
say Y here, and go read the file Documentation/rtc.txt for details.
+Tadpole ANA H8 Support
+CONFIG_H8
+ The Hitachi H8/337 is a microcontroller used to deal with the power
+ and thermal environment. If you say Y here, you will be able to
+ communicate with it via via a character special device. If unsure,
+ say N.
+
/dev/nvram support
CONFIG_NVRAM
If you say Y here and create a character special file /dev/nvram
@@ -5802,18 +6560,17 @@
PC joystick support
CONFIG_JOYSTICK
- If you have a PC compatible analog or digital joystick, you can
- say Y here. If you then create a character special file under /dev
- with major number 15 and minor number 0 or 1 (for the two joystick
- ports) using mknod ("man mknod"), you can read the status of the
- buttons and the x and y coordinates from that file. More
- information, an example program and a calibration program are
- contained in the joystick package which is available at:
- ftp://sunsite.unc.edu/pub/Linux/kernel/patches/console
- 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 joystick.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ If you have a PC compatible analog or digital joystick, you can say
+ Y here. If you then create a character special file under /dev with
+ major number 15 and minor number 0 or 1 (for the two joystick ports)
+ using mknod ("man mknod"), you can read the status of the buttons
+ and the x and y coordinates from that file. Please read the file
+ Documentation/joystick.txt which contains more information and the
+ location of the joystick package that you'll need. 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 joystick.o. If you want to compile it as a module, say M
+ here and read Documentation/modules.txt.
ARC console time
CONFIG_RTC_ARC
@@ -5864,6 +6621,9 @@
these cards may cause trouble (I don't currently know of any such
cards, however).
+Loopback MIDI device support
+CONFIG_VMIDI
+
Gravis Ultrasound support
CONFIG_GUS
Say Y here for any type of Gravis Ultrasound card, including
@@ -5937,14 +6697,15 @@
Answer Y if you have the AudioTriX Pro sound card manufactured
by MediaTrix.
-Support for MAD16 and/or Mozart based cards
+Support for OPTi MAD16 and/or Mozart based cards
CONFIG_MAD16
- Answer Y if your card has a Mozart (OAK OTI-601) or MAD16
- (OPTi 82C928 or 82C929) audio interface chip. These chips are
- currently quite common so it's possible that many no-name cards
- have one of them. In addition the MAD16 chip is used in some
- cards made by known manufacturers such as Turtle Beach (Tropez),
- Reveal (some models) and Diamond (latest ones).
+ Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
+ 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
+ please read drivers/sound/README.C931. These chips are currently
+ quite common so it's possible that many no-name cards have one of
+ them. In addition the MAD16 chip is used in some cards made by known
+ manufacturers such as Turtle Beach (Tropez), Reveal (some models)
+ and Diamond (latest ones).
Support for Crystal CS4232 based (PnP) cards
CONFIG_CS4232
@@ -5980,7 +6741,7 @@
SB32/AWE support
CONFIG_AWE32_SYNTH
Say Y here if you have a SB32 or SB AWE soundcard. See
- linux/drivers/sound/lowlevel/README.awe for more info.
+ drivers/sound/lowlevel/README.awe for more info.
Additional low level drivers
CONFIG_LOWLEVEL_SOUND
@@ -6002,23 +6763,23 @@
Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
CONFIG_AEDSP16
Answer Y if you have a Gallant's Audio Excel DSP 16 card. This card
- can emulate an SBPro or a Microsoft Sound System card, so you should
- have said Y to either "SoundBlaster (SB, SBPro, SB16, clones)
+ can emulate either an SBPro or a Microsoft Sound System card, so you
+ should have said Y to either "SoundBlaster (SB, SBPro, SB16, clones)
support" or "Microsoft Sound System support", above, and you need to
answer the "MSS emulation" and "SBPro emulation" questions below
- accordingly. You should say Y to one and only one of these
+ accordingly. You should say Y to one and only one of these two
questions. Read the drivers/sound/lowlevel/README.aedsp16 file and
- the head of drivers/sound/lowlevel/aedsp16.c to get more
- information about this driver and its configuration. This driver
- supports Audio Excel DSP 16 but not the III nor Pnp versions of this
- card. Read drivers/sound/lowlevel/README.aedsp16 if you want to know
- something more on how to use the III version with this sound driver.
+ the head of drivers/sound/lowlevel/aedsp16.c to get more information
+ about this driver and its configuration. This driver supports Audio
+ Excel DSP 16 but not the III nor Pnp versions of this card. Read
+ drivers/sound/lowlevel/README.aedsp16 if you want to know something
+ more on how to use the III version with this sound driver.
SC-6600 based audio cards (new Audio Excel DSP 16)
CONFIG_SC6600
- The SC6600 is the new version of DSP mounted on the Audio Excel DSP 16
- cards. Find in the manual the FCC ID of your audio card and answer Y if
- you have an SC6600 DSP.
+ The SC6600 is the new version of DSP mounted on the Audio Excel DSP
+ 16 cards. Find in the manual the FCC ID of your audio card and
+ answer Y if you have an SC6600 DSP.
Audio Excel DSP 16 (MSS emulation)
CONFIG_AEDSP16_MSS
@@ -6040,9 +6801,10 @@
read it, you need the readprofile package from sunsite.unc.edu. Its
manpage gives information regarding the format of profiling data. To
become a kernel hacker, you can start with the Kernel Hacker's Guide
- at http://www.redhat.com:8080/HyperNews/get/khg.html. Mere mortals
- say N.
-
+ at http://www.redhat.com:8080/HyperNews/get/khg.html (to browse the
+ WWW, you need to have access to a machine on the Internet that has a
+ program like lynx or netscape). Mere mortals say N.
+
Profile shift count
CONFIG_PROFILE_SHIFT
This is used to adjust the granularity with which the addresses of
@@ -6079,12 +6841,13 @@
emulator. Network devices support autodial, channel-bundling,
callback and caller-authentication without having a daemon
running. A reduced T.70 protocol is supported with tty's suitable
- for German BTX. On D-Channel, the protocols EDSS1 and 1TR6 are
- supported. See Documentation/isdn/README for more information. If
- you want to compile the ISDN 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 isdn.o. If unsure, say N.
+ for German BTX. On D-Channel, the protocols EDSS1 (Euro-ISDN) and
+ 1TR6 (German style) are supported. See Documentation/isdn/README for
+ more information. If you want to compile the ISDN code 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 isdn.o. If
+ unsure, say N.
Support synchronous PPP
CONFIG_ISDN_PPP
@@ -6199,7 +6962,7 @@
CONFIG_HISAX_NI1
You should choose the D-channel protocol your local
telephone service provider uses here by saying Y or N.
-
+
HiSax Support for German 1TR6
CONFIG_HISAX_1TR6
You should choose the D-channel protocol your local
@@ -6226,21 +6989,25 @@
can be inserted in and removed from the running kernel whenever you
want, details in Documentation/modules.txt); the module will be
called sc.o. See Documentation/isdn/README.sc and
- http://www.spellcast.com for more information.
+ http://www.spellcast.com for more information (to browse the WWW,
+ you need to have access to a machine on the Internet that has a
+ program like lynx or netscape).
AVM-B1 with CAPI2.0 support
CONFIG_ISDN_DRV_AVMB1
This enables support for the AVM B1 ISDN networking cards. In
addition, a CAPI (Common ISDN Application Programming Interface, a
standard making it easy for programs to access ISDN hardware, see
- http://www.capi.org/) interface for this card is provided. In order
- to use this card, additional firmware is necessary, which has to be
- downloaded into the card using a utility which is distributed
- separately. Please read the file Documentation/isdn/README.avmb1.
- 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 avmb1.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ http://www.capi.org/; to browse the WWW, you need to have access to
+ a machine on the Internet that has a program like lynx or netscape)
+ interface for this card is provided. In order to use this card,
+ additional firmware is necessary, which has to be downloaded into
+ the card using a utility which is distributed separately. Please
+ read the file Documentation/isdn/README.avmb1. 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 avmb1.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt.
Verbose reason code reporting (kernel size +=7K)
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
@@ -6252,8 +7019,9 @@
CONFIG_AP1000
This enables support for a sparc based parallel multi-computer
called AP1000+. For details on our efforts to port Linux to this
- machine see http://cap.anu.edu.au/cap/projects/linux or mail to
- hackers@cafe.anu.edu.au
+ machine see http://cap.anu.edu.au/cap/projects/linux (to browse the
+ WWW, you need to have access to a machine on the Internet that has a
+ program like lynx or netscape) or mail to hackers@cafe.anu.edu.au
Sparc ESP SCSI support
CONFIG_SCSI_SUNESP
@@ -6269,6 +7037,14 @@
removed from the running kernel whenever you want), say M and read
Documentation/modules.txt. If unsure, say Y.
+Mostek real time clock support
+CONFIG_SUN_MOSTEK_RTC
+
+Siemens SAB82532 serial support
+CONFIG_SAB82532
+###
+### Please someone fill these in.
+###
# m68k-specific kernel options
# Documented by Chris Lawrence <quango@themall.net> et al.
@@ -6507,8 +7283,8 @@
Fastlane SCSI support
CONFIG_FASTLANE_SCSI
- If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one
- in the near future, say Y to this question. Otherwise, say N.
+ If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
+ one in the near future, say Y to this question. Otherwise, say N.
Atari native SCSI support
CONFIG_ATARI_SCSI
@@ -6629,32 +7405,13 @@
whenever you want). If you want to compile it as a module, say M
here and read Documentation/modules.txt.
-Radio support
-CONFIG_MISC_RADIO
- If you have a radio card (you will probably know if you do!), then
- you will want to say "y" here and make a character device file
- (usually /dev/radio) with major number 10 and minor 152 using mknod
- ("man mknod"). And then, don't forget to pick up some useful tools
- to use said device (you _might_ find something at ftp.lmh.ox.ac.uk:
- /users/weejock/linux/radio/, but I haven't written anything too
- useful yet...)
-
-AIMSlab RadioTrack card
-CONFIG_RADIO_RTRACK
- Choose "y" here if you have one of these, and then fill in the port
- address below.
-
-RadioTrack i/o port
-CONFIG_RADIO_RTRACK_PORT
- Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
- haven't changed the jumper setting on the card.
-
Atari SCC serial DMA support
CONFIG_ATARI_SCC_DMA
- This enables DMA support for receiving data on channel A of the SCC. If
- you have a TT you may say Y here and read drivers/char/atari_SCC.README.
- All other users should say N here, because only the TT has SCC-DMA, even
- if your machine keeps claiming so at boot time.
+ This enables DMA support for receiving data on channel A of the
+ SCC. If you have a TT you may say Y here and read
+ drivers/char/atari_SCC.README. All other users should say N here,
+ because only the TT has SCC-DMA, even if your machine keeps claiming
+ so at boot time.
Atari MIDI serial support
CONFIG_ATARI_MIDI
@@ -6760,7 +7517,10 @@
Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
other Power Macintoshes do). Say Y to include support for this SCSI
- adaptor.
+ adaptor. This driver is also available as a module called mesh.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 Documentation/modules.txt.
Maximum synchronous transfer rate
CONFIG_SCSI_MESH_SYNC_RATE
@@ -6778,7 +7538,11 @@
On Power Macintoshes (and clones) with two SCSI buses, the external
SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
machines which only have one SCSI bus, such as the 7200, also use
- the 53C94. Say Y to include support for the 53C94.
+ the 53C94. Say Y to include support for the 53C94. This driver is
+ also available as a module called mac53c94.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
+ Documentation/modules.txt.
MACE (Power Mac ethernet) support
CONFIG_MACE
@@ -6788,14 +7552,37 @@
Video For Linux
CONFIG_VIDEO_DEV
- Support for audio/video capture and overlay devices. The exact capabilities
- of each device vary. User tools for this are available from
- ftp://ftp.uk.linux.org/pub/linux/video4linux
+ Support for audio/video capture and overlay devices. The exact
+ capabilities of each device vary. User tools for this are available
+ from ftp://ftp.uk.linux.org/pub/linux/video4linux. This driver is
+ also available as a module called videodev.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
+ Documentation/modules.txt.
BT848 Video For Linux
CONFIG_VIDEO_BT848
- Support for BT848 based frame grabber/overlay boards. This includes the
- Miro, Hauppauge and STB boards.
+ Support for BT848 based frame grabber/overlay boards. This includes
+ the Miro, Hauppauge and STB boards. This driver is
+ also available as a module called bttv.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
+ Documentation/modules.txt.
+
+Quickcam BW Video For Linux
+CONFIG_VIDEO_BWQCAM
+ Say Y have if you have such a thing. This driver is also available
+ as a module called bw-qcam.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
+ Documentation/modules.txt.
+
+Mediavision Pro Movie Studio Video For Linux
+CONFIG_VIDEO_PMS
+ Say Y if you have such a thing. This driver is also available as a
+ module called pms.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 Documentation/modules.txt.
# need an empty line after last entry, for sed script in Configure.
@@ -6924,18 +7711,36 @@
# LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
# LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
# LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
-# LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni
-# LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS
+# LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni NBD nbd
+# LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
# LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
# LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
# LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt SCB's RX
# LocalWords: dataless kerneltype SYSNAME Netbeui Comtrol Rocketport palmtop
# LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
# LocalWords: HFMODEM shortwave Sitor Amtor Pactor GTOR hfmodem hayes TX TMOUT
-# LocalWords: QIC TR CONFIG FTAPE Iomega CMS FC FDC Exabyte Iomega's DFLT
-# LocalWords: tapedrive THR FCD IRQ DMA SZ PCI ftape README txt HOWTO
-# LocalWords: http www rwth aachen LBFM claus FAQ mt ZFTAPE VFS
-# LocalWords: zftape zft William's lzrw kerneld BLK zftape's tar's
-# LocalWords: afio's MTSETBLK MTIOCTOP dev qft setblk BLKSZ NR
-# LocalWords: setdrvbuffer kb NUMBUFFERS Procfs PROC FS proc resp STD
-# LocalWords: Alt LocalWords
+# LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
+# LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
+# LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
+# LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
+# LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
+# LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
+# LocalWords: ipddp Decapsulation DECAP bool HAMRADIO WAN's tcpdump af CD's tx
+# LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio LAN's
+# LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
+# LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
+# LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
+# LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
+# LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu
+# LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
+# LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
+# LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
+# LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
+# LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's
+# LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
+# LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
+# LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
+# LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
+# LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
+# LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
+# LocalWords: pms
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen, slshen@lbl.gov