diff -u --recursive --new-file v2.1.99/linux/Documentation/Configure.help linux/Documentation/Configure.help
--- v2.1.99/linux/Documentation/Configure.help	Sat May  2 14:19:50 1998
+++ linux/Documentation/Configure.help	Sun May  3 17:52:07 1998
@@ -4,7 +4,7 @@
 # corresponds to the kernel versions 2.1.x. Be aware that these are
 # development kernels and need not be completely stable.
 #
-# International versions of this file available on the WWW:
+# Translations of this file available on the WWW:
 #   - http://jf.gee.kyoto-u.ac.jp/JF/JF-ftp/euc/Configure.help.euc
 # is a Japanese translation, maintained by Tetsuyasu YAMADA
 # (tetsu@cauchy.nslab.ntt.jp). 
@@ -33,16 +33,14 @@
 #
 # Format of this file: description<nl>variable<nl>helptext<nl><nl>. If
 # the question being documented is of type "choice", we list only the
-# first occurring config variable. The help texts must not contain
-# empty lines. Order of the help texts does not matter, however, no
-# variable should be documented twice: if it is, only the first
-# occurrence will be used by Configure. It is not absolutely necessary
-# that the one-line descriptions of the variables used here are
-# exactly the same as the ones in the corresponding Config.in scripts.
-# The lines in a help text should be indented two positions. Lines
-# starting with `#' are ignored. To be nice to menuconfig, limit your
-# lines to 70 characters. Use emacs' kfill.el to edit and ispell.el to
-# spell check this file or you lose.
+# first occurring config variable. The help texts may contain empty
+# lines, but every non-empty line must be indented two positions.
+# Order of the help texts does not matter, however, no variable should
+# be documented twice: if it is, only the first occurrence will be
+# used by Configure. We try to keep the help texts of related variables
+# close together. Lines starting with `#' are ignored. To be nice to
+# menuconfig, limit your line length to 70 characters. Use emacs'
+# kfill.el to edit and ispell.el to spell check this file or you lose.
 #
 # If you add a help text to this file, please try to be as gentle as
 # possible. Don't use unexplained acronyms and generally write for the
@@ -51,12 +49,14 @@
 # for the first time. Tell them what to do if they're unsure. Technical 
 # information should go in a README in the Documentation directory.
 # Mention all the relevant READMEs and HOWTOs in the help text.
+# Repetitions are fine since the help texts are not meant to be read
+# in sequence.
 #
 # All this was shamelessly stolen from several different sources. Many
 # thanks to all the contributors. Feel free to use these help texts in
 # your own kernel configuration tools. The texts are copyrighted (c)
 # 1995-1998 by Axel Boldt and many others and are governed by the GNU
-# Public License.
+# General Public License.
 
 Prompt for development and/or incomplete code/drivers
 CONFIG_EXPERIMENTAL
@@ -75,6 +75,7 @@
   (before submitting bug reports, please read the documents README,
   MAINTAINERS, Documentation/BUG-HUNTING, and
   Documentation/oops-tracing.txt in the kernel source).  
+
   Unless you intend to help test and develop a feature or driver that
   falls into this category, or you have a situation that requires
   using these features you should probably say N here, which will
@@ -88,32 +89,25 @@
   operations) if you don't have one. 486DX and Pentium processors have
   a math coprocessor built in, 486SX and 386 do not, unless you added
   a 487DX or 387, respectively.  (The messages during boot time can
-  give you some hints here ["man dmesg"]) Everyone needs either a
-  coprocessor or this emulation. If you say Y here even
-  though you have a coprocessor, the coprocessor will be used
-  nevertheless. (This behavior can be changed with the kernel command
-  line option "no387", which comes handy if your coprocessor is
-  broken. Try "man bootparam" or see the documentation of your boot
+  give you some hints here ["man dmesg"].) Everyone needs either a
+  coprocessor or this emulation. 
+
+  If you don't have a math coprocessor, you need to say Y here; if you
+  say Y here even though you have a coprocessor, the coprocessor will
+  be used nevertheless. (This behavior can be changed with the kernel
+  command line option "no387", which comes handy if your coprocessor
+  is broken. Try "man bootparam" or see the documentation of your boot
   loader (lilo or loadlin) about how to pass options to the kernel at
   boot time. The lilo procedure is also explained in the SCSI-HOWTO,
   available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.) This means that it is a good
-  idea to say Y here if you intend to use this kernel on different
-  machines. More information about the internals of Linux math
-  coprocessor emulation can be found in arch/i386/math-emu/README. If
-  you are not sure, say Y; apart from resulting in a 45kB bigger
-  kernel, it won't hurt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) This means that it is a
+  good idea to say Y here if you intend to use this kernel on
+  different machines. More information about the internals of Linux
+  math coprocessor emulation can be found in
+  arch/i386/math-emu/README.
 
-Max physical memory
-CONFIG_MAX_MEMSIZE
-  Linux/x86 can use up to 3.8 gigabytes of physical memory. Default
-  is max 1 gigabyte physical memory (1024 MB), this is enough for
-  most systems.
-  A system with 2G physical memory should use a value of ~2400, a
-  system with 3.8G memory should use something like 3900. A bit of
-  experimentation with the limit wont hurt, the kernel needs a ~128M
-  window for vmalloc() plus PCI space uses up some memory too, thus
-  addresses above FD000000 should rather be kept free.
+  If you are not sure, say Y; apart from resulting in a 45kB bigger
+  kernel, it won't hurt.
 
 Normal floppy disk support
 CONFIG_BLK_DEV_FD
@@ -122,11 +116,12 @@
   Thinkpad users, is contained in drivers/block/README.fd. This file
   also contains the location of the Floppy driver FAQ as well as
   location of the fdutils package used to configure additional
-  parameters of the driver at run time. 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
-  floppy.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  parameters of the driver at run time. 
+
+  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 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
@@ -137,11 +132,15 @@
   store a copy of a minimal root file system off of a floppy into RAM
   during the initial install of Linux.  Note that the kernel command
   line option "ramdisk=XX" is now obsolete.  For details, read
-  Documentation/ramdisk.txt. If you want to compile this as a module (
-  = code which can be inserted in and removed from the running kernel
-  whenever you want), say M and read Documentation/modules.txt. The
-  module will be called rd.o. Most normal users won't need the RAM
-  disk functionality, and can thus say N here.
+  Documentation/ramdisk.txt. 
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M and read Documentation/modules.txt. The module will be called
+  rd.o. 
+
+  Most normal users won't need the RAM disk functionality, and can
+  thus say N here.
 
 Initial RAM disk (initrd) support
 CONFIG_BLK_DEV_INITRD
@@ -153,15 +152,16 @@
 
 Loop device support
 CONFIG_BLK_DEV_LOOP
-  Saying Y here will allow you to mount a file as a file system.  This
+  Saying Y here will allow you to mount a file as a file system. This
   is useful if you want to check an ISO9660 file system before burning
   the CD, or want to use floppy images without first writing them to
-  floppy.  This option also allows you to mount a filesystem with
-  encryption.  To use these features, you need a recent version of
+  floppy. This option also allows you to mount a filesystem with
+  encryption. To use these features, you need a recent version of
   mount (available via ftp (user: anonymous) from
-  ftp.win.tue.nl/pub/linux/util/).  Note that this loop device has
-  nothing to do with the loopback device used for network connections
-  from the machine to itself.  Most users will answer N here.
+  ftp://ftp.win.tue.nl/pub/linux/util/). Note that this loop device
+  has nothing to do with the loopback device used for network
+  connections from the machine to itself. Most users will answer N
+  here.
 
 Network Block Device support
 CONFIG_BLK_DEV_NBD
@@ -172,33 +172,44 @@
   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.
+  same computer, communicating using the loopback network device). 
+  Read Documentation/nbd.txt for details.
+
+  Note that this has nothing to do with the network file system NFS;
+  you can say N here even if you intend to use NFS.
+
+  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.
+
+  If unsure, say N.
 
 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
 CONFIG_BLK_DEV_IDE
-  This will use the full-featured IDE driver to control up to four IDE
-  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, sound
-  card IDE ports, module support, and other topics, is contained in
+  If you say Y here, you will use the full-featured IDE driver to
+  control up to four IDE interfaces, each being able to serve a
+  "master" and a "slave" device, for a total of up to eight IDE
+  disk/cdrom/tape/floppy drives.
+
+  Useful information about large (>540MB) IDE disks, sound card IDE
+  ports, module support, and other topics, is contained in
   Documentation/ide.txt. For detailed information about hard drives,
   consult the Disk-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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 hard disk 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
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. To fine-tune IDE
+  drive/interface parameters for improved performance, look for the
+  hdparm package at
   sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/
 
+  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 hard disk driver" instead to save
+  about 13kB of memory in the kernel.
+
 Old hard disk (MFM/RLL/IDE) driver
 CONFIG_BLK_DEV_HD_ONLY
-  There are two drivers for MFM/RLL/IDE disks. Most people use the
-  newer enhanced driver, but this old one is still around for two
+  There are two drivers for MFM/RLL/IDE hard disks. Most people use
+  the newer enhanced driver, but this old one is still around for two
   reasons. Some older systems have strange timing problems and seem to
   work only with the old driver (which itself does not work with some
   newer systems). The other reason is that the old driver is smaller,
@@ -208,68 +219,78 @@
   driver can save 13kB or so of kernel memory. If you are unsure, then
   just choose the Enhanced IDE/MFM/RLL driver instead of this one. For
   more detailed information, read the Disk-HOWTO, available via ftp
-  (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 Use old disk-only driver on primary interface
 CONFIG_BLK_DEV_HD_IDE
-  There are two drivers for MFM/RLL/IDE disks.  Most people use just
-  the new enhanced driver by itself.  This option however installs the
-  old hard disk driver to control the primary IDE/disk interface in the
-  system, leaving the new enhanced IDE driver take care of only the
-  2nd/3rd/4th IDE interfaces. Doing this will prevent you from having
-  an IDE/ATAPI CDROM or tape drive connected to the primary IDE
+  There are two drivers for MFM/RLL/IDE disks. Most people use just
+  the new enhanced driver by itself. This option however installs the
+  old hard disk driver to control the primary IDE/disk interface in
+  the system, leaving the new enhanced IDE driver to take care of only
+  the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
+  having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
   interface. Choosing this option may be useful for older systems
   which have MFM/RLL/ESDI controller+drives at the primary port
   address (0x1f0), along with IDE drives at the secondary/3rd/4th port
-  addresses.  Normally, just say N here; you will then use the new
+  addresses. Normally, just say N here; you will then use the new
   driver for all 4 interfaces.
 
 Include IDE/ATA-2 DISK support
 CONFIG_BLK_DEV_IDEDISK
   This will include enhanced support for MFM/RLL/IDE hard disks. If you
   have a MFM/RLL/IDE disk, and there is no special reason to use the
-  old hard disk driver instead, say Y.  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 ide-disk.o. Do
-  not compile this driver as a module if your root filesystem (the one
-  containing the directory /) is located on the IDE disk. If unsure,
-  say Y.
+  old hard disk driver instead, say Y.  
+
+  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 ide-disk.o. Do not compile this driver as a module if your
+  root filesystem (the one containing the directory /) is located on
+  the IDE disk. If unsure, say Y.
 
 Include IDE/ATAPI CDROM support
 CONFIG_BLK_DEV_IDECD
-  If you have a CDROM drive using the ATAPI protocol, say Y.  ATAPI is
+  If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
   a new protocol used by IDE CDROM and TAPE drives, similar to the
-  SCSI protocol.  Most new CDROM drives use ATAPI, including the
+  SCSI protocol. Most new CDROM drives use ATAPI, including the
   NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
-  double(2X), quad(4X), and six(6X) speed drives.  At boot time, the
-  CDROM drive will be identified along with other IDE devices, as
-  "hdb" or "hdc", or something similar (check the boot messages with
-  dmesg).  If this is your only CDROM drive, you can say N to all
-  other CDROM options, but be sure to say Y to "ISO9660 cdrom
-  filesystem support".  Read the CDROM-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO and the file
-  Documentation/cdrom/ide-cd.  Note that older versions of lilo (the
-  linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
+  double(2X), quad(4X), and six(6X) speed drives.
+
+  If you say Y here, the CDROM drive will be identified at boot time
+  along with other IDE devices, as "hdb" or "hdc", or something
+  similar (check the boot messages with dmesg). If this is your only
+  CDROM drive, you can say N to all other CDROM options, but be sure
+  to say Y to "ISO9660 cdrom filesystem support".
+
+  Read the CDROM-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and the file
+  Documentation/cdrom/ide-cd. Note that older versions of lilo (the
+  Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
   install lilo-16 or higher, available from
-  sunsite.unc.edu:/pub/Linux/system/Linux-boot/lilo.  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-cd.o.
+  ftp://sunsite.unc.edu/pub/Linux/system/Linux-boot/lilo.
+
+  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-cd.o.
 
 Include IDE/ATAPI TAPE support
 CONFIG_BLK_DEV_IDETAPE
   If you have an IDE tape drive using the ATAPI protocol, say Y.
   ATAPI is a new protocol used by IDE tape and CDROM drives, similar
-  to the SCSI protocol.  At boot time, the tape drive will be
-  identified along with other IDE devices, as "hdb" or "hdc", or
-  something similar, and will be mapped to a character device such as
-  "ht0" (check the boot messages with dmesg).  Be sure to consult the
+  to the SCSI protocol.  
+
+  If you say Y here, the tape drive will be identified at boot time
+  along with other IDE devices, as "hdb" or "hdc", or something
+  similar, and will be mapped to a character device such as "ht0"
+  (check the boot messages with dmesg). Be sure to consult the
   drivers/block/ide-tape.c and Documentation/ide.txt files for usage
-  information.  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-tape.o.
+  information.
+
+  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-tape.o.
 
 Include IDE/ATAPI FLOPPY support
 CONFIG_BLK_DEV_IDEFLOPPY
@@ -277,13 +298,17 @@
   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
-  (check the boot messages with dmesg). 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.
+  driver; support for PD-CD/CDR drives is available if you say Y to
+  "SCSI emulation support", below).
+
+  If you say Y here, the FLOPPY drive will be identified along with
+  other IDE devices, as "hdb" or "hdc", or something similar (check
+  the boot messages with dmesg).
+
+  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
@@ -305,10 +330,17 @@
   conditions.  Say Y here to include code which tries to automatically
   detect and correct the problems under Linux.  This option also
   enables access to the secondary IDE ports in some CMD640 based
-  systems.  This driver will work automatically in PCI based systems
-  (most new systems have PCI slots).  But if your system uses VESA
-  local bus (VLB) instead of PCI, you must also supply a kernel boot
-  parameter to enable the CMD640 bugfix/support: "ide0=cmd640_vlb".
+  systems.  
+
+  This driver will work automatically in PCI based systems (most new
+  systems have PCI slots). But if your system uses VESA local bus
+  (VLB) instead of PCI, you must also supply a kernel boot parameter
+  to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
+  bootparam" or see the documentation of your boot loader about how to
+  pass options to the kernel. The lilo procedure is also explained in
+  the SCSI-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.)
+
   The CMD640 chip is also used on add-in cards by Acculogic, and on
   the "CSA-6400E PCI to IDE controller" that some people have. For
   details, read Documentation/ide.txt. If unsure, say Y.
@@ -348,16 +380,18 @@
   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/. Read the comments at the
-  beginning of drivers/block/idedma.c and the file
-  Documentation/ide.txt for more information.
+  ftp://sunsite.unc.edu/pub/Linux/system/hardware/. 
+
+  Read the comments at the beginning of drivers/block/idedma.c and the
+  file Documentation/ide.txt for more information. 
+
   It is safe to say Y to this question.
 
 Other IDE chipset support
 CONFIG_IDE_CHIPSETS
   Say Y here if you want to include enhanced support for various IDE
   interface chipsets used on motherboards and add-on cards.  This
-  enhanced support may be necessary for linux to be able to access the
+  enhanced support may be necessary for Linux to be able to access the
   3rd/4th drives in some systems.  It may also enable setting of
   higher speed I/O rates to improve system performance with these
   chipsets.  Most of these also require special kernel boot parameters
@@ -396,6 +430,12 @@
   "ide0=dc4030" kernel boot parameter.  See the Documentation/ide.txt
   and drivers/block/pdc4030.c files for more info.
 
+PS/2 ESDI hard disk support
+CONFIG_BLK_DEV_PS2
+  Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
+  hard disk.
+
+Tekram TRM290 chipset support (EXPERIMENTAL)
 CONFIG_BLK_DEV_TRM290
   This driver adds support for bus master DMA transfers
   using the Tekram TRM290 PCI IDE chip.  Volunteers are
@@ -458,21 +498,24 @@
   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 said Y to the "Parallel-port support" 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 say Y or M
-  here and also to at least one high-level driver (e.g. "Parallel port
-  IDE disks", "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI
-  disks" etc.) and to at least one protocol driver (e.g. "ATEN EH-100
-  protocol", "MicroSolutions backpack protocol", "DataStor Commuter
-  protocol" etc.). If you build this support as a module, it will be
-  called paride.o.
+  Read linux/Documentation/paride.txt for more information.
+
+  If you have said Y to the "Parallel-port support" 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. If you build this support as a module,
+  it will be called paride.o.
+
+  To use the PARIDE support, you must say Y or M here and also to at
+  least one high-level driver (e.g. "Parallel port IDE disks",
+  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
+  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
+  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
+  etc.).
 
 Parallel port IDE disks
 CONFIG_PARIDE_PD 
@@ -626,12 +669,14 @@
 Multiple devices driver support
 CONFIG_BLK_DEV_MD
   This driver lets you combine several hard disk 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/Linux in the md package and the
-  md-FAQ. Please read drivers/block/README.md and the relevant section
-  of the Disk-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. If unsure, say N.
+  logical block device. This can be used to combine several redundant
+  hard disks to a RAID1/4/5 device so as to provide protection against
+  hard disk failures. More information and the necessary tools are
+  available over ftp (user: anonymous) from
+  ftp://sweet-smoke.ufr-info-p7.ibp.fr/pub/Linux in the md package and
+  the md-FAQ. Please read drivers/block/README.md and the relevant
+  section of the Disk-HOWTO, available via ftp (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If unsure, say N.
 
 Linear (append) mode
 CONFIG_MD_LINEAR
@@ -663,11 +708,14 @@
   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:
+  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
+
+  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
@@ -682,10 +730,12 @@
   For a RAID-4 set, the parity blocks are present on a single drive,
   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
+
+  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
@@ -694,8 +744,8 @@
 
 Boot support (linear, striped)
 CONFIG_MD_BOOT
-  To boot with an initial linear or striped md device you have to 
-  select this. For lilo and loadlin options see Documentation/md.txt.
+  To boot with an initial linear or striped md device you have to say
+  Y here. For lilo and loadlin options see Documentation/md.txt.
 
 Support for Deskstation RPC44 
 CONFIG_DESKSTATION_RPC44
@@ -708,11 +758,11 @@
 
 Support for Mips Magnum 3000 
 CONFIG_MIPS_MAGNUM_3000
-  To compile a Linux kernel that runs on these, say Y here. For
-  details about Linux on the MIPS architecture, check out the
+  To compile a Linux kernel that runs on these machines, say Y here.
+  For details about Linux on the MIPS architecture, check out the
   Linux/MIPS FAQ on the WWW at http://lena.fnet.fr/ (To browse the
-  WWW, you need to have access to a machine on the Internet that has
-  a program like lynx or netscape).
+  WWW, you need to have access to a machine on the Internet that has a
+  program like lynx or netscape).
 
 Support for Mips Magnum 4000
 CONFIG_MIPS_MAGNUM_4000
@@ -773,52 +823,31 @@
   should consider updating your networking tools too because changes
   in the kernel and the tools often go hand in hand. The tools are
   contained in the package net-tools, the location and version number
-  of which is given in Documentation/Changes.
-
-Fast switching (read help!)
-CONFIG_NET_FASTROUTE
-  Enables direct NIC-to-NIC data transfers, which is fast.
-    *** This option is NOT COMPATIBLE with several important ***
-    *** networking options: especially CONFIG*FIREWALL.      ***
-  However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER
-  section (except for CONFIG_IP_ROUTE_TOS). At the moment, few devices
-  support fast switching (tulip is one of them, modified 8390 can be
-  found at ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). If
-  unsure, say N.
-
-Forwarding between high speed interfaces
-CONFIG_NET_HW_FLOWCONTROL
-  This option enables NIC hardware throttling during periods of
-  extremal congestion. At the moment only a couple of device drivers
-  support it (really only one ---tulip, modified 8390 can be found at
-  ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz).  Really, this
-  option is applicable to any machine attached to a fast enough
-  network, and even a 10Mb NIC is able to kill a not very slow box,
-  such as a 120MHz Pentium.
-  However, do not enable this option, if you did not experience
-  any serious problems.
+  of which are given in Documentation/Changes.
 
 Network aliasing
 CONFIG_NET_ALIAS
-  This will allow you to set multiple network addresses on the same
-  low-level network device driver. Typically used for services that
-  act differently based on the address they listen on (e.g.
-  "multihosting" or "virtual domains" or "virtual hosting services" on
-  the web server apache and the ftp server wuftpd -- read the
-  Virtual-Services-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO) or for connecting to
-  different logical networks through the same physical interface (most
-  commonly an Ethernet networking card). This is the generic part,
-  later when configuring network protocol options you will be asked
-  for protocol-specific aliasing support, and you will have to say Y
-  to at least one of them, most likely "IP: aliasing support". See
-  Documentation/networking/alias.txt for more info. If you need this
-  feature (for any protocol, like IP) say Y; if unsure, say N.
+  If you say Y here, you will be able to set multiple network
+  addresses on the same low-level network device driver. This is
+  typically used for services that act differently based on the
+  address they listen on (e.g. "multihosting" or "virtual domains" or
+  "virtual hosting services" on the web server apache and the ftp
+  server wuftpd -- read the Virtual-Services-HOWTO, available via ftp
+  (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO)
+  or for connecting to different logical networks through the same
+  physical interface (most commonly an Ethernet networking card). See
+  Documentation/networking/alias.txt for more info.
+
+  This is the generic part, later when configuring network protocol
+  options you will be asked for protocol-specific aliasing support,
+  and you will have to say Y to at least one of them, most likely to
+  "IP: aliasing support". If you need this feature (for any protocol,
+  like IP) say Y; if unsure, say N.
 
 Socket filtering
 CONFIG_FILTER
   The Linux Socket Filter is derived from the Berkeley Packet Filter.
-  If you say Y here, user-space programs can attach a filter onto any
+  If you say Y here, user-space programs can attach a filter to any
   socket and thereby tell the kernel that it should allow or disallow
   certain types of data to get through the socket. Linux Socket
   Filtering works on all socket types except TCP for now. See the text
@@ -829,22 +858,39 @@
 CONFIG_FIREWALL
   A firewall is a computer which protects a local network from the
   rest of the world: all traffic to and from computers on the local
-  net is inspected by the firewall first, and sometimes blocked. If
-  you want to configure your Linux box as a firewall for a local
-  network, say Y here. If your local network is TCP/IP based, you will
-  then also have to say Y to "IP: firewalling", below.  
-  You also need to say Y here and say Y to "IP firewalling" below 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). Chances are that you should use this on every machine
-  being run as a router and not on any regular host. If unsure, say N.
+  net is inspected by the firewall first, and sometimes blocked or
+  modified. The type of firewall you'll get if you say Y here is
+  called a "packet filter": it can block network traffic based on
+  type, origin and destination. By contrast, "proxy-based" firewalls
+  are more secure but more intrusive and more bothersome to set up;
+  they inspect the network traffic much more closely, modify it and
+  have knowledge about the higher level protocols, which packet
+  filters lack. They also often require changes in the programs
+  running on the local clients. Proxy-based firewalls don't need
+  support by the kernel, but they are often combined with packet
+  filters, which only works if you say Y here.
+
+  If you want to configure your Linux box as a packet filter firewall
+  for a local network, say Y here. If your local network is TCP/IP
+  based, you will then also have to say Y to "IP: firewalling", below.
+
+  You also need to say Y here and to "IP firewalling" below 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 to the outside world and avoids the need to allocate
+  globally valid IP host addresses for the machines on the local net)
+  and IP packet accounting (keeping track of what is using up 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).
+  
+  Make sure to say N to "Fast switching" below if you intend to say Y
+  here.
+
+  Chances are that you should say Y here for every machine which is
+  run as a router and N for every regular host. If unsure, say N.
 
 SYN flood protection
 CONFIG_SYN_COOKIES
@@ -852,19 +898,24 @@
   This denial-of-service attack prevents legitimate remote users from
   being able to connect to your computer and requires very little work
   from the attacker, who can operate from anywhere on the Internet.
-  SYN cookies provide protection against this type of attack. With
-  this option turned on, the TCP/IP stack will use a cryptographic
-  challenge protocol known as SYN cookies to enable legitimate users
-  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
+
+  SYN cookies provide protection against this type of attack. If you
+  say Y here, the TCP/IP stack will use a cryptographic challenge
+  protocol known as "SYN cookies" to enable legitimate users 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
   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
+
+  If you say Y here, note that SYN cookies aren't enabled by default;
+  you can enable them by saying Y to "/proc filesystem support" and
+  "Sysctl support" below and executing the command
+
     echo 1 >/proc/sys/net/ipv4/tcp_syncookies 
-  to one of your startup scripts (e.g. /etc/rc.local or 
-  /etc/rc.d/rc.local) in addition.
+
+  at boot time after the proc filesystem has been mounted.
+  
   If unsure, say Y.
 
 Sun floppy controller support
@@ -879,7 +930,7 @@
   http://www.azstarnet.com/~axplinux/ (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 the Alpha-HOWTO, available via ftp (user:
-  anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. For this
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. For this
   question, it suffices to give a unique prefix of the option you want
   to choose. The choices:
   ** Avanti: This is for Mustang (AS200), M3 (AS250), Avanti (AS400)
@@ -910,21 +961,24 @@
 CONFIG_ALPHA_SRM
   There are two different types of booting firmware on Alphas: SRM,
   which is command line driven, and ARC, which uses menus and arrow
-  keys. The usual way to load Linux on an Alpha machine is to use MILO
+  keys. Details about the Linux/Alpha booting process are contained in
+  the Linux/Alpha FAQ, accessible on the WWW from
+  http://www.azstarnet.com/~axplinux/ (To browse the WWW, you need to
+  have access to a machine on the Internet that has a program like
+  lynx or netscape).
+
+  The usual way to load Linux on an Alpha machine is to use MILO
   (a bootloader that lets you pass command line parameters to the
-  kernel just like lilo does for the 386 architecture) which can be
+  kernel just like lilo does for the x86 architecture) which can be
   loaded either from ARC or can be installed directly as a permanent
   firmware replacement from floppy (which requires changing a certain
   jumper on the motherboard). If you want to do either of these, say N
   here. If MILO doesn't work on your system (true for Jensen
   motherboards), you can bypass it altogether and boot Linux directly
   from an SRM console; say Y here in order to do that. Note that you
-  won't be able to boot from an IDE disk using SRM. If unsure, say
-  N. Details about the Linux/Alpha booting process are contained in
-  the Linux/Alpha FAQ, accessible on the WWW from
-  http://www.azstarnet.com/~axplinux/ (To browse the WWW, you need to
-  have access to a machine on the Internet that has a program like
-  lynx or netscape).
+  won't be able to boot from an IDE disk using SRM. 
+
+  If unsure, say N.
 
 Non-standard serial port support
 CONFIG_SERIAL_NONSTANDARD
@@ -950,14 +1004,15 @@
 
 Support more than 4 serial ports
 CONFIG_SERIAL_MANY_PORTS
-  Enable this option if you have dumb serial boards other than the
-  four standard COM 1/2/3/4 ports. This may happen if you have an AST
+  Say Y here if you have dumb serial boards other than the four
+  standard COM 1/2/3/4 ports. This may happen if you have an AST
   FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
   via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini), or other custom serial
-  port hardware which acts similar to standard serial port hardware.
-  If you only use the standard COM 1/2/3/4 ports, you can say N here
-  to save some memory.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini), or other custom
+  serial port hardware which acts similar to standard serial port
+  hardware. If you only use the standard COM 1/2/3/4 ports, you can
+  say N here to save some memory. You can also say Y if you have an
+  "intelligent" multiport card such as Cyclades, Digiboards, etc.
 
 Support for sharing serial interrupts
 CONFIG_SERIAL_SHARE_IRQ
@@ -996,7 +1051,7 @@
   that implements the TGA interface (much like the VGA standard, but
   older TGA adapters are *not* VGA compatible).  On such systems, you
   should say Y here so that the TGA driver rather than the standard
-  VGA driver is used.
+  VGA driver is used. 
 
 PCI support
 CONFIG_PCI
@@ -1007,6 +1062,7 @@
   via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO,
   contains valuable information about which PCI hardware does work
   under Linux and which doesn't.
+
   If some of your PCI devices don't work and you get a warning during
   boot time ("man dmesg"), please follow the instructions at the top
   of include/linux/pci.h.
@@ -1016,9 +1072,10 @@
   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.
+  BIOS bugs and may crash if you say Y here -- 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.
 
@@ -1047,12 +1104,17 @@
 Backward-compatible /proc/pci
 CONFIG_PCI_OLD_PROC
   Older kernels supported a /proc/pci file containing brief textual
-  description of all PCI devices in the system. Several programs tried
-  to parse this file, so it became almost impossible to add new
+  descriptions of all PCI devices in the system. Several programs
+  tried to parse this file, so it became almost impossible to add new
   fields without breaking compatibility. So a new /proc interface to
-  PCI (/proc/bus/pci) has been implemented and the old one is supported
-  for compatibility reasons only (you can disable it here, gaining
-  some memory).  If unsure, say Y.
+  PCI (/proc/bus/pci) has been implemented and the old one is
+  supported for compatibility reasons only; you'll get the old one (in
+  addition to the new one) if you say Y here and to "/proc filesystem
+  support", below. If unsure, say Y.
+
+If you say Y here and to the "/proc filesystem support" below, you
+  will get a directory /proc/pci with information about your PCI
+  hardware. If unsure, say Y.
 
 MCA support
 CONFIG_MCA
@@ -1064,19 +1126,21 @@
 
 System V IPC
 CONFIG_SYSVIPC
-  Inter Process Communication is a suite of library functions and system
-  calls which let processes (= running programs) synchronize and
-  exchange information. It is generally considered to be a good thing,
-  and some programs won't run unless you say Y here. In particular,
-  if you want to run the DOS emulator dosemu under Linux (read the
-  DOSEMU-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO), you'll need to say Y here. You
-  can find documentation about IPC in ipc.info, which is contained in
-  sunsite.unc.edu:/pub/Linux/docs/man/info.tar.gz (extract with "tar
-  xzvf filename"). These docs are in the info format which is used to
-  document GNU software and can be read from within emacs ("Ctrl-h i")
-  or with the program info ("man info"). Saying Y here enlarges
-  your kernel by about 7kB. Just say Y.
+  Inter Process Communication is a suite of library functions and
+  system calls which let processes (= running programs) synchronize
+  and exchange information. It is generally considered to be a good
+  thing, and some programs won't run unless you say Y here. In
+  particular, if you want to run the DOS emulator dosemu under Linux
+  (read the DOSEMU-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO), you'll need to say Y
+  here.
+  
+  You can find documentation about IPC with "info ipc" and also in
+  section 6.4 of the Linux Programmer's Guide, available via ftp
+  (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/LDP/programmers-guide.
+
+  Saying Y here enlarges your kernel by about 7kB. Just say Y.
 
 BSD Process Accounting
 CONFIG_BSD_PROCESS_ACCT
@@ -1100,33 +1164,36 @@
   beneath the /proc/sys directory. They are explained in the files in
   Documentation/sysctl/. Note that enabling this option will enlarge
   the kernel by at least 8kB. As it is generally a good thing, you
-  probably want to say Y here unless building a kernel for
-  install/rescue disks or your system is very limited in memory.
+  should say Y here unless building a kernel for install/rescue disks
+  or your system is very limited in memory.
 
 Kernel support for ELF binaries
 CONFIG_BINFMT_ELF
   ELF (Executable and Linkable Format) is a format for libraries and
   executables used across different architectures and operating
-  systems. This option will enable your kernel to run ELF binaries and
+  systems. Saying Y here will enable your kernel to run ELF binaries and
   enlarge it by about 2kB. ELF support under Linux has now all but
   replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
   because it is portable (this does *not* mean that you will be able
   to run executables from different architectures or operating
   systems!) and makes building run-time libraries very easy. Many new
   executables are distributed solely in ELF format. You definitely
-  want to say Y here. Information about ELF is on the WWW at
+  want to say Y here. 
+
+  Information about ELF is on the WWW at
   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
-  program like lynx or netscape).  If you find that after upgrading
+  program like lynx or netscape). If you find that after upgrading
   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
-  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
-  binfmt_elf.o. Saying M or N here is dangerous because some crucial
-  programs on your system might be in ELF format.
+  Documentation/Changes for location and latest version).
+
+  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 binfmt_elf.o. Saying M or N here is dangerous because some
+  crucial programs on your system might be in ELF format.
 
 Kernel support for A.OUT binaries
 CONFIG_BINFMT_AOUT
@@ -1134,6 +1201,7 @@
   executables used in the earliest versions of UNIX. Linux used the
   a.out formats QMAGIC and ZMAGIC until they were replaced with the
   ELF format.
+
   As more and more programs are converted to ELF, the use for a.out
   will gradually diminish. If you disable this option it will reduce
   your kernel by one page. This is not much and by itself does not
@@ -1153,13 +1221,16 @@
   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.
+  architectures and 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
+  ftp://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
@@ -1167,13 +1238,16 @@
   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. 
+  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 should
@@ -1193,31 +1267,36 @@
 CONFIG_BINFMT_MISC
   This enables the possibility to plug wrapper-driven binary formats
   into the kernel. You will like this especially when you use programs
-  that need an interpreter to run like Java, Python or
-  Emacs-Lisp. Once you have registered such a binary class with the
-  kernel, you can start such a program simply by typing in its name;
-  Linux will feed it to the correct interpreter. If you say Y here,
-  you won't need "Kernel support for JAVA binaries"
+  that need an interpreter to run like Java, Python or Emacs-Lisp.
+  Once you have registered such a binary class with the kernel, you
+  can start such a program simply by typing in its name; Linux will
+  feed it to the correct interpreter.
+
+  If you say Y here, you won't need "Kernel support for JAVA binaries"
   (CONFIG_BINFMT_JAVA) or "Kernel support for Linux/Intel ELF
   binaries" (CONFIG_BINFMT_EM86), as this is a more general solution.
+
   You can do other nice things, too. Read
   Documentation/binfmt_misc.txt to learn how to use this feature, and
   Documentation/java.txt for information about how to include Java
-  support. 
+  support.
+
   You must enable the "proc filesystem support" (CONFIG_PROC_FS) to
   use this part of the kernel.
+
   You may answer M for module support and later load the module when
-  you have use for it; the module is called binfmt_misc.o.  
-  If you don't know what to answer at this point, say Y.
+  you have use for it; the module is called binfmt_misc.o. 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.
+  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
@@ -1229,6 +1308,7 @@
   (=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 have a single processor machine, make sure that the line
   "SMP=1" at the top of the toplevel kernel Makefile is commented out;
   if you have a multi processor machine and want Linux to use all the
@@ -1239,10 +1319,14 @@
   need to have access to a machine on the Internet that has a program
   like lynx or netscape). People using multiprocessor machines should
   also say Y to "Enhanced Real Time Clock Support", below.
+
   If you want to compile a kernel that should work on both single
-  processor and multi processor machines, it is possible to set
-  SMP=1. The "Advance Power Management" code (see configuration option
-  below) will not work in that scenario, though.
+  processor and multi processor machines, it is possible to set SMP=1.
+  The "Advanced Power Management" code (see configuration option
+  below) will not work in that scenario, though. In addition, the
+  kernel will be slower on single processor machines, and other
+  problems may appear, so this is not recommended.
+
   If you don't know what to do, choose "386".
 
 Video mode selection support
@@ -1256,30 +1340,34 @@
   "man bootparam" or see the documentation of your boot loader about
   how to pass options to the kernel. The lilo procedure is also
   explained in the SCSI-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  Read Documentation/svga.txt
-  for more information about the Video mode selection support. If
-  unsure, say N.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Read
+  Documentation/svga.txt for more information about the Video mode
+  selection support. If unsure, say N.
 
 Parallel-port support
 CONFIG_PARPORT
-  If you want to use devices connected to your parallel port (the
-  connector at the computer with 25 holes), e.g. printer, Zip drive,
-  PLIP link (Parallel Line Internet Protocol is mainly used to create
-  a mini network by connecting the parallel ports of two local
+  If you want to use devices connected to your machine's parallel port
+  (the connector at the computer with 25 holes), e.g. printer, Zip
+  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
+  create a mini network by connecting the parallel ports of two local
   machines) etc., then you need to say Y here; please read
-  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 program 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 be used 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 program 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 be used by
+  this driver at module load time, read
+  Documentation/networking/net-modules.txt.
+
   If unsure, say Y.
 
 PC-style hardware 
@@ -1329,10 +1417,11 @@
   inserted in or removed from the running kernel, using the programs
   insmod and rmmod. This is described in the file
   Documentation/modules.txt, including the fact that you have to say
-  "make modules" in order to compile the modules. Modules can be
-  device drivers, file systems, binary executable formats, and so
-  on. If you think that you may want to make use of modules with this
-  kernel in the future, then say Y here. If unsure, say Y.
+  "make modules" in order to compile the modules that you chose during
+  kernel configuration. Modules can be device drivers, file systems,
+  binary executable formats, and so on. If you think that you may want
+  to make use of modules with this kernel in the future, then say Y
+  here. If unsure, say Y.
 
 Set version information on all symbols for modules
 CONFIG_MODVERSIONS
@@ -1354,7 +1443,7 @@
   be created as loadable modules, you also have the responsibility to
   load the corresponding modules (using the programs insmod or
   modprobe) before you can use them. If you say Y here however, the
-  kernel will be able to load modules for itself. When a part of the
+  kernel will be able to load modules for itself: when a part of the
   kernel needs a module, it runs modprobe with the appropriate
   arguments. (This is a replacement for kerneld.) Say Y here and read
   about configuring it in Documentation/kmod.txt.
@@ -1369,14 +1458,18 @@
   resolution (ARP) cache inside the kernel works well.  However,
   maintaining an internal ARP cache does not work well for very large
   switched networks, and will use a lot of kernel memory if TCP/IP
-  connections are made to many machines on the network.  By saying Y
-  here, the kernel's internal ARP cache will never grow to more than
-  256 entries (the oldest entries are expired in a LIFO manner) and
-  communication will be attempted with an external ARP daemon, arpd.
-  This code is still experimental.  If you do say Y here, you should
-  obtain a copy of arpd from http://www.loran.com/~layes/arpd/index.html, 
-  and you should say Y to "Kernel/User network link driver", below.
-  If unsure, say N.
+  connections are made to many machines on the network.  
+
+  If you say Y here, the kernel's internal ARP cache will never grow
+  to more than 256 entries (the oldest entries are expired in a LIFO
+  manner) and communication will be attempted with the user space ARP
+  daemon arpd. Arpd then answers the address resolution request either
+  from its own cache or by asking the net.
+
+  This code is still experimental. If you do say Y here, you should
+  obtain a copy of arpd from
+  http://www.loran.com/~layes/arpd/index.html, and you should also say
+  Y to "Kernel/User network link driver", below. If unsure, say N.
 
 TCP/IP networking
 CONFIG_INET
@@ -1390,6 +1483,13 @@
   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).
+  
+  If you say Y here and also to "/proc filesystem support" and "Sysctl
+  support" below, you can change various aspects of the behavior of
+  the TCP/IP code by writing to the (virtual) files in
+  /proc/sys/net/ipv4/*; the options are explained in the file
+  Documentation/Networking/ip-sysctl.txt.
+
   Short answer: say Y.
 
 IP: multicasting
@@ -1412,14 +1512,19 @@
   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.  
+
+  Note that your box can only act as a router if you enable IP
+  forwarding in your kernel; you can do that by saying Y to "/proc
+  filesystem support" and "Sysctl support" below and executing the line
+
+    echo "1" > /proc/sys/net/ipv4/ip_forward
+
+  at boot time after the /proc filesystem has been mounted.  
+
   If unsure, say N here.
 
 IP: policy routing
@@ -1470,50 +1575,62 @@
 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 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
+  to optimize host performance. For a machine which acts as 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 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.
+
+  Note that your box can only act as a router if you enable IP
+  forwarding in your kernel; you can do that by saying Y to "/proc
+  filesystem support" and "Sysctl support" below and executing the line
+
+    echo "1" > /proc/sys/net/ipv4/ip_forward
+
+  at boot time after the /proc filesystem has been mounted.  
+
+  If unsure, say N here.
 
 IP: firewalling
 CONFIG_IP_FIREWALL
-  If you want to configure your Linux box as a firewall for a local
-  TCP/IP based network, say Y here. This will enlarge your kernel by
-  about 2kB. You may need to read the FIREWALL-HOWTO, available via
-  ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also, you will need the
-  ipfwadm tool (available via ftp (user: anonymous) from
-  ftp.xos.nl/pub/linux/ipfwadm/) to allow selective blocking of
-  Internet traffic based on type, origin and destination; this type of
-  firewall is called a "packet filter".  The other type of firewall,
-  "proxy-based" ones, is more secure but more intrusive and more
-  bothersome to set up; it inspects the network traffic much more
-  closely and has knowledge about the higher level protocols, which
-  packet filters lack. Proxy-based firewalls don't need support by the
-  kernel, but they are often combined with a packet filter, which only
-  works if you say Y here.
-  The firewalling code will only work if you say Y to "/proc
-  filesystem 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.  
+  If you want to configure your Linux box as a packet filter firewall
+  for a local TCP/IP based network, say Y here. This will enlarge your
+  kernel by about 2kB. You may need to read the FIREWALL-HOWTO,
+  available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  Also, you will need the ipfwadm tool (available via ftp (user:
+  anonymous) from ftp://ftp.xos.nl/pub/linux/ipfwadm/) to allow selective
+  blocking of Internet traffic based on type, origin and destination;
+  this type of firewall is called a "packet filter". The other type of
+  firewall, "proxy-based" ones, is more secure but more intrusive and
+  more bothersome to set up; it inspects the network traffic much more
+  closely, modifies it and has knowledge about the higher level
+  protocols, which a packet filter lacks. Moreover, proxy-based
+  firewalls often require changes to the programs running on the local
+  clients. Proxy-based firewalls don't need support by the kernel, but
+  they are often combined with a packet filter, which only works if
+  you say Y here.
+
+  The firewalling code will only work if IP forwarding is enabled in
+  your kernel. You can do that by saying Y to "/proc filesystem
+  support" and "Sysctl support" below and executing the line
+
+    echo "1" > /proc/sys/net/ipv4/ip_forward
+
+  at boot time 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.
+  invisible to the outside world and avoids the need to allocate
+  globally 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).
 
 IP: firewall packet netlink device
 CONFIG_IP_FIREWALL_NETLINK
@@ -1535,7 +1652,7 @@
   /proc/net/ip_acct", so you want to say Y to the /proc filesystem
   below, if you say Y here. To specify what exactly should be
   recorded, you need the tool ipfwadm (available via ftp (user:
-  anonymous) from ftp.xos.nl/pub/linux/ipfwadm/).
+  anonymous) from ftp://ftp.xos.nl/pub/linux/ipfwadm/).
 
 IP: kernel level autoconfiguration
 CONFIG_IP_PNP
@@ -1580,10 +1697,11 @@
   appear on a different network than it physically is, or to use
   mobile-IP facilities (allowing laptops to seamlessly move between
   networks without changing their IP addresses; check out
-  http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html). Saying Y
-  to this option will produce two modules ( = code which can be
-  inserted in and removed from the running kernel whenever you want),
-  one encapsulator called tunnel.o and one decapsulator called
+  http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html). 
+
+  Saying Y to this option will produce two modules ( = code which can
+  be inserted in and removed from the running kernel whenever you
+  want), one encapsulator called tunnel.o and one decapsulator called
   ipip.o. You can read details in drivers/net/README.tunnel. Most
   people won't need this and can say N.
 
@@ -1640,20 +1758,29 @@
   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/].) The IP
-  masquerading code will only work if you say Y to "/proc filesystem
-  support" below and IP forwarding is enabled 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. Details on how to set things up are contained in the IP
-  Masquerade mini-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. If you say Y here, then
-  the modules ip_masq_ftp.o (for ftp transfers through the firewall),
-  ip_masq_irc.o (for irc chats through the firewall), and
-  ip_masq_raudio.o (for realaudio downloads through the firewall) will
-  automatically be compiled. Modules are pieces of code which can be
-  inserted in and removed from the running kernel whenever you want;
-  read Documentation/modules.txt for details.
+  ftp://sunsite.unc.edu/pub/Linux/system/network/serial/ ].) 
+
+  The IP masquerading code will only work if IP forwarding is enabled
+  in your kernel; you can do this by saying Y to "/proc
+  filesystem support" and "Sysctl support" below and then executing a
+  line like
+
+    echo "1" > /proc/sys/net/ipv4/ip_forward
+
+  from a boot time script after the /proc filesystem has been mounted. 
+
+  Details on how to set things up are contained in the IP Masquerade
+  mini-HOWTO, available via ftp (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini.
+
+  If you say Y here, you should also say Y to "IP: always defragment",
+  below. If you say Y here, then the modules ip_masq_ftp.o (for ftp
+  transfers through the firewall), ip_masq_irc.o (for irc chats
+  through the firewall), and ip_masq_raudio.o (for realaudio downloads
+  through the firewall) will automatically be compiled. Modules are
+  pieces of code which can be inserted in and removed from the running
+  kernel whenever you want; read Documentation/modules.txt for
+  details.
 
 IP: ICMP masquerading
 CONFIG_IP_MASQUERADE_ICMP
@@ -1662,22 +1789,24 @@
   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. 
 
-IP: ipautofw masquerade support
-CONFIG_IP_MASQUERADE_IPAUTOFW (Experimental)
+IP: ipautofw masquerade support (Experimental)
+CONFIG_IP_MASQUERADE_IPAUTOFW
   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
+  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. 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.
+  marked EXPERIMENTAL. If you want to try it, 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
@@ -1688,32 +1817,34 @@
   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. 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.
+  marked EXPERIMENTAL. If you want to try it, 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
   This option means that all incoming fragments (= parts of IP packets
   that arose when some host between origin and destination decided
-  that the IP packets were too large and cut them in pieces) will be
+  that the IP packets were too large and cut them into pieces) will be
   reassembled (defragmented) before being processed, even if they are
-  about to be forwarded.  This option is highly recommended if you
-  have said Y to "IP: masquerading" because that facility requires
-  that second and further fragments can be related to TCP or UDP port
-  numbers, which are only stored in the first fragment.  When using
-  "IP: firewalling" support , you might also want to say Y here, to
-  have a more reliable firewall (otherwise second and further
-  fragments will always be accepted by the firewall).  When using "IP:
-  transparent proxying", this option is implicit, although it is safe
-  to say Y here. Do not say Y to this option except when running
-  either a firewall that is the sole link to your network or a
-  transparent proxy. Never ever say Y to this for a normal router or
-  host.
+  about to be forwarded.  
+
+  This option is highly recommended if you have said Y to "IP:
+  masquerading" because that facility requires that second and further
+  fragments can be related to TCP or UDP port numbers, which are only
+  stored in the first fragment. When using "IP: firewalling" support ,
+  you might also want to say Y here, to have a more reliable firewall
+  (otherwise second and further fragments will always be accepted by
+  the firewall). When using "IP: transparent proxying", this option is
+  implicit, although it is safe to say Y here. Do not say Y to this
+  option except when running either a firewall that is the sole link
+  to your network or a transparent proxy. Never ever say Y to this for
+  a normal router or host.
 
 IP: aliasing support
 CONFIG_IP_ALIAS
@@ -1727,13 +1858,17 @@
   WWW, you need to have access to a machine on the Internet that has a
   program like lynx or netscape) and also in the
   Virtual-Hosting-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Another scenario would be
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. 
+
+  Another scenario would be
   that there are two logical networks living on your local Ethernet
-  and you want to access them both with the same Ethernet card. The
-  configuration of these alias addresses is done with a special name
-  syntax explained in Documentation/networking/alias.txt and in the
-  IP-Alias mini-HOWTO. If you want this, say Y. Most people don't need
-  it and say N.
+  and you want to access them both with the same Ethernet card. This
+  can be done if you say Y here.
+
+  The configuration of these alias addresses is done with a special
+  name syntax explained in Documentation/networking/alias.txt and in
+  the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
+  need it and say N.
 
 IP: multicast routing
 CONFIG_IP_MROUTE
@@ -1772,28 +1907,35 @@
   here.  Everyone else says N. People having problems with NCSA telnet
   should see the file linux/Documentation/networking/ncsa-telnet.
 
-Reverse ARP
+Reverse ARP server
 CONFIG_INET_RARP
-  Since you asked: if there are (usually diskless or portable)
-  machines on your local network that know their hardware Ethernet
-  addresses but don't know their IP addresses upon startup, they can
-  send out a Reverse Address Resolution Protocol (RARP) request to
-  find out their own IP addresses. Diskless Sun 3 machines use this
-  procedure at boot time. If you want your Linux box to be able to
-  *answer* such requests, say Y here; you'd have to run the program
-  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
-  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
+  If there are (usually diskless or portable) machines on your local
+  network that know their hardware Ethernet addresses but don't know
+  their IP addresses upon startup, they can send out a Reverse Address
+  Resolution Protocol (RARP) request to find out their own IP
+  addresses. Diskless Sun 3 machines use this procedure at boot time,
+  and diskless Linux boxes can be configured to do it as well.
+  
+  If you want your Linux box to be able to *answer* such requests, say
+  Y here; you'll then have to run the program 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 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 (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.
+  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.
 
@@ -1805,20 +1947,6 @@
   links, between machines of your IP network, say N.  If in doubt, say
   N. The PATH mtu discovery facility will cover most cases anyway.
 
-Disable Path MTU Discovery (normally enabled)
-CONFIG_NO_PATH_MTU_DISCOVERY
-  MTU (maximal transfer unit) is the size of the chunks we send out
-  over the net. "Path MTU Discovery" means that, instead of always
-  sending very small chunks, we start out sending big ones and if we
-  then discover that some host along the way likes its chunks smaller,
-  we adjust to a smaller size. This is good, so most people say N
-  here, thereby not disabling it. However, some DOS software (versions
-  of DOS NCSA telnet and Trumpet Winsock in PPP mode) is broken and
-  won't be able to connect to your Linux machine correctly in all
-  cases (especially through a terminal server) unless you say Y
-  here. See Documentation/networking/ncsa-telnet for the location of
-  fixed NCSA telnet clients. If in doubt, say N.
-
 Path MTU Discovery (normally enabled)
 CONFIG_PATH_MTU_DISCOVERY
   MTU (maximal transfer unit) is the size of the chunks we send out
@@ -1826,10 +1954,14 @@
   sending very small chunks, we start out sending big ones and if we
   then discover that some host along the way likes its chunks smaller,
   we adjust to a smaller size. This is good, so most people say
-  Y here. However, some versions of DOS NCSA telnet (and other software)
-  are broken and can only connect to your Linux machine if you say N
-  here. See Documentation/networking/ncsa-telnet for the location
-  of fixed NCSA telnet clients. If in doubt, say Y.
+  Y here. 
+
+  However, some DOS software (versions of DOS NCSA telnet and Trumpet
+  Winsock in PPP mode) is broken and won't be able to connect to your
+  Linux machine correctly in all cases (especially through a terminal
+  server) unless you say N here. See
+  Documentation/networking/ncsa-telnet for the location of fixed NCSA
+  telnet clients. If in doubt, say Y.
 
 Disable NAGLE algorithm (normally enabled)
 CONFIG_TCP_NAGLE_OFF
@@ -1853,7 +1985,7 @@
   problems (and is rarely a useful feature), and hence it is recommended
   that you say Y here unless you really know what you're doing.
 
-IP: Allow large windows (not recommend if <16Mb of memory)
+IP: Allow large windows (not recommended if <16Mb of memory)
 CONFIG_SKB_LARGE
   On high speed, long distance networks the performance limit on 
   networking becomes the amount of data a machine can buffer until the
@@ -1869,14 +2001,16 @@
 Unix domain sockets
 CONFIG_UNIX
   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
+  establishing and accessing network connections. Unless you are
+  working on an embedded system or something, you definitely want to
+  say Y here.
+
+  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
+  to add 'alias net-pf-1 unix' to your /etc/conf.module file. If
   unsure, say Y.
 
 The IPv6 protocol
@@ -1890,62 +2024,84 @@
   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.
+  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, 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
+  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 your site is moved to EUI-64
+  Linux tries to operate correctly when your site has 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
+  "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.
 
+IPv6: routing messages via old netlink
+CONFIG_IPV6_NETLINK
+  You can say Y here to receive routing messages from the IPv6 code
+  through the old netlink interface. However, a better option is to
+  say Y to "Kernel/User network link driver" and to "Routing
+  messages" instead.
+  
 The IPX protocol
 CONFIG_IPX
   This is support for the Novell networking protocol, IPX, commonly
   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
-  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
+  ftp://sunsite.unc.edu/pub/Linux/system/filesystems/) or from within
+  the Linux DOS emulator dosemu (read the DOSEMU-HOWTO, available in
+  ftp://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.
+
+  IPX is similar in scope to IP, while SPX, which runs on top of IPX,
+  is similar to TCP. There is also experimental support for SPX in
+  Linux (see "SPX networking", 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
-  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
-  available as a module ( = code which can be inserted in and removed
-  from the running kernel whenever you want). The module will be
-  called ipx.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt.  Unless you want to integrate
+  ftp://sunsite.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe from
+  ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. For more information, read the
+  IPX-HOWTO in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+  General information about how to connect Linux, Windows machines and
+  Macs is on the WWW at http://www.eats.com/linux_mac_win.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 IPX driver would enlarge your kernel by about 5 kB. 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 ipx.o. If you want to compile it as a module, say M here
+  and read Documentation/modules.txt. Unless you want to integrate
   your Linux box with a local Novell network, say N.
 
-Full internal IPX network
+IPX: Full internal IPX network
 CONFIG_IPX_INTERN
   Every IPX network has an address that identifies it. Sometimes it is
   useful to give an IPX "network" address to your Linux box as well
   (for example if your box is acting as a fileserver for different IPX
-  networks: it will then be accessible form everywhere using the same
+  networks: it will then be accessible from everywhere using the same
   address).  The way this is done is to create a virtual internal
   "network" inside your box and to assign an IPX address to this
   network. Say Y here if you want to do this; read the IPX-HOWTO at
   sunsite.unc.edu:/pub/Linux/docs/howto for details.  
+
   The full internal IPX network enables you to allocate sockets on
   different virtual nodes of the internal network. This is done by
   evaluating the field sipx_node of the socket address given to the
@@ -1957,58 +2113,72 @@
   'special' sockets to sockets listening on the primary network is
   disabled. This might break existing applications, especially RIP/SAP
   daemons. A RIP/SAP daemon that works well with the full internal net
-  can be found on ftp.gwdg.de:/pub/linux/misc/ncpfs.  If you don't
+  can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs.  If you don't
   know what you are doing, say N.
 
-IPX Type 20 Routing
-CONFIG_IPX_PPROP_ROUTING
-  IPX Type 20 packets are special broadcast messages designed to work
-  across routers.  If you are using an internal network, have multiple
-  interfaces that route IPX, or will want to route IPX connections over
-  ppp to internal networks, setting this will allow the type 20 packets
-  to be propagated to all connected networks.  These packets are used by
-  Novell NETBIOS and the NETBIOS name functions of SMB protocols that
-  work over IPX (e.g. the "Network Neighborhood" on another popular OS
-  cum GUI).  In brief, if your Linux box needs to route IPX packets,
-  this should be set to Y.
+IPX: SPX networking (EXPERIMENTAL)
+CONFIG_SPX
+  The Sequenced Packet eXchange protocol is a transport layer protocol
+  built on top of IPX. It is used in Novell NetWare systems for
+  client-server applications and is similar to TCP (which runs on top
+  of IP).
+
+  Note that Novell NetWare file sharing does not use SPX; it uses a
+  protocol called NCP, for which separate Linux support is available
+  ("NCP filesystem support" below for the client side, and the user
+  space programs lwared or mars_nwe for the server side).
+
+  Say Y here if you have use for SPX; read the IPX-HOWTO at
+  sunsite.unc.edu:/pub/Linux/docs/howto for details.
+
+  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 af_spx.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Appletalk DDP
 CONFIG_ATALK
   Appletalk is the way Apple computers speak to each other on a
-  network. If your linux box is connected to such a network and you
+  network. If your Linux box is connected to such a network and you
   want to join the conversation, say Y. You will need to use the
   netatalk package so that your Linux box can act as a print and file
   server for macs as well as access appletalk printers. Check out
-  http://artoo.hitchcock.org/~flowerpt/projects/linux-netatalk/ on the
-  WWW 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). 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 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 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.
+  http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
+  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). 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 are fully supported by Linux.
+  The NET-2-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO contains valuable
+  information as well.
+
+  General information about how to connect Linux, Windows machines and
+  Macs is on the WWW at http://www.eats.com/linux_mac_win.html
+
+  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 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
   This allows IP networking for users who only have Appletalk
-  networking available.  This feature is experimental. With this
+  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
+  Linux box is stuck on an Appletalk only network) or decapsulate
+  (e.g. if you want your Linux box to act as an 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.
+  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.
 
 IP to Appletalk-IP Encapsulation support
 CONFIG_IPDDP_ENCAP
@@ -2064,9 +2234,10 @@
   (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.
+  ftp://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
@@ -2081,28 +2252,30 @@
   the Gracilis Packetwin or the generic Z8530 driver. Another option
   are the Baycom modem serial and parallel port hacks or the sound card
   modem (supported by their own drivers). If you say Y here, you also
-  have to say Y to one of those drivers. Information about where to
-  get supporting software for Linux amateur radio as well as
-  information about how to configure an AX.25 port is contained in the
-  AX25-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. You might also want to check
-  out the file Documentation/networking/ax25.txt in the kernel
+  have to say Y to one of those drivers. 
+
+  Information about where to get supporting software for Linux amateur
+  radio as well as information about how to configure an AX.25 port is
+  contained in the AX25-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You might also want to
+  check out the file Documentation/networking/ax25.txt in the kernel
   source. More information about digital amateur radio in general is
-  on the WWW at 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).  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 ax25.o. If you want to compile it as a module, say M here and
-  read Documentation/modules.txt.
+  on the WWW at 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).
+
+  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 ax25.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 AX.25 DAMA Slave support
 CONFIG_AX25_DAMA_SLAVE
   DAMA is a mechanism to prevent collisions when doing AX.25
   networking. A DAMA server (called "master") accepts incoming traffic
-  from clients (called "slaves") and redistributes it to other
-  slaves. If you say Y here, your Linux box will act as a DAMA slave;
-  this is transparent in that you don't have to do any special DAMA
+  from clients (called "slaves") and redistributes it to other slaves.
+  If you say Y here, your Linux box will act as a DAMA slave; this is
+  transparent in that you don't have to do any special DAMA
   configuration. (Linux cannot yet act as a DAMA server.) If unsure,
   say N.
 
@@ -2117,46 +2290,289 @@
 Amateur Radio NET/ROM
 CONFIG_NETROM
   NET/ROM is a network layer protocol on top of AX.25 useful for
-  routing.  A comprehensive listing of all the software for Linux
-  amateur radio users as well as information about how to configure an
-  AX.25 port is contained in the AX25-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. You also might
-  want to check out the file Documentation/networking/ax25.txt. More
+  routing.
+
+  A comprehensive listing of all the software for Linux amateur radio
+  users as well as information about how to configure an AX.25 port is
+  contained in the AX25-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You also might want to
+  check out the file Documentation/networking/ax25.txt. More
   information about digital amateur radio in general is on the WWW at
   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).  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 netrom.o. If you want
-  to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  like lynx or netscape).
 
-AX.25 over Ethernet
-CONFIG_BPQETHER
-  AX.25 is the protocol used for computer communication over amateur
-  radio. If you say Y here, you will be able to send and receive AX.25
-  traffic over Ethernet (also called "BPQ AX.25"), which could be
-  useful if some other computer on your local network has a direct
-  amateur radio connection.
+  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 netrom.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Amateur Radio X.25 PLP (Rose)
 CONFIG_ROSE
   The Packet Layer Protocol (PLP) is a way to route packets over X.25
   connections in general and amateur radio AX.25 connections in
-  particular, essentially an alternative to NET/ROM.  A comprehensive
-  listing of all the software for Linux amateur radio users as well as
-  information about how to configure an AX.25 port is contained in the
-  AX25-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. You also might want to check
+  particular, essentially an alternative to NET/ROM.
+
+  A comprehensive listing of all the software for Linux amateur radio
+  users as well as information about how to configure an AX.25 port is
+  contained in the AX25-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You also might want to check
   out the file Documentation/networking/ax25.txt. More information
   about digital amateur radio in general is on the WWW at
   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).  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 rose.o. If you want to
-  compile it as a module, say M here and read
-  Documentation/modules.txt.
+  like lynx or netscape).
+
+  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 rose.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
+Serial port KISS driver for AX.25
+CONFIG_MKISS
+  KISS is a protocol used to send IP traffic over AX.25 radio
+  connections, somewhat similar to SLIP for telephone lines. Say Y
+  here if you intend to send Internet traffic over amateur radio,
+  using some device connected to your machine's serial port. In that
+  case, you also have to say Y to "Amateur Radio AX.25 Level 2"
+  support.  
+
+  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 mkiss.o.
+
+Serial port 6PACK driver for AX.25
+CONFIG_6PACK
+  6pack is a transmission protocol for the data exchange between your
+  PC and your TNC (the Terminal Node Controller acts as a kind of
+  modem connecting your computer's serial port to your radio's
+  microphone input and speaker output). This protocol can be used as
+  an alternative to KISS for networking over AX.25 amateur radio
+  connections, but it has some extended functionality.
+
+  Note that this driver is still experimental and might cause
+  problems. For details about the features and the usage of the
+  driver, read Documentation/networking/6pack.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. The module will be
+  called 6pack.o.
+
+BPQ Ethernet driver
+CONFIG_BPQETHER
+  AX.25 is the protocol used for computer communication over amateur
+  radio. If you say Y here, you will be able to send and receive AX.25
+  traffic over Ethernet (also called "BPQ AX.25"), which could be
+  useful if some other computer on your local network has a direct
+  amateur radio connection.
+
+High-speed (DMA) SCC driver for AX.25
+CONFIG_DMASCC
+  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
+  ftp://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.
+
+Z8530 SCC driver for AX.25
+CONFIG_SCC
+  These cards are used to connect your Linux box to an amateur radio
+  in order to communicate with other computers.  If you want to use
+  this, read Documentation/networking/z8530drv.txt and the
+  AX.25-HOWTO, available via ftp (user: anonymous) at
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.  Also make sure to say Y to
+  "Amateur Radio AX.25 Level 2" support. 
+
+  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 scc.o.
+
+additional delay for PA0HZP OptoSCC compatible boards
+CONFIG_SCC_DELAY
+  Say Y here if you experience problems with the SCC driver not
+  working properly; please read Documentation/networking/z8530drv.txt
+  for details. If unsure, say N.
+
+#support for TRX that feedback the tx signal to rx
+#CONFIG_SCC_TRXECHO
+###
+### Don't know what's going on here.
+###
+#
+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 (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_par.o.
+
+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
+  baudrate to be set between 300 and 4800 baud (however not all modems
+  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 (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.
+
+Sound card modem driver for AX.25
+CONFIG_SOUNDMODEM
+  This experimental driver allows a standard SoundBlaster or
+  WindowsSoundSystem compatible sound card to be used as a packet radio
+  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 Documentation/modules.txt. This is recommended.
+  The module will be called soundmodem.o.
+
+Sound card modem support for SoundBlaster and compatible cards
+CONFIG_SOUNDMODEM_SBC
+  This option enables the soundmodem driver to use SoundBlaster and
+  compatible cards. If you have a dual mode card (i.e. a WSS cards
+  with a SoundBlaster emulation) you should say N here and Y to
+  "Sound card modem support for WSS and Crystal cards", below, because
+  this usually results in better performance. This option also supports
+  SB16/32/64 in full duplex mode.
+
+Sound card modem support for WSS and Crystal cards
+CONFIG_SOUNDMODEM_WSS
+  This option enables the soundmodem 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). This option also supports
+  the WSS full duplex operation which currently works with Crystal
+  CS423x chips. If you don't need full duplex operation, do not enable
+  it to save performance.
+
+Sound card modem support for 1200 baud AFSK modulation
+CONFIG_SOUNDMODEM_AFSK1200
+  This option enables the soundmodem driver 1200 baud AFSK modem, 
+  compatible to popular modems using TCM3105 or AM7911. The demodulator
+  requires about 12% of the CPU power of a Pentium 75 CPU per channel.
+
+Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
+CONFIG_SOUNDMODEM_AFSK2400_7
+  This option enables the soundmodem driver 2400 baud AFSK modem,
+  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
+  crystal.  Note that the availability of this driver does _not_ imply
+  that I recommend building such links. It is only here since users
+  especially in eastern Europe have asked me to do so. In fact this
+  modulation scheme has many disadvantages, mainly its incompatibility
+  with many transceiver designs and the fact that the TCM3105 (if
+  used) is operated widely outside its specifications.
+
+Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
+CONFIG_SOUNDMODEM_AFSK2400_8
+  This option enables the soundmodem driver 2400 baud AFSK modem,
+  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
+  Note that the availability of this driver does _not_ imply that I
+  recommend building such links. It is only here since users
+  especially in eastern Europe have asked me to do so. In fact this
+  modulation scheme has many disadvantages, mainly its incompatibility
+  with many transceiver designs and the fact that the TCM3105 (if
+  used) is operated widely outside its specifications.
+
+Sound card modem support for 2666 baud AFSK modulation
+CONFIG_SOUNDMODEM_AFSK2666
+  This option enables the soundmodem driver 2666 baud AFSK modem.
+  This modem is experimental, and not compatible to anything
+  else I know of.
+
+Sound card modem support for 4800 baud 8PSK modulation
+CONFIG_SOUNDMODEM_PSK4800
+  This option enables the soundmodem driver 4800 baud 8PSK modem.
+  This modem is experimental, and not compatible to anything
+  else I know of.
+
+Sound card modem support for 4800 baud HAPN-1 modulation
+CONFIG_SOUNDMODEM_HAPN4800
+  This option enables the soundmodem driver 4800 baud HAPN-1
+  compatible modem. This modulation seems to be widely used 'down
+  under' and in the Netherlands. Here, nobody uses it, so I could not
+  test if it works.  It is compatible to itself, however :-)
+
+Sound card modem support for 9600 baud FSK G3RUH modulation
+CONFIG_SOUNDMODEM_FSK9600
+  This option enables the soundmodem driver 9600 baud FSK modem,
+  compatible to the G3RUH standard. The demodulator requires about 4%
+  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
+  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
+  can only use one protocol at a time, depending on what the other end
+  can understand).
 
 CCITT X.25 Packet Layer
 CONFIG_X25
@@ -2169,25 +2585,28 @@
   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
+  (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
+  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
-  (not yet supported by Linux) or one can do X.25 over a standard
-  telephone line using an ordinary modem (say Y to "X.25 async driver"
-  below) or over Ethernet using an ordinary Ethernet card and either
-  the 802.2 LLC protocol (say Y to "802.2 LLC" below) or LAPB over
-  Ethernet (say Y to "LAPB Data Link Driver" and "LAPB over Ethernet
-  driver" 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 x25.o. If
-  unsure, say N.
+  Documentation/networking/x25-iface.txt. 
+
+  One connects to an X.25 network either with a dedicated network card
+  using the X.21 protocol (not yet supported by Linux) or one can do
+  X.25 over a standard telephone line using an ordinary modem (say Y
+  to "X.25 async driver" below) or over Ethernet using an ordinary
+  Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
+  LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
+  and "LAPB over Ethernet driver" 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 x25.o. If unsure, say N.
 
 LAPB Data Link Driver (EXPERIMENTAL) 
 CONFIG_LAPB
@@ -2200,11 +2619,12 @@
   Linux currently supports LAPB only over Ethernet connections. If you
   want to use LAPB connections over Ethernet, say Y here and to "LAPB
   over Ethernet driver" below.  Read
-  Documentation/networking/lapb-module.txt for technical details.  If
-  you want to compile this driver as a module though ( = code which
+  Documentation/networking/lapb-module.txt for technical details.  
+
+  If you want to compile this driver as a module though ( = 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 lapb.o.  If unsure, say N.
+  will be called lapb.o. If unsure, say N.
 
 802.2 LLC (VERY EXPERIMENTAL)
 CONFIG_LLC
@@ -2219,15 +2639,17 @@
   Several such bridges can work together to create even larger
   networks of Ethernets using the IEEE802.1 spanning tree 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 in /pub/Linux. Please read the Bridge
-  mini-HOWTO for more information. 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 Ethernet-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. The
-  Bridging code is still in test. If unsure, say N.
+  other third party bridge products. 
+
+  In order to use this, you'll need the bridge configuration tools
+  available via ftp (user: anonymous) from
+  ftp://shadow.cabi.net/pub/Linux. Please read the Bridge mini-HOWTO
+  for more information. 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 Ethernet-HOWTO, available via ftp (user: anonymous)
+  in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. The Bridging code is
+  still in test. If unsure, say N.
 
 Packet socket
 CONFIG_PACKET
@@ -2260,8 +2682,9 @@
 CONFIG_RTNETLINK
   If you say Y here and create a character special file /dev/route
   with major number 36 and minor number 0 using mknod ("man mknod"),
-  you can read some network related routing information from that
-  file. Everything you write to that file will be discarded.
+  you (or some user space utility) 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
@@ -2277,11 +2700,12 @@
   it. You also need to say Y here if you want support for the parallel
   port version of the 100MB IOMEGA ZIP drive. Please read the
   SCSI-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 scsi_mod.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt and
+  ftp://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 scsi_mod.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt and
   Documentation/scsi.txt. However, do not compile this as a module if
   your root filesystem (the one containing the directory /) is located
   on a SCSI device.
@@ -2291,38 +2715,44 @@
   If you want to use a SCSI hard disk or the SCSI or parallel port
   version of the IOMEGA ZIP drive under Linux, say Y and read the
   SCSI-HOWTO and the Disk-HOWTO, both available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. This is NOT for
-  SCSI 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 sd_mod.o. If you want
-  to compile it as a module, say M here and read
-  Documentation/modules.txt and Documentation/scsi.txt. Do not compile
-  this driver as a module if 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.
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. This is
+  NOT for SCSI 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 sd_mod.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt and
+  Documentation/scsi.txt. Do not compile this driver as a module if
+  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
   SCSI-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO and drivers/scsi/README.st in
-  the kernel source. This is NOT for SCSI 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 st.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt and Documentation/scsi.txt .
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and
+  drivers/scsi/README.st in the kernel source. This is NOT for SCSI
+  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 st.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt and
+  Documentation/scsi.txt .
 
 SCSI CDROM support
 CONFIG_BLK_DEV_SR
   If you want to use a SCSI CDROM under Linux, say Y and read the
   SCSI-HOWTO and the CDROM-HOWTO from
   sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also make sure to say Y to
-  "ISO9660 cdrom filesystem support" later. 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 sr_mod.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt and Documentation/scsi.txt .
+  "ISO9660 cdrom filesystem support" later. 
+
+  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 sr_mod.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt and
+  Documentation/scsi.txt .
 
 Enable vendor-specific extensions (for SCSI CDROM)
 CONFIG_BLK_DEV_SR_VENDOR
@@ -2339,15 +2769,17 @@
   directly, so you need some additional software which knows how to
   talk to these devices using the SCSI protocol. For CD-writers, you
   would need the program cdwrite, available via ftp (user: anonymous)
-  from sunsite.unc.edu:/pub/Linux/utils/disk-management; for other
+  from ftp://sunsite.unc.edu/pub/Linux/utils/disk-management; for other
   devices, it's possible that you'll have to write the driver software
   yourself, so have a look at the SCSI-HOWTO and at the
   SCSI-Programming-HOWTO, both available via ftp (user: anonymous) in
-  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 and Documentation/scsi.txt. The module
-  will be called sg.o. If unsure, say N.
+  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 and
+  Documentation/scsi.txt. The module will be called sg.o. If unsure,
+  say N.
 
 Probe all LUNs on each SCSI device
 CONFIG_SCSI_MULTI_LUN
@@ -2370,45 +2802,51 @@
   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' (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.
+  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
   This is a driver for all SCSI host adapters manufactured by
   AdvanSys. It is documented in the kernel source in
-  drivers/scsi/advansys.c. 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 want to compile it as a module, say M
-  here and read Documentation/modules.txt. The module will be called
-  advansys.o.
+  drivers/scsi/advansys.c. 
+
+  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 want to compile it as a module, say M here and read
+  Documentation/modules.txt. The module will be called advansys.o.
 
 Adaptec AHA152X/2825 support
 CONFIG_SCSI_AHA152X
   This is support for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
   SCSI host adapters. It is explained in section 3.3 of the
   SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. You might also want to read
-  the comments at the top of drivers/scsi/aha152x.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 aha152x.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You might also want to
+  read the comments at the top of drivers/scsi/aha152x.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 aha152x.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Adaptec AHA1542 support
 CONFIG_SCSI_AHA1542
   This is support for a SCSI host adapter. It is explained in section
   3.4 of the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  Note that Trantor was
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.  Note that Trantor was
   recently purchased by Adaptec, and some former Trantor products are
   being sold under the Adaptec name. If it doesn't work out of the
   box, you may have to change some settings in drivers/scsi/aha1542.h.
+  
   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
@@ -2418,86 +2856,111 @@
 CONFIG_SCSI_AHA1740
   This is support for a SCSI host adapter. It is explained in section
   3.5 of the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  If it doesn't work out of
-  the box, you may have to change some settings in
-  drivers/scsi/aha1740.h. 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 aha17400.o. If you
-  want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
+  drivers/scsi/aha1740.h.
+
+  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 aha17400.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Adaptec AIC7xxx chipset SCSI controller support
 CONFIG_SCSI_AIC7XXX
-  This is support for the various aic7xxx based Adaptec SCSI controllers.
-  These include the 274x EISA cards, 284x VLB cards, 294x PCI cards,
-  394x PCI cards, 3985 PCI card, and several versions of the Adaptec
-  built-in SCSI controllers on various PC motherboards.  Information on
-  the configuration options for this controller can be found by checking
-  the README.aic7xxx file, usually in /usr/src/linux/drivers/scsi.
+  This is support for the various aic7xxx based Adaptec SCSI
+  controllers. These include the 274x EISA cards, 284x VLB cards, 294x
+  PCI cards, 394x PCI cards, 3985 PCI card, and several versions of
+  the Adaptec built-in SCSI controllers on various PC motherboards.
+  Information on the configuration options for this controller can be
+  found by checking the help file for each of the available
+  configuration options. You also want to read
+  drivers/scsi/README.aic7xxx and the SCSI-HOWTO, available via ftp
+  (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note
+  that the AHA2920 SCSI host adapter is *not* supported by this
+  driver; choose "Future Domain 16xx SCSI support" instead if you have
+  one of those. 
+
+  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 aic7xxx.o.
 
 Override driver defaults for commands per LUN
 CONFIG_OVERRIDE_CMDS
-  Use this option to allow you to override the default maximum number of
-  commands that a single device on the aic7xxx controller is allowed to have
-  active at one time.  This option only effects tagged queueing capable
-  devices.  The driver uses a "failsafe" value of 8 by default.  This is
-  much lower than many devices can handle, but left in place for safety sake.
-  NOTE: This does not actually enabled tagged queueing on any particular
-  device.  The driver has changed in this respect.  Please see the file
-  README.aic7xxx in /usr/src/linux/drivers/scsi for more information on how
+  Say Y here if you want to override the default maximum number of
+  commands that a single device on the aic7xxx controller is allowed
+  to have active at one time. This option only effects tagged queueing
+  capable devices. The driver uses a "failsafe" value of 8 by default.
+  This is much lower than many devices can handle, but left in place
+  for safety's sake. If you say Y here, you can adjust the number of
+  commands per LUN with the following configuration option.
+  
+  NOTE: This does not actually enable tagged queueing on any
+  particular device. The driver has changed in this respect. Please
+  see the file drivers/scsi/README.aic7xxx for more information on how
   to get particular devices to use tagged command queueing.
-  Default: N
+  
+  If unsure, say N.
 
 Maximum number of commands per LUN
 CONFIG_AIC7XXX_CMDS_PER_LUN
-  Specify the maximum number of commands per lun you would like to allocate
-  per device.  Reasonable figures are in the range of 14 to 32 commands per
-  device, but depending on hardware could be increased or decreased from
-  that figure.  If the number is too high for any particular device, the
-  driver will automatically compensate usually after only 10 minutes of
-  uptime and will issue a message to alert you to the fact that the number
-  of commands for that device has been reduced.  It will not hinder
-  performance if a portion of your devices eventually have their commands
-  per lun reduced, but is a waste of memory if all of your devices end
-  up reducing this number down to a more reasonable figure.  Default: 24
+  Specify the maximum number of commands you would like to allocate
+  per LUN (a LUN is a Logical Unit Number - some physical SCSI devices,
+  e.g. CD jukeboxes, act logically as several separate units, each of
+  which gets its own number).  
+
+  Reasonable figures are in the range of 14 to 32 commands per device,
+  but depending on hardware could be increased or decreased from that
+  figure. If the number is too high for any particular device, the
+  driver will automatically compensate usually after only 10 minutes
+  of uptime and will issue a message to alert you to the fact that the
+  number of commands for that device has been reduced. It will not
+  hinder performance if some of your devices eventually have their
+  commands per LUN reduced, but is a waste of memory if all of your
+  devices end up reducing this number down to a more reasonable
+  figure. Default: 24
 
 Collect statistics to report in /proc
 CONFIG_AIC7XXX_PROC_STATS
-  This option tells the driver to keep track of how many commands have been
-  sent to each particular device and report that information to the user
-  via the /proc/scsi/aic7xxx/x file, where x is the number of the aic7xxx
-  controller you want the information on.  This adds a small amount of
-  overhead to each and every SCSI command the aic7xxx driver handles, so if
-  you aren't really interested in this information, it is best to leave it
-  disabled.  Default: N
+  This option tells the driver to keep track of how many commands have
+  been sent to each particular device and report that information to
+  the user via the /proc/scsi/aic7xxx/n file, where n is the number of
+  the aic7xxx controller you want the information on. This adds a
+  small amount of overhead to each and every SCSI command the aic7xxx
+  driver handles, so if you aren't really interested in this
+  information, it is best to leave it disabled. This will only work if
+  you also say Y to "/proc filesystem support", below. If unsure, say N.
 
 Delay in seconds after SCSI bus reset
 CONFIG_AIC7XXX_RESET_DELAY
-  This sets how long the driver will wait after resetting the SCSI bus before
-  attempting to communicate with the devices on the SCSI bus again.  This
-  delay will be used during the reset phase at bootup time as well as after
-  any reset that might occur during normal operation.  Reasonable numbers
-  range anywhere from 5 to 15 seconds depending on your devices.  DAT tape
-  drives are notorious for needing more time after a bus reset to be
-  ready for the next command, but most hard drives and CD-ROM devices are
-  ready in only a few seconds.  This option has a maximum upper limit of
-  20 seconds to avoid bad interactions between the aic7xxx driver and the
-  rest of the linux kernel.  The default value has been reduced.  If this
-  doesn't work with your hardware, try increasing this value.  Default: 5
+  This sets how long the driver will wait after resetting the SCSI bus
+  before attempting to communicate with the devices on the SCSI bus
+  again. This delay will be used during the reset phase at bootup time
+  as well as after any reset that might occur during normal operation.
+  Reasonable numbers range anywhere from 5 to 15 seconds depending on
+  your devices. DAT tape drives are notorious for needing more time
+  after a bus reset to be ready for the next command, but most hard
+  drives and CD-ROM devices are ready in only a few seconds. This
+  option has a maximum upper limit of 20 seconds to avoid bad
+  interactions between the aic7xxx driver and the rest of the linux
+  kernel. The default value has been reduced to 5 seconds. If this
+  doesn't work with your hardware, try increasing this value.
 
 BusLogic SCSI support
 CONFIG_SCSI_BUSLOGIC
   This is support for BusLogic MultiMaster and FlashPoint SCSI Host
   Adapters.  Consult the SCSI-HOWTO, available via anonymous ftp from
-  sunsite.unc.edu in /pub/Linux/docs/HOWTO, and the files
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, and the files
   README.BusLogic and README.FlashPoint in drivers/scsi for more
   information.  If this driver does not work correctly without
   modification, please contact the author, Leonard N. Zubkoff, by
-  email to lnz@dandelion.com.  You can also build this driver as a
-  module ( = code which can be inserted in and removed from the
-  running kernel whenever you want), but only a single instance may be
-  loaded.  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt. The module will be called BusLogic.o.
+  email to lnz@dandelion.com.  
+
+  You can also build this driver as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  but only a single instance may be loaded. If you want to compile it
+  as a module, say M here and read Documentation/modules.txt. The
+  module will be called BusLogic.o.
 
 Omit BusLogic SCSI FlashPoint support
 CONFIG_SCSI_OMIT_FLASHPOINT
@@ -2506,17 +2969,17 @@
   substantial, so users of MultiMaster Host Adapters may wish to omit
   it.
 
-
 DTC3180/3280 SCSI support
 CONFIG_SCSI_DTC3280
   This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
   the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO and the file
-  drivers/scsi/README.dtc3x80.  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 dtc.o. If you
-  want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and the file
+  drivers/scsi/README.dtc3x80.  
+
+  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 dtc.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 EATA-DMA (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
 CONFIG_SCSI_EATA_DMA
@@ -2526,11 +2989,12 @@
   also another driver for the same hardware: "EATA ISA/EISA/PCI
   support". You should only say Y to one of them. 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 (= code which can be inserted in and removed
-  from the running kernel whenever you want). The module will be
-  called eata_dma.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt.
+  ftp://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 eata_dma.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 EATA-PIO (old DPT PM2001, PM2012A) support
 CONFIG_SCSI_EATA_PIO
@@ -2540,10 +3004,12 @@
   doing so, since this driver only supports hard disks and lacks
   numerous features.  You might want to have a look at the SCSI-HOWTO,
   available via ftp (user: anonymous) at
-  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. The module will be called eata_pio.o.
+  ftp://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. The module will be
+  called eata_pio.o.
 
 UltraStor 14F/34F support
 CONFIG_SCSI_U14_34F
@@ -2552,13 +3018,15 @@
   this hardware. If the driver doesn't work out of the box, you may
   have to change some settings in drivers/scsi/u14-34f.c.  Read the
   SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that there is also
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that there is also
   another driver for the same hardware: "UltraStor SCSI support",
   below.  You should say Y to both only if you want 24F support 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 u14-34f.o. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt.
+  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 u14-34f.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 enable elevator sorting
 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
@@ -2580,10 +3048,11 @@
   other adapters based on the Future Domain chipsets (Quantum
   ISA-200S, ISA-250MG; Adaptec AHA-2920; and at least one IBM board).
   It is explained in section 3.7 of the SCSI-HOWTO, available via ftp
-  (user: anonymous) at 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 fdomain.o. If you want to compile it as a
+  (user: anonymous) at ftp://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 fdomain.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Generic NCR5380/53c400 SCSI support
@@ -2591,13 +3060,14 @@
   This is the generic NCR family of SCSI controllers, not to be
   confused with the NCR 53c7 or 8xx controllers. It is explained in
   section 3.8 of the SCSI-HOWTO, available via ftp (user: anonymous)
-  at sunsite.unc.edu:/pub/Linux/docs/HOWTO.  If it doesn't work out of
-  the box, you may have to change some settings in
-  drivers/scsi/g_NCR5380.h. 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 g_NCR5380.o. If
-  you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work
+  out of the box, you may have to change some settings in
+  drivers/scsi/g_NCR5380.h.
+
+  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 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
@@ -2619,13 +3089,14 @@
   This is the 53c7 and 8xx NCR family of SCSI controllers, not to be
   confused with the NCR 5380 controllers. It is explained in section
   3.8 of the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
-  box, you may have to change some settings in
-  drivers/scsi/53c7,8xx.h. 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 53c7,8xx.o. If you
-  want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
+  drivers/scsi/53c7,8xx.h.
+
+  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 53c7,8xx.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 always negotiate synchronous transfers
 CONFIG_SCSI_NCR53C7xx_sync
@@ -2653,7 +3124,7 @@
 
 NCR53C8XX SCSI support
 CONFIG_SCSI_NCR53C8XX
-  This is the BSD ncr driver adapted to linux for the NCR53C8XX family
+  This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
   of PCI-SCSI controllers. This driver supports parity checking,
   tagged command queuing, Fast-20 data transfer up to 20 MB/s with
   narrow SCSI devices and 40 MB/s with wide SCSI devices.
@@ -2664,21 +3135,26 @@
 CONFIG_SCSI_NCR53C8XX_SYNC
   SCSI-2 specifications allow SCSI devices to negotiate a synchronous 
   transfer period of 25 nano-seconds or more.
+
   The transfer period value is 4 times the agreed transfer period.
   So, data can be transferred at a 10 MHz frequency, allowing 10
   MB/second throughput with 8 bits SCSI-2 devices and 20 MB/second
   with wide16 devices.  This frequency can be used safely with
   differential devices but may cause problems with single-ended
   devices.
+
   Specify 0 if you want to only use asynchronous data transfers.
   Otherwise, specify a value between 5 and 10.  Commercial O/Ses
   generally use 5 Mhz frequency for synchronous transfers.  It is a
   reasonable default value.
+
   However, a flawless single-ended SCSI bus supports 10 MHz data
   transfers.  Regardless of the value chosen in the Linux
   configuration, the synchronous period can be changed after boot-up
   through the /proc/scsi file system. The generic command is:
+
       echo "setsync #target period" >/proc/scsi/ncr53c8xx/0
+
   Use a 25 ns period for 10 Mhz synchronous data transfers.
   If you don't know what to do now, go with the default.
 
@@ -2722,15 +3198,19 @@
 enable tagged command queuing
 CONFIG_SCSI_NCR53C8XX_TAGGED_QUEUE
   This option allows you to enable tagged command queuing support at
-  linux start-up.  Some SCSI devices do not properly support this
+  Linux start-up.  Some SCSI devices do not properly support this
   feature.  The suggested method is to say N here and to use the
   "settags" control command after boot-up to enable this feature:
+
       echo "settags 2 4" >/proc/scsi/ncr53c8xx/0
+
   asks the driver to use up to 4 concurrent tagged commands for target
   2 of controller 0.
+
   See the file drivers/scsi/README.ncr53c8xx for more information.
   WARNING! If you say Y here, then you have to say N to "not allow
   targets to disconnect", above.
+
   The safe answer therefore is N.
   The normal answer therefore is Y.
 
@@ -2749,6 +3229,7 @@
   features.  Genuine SYMBIOS boards use GPIO0 in output for controller
   LED and GPIO3 bit as a flag indicating single-ended/differential
   interface.
+
   If all the boards of your system are genuine SYMBIOS boards or use
   BIOS and drivers from SYMBIOS, you would want to enable this option.
   The driver behaves correctly on my system with this option enabled.
@@ -2756,11 +3237,13 @@
   0x12).  This option must be set to N if your system has at least one
   53C8XX based SCSI board with a vendor-specific BIOS (example: Tekram
   DC-390/U/W/F). 
+
   However, if all your non Symbios compatible boards have NVRAM,
   setting option "detect and read serial NVRAMs"
   (CONFIG_SCSI_NCR53C8XX_NVRAM_DETECT) above allows the driver to
   distinguish Symbios compatible boards from other ones.  So, you can
   answer Y if all non Symbios compatible boards have NVRAM.
+
   If unsure, say N.
 
 IBMMCA SCSI support
@@ -2768,6 +3251,7 @@
   This is support for the IBM SCSI adapter found in many of the PS/2
   series computers. These machines have an MCA bus, so you need to say
   Y to "MCA support" as well and read Documentation/mca.txt.
+
   If the adapter isn't found during boot (a common problem for models
   56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
   option, where <pun> is the id of the SCSI subsystem (usually 7, but
@@ -2778,7 +3262,8 @@
   bootparam" or see the documentation of your boot loader about how to
   pass options to the kernel. The lilo procedure is also explained in
   the SCSI-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
   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
@@ -2801,12 +3286,14 @@
   original definition of the SCSI-standard as also industrial- and
   process-control-machines, like VME-CPUs running under realtime-OSs
   (e.g. LynxOS, OS9) do.
+
   If you like to run Linux on your MCA-machine with the same assignment
   of hard disks as seen from e.g. DOS or OS/2 on your machine, which
   is in addition conformant to the SCSI-standard, you must say Y here.
   This is also necessary for MCA-Linux-users who want to keep downward-
   compatibility to older releases of the IBM-MCA-SCSI-driver (older than
   driver-release 2.00 and older than June 1997).
+
   If you like to have the lowest SCSI-id assigned as drive C:, as
   modern SCSI-BIOSes do, which does not conform to the standard, but
   is widespread and common in the PC-world of today, you must say N
@@ -2830,39 +3317,44 @@
   This is support for an ISA bus SCSI host adapter. You'll find more
   information in drivers/scsi/in2000.readme. If it doesn't work out of
   the box, you may have to change the jumpers for IRQ or address
-  selection. 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 in2000.o.
+  selection. 
+
+  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 in2000.o.
 
 PAS16 SCSI support
 CONFIG_SCSI_PAS16
   This is support for a SCSI host adapter. It is explained in section
   3.10 of the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
-  box, you may have to change some settings in drivers/scsi/pas16.h.
-  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
-  pas16.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
+  drivers/scsi/pas16.h.
+  
+  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 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.
+  (user: anonymous) at ftp://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
+  (user: anonymous) at ftp://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.
@@ -2871,11 +3363,12 @@
 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.
+  (user: anonymous) at ftp://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
@@ -2886,11 +3379,12 @@
   the Qlogic ISP driver though.  Information about this driver is
   contained in drivers/scsi/README.qlogicfas.  You should also 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 ( = code which can be inserted in and removed from the
-  running kernel whenever you want). The module will be called
-  qlogicfas.o. If you want to compile it as a module, say M here and
-  read Documentation/modules.txt.
+  ftp://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 qlogicfas.o. If you want to compile it as
+  a module, say M here and read Documentation/modules.txt.
 
 Qlogic ISP SCSI support (EXPERIMENTAL)
 CONFIG_SCSI_QLOGIC_ISP
@@ -2901,55 +3395,63 @@
   information is contained in the file
   drivers/scsi/README.qlogicisp. You should also 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 ( = code which can be inserted in and removed from the
-  running kernel whenever you want). The module will be called
-  qlogicisp.o. If you want to compile it as a module, say M here and
-  read Documentation/modules.txt.
+  ftp://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 qlogicisp.o. If you want to compile it as
+  a module, say M here and read Documentation/modules.txt.
 
 Seagate ST-02 and Future Domain TMC-8xx SCSI support
 CONFIG_SCSI_SEAGATE
   These are 8-bit SCSI controllers; the ST-01 is also supported by
-  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
+  this driver. It is explained in section 3.9 of the SCSI-HOWTO,
   available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
-  box, you may have to change some settings in drivers/scsi/seagate.h.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
+  drivers/scsi/seagate.h.
+
   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 seagate.o. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt.
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called seagate.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Trantor T128/T128F/T228 SCSI support
 CONFIG_SCSI_T128
   This is support for a SCSI host adapter. It is explained in section
   3.11 of the SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  If it doesn't work out of
-  the box, you may have to change some settings in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
   drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
-  some former Trantor products are being sold under the Adaptec
-  name. 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 t128.o. If you want to compile it
-  as a module, say M here and read Documentation/modules.txt.
+  some former Trantor products are being sold under the Adaptec name.
+
+  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 t128.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 UltraStor SCSI support
 CONFIG_SCSI_ULTRASTOR
   This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
   adapter family. This driver is explained in section 3.12 of the
   SCSI-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
-  box, you may have to change some settings in
-  drivers/scsi/ultrastor.h. 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 ultrastor.o.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
+  of the box, you may have to change some settings in
+  drivers/scsi/ultrastor.h.
+  
   Note that there is also another driver for the same hardware:
   "UltraStor 14F/34F support", above.
 
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called ultrastor.o. 
+
 7000FASST SCSI support
 CONFIG_SCSI_7000FASST
   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
@@ -2961,15 +3463,17 @@
   and does not need any BIOS32 service.  DPT ISA and all EISA i/o
   addresses are probed looking for the "EATA" signature. If you said Y
   to "PCI bios support", the addresses of all the PCI SCSI controllers
-  reported by BIOS32 are probed as well.  Note that there is also
-  another driver for the same hardware available: "EATA-DMA
-  support". You should say Y to only one of them.  You want to read
+  reported by BIOS32 are probed as well.  You want to read
   the start of drivers/scsi/eata.c and the SCSI-HOWTO, available via
-  ftp (user: anonymous) at 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. The module will be called
-  eata.o.
+  ftp (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.  
+
+  Note that there is also another driver for the same hardware
+  available: "EATA-DMA support". You should say Y to only one of them.
+
+  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 eata.o.
 
 enable tagged command queuing
 CONFIG_SCSI_EATA_TAGGED_QUEUE
@@ -2997,11 +3501,12 @@
   This is support for the NCR53c406a SCSI host adapter. For user
   configurable parameters, check out drivers/scsi/NCR53c406.c in the
   kernel source. Also read the SCSI-HOWTO, available via ftp (user:
-  anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO.  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
-  NCR53c406.o.
+  anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.  
+
+  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 NCR53c406.o.
 
 Tekram DC390(T) (AMD PCscsi) SCSI support
 CONFIG_SCSI_DC390T
@@ -3009,6 +3514,7 @@
   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 "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
@@ -3019,37 +3525,44 @@
   This is support for the AM53/79C974 SCSI host adapters. Please read
   drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
   available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO, is for you. 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
-  AM53C974.o.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, is for you. 
+
+  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 AM53C974.o.
 
 GDT SCSI Disk Array Controller support
 CONFIG_SCSI_GDTH
   This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI) 
   manufactured by ICP vortex. It is documented in the kernel source in
-  drivers/scsi/gdth.c and drivers/scsi/gdth.h. 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 want to compile 
-  it as a module, say M here and read Documentation/modules.txt. 	
+  drivers/scsi/gdth.c and drivers/scsi/gdth.h. 
+
+  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 want to compile it as a module, say M here and read
+  Documentation/modules.txt.
 
 IOMEGA Parallel Port ZIP drive SCSI support
 CONFIG_SCSI_PPA
   This driver supports the parallel port version of IOMEGA's ZIP drive
-  (a 100Mb removable media device).  For more information about this
+  (a 100Mb removable media device). For more information about this
   driver and how to use it you should read the file
-  drivers/scsi/README.ppa.  You should also read the SCSI-HOWTO, which
-  is available via anonymous ftp from sunsite.unc.edu in the directory
-  /pub/Linux/docs/HOWTO. If you use this driver, you will still be
-  able to use the parallel port for other tasks, such as a printer; it
-  is safe to compile both drivers into the kernel. This driver is also
-  available as a module which can be inserted in and removed from the
-  running kernel whenever you want. To compile this driver as a
-  module, say M here and read Documentation/modules.txt. The module
-  will be called ppa.o. Note that you can say N here if you have the
-  SCSI version of the ZIP drive: it will be supported automatically if
-  you said Y to the generic "SCSI disk support", above.
+  drivers/scsi/README.ppa. You should also read the SCSI-HOWTO, which
+  is available via ftp (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
+  you will still be able to use the parallel port for other tasks,
+  such as a printer; it is safe to compile both drivers into the
+  kernel.
+
+  Note that you can say N here if you have the SCSI version of the ZIP
+  drive: it will be supported automatically if you said Y to the
+  generic "SCSI disk support", above.
+
+  This driver is also available as a module which can be inserted in
+  and removed from the running kernel whenever you want. To compile
+  this driver as a module, say M here and read
+  Documentation/modules.txt. The module will be called ppa.o. 
 
 EPP FIFO Checking
 CONFIG_SCSI_PPA_HAVE_PEDANTIC
@@ -3065,30 +3578,32 @@
 
 SCSI Debug host simulator.
 CONFIG_SCSI_DEBUG
-  This is a host adapter simulator that can be programmed to simulate a
-  large number of conditions that could occur on a real bus.  The advantage
-  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. If unsure, say N.
+  This is a host adapter simulator that can be programmed to simulate
+  a large number of conditions that could occur on a real bus. The
+  advantage 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. If unsure, say N.
 
 Network device support?
 CONFIG_NETDEVICES
   You can say N here if you don't intend to connect to any other
-  computer at all or if all your connections will be either via UUCP
-  (UUCP is a protocol to forward mail and news between unix hosts over
-  telephone lines; read the UUCP-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO) or dialing up a
-  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
+  computer at all or if all your connections will be over a telephone
+  line with a modem either via UUCP (UUCP is a protocol to forward
+  mail and news between unix hosts over telephone lines; read the
+  UUCP-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO) or dialing up a 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 (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 (especially if you plan to use more than one
-  network card under linux), available from
+  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 (especially if you
+  plan to use more than one network card under Linux), 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
@@ -3096,28 +3611,31 @@
   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 and free book "Network Administrator's Guide", to be found
-  in sunsite.unc.edu:/pub/Linux/docs/LDP. If unsure, say Y.
+  Internet traffic over radio links).
+
+  Make sure to read the NET-2-HOWTO. Eventually, you will have to read
+  Olaf Kirch's excellent and free book "Network Administrator's
+  Guide", to be found in sunsite.unc.edu:/pub/Linux/docs/LDP. If
+  unsure, say Y.
 
 Dummy net driver support
 CONFIG_DUMMY
   This is essentially a bit-bucket device (i.e. traffic you send to
   this device is consigned into oblivion) with a configurable IP
   address. It is most commonly used in order to make your currently
-  inactive SLIP address seem like a real address for local
-  programs. If you use SLIP or PPP, you might want to say Y here. Read
-  about it in the Network Administrator's Guide, available via ftp
-  (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/LDP. Since
-  this thing often comes in handy, the default is Y. It won't enlarge
-  your kernel either. What a deal.  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 dummy.o. If you
-  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.
+  inactive SLIP address seem like a real address for local programs.
+  If you use SLIP or PPP, you might want to say Y here. Read about it
+  in the Network Administrator's Guide, available via ftp (user:
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/LDP. Since this
+  thing often comes in handy, the default is Y. It won't enlarge your
+  kernel either. What a deal.
+
+  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 dummy.o. If you 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
@@ -3125,27 +3643,30 @@
   connect to your Internet service provider or to connect to some
   other local Unix box or if you want to configure your Linux box as a
   Slip/CSlip server for other people to dial in.  SLIP (Serial Line
-  Internet Protocol) is the protocol used to send Internet traffic
+  Internet Protocol) is a protocol used to send Internet traffic
   over telephone lines or serial cables (also known as
-  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
-  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
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO, explains how to configure
-  SLIP. Note that you don't need this option if you just want to run
-  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
+  nullmodems); nowadays, the protocol PPP is more common than SLIP. 
+
+  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
+  ftp://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
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, explains how to
+  configure SLIP. Note that you don't need this option if you just
+  want to run 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 (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
+  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.
 
@@ -3156,12 +3677,12 @@
   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/)
-  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
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO, explains how to configure
-  CSLIP. This won't enlarge your kernel.
+  anonymous) from
+  ftp://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 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO,
+  explains how to configure CSLIP. This won't enlarge your kernel.
 
 Keepalive and linefill
 CONFIG_SLIP_SMART
@@ -3179,43 +3700,37 @@
   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.
 
-Wireless LAN (non-hamradio)
-CONFIG_NET_RADIO
-  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
   PPP (Point to Point Protocol) is a newer and better SLIP. It serves
   the same purpose: sending Internet traffic over telephone (and other
-  serial) lines.  Ask your access provider if they support it, because
+  serial) lines. Ask your access provider if they support it, because
   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/).
-  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
-  older kernel, you might need to upgrade pppd as well.  Note that you
-  don't need "PPP support" if you just want to run term (term is a
+  anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/system/network/serial/). Note that
+  you don't need "PPP support" if you just want to run 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 (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
+  has a program like lynx or netscape)).
+
+  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
+  older kernel, you might need to upgrade pppd as well. 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
@@ -3223,25 +3738,17 @@
   and will show up in the directory modules once you have said "make
   modules". If unsure, say N.
 
-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 sound card. 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.
+Wireless LAN (non-hamradio)
+CONFIG_NET_RADIO
+  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. 
 
-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) or Crystal
-  Semiconductors (such as CS4248, CS423x).
+  Some user-level drivers for scarab devices which don't require
+  special kernel support are available via ftp (user: anonymous) from
+  ftp://shadow.cabi.net/pub/Linux.
 
 STRIP (Metricom Starmode radio IP)
 CONFIG_STRIP
@@ -3255,23 +3762,48 @@
   a cellular telephone.  (You may also have heard them called
   "Metricom modems" but we avoid the term "modem" because it misleads
   many people into thinking that you can plug a Metricom modem into a
-  phone line and use it as a modem.)  You can use STRIP on any Linux
-  machine with a serial port, although it is obviously most useful for
-  people with laptop computers. If you think you might get a Metricom
-  radio in the future, there is no harm in saying Y to STRIP now,
-  except that it makes the kernel a bit bigger. You can also 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 strip.o.
+  phone line and use it as a modem.)  
+
+  You can use STRIP on any Linux machine with a serial port, although
+  it is obviously most useful for people with laptop computers. If you
+  think you might get a Metricom radio in the future, there is no harm
+  in saying Y to STRIP now, except that it makes the kernel a bit
+  bigger. 
+
+  You can also 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
+  strip.o.
+
+AT&T WaveLAN & DEC RoamAbout DS support
+CONFIG_WAVELAN
+  The Lucent Wavelan (formerly NCR and AT&T ; or DEC RoamAbout DS) is
+  a Radio LAN (wireless Ethernet-like Local Area Network) using the
+  radio frequencies 900 MHz and 2.4 GHz.
+  
+  This driver support the ISA version of the Wavelan card. A separate
+  driver for the pcmcia hardware is available in David Hinds's pcmcia
+  package. If you want to use an ISA Wavelan card under Linux, say Y
+  and read the Ethernet-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Some more specific
+  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 want).
+  The module will be called wavelan.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.
 
 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
+  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
+  something at ftp://ftp.lmh.ox.ac.uk/users/weejock/linux/, but I haven't
   written anything too useful yet...)
 
 AIMSlab RadioTrack card
@@ -3290,11 +3822,12 @@
   which allows you to open an LAPB point-to-point connection to some
   other computer on your Ethernet network. In order to do this, you
   need to say Y or M to the driver for your Ethernet card as well as
-  to "LAPB Data Link Driver".  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 lapbether.o.
-  If unsure, say N.
+  to "LAPB Data Link Driver".  
+
+  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 lapbether.o. If unsure, say N.
 
 X.25 async driver
 CONFIG_X25_ASY
@@ -3302,223 +3835,32 @@
   asynchronous serial lines such as telephone lines equipped with
   ordinary modems. Experts should note that this driver doesn't
   currently comply with the asynchronous HDLS framing protocols in
-  CCITT recommendation X.25. 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 x25_asy.o.  If
-  unsure, say N.
-
-Z8530 SCC driver for AX.25
-CONFIG_SCC
-  These cards are used to connect your Linux box to an amateur radio
-  in order to communicate with other computers.  If you want to use
-  this, read Documentation/networking/z8530drv.txt and the
-  AX.25-HOWTO, available via ftp (user: anonymous) at
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  Also make sure to say Y to
-  "Amateur Radio AX.25 Level 2" support. 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 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 (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.
+  CCITT recommendation X.25. 
 
-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 (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
+  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_par.o.
-
-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
-  baudrate to be set between 300 and 4800 baud (however not all modems
-  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 (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.
+  say M here and read Documentation/modules.txt. The module will be
+  called x25_asy.o. If unsure, say N.
 
-Sound card modem driver for AX.25
-CONFIG_SOUNDMODEM
-  This experimental driver allows a standard SoundBlaster or
-  WindowsSoundSystem compatible sound card to be used as a packet radio
-  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
-  Documentation/modules.txt. This is recommended. The module will be
-  called soundmodem.o.
+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 sound card. If unsure,
+  say N.
 
-Sound card modem support for SoundBlaster and compatible cards
-CONFIG_SOUNDMODEM_SBC
-  This option enables the soundmodem driver to use SoundBlaster and
-  compatible cards. If you have a dual mode card (i.e. a WSS cards
-  with a SoundBlaster emulation) you should say N here and Y to
-  "Sound card modem support for WSS and Crystal cards", below, because
-  this usually results in better performance. This option also supports
-  SB16/32/64 in full duplex mode.
+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.
 
-Sound card modem support for WSS and Crystal cards
-CONFIG_SOUNDMODEM_WSS
-  This option enables the soundmodem driver to use WindowsSoundSystem
+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). This option also supports
-  the WSS full duplex operation which currently works with Crystal
-  CS423x chips. If you don't need full duplex operation, do not enable
-  it to save performance.
-
-Sound card modem support for 1200 baud AFSK modulation
-CONFIG_SOUNDMODEM_AFSK1200
-  This option enables the soundmodem driver 1200 baud AFSK modem, 
-  compatible to popular modems using TCM3105 or AM7911. The demodulator
-  requires about 12% of the CPU power of a Pentium 75 CPU per channel.
-
-Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
-CONFIG_SOUNDMODEM_AFSK2400_7
-  This option enables the soundmodem driver 2400 baud AFSK modem,
-  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
-  crystal.  Note that the availability of this driver does _not_ imply
-  that I recommend building such links. It is only here since users
-  especially in eastern Europe have asked me to do so. In fact this
-  modulation scheme has many disadvantages, mainly its incompatibility
-  with many transceiver designs and the fact that the TCM3105 (if
-  used) is operated widely outside its specifications.
-
-Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
-CONFIG_SOUNDMODEM_AFSK2400_8
-  This option enables the soundmodem driver 2400 baud AFSK modem,
-  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
-  Note that the availability of this driver does _not_ imply that I
-  recommend building such links. It is only here since users
-  especially in eastern Europe have asked me to do so. In fact this
-  modulation scheme has many disadvantages, mainly its incompatibility
-  with many transceiver designs and the fact that the TCM3105 (if
-  used) is operated widely outside its specifications.
-
-Sound card modem support for 2666 baud AFSK modulation
-CONFIG_SOUNDMODEM_AFSK2666
-  This option enables the soundmodem driver 2666 baud AFSK modem.
-  This modem is experimental, and not compatible to anything
-  else I know of.
-
-Sound card modem support for 4800 baud 8PSK modulation
-CONFIG_SOUNDMODEM_PSK4800
-  This option enables the soundmodem driver 4800 baud 8PSK modem.
-  This modem is experimental, and not compatible to anything
-  else I know of.
-
-Sound card modem support for 4800 baud HAPN-1 modulation
-CONFIG_SOUNDMODEM_HAPN4800
-  This option enables the soundmodem driver 4800 baud HAPN-1
-  compatible modem. This modulation seems to be widely used 'down
-  under' and in the Netherlands. Here, nobody uses it, so I could not
-  test if it works.  It is compatible to itself, however :-)
-
-Sound card modem support for 9600 baud FSK G3RUH modulation
-CONFIG_SOUNDMODEM_FSK9600
-  This option enables the soundmodem driver 9600 baud FSK modem,
-  compatible to the G3RUH standard. The demodulator requires about 4%
-  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
-  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
-  can only use one protocol at a time, depending on what the other end
-  can understand).
-
-Serial port KISS driver for AX.25
-CONFIG_MKISS
-  KISS is the protocol used to send IP traffic over AX.25 radio
-  connections, somewhat similar to SLIP for telephone lines. Say Y
-  here if you intend to send Internet traffic over amateur radio,
-  using some device connected to your machine's serial port. In that
-  case, you also have to say Y to "Amateur Radio AX.25 Level 2"
-  support.  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 mkiss.o.
-
-Serial port 6PACK driver for AX.25
-CONFIG_6PACK
-6pack is a protocol that attaches a TNC connected to a serial interface
-to be used as a network device. 6pack can be used as an alternative to KISS,
-but has some extended functionality. Note that this driver is still
-experimental and might cause problems. For details about the features
-and the usage of the driver, read Documentation/networking/6pack.txt.
+  Analog Devices (such as AD1848, AD1845) or Crystal
+  Semiconductors (such as CS4248, CS423x).
 
 PLIP (parallel port) support
 CONFIG_PLIP
@@ -3529,27 +3871,31 @@
   drive (a minimal system has to be transferred with floppies
   first). The kernels on both machines need to have this PLIP option
   enabled for this to work.
+
   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/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://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.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
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini as well as the
+  NET-2-HOWTO in ftp://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.
 
@@ -3562,11 +3908,13 @@
   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 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.
+  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
@@ -3582,10 +3930,11 @@
   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
+  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.
 
@@ -3601,12 +3950,13 @@
   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 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.
 
 Max open DLCI
 CONFIG_DLCI_COUNT
@@ -3626,39 +3976,71 @@
   Say Y here if you need a driver for the Sangoma S502A, S502E, and
   S508 Frame Relay Access Devices. These are multi-protocol cards, but
   only frame relay is supported by the driver at this time. Please
-  read Documentation/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
-  sdla.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  read Documentation/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 sdla.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
+
+WAN Router
+CONFIG_WAN_ROUTER
+  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 a `WAN router' is
+  needed to connect to a WAN.
+
+  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 cards and
+  wish to use your Linux box as a WAN router, say Y here and to the
+  WAN driver for your card, below. You will also need a wan-tools
+  package available via FTP (user: anonymous) from
+  ftp://ftp.sangoma.com. Read Documentation/networking/wan-router.txt
+  for more information.
+
+  WAN routing support 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.
+
+Fast switching (read help!)
+CONFIG_NET_FASTROUTE
+  Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
+  Card) data transfers, which is fast.
+
+    *** This option is NOT COMPATIBLE with several important ***
+    *** networking options: especially CONFIG*FIREWALL.      ***
+
+  However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER
+  section (except for CONFIG_IP_ROUTE_TOS). At the moment, few devices
+  support fast switching (tulip is one of them, modified 8390 can be
+  found at ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). 
+
+  If unsure, say N.
+
+Forwarding between high speed interfaces
+CONFIG_NET_HW_FLOWCONTROL
+  This option enables NIC (Network Interface Card) hardware throttling
+  during periods of extremal congestion. At the moment only a couple
+  of device drivers support it (really only one ---tulip, modified
+  8390 can be found at
+  ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). Really, this
+  option is applicable to any machine attached to a fast enough
+  network, and even a 10Mb NIC is able to kill a not very slow box,
+  such as a 120MHz Pentium.
 
-WAN Router
-CONFIG_WAN_ROUTER
-  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 a `WAN router' is
-  needed to connect to a WAN.
-  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
-  cards (with appropriate WAN Link Driver) and wish to use your Linux
-  box as a WAN router, you may say 'Y' to this option.  You will also
-  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 support 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.
+  However, do not say Y here if you did not experience any serious
+  problems.
 
 CPU is too slow to handle full bandwidth
 CONFIG_CPU_IS_SLOW
-###
-### How to know when the CPU is too slow?
-###
+  If you suspect that your CPU is not fast enough to handle the
+  full bandwidth of your network connection, try saying Y here. If
+  unsure, say N.
 
 QoS and/or fair queueing
 CONFIG_NET_SCHED
@@ -3670,7 +4052,12 @@
   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
+  couple of different algorithms, say Y. 
+
+  To administer these schedulers, you'll need the user-level utilities
+  from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/
+
+  The available schedulers are
   listed in the following questions; you can say Y to as many as you
   like.  If unsure, say N now.
 
@@ -3683,11 +4070,11 @@
   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.
+
+  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
@@ -3695,21 +4082,26 @@
   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.
+  details and references about the algorithm). 
+  
+  Note: this scheduler is currently broken.
+
+  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.
+  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
@@ -3717,45 +4109,46 @@
   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.
+  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.
+  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.
+  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?
-###
+  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.
 
 Network code profiler
 CONFIG_NET_PROFILE
@@ -3766,16 +4159,16 @@
 
 WAN Drivers
 CONFIG_WAN_DRIVERS
-  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
+  Say Y to this option if your Linux box contains a WAN card and you
+  are planning to use the 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 drivers
+  for WAN cards 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.
+  card drivers. If unsure, say N.
 
 Sangoma WANPIPE(tm) multiprotocol cards
 CONFIG_VENDOR_SANGOMA
@@ -3788,11 +4181,12 @@
   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.
+  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
@@ -3826,93 +4220,117 @@
   you say N, the PPP support will not be included in the driver (saves
   about 16K of kernel memory).
 
+Ethernet (10 or 100Mbit)
+CONFIG_NET_ETHERNET
+  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
+  type of Local Area Networks (LANs) in universities or
+  companies. 10-base-2 or Thinnet (10 Mbps over coaxial cable, linking
+  computers in a chain), 10-base-T (10 Mbps over twisted pair
+  telephone cable, linking computers to a central hub) and
+  100-base-<whatever> (100 Mbps) are common types of Ethernet. 
+
+  If your Linux machine will be connected to an Ethernet and you have
+  an Ethernet network card installed in your computer, say Y here and
+  read the Ethernet-HOWTO, available via ftp (user: anonymous) from
+  ftp://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 Ethernet network cards. If unsure, say N.
+
 Sun LANCE Ethernet support
 CONFIG_SUN_LANCE
   This is support for lance Ethernet cards on Sun workstations such as
   the Sparcstation IPC (any Sparc with a network interface 'le0' under
-  SunOS basically). 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 lance.o. If you want
-  to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  SunOS basically). 
+
+  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 lance.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Sun Intel Ethernet support
 CONFIG_SUN_INTEL
   This is support for the Intel Ethernet cards on some Sun workstations
   (all those with a network interface 'ie0' under SunOS).
 
-Ethernet (10 or 100Mbit)
-CONFIG_NET_ETHERNET
-  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
-  type of Local Area Networks (LANs) in universities or
-  companies. 10-base-2 or Thinnet (10 Mbps over coaxial cable, linking
-  computers in a chain), 10-base-T (10 Mbps over twisted pair
-  telephone cable, linking computers to a central hub) and
-  100-base-<whatever> (100 Mbps) are common types of Ethernet. If your
-  Linux machine will be connected to an Ethernet and you have an
-  Ethernet network card installed in your computer, say Y here and
-  read the Ethernet-HOWTO, 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 Ethernet
-  network cards. If unsure, say N.
-
 Western Digital/SMC cards
 CONFIG_NET_VENDOR_SMC
   If you have a network (Ethernet) card belonging to this class, say Y
   and read the Ethernet-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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 Western
-  Digital cards. If you say Y, you will be asked for your specific
-  card in the following questions.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. 
+
+  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 Western Digital cards. If you say Y, you will be
+  asked for your specific card in the following questions.
 
 WD80*3 support
 CONFIG_WD80x3
   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
-  wd.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 wd.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.
+
+SMC Ultra MCA support
+CONFIG_ULTRAMCA
+  If you have a network (Ethernet) card of this type and are running
+  an MCA based system (PS/2), say Y and read
+  the Ethernet-HOWTO, available via ftp (user: anonymous) in
+  ftp://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 smc-mca.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.
 
 SMC Ultra support
 CONFIG_ULTRA
   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
-  smc-ultra.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.
-  Important: There have been many reports that, with some motherboards 
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. 
+  
+  Important: There have been many reports that, with some motherboards
   mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
-  such as some BusLogic models) causes corruption problems with many 
-  operating systems. The linux smc-ultra driver has a work-around for this
-  but keep it in mind if you have such a SCSI card and have problems.
+  such as some BusLogic models) causes corruption problems with many
+  operating systems. The Linux smc-ultra driver has a work-around for
+  this but keep it in mind if you have such a SCSI card and have
+  problems.
+
+  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 smc-ultra.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. 
 
 SMC Ultra32 EISA support
 CONFIG_ULTRA32
   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 smc-ultra32.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. 
+  ftp://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 smc-ultra32.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.
 
 SMC 9194 Support
 CONFIG_SMC9194
-  This is support for the SMC9xxx based Ethernet cards.  Choose this
+  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
+  another SMC9192/9194 based chipset. Say Y if you want it compiled
   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.
+  via ftp (user: anonymous) in
+  ftp://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
@@ -3924,7 +4342,8 @@
   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.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
   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
@@ -3934,76 +4353,82 @@
 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
+  ftp://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
   Documentation/networking/net-modules.txt.
 
 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
+  ftp://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.
 
 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
+  ftp://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.
 
 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
-  this type.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Some LinkSys cards are
+  of this type.
 
 3COM cards
 CONFIG_NET_VENDOR_3COM
   If you have a network (Ethernet) card belonging to this class, say Y
-  and read the Ethernet-HOWTO, available via ftp (user: anonymous)
-  in sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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 3COM
-  cards. If you say Y, you will be asked for your specific card in the
-  following questions.
+  and read the Ethernet-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  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 3COM cards. If you say Y, you will be asked for
+  your specific card in the following questions.
 
 3c501 support
 CONFIG_EL1
   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.  Also, consider buying a new
-  card, since the 3c501 is slow, broken, and obsolete: you will have
-  problems. Some people suggest to ping ("man ping") a nearby machine
-  every minute ("man cron") when using this card.  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 3c501.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt as well as
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Also, consider buying a
+  new card, since the 3c501 is slow, broken, and obsolete: you will
+  have problems. Some people suggest to ping ("man ping") a nearby
+  machine every minute ("man cron") when using this card.
+
+  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 3c501.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.
 
 3c503 support
 CONFIG_EL2
   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
-  3c503.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 3c503.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.
 
 3c505 support
@@ -4011,10 +4436,11 @@
   Information about this network (Ethernet) card can be found in
   Documentation/networking/3c505.txt. If you have a 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 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
+  anonymous) in ftp://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
   3c505.o.
 
@@ -4022,48 +4448,56 @@
 CONFIG_EL16
   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
-  3c507.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 3c507.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.
 
 3c523 support 
 CONFIG_ELMC
   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
-  3c523.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 3c523.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.
 
 3c509/3c579 support
 CONFIG_EL3
   If you have a network (Ethernet) card belonging to the 3Com
   EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
-  via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  If your card is not working you may need to use the DOS
+  setup disk to disable Plug & Play mode, and to select the default
+  media type.
+
   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
-  3c509.o. If your card is not working you may need to use the DOS
-  setup disk to disable Plug & Play mode, and to select the default
-  media type.
+  3c509.o. 
 
 3c590 series (592/595/597) "Vortex" support
 CONFIG_VORTEX
-  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. More specific information is
-  in Documentation/networking/vortex.txt and in the comments at the
-  beginning of drivers/net/3c59x.c. 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. 
+  If you have a 3Com "Vortex" or "Boomerang" series network (Ethernet)
+  card (Fast EtherLink 3c590/3c592/3c595/3c597 or the EtherLink XL
+  3c900 or 3c905), say Y and read the Ethernet-HOWTO, available via
+  ftp (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+  More specific information is in Documentation/networking/vortex.txt
+  and in the comments at the beginning of drivers/net/3c59x.c.
+
+  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.
 
 Other ISA cards
 CONFIG_NET_ISA
@@ -4071,28 +4505,33 @@
   bus system (that's the way the components of the card talk to each
   other) is ISA (as opposed to EISA, VLB or PCI), say Y. Make sure you
   know the name of your card. Read the Ethernet-HOWTO, available via
-  ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. If
-  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 remaining ISA network card questions.  If you
-  say Y, you will be asked for your specific card in the following
-  questions.
+  ftp (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+  If 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 remaining ISA network card questions. If you say Y, you will be
+  asked for your specific card in the following questions.
 
 Generic ARCnet support
 CONFIG_ARCNET
   If you have a network card of this type, say Y and check out the
   (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"
   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
-  (even though ARCnet is not really Ethernet). 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 arcnet.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt as well as
+  via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO (even though ARCnet is
+  not really Ethernet).
+
+  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 arcnet.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.
 
 Enable arc0e (ARCnet "ether-encap" packet format)
@@ -4124,23 +4563,26 @@
 CONFIG_ARCNET_COM90xx
   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
+  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 COM90xx (IO mapped) chipset driver
-CONFIG_ARCNET_COM90x
+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 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.
+  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
@@ -4148,6 +4590,7 @@
   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
@@ -4158,34 +4601,37 @@
 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 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
+  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
   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
-  e2100.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 e2100.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.
 
 CS89x0 support
 CONFIG_CS89x0
-  Support for CS89x0 chipset based Ethernet cards.  If you have a
+  Support for CS89x0 chipset based Ethernet cards. 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 as well as
-  Documentation/networking/cs89x0.txt.  If you want to compile this as
-  a module ( = code which can be inserted in and removed from the
-  running kernel whenever you want), say M here and read
-  Documentation/modules.txt as well as
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO as well as
+  Documentation/networking/cs89x0.txt.
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt as well as
   Documentation/networking/net-modules.txt. The module will be called
   cs89x.o.
 
@@ -4193,12 +4639,14 @@
 CONFIG_DEPCA
   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 as well as
-  drivers/net/depca.c.  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 depca.o.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO as well as
+  drivers/net/depca.c.
+
+  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
+  depca.o.
 
 EtherWorks 3 support
 CONFIG_EWRK3
@@ -4206,10 +4654,11 @@
   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
+  ftp://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.
 
@@ -4217,16 +4666,18 @@
 CONFIG_SEEQ8005
   This is a driver for the SEEQ 8005 network (Ethernet) card. If this
   is for you, read the Ethernet-HOWTO, available via ftp (user:
-  anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 AT1700 support
 CONFIG_AT1700
   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). If you want to compile it as a
-  module, say M here and read Documentation/modules.txt as well as
+  ftp://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).
+  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
   at1700.o.
 
@@ -4234,24 +4685,27 @@
 CONFIG_FMV18X
   If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
   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 fmv18x.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 use an FMV-183 or
-  FMV-184 and it is not working, you may need to disable Plug & Play
-  mode of the card.
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  If you use an FMV-183 or FMV-184 and it is not working, you may need
+  to disable Plug & Play mode of the card.
+
+  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 fmv18x.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. 
 
 EtherExpressPro support
 CONFIG_EEXPRESS_PRO
   If you have a network (Ethernet) card of this type, say Y. Note
   however that the EtherExpressPro 100 Ethernet card has its own
   separate driver. Please 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 eepro.o. If you want to compile it as a
+  (user: anonymous) in ftp://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 eepro.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.
 
@@ -4259,67 +4713,50 @@
 CONFIG_EEXPRESS
   If you have an EtherExpress16 network (Ethernet) card, say Y and
   read the Ethernet-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the Intel
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that the Intel
   EtherExpress16 card used to be regarded as a very poor choice
   because the driver was very unreliable. We now have a new driver
-  that should do better. 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 as well as
+  that should do better.
+
+  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 as well as
   Documentation/networking/net-modules.txt. The module will be called
   eexpress.o.
 
-AT&T WaveLAN & DEC RoamAbout DS support
-CONFIG_WAVELAN
-  The Lucent Wavelan (formerly NCR and AT&T ; or DEC RoamAbout DS) is
-  a Radio LAN (wireless Ethernet-like Local Area Network) using the
-  radio frequencies 900 MHz and 2.4 GHz.
-  This driver support the ISA version of the Wavelan card. A driver
-  for the pcmcia hardware is available in David Hinds's pcmcia
-  package.
-  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
-  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
-  want). The module will be called wavelan.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.
-
 HP PCLAN+ (27247B and 27252A) support
 CONFIG_HPLAN_PLUS
   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
-  hp-plus.o. If you want to compile it as a module, say M here and
-  read Documentation/modules.txt as well as
+  ftp://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 hp-plus.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.
 
 HP PCLAN (27245 and other 27xxx series) support
 CONFIG_HPLAN
   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
-  hp.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 hp.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.
 
 HP 10/100VG PCLAN (ISA, EISA, PCI) support
 CONFIG_HP100
   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 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
+  ftp://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
   hp100.o.
 
@@ -4327,82 +4764,89 @@
 CONFIG_NE2000
   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. Many Ethernet cards without a
-  specific driver are compatible with NE2000. 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 ne.o. If you want to compile it as a module, say M here and
-  read Documentation/modules.txt as well as
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Many Ethernet cards
+  without a specific driver are compatible with NE2000.
+
+  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 ne.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.
 
 SK_G16 support
 CONFIG_SK_G16
   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.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 EISA, VLB, PCI and on board controllers
 CONFIG_NET_EISA
   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. 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 are unsure, say Y.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  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 are unsure, say Y.
 
 AMD PCnet32 (VLB and PCI) support
 CONFIG_PCNET32
   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. 
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 Ansel Communications EISA 3200 support
 CONFIG_AC3200
   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
-  ac3200.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 ac3200.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.
 
 Racal-Interlan EISA ES3210 support
 CONFIG_ES3210
   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
-  es3210.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  ftp://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 es3210.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.
 
 Apricot Xen-II on board Ethernet
 CONFIG_APRICOT
   If you have a network (Ethernet) controller 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 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
+  ftp://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
   apricot.o.
 
 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
 CONFIG_DE4X5
-  This is support for the DIGITAL series of PCI/EISA Ethernet
-  cards. These include the DE425, DE434, DE435, DE450 and DE500
-  models. If you have a network card of this type, say Y and read the
+  This is support for the DIGITAL series of PCI/EISA Ethernet cards.
+  These include the DE425, DE434, DE435, DE450 and DE500 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 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
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. More specific
+  information is 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.
 
 DECchip Tulip (dc21x4x) PCI support
@@ -4414,59 +4858,83 @@
   (smc9332dst), you can also try the driver for "Generic DECchip"
   cards, above. However, most people with a network card of this type
   will say Y here.) Do read the Ethernet-HOWTO, available via ftp
-  (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. More
-  specific information is contained in
-  Documentation/networking/tulip.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
-  tulip.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt as well as
+  (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+  More specific information is contained in
+  Documentation/networking/tulip.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 tulip.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.
 
 Digi Intl. RightSwitch support
 CONFIG_DGRS
   This is support for the Digi International RightSwitch series of
-  PCI/EISA Ethernet switch cards.  These include the SE-4 and the SE-6
+  PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
   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 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. 
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. More specific
+  information is 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.
 
 EtherExpressPro/100 support
 CONFIG_EEXPRESS_PRO100
   If you have an Intel EtherExpressPro 100 PCI network (Ethernet)
   card, 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 eepro100.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. 
+  anonymous) in ftp://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 eepro100.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.
 
 ICL EtherTeam 16i/32 support
 CONFIG_ETH16I
   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
-  eth16i.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. 
+  ftp://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 eth16i.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.
 
 TI ThunderLAN support (EXPERIMENTAL)
 CONFIG_TLAN
   If you have a TLAN based network card which is supported by this
-  driver, say Y and read the Ethernet-HOWTO.  Devices currently
-  supported are the Compaq Netelligent 10, Netelligent 10/100, and
-  Internal NetFlex 3.  This driver is also available as a module.  The
-  module will be called tlan.o. Please email feedback to
-  james.banks@caldera.com.
+  driver, say Y and read the Ethernet-HOWTO, available via ftp (user:
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Devices
+  currently supported are the Compaq Netelligent 10, Netelligent
+  10/100, and Internal NetFlex 3.
+
+  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 tlan.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.
+
+  Please email feedback to james.banks@caldera.com.
+
+SMC EtherPower II (EXPERIMENTAL)
+CONFIG_EPIC100
+  If you have an SMC EtherPower II 9432 PCI ethernet network card
+  which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
+  available via ftp (user: anonymous) in
+  ftp://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 epic100.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.
 
 Zenith Z-Note support
 CONFIG_ZNET
@@ -4474,35 +4942,38 @@
   (Ethernet) card, and this is the Linux driver for it. Note that the
   IBM Thinkpad 300 is compatible with the Z-Note and is also supported
   by this driver. Read the Ethernet-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 Pocket and portable adapters
 CONFIG_NET_POCKET
   Cute little network (Ethernet) devices which attach to the parallel
   port ("pocket adapters"), commonly used with laptops. 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
-  want to plug a network card into the PCMCIA slot of your laptop
-  instead (PCMCIA is the standard for credit card size extension cards
-  used by all modern laptops), look on the ftp site (user: anonymous)
-  cb-iris.stanford.edu:/pub/pcmcia and say N here.  
+  (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  If you want to plug a network card into the PCMCIA slot of your
+  laptop instead (PCMCIA is the standard for credit card size
+  extension cards used by all modern laptops), look on the ftp site
+  (user: anonymous) ftp://cb-iris.stanford.edu/pub/pcmcia and say N
+  here.
+
   Laptop user want to read the Linux Laptop homepage at
   http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
   WWW, you need to have access to a machine on the Internet that has a
-  program like lynx or netscape).
+  program like lynx or netscape). 
+
   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 devices.  If you say Y,
-  you will be asked for your specific device in the following
-  questions.
+  the questions about this class of network devices. If you say Y, you
+  will be asked for your specific device in the following questions.
 
 AT-LAN-TEC/RealTek pocket adapter support
 CONFIG_ATP
   This is a network (Ethernet) device which attaches to your parallel
   port. Read drivers/net/atp.c 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. If
-  you intend to use this driver, you should have said N to the
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
+  If you intend to use this driver, you should have said N to the
   Parallel Printer support, because the two drivers don't like each
   other.
 
@@ -4511,26 +4982,28 @@
   This is a network (Ethernet) device which attaches to your parallel
   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
-  want to compile this driver as a module however ( = code which can
-  be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called de600.o.
+  ftp://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 want to compile this driver as a module however ( = code
+  which can be inserted in and removed from the running kernel
+  whenever you want), say M here and read Documentation/modules.txt.
+  The module will be called de600.o.
 
 D-Link DE620 pocket adapter support
 CONFIG_DE620
   This is a network (Ethernet) device which attaches to your parallel
   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
-  want to compile this driver as a module however ( = code which can
-  be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called de620.o.
+  ftp://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 want to compile this driver as a module however ( = code
+  which can be inserted in and removed from the running kernel
+  whenever you want), say M here and read Documentation/modules.txt.
+  The module will be called de620.o.
 
 Token Ring driver support
 CONFIG_TR
@@ -4538,34 +5011,41 @@
   rest of the world uses Ethernet. To participate on a Token Ring
   network, you need a special Token ring network card. If you are
   connected to such a Token Ring network and want to use your Token
-  Ring card under Linux, say Y here and read the Token-Ring
-  mini-HOWTO, available via ftp (user:anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Most people can say N here.
+  Ring card under Linux, say Y here and to the driver for your
+  particular card below and read the Token-Ring mini-HOWTO, available
+  via ftp (user:anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Most people can say N
+  here.
 
 IBM Tropic chipset based adapter support
 CONFIG_IBMTR
   This is support for all IBM Token Ring cards that don't use DMA. If
   you have such a beast, say Y and read the Token-Ring mini-HOWTO,
   available via ftp (user:anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Warning: this driver will
-  almost definitely fail if more than one active Token Ring card is
-  present. 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 ibmtr.o. If you want to compile it
-  as a module, say M here and read Documentation/modules.txt.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  Warning: this driver will almost definitely fail if more than one
+  active Token Ring card is present. 
+
+  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 ibmtr.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Traffic Shaper (EXPERIMENTAL)
 CONFIG_SHAPER
   The traffic shaper is a virtual network device that allows you to
-  limit the rate of outgoing data flow over another network
+  limit the rate of outgoing data flow over some other network
   device. See Documentation/networking/shaper.txt for more
   information.  To set up and configure shaper devices, you need the
   shapecfg program, available via ftp (user: anonymous) from
-  shadow.cabi.net/pub/Linux in the shaper package.  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 shaper.o. If you want to compile it as a module, say M
-  here and read Documentation/modules.txt. If unsure, say N.
+  ftp://shadow.cabi.net/pub/Linux in the shaper package.  
+
+  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 shaper.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt. If unsure,
+  say N.
 
 FDDI driver support
 CONFIG_FDDI
@@ -4585,21 +5065,25 @@
 CONFIG_CD_NO_IDESCSI
   If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
   here, otherwise N. Read the CDROM-HOWTO, available via ftp (user:
-  anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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 these CDROM drives. If you are unsure what you have, say Y and
-  find out whether you have one of the following drives.
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. 
+
+  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 these CDROM drives. If you are unsure what you
+  have, say Y and find out whether you have one of the following
+  drives. 
+
   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.
-  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
-  Documentation/modules.txt.
+  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. 
+
+  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 Documentation/modules.txt. 
+
   If you want to use any of these CDROM drivers, you also have to say
   Y to "ISO9660 cdrom filesystem support" below (this answer will get
   "defaulted" for you if you enable any of the Linux CDROM drivers).
@@ -4614,34 +5098,41 @@
   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
-  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 cdu31a.o. If
-  you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  explained in the SCSI-HOWTO. 
+
+  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 cdu31a.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Standard Mitsumi [no XA/Multisession] CDROM support
 CONFIG_MCD
   This is the older of the two drivers for the older Mitsumi models
   LU-005, FX-001 and FX-001D. This is not the right driver for the
   FX-001DE and the triple or quad speed models (all these are
-  IDE/ATAPI models).
+  IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
+
   With the old LU-005 model, the whole drive chassis slides out for cd
   insertion.  The FX-xxx models use a motorized tray type mechanism.
   Note that this driver does not support XA or MultiSession CDs
   (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 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 (
-  = code which can be inserted in and removed from the running kernel
-  whenever you want). The module will be called mcd.o. If you want to
-  compile it as a module, say M here and read
-  Documentation/modules.txt.
+  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. 
+
+  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 mcd.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Mitsumi [XA/MultiSession] support
 CONFIG_MCDX
@@ -4650,51 +5141,58 @@
   FX-001 or FX-001D CDROM drive. In addition, this driver uses much less
   kernel memory than the old one, if that is a concern. This driver is
   able to support more than one drive, but each drive needs a separate
-  interface card.
+  interface card. Please read the file Documentation/cdrom/mcdx. 
+
   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/mcdx. 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 mcdx.o. If you want to compile it as a module,
-  say M here and read Documentation/modules.txt.
+  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 mcdx.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
 CONFIG_SBPCD
   This driver supports most of the drives which use the Panasonic or
-  SoundBlaster interface.
+  SoundBlaster interface. Please read the file
+  Documentation/cdrom/sbpcd.
+
   The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
   (sometimes labeled "Creative"), the CreativeLabs CD200, the
   Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
   model), the TEAC CD-55A fall under this category. Some other
   "electrically compatible" drives (Vertos, Genoa, some Funai models)
   are currently not supported; for the Sanyo H94A drive currently a
-  separate driver (asked later) is responsible.  Most drives have a
+  separate driver (asked later) is responsible. Most drives have a
   uniquely shaped faceplate, with a caddyless motorized drawer, but
   without external brand markings. The older CR-52x drives have a
-  caddy and manual loading/eject, but still no external markings.  The
+  caddy and manual loading/eject, but still no external markings. The
   driver is able to do an extended auto-probing for interface
   addresses and drive types; this can help to find facts in cases you
   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 drivers/cdrom/sbpcd.h and set "DISTRIBUTION 0" there.
-  This driver can support up to four CDROM interface cards, and each
+  none of the supported drives gets found. Once your drive got found,
+  you should enter the reported parameters into drivers/cdrom/sbpcd.h
+  and set "DISTRIBUTION 0" there.
+
+  This driver can support up to four CDROM controller 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
-  module, only one interface card (but with up to four drives) is
-  usable. 
+  will be asked how many controller cards you have. If compiled as a
+  module, only one controller card (but with up to four drives) is
+  usable.
+
   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/sbpcd. 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 sbpcd.o. If you want to compile it as a
+  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 sbpcd.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Matsushita/Panasonic, ... second CDROM controller support
 CONFIG_SBPCD2
-  Say Y here only if you have two CDROM controller boards of this type
+  Say Y here only if you have two CDROM controller cards 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/include/linux/sbpcd.h before compiling the new kernel. Read
@@ -4706,49 +5204,61 @@
   CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
   CR540 CDROM drive.  This driver - just like all these CDROM drivers
   - is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
-  CDA269-031SE. 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/aztcd. 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 aztcd.o. If you want to compile it as a
+  CDA269-031SE. Please read the file Documentation/cdrom/aztcd. 
+
+  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 aztcd.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Sony CDU535 CDROM support
 CONFIG_CDU535
   This is the driver for the older Sony CDU-535 and CDU-531 CDROM
-  drives.  If you say Y here, you should also say Y to "ISO9660 cdrom
+  drives. Please read the file Documentation/cdrom/sonycd535.
+
+  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/sonycd535. 
+  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 sonycd535.o. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt.
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called sonycd535.o. If you want to compile it as
+  a module, say M here and read Documentation/modules.txt.
 
 Goldstar R420 CDROM support
 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.
+  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
   If you have a Philips/LMS CDROM drive cm206 in combination with a
   cm260 host adapter card, say Y here.  Please also read the file
-  Documentation/cdrom/cm206. 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 cm206.o. If you
-  want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  Documentation/cdrom/cm206. 
+
+  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 cm206.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Optics Storage DOLPHIN 8000AT CDROM support
 CONFIG_OPTCD
@@ -4757,31 +5267,38 @@
   you have one of those, say Y. This driver does not work for the
   Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
   one. Please read the file Documentation/cdrom/optcd. 
+
   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 optcd.o. If you want to compile it
-  as a module, say M here and read Documentation/modules.txt.
+  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 optcd.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Sanyo CDR-H94A CDROM support
 CONFIG_SJCD
   If this is your CDROM drive, say Y here and read the file
   Documentation/cdrom/sjcd. You should then 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 sjcd.o. If you want to compile it
-  as a module, say M here and read Documentation/modules.txt.
+  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 sjcd.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Soft configurable cdrom interface card support
 CONFIG_CDI_INIT
   If you want to include boot-time initialization of any cdrom
   interface card that is software configurable, say Y here.  Currently
   only the ISP16/MAD16/Mozart sound cards with built-in cdrom
-  interfaces are supported.  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 these CDROM drives.
+  interfaces are supported.  
+
+  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 these CDROM drives.
 
 ISP16/MAD16/Mozart soft configurable cdrom interface support
 CONFIG_ISP16_CDI
@@ -4789,20 +5306,23 @@
   OPTi 82C928 or 82C929 chips. Say Y here to have them detected and
   possibly configured at boot time. In addition, You'll have to say Y
   to a driver for the particular cdrom drive you have attached to the
-  card. Read Documentation/cdrom/isp16 for details.  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 isp16.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt.
+  card. Read Documentation/cdrom/isp16 for details.  
+
+  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 isp16.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Preload dcache
 CONFIG_DCACHE_PRELOAD
   Preloading will create dcache entries when a directory is scanned
-  (e.g. with ls) for the *first* time. This should speed up successive
-  lookups of information about files in that directory, but can also
-  consume large amounts of memory.  
+  (e.g. because the ls command was used) for the *first* time. This
+  should speed up successive lookups of information about files in
+  that directory, but can also consume large amounts of memory.
+
   Please report speedups (or slowdowns due to the memory usage if they
   occur) to schoebel@informatik.uni-stuttgart.de .
+
   If unsure, say N.
 
 Quota support
@@ -4812,24 +5332,30 @@
   ext2 filesystem. You need additional software in order to use quota
   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
+  ftp://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
   omirr is a package for _symmetric_ mirroring of files over the
-  Internet. In contrast to rdist, the online mirror daemon (omirrd)
-  is running all the time and transfers any changes on the file system
-  as soon as possible to all other servers. Symmetric means that all
+  Internet. In contrast to rdist, the online mirror daemon (omirrd) is
+  running all the time and transfers any changes on the file system as
+  soon as possible to all other servers. Symmetric means that all
   servers have equal rights in changing a file: the last changer of a
   file will win. This is the same behaviour as multiple processes
   operating on a global file system. In effect, omirr can do the same
-  as nfs mounts, but will have better performance since the data is
+  as NFS mounts, but will have better performance since the data is
   stored on local disks. In contrast to a cache filesystem which has a
-  dedicated master copy, broken connections and/or servers are no problem
-  for continuing work on the remaining ones, because there is no master
-  copy. You must say Y if you want to use omirrd, but you should (but
-  need not) say N if you don't (for performance reasons).
+  dedicated master copy, broken connections and/or servers are no
+  problem for continuing work on the remaining ones, because there is
+  no master copy. Every computer that wants to participate in the
+  mirroring needs to run the daemon omirrd, contained in the omirr
+  package which is available via ftp (user: anonymous) from
+  ftp://ftp.isa.de/pub/home/luik. You must say Y if you want to use
+  in.omirrd, but you should (but need not) say N if you don't (for
+  performance reasons).
+
+  Note that this is experimental code; use at your own risk.
 
 Filename translation support
 CONFIG_TRANS_NAMES
@@ -4840,6 +5366,7 @@
   minimum when used for configuration files. The kernel running on the
   clients should have this option enabled. If you don't administer a
   pool of Linux clients, say N here, otherwise read on:
+
   When you say Y here, filenames, directory names etc become
   context-sensitive.  If you have a file named
   "/etc/config#host=banana#", it will appear (by default) as
@@ -4848,19 +5375,26 @@
   hardlinked to "/etc/config".
   This default behaviour can be changed by setting the _first_
   environment variable NAMETRANS to a colon-separated list of suffixes
-  which are tried in the specified order. For example, in 'env -
-  NAMETRANS=#host=mango#:#ktype=diskless# "`env`" command ...' the
-  command will see the same files as if it had been executed on host
-  "mango" with a diskless kernel.
+  which are tried in the specified order. For example, in 
+ 
+  'env - NAMETRANS=#host=mango#:#ktype=diskless# "`env`" command ...'
+   
+  the command will see the same files as if it had been executed on
+  host "mango" with a diskless kernel.
+
   Using NAMETRANS supersedes _all_ default translations. Thus
   translations can be completely switched off with an empty list,
-  e.g. 'env - NAMETRANS= "`env`" command ...'.  Note that some system
-  utilities like tar, dump, restore should be used with translation
-  switched off, in order to avoid doubled space in archive files and
-  when extracting from them. Also, make sure that nfsd, mountd (and
-  similar ones like samba daemons) run without translation, in order
-  to avoid doubled (or even wrong) translation at the server and at
-  the client.
+  e.g. 
+
+  'env - NAMETRANS= "`env`" command ...'  
+
+  Note that some system utilities like tar, dump, restore should be
+  used with translation switched off, in order to avoid doubled space
+  in archive files and when extracting from them. Also, make sure that
+  nfsd, mountd (and similar ones like samba daemons) run without
+  translation, in order to avoid doubled (or even wrong) translation
+  at the server and at the client.
+
   You can automatically force the creation of context-dependent
   filenames if there exists a template filename like
   "/etc/mtab#host=CREATE#". As soon as a process running on "mango"
@@ -4873,6 +5407,7 @@
   otherwise try to create one shared /etc/mtab which would result in a
   clash. Also one should execute "touch /etc/nologin#host=CREATE#" to
   prevent global side effects from shutdown resp. runlevel.
+
   Please read Documentation/transname.txt if you intend to say Y here.
 
 Restrict translation to gid
@@ -4886,9 +5421,11 @@
   context-dependent files to some special group like "adm" (group id
   4) and enable this option. As a result, users will not notice any
   performance degradation resulting from filename translation.
+
   Note that translations resulting from the first environment variable
   "NAMETRANS=..." are always carried out regardless of the gid of
   directories.
+
   Beware: before turning on this option make sure that all directories
   containing context-dependent files belong to the special group, or
   system initialization may fail. If unsure, select N.
@@ -4915,7 +5452,7 @@
   the hostname at boot time, and there is no way to tell the hostname
   by lilo or bootp. Please avoid using this option and prefer
   "Nodename (hostname) translation" (CONFIG_TR_NODENAME) wherever
-  possible. When mounting the root over nfs, the own hostname must be
+  possible. When mounting the root over NFS, the own hostname must be
   known at boot time anyway; this option is just for special use.
   Note that the default translations are tried in the order as
   occurring in the configuration, that is 1) host 2) kname 3) ktype 4)
@@ -4975,12 +5512,13 @@
   leaner. You don't want to use it on your hard disk because of certain
   built-in restrictions. This option will enlarge your kernel by about
   25 kB. Everyone should say Y or M so that they are able to read this
-  common floppy format.  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 minix.o. Note
-  that the filesystem of your root partition cannot be compiled as a
-  module.
+  common floppy format.  
+
+  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 minix.o. Note that the filesystem of your root partition
+  cannot be compiled as a module.
 
 Second extended fs support
 CONFIG_EXT2_FS
@@ -4997,32 +5535,41 @@
   transition to a *real* Linux partition later. Another (rare) case
   which doesn't require ext2fs is a diskless Linux box which mounts
   all files over the network using NFS (in this case it's sufficient
-  to say Y to "NFS filesystem support" below). There is a short
-  ext2fs-FAQ, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/faqs. This option will enlarge your
-  kernel by about 41 kB. If you want to compile this filesystem 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 ext2.o. Be
-  aware however that the filesystem of your root partition cannot be
-  compiled as a module, and so this could be dangerous. Most everyone
-  wants to say Y here.
+  to say Y to "NFS filesystem support" below). Saying Y here will
+  enlarge your kernel by about 41 kB.
+
+  The Ext2fs-Undeletion mini-HOWTO, available via ftp (user:
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini,
+  gives information about how to retrieve deleted files on ext2fs
+  filesystems.
+
+  To change the behavior of ext2fs filesystems, you can use the
+  tune2fs utility ("man tune2fs"). 
+
+  If you want to compile this filesystem 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 ext2.o. Be aware however that the filesystem of your
+  root partition cannot be 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
+  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.
+  ftp://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
@@ -5044,15 +5591,16 @@
   foundation for the other filesystems. It is now also becoming
   possible to read and write compressed FAT filesystems; read
   Documentation/filesystems/fat_cvf.txt for details. This option will
-  enlarge your kernel by about 24 kB. If unsure, say Y. If you want to
-  compile this as a module however ( = code which can be inserted in
-  and removed from the running kernel whenever you want), say M here
-  and read Documentation/modules.txt. The module will be called fat.o.
-  Note that if you compile the FAT support as a module, you cannot
-  compile any of the FAT-based filesystems into the kernel - they will
-  have to be modules as well. The filesystem of your root partition
-  cannot be a module, so don't say M here if you intend to use UMSDOS
-  as your root filesystem.
+  enlarge your kernel by about 24 kB. If unsure, say Y. 
+
+  If you want to compile this as a module however ( = code which can
+  be inserted in and removed from the running kernel whenever you
+  want), say M here and read Documentation/modules.txt. The module
+  will be called fat.o. Note that if you compile the FAT support as a
+  module, you cannot compile any of the FAT-based filesystems into the
+  kernel - they will have to be modules as well. The filesystem of
+  your root partition cannot be a module, so don't say M here if you
+  intend to use UMSDOS as your root filesystem.
 
 msdos fs support
 CONFIG_MSDOS_FS
@@ -5060,26 +5608,30 @@
   they are compressed; to access compressed MSDOS partitions under
   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
-  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.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, or try dmsdosfs in
+  ftp://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.
+
   Another way to read and write MSDOS floppies from within Linux (but
   not transparently) is with the mtools ("man mtools") program suite,
-  which doesn't require the msdos filesystem support.  If you want to
-  use umsdos, the Unix-like filesystem on top of DOS, which allows you
-  to run Linux from within a DOS partition without repartitioning,
-  you'll have to say Y or M here. If you have Windows 95 or Windows
-  NT installed on your MSDOS partitions, you should use the VFAT
-  filesystem instead, or you will not be able to see the long
-  filenames generated by Windows 95 / Windows NT. This option will
-  enlarge your kernel by about 7 kB. If unsure, say Y. This will only
-  work if you said Y to "fat fs support" as well. If you want to
-  compile this as a module however ( = code which can be inserted in
-  and removed from the running kernel whenever you want), say M here
-  and read Documentation/modules.txt. The module will be called
-  msdos.o.
+  which doesn't require the msdos filesystem support.  
+
+  If you want to use umsdos, the Unix-like filesystem on top of DOS,
+  which allows you to run Linux from within a DOS partition without
+  repartitioning, you'll have to say Y or M here. If you have Windows
+  95 or Windows NT installed on your MSDOS partitions, you should use
+  the VFAT filesystem instead, or you will not be able to see the long
+  filenames generated by Windows 95 / Windows NT. 
+
+  This option will enlarge your kernel by about 7 kB. If unsure, say
+  Y. This will only work if you said Y to "fat fs support" as well. If
+  you want to compile this as a module however ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called msdos.o.
 
 vfat fs support
 CONFIG_VFAT_FS
@@ -5091,10 +5643,12 @@
   UMSDOS instead. This option enlarges your kernel by about 10 kB and
   it only works if you said Y to the "fat fs support" above. Please read
   the file Documentation/filesystems/vfat.txt for details.
-  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. The module
-  will be called vfat.o.
+  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. The module will be
+  called vfat.o.
 
 umsdos: Unix like fs on top of std MSDOS fs
 CONFIG_UMSDOS_FS
@@ -5108,12 +5662,13 @@
   is to write files with long unix filenames to MSDOS floppies; it
   also allows unix style softlinks and owner/permissions of files on
   MSDOS floppies. You will need a program called umssync in order to
-  make use of umsdos; read Documentation/filesystems/umsdos.txt. This
-  option enlarges your kernel by about 25 kB and it only works if you
-  said Y to both "fat fs support" and "msdos fs support" above. If you
-  want to compile this as a module ( = code which can be inserted in
-  and removed from the running kernel whenever you want), say M here
-  and read Documentation/modules.txt. The module will be called
+  make use of umsdos; read Documentation/filesystems/umsdos.txt. 
+
+  This option enlarges your kernel by about 25 kB and it only works if
+  you said Y to both "fat fs support" and "msdos fs support" above. If
+  you want to compile this as a module ( = code which can be inserted
+  in and removed from the running kernel whenever you want), say M
+  here and read Documentation/modules.txt. The module will be called
   umsdos.o. Note that the filesystem of your root partition cannot be
   a module, so this could be dangerous. If unsure, say N.
 
@@ -5121,21 +5676,23 @@
 CONFIG_PROC_FS
   This is a virtual filesystem providing information about the status
   of the system. "Virtual" means that it doesn't take up any space on
-  your hard disk: the files are created on the fly when you access
-  them. Also, you cannot read the files with older version of the
-  program less: you need to use more or cat. The filesystem is
-  explained in the Kernel Hacker's Guide at
+  your hard disk: the files are created on the fly by the kernel when
+  you try to access them. Also, you cannot read the files with older
+  version of the program less: you need to use more or cat. The
+  filesystem is explained in the Kernel Hacker's Guide at
   http://www.redhat.com:8080/HyperNews/get/khg.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), 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.
+  manpage ("man 8 proc").
+
+  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). This option will enlarge your kernel by about
+  18 kB. Several programs depend on this, so everyone should say Y
+  here.
 
 NFS filesystem support
 CONFIG_NFS_FS
@@ -5146,29 +5703,39 @@
   the files with usual UNIX commands as if they were sitting on the
   client's hard disk. For this to work, the server must run the
   programs nfsd and mountd (but does not need to have NFS filesystem
-  support enabled). NFS is explained in the Network Administrator's
-  Guide, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/LDP, on its man page: "man nfs", and
-  in the NFS-HOWTO. If you say Y here, you should have said Y to
-  TCP/IP networking also. This option would enlarge your kernel by
-  about 27 kB. This 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 nfs.o. If you want to
-  compile it as a module, say M here and read
-  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/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.
+  support enabled in its kernel). NFS is explained in the Network
+  Administrator's Guide, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/LDP, on its man page: "man
+  nfs", and in the NFS-HOWTO.
+
+  If you say Y here, you should have said Y to TCP/IP networking also.
+  This option would enlarge your kernel by about 27 kB. 
+
+  This 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 nfs.o. If you want to compile it as a module,
+  say M here and read Documentation/modules.txt. 
+
+  If you are configuring 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
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/ethernet/, extract with
+  "tar xzvf filename", and say Y to "Root file system on NFS" and to
+  "IP: kernel level autoconfiguration"), then you cannot compile this
+  driver as a module.
+
+  If you don't know what all this is about, say N.
 
 Root file system on NFS
 CONFIG_ROOT_NFS
   If you want your Linux box to mount its whole root filesystem from
   some other computer over the net via NFS (presumably because your
   box doesn't have a hard disk), say Y. Read Documentation/nfsroot.txt
-  for details. Most people say N here. 
+  for details. It is likely that in this case, you also want to say Y
+  to "IP: kernel level autoconfiguration" so that your box can
+  discover its network address at boot time. 
+  
+  Most people say N here. 
 
 NFS server support
 CONFIG_NFSD
@@ -5182,34 +5749,12 @@
   You will need the support software from the linux-nfs package
   available at ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir/.
   Please read the NFS-HOWTO, available via ftp (user: anonymous) from
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO. The nfs server is also
-  available as a module ( = code which can be inserted in and removed
-  from the running kernel whenever you want). The module is called
-  nfsd.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt. If unsure, say N.
+  sunsite.unc.edu:/pub/Linux/docs/HOWTO. 
 
-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.
+  The NFS server is also available as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want).
+  The module is called nfsd.o. If you want to compile it as a module,
+  say M here and read Documentation/modules.txt. If unsure, say N.
 
 OS/2 HPFS filesystem support (read only)
 CONFIG_HPFS_FS
@@ -5218,24 +5763,25 @@
   partitions. Say Y if you want to be able to read files from an OS/2
   HPFS partition of your hard drive. OS/2 floppies however are in
   regular MSDOS format, so you don't need this option in order to be
-  able to read them. Read Documentation/filesystems/hpfs.txt. 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 hpfs.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt. If unsure,
-  say N.
+  able to read them. Read Documentation/filesystems/hpfs.txt. 
+
+  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 hpfs.o. If you want to compile it as a module,
+  say M here and read Documentation/modules.txt. If unsure, say N.
 
 Windows NT NTFS support (read only)
 CONFIG_NTFS_FS
   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. 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.
+  to get read access to files on NTFS partitions of your hard drive.
+  The Linux NTFS driver supports most of the mount options of the VFAT
+  driver, see 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
@@ -5249,99 +5795,126 @@
 CONFIG_SYSV_FS
   SCO, Xenix and Coherent are commercial Unix systems for Intel
   machines. Saying Y here would allow you to read and write to and
-  from their floppies and hard disk partitions. If you have a floppy or
-  hard disk partition like that, it is probable that they contain
-  binaries from those other Unix systems; in order to run these
-  binaries, you will want to install iBCS2 (iBCS2 [Intel Binary
-  Compatibility Standard] is a kernel module which lets you run SCO,
-  Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
-  and is often needed to run commercial software, most prominently
-  WordPerfect. It's in tsx-11.mit.edu:/pub/linux/BETA). If you only
-  intend to mount files from some other Unix over the network using
-  NFS, you don't need the System V 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" or
-  preferably "info tar").  Note also that this option has nothing
+  from their floppies and hard disk partitions. 
+
+  If you have a floppy or hard disk partition like that, it is likely
+  that they contain binaries from those other Unix systems; in order
+  to run these binaries, you will want to install iBCS2 (iBCS2 [Intel
+  Binary Compatibility Standard] is a kernel module which lets you run
+  SCO, Xenix, Wyse, UnixWare, Dell Unix and System V programs under
+  Linux and is often needed to run commercial software that's only
+  available for those systems. It's available via ftp (user:
+  anonymous) from ftp://tsx-11.mit.edu/pub/linux/BETA).
+
+  If you only intend to mount files from some other Unix over the
+  network using NFS, you don't need the System V 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" 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.
+  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.
 
 Amiga FFS filesystem support
 CONFIG_AFFS_FS
-  If you say Y here, you will be able to mount floppies and hard drive
-  partitions which were formatted with the Amiga FFS filesystem. Full
-  read-write support is available for most versions of FFS, see
-  Documentation/filesystems/affs.txt for details. This filesystem
-  support is also available as a module ( = code which can be inserted
-  in and removed from the running kernel whenever you want). The
-  module is called affs.o. If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  The Fast File System (FFS) is the common filesystem used on hard
+  disks by Amiga(tm) Systems since AmigaOS Version 1.3 (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 hard drive. Amiga floppies however cannot be
+  read with this driver due to an incompatibility of the floppy
+  controller used in an Amiga and the standard floppy controller in
+  PCs and workstations. Read 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.
 
 Apple Macintosh filesystem support (experimental)
 CONFIG_HFS_FS
   If you say Y here, you will be able to mount Macintosh-formatted
   floppy disks and hard drive partitions with full read-write access.
   Please read fs/hfs/HFS.txt to learn about the available mount
-  options. This filesystem support is also available as a module ( =
-  code which can be inserted in and removed from the running kernel
-  whenever you want). The module is called hfs.o. If you want to
-  compile it as a module, say M here and read
-  Documentation/modules.txt.
+  options. 
+
+  This filesystem support is also available as a module ( = code which
+  can be inserted in and removed from the running kernel whenever you
+  want). The module is called hfs.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 ROM filesystem support
 CONFIG_ROMFS_FS
   This is a very small read-only filesystem mainly intended for
   initial ram disks of installation disks, but it could be used for
   other read-only media as well. Read
-  Documentation/filesystems/romfs.txt for details. This filesystem
-  support is also available as a module ( = code which can be inserted
-  in and removed from the running kernel whenever you want). The
-  module is called romfs.o. If you want to compile it as a module, say
-  M here and read Documentation/modules.txt. If you don't know whether
-  you need it, then you don't need it: say N.
+  Documentation/filesystems/romfs.txt for details. 
+
+  This filesystem support is also available as a module ( = code which
+  can be inserted in and removed from the running kernel whenever you
+  want). The module is called romfs.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt. 
+
+  If you don't know whether you need it, then you don't need it: say
+  N.
 
 Kernel automounter support
 CONFIG_AUTOFS_FS
   The automounter is a tool to automatically mount remote filesystems
   on demand.  This implementation is partially kernel-based to reduce
   overhead in the already-mounted case; this is unlike the BSD
-  automounter (amd), which is only in user space.  To use the
-  automounter you need the user-space tools from
-  ftp.kernel.org:/pub/linux/daemons/autofs; you also want to say Y to
-  "NFS filesystem support", above.  If you want to compile this as a
-  module ( = code which can be inserted in and removed from the
-  running kernel whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called autofs.o.
+  automounter (amd), which is only in user space.  
+
+  To use the automounter you need the user-space tools from
+  ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to say Y to
+  "NFS filesystem support", above. 
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called autofs.o. 
+
   If you are not a part of a fairly large, distributed network, you
   probably do not need an automounter, and can say N here.
 
 BSD UFS filesystem support (read only)
 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 hard disk 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" 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 and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
+  OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
+  Unixes can create and mount hard disk 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" or
+  preferably "info tar"). 
+
+  When accessing NeXTstep files, you may need to convert them from the
+  NeXT character set to the Latin1 character set; use the program
+  recode ("info recode") for this purpose. 
+
+  If you want to compile 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
@@ -5370,27 +5943,41 @@
 
 Solaris (x86) partition table support
 CONFIG_SOLARIS_X86_PARTITION
-  Say Y here if you have a hard drive that will be accessed from Linux
-  and from Solaris x86. This is NOT for Solaris on the sparc
-  architecture. 
+  Like most systems, Solaris x86 uses its own hard disk partition
+  table format, incompatible with all others. Saying Y here allows you
+  to read these partition tables and further mount Solaris x86 disks
+  read-only from within Linux if you have also said Y to "BSD ufs
+  filesystem support", above.
 
 ADFS filesystem support (read only) (EXPERIMENTAL)
 CONFIG_ADFS_FS
   Acorn Disc Filing System is the standard filesystem of the Risc OS
-  operating system which runs on Acorn's StrongARM Risc PC computers.
+  operating system which runs on Acorn's ARM based Risc PC computers.
   If you say Y here, Linux will be able to read from ADFS partitions
-  on hard drives and from ADFS-formatted floppy disks. This code is
-  also available as a module called adfs.o ( = code which can be
-  inserted in and removed from the running kernel whenever you want).
-  If you want to compile it as a module, say M here and read
+  on hard drives and from ADFS-formatted floppy disks. 
+
+  This code is also available as a module called adfs.o ( = code which
+  can be inserted in and removed from the running kernel whenever you
+  want). If you want to compile it as a module, say M here and read
   Documentation/modules.txt.
 
-/dev/pts filesystem
+/dev/pts filesystem (experimental)
 CONFIG_DEVPTS_FS
-  A filesystem which when mounted on /dev/pts and used in conjunction
-  with the /dev/ptmx multiplexing pty device, should allow full
-  support for Unix98 pty's without requiring setuid or daemons.  glibc
-  2.1 contains the requisite support for this mode of operation.
+  If you say Y here, you'll get a virtual filesystem which can be
+  mounted on /dev/pts with "mount -t devpts". This, together with the
+  pseudo terminal master multiplexer /dev/ptmx is used for pseudo
+  terminal support as described in the Open Group's Unix98 standard:
+  in order to acquire a pseudo terminal, a process opens /dev/ptmx;
+  the number of the pseudo terminal is then made available to the
+  process and the pseudo terminal slave can be accessed as
+  /dev/pts/<number>. What was traditionally /dev/ttyp2 will then be
+  /dev/pts/2, for example. The GNU C library glibc 2.1 contains the
+  requisite support for this mode of operation.
+
+  This code is also available as a module called devpts.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.
 
 Macintosh partition map support
 CONFIG_MAC_PARTITION
@@ -5408,47 +5995,55 @@
   if the Windows machines use TCP/IP as the underlying transport
   protocol, and not Netbeui. For details, read
   Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available via
-  ftp (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  ftp (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
   Note: if you just want your box to act as an SMB *server* and make
   files and printing services available to Windows clients (which need
   to have a TCP/IP stack), you don't need to say Y here; you can use
   the program samba (available via ftp (user: anonymous) in
-  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
-  program like lynx or netscape). If you want to compile the SMB
-  support as a module ( = code which can be inserted in and removed
-  from the running kernel whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called smbfs.o. Most
-  people say N, however.
+  ftp://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://www.eats.com/linux_mac_win.html (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 the SMB support as a module ( = code which
+  can be inserted in and removed from the running kernel whenever you
+  want), say M here and read Documentation/modules.txt. The module
+  will be called smbfs.o. Most people say N, however.
+
+SMB Win95 bug work-around
+CONFIG_SMB_WIN95
+  If you want to connect to a share exported by Windows 95, you should
+  say Y here. The Windows 95 server contains a bug that makes listing
+  directories unreliable. This option slows down the listing of
+  directories. This makes the Windows 95 server a bit more stable.
 
 Coda filesystem support
 CONFIG_CODA_FS
-  CODA is an advanced network filesystem, similar to NFS in that it
+  Coda is an advanced network filesystem, similar to NFS in that it
   enables you to mount filesystems of a remote server and access them
   with regular Unix commands as if they were sitting on your hard
-  disk. 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
+  disk. Coda has several advantages over NFS: support for disconnected
+  operation for laptops, read/write server replication, security model
+  for authentication and encryption, persistent client caches and
+  write back caching.
+
+  If you say Y here, your Linux box will be able to act as a Coda
+  *client*. You will need user level code as well, both for the client
+  and server. Servers are currently user level, i.e. need no kernel
+  support. For technical information, read
+  Documentation/filesystems/coda.txt. 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
-  If you want to connect to a share exported by Windows 95, you should
-  say Y here. The Windows 95 server contains a bug that makes listing
-  directories unreliable. This option slows down the listing of
-  directories. This makes the Windows 95 server a bit more stable.
+  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. 
 
 NCP filesystem support (to mount NetWare volumes)
 CONFIG_NCP_FS
@@ -5458,11 +6053,20 @@
   mount NetWare file server volumes and to access them just like any
   other Unix directory. For details, please read the file
   Documentation/filesystems/ncpfs.txt in the kernel source and the
-  IPX-HOWTO on 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. The module will be called
-  ncpfs.o. Say N unless you are connected to a Novell network.
+  IPX-HOWTO on sunsite.unc.edu:/pub/Linux/docs/howto.
+
+  You do not have to say Y here if you want your Linux box to act as a
+  file *server* for Novell NetWare clients.
+
+  General information about how to connect Linux, Windows machines and
+  Macs is on the WWW at http://www.eats.com/linux_mac_win.html (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 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 ncpfs.o. Say N unless you are connected to a Novell network.
 
 Packet signatures
 CONFIG_NCPFS_PACKET_SIGNING
@@ -5501,6 +6105,7 @@
   also subdirectories from a volume. It can be used to reexport data
   and so on. There is no reason to say N, so Y is recommended unless
   you count every byte.
+
   To utilize this feature you must use ncpfs-2.0.12 or newer.
 
 NDS interserver authentication domains
@@ -5512,44 +6117,28 @@
   servers. Do not say Y if security is primary for you because root
   can read your session key (from /proc/kcore).
 
-Amiga FFS filesystem support
-CONFIG_AFFS_FS
-  The Fast File System (FFS) is the common filesystem used on hard
-  disks by Amiga(tm) Systems since AmigaOS Version 1.3 (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 hard drive. Amiga floppies however cannot be
-  read with this driver due to an incompatibility of the floppy
-  controller used in an Amiga and the standard floppy controller in
-  PCs and workstations. Read 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.
-
 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.
+  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 translate the FAT filenames, not the contents of the
+  files.
 
 nls codepage 437
 CONFIG_NLS_CODEPAGE_437
@@ -5855,83 +6444,99 @@
 Standard/generic serial support
 CONFIG_SERIAL
   This selects whether you want to include the driver for the standard
-  serial ports.  People who might say N here are those that are
-  setting up dedicated Ethernet WWW/ftp servers, or users that have
-  one of the various bus mice instead of a serial mouse.  (Note that
-  the Cyclades and Stallion multi serial port drivers do not need this
-  driver built in for them to work.)  If you want to compile this
-  driver as a module, say M here and read
-  Documentation/modules.txt. The module will be called
-  serial.o. [WARNING: Do not compile this driver as a module if you
-  are using non-standard serial ports, since the configuration
-  information will be lost when kerneld automatically unloads the
-  driver.  This limitation may be lifted in the future.] BTW: If you
-  have a mouseman serial mouse which is not recognized by the X window
-  system, try running gpm first.  Most people will say Y or M here, so
-  that they can use serial mice, modems and similar devices connecting
-  to the standard serial ports.
+  serial ports. The standard answer is Y. People who might say N here
+  are those that are setting up dedicated Ethernet WWW/ftp servers, or
+  users that have one of the various bus mice instead of a serial
+  mouse and don't intend to use their machine's standard serial port
+  for anything. (Note that the Cyclades and Stallion multi serial port
+  drivers do not need this driver built in for them to work.)
+
+  If you want to compile this driver as a module, say M here and read
+  Documentation/modules.txt. The module will be called serial.o.
+  [WARNING: Do not compile this driver as a module if you are using
+  non-standard serial ports, since the configuration information will
+  be lost when kerneld automatically unloads the driver. This
+  limitation may be lifted in the future.] 
+
+  BTW: If you have a mouseman serial mouse which is not recognized by
+  the X window system, try running gpm first. 
+
+  Most people will say Y or M here, so that they can use serial mice,
+  modems and similar devices connecting to the standard serial ports.
 
 Support for console on serial port
 CONFIG_SERIAL_CONSOLE
   If you say Y here, it 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.
+  command line option such as "console=ttyS1". (Try "man bootparam" or
+  see the documentation of your boot loader (lilo or loadlin) about
+  how to pass options to the kernel at boot time. The lilo procedure
+  is also explained in the SCSI-HOWTO, available via ftp (user:
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) 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
   This is a driver for the Comtrol Rocketport cards which provide
   multiple serial ports.  You would need something like this to
-  connect more than two modems to your linux box, for instance in
-  order to become a BBS.If you want to compile this driver as a
-  module, say M here and read Documentation/modules.txt. The module
-  will be called rocket.o.
+  connect more than two modems to your Linux box, for instance in
+  order to become a BBS. 
+
+  If you want to compile this driver as a module, say M here and read
+  Documentation/modules.txt. The module will be called rocket.o.
 
 Digiboard Intelligent async support
 CONFIG_DIGIEPCA
   This is a driver for Digi International's Xx, Xeve, and Xem series
   of cards which provide multiple serial ports.  You would need
-  something like this to connect more than two modems to your linux
+  something like this to connect more than two modems to your Linux
   box, for instance in order to become a BBS. This driver supports the
   original PC (ISA) boards as well as PCI, and EISA.  If you have a
   card like this, say Y here and read the file
-  Documentation/digiepca.txt.  NOTE: There is another, separate driver
-  for the Digiboard PC boards: "Digiboard PC/Xx Support" below. You
-  should (and can) only select one of the two drivers. If you want to
-  compile this driver as a module, say M here and read
+  Documentation/digiepca.txt.  
+
+  NOTE: There is another, separate driver for the Digiboard PC boards:
+  "Digiboard PC/Xx Support" below. You should (and can) only select
+  one of the two drivers. 
+
+  If you want to compile this driver as a module, say M here and read
   Documentation/modules.txt. The module will be called epca.o.
 
 Digiboard PC/Xx Support
 CONFIG_DIGI
   This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
   that give you many serial ports. You would need something like this
-  to connect more than two modems to your linux box, for instance in
+  to 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/digiboard.txt. If you want to compile
-  this driver as a module, say M here and read
+  read the file Documentation/digiboard.txt. 
+
+  If you want to compile this driver as a module, say M here and read
   Documentation/modules.txt. The module will be called pcxx.o.
 
 SDL RISCom/8 card support
 CONFIG_RISCOM8
   This is a driver for the SDL Communications RISCom/8 multiport card,
   which gives you many serial ports. You would need something like
-  this to connect more than two modems to your linux box, for instance
+  this to 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/riscom8.txt. Also it's possible to
-  say M here and compile this driver as kernel loadable module; the
-  module will be called riscom8.o.
+  and read the file Documentation/riscom8.txt. 
+
+  Also it's possible to say M here and compile this driver as kernel
+  loadable module; the module will be called riscom8.o.
 
 Specialix IO8+ card support
 CONFIG_SPECIALIX
   This is a driver for the Specialix IO8+ multiport card, that give 
   you many serial ports. You would need something like this to 
-  connect more than two modems to your linux box, for instance in
-  order to become a 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 which will
-  be called specialix.o.
+  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 which will be called
+  specialix.o.
 
 Specialix DTR/RTS pin is RTS
 CONFIG_SPECIALIX_RTSCTS
@@ -5945,19 +6550,24 @@
 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. For
+  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.)
+  drivers/char/README.cycladesZ. 
+
+  As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
+  of 32.
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called cyclades.o. 
+
+  If you haven't heard about it, it's safe to say N.
 
 Stallion multiport serial support 
 CONFIG_STALDRV
   Stallion cards give you many serial ports. You would need something
-  like this to connect more than two modems to your linux box, for
+  like this to connect more than two modems to your Linux box, for
   instance in order to become a BBS. If you say Y here, you will be
   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
@@ -5967,28 +6577,33 @@
 CONFIG_STALLION
   If you have an EasyIO or EasyConnection 8/32 multiport Stallion
   card, then this is for you; say Y. Make sure to read
-  Documentation/stallion.txt. If you want to compile this as a
-  module ( = code which can be inserted in and removed from the
-  running kernel whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called stallion.o.
+  Documentation/stallion.txt. 
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called stallion.o.
 
 Stallion EC8/64, ONboard, Brumby support
 CONFIG_ISTALLION
   If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
   serial multiport card, say Y here. Make sure to read
-  Documentation/stallion.txt. To compile it as a module ( = code
-  which can be inserted in and removed from the running kernel
-  whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called istallion.o.
+  Documentation/stallion.txt. 
+
+  To compile it as a module ( = code which can be inserted in and
+  removed from the running kernel whenever you want), say M here and
+  read Documentation/modules.txt. The module will be called
+  istallion.o.
 
 Hayes ESP serial port support
 CONFIG_ESPSERIAL
   This is a driver which supports Hayes ESP serial ports.  It uses DMA
   to transfer data to and from the host.  Make sure to read
-  Documentation/hayes-esp.txt. To compile this driver as a module ( = code
-  which can be inserted in and removed from the running kernel
-  whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called esp.o.
+  Documentation/hayes-esp.txt. 
+
+  To compile this driver as a module ( = code which can be inserted in
+  and removed from the running kernel whenever you want), say M here
+  and read Documentation/modules.txt. The module will be called esp.o.
   If unsure, say N.
 
 Hayes ESP serial port DMA channel
@@ -5999,16 +6614,17 @@
 
 Hayes ESP serial port receive trigger level
 CONFIG_ESPSERIAL_RX_TRIGGER
-  This is the trigger level (in bytes) of the receive FIFO.  Larger
-  values may result in fewer interrupts; however, a value too high
-  could result in data loss.  Valid values are 1 through 1023.
+  This is the trigger level (in bytes) of the receive FIFO. Larger
+  values may result in fewer interrupts and hence better performance;
+  however, a value too high could result in data loss. Valid values
+  are 1 through 1023.
 
 Hayes ESP serial port transmit trigger level
 CONFIG_ESPSERIAL_TX_TRIGGER
-  This is the trigger level (in bytes) of the transmit FIFO.  Larger
-  values may result in fewer interrupts; however, a value too high
-  could result in degraded transmit performance.  Valid values are 1
-  through 1023.
+  This is the trigger level (in bytes) of the transmit FIFO. Larger
+  values may result in fewer interrupts and hence better performance;
+  however, a value too high could result in degraded transmit
+  performance. Valid values are 1 through 1023.
 
 Hayes ESP serial port flow off level
 CONFIG_ESPSERIAL_FLOW_OFF
@@ -6038,23 +6654,29 @@
   box (as opposed to using a serial printer; if the connector at the
   printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
   read the Printing-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.  It is possible to share one
-  parallel port among several devices (e.g. printer and ZIP drive) and
-  it is safe to compile the corresponding drivers into the kernel. If
-  you want to compile this driver as a module however ( = code which
-  can be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called lp.o.  If you have several parallel ports, you should
-  specify the base address for the port to be used by the printer with
-  the "lp" kernel command line option. (Try "man bootparam" or see the
-  documentation of your boot loader (lilo or loadlin) about how to
-  pass options to the kernel at boot time. The lilo procedure is also
-  explained in the SCSI-HOWTO, available via ftp (user: anonymous) in
-  sunsite.unc.edu:/pub/Linux/docs/HOWTO.) The standard base addresses
-  as well as the syntax of the "lp" command line option can be found
-  in drivers/char/lp.c. If you have more than 3 printers, you need to
-  increase the LP_NO variable in lp.c.
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  It is possible to share one parallel port among several devices
+  (e.g. printer and ZIP drive) and it is safe to compile the
+  corresponding drivers into the kernel. If you want to compile this
+  driver as a module however ( = code which can be inserted in and
+  removed from the running kernel whenever you want), say M here and
+  read Documentation/modules.txt. The module will be called lp.o. 
+
+  If you have several parallel ports, you should specify the base
+  address for the port to be used by the printer with the "lp" kernel
+  command line option. (Try "man bootparam" or see the documentation
+  of your boot loader (lilo or loadlin) about how to pass options to
+  the kernel at boot time. The lilo procedure is also explained in the
+  SCSI-HOWTO, available via ftp (user: anonymous) in
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) The standard base
+  addresses as well as the syntax of the "lp" command line option can
+  be found in drivers/char/lp.c.
+
+  If you have more than 3 printers, you need to increase the LP_NO
+  variable in lp.c.
 
+Support IEEE1284 status readback
 CONFIG_PRINTER_READBACK
   If your printer conforms to IEEE 1284, it may be able to provide a
   status indication when you read from it (for example, with `cat
@@ -6067,13 +6689,16 @@
   Microsoft mouse (made by Logitech) that plugs into a COM port
   (rectangular with 9 or 25 pins). These people say N here. If you
   have something else, read the Busmouse-HOWTO, available via ftp
-  (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO and say Y
-  here. If you have a laptop, you either have to check the
-  documentation or experiment a bit to find out whether the trackball
-  is a serial mouse or not; it's best to say Y here for you. 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 non-serial mice.  If unsure, say Y.
+  (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and
+  say Y here.
+
+  If you have a laptop, you either have to check the documentation or
+  experiment a bit to find out whether the trackball is a serial mouse
+  or not; it's best to say Y here for you. 
+
+  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 non-serial mice. If unsure, say Y.
 
 Logitech busmouse support
 CONFIG_BUSMOUSE
@@ -6082,12 +6707,13 @@
   made by Logitech don't use the Logitech protocol anymore; for those,
   you don't need this option. You want to read the Busmouse-HOWTO,
   available via ftp (user: anonymous) in
-  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. The module will be called busmouse.o. If
-  you are unsure, say N and read the HOWTO nevertheless: it will tell
-  you what you have.
+  ftp://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. The module will be
+  called busmouse.o. If you are unsure, say N and read the HOWTO
+  nevertheless: it will tell you what you have.
 
 PS/2 mouse (aka "auxiliary device") support
 CONFIG_PSMOUSE
@@ -6097,15 +6723,16 @@
   for other input devices like light pens, tablets, keypads. Compaq,
   AST and IBM all use this as their mouse port on currently shipping
   machines. The trackballs of some laptops are PS/2 mice also. In
-  particular, the C&T 82C710 mouse on TI Travelmates is a PS/2
-  mouse. Although PS/2 mice are not technically bus mice, they are
-  explained in detail in the Busmouse-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.  When using a
-  PS/2 mouse, you can get problems if you want to use the mouse both
-  on the Linux console and under X. Using the "-R" option of the Linux
-  mouse managing program gpm (available from
+  particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
+  Although PS/2 mice are not technically bus mice, they are explained
+  in detail in the Busmouse-HOWTO, available via ftp (user: anonymous)
+  in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. When using a PS/2
+  mouse, you can get problems if you want to use the mouse both on the
+  Linux console and under X. Using the "-R" option of the Linux mouse
+  managing program gpm (available from
   sunsite.unc.edu:/pub/Linux/system/Daemons) solves this problem, or
   you can get the "mconv" utility also from sunsite.
+
   If you want to compile this mouse 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
@@ -6117,7 +6744,7 @@
   This is a certain kind of PS/2 mouse used on the TI Travelmate. If
   you are unsure, try first to say N here and come back if the mouse
   doesn't work. Read the Busmouse-HOWTO, available via ftp (user:
-  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+  anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
 
 PC110 digitizer pad support
 CONFIG_PC110_PAD
@@ -6125,36 +6752,44 @@
   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.
+  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
   These animals (also called Inport mice) are connected to an
   expansion board using a round connector with 9 pins. If this is what
   you have, say Y and read the Busmouse-HOWTO, available via ftp
-  (user: anonymous) in 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. The module will be called
-  msbusmouse.o. If you are unsure, say N and read the HOWTO
-  nevertheless: it will tell you what you have. Also be aware that
-  several vendors talk about 'Microsoft busmouse' and actually mean
-  PS/2 busmouse - so count the pins on the connector.
+  (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+  If you are unsure, say N and read the HOWTO nevertheless: it will
+  tell you what you have. Also be aware that several vendors talk
+  about 'Microsoft busmouse' and actually mean PS/2 busmouse - so
+  count the pins on the connector.
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called msbusmouse.o. 
 
 ATIXL busmouse support
 CONFIG_ATIXL_BUSMOUSE
   This is a rare type of busmouse that is connected to the back of an
   ATI video card. Note that most ATI mice are actually Microsoft
   busmice. Read the Busmouse-HOWTO, available via ftp (user:
-  anonymous) in 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. The module will be called
-  atixlmouse.o. If you are unsure, say N and read the HOWTO
-  nevertheless: it will tell you what you have.
+  anonymous) in ftp://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. The module will be
+  called atixlmouse.o. 
+
+  If you are unsure, say N and read the HOWTO nevertheless: it will
+  tell you what you have.
 
 Support for user miscellaneous modules
 CONFIG_UMISC
@@ -6180,29 +6815,36 @@
   to configure this driver during runtime. The program to do this is
   called 'qic02conf' and it is part of the 'tpqic02-support-X.Y.tar.gz'
   support package.
+
   If you want to use the qic02conf program, say Y.
 
 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
 CONFIG_FTAPE
   If you have a tape drive that is connected to your floppy
-  controller, say Y here. Some tape drives (like the Seagate "Tape
-  Store 3200" or the Iomega "Ditto 3200" or the Exabyte "Eagle TR-3")
-  come with a "high speed" controller of their own. These drives (and
-  their companion controllers) are also supported if you say Y here.
+  controller, say Y here. 
+
+  Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
+  "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
+  controller of their own. These drives (and their companion
+  controllers) are also supported if you say Y here. 
+
   If you have a special controller (such as the CMS FC-10, FC-20,
   Mountain Mach-II, or any controller that is based on the Intel 82078
   FDC like the high speed controllers by Seagate and Exabyte and
   Iomega's "Ditto Dash") you must configure it by selecting the
   appropriate entries from the "Floppy tape controllers" sub-menu
   below and possibly modify the default values for the IRQ and DMA
-  channel and the IO base in ftape's configuration menu. If you want
-  to use your floppy tape drive on a PCI-bus based system, please read
-  the file drivers/char/ftape/README.PCI.
+  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. The module
-  will be called ftape.o.
+  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
@@ -6218,15 +6860,18 @@
 CONFIG_ZFTAPE
   Normally, you want to say Y or M. DON'T say N here or you
   WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
+
   The ftape module itself no longer contains the routines necessary
   to interface with the kernel VFS layer (i.e. to actually write data
   to and read data from the tape drive). Instead the file system
   interface (i.e. the hardware independent part of the driver) has
   been moved to a separate module.
+
   If you say M zftape will be compiled as a runtime loadable
   module ( = code which can be inserted in and removed from the
   running kernel whenever you want). In this case you should read
   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
@@ -6234,6 +6879,7 @@
   kernel module loader (i.e. have said Y to "Kernel module loader
   support", above) then `zft-compressor.o' will be loaded
   automatically by zftape when needed.
+
   Despite its name, zftape does NOT use compression by default. The
   file Documentation/ftape.txt contains a short description of the
   most important changes in the file system interface compared to
@@ -6241,6 +6887,7 @@
   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
@@ -6253,6 +6900,7 @@
   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
   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
@@ -6260,6 +6908,7 @@
   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),
   `5120' (afio's default block size), `32768' (default block size some
   backup programs assume for SCSI tape drives) or `1' (no restriction
@@ -6277,15 +6926,16 @@
 
 Procfs entry for ftape
 CONFIG_FT_PROC_FS
-  Optional. Saying `Y' will result in creation of a directory
+  Optional. Saying Y will result in creation of a directory
   `/proc/ftape' under the proc file system. The 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
   file will contain some status information about the inserted
   cartridge, the kernel driver, your tape drive, the floppy disk
   controller and the error history for the most recent use of the
-  kernel driver. Saying `Y' will enlarge the size of the ftape driver
+  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
   "Floppy tape drive") it is dangerous to use ftape's proc file system
   interface. Accessing `/proc/ftape' while the module is unloaded will
@@ -6297,10 +6947,12 @@
   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
   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
   recommended: leave this option at its default setting "Normal" until
   you know that the driver works as expected, afterwards reconfigure
@@ -6309,6 +6961,7 @@
   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
   how to control the amount of debugging output.
 
@@ -6319,6 +6972,7 @@
   plugged the floppy tape cable into the already existing floppy drive
   controller then you don't want to change the default setting,
   i.e. choose "Standard".
+
   Choose "MACH-2" if you have a Mountain Mach-2 controller.
   Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
   controller.
@@ -6329,19 +6983,23 @@
   `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
   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
   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
   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 "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
@@ -6363,11 +7021,13 @@
   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
   the IO base. The hardware configuration can be changed at boot 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.
@@ -6387,11 +7047,13 @@
   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
   the IRQ channel. The hardware configuration can be changed at boot
   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.
@@ -6411,11 +7073,13 @@
   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
   the DMA channel. The hardware configuration can be changed at boot
   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.
@@ -6428,6 +7092,7 @@
   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 effect.
+
   If unsure, don't touch the initial value, i.e. leave it at "8".
 
 FDC maximum data rate
@@ -6437,6 +7102,7 @@
   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
   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
@@ -6444,13 +7110,13 @@
 
 MTRR control and configuration
 CONFIG_MTRR
-  On Intel Pentium Pro systems the Memory Type Range Registers (MTRRs)
-  may be used to control processor access to memory ranges. This is
-  most useful when you have a video (VGA) card on the PCI
-  bus. Enabling write-combining allows PCI write transfers to be
-  combined into a larger transfer before bursting over the PCI
-  bus. This can increase performance of image write operations 2.5
-  times or more.
+  On Intel Pentium Pro/Pentium II systems the Memory Type Range
+  Registers (MTRRs) may be used to control processor access to memory
+  ranges. This is most useful when you have a video (VGA) card on a
+  PCI or AGP bus. Enabling write-combining allows bus write transfers
+  to be combined into a larger transfer before bursting over the
+  PCI/AGP bus. This can increase performance of image write operations
+  2.5 times or more.
   This option creates a /proc/mtrr file which may be used to manipulate
   your MTRRs. Typically the X server should use this. This should have
   a reasonably generic interface so that similar control registers on
@@ -6458,10 +7124,9 @@
   This option also fixes a problem with buggy SMP BIOSes which only
   set the MTRRs for the boot CPU and not the secondary CPUs. This can
   lead to all sorts of problems.
-  In general you should compile this into the kernel, rather than as a
-  loadable module, because the BIOS fix needs to be done early in the
-  boot sequence. If you compile this as a module, the BIOS fix will be
-  delayed until when you load the module. You do this at your own risk.
+  Compiling this as a module is not available because the BIOS fix
+  needs to be done early in the boot sequence, otherwise your machine
+  could lock up.
   See Documentation/mtrr.txt for more information.
 
 Main CPU frequency, only for DEC alpha machine
@@ -6478,34 +7143,44 @@
 Advanced Power Management
 CONFIG_APM
   APM is a BIOS specification for saving power using several different
-  techniques.  This is mostly useful for battery powered laptops with
-  APM compliant BIOSes.  Specifically, the time will be reset after a
-  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 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 the hdparm(8) manpage
-  ("man 8 hdparm") 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).
+  techniques. This is mostly useful for battery powered laptops with
+  APM compliant BIOSes. If you say Y here, the system time will be
+  reset after a 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 is available; for more information, read the
+  Battery Powered Linux mini-HOWTO, available via ftp (user:
+  anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini.
+
+  This driver does not spin down disk drives (see the hdparm(8)
+  manpage ("man 8 hdparm") 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). 
+
   If you are running Linux on a laptop, you may also want to read the
   Linux Laptop homepage on the WWW at
   http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
   WWW, you need to have access to a machine on the Internet that has a
-  program like lynx or netscape).
+  program like lynx or netscape). 
+
   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
+  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:
+  anything, try disabling/enabling this option (or disabling/enabling
+  APM in your BIOS). 
+
+  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 
+   2) switching on floating point emulation in the kernel and passing
+      the "no387" option to the kernel
    3) passing the "floppy=nodma" option to the kernel
    4) passing the "mem=4M" option to the kernel (thereby disabling 
       all but the first 4M of RAM)
@@ -6583,20 +7258,22 @@
   If you say Y here (and to one of the following options) and create a
   character special file /dev/watchdog with major number 10 and minor
   number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
-  subsequently opening the file and failing to write to it for longer
-  than 1 minute will result in rebooting the machine. This could be
-  useful for a networked machine that needs to come back online as
-  fast as possible after a lock-up. There's both a watchdog
+  subsequently opening the file and then failing to write to it for
+  longer than 1 minute will result in rebooting the machine. This
+  could be useful for a networked machine that needs to come back
+  online as fast as possible after a lock-up. There's both a watchdog
   implementation entirely in software (which can sometimes fail to
   reboot the machine) and a driver for hardware watchdog boards, which
   are more robust and can also keep track of the temperature inside
   your computer. For details, read Documentation/watchdog.txt in the
   kernel source.
+
   The watchdog is usually used together with the watchdog daemon which
   is available via ftp (user: anonymous) from
-  tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also monitor
-  NFS connections and can reboot the machine when the process table is
-  full.
+  ftp://tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also
+  monitor NFS connections and can reboot the machine when the process
+  table is full.
+
   If unsure, say N.
 
 Disable watchdog shutdown on close
@@ -6612,10 +7289,12 @@
   If you have a WDT500P or WDT501P watchdog board, say Y here,
   otherwise N. It is not possible to probe for this board, which means
   that you have to set the IO port and IRQ it uses in the kernel
-  source at the top of drivers/char/wdt.c. 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 wdt.o.
+  source at the top of drivers/char/wdt.c. 
+
+  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 wdt.o.
 
 WDT501 features
 CONFIG_WDT_501
@@ -6635,32 +7314,36 @@
 CONFIG_SOFT_WATCHDOG
   A software monitoring watchdog. This will fail to reboot your system
   from some situations that the hardware watchdog will recover
-  from. Equally it's a lot cheaper to install. 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 want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called softdog.o.
+  from. Equally it's a lot cheaper to install. 
+
+  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 want to compile it as a module, say M here and read
+  Documentation/modules.txt. The module will be called softdog.o.
 
 Berkshire Products PC Watchdog
 CONFIG_PCWATCHDOG
   This is the driver for the Berkshire Products PC Watchdog card.
   This card simply watches your kernel to make sure it doesn't freeze,
-  and if it does, it resets your computer after a certain amount of
+  and if it does, it reboots your computer after a certain amount of
   time.  This driver is like the WDT501 driver but for different
   hardware. Please read Documentation/pcwd-watchdog.txt. The PC
   watchdog cards can be ordered from http://www.berkprod.com. Some
-  example rc.local files are available from ftp.bitgate.com. 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 pcwd.o. If you want to compile it as a module, say
-  M here and read Documentation/modules.txt.  Most people will say N.
+  example rc.local files are available from ftp://ftp.bitgate.com. 
+
+  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 pcwd.o. If you want to compile it as a module,
+  say M here and read Documentation/modules.txt. Most people will say
+  N.
 
 Acquire SBC Watchdog Timer
 CONFIG_ACQUIRE_WDT
   This is the driver for the hardware watchdog on the PSC-6x86 Single
   Board Computer produced by Acquire Inc (and others). This watchdog
   simply watches your kernel to make sure it doesn't freeze, and if
-  it does, it resets your computer after a certain amount of time.
+  it does, it reboots your computer after a certain amount of time.
+
   This driver is like the WDT501 driver but for different hardware.
   This driver is also available as a module ( = code which can be 
   inserted in and removed from the running kernel whenever you want).
@@ -6677,13 +7360,15 @@
   used as a 24 hour alarm.  It reports status information via the file
   /proc/rtc and its behaviour is set by various ioctls on
   /dev/rtc. 
+
   People running SMP (= multiprocessor) versions of Linux should say Y
   here to read and set the RTC clock in a SMP compatible
-  fashion. (They should also Documentation/smp and
+  fashion. (They should also read Documentation/smp and
   Documentation/IO-APIC.txt and the SMP-FAQ on the WWW at
   http://www.irisa.fr/prive/mentre/smp-faq/ (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 think you 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.
@@ -6707,11 +7392,12 @@
   frequently save a few bits of very important data that may not be
   lost over power-off and for which writing to disk is too
   insecure. On Atari machines, /dev/nvram is always configured and
-  does not need to be selected.  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
-  nvram.o. If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  does not need to be selected.  
+
+  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 nvram.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 PC joystick support
 CONFIG_JOYSTICK
@@ -6721,11 +7407,12 @@
   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.
+  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.
 
 Sound card support
 CONFIG_SOUND
@@ -6734,10 +7421,11 @@
   about your sound card and its configuration down (I/O port,
   interrupt and DMA channel), because you will be asked for it. You
   want to read the Sound-HOWTO, available via ftp (user: anonymous)
-  from sunsite.unc.edu:/pub/Linux/docs/HOWTO. There is also some
+  from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. There is also some
   information in various README files in drivers/sound, esp. in
   Readme.cards which you should read first to find out whether your
   card is supported by Linux.
+
   If you have a PnP sound card and you want to configure it at boot
   time using the ISA PnP tools (read
   http://www.roestock.demon.co.uk/isapnptools/ (to browse the WWW, you
@@ -6748,11 +7436,11 @@
   after the PnP configuration is finished. To do this, say M here and
   read Documentation/modules.txt as well as
   drivers/sound/Readme.modules; the module will be called sound.o.
+
   I'm told that even without a sound card, you can make your computer
   say more than an occasional beep, by programming the PC speaker.
-  Kernel patches and programs to do that are at
-  sunsite.unc.edu:/pub/Linux/kernel/patches/console/pcsndrv-X.X.tar.gz,
-  to be extracted with "tar xzvf filename".
+  Kernel patches and programs to do that are in the pcsndrv package on
+  sunsite.unc.edu:/pub/Linux/kernel/patches/console/.
 
 ProAudioSpectrum 16 support
 CONFIG_PAS
@@ -6769,7 +7457,11 @@
   cards look at the card specific instructions in the
   drivers/sound/Readme.cards file before answering this question. For
   an unknown card you may answer Y if the card claims to be
-  SoundBlaster compatible. If you have an SB AWE 32 or SB AWE 64, say
+  SoundBlaster compatible. 
+
+  Please read Documentation/sound/Soundblaster.
+
+  If you have an SB AWE 32 or SB AWE 64, say
   Y here and to "Additional lowlevel drivers" and to "SB32/AWE
   support" below.
 
@@ -6778,20 +7470,8 @@
   The IBM Mwave can do what's loosely describable as emulation of an
   8bit SoundBlaster card if you load the right firmware from DOS warm
   boot and pray and your machine happens to like you. Say Y if you are
-  doing this as the IRQ test normally fails on the Mwave emulation. If
-  you'd like real MWAVE support phone IBM (425-556-8822) and ask them
-  why they still haven't released any documentation.
-  [http://204.200.238.31/cgi-bin/link.pl?co=i&cl=/ts/ibm/contact.html]
-
-Are you using the IBM Mwave "emulation" of SB ?
-CONFIG_SB_MWAVE
-  The IBM Mwave can do whats loosely describable as emulation of an 8bit
-  soundblaster if you load the right firmware from DOS warm boot and pray
-  and your machine happens to like you. Say Y if you are doing this as the
-  IRQ test normally fails on the mwave emulation. If you'd like real MWAVE
-  support phone IBM (425-556-8822) and ask them why they still haven't 
-  released any documentation.
-  [http://204.200.238.31/cgi-bin/link.pl?co=i&cl=/ts/ibm/contact.html]
+  doing this as the IRQ test normally fails on the Mwave emulation.
+  Please read Documentation/sound/mwave.
 
 Generic OPL2/OPL3 FM synthesizer support
 CONFIG_ADLIB
@@ -6801,16 +7481,17 @@
   these cards may cause trouble (I don't currently know of any such
   cards, however). If unsure, say Y.
 
-Loopback MIDI device support
-CONFIG_VMIDI
+#Loopback MIDI device support
+#CONFIG_VMIDI
 ###
 ### somebody please fill this in.
 ###
-
+#
 Gravis Ultrasound support
 CONFIG_GUS
   Say Y here for any type of Gravis Ultrasound card, including
-  the GUS or GUS MAX.
+  the GUS or GUS MAX. Please read Documentation/sound/ultrasound for
+  more information.
 
 MPU-401 support (NOT for SB16)
 CONFIG_MPU401
@@ -6829,12 +7510,18 @@
   UART chip. This interface is rarely found on sound cards.  It's safe
   to answer N to this question.
 
-PSS (ECHO-ADI2111) support
+PSS (AD1848, ADSP-2115, ESC614) support
 CONFIG_PSS
   Answer Y only if you have Orchid SW32, Cardinal DSP16 or some other
   card based on the PSS chipset (AD1848 codec + ADSP-2115 DSP chip +
   Echo ESC614 ASIC CHIP).
 
+#Enable PSS mixer (Beethoven ADSP-16 and other compatible)
+#CONFIG_PSS_MIXER
+###
+### Don't know what this is
+###
+#
 16 bit sampling option of GUS (_NOT_ GUS MAX)
 CONFIG_GUS16
   Answer Y if you have installed the 16 bit sampling daughtercard on
@@ -6851,6 +7538,7 @@
   safe to answer Y if you have the original Windows Sound System card
   made by Microsoft or Aztech SG 16 Pro (or NX16 Pro).  Also you may
   answer Y in case your card is NOT among these:
+
      ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
      Ensoniq SoundScape (and compatibles made by Reveal and Spea),
      Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
@@ -6864,6 +7552,7 @@
      Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
      notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
      synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
+
   For cards having native support in VoxWare, consult the card
   specific instructions in drivers/sound/Readme.cards. Some drivers
   have their own MSS support and saying Y to this option will cause a
@@ -6883,26 +7572,25 @@
 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 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).
+  82C928 or 82C929 or 82C931) audio interface chip. Please read
+  Documentation/sound/MAD16. Please read Documentation/sound/Opti. For
+  the 82C931, additional information is in 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 MIDI in older MAD16 based cards (requires SB)
 CONFIG_MAD16_OLDCARD
-  Answer Y (or M) if you have an older card based on the C928
-  or Mozart chipset and you want to have  MIDI support. If you
-  enable this option you also need to enable support for SoundBlaster.
-
- If you answer Y here you will
-  also need to enable the SoundBlaster driver.
+  Answer Y (or M) if you have an older card based on the C928 or
+  Mozart chipset and you want to have MIDI support. If you enable this
+  option you also need to enable support for SoundBlaster.
 
 Support for Crystal CS4232 based (PnP) cards
 CONFIG_CS4232
   Say Y here if you have a card based on the Crystal CS4232 chip set,
-  which use the Plug and Play protocol.
+  which use the Plug and Play protocol. Please read
+  Documentation/sound/CS4232 for more info.
 
 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
 CONFIG_MAUI
@@ -6923,7 +7611,8 @@
 
 FM synthesizer (YM3812/OPL-3) support
 CONFIG_YM3812
-  Answer Y here, unless you know you will not need the option.
+  Answer Y here, unless you know you will not need the option. For
+  OPL-3 cards, you may want to read Documentation/sound/OPL3.
 
 Sun Audio support
 CONFIG_SUN_AUDIO
@@ -6951,9 +7640,10 @@
 SB32/AWE support
 CONFIG_AWE32_SYNTH
   Say Y here if you have a SoundBlaster SB32, AWE32-PnP, SB AWE64 or
-  similar sound card. See drivers/sound/lowlevel/README.awe and the
-  Soundblaster-AWE mini-HOWTO, available via ftp (user: anonymous)
-  from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini for more info.
+  similar sound card. See drivers/sound/lowlevel/README.awe,
+  Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
+  available via ftp (user: anonymous) from
+  ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini for more info.
 
 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
 CONFIG_AEDSP16
@@ -6993,10 +7683,11 @@
   This is for kernel hackers who want to know how much time the kernel
   spends in the various procedures. The information is stored in
   /proc/profile (say Y to "/proc filesystem support"!) and in order to
-  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 (to browse the
+  read it, you need the readprofile package from
+  sunsite.unc.edu:/pub/Linux/kernel. 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 (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.
 
@@ -7009,14 +7700,13 @@
 
 Magic System Request Key support
 CONFIG_MAGIC_SYSRQ
-  This is for kernel hackers who want to have some control over the
-  system even if the system crashes during kernel debugging (e.g., to
-  flush the disks, reboot the system immediately or dump some status
-  information). This is accomplished by pressing various keys while
-  holding SysRq (Alt+PrintScreen). As you are expected to be a kernel
-  hacker to use this, the simple rule about learning what the keys
-  mean is "Use the source, Luke!" -- read drivers/char/sysrq.c.  
-  Don't say Y unless you really know what this hack does.
+  If you say Y here, you will have some control over the system even
+  if the system crashes for example during kernel debugging (e.g., you
+  will be able to flush the disks, reboot the system immediately or
+  dump some status information). This is accomplished by pressing
+  various keys while holding SysRq (Alt+PrintScreen). The keys are
+  documented in Documentation/sysrq.txt. Don't say Y unless you really
+  know what this hack does.
 
 ISDN subsystem
 CONFIG_ISDN
@@ -7030,31 +7720,33 @@
   provider purchased an ISDN line from the phone company.  For
   details, read http://alumni.caltech.edu/~dank/isdn/ 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.)  This driver allows you
-  to use an ISDN-card for networking connections and as dialin/out
-  device. The isdn-tty's have a built in AT-compatible modem
-  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 (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.
+  that has a program like lynx or netscape.)  
+
+  This driver allows you to use an ISDN-card for networking
+  connections and as dialin/out device. The isdn-tty's have a built in
+  AT-compatible modem 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
+  (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
   Over digital connections such as ISDN, there is no need to
   synchronize sender and recipient's clocks with start and stop bits
-  as is done over telephone lines. Instead, one can use "synchronous
-  PPP". Saying Y here will include this protocol. This protocol is
-  used by Cisco and Sun for example. So you want to say Y here if the
-  other end of your ISDN connection supports it. You will need a
-  special version of pppd (called ipppd) for using this feature. See
-  Documentation/isdn/README.syncppp and Documentation/isdn/syncPPP.FAQ
-  for more information.
+  as is done over analog telephone lines. Instead, one can use
+  "synchronous PPP". Saying Y here will include this protocol. This
+  protocol is used by Cisco and Sun for example. So you want to say Y
+  here if the other end of your ISDN connection supports it. You will
+  need a special version of pppd (called ipppd) for using this
+  feature. See Documentation/isdn/README.syncppp and
+  Documentation/isdn/syncPPP.FAQ for more information.
 
 Support generic MP (RFC 1717)
 CONFIG_ISDN_MPP
@@ -7065,6 +7757,7 @@
 Use VJ-compression with synchronous PPP
 CONFIG_ISDN_PPP_VJ
   This enables Van Jacobson header compression for synchronous PPP.
+  Say Y if the other end of the connection supports it.
 
 Support audio via ISDN
 CONFIG_ISDN_AUDIO
@@ -7079,9 +7772,9 @@
 
 X.25 PLP on top of ISDN (EXPERIMENTAL)
 CONFIG_ISDN_X25
-  This experimental feature provides X.25 over ISDN. See
-  Documentation/isdn/README.x25 for more information about how to
-  configure and what other options must be enabled for using X.25.
+  This experimental feature provides the X.25 protocol over ISDN
+  connections. See Documentation/isdn/README.x25 for more information
+  if you are thinking about using this.
 
 ICN 2B and 4B support
 CONFIG_ISDN_DRV_ICN
@@ -7091,14 +7784,16 @@
   this card, additional firmware is necessary, which has to be
   downloaded into the card using a utility which is distributed
   separately.  See Documentation/isdn/README and README.icn for more
-  information. If you want to compile this as a module ( = code which
-  can be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called icn.o.
+  information. 
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called icn.o.
 
 isdnloop support
 CONFIG_ISDN_DRV_LOOP
-  This driver provides a virtual ISDN card. It's primary purpose is
+  This driver provides a virtual ISDN card. Its primary purpose is
   testing of linklevel features or configuration without getting
   charged by your service-provider for lots of phone calls.
   You need will need the loopctrl utility from the latest isdn4k-utils
@@ -7109,11 +7804,19 @@
   This is a driver supporting the Siemens chipset on various
   ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
   S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
-  compatibles). 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 hisax.o.  See Documentation/isdn/README.HiSax for
-  further informations on using this driver.
+  compatibles). 
+
+  HiSax is just the name of this driver, not the name of any hardware.
+  
+  If you have a card with such a chipset, you should say Y here and
+  also to the configuration option of the driver for your particular
+  card, below.
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called hisax.o. See Documentation/isdn/README.HiSax for more
+  information on using this driver.
 
 HiSax Support for Teles 16.0/8.0
 CONFIG_HISAX_16_0
@@ -7129,21 +7832,21 @@
   the Teles/Creatix PnP and the Teles PCMCIA.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for Teles 16.3c
 CONFIG_HISAX_TELES3C
   This enables HiSax support for the Teles ISDN-cards 16.3c.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for AVM A1 (Fritz)
 CONFIG_HISAX_AVM_A1
   This enables HiSax support for the AVM A1 (aka "Fritz").
   See Documentation/isdn/README.HiSax on how to configure it
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for Elsa ISA cards
 CONFIG_HISAX_ELSA
@@ -7151,68 +7854,71 @@
   for the Elsa Quickstep series cards and Elsa PCMCIA.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for ITK ix1-micro Revision 2
 CONFIG_HISAX_IX1MICROR2
   This enables HiSax support for the ITK ix1-micro Revision 2 card.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for Eicon.Diehl Diva cards
 CONFIG_HISAX_DIEHLDIVA
   This enables HiSax support for the Eicon.Diehl Diva none PRO versions
   passive ISDN cards.
+
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for ASUSCOM cards
 CONFIG_HISAX_ASUSCOM
   This enables HiSax support for the AsusCom and their OEM versions
   passive ISDN cards.
+
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for TELEINT cards
 CONFIG_HISAX_TELEINT
   This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for Sedlbauer speed card/win-star
 CONFIG_HISAX_SEDLBAUER
   This enables HiSax support for the Sedlbauer passive ISDN cards.
   See Documentation/isdn/README.HiSax on how to configure it 
   using the different cards, a different D-channel protocol, or
-  non-standard irq/port settings.
+  non-standard IRQ/port settings.
 
 HiSax Support for USR Sportster internal TA
 CONFIG_HISAX_SPORTSTER
   This enables HiSax support for the USR Sportster internal TA card.
-  See Documentation/isdn/README.HiSax on how to configure it 
-  using a different D-channel protocol, or non-standard irq/port settings.
+  See Documentation/isdn/README.HiSax on how to configure it using a
+  different D-channel protocol, or non-standard IRQ/port settings.
 
 HiSax Support for MIC card
 CONFIG_HISAX_MIC
-  This enables HiSax support for the ITH MIC card.
-  See Documentation/isdn/README.HiSax on how to configure it 
-  using a different D-channel protocol, or non-standard irq/port settings.
+  This enables HiSax support for the ITH MIC card. See
+  Documentation/isdn/README.HiSax on how to configure it using a
+  different D-channel protocol, or non-standard IRQ/port settings.
 
 HiSax Support for NETjet card
 CONFIG_HISAX_NETJET
-  This enables HiSax support for the NetJet from Traverse Technologies.
-  See Documentation/isdn/README.HiSax on how to configure it 
-  using a different D-channel protocol, or non-standard irq/port settings.
+  This enables HiSax support for the NetJet from Traverse
+  Technologies. See Documentation/isdn/README.HiSax on how to
+  configure it using a different D-channel protocol, or non-standard
+  IRQ/port settings.
 
 HiSax Support for Niccy PnP/PCI card
 CONFIG_HISAX_NICCY
-  This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
-  See Documentation/isdn/README.HiSax on how to configure it 
-  using a different D-channel protocol, or non-standard irq/port settings.
+  This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. See
+  Documentation/isdn/README.HiSax on how to configure it using a
+  different D-channel protocol, or non-standard IRQ/port settings.
 
 HiSax Support for Am7930 (EXPERIMENTAL)
 CONFIG_HISAX_AMD7930
@@ -7221,45 +7927,57 @@
 
 HiSax Support for EURO/DSS1
 CONFIG_HISAX_EURO
-  You should choose the D-channel protocol your local
-  telephone service provider uses here by saying Y or N.
-  NOTE: This is mutually exclusive with HiSax Support for
-  German 1TR6 if you have only one ISDN card installed.
+  Say Y or N according to the D-channel protocol which your local
+  telephone service company provides.
+
+  NOTE: If you say Y here and you have only one ISDN card installed,
+  you cannot say Y to "HiSax Support for German 1TR6", below. And vice
+  versa.
 
-Support for german tarifinfo
+Support for German tariff info
 CONFIG_DE_AOC
-  If you want, that HiSax send messages to the linklevel on each
-  AOCD/AOCE, enable this. This works only in Germany.
+  If you want that the HiSax hardware driver sends messages to the
+  upper level of the isdn code on each AOCD (Advice Of Charge, During
+  the call - transmission of the fee information during a call) and on
+  each AOCE (Advice Of Charge, at the End of the call - transmission
+  of fee information at the end of the call), say Y here. This works
+  only in Germany.
 
-Support for australian Microlink service (not for std. EURO)
+Support for Australian Microlink service (not for std. EURO)
 CONFIG_HISAX_ML
-  If you are in Australia and connected on the Microlink telephone
-  network enable this, because here are little differences in protocol.
+  If you are in Australia and connected to the Microlink telephone
+  network, enable this, because there are little differences in
+  protocol.
+  
   Please don't enable this in other countries.
 
 HiSax Support for US/NI-1 (not released yet)
 CONFIG_HISAX_NI1
-  You should choose the D-channel protocol your local
-  telephone service provider uses here by saying Y or N.
+  Say Y or N according to the D-channel protocol which your local
+  telephone service company provides.
 
 HiSax Support for German 1TR6
 CONFIG_HISAX_1TR6
-  You should choose the D-channel protocol your local
-  telephone service provider uses here by saying Y or N.
-  NOTE: This is mutually exclusive with HiSax Support for
-  EURO/DSS1 if you have only one ISDN card installed.
+  Say Y or N according to the D-channel protocol which your local
+  telephone service company provides.
+
+  NOTE: If you say Y here and you have only one ISDN card installed,
+  you cannot say Y to "HiSax Support for EURO/DSS1", above. And vice
+  versa.
 
 PCBIT-D support
 CONFIG_ISDN_DRV_PCBIT
-  This enables support for the PCBIT ISDN-cards. This card is
+  This enables support for the PCBIT ISDN-card. This card is
   manufactured in Portugal by Octal. For running this card, additional
   firmware is necessary, which has to be downloaded into the card
   using a utility which is distributed separately.  See
   Documentation/isdn/README and Documentation/isdn/README.pcbit for
-  more information. If you want to compile this as a module ( = code
-  which can be inserted in and removed from the running kernel
-  whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called pcbit.o.
+  more information. 
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read Documentation/modules.txt. The module will be
+  called pcbit.o.
 
 Spellcaster support (EXPERIMENTAL)
 CONFIG_ISDN_DRV_SC
@@ -7282,11 +8000,12 @@
   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.
+  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
@@ -7296,7 +8015,7 @@
 
 IBM Active 2000 support (EXPERIMENTAL)
 CONFIG_ISDN_DRV_ACT2000
-  This enables support for IBM Active 2000 ISDN card. In order to use
+  Say Y here if you have an IBM Active 2000 ISDN card. In order to use
   this card, additional firmware is necessary, which has to be loaded
   into the card using a utility which is part of the latest isdn4k-utils
   package. Please read the file Documentation/isdn/README.act2000 for
@@ -7319,23 +8038,24 @@
 CONFIG_SUN_OPENPROMIO
   This driver provides user programs with an interface to the Sparc
   PROM device tree. The driver implements a SunOS-compatible
-  interface and a NetBSD-compatible interface. 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 and read
-  Documentation/modules.txt. If unsure, say Y.
+  interface and a NetBSD-compatible interface. 
 
-Mostek real time clock support
-CONFIG_SUN_MOSTEK_RTC
+  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 and read Documentation/modules.txt. If unsure, say Y.
 
-Siemens SAB82532 serial support
-CONFIG_SAB82532
+#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.
-
+#
 Amiga support
 CONFIG_AMIGA
   This option enables support for the Amiga series of computers.  If
@@ -7425,6 +8145,7 @@
   it will enlarge your kernel by about 10KB. The identification
   information is also available through /proc/zorro (say Y to
   "/proc filesystem support"!).
+
   Note that even if you say N here, you can still use your expansion
   cards. If in doubt, say Y.
 
@@ -7494,10 +8215,11 @@
   driver is also the basis for certain other drivers for devices
   attached to the ACSI bus: Atari SLM laser printer, BioNet-100
   Ethernet, and PAMsNet Ethernet. If you want to use one of these
-  devices, you need ACSI support, too. 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 acsi.o.
+  devices, you need ACSI support, too. 
+
+  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 acsi.o.
 
 Probe all LUNs on each ACSI device
 CONFIG_ACSI_MULTI_LUN
@@ -7541,6 +8263,7 @@
   (such as the GVP A4008 or a Combo board).  Otherwise, say N.
   This driver does NOT work for the T-Rex series of accelerators from
   TekMagic and GVP-M.
+
   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 gvp11.o. If you want to compile it
@@ -7598,6 +8321,7 @@
 CONFIG_ARIADNE
   If you have a VillageTronics Ariadne Ethernet adapter, say Y.
   Otherwise, say N.
+
   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 ariadne.o. If you want to compile it as
@@ -7607,6 +8331,7 @@
 CONFIG_A2065
   If you have a Commodore A2065 Ethernet adapter, say Y.  Otherwise,
   say N.
+
   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 a2065.o. If you want to compile it as a
@@ -7615,6 +8340,7 @@
 Hydra support
 CONFIG_HYDRA
   If you have a Hydra Ethernet adapter, say Y.  Otherwise, say N.
+
   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 hydra.o. If you want to compile it as a
@@ -7641,18 +8367,20 @@
 Multiface Card III parallel support
 CONFIG_MULTIFACE_III_LP
   If you have a Multiface III card for your Amiga, and want to use its
-  parallel port in Linux, say Y.  Otherwise, say N.  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 lp_m68k.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt.
+  parallel port in Linux, say Y.  Otherwise, say N.  
+
+  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 lp_m68k.o. If you want to compile it as a
+  module, say M here and read Documentation/modules.txt.
 
 Amiga mouse support
 CONFIG_AMIGAMOUSE
-  If you want to be able to use an Amiga mouse in Linux, say Y.  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 amigamouse.o. If you want to compile it as a
+  If you want to be able to use an Amiga mouse in Linux, say Y.  
+
+  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 amigamouse.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Amiga Copper Console
@@ -7664,21 +8392,24 @@
 
 Atari mouse support
 CONFIG_ATARIMOUSE
-  If you want to be able to use an Atari mouse in Linux, say Y.  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 atarimouse.o. If you want to compile it as a
+  If you want to be able to use an Atari mouse in Linux, say Y.  
+
+  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 atarimouse.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Atari MFP serial support
 CONFIG_ATARI_MFPSER
   If you like to use the MFP serial ports ("Modem1", "Serial1") under
   Linux, say Y. The driver equally supports all kinds of MFP serial
-  ports and automatically detects whether Serial1 is available. 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
-  want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  ports and automatically detects whether Serial1 is available. 
+
+  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 want to compile it as a module, say M here and read
+  Documentation/modules.txt. 
+
   Note for Falcon users: You also have an MFP port, it's just not
   wired to the outside... But you could use the port under Linux.
 
@@ -7688,10 +8419,12 @@
   LAN) and like to use them under Linux, say Y. All built-in SCC's are
   supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
   two connectors for channel A (Serial2 and LAN), they are visible as
-  two separate devices. 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 want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  two separate devices. 
+
+  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 want to compile it as a module, say M here and read
+  Documentation/modules.txt.
 
 Atari SCC serial DMA support
 CONFIG_ATARI_SCC_DMA
@@ -7704,6 +8437,7 @@
 Atari MIDI serial support
 CONFIG_ATARI_MIDI
   If you want to use your Atari's MIDI port in Linux, say Y.
+
   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 want to compile it as a module, say M here and read
@@ -7714,6 +8448,7 @@
   If you want to be able to use the DSP56001 in Falcons, say Y.
   This driver is still experimental, and if you don't know what it is,
   or if you don't have this processor, just say N.
+
   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
   want to compile it as a module, say M here and read
@@ -7723,6 +8458,7 @@
 CONFIG_AMIGA_BUILTIN_SERIAL
   If you want to use your Amiga's built-in serial port in Linux, say
   Y.
+
   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 want to compile it as a module, say M here and read
@@ -7737,9 +8473,10 @@
 CONFIG_MULTIFACE_III_TTY
   If you want to use a Multiface III card's serial port in Linux, say
   Y.
-  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
-  want to compile it as a module, say M here and read
+
+  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 want to compile it as a module, say M here and read
   Documentation/modules.txt.
 
 Amiga or Atari DMA sound support
@@ -7748,6 +8485,7 @@
   Linux, answer Y to this question.  This will provide a Sun-like
   /dev/audio, compatible with the Linux/i386 sound system.  Otherwise,
   say N.
+
   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 want to compile it as a module, say M here and read
@@ -7826,11 +8564,12 @@
   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.  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.
+  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
@@ -7842,34 +8581,42 @@
 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.  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.
+  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. 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.
+  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.
 
 SAA5249 Teletext processor
 CONFIG_VIDEO_SAA5249
-  Support for I2C bus based teletext using the SAA5249 chip. At the moment
-  this is only useful on some european WinTV cards.
+  Support for I2C bus based teletext using the SAA5249 chip. At the
+  moment this is only useful on some European WinTV cards.
+
+  This driver is also available as a module called saa5249.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 the black and white version of the QuickCam
-  camera. See the next option for the color version. 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.
+  camera. See the next option for the color version. 
+
+  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.
 
 Colour QuickCam Video For Linux
 CONFIG_VIDEO_CQCAM
@@ -7886,14 +8633,13 @@
   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.
 #
 # A couple of things I keep forgetting:
-#   capitalize: Internet, Intel, SCSI, NetWare, PCI, IRQ, DMA
+#   capitalize: DMA, Internet, Intel, IRQ, Linux, NetWare, NFS, PCI, SCSI
 #   two words: hard drive, hard disk, sound card
-#   other: it's safe to save.
+#   other: it's safe to save; daemon
 #
-# This is used by ispell.el:
+# This is used by Emacs' spell checker ispell.el:
 #
 # LocalWords:  CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp sunsite
 # LocalWords:  unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
@@ -8053,7 +8799,13 @@
 # LocalWords:  dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
 # LocalWords:  KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
 # LocalWords:  struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
-# LocalWords:  StrongARM adfs ncpmount namespace SUBDIR reexport NDS kcore FT
+# LocalWords:  adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
 # LocalWords:  interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
 # LocalWords:  isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
 # LocalWords:  KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
+# LocalWords:  eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
+# LocalWords:  EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
+# LocalWords:  mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
+# LocalWords:  ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
+# LocalWords:  NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
+# LocalWords:  teletext WinTV saa iproute tc
diff -u --recursive --new-file v2.1.99/linux/Documentation/filesystems/vfs.txt linux/Documentation/filesystems/vfs.txt
--- v2.1.99/linux/Documentation/filesystems/vfs.txt	Sat May  2 14:19:51 1998
+++ linux/Documentation/filesystems/vfs.txt	Sat May  2 14:35:51 1998
@@ -10,7 +10,6 @@
 Hopefully this helps anyone attempting such a feat, as well as clearing up
 a few important points/dependencies.
 
-
 register_filesystem (struct file_system_type *fstype)
 =====================================================
 
@@ -133,10 +132,12 @@
 
 	int (*follow_link) (struct inode *,struct inode *,int,int,struct inode **);
 	[optional]
-		The follow_link function is only necessary if a filesystem uses a really
-		twisted form of symbolic links - namely if the symbolic link comes from a
-		foreign filesystem that makes no sense....
-		I threw this one out - too much redundant code!
+		follow_link must be implemented if readlink is implemented.
+		Note that follow_link can return a different inode than a
+		lookup_dentry() on the result of readlink() would return.
+		The proc filesystem, in particular, uses this feature heavily.
+		For most user filesystems, however, follow_link() and readlink()
+		should return consistent results.
 
 	int (*readpage) (struct inode *, struct page *);	[optional]
 	int (*writepage) (struct inode *, struct page *);	[mandatory with readpage]
diff -u --recursive --new-file v2.1.99/linux/Documentation/mtrr.txt linux/Documentation/mtrr.txt
--- v2.1.99/linux/Documentation/mtrr.txt	Sat May  2 14:19:51 1998
+++ linux/Documentation/mtrr.txt	Sat May  2 17:42:08 1998
@@ -1,15 +1,15 @@
 MTRR (Memory Type Range Register) control
-17 Dec 1997
+2 May 1998
 Richard Gooch
 <rgooch@atnf.csiro.au>
 
-  On Intel Pentium Pro systems the Memory Type Range Registers (MTRRs)
-  may be used to control processor access to memory ranges. This is
-  most useful when you have a video (VGA) card on the PCI
-  bus. Enabling write-combining allows PCI write transfers to be
-  combined into a larger transfer before bursting over the PCI
-  bus. This can increase performance of image write operations 2.5
-  times or more.
+  On Intel Pentium Pro/Pentium II systems the Memory Type Range
+  Registers (MTRRs) may be used to control processor access to memory
+  ranges. This is most useful when you have a video (VGA) card on a
+  PCI or AGP bus. Enabling write-combining allows bus write transfers
+  to be combined into a larger transfer before bursting over the
+  PCI/AGP bus. This can increase performance of image write operations
+  2.5 times or more.
 
   The CONFIG_MTRR option creates a /proc/mtrr file which may be used
   to manipulate your MTRRs. Typically the X server should use
@@ -30,13 +30,40 @@
 % cat /proc/mtrr
 reg00: base=0x00000000 (   0MB), size= 128MB: write-back, count=1
 reg01: base=0x08000000 ( 128MB), size=  64MB: write-back, count=1
-reg05: base=0x80000000 (2048MB), size=   4MB: write-combining, count=1
 ===============================================================================
 Creating MTRRs from the shell:
-% echo "base=0x80000000 size=0x400000 type=write-combining" >! /proc/mtrr
+# echo "base=0xf8000000 size=0x400000 type=write-combining" >! /proc/mtrr
+
+And the result thereof:
+% cat /proc/mtrr
+reg00: base=0x00000000 (   0MB), size= 128MB: write-back, count=1
+reg01: base=0x08000000 ( 128MB), size=  64MB: write-back, count=1
+reg02: base=0xf8000000 (3968MB), size=   4MB: write-combining, count=1
+
+This is for videoram at base address 0xf8000000 and size 4 MBytes. To
+find out your base address, you need to look at the output of your X
+server, which tells you where the linear framebuffer address is. A
+typical line that you may get is:
+
+(--) S3: PCI: 968 rev 0, Linear FB @ 0xf8000000
+
+Note that you should only use the value from the X server, as it may
+move the framebuffer base address, so the only value you can trust is
+that reported by the X server.
+
+To find out the size of your framebuffer (what, you don't actually
+know?), the following line will tell you:
+
+(--) S3: videoram:  4096k
+
+That's 4 MBytes, which is 0x400000 bytes (in hexadecimal).
+A patch is being written for XFree86 which will make this automatic:
+in other words the X server will manipulate /proc/mtrr using the
+ioctl() interface, so users won't have to do anything. If you use a
+commercial X server, lobby your vendor to add support for MTRRs.
 ===============================================================================
 Removing MTRRs from the shell:
-% echo "disable=5" >! /proc/mtrr
+% echo "disable=2" >! /proc/mtrr
 ===============================================================================
 Reading MTRRs from a C programme using ioctl()'s:
 
@@ -44,7 +71,7 @@
 
     Source file for mtrr-show (example programme to show MTRRs using ioctl()'s)
 
-    Copyright (C) 1997  Richard Gooch
+    Copyright (C) 1997-1998  Richard Gooch
 
     This program is free software; you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
@@ -72,7 +99,7 @@
 
     Written by      Richard Gooch   17-DEC-1997
 
-    Last updated by Richard Gooch   17-DEC-1997
+    Last updated by Richard Gooch   2-MAY-1998
 
 
 */
@@ -84,7 +111,7 @@
 #include <sys/ioctl.h>
 #include <errno.h>
 #define MTRR_NEED_STRINGS
-#include <linux/mtrr.h>
+#include <asm/mtrr.h>
 
 #define TRUE 1
 #define FALSE 0
@@ -130,7 +157,7 @@
 
     Source file for mtrr-add (example programme to add an MTRRs using ioctl())
 
-    Copyright (C) 1997  Richard Gooch
+    Copyright (C) 1997-1998  Richard Gooch
 
     This program is free software; you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
@@ -158,7 +185,7 @@
 
     Written by      Richard Gooch   17-DEC-1997
 
-    Last updated by Richard Gooch   17-DEC-1997
+    Last updated by Richard Gooch   2-MAY-1998
 
 
 */
@@ -172,7 +199,7 @@
 #include <sys/ioctl.h>
 #include <errno.h>
 #define MTRR_NEED_STRINGS
-#include <linux/mtrr.h>
+#include <asm/mtrr.h>
 
 #define TRUE 1
 #define FALSE 0
diff -u --recursive --new-file v2.1.99/linux/Documentation/sysctl/vm.txt linux/Documentation/sysctl/vm.txt
--- v2.1.99/linux/Documentation/sysctl/vm.txt	Sat May  2 14:19:52 1998
+++ linux/Documentation/sysctl/vm.txt	Sat May  2 17:45:03 1998
@@ -18,6 +18,7 @@
 - bdflush
 - buffermem
 - freepages
+- kswapd
 - overcommit_memory
 - pagecache
 - swapctl
@@ -112,9 +113,58 @@
 This file contains the values in the struct freepages. That
 struct contains three members: min, low and high.
 
-These variables are currently unused (?), but they're
-very likely to be abused for something else in the near
-future, so don't yet remove it from the source...
+Although the goal of the Linux memory management subsystem
+is to avoid fragmentation and make large chunks of free
+memory (so that we can hand out DMA buffers and such), there
+still are some page-based limits in the system, mainly to
+make sure we don't waste too much memory trying to get large
+free area's.
+
+The meaning of the numbers is:
+
+freepages.min	When the number of free pages in the system
+		reaches this number, only the kernel can
+		allocate more memory.
+freepages.low	If memory is too fragmented, the swapout
+		daemon is started, except when the number
+		of free pages is larger than freepages.low.
+freepages.high	The swapping daemon exits when memory is
+		sufficiently defragmented, when the number
+		of free pages reaches freepages.high or when
+		it has tried the maximum number of times. 
+
+==============================================================
+
+kswapd:
+
+Kswapd is the kernel swapout daemon. That is, kswapd is that
+piece of the kernel that frees memory when it get's fragmented
+or full. Since every system is different, you'll probably want
+some control over this piece of the system.
+
+The numbers in this page correspond to the numbers in the
+struct pager_daemon {tries_base, tries_min, swap_cluster
+}; The tries_base and swap_cluster probably have the
+largest influence on system performance.
+
+tries_base	The maximum number of pages kswapd tries to
+		free in one round is calculated from this
+		number. Usually this number will be divided
+		by 4 or 8 (see mm/vmscan.c), so it isn't as
+		big as it looks.
+		When you need to increase the bandwith to/from
+		swap, you'll want to increase this number.
+tries_min	This is the minimum number of times kswapd
+		tries to free a page each time it is called.
+		Basically it's just there to make sure that
+		kswapd frees some pages even when it's being
+		called with minimum priority.
+swap_cluster	This is the number of pages kswapd writes in
+		one turn. You want this large so that kswapd
+		does it's I/O in large chunks and the disk
+		doesn't have to seek often, but you don't want
+		it to be too large since that would flood the
+		request queue.
 
 ==============================================================
 
diff -u --recursive --new-file v2.1.99/linux/Makefile linux/Makefile
--- v2.1.99/linux/Makefile	Sat May  2 14:19:52 1998
+++ linux/Makefile	Fri May  1 11:20:31 1998
@@ -1,6 +1,6 @@
 VERSION = 2
 PATCHLEVEL = 1
-SUBLEVEL = 99
+SUBLEVEL = 100
 
 ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/)
 
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/bios32.c linux/arch/i386/kernel/bios32.c
--- v2.1.99/linux/arch/i386/kernel/bios32.c	Thu Apr 23 20:21:28 1998
+++ linux/arch/i386/kernel/bios32.c	Sun May  3 11:30:02 1998
@@ -1,7 +1,7 @@
 /*
  * bios32.c - Low-Level PCI Access
  *
- * $Id: bios32.c,v 1.29 1998/04/17 16:31:15 mj Exp $
+ * $Id: bios32.c,v 1.32 1998/05/02 12:03:05 davem Exp $
  *
  * Sponsored by
  *	iX Multiuser Multitasking Magazine
@@ -66,6 +66,8 @@
  *	and cleaned it up...     Martin Mares <mj@atrey.karlin.mff.cuni.cz>
  *
  * Feb 6,  1998 : No longer using BIOS to find devices and device classes. [mj]
+ *
+ * May 1,  1998 : Support for peer host bridges. [mj]
  */
 
 #include <linux/config.h>
@@ -74,6 +76,7 @@
 #include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/ioport.h>
+#include <linux/malloc.h>
 
 #include <asm/page.h>
 #include <asm/segment.h>
@@ -832,7 +835,10 @@
 }
 
 /*
- * Sort the device list according to PCI BIOS.
+ * Sort the device list according to PCI BIOS. Nasty hack, but since some
+ * fool forgot to define the `correct' device order in the PCI BIOS specs
+ * and we want to be (possibly bug-to-bug ;-]) compatible with older kernels
+ * which used BIOS ordering, we are bound to do this...
  */
 
 __initfunc(void pcibios_sort(void))
@@ -924,11 +930,41 @@
 }
 
 /*
- * Arch-dependent fixups. We need to fix here base addresses, I/O
- * and memory enables and IRQ's as the PCI BIOS'es are buggy as hell.
+ * In case there are peer host bridges, scan bus behind each of them.
+ * Although several sources claim that the host bridges should have
+ * header type 1 and be assigned a bus number as for PCI2PCI bridges,
+ * the reality doesn't pass this test and the bus number is usually
+ * hard-wired to 1.
  */
+__initfunc(void pcibios_fixup_peer_bridges(void))
+{
+	struct pci_dev *dev;
+	int cnt = 0;
 
-__initfunc(void pcibios_fixup(void))
+	for(dev=pci_root.devices; dev; dev=dev->sibling)
+		if ((dev->class >> 8) == PCI_CLASS_BRIDGE_HOST) {
+			DBG("PCI: Host bridge at %02x\n", dev->devfn);
+			if (cnt) {
+				struct pci_bus *b = kmalloc(sizeof(struct pci_bus), GFP_KERNEL);
+				memset(b, 0, sizeof(*b));
+				b->parent = &pci_root;
+				b->next = pci_root.next;
+				pci_root.next = b;
+				b->self = dev;
+				b->number = b->secondary = cnt;
+				b->subordinate = 0xff;
+				b->subordinate = pci_scan_bus(b);
+			}
+			cnt++;
+		}
+}
+
+/*
+ * Fix base addresses, I/O and memory enables and IRQ's (mostly work-arounds
+ * for buggy PCI BIOS'es :-[).
+ */
+
+__initfunc(void pcibios_fixup_devices(void))
 {
 	struct pci_dev *dev;
 	int i, has_io, has_mem;
@@ -991,6 +1027,16 @@
 		if (dev->irq >= NR_IRQS)
 			dev->irq = 0;
 	}
+}
+
+/*
+ * Arch-dependent fixups.
+ */
+
+__initfunc(void pcibios_fixup(void))
+{
+	pcibios_fixup_peer_bridges();
+	pcibios_fixup_devices();
 
 #ifdef CONFIG_PCI_BIOS
 	if ((pci_probe & PCI_BIOS_SORT) && !(pci_probe & PCI_NO_SORT))
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/io_apic.c linux/arch/i386/kernel/io_apic.c
--- v2.1.99/linux/arch/i386/kernel/io_apic.c	Mon Apr  6 17:40:59 1998
+++ linux/arch/i386/kernel/io_apic.c	Tue May  5 16:10:32 1998
@@ -1,7 +1,7 @@
 /*
  *	Intel IO-APIC support for multi-pentium hosts.
  *
- *	(c) 1997 Ingo Molnar, Hajnalka Szabo
+ *	Copyright (C) 1997, 1998 Ingo Molnar, Hajnalka Szabo
  *
  *	Many thanks to Stig Venaas for trying out countless experimental
  *	patches and reporting/debugging problems patiently!
@@ -34,6 +34,19 @@
  */
 #define IO_APIC_BASE ((volatile int *)0xfec00000)
 
+enum mp_irq_source_types {
+    mp_INT = 0,
+    mp_NMI = 1,
+    mp_SMI = 2,
+    mp_ExtINT = 3
+};
+
+enum ioapic_irq_destination_types {
+    dest_Fixed = 0,
+    dest_LowestPrio = 1,
+    dest_ExtINT = 7
+};
+
 /*
  * The structure of the IO-APIC:
  */
@@ -60,7 +73,7 @@
 	__u32	vector		:  8,
 		delivery_mode	:  3,	/* 000: FIXED
 					 * 001: lowest prio
-					 * 111: ExtInt
+					 * 111: ExtINT
 					 */
 		dest_mode	:  1,	/* 0: physical, 1: logical */
 		delivery_status	:  1,
@@ -137,7 +150,7 @@
 	io_apic_write(0x10+2*irq, *(((int *)&entry)+0));
 }
 
-void clear_IO_APIC_irq (unsigned int irq)
+void clear_IO_APIC_pin (unsigned int pin)
 {
 	struct IO_APIC_route_entry entry;
 
@@ -146,12 +159,12 @@
 	 */
 	memset(&entry, 0, sizeof(entry));
 	entry.mask = 1;
-	io_apic_write(0x10+2*irq, *(((int *)&entry)+0));
-	io_apic_write(0x11+2*irq, *(((int *)&entry)+1));
+	io_apic_write(0x10+2*pin, *(((int *)&entry)+0));
+	io_apic_write(0x11+2*pin, *(((int *)&entry)+1));
 }
 
 /*
- * support for broken MP BIOSes, enables hand-redirection of PIRQ0-3 to
+ * support for broken MP BIOSes, enables hand-redirection of PIRQ0-7 to
  * specific CPU-side IRQs.
  */
 
@@ -159,7 +172,7 @@
 int pirq_entries [MAX_PIRQS];
 int pirqs_enabled;
 
-void ioapic_pirq_setup(char *str, int *ints)
+__initfunc(void ioapic_pirq_setup(char *str, int *ints))
 {
 	int i, max;
 
@@ -187,12 +200,15 @@
 	}
 }
 
-int find_irq_entry(int pin)
+/*
+ * Find the irq entry nr of a certain pin.
+ */
+__initfunc(static int find_irq_entry(int pin, int type))
 {
 	int i;
 
 	for (i=0; i<mp_irq_entries; i++)
-		if ( (mp_irqs[i].mpc_irqtype == 0x00) &&
+		if ( (mp_irqs[i].mpc_irqtype == type) &&
 			(mp_irqs[i].mpc_dstirq == pin))
 
 			return i;
@@ -200,7 +216,227 @@
 	return -1;
 }
 
-void setup_IO_APIC_irqs (void)
+/*
+ * Find the pin to which IRQ0 (ISA) is connected
+ */
+__initfunc(int find_timer_pin (int type))
+{
+	int i;
+
+	for (i=0; i<mp_irq_entries; i++) {
+		int lbus = mp_irqs[i].mpc_srcbus;
+
+		if ((mp_bus_id_to_type[lbus] == MP_BUS_ISA) &&
+		    (mp_irqs[i].mpc_irqtype == type) &&
+		    (mp_irqs[i].mpc_srcbusirq == 0x00))
+
+			return mp_irqs[i].mpc_dstirq;
+	}
+	return -1;
+}
+
+/*
+ * Find a specific PCI IRQ entry.
+ * Not an initfunc, possibly needed by modules
+ */
+int IO_APIC_get_PCI_irq_vector (int bus, int slot, int pci_pin)
+{
+	int i;
+
+	for (i=0; i<mp_irq_entries; i++) {
+		int lbus = mp_irqs[i].mpc_srcbus;
+
+		if (IO_APIC_IRQ(mp_irqs[i].mpc_dstirq) &&
+		    (mp_bus_id_to_type[lbus] == MP_BUS_PCI) &&
+		    !mp_irqs[i].mpc_irqtype &&
+		    (bus == mp_bus_id_to_pci_bus[mp_irqs[i].mpc_srcbus]) &&
+		    (slot == ((mp_irqs[i].mpc_srcbusirq >> 2) & 0x1f)) &&
+		    (pci_pin == (mp_irqs[i].mpc_srcbusirq & 3)))
+
+			return mp_irqs[i].mpc_dstirq;
+	}
+	return -1;
+}
+
+static int irq_trigger(int idx)
+{
+	int bus = mp_irqs[idx].mpc_srcbus;
+	int trigger;
+
+	/*
+	 * Determine IRQ trigger mode (edge or level sensitive):
+	 */
+	switch ((mp_irqs[idx].mpc_irqflag>>2) & 3)
+	{
+		case 0: /* conforms, ie. bus-type dependent */
+		{
+			switch (mp_bus_id_to_type[bus])
+			{
+				case MP_BUS_ISA: /* ISA pin, edge */
+				{
+					trigger = 0;
+					break;
+				}
+				case MP_BUS_PCI: /* PCI pin, level */
+				{
+					trigger = 1;
+					break;
+				}
+				default:
+				{
+					printk("broken BIOS!!\n");
+					trigger = 1;
+					break;
+				}
+			}
+			break;
+		}
+		case 1: /* edge */
+		{
+			trigger = 0;
+			break;
+		}
+		case 2: /* reserved */
+		{
+			printk("broken BIOS!!\n");
+			trigger = 1;
+			break;
+		}
+		case 3: /* level */
+		{
+			trigger = 1;
+			break;
+		}
+		default: /* invalid */
+		{
+			printk("broken BIOS!!\n");
+			trigger = 0;
+			break;
+		}
+	}
+	return trigger;
+}
+
+__initfunc(static int irq_polarity(int idx))
+{
+	int bus = mp_irqs[idx].mpc_srcbus;
+	int polarity;
+
+	/*
+	 * Determine IRQ line polarity (high active or low active):
+	 */
+	switch (mp_irqs[idx].mpc_irqflag & 3)
+	{
+		case 0: /* conforms, ie. bus-type dependent polarity */
+		{
+			switch (mp_bus_id_to_type[bus])
+			{
+				case MP_BUS_ISA: /* ISA pin */
+				{
+					polarity = 0;
+					break;
+				}
+				case MP_BUS_PCI: /* PCI pin */
+				{
+					polarity = 1;
+					break;
+				}
+				default:
+				{
+					printk("broken BIOS!!\n");
+					polarity = 1;
+					break;
+				}
+			}
+			break;
+		}
+		case 1: /* high active */
+		{
+			polarity = 0;
+			break;
+		}
+		case 2: /* reserved */
+		{
+			printk("broken BIOS!!\n");
+			polarity = 1;
+			break;
+		}
+		case 3: /* low active */
+		{
+			polarity = 1;
+			break;
+		}
+		default: /* invalid */
+		{
+			printk("broken BIOS!!\n");
+			polarity = 1;
+			break;
+		}
+	}
+	return polarity;
+}
+
+__initfunc(static int pin_2_irq (int idx, int pin))
+{
+	int irq;
+	int bus = mp_irqs[idx].mpc_srcbus;
+
+	switch (mp_bus_id_to_type[bus])
+	{
+		case MP_BUS_ISA: /* ISA pin */
+		{
+			irq = mp_irqs[idx].mpc_srcbusirq;
+			break;
+		}
+		case MP_BUS_PCI: /* PCI pin */
+		{
+			/*
+			 * PCI IRQs are 'directly mapped'
+			 */
+			irq = pin;
+			break;
+		}
+		default:
+		{
+			printk("unknown bus type %d.\n",bus); 
+			irq = 0;
+			break;
+		}
+	}
+
+	/*
+	 * PCI IRQ command line redirection. Yes, limits are hardcoded.
+	 */
+	if ((pin>=16) && (pin<=23)) {
+		if (pirq_entries[pin-16] != -1) {
+			if (!pirq_entries[pin-16]) {
+				printk("disabling PIRQ%d\n", pin-16);
+			} else {
+				irq = pirq_entries[pin-16];
+				printk("using PIRQ%d -> IRQ %d\n",
+						pin-16, irq);
+			}
+		}
+	}
+	return irq;
+}
+
+int IO_APIC_irq_trigger (int irq)
+{
+	int idx, i;
+
+	for (i=0; i<nr_ioapic_registers; i++) {
+		idx = find_irq_entry(i,mp_INT);
+		if (irq == pin_2_irq(idx,i))
+			return irq_trigger(idx);
+	}
+	/*
+	 * nonexistant IRQs are edge default
+	 */
+	return 0;
+}
+
+__initfunc(void setup_IO_APIC_irqs (void))
 {
 	struct IO_APIC_route_entry entry;
 	int i, idx, bus, irq, first_notcon=1;
@@ -214,12 +450,12 @@
 		 */
 		memset(&entry,0,sizeof(entry));
 
-		entry.delivery_mode = 1;		/* lowest prio */
+		entry.delivery_mode = dest_LowestPrio;
 		entry.dest_mode = 1;			/* logical delivery */
 		entry.mask = 0;				/* enable IRQ */
 		entry.dest.logical.logical_dest = 0xff;	/* all CPUs */
 
-		idx = find_irq_entry(i);
+		idx = find_irq_entry(i,mp_INT);
 		if (idx == -1) {
 			if (first_notcon) {
 				printk(" IO-APIC pin %d", i);
@@ -228,137 +464,32 @@
 				printk(", %d", i);
 			continue;
 		}
-		bus = mp_irqs[idx].mpc_srcbus;
 
-		switch (mp_bus_id_to_type[bus])
-		{
-			case MP_BUS_ISA: /* ISA pin */
-			{
-				irq = mp_irqs[idx].mpc_srcbusirq;
-				break;
-			}
-			case MP_BUS_PCI: /* PCI pin */
-			{
-				/*
-				 * PCI IRQs are 'directly mapped'
-				 */
-				irq = i;
-				break;
-			}
-			default:
-			{
-				printk("unknown bus type %d.\n",bus); 
-				irq = 0;
-				break;
-			}
-		}
+		entry.trigger = irq_trigger(idx);
+		entry.polarity = irq_polarity(idx);
 
-		/*
-		 * PCI IRQ redirection. Yes, limits are hardcoded.
-		 */
-		if ((i>=16) && (i<=23)) {
-			if (pirq_entries[i-16] != -1) {
-				if (!pirq_entries[i-16]) {
-					printk("disabling PIRQ%d\n", i-16);
-				} else {
-					irq = pirq_entries[i-16];
-					printk("using PIRQ%d -> IRQ %d\n",
-							i-16, irq);
-				}
-			}
-		}
+		irq = pin_2_irq(idx,i);
 
 		if (!IO_APIC_IRQ(irq))
 			continue;
 
 		entry.vector = IO_APIC_VECTOR(irq);
 
-		/*
-		 * Determine IRQ line polarity (high active or low active):
-		 */
-		switch (mp_irqs[idx].mpc_irqflag & 3)
-		{
-			case 0: /* conforms, ie. bus-type dependent polarity */
-			{
-				switch (mp_bus_id_to_type[bus])
-				{
-					case MP_BUS_ISA: /* ISA pin */
-					{
-						entry.polarity = 0;
-						break;
-					}
-					case MP_BUS_PCI: /* PCI pin */
-					{
-						entry.polarity = 1;
-						break;
-					}
-					default:
-					{
-						printk("broken BIOS!!\n");
-						break;
-					}
-				}
-				break;
-			}
-			case 1: /* high active */
-			{
-				entry.polarity = 0;
-				break;
-			}
-			case 2: /* reserved */
-			{
-				printk("broken BIOS!!\n");
-				break;
-			}
-			case 3: /* low active */
-			{
-				entry.polarity = 1;
-				break;
-			}
-		}
+	/*
+	 * There are broken mptables which register ISA+high-active+level IRQs,
+	 * these are illegal and are converted here to ISA+high-active+edge
+	 * IRQ sources. Careful, ISA+low-active+level is another broken entry
+	 * type, it represents PCI IRQs 'embedded into an ISA bus', they have
+	 * to be accepted. Yes, ugh.
+	 */
+		bus = mp_irqs[idx].mpc_srcbus;
 
-		/*
-		 * Determine IRQ trigger mode (edge or level sensitive):
-		 */
-		switch ((mp_irqs[idx].mpc_irqflag>>2) & 3)
+		if ( (mp_bus_id_to_type[bus] == MP_BUS_ISA) &&
+			(entry.polarity == 0) /* active-high */ &&
+			(entry.trigger == 1) /* level */ )
 		{
-			case 0: /* conforms, ie. bus-type dependent */
-			{
-				switch (mp_bus_id_to_type[bus])
-				{
-					case MP_BUS_ISA: /* ISA pin, edge */
-					{
-						entry.trigger = 0;
-						break;
-					}
-					case MP_BUS_PCI: /* PCI pin, level */
-					{
-						entry.trigger = 1;
-						break;
-					}
-					default:
-					{
-						printk("broken BIOS!!\n");
-						break;
-					}
-				}
-				break;
-			}
-			case 1: /* edge */
-			{
-				entry.trigger = 0;
-				break;
-			}
-			case 2: /* reserved */
-			{
-				printk("broken BIOS!!\n");
-				break;
-			}
-			case 3: /* level */
-			{
-				entry.trigger = 1;
-				break;
-			}
+			printk("broken BIOS, changing pin %d to edge\n", i);
+			entry.trigger = 0;
 		}
 
 		io_apic_write(0x10+2*i, *(((int *)&entry)+0));
@@ -369,7 +500,7 @@
 		printk(" not connected.\n");
 }
 
-void setup_IO_APIC_irq_ISA_default (unsigned int irq)
+__initfunc(void setup_IO_APIC_irq_ISA_default (unsigned int irq))
 {
 	struct IO_APIC_route_entry entry;
 
@@ -378,9 +509,9 @@
 	 */
 	memset(&entry,0,sizeof(entry));
 
-	entry.delivery_mode = 1;			/* lowest prio */
+	entry.delivery_mode = dest_LowestPrio;		/* lowest prio */
 	entry.dest_mode = 1;				/* logical delivery */
-	entry.mask = 1;					/* unmask IRQ now */
+	entry.mask = 0;					/* unmask IRQ now */
 	entry.dest.logical.logical_dest = 0xff;		/* all CPUs */
 
 	entry.vector = IO_APIC_VECTOR(irq);
@@ -392,56 +523,42 @@
 	io_apic_write(0x11+2*irq, *(((int *)&entry)+1));
 }
 
-int IO_APIC_get_PCI_irq_vector (int bus, int slot, int pci_pin)
-{
-	int i;
-
-	for (i=0; i<mp_irq_entries; i++) {
-		int lbus = mp_irqs[i].mpc_srcbus;
-
-		if (IO_APIC_IRQ(mp_irqs[i].mpc_dstirq) &&
-		    (mp_bus_id_to_type[lbus] == MP_BUS_PCI) &&
-		    !mp_irqs[i].mpc_irqtype &&
-		    (bus == mp_bus_id_to_pci_bus[mp_irqs[i].mpc_srcbus]) &&
-		    (slot == ((mp_irqs[i].mpc_srcbusirq >> 2) & 0x1f)) &&
-		    (pci_pin == (mp_irqs[i].mpc_srcbusirq & 3)))
-
-			return mp_irqs[i].mpc_dstirq;
-	}
-	return -1;
-}
-
 /*
- * There is a nasty bug in some older SMP boards, their mptable lies
- * about the timer IRQ. We do the following to work around the situation:
- *
- *	- timer IRQ defaults to IO-APIC IRQ
- *	- if this function detects that timer IRQs are defunct, then we fall
- *	  back to ISA timer IRQs
+ * Set up a certain pin as ExtINT delivered interrupt
  */
-static int timer_irq_works (void)
+__initfunc(void setup_ExtINT_pin (unsigned int pin))
 {
-	unsigned int t1=jiffies;
-	unsigned long flags;
+	struct IO_APIC_route_entry entry;
 
-	save_flags(flags);
-	sti();
+	/*
+	 * add it to the IO-APIC irq-routing table:
+	 */
+	memset(&entry,0,sizeof(entry));
 
-	udelay(100*1000);
+	entry.delivery_mode = dest_ExtINT;
+	entry.dest_mode = 1;				/* logical delivery */
+	entry.mask = 0;					/* unmask IRQ now */
+	entry.dest.logical.logical_dest = 0xff;		/* all CPUs */
 
-	if (jiffies-t1>1)
-		return 1;
+	entry.vector = IO_APIC_VECTOR(pin);		/* it's ignored */
 
-	return 0;
+	entry.polarity=0;
+	entry.trigger=0;
+
+	io_apic_write(0x10+2*pin, *(((int *)&entry)+0));
+	io_apic_write(0x11+2*pin, *(((int *)&entry)+1));
 }
 
-void print_IO_APIC (void)
+__initfunc(void print_IO_APIC (void))
 {
 	int i;
 	struct IO_APIC_reg_00 reg_00;
 	struct IO_APIC_reg_01 reg_01;
 	struct IO_APIC_reg_02 reg_02;
 
+ 	printk("nr of MP irq sources: %d.\n", mp_irq_entries);
+ 	printk("nr of IO-APIC registers: %d.\n", nr_ioapic_registers);
+
 	*(int *)&reg_00 = io_apic_read(0);
 	*(int *)&reg_01 = io_apic_read(1);
 	*(int *)&reg_02 = io_apic_read(2);
@@ -513,14 +630,41 @@
 	return;
 }
 
-static void init_sym_mode (void)
+__initfunc(static void init_sym_mode (void))
 {
+	int i;
+
+	if (!pirqs_enabled)
+		for (i=0; i<MAX_PIRQS; i++)
+			pirq_entries[i]=-1;
+
 	printk("enabling Symmetric IO mode ... ");
-		outb_p (0x70, 0x22);
-		outb_p (0x01, 0x23);
+
+	outb(0x70, 0x22);
+	outb(0x01, 0x23);
+
 	printk("...done.\n");
+
+	/*
+	 * The number of IO-APIC irq-registers (== #pins):
+	 */
+	{
+		struct IO_APIC_reg_01 reg_01;
+
+		*(int *)&reg_01 = io_apic_read(1);
+		nr_ioapic_registers = reg_01.entries+1;
+	}
+
+	/*
+	 * Do not trust the IO-APIC being empty at bootup
+	 */
+	for (i=0; i<nr_ioapic_registers; i++)
+		clear_IO_APIC_pin (i);
 }
 
+/*
+ * Not an initfunc, needed by the reboot code
+ */
 void init_pic_mode (void)
 {
 	printk("disabling Symmetric IO mode ... ");
@@ -551,8 +695,7 @@
 	{ 0		,	0		}
 };
 
-
-static int in_ioapic_list (struct ioapic_list_entry * table)
+__initfunc(static int in_ioapic_list (struct ioapic_list_entry * table))
 {
 	for (;table->oem_id; table++)
 		if ((!strcmp(table->oem_id,ioapic_OEM_ID)) &&
@@ -561,7 +704,7 @@
 	return 0;
 }
 
-static int ioapic_whitelisted (void)
+__initfunc(static int ioapic_whitelisted (void))
 {
 /*
  * Right now, whitelist everything to see whether the new parsing
@@ -574,12 +717,12 @@
 #endif
 }
 
-static int ioapic_blacklisted (void)
+__initfunc(static int ioapic_blacklisted (void))
 {
 	return in_ioapic_list(ioapic_blacklist);
 }
 
-static void setup_ioapic_id (void)
+__initfunc(static void setup_ioapic_id (void))
 {
 	struct IO_APIC_reg_00 reg_00;
 
@@ -598,7 +741,7 @@
 		panic("APIC ID 2 already used");
 
 	/*
-	 * set the ID
+	 * Set the ID
 	 */
 	*(int *)&reg_00 = io_apic_read(0);
 	printk("... changing IO-APIC physical APIC ID to 2 ...\n");
@@ -613,7 +756,7 @@
 		panic("could not set ID");
 }
 
-static void construct_default_ISA_mptable (void)
+__initfunc(static void construct_default_ISA_mptable (void))
 {
 	int i, pos=0;
 
@@ -650,31 +793,84 @@
 
 	setup_ioapic_id();
 }
-			
-void setup_IO_APIC (void)
+
+/*
+ * There is a nasty bug in some older SMP boards, their mptable lies
+ * about the timer IRQ. We do the following to work around the situation:
+ *
+ *	- timer IRQ defaults to IO-APIC IRQ
+ *	- if this function detects that timer IRQs are defunct, then we fall
+ *	  back to ISA timer IRQs
+ */
+__initfunc(static int timer_irq_works (void))
 {
-	int i;
+	unsigned int t1=jiffies;
+	unsigned long flags;
 
-	if (!pirqs_enabled)
-		for (i=0; i<MAX_PIRQS; i++)
-			pirq_entries[i]=-1;
+	save_flags(flags);
+	sti();
 
-	init_sym_mode();
-	{
-		struct IO_APIC_reg_01 reg_01;
+	udelay(10*10000);
 
-		*(int *)&reg_01 = io_apic_read(1);
-		nr_ioapic_registers = reg_01.entries+1;
+	if (jiffies-t1>1)
+		return 1;
+
+	return 0;
+}
+
+/*
+ * This code may look a bit paranoid, but it's supposed to cooperate with
+ * a wide range of boards and BIOS bugs ... fortunately only the timer IRQ
+ * is so screwy. Thanks to Brian Perkins for testing/hacking this beast
+ * fanatically on his truly bugged board.
+ */
+__initfunc(static void check_timer (void))
+{
+	int pin1, pin2;
+
+	pin1 = find_timer_pin (mp_INT);
+	pin2 = find_timer_pin (mp_ExtINT);
+
+	if (!timer_irq_works ()) {
+		if (pin1 != -1)
+			printk("..MP-BIOS bug: 8254 timer not connected to IO-APIC\n");
+		printk("..trying to set up timer as ExtINT ... ");
+
+		if (pin2 != -1) {
+			printk(".. (found pin %d) ...", pin2);
+			setup_ExtINT_pin (pin2);
+			make_8259A_irq(0);
+		}
+
+		if (!timer_irq_works ()) {
+			printk(" failed.\n");
+			printk("..trying to set up timer as BP irq ...");
+			/*
+			 * Just in case ...
+			 */
+			if (pin1 != -1)
+				clear_IO_APIC_pin (pin1);
+			if (pin2 != -1)
+				clear_IO_APIC_pin (pin2);
+
+			make_8259A_irq(0);
+
+			if (!timer_irq_works ()) {
+				printk(" failed.\n");
+				panic("IO-APIC + timer doesnt work!");
+			}
+		}
+		printk(" works.\n");
 	}
+}
 
-	/*
-	 * do not trust the IO-APIC being empty at bootup
-	 */
-	for (i=0; i<nr_ioapic_registers; i++)
-		clear_IO_APIC_irq (i);
+__initfunc(void setup_IO_APIC (void))
+{
+	init_sym_mode();
 
 	/*
-	 * the following IO-APIC's can be enabled:
+	 * Determine the range of IRQs handled by the IO-APIC. The
+	 * following boards can be fully enabled:
 	 *
 	 * - whitelisted ones
 	 * - those which have no PCI pins connected
@@ -699,7 +895,7 @@
 	/*
 	 * If there are no explicit mp irq entries: it's either one of the
 	 * default configuration types or we are broken. In both cases it's
-	 * fine to set up most of the low 16 IOAPIC pins to ISA defaults.
+	 * fine to set up most of the low 16 IO-APIC pins to ISA defaults.
 	 */
 	if (!mp_irq_entries) {
 		printk("no explicit IRQ entries, using default mptable\n");
@@ -708,18 +904,13 @@
 
 	init_IO_APIC_traps();
 
+	/*
+	 * Set up the IO-APIC irq routing table by parsing the MP-BIOS
+	 * mptable:
+	 */
 	setup_IO_APIC_irqs ();
-
-	if (!timer_irq_works ()) {
-		make_8259A_irq(0);
-		if (!timer_irq_works ())
-			panic("IO-APIC + timer doesnt work!");
-		printk("..MP-BIOS bug: i8254 timer not connected to IO-APIC\n");
-		printk("..falling back to 8259A-based timer interrupt\n");
-	}
+	check_timer();
  
- 	printk("nr of MP irq sources: %d.\n", mp_irq_entries);
- 	printk("nr of IOAPIC registers: %d.\n", nr_ioapic_registers);
 	print_IO_APIC();
 }
 
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/irq.c linux/arch/i386/kernel/irq.c
--- v2.1.99/linux/arch/i386/kernel/irq.c	Sat May  2 14:19:52 1998
+++ linux/arch/i386/kernel/irq.c	Tue May  5 16:13:49 1998
@@ -70,9 +70,8 @@
 
 /*
  * Not all IRQs can be routed through the IO-APIC, eg. on certain (older)
- * boards the timer interrupt and sometimes the keyboard interrupt is
- * not connected to any IO-APIC pin, it's fed to the CPU ExtInt IRQ line
- * directly.
+ * boards the timer interrupt is not connected to any IO-APIC pin, it's
+ * fed to the CPU IRQ line directly.
  *
  * Any '1' bit in this mask means the IRQ is routed through the IO-APIC.
  * this 'mixed mode' IRQ handling costs us one more branch in do_IRQ,
@@ -82,11 +81,8 @@
 /*
  * Default to all normal IRQ's _not_ using the IO APIC.
  *
- * To get IO-APIC interrupts you should either:
- *  - turn some of them into IO-APIC interrupts at runtime
- *    with some magic system call interface.
- *  - explicitly use irq 16-19 depending on which PCI irq
- *    line your PCI controller uses.
+ * To get IO-APIC interrupts we turn some of them into IO-APIC
+ * interrupts during boot.
  */
 unsigned int io_apic_irqs = 0;
 
@@ -109,15 +105,34 @@
 
 
 #ifdef __SMP__
-static void do_ioapic_IRQ (unsigned int irq, int cpu, struct pt_regs * regs);
-static void enable_ioapic_irq (unsigned int irq);
-static void disable_ioapic_irq (unsigned int irq);
-
-static struct hw_interrupt_type ioapic_irq_type = {
-	do_ioapic_IRQ,
-	enable_ioapic_irq,
-	disable_ioapic_irq
+
+/*
+ * Level and edge triggered IO-APIC interrupts need different handling,
+ * so we use two separate irq descriptors:
+ */
+
+static void do_edge_ioapic_IRQ (unsigned int irq, int cpu,
+						 struct pt_regs * regs);
+static void enable_edge_ioapic_irq (unsigned int irq);
+static void disable_edge_ioapic_irq (unsigned int irq);
+
+static struct hw_interrupt_type ioapic_edge_irq_type = {
+	do_edge_ioapic_IRQ,
+	enable_edge_ioapic_irq,
+	disable_edge_ioapic_irq
+};
+
+static void do_level_ioapic_IRQ (unsigned int irq, int cpu,
+						 struct pt_regs * regs);
+static void enable_level_ioapic_irq (unsigned int irq);
+static void disable_level_ioapic_irq (unsigned int irq);
+
+static struct hw_interrupt_type ioapic_level_irq_type = {
+	do_level_ioapic_IRQ,
+	enable_level_ioapic_irq,
+	disable_level_ioapic_irq
 };
+
 #endif
 
 /*
@@ -147,7 +162,7 @@
 irq_desc_t irq_desc[NR_IRQS] = {
 	[0 ... 15] = { 0, 0, 0, &i8259A_irq_type, },	/* standard ISA IRQs */
 #ifdef __SMP__
-	[16 ... 23] = { 0, 0, 0, &ioapic_irq_type, },	/* 'high' PCI IRQs */
+	[16 ... 23] = { 0, 0, 0, &ioapic_edge_irq_type, }, /* 'high' PCI IRQs */
 #endif
 };
 
@@ -342,10 +357,14 @@
 				kstat.irqs[cpu_logical_map(j)][i]);
 #endif
 
-		if (IO_APIC_IRQ(i))
-			p += sprintf(p, " IO-APIC ");
-		else
-			p += sprintf(p, "  XT-PIC ");
+		if (IO_APIC_IRQ(i)) {
+			p += sprintf(p, " IO-APIC");
+			if (irq_desc[i].handler == &ioapic_level_irq_type)
+				p += sprintf(p, "-level ");
+			else
+				p += sprintf(p, "-edge  ");
+		} else
+			p += sprintf(p, "  XT-PIC       ");
 		p += sprintf(p, "  %s", action->name);
 
 		for (action=action->next; action; action = action->next) {
@@ -732,38 +751,43 @@
  * better to do it this way as thus we dont have to be aware of
  * 'pending' interrupts in the IRQ path, except at this point.
  */
-static void enable_ioapic_irq(unsigned int irq)
+static inline void self_IPI (unsigned int irq)
 {
 	irq_desc_t *desc = irq_desc + irq;
+
 	if (desc->events && !desc->ipi) {
 		desc->ipi = 1;
 		send_IPI(APIC_DEST_SELF, IO_APIC_VECTOR(irq));
 	}
 }
 
-/*
- * We do not actually disable IO-APIC irqs in hardware ...
- */
-static void disable_ioapic_irq(unsigned int irq)
+static void enable_edge_ioapic_irq(unsigned int irq)
 {
+	self_IPI(irq);
 }
 
-static void do_ioapic_IRQ(unsigned int irq, int cpu, struct pt_regs * regs)
+static void disable_edge_ioapic_irq(unsigned int irq)
 {
-	irq_desc_t *desc = irq_desc + irq;
+}
 
-	spin_lock(&irq_controller_lock);
+static void enable_level_ioapic_irq(unsigned int irq)
+{
+	enable_IO_APIC_irq(irq);
+	self_IPI(irq);
+}
 
-	/* Ack the irq inside the lock! */
-	ack_APIC_irq();
-	desc->ipi = 0;
+static void disable_level_ioapic_irq(unsigned int irq)
+{
+	disable_IO_APIC_irq(irq);
+}
 
-	/* If the irq is disabled for whatever reason, just set a flag and return */
-	if (desc->status & (IRQ_DISABLED | IRQ_INPROGRESS)) {
-		desc->events = 1;
-		spin_unlock(&irq_controller_lock);
-		return;
-	}
+/*
+ * Has to be called with the irq controller locked
+ */
+static void handle_ioapic_event (unsigned int irq, int cpu,
+						struct pt_regs * regs)
+{
+	irq_desc_t *desc = irq_desc + irq;
 
 	desc->status = IRQ_INPROGRESS;
 	desc->events = 0;
@@ -790,6 +814,63 @@
 	spin_unlock(&irq_controller_lock);
 
 no_handler:
+}
+
+static void do_edge_ioapic_IRQ(unsigned int irq, int cpu, struct pt_regs * regs)
+{
+	irq_desc_t *desc = irq_desc + irq;
+
+	/*
+	 * Edge triggered IRQs can be acked immediately
+	 */
+	ack_APIC_irq();
+
+	spin_lock(&irq_controller_lock);
+	desc->ipi = 0;
+
+	/*
+	 * If the irq is disabled for whatever reason, just
+	 * set a flag and return
+	 */
+	if (desc->status & (IRQ_DISABLED | IRQ_INPROGRESS)) {
+		desc->events = 1;
+		spin_unlock(&irq_controller_lock);
+		return;
+	}
+
+	handle_ioapic_event(irq,cpu,regs);
+
+	hardirq_exit(cpu);
+	release_irqlock(cpu);
+}
+
+static void do_level_ioapic_IRQ (unsigned int irq, int cpu,
+						 struct pt_regs * regs)
+{
+	irq_desc_t *desc = irq_desc + irq;
+
+	spin_lock(&irq_controller_lock);
+	/*
+	 * in the level triggered case we first disable the IRQ
+	 * in the IO-APIC, then we 'early ACK' the IRQ, then we
+	 * handle it and enable the IRQ when finished.
+	 */
+	disable_IO_APIC_irq(irq);
+	ack_APIC_irq();
+	desc->ipi = 0;
+
+	/*
+	 * If the irq is disabled for whatever reason, just
+	 * set a flag and return
+	 */
+	if (desc->status & (IRQ_DISABLED | IRQ_INPROGRESS)) {
+		desc->events = 1;
+		spin_unlock(&irq_controller_lock);
+		return;
+	}
+
+	handle_ioapic_event(irq,cpu,regs);
+
 	hardirq_exit(cpu);
 	release_irqlock(cpu);
 }
@@ -912,7 +993,12 @@
 		spin_lock(&irq_controller_lock);
 #ifdef __SMP__
 		if (IO_APIC_IRQ(irq)) {
-			irq_desc[irq].handler = &ioapic_irq_type;
+			if (IO_APIC_VECTOR(irq) > 0xfe)
+				/*
+				 * break visibly for now, FIXME
+				 */
+				panic("ayiee, tell mingo");
+
 			/*
 			 * First disable it in the 8259A:
 			 */
@@ -1066,18 +1152,21 @@
 	 * also, we've got to be careful not to trash gate
 	 * 0x80, because int 0x80 is hm, kindof importantish ;)
 	 */
-	for (i = 0; i < NR_IRQS ; i++)
-		if (IO_APIC_VECTOR(i) <= 0xfe)  /* HACK */ {
-			if (IO_APIC_IRQ(i)) {
-				irq_desc[i].handler = &ioapic_irq_type;
-				/*
-				 * First disable it in the 8259A:
-				 */
-				cached_irq_mask |= 1 << i;
-				if (i < 16)
-					set_8259A_irq_mask(i);
-			}
+	for (i = 0; i < NR_IRQS ; i++) {
+		if ((IO_APIC_VECTOR(i) <= 0xfe)  /* HACK */ &&
+		    (IO_APIC_IRQ(i))) {
+			if (IO_APIC_irq_trigger(i))
+				irq_desc[i].handler = &ioapic_level_irq_type;
+			else
+				irq_desc[i].handler = &ioapic_edge_irq_type;
+			/*
+			 * disable it in the 8259A:
+			 */
+			cached_irq_mask |= 1 << i;
+			if (i < 16)
+				set_8259A_irq_mask(i);
 		}
+	}
 }
 #endif
 
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/irq.h linux/arch/i386/kernel/irq.h
--- v2.1.99/linux/arch/i386/kernel/irq.h	Sat May  2 14:19:52 1998
+++ linux/arch/i386/kernel/irq.h	Tue May  5 16:10:32 1998
@@ -17,6 +17,7 @@
 void setup_IO_APIC (void);
 void init_IO_APIC_traps(void);
 int IO_APIC_get_PCI_irq_vector (int bus, int slot, int fn);
+int IO_APIC_irq_trigger (int irq);
 void make_8259A_irq (unsigned int irq);
 void send_IPI (int dest, int vector);
 void init_pic_mode (void);
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/mtrr.c linux/arch/i386/kernel/mtrr.c
--- v2.1.99/linux/arch/i386/kernel/mtrr.c	Sat May  2 14:19:52 1998
+++ linux/arch/i386/kernel/mtrr.c	Sun May  3 11:58:36 1998
@@ -104,6 +104,12 @@
 	       Moved register-setting macros into this file.
 	       Moved setup code from init/main.c to i386-specific areas.
   v1.18
+    19980502   Richard Gooch <rgooch@atnf.csiro.au>
+	       Moved MTRR detection outside conditionals in <mtrr_init>.
+  v1.19
+    19980502   Richard Gooch <rgooch@atnf.csiro.au>
+	       Documentation improvement: mention Pentium II and AGP.
+  v1.20
 */
 #include <linux/types.h>
 #include <linux/errno.h>
@@ -137,7 +143,7 @@
 #include <asm/atomic.h>
 #include <linux/smp.h>
 
-#define MTRR_VERSION            "1.18 (19980429)"
+#define MTRR_VERSION            "1.20 (19980502)"
 
 #define TRUE  1
 #define FALSE 0
@@ -801,7 +807,7 @@
 	if (ltype != type)
 	{
 	    spin_unlock (&main_lock);
-	    printk ( "mtrr: type missmatch for %lx,%lx old: %s new: %s\n",
+	    printk ( "mtrr: type mismatch for %lx,%lx old: %s new: %s\n",
 		     base, size, attrib_to_str (ltype), attrib_to_str (type) );
 	    return -EINVAL;
 	}
@@ -1193,8 +1199,8 @@
 __initfunc(int mtrr_init(void))
 #endif
 {
-#  if !defined(__SMP__) || defined(MODULE) 
     if ( !(boot_cpu_data.x86_capability & X86_FEATURE_MTRR) ) return 0;
+#  if !defined(__SMP__) || defined(MODULE) 
     printk("mtrr: v%s Richard Gooch (rgooch@atnf.csiro.au)\n", MTRR_VERSION);
 #endif
 
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/process.c linux/arch/i386/kernel/process.c
--- v2.1.99/linux/arch/i386/kernel/process.c	Thu Apr 23 20:21:28 1998
+++ linux/arch/i386/kernel/process.c	Sun May  3 18:09:24 1998
@@ -297,9 +297,9 @@
 			int i;
 			for (i=0; i<100; i++) {
 				kb_wait();
-				udelay(10);
+				udelay(50);
 				outb(0xfe,0x64);         /* pulse reset low */
-				udelay(10);
+				udelay(50);
 			}
 			/* That didn't work - force a triple fault.. */
 			__asm__ __volatile__("lidt %0": :"m" (no_idt));
diff -u --recursive --new-file v2.1.99/linux/arch/i386/kernel/smp.c linux/arch/i386/kernel/smp.c
--- v2.1.99/linux/arch/i386/kernel/smp.c	Sat May  2 14:19:52 1998
+++ linux/arch/i386/kernel/smp.c	Mon May  4 14:54:04 1998
@@ -627,20 +627,29 @@
 	smp_commenced=1;
 }
 
+__initfunc(void enable_local_APIC(void))
+{
+	unsigned long value;
+
+ 	value = apic_read(APIC_SPIV);
+ 	value |= (1<<8);		/* Enable APIC (bit==1) */
+ 	value &= ~(1<<9);		/* Enable focus processor (bit==0) */
+ 	apic_write(APIC_SPIV,value);
+
+	udelay(100);			/* B safe */
+}
+
 __initfunc(void smp_callin(void))
 {
 	extern void calibrate_delay(void);
 	int cpuid=GET_APIC_ID(apic_read(APIC_ID));
-	unsigned long l;
 
 	/*
 	 *	Activate our APIC
 	 */
 	
 	SMP_PRINTK(("CALLIN %d %d\n",hard_smp_processor_id(), smp_processor_id()));
- 	l=apic_read(APIC_SPIV);
- 	l|=(1<<8);		/* Enable */
- 	apic_write(APIC_SPIV,l);
+	enable_local_APIC();
 
 	/*
 	 * Set up our APIC timer.
@@ -1004,15 +1013,7 @@
 	}
 #endif
 
-	/*
-	 *	Enable the local APIC
-	 */
-
-	cfg=apic_read(APIC_SPIV);
-	cfg|=(1<<8);		/* Enable APIC */
-	apic_write(APIC_SPIV,cfg);
-
-	udelay(10);
+	enable_local_APIC();
 
 	/*
 	 * Set up our local APIC timer:
@@ -1561,7 +1562,7 @@
  * APIC double write bug.
  */
 
-#define APIC_DIVISOR 16
+#define APIC_DIVISOR 1
 
 void setup_APIC_timer (unsigned int clocks)
 {
@@ -1585,7 +1586,7 @@
 	 */
 	tmp_value = apic_read(APIC_TDCR);
 	apic_write(APIC_TDCR , (tmp_value & ~APIC_TDR_DIV_1 )
-				 | APIC_TDR_DIV_16);
+				 | APIC_TDR_DIV_1);
 
 	tmp_value = apic_read(APIC_TMICT);
 	apic_write(APIC_TMICT, clocks/APIC_DIVISOR);
diff -u --recursive --new-file v2.1.99/linux/drivers/block/ide-cd.c linux/drivers/block/ide-cd.c
--- v2.1.99/linux/drivers/block/ide-cd.c	Wed Apr  1 20:11:48 1998
+++ linux/drivers/block/ide-cd.c	Tue May  5 10:53:18 1998
@@ -201,10 +201,14 @@
  *                         now set ionly for CD-R and CD-RW drives.  I had 
  *                         removed this support because it produced errors.
  *                         It produced errors _only_ for non-writers. duh.
+ * 4.13  May 05, 1998  -- Suppress useless "in progress of becoming ready"
+ *                         messages, since this is not an error.
+ *                     -- Change error messages to be const
+ *                     -- Remove a "\t" which looks ugly in the syslogs
  *
  *************************************************************************/
 
-#define IDECD_VERSION "4.12"
+#define IDECD_VERSION "4.13"
 
 #include <linux/module.h>
 #include <linux/types.h>
@@ -264,11 +268,13 @@
 			return;
 	}
 	if (reqbuf->error_code == 0x70 && reqbuf->sense_key  == 0x02
-	 && reqbuf->asc        == 0x3a && reqbuf->ascq       == 0x00)
+	 && ((reqbuf->asc        == 0x3a && reqbuf->ascq       == 0x00) ||
+	     (reqbuf->asc        == 0x04 && reqbuf->ascq       == 0x01)))
 	{
 		/*
-		 * No disc in drive ("Medium not present"),
-		 * so keep the noise level down to a dull roar.
+		 * Suppress the following errors:
+		 * "Medium not present", and "in progress of becoming ready",
+		 * to keep the noise level down to a dull roar.
 		 */
 		return;
 	}
@@ -276,7 +282,7 @@
 #if VERBOSE_IDE_CD_ERRORS
 	{
 		int i;
-		char *s;
+		const char *s;
 		char buf[80];
 
 		printk ("ATAPI device %s:\n", drive->name);
@@ -346,7 +352,7 @@
 					lo = mid+1;
 			}
 
-			printk ("  The failed \"%s\" packet command was: \n\t\"", s);
+			printk ("  The failed \"%s\" packet command was: \n  \"", s);
 			for (i=0; i<sizeof (failed_command->c); i++)
 				printk ("%02x ", failed_command->c[i]);
 			printk ("\"\n");
@@ -1020,7 +1026,7 @@
 
 #define IDECD_SEEK_THRESHOLD	(1000)			/* 1000 blocks */
 #define IDECD_SEEK_TIMER	(2 * WAIT_MIN_SLEEP)	/* 40 ms */
-#define IDECD_SEEK_TIMEOUT	(20 * IDECD_SEEK_TIMER) /* 0.8 sec */
+#define IDECD_SEEK_TIMEOUT     WAIT_CMD                /* 10 sec */
 
 static void cdrom_seek_intr (ide_drive_t *drive)
 {
diff -u --recursive --new-file v2.1.99/linux/drivers/block/ide-cd.h linux/drivers/block/ide-cd.h
--- v2.1.99/linux/drivers/block/ide-cd.h	Wed Apr  1 20:11:48 1998
+++ linux/drivers/block/ide-cd.h	Tue May  5 10:53:18 1998
@@ -415,7 +415,7 @@
 /* From Table 124 of the ATAPI 1.2 spec.
    Unchanged in Table 140 of the ATAPI 2.6 draft standard. */
 
-char *sense_key_texts[16] = {
+const char *sense_key_texts[16] = {
 	"No sense data",
 	"Recovered error",
 	"Not ready",
@@ -438,7 +438,7 @@
 /* From Table 37 of the ATAPI 2.6 draft standard. */
 struct {
 	unsigned short packet_command;
-	char *text;
+	const char *text;
 } packet_command_texts[] = {
 	{ TEST_UNIT_READY, "Test Unit Ready" },
 	{ REQUEST_SENSE, "Request Sense" },
@@ -473,7 +473,7 @@
 
 struct {
 	unsigned short asc_ascq;
-	char *text;
+	const char *text;
 } sense_data_texts[] = {
 	{ 0x0000, "No additional sense information" },
 
diff -u --recursive --new-file v2.1.99/linux/drivers/block/raid5.c linux/drivers/block/raid5.c
--- v2.1.99/linux/drivers/block/raid5.c	Tue Mar 17 22:18:14 1998
+++ linux/drivers/block/raid5.c	Mon May  4 11:37:02 1998
@@ -1209,6 +1209,14 @@
 	sh->pd_idx = pd_idx;
 	if (sh->phase != PHASE_COMPLETE && sh->phase != PHASE_BEGIN)
 		PRINTK(("stripe %lu catching the bus!\n", sh->sector));
+	if (sh->bh_new[dd_idx]) {
+		printk("raid5: bug: stripe->bh_new[%d], sector %lu exists\n", dd_idx, sh->sector);
+		printk("raid5: bh %p, bh_new %p\n", bh, sh->bh_new[dd_idx]);
+		lock_stripe(sh);
+		md_wakeup_thread(raid_conf->thread);
+		wait_on_stripe(sh);
+		goto repeat;
+	}
 	add_stripe_bh(sh, bh, dd_idx, rw);
 
 	md_wakeup_thread(raid_conf->thread);
diff -u --recursive --new-file v2.1.99/linux/drivers/misc/parport_procfs.c linux/drivers/misc/parport_procfs.c
--- v2.1.99/linux/drivers/misc/parport_procfs.c	Sat Apr 25 18:13:11 1998
+++ linux/drivers/misc/parport_procfs.c	Tue May  5 10:44:06 1998
@@ -37,8 +37,8 @@
 	int retval = -EINVAL;
 	int newirq = PARPORT_IRQ_NONE;
 	struct parport *pp = (struct parport *)data;
-	struct pardevice *cad = pp->cad;
 	int oldirq = pp->irq;
+	unsigned long flags;
 
 /*
  * We can have these valid cases:
@@ -70,35 +70,30 @@
 	if (oldirq == newirq)
 		goto out;
 
+	spin_lock_irqsave(&pp->lock, flags);
 	if (pp->flags & PARPORT_FLAG_COMA)
 		goto out_ok;
 
-	if (newirq != PARPORT_IRQ_NONE) { 
-		void (*handler)(int, void *, struct pt_regs *);
+	retval = -EBUSY;
+	if (pp->cad)
+		goto out_unlock;
 
-		if (cad && cad->irq_func)
-			handler = cad->irq_func;
-		else
-			handler = parport_null_intr_func;
-
-		retval = request_irq(newirq, handler,
-				     SA_INTERRUPT,
-				     cad ? cad->name : pp->name,
-				     cad ? cad->private : NULL);
+	if (newirq != PARPORT_IRQ_NONE) { 
+		retval = request_irq(newirq, parport_null_intr_func,
+				     SA_INTERRUPT, pp->name, NULL);
 		if (retval)
-			goto out;
+			goto out_unlock;
 		else retval = count;
 	}
 
-	if (oldirq != PARPORT_IRQ_NONE) {
-		if (cad && cad->irq_func)
-			free_irq(oldirq, cad->private);
-		else
-			free_irq(oldirq, NULL);
-	}
+	if (oldirq != PARPORT_IRQ_NONE)
+		free_irq(oldirq, NULL);
 
 out_ok:
 	pp->irq = newirq;
+
+out_unlock:
+	spin_unlock_irqrestore (&pp->lock, flags);
 
 out:
 	return retval;
diff -u --recursive --new-file v2.1.99/linux/drivers/misc/parport_share.c linux/drivers/misc/parport_share.c
--- v2.1.99/linux/drivers/misc/parport_share.c	Sat Apr 25 18:13:11 1998
+++ linux/drivers/misc/parport_share.c	Mon May  4 11:03:09 1998
@@ -308,7 +308,9 @@
 	}
 
 	/* Now we do the change of devices */
+	spin_lock_irqsave(&port->lock, flags);
 	port->cad = dev;
+	spin_unlock_irqrestore(&port->lock, flags);
 
 	/* Swap the IRQ handlers. */
 	if (port->irq != PARPORT_IRQ_NONE) {
@@ -346,9 +348,8 @@
 			dev->waitprev = port->waittail;
 			if (port->waittail)
 				port->waittail->waitnext = dev;
-			else {
-				port->waithead = dev->port->waittail = dev;
-			}
+			else
+				port->waithead = port->waittail = dev;
 		}
 		spin_unlock_irqrestore (&port->lock, flags);
 	}
diff -u --recursive --new-file v2.1.99/linux/drivers/net/ppp.c linux/drivers/net/ppp.c
--- v2.1.99/linux/drivers/net/ppp.c	Wed Apr  1 20:11:52 1998
+++ linux/drivers/net/ppp.c	Sun May  3 12:03:35 1998
@@ -8,7 +8,7 @@
  *  Dynamic PPP devices by Jim Freeman <jfree@caldera.com>.
  *  ppp_tty_receive ``noisy-raise-bug'' fixed by Ove Ewerlid <ewerlid@syscon.uu.se>
  *
- *  ==FILEVERSION 980319==
+ *  ==FILEVERSION 980501==
  *
  *  NOTE TO MAINTAINERS:
  *     If you modify this file at all, please set the number above to the
@@ -107,8 +107,10 @@
 #define PPP_LQR 0xc025	/* Link Quality Reporting Protocol */
 #endif
 
+#ifdef CONFIG_MODULES
 static int ppp_register_compressor (struct compressor *cp);
 static void ppp_unregister_compressor (struct compressor *cp);
+#endif
 
 /*
  * Local functions
@@ -3210,6 +3212,7 @@
 	return (struct compressor *) 0;
 }
 
+#ifdef CONFIG_MODULES
 static int ppp_register_compressor (struct compressor *cp)
 {
 	struct compressor_link *new;
@@ -3261,6 +3264,7 @@
 	}
 	restore_flags(flags);
 }
+#endif
 
 /*************************************************************
  * Module support routines
diff -u --recursive --new-file v2.1.99/linux/drivers/net/sdla_fr.c linux/drivers/net/sdla_fr.c
--- v2.1.99/linux/drivers/net/sdla_fr.c	Wed Apr  8 19:36:27 1998
+++ linux/drivers/net/sdla_fr.c	Sat May  2 14:22:29 1998
@@ -831,7 +831,7 @@
 {
 	int hdr_len = 0;
 	skb->protocol = type;
-	hdr_len = wan_encapsulate(skb, dev);
+	hdr_len = wanrouter_encapsulate(skb, dev);
 	if (hdr_len < 0) 
 	{
 		hdr_len = 0;
@@ -1486,7 +1486,7 @@
 		/* Decapsulate packet and pass it up the protocol stack */
 		skb->dev = dev;
 		buf = skb_pull(skb, 1);		/* remove hardware header */
-		if (!wan_type_trans(skb, dev)) 
+		if (!wanrouter_type_trans(skb, dev)) 
 		{
 			/* can't decapsulate packet */
 			dev_kfree_skb(skb);
@@ -1601,7 +1601,7 @@
 					skb->dev = dev;
 					/* remove hardware header */
 					buf = skb_pull(skb, 1);
-					if (!wan_type_trans(skb, dev)) 
+					if (!wanrouter_type_trans(skb, dev)) 
 					{
 						/* can't decapsulate packet */
 						dev_kfree_skb(skb);
@@ -2746,7 +2746,7 @@
 			   stack */
 			new_skb->dev = dev;
 			buf = skb_pull(new_skb, 1);	/* remove hardware header */
-			if (!wan_type_trans(new_skb, dev)) 
+			if (!wanrouter_type_trans(new_skb, dev)) 
 			{
 				++chan->UDP_FPIPE_mgmt_not_passed_to_stack;
 				/* can't decapsulate packet */
@@ -2944,7 +2944,7 @@
 			new_skb->dev = dev;
 			/* remove hardware header */
 			buf = skb_pull(new_skb, 1);
-			if (!wan_type_trans(new_skb, dev)) 
+			if (!wanrouter_type_trans(new_skb, dev)) 
 			{
 				/* can't decapsulate packet */
 				++chan->UDP_DRVSTATS_mgmt_not_passed_to_stack;
diff -u --recursive --new-file v2.1.99/linux/drivers/net/sdla_x25.c linux/drivers/net/sdla_x25.c
--- v2.1.99/linux/drivers/net/sdla_x25.c	Wed Apr  8 19:36:27 1998
+++ linux/drivers/net/sdla_x25.c	Sat May  2 14:22:29 1998
@@ -649,7 +649,7 @@
 	skb->protocol = type;
 	if (!chan->protocol)
 	{
-		hdr_len = wan_encapsulate(skb, dev);
+		hdr_len = wanrouter_encapsulate(skb, dev);
 		if (hdr_len < 0)
 		{
 			hdr_len = 0;
@@ -999,7 +999,7 @@
 	chan->rx_skb = NULL;		/* dequeue packet */
 
 	/* Decapsulate packet, if necessary */
-	if (!skb->protocol && !wan_type_trans(skb, dev))
+	if (!skb->protocol && !wanrouter_type_trans(skb, dev))
 	{
 		/* can't decapsulate packet */
 		dev_kfree_skb(skb);
diff -u --recursive --new-file v2.1.99/linux/drivers/net/sdlamain.c linux/drivers/net/sdlamain.c
--- v2.1.99/linux/drivers/net/sdlamain.c	Mon Jan 12 14:46:16 1998
+++ linux/drivers/net/sdlamain.c	Sat May  2 14:22:29 1998
@@ -152,7 +152,7 @@
 		wandev->setup    = &setup;
 		wandev->shutdown = &shutdown;
 		wandev->ioctl    = &ioctl;
-		err = register_wandev(wandev);
+		err = register_wan_device(wandev);
 		if (err)
 		{
 			printk(KERN_ERR
@@ -179,7 +179,7 @@
 	for (i = 0; i < ncards; ++i)
 	{
 		sdla_t* card = &card_array[i];
-		unregister_wandev(card->devname);
+		unregister_wan_device(card->devname);
 	}
 	kfree(card_array);
 }
diff -u --recursive --new-file v2.1.99/linux/drivers/net/smc-mca.c linux/drivers/net/smc-mca.c
--- v2.1.99/linux/drivers/net/smc-mca.c	Wed Apr  1 20:11:52 1998
+++ linux/drivers/net/smc-mca.c	Sat May  2 14:22:29 1998
@@ -337,7 +337,7 @@
 		dev->name = namelist+(NAMELEN*this_dev);
 		dev->irq = irq[this_dev];
 		dev->base_addr = io[this_dev];
-		dev->init = ultra_probe;
+		dev->init = ultramca_probe;
 		if (io[this_dev] == 0)
 		{
 			if (this_dev != 0)
diff -u --recursive --new-file v2.1.99/linux/drivers/pci/oldproc.c linux/drivers/pci/oldproc.c
--- v2.1.99/linux/drivers/pci/oldproc.c	Fri Apr 10 13:03:48 1998
+++ linux/drivers/pci/oldproc.c	Mon May  4 13:24:12 1998
@@ -1,5 +1,5 @@
 /*
- *	$Id: oldproc.c,v 1.10 1998/03/15 13:50:11 ecd Exp $
+ *	$Id: oldproc.c,v 1.12 1998/05/01 10:58:21 mj Exp $
  *
  *	Backward-compatible procfs interface for PCI.
  *
@@ -60,10 +60,14 @@
 	DEVICE( ATI,		ATI_210888CX,   "210888CX"),
 	DEVICE( ATI,		ATI_215GB,	"Mach64 GB"),
 	DEVICE( ATI,		ATI_215GD,	"Mach64 GD (Rage Pro)"),
+	DEVICE( ATI,		ATI_215GI,	"Mach64 GI (Rage Pro)"),
 	DEVICE( ATI,		ATI_215GP,	"Mach64 GP (Rage Pro)"),
+	DEVICE( ATI,		ATI_215GQ,	"Mach64 GQ (Rage Pro)"),
 	DEVICE( ATI,		ATI_215GT,	"Mach64 GT (Rage II)"),
 	DEVICE( ATI,		ATI_215GTB,	"Mach64 GT (Rage II)"),
 	DEVICE( ATI,		ATI_210888GX,   "210888GX"),
+	DEVICE( ATI,		ATI_215LG,	"Mach64 LG (Rage Pro)"),
+	DEVICE( ATI,		ATI_264LT,	"Mach64 LT"),
 	DEVICE( ATI,		ATI_264VT,	"Mach64 VT"),
 	DEVICE( VLSI,		VLSI_82C592,	"82C592-FC1"),
 	DEVICE( VLSI,		VLSI_82C593,	"82C593-FC1"),
@@ -116,6 +120,9 @@
 	DEVICE( IBM,		IBM_82G2675,	"82G2675"),
 	DEVICE( IBM,		IBM_MCA,	"MicroChannel"),
 	DEVICE( IBM,		IBM_82351,	"82351"),
+	DEVICE( IBM,		IBM_SERVERAID,	"ServeRAID"),
+	DEVICE( IBM,		IBM_TR_WAKE,	"Wake On LAN Token Ring"),
+	DEVICE( IBM,		IBM_3780IDSP,	"MWave DSP"),
 	DEVICE( WD,		WD_7197,	"WD 7197"),
 	DEVICE( AMD,		AMD_LANCE,	"79C970"),
 	DEVICE( AMD,		AMD_SCSI,	"53C974"),
@@ -135,12 +142,15 @@
 	DEVICE( CT,		CT_65548,	"65548"),
 	DEVICE(	CT,		CT_65550,	"65550"),
 	DEVICE( CT,		CT_65554,	"65554"),
+	DEVICE( CT,		CT_65555,	"65555"),
 	DEVICE( MIRO,		MIRO_36050,	"ZR36050"),
 	DEVICE( NEC,		NEC_PCX2,	"PowerVR PCX2"),
 	DEVICE( FD,		FD_36C70,	"TMC-18C30"),
-	DEVICE( SI,		SI_6201,	"6201"),
+	DEVICE( SI,		SI_5591_AGP,	"5591/5592 AGP"),
 	DEVICE( SI,		SI_6202,	"6202"),
 	DEVICE( SI,		SI_503,		"85C503"),
+	DEVICE( SI,		SI_ACPI,	"ACPI"),
+	DEVICE( SI,		SI_5597_VGA,	"5597/5598 VGA"),
 	DEVICE( SI,		SI_6205,	"6205"),
 	DEVICE( SI,		SI_501,		"85C501"),
 	DEVICE( SI,		SI_496,		"85C496"),
@@ -149,8 +159,9 @@
 	DEVICE( SI,		SI_5511,		"85C5511"),
 	DEVICE( SI,		SI_5513,		"85C5513"),
 	DEVICE( SI,		SI_5571,	"5571"),
-	DEVICE( SI,		SI_5597,	"5597"),
-	DEVICE( SI,		SI_7001,	"7001"),
+	DEVICE( SI,		SI_5591,	"5591/5592 Host"),
+	DEVICE( SI,		SI_5597,	"5597/5598 Host"),
+	DEVICE( SI,		SI_7001,	"7001 USB"),
 	DEVICE( HP,		HP_J2585A,	"J2585A"),
 	DEVICE( HP,		HP_J2585B,	"J2585B (Lassen)"),
 	DEVICE( PCTECH,		PCTECH_RZ1000,  "RZ1000 (buggy)"),
@@ -198,6 +209,7 @@
 	DEVICE( UMC,		UMC_UM8891N,	"UM8891N"),
 	DEVICE( X,		X_AGX016,	"ITT AGX016"),
 	DEVICE( PICOP,		PICOP_PT86C52X,	"PT86C52x Vesuvius"),
+	DEVICE( PICOP,		PICOP_PT80C524,	"PT80C524 Nile"),
 	DEVICE( APPLE,		APPLE_BANDIT,	"Bandit"),
 	DEVICE( APPLE,		APPLE_GC,	"Grand Central"),
 	DEVICE( APPLE,		APPLE_HYDRA,	"Hydra"),
@@ -242,6 +254,8 @@
 	DEVICE( WINBOND,	WINBOND_83C553,	"W83C553"),
 	DEVICE( DATABOOK,      	DATABOOK_87144,	"DB87144"),
 	DEVICE( PLX,		PLX_9080,	"PCI9080 I2O"),
+	DEVICE( MADGE,		MADGE_MK2,	"Smart 16/4 BM Mk2 Ringnode"),
+	DEVICE( 3COM,		3COM_3C339,	"3C339 TokenRing"),
 	DEVICE( 3COM,		3COM_3C590,	"3C590 10bT"),
 	DEVICE( 3COM,		3COM_3C595TX,	"3C595 100bTX"),
 	DEVICE( 3COM,		3COM_3C595T4,	"3C595 100bT4"),
@@ -249,6 +263,8 @@
 	DEVICE( 3COM,		3COM_3C900TPO,	"3C900 10bTPO"),
 	DEVICE( 3COM,		3COM_3C900COMBO,"3C900 10b Combo"),
 	DEVICE( 3COM,		3COM_3C905TX,	"3C905 100bTX"),
+	DEVICE( 3COM,		3COM_3C905T4,	"3C905 100bT4"),
+	DEVICE( 3COM,		3COM_3C905B_TX,	"3C905B 100bTX"),
 	DEVICE( SMC,		SMC_EPIC100,	"9432 TX"),
 	DEVICE( AL,		AL_M1445,	"M1445"),
 	DEVICE( AL,		AL_M1449,	"M1449"),
@@ -274,6 +290,8 @@
 	DEVICE( ASP,		ASP_ABP940,	"ABP940"),
 	DEVICE( ASP,		ASP_ABP940U,	"ABP940U"),
 	DEVICE( ASP,		ASP_ABP940UW,	"ABP940UW"),
+	DEVICE( MACRONIX,	MACRONIX_MX98713,"MX98713"),
+	DEVICE( MACRONIX,	MACRONIX_MX987x5,"MX98715 / MX98725"),
 	DEVICE( CERN,		CERN_SPSB_PMC,	"STAR/RD24 SCI-PCI (PMC)"),
 	DEVICE( CERN,		CERN_SPSB_PCI,	"STAR/RD24 SCI-PCI (PMC)"),
 	DEVICE( CERN,		CERN_HIPPI_DST,	"HIPPI destination"),
@@ -282,12 +300,14 @@
 	DEVICE( TEKRAM2,	TEKRAM2_690c,	"DC690c"),
 	DEVICE( TUNDRA,		TUNDRA_CA91C042,"CA91C042 Universe"),
 	DEVICE( AMCC,		AMCC_MYRINET,	"Myrinet PCI (M2-PCI-32)"),
+	DEVICE( AMCC,		AMCC_PARASTATION,"ParaStation Interface"),
 	DEVICE( AMCC,		AMCC_S5933,	"S5933 PCI44"),
 	DEVICE( AMCC,		AMCC_S5933_HEPC3,"S5933 Traquair HEPC3"),
 	DEVICE( INTERG,		INTERG_1680,	"IGA-1680"),
 	DEVICE( INTERG,         INTERG_1682,    "IGA-1682"),
 	DEVICE( REALTEK,	REALTEK_8029,	"8029"),
 	DEVICE( REALTEK,	REALTEK_8129,	"8129"),
+	DEVICE( REALTEK,	REALTEK_8139,	"8139"),
 	DEVICE( TRUEVISION,	TRUEVISION_T1000,"TARGA 1000"),
 	DEVICE( INIT,		INIT_320P,	"320 P"),
 	DEVICE( INIT,		INIT_360P,	"360 P"),
@@ -304,6 +324,7 @@
 	DEVICE( VIA,		VIA_82C595_97,	"VT 82C595 Apollo VP2/97"),
 	DEVICE( VIA,		VIA_82C586_2,	"VT 82C586 Apollo USB"),
 	DEVICE( VIA,		VIA_82C586_3,	"VT 82C586B Apollo ACPI"),
+	DEVICE( VIA,		VIA_86C100A,	"VT 86C100A"),
 	DEVICE( VIA,		VIA_82C597_1,	"VT 82C597 Apollo VP3 AGP"),
 	DEVICE( VORTEX,		VORTEX_GDT60x0,	"GDT 60x0"),
 	DEVICE( VORTEX,		VORTEX_GDT6000B,"GDT 6000b"),
@@ -342,6 +363,7 @@
 	DEVICE( FORE,		FORE_PCA200PC, "PCA-200PC"),
 	DEVICE( FORE,		FORE_PCA200E,	 "PCA-200E"),
 	DEVICE( IMAGINGTECH,	IMAGINGTECH_ICPCI, "MVC IC-PCI"),
+	DEVICE( PHILIPS,	PHILIPS_SAA7145,"SAA7145"),
 	DEVICE( PHILIPS,	PHILIPS_SAA7146,"SAA7146"),
 	DEVICE( CYCLONE,	CYCLONE_SDK,	"SDK"),
 	DEVICE( ALLIANCE,	ALLIANCE_PROMOTIO, "Promotion-6410"),
@@ -356,6 +378,7 @@
 	DEVICE( DIGI,		DIGI_CX,	"AccelPort C/X"),
 	DEVICE( DIGI,		DIGI_XRJ,	"AccelPort Xr/J"),
 	DEVICE( DIGI,		DIGI_EPCJ,	"AccelPort EPC/J"),
+	DEVICE( DIGI,		DIGI_XR_920,	"AccelPort Xr 920"),
 	DEVICE( MUTECH,		MUTECH_MV1000,	"MV-1000"),
 	DEVICE( RENDITION,	RENDITION_VERITE,"Verite 1000"),
 	DEVICE( RENDITION,	RENDITION_VERITE2100,"Verite 2100"),
@@ -377,20 +400,21 @@
 	DEVICE( IKON,		IKON_10117,	"10117 Greensheet"),
 	DEVICE( ZORAN,		ZORAN_36057,	"ZR36057"),
 	DEVICE( ZORAN,		ZORAN_36120,	"ZR36120"),
+	DEVICE( KINETIC,	KINETIC_2915,	"2915 CAMAC"),
 	DEVICE( COMPEX,		COMPEX_ENET100VG4, "Readylink ENET100-VG4"),
 	DEVICE( COMPEX,		COMPEX_RL2000,	"ReadyLink 2000"),
 	DEVICE( RP,             RP8OCTA,        "RocketPort 8 Oct"),
 	DEVICE( RP,             RP8INTF,        "RocketPort 8 Intf"),
 	DEVICE( RP,             RP16INTF,       "RocketPort 16 Intf"),
 	DEVICE( RP,             RP32INTF,       "RocketPort 32 Intf"),
-	DEVICE( ESSENTIAL,      ROADRUNNER,     "RoadRunner serial HIPPI"),
 	DEVICE( CYCLADES,	CYCLOM_Y_Lo,	"Cyclom-Y below 1Mbyte"),
 	DEVICE( CYCLADES,	CYCLOM_Y_Hi,	"Cyclom-Y above 1Mbyte"),
 	DEVICE( CYCLADES,	CYCLOM_Z_Lo,	"Cyclom-Z below 1Mbyte"),
 	DEVICE( CYCLADES,	CYCLOM_Z_Hi,	"Cyclom-Z above 1Mbyte"),
+	DEVICE( ESSENTIAL,	ESSENTIAL_ROADRUNNER,"Roadrunner serial HIPPI"),
 	DEVICE( O2,		O2_6832,	"6832"),
 	DEVICE( 3DFX,		3DFX_VOODOO,	"Voodoo"),
-	DEVICE( 3DFX,		3DFX_VOODOO2,	"Voodoo2"),	
+	DEVICE( 3DFX,		3DFX_VOODOO2,	"Voodoo2"),
 	DEVICE( SIGMADES,	SIGMADES_6425,	"REALmagic64/GX"),
 	DEVICE( STALLION,	STALLION_ECHPCI832,"EasyConnection 8/32"),
 	DEVICE( STALLION,	STALLION_ECHPCI864,"EasyConnection 8/64"),
@@ -400,15 +424,20 @@
 	DEVICE( OPTIBASE,	OPTIBASE_VPLEX,	"VideoPlex"),
 	DEVICE( OPTIBASE,	OPTIBASE_VPLEXCC,"VideoPlex CC"),
 	DEVICE( OPTIBASE,	OPTIBASE_VQUEST,"VideoQuest"),
+	DEVICE( SATSAGEM,	SATSAGEM_PCR2101,"PCR2101 DVB receiver"),
+	DEVICE( SATSAGEM,	SATSAGEM_TELSATTURBO,"Telsat Turbo DVB"),
+	DEVICE( HUGHES,		HUGHES_DIRECPC,	"DirecPC"),
 	DEVICE( ENSONIQ,	ENSONIQ_AUDIOPCI,"AudioPCI"),
 	DEVICE( PICTUREL,	PICTUREL_PCIVST,"PCIVST"),
 	DEVICE( NVIDIA_SGS,	NVIDIA_SGS_RIVA128,	"Riva 128"),
+	DEVICE( CBOARDS,	CBOARDS_DAS1602_16,"DAS1602/16"),
 	DEVICE( SYMPHONY,	SYMPHONY_101,	"82C101"),
 	DEVICE( TEKRAM,		TEKRAM_DC290,	"DC-290"),
 	DEVICE( 3DLABS,		3DLABS_300SX,	"GLINT 300SX"),
 	DEVICE( 3DLABS,		3DLABS_500TX,	"GLINT 500TX"),
 	DEVICE( 3DLABS,		3DLABS_DELTA,	"GLINT Delta"),
 	DEVICE( 3DLABS,		3DLABS_PERMEDIA,"PERMEDIA"),
+	DEVICE( 3DLABS,		3DLABS_MX,	"GLINT MX"),
 	DEVICE( AVANCE,		AVANCE_ALG2064,	"ALG2064i"),
 	DEVICE( AVANCE,		AVANCE_2302,	"ALG-2302"),
 	DEVICE( NETVIN,		NETVIN_NV5000SC,"NV5000"),
@@ -450,6 +479,7 @@
 	DEVICE( INTEL,		INTEL_82371MX,	"430MX - 82371MX MPIIX"),
 	DEVICE( INTEL,		INTEL_82437MX,	"430MX - 82437MX MTSC"),
 	DEVICE( INTEL,		INTEL_82441,	"82441FX Natoma"),
+	DEVICE( INTEL,		INTEL_82380FB,	"82380FB Mobile"),
 	DEVICE( INTEL,		INTEL_82439,	"82439HX Triton II"),
 	DEVICE(	INTEL,		INTEL_82371SB_0,"82371SB PIIX3 ISA"),
 	DEVICE(	INTEL,		INTEL_82371SB_1,"82371SB PIIX3 IDE"),
@@ -462,9 +492,13 @@
 	DEVICE( INTEL,		INTEL_82371AB_3,"82371AB PIIX4 ACPI"),
 	DEVICE( INTEL,		INTEL_82443LX_0,"440LX - 82443LX PAC Host"),
 	DEVICE( INTEL,		INTEL_82443LX_1,"440LX - 82443LX PAC AGP"),
+	DEVICE( INTEL,		INTEL_82443BX_0,"440BX - 82443BX Host"),
+	DEVICE( INTEL,		INTEL_82443BX_1,"440BX - 82443BX AGP"),
+	DEVICE( INTEL,		INTEL_82443BX_2,"440BX - 82443BX Host (no AGP)"),
 	DEVICE( INTEL,		INTEL_P6,	"Orion P6"),
  	DEVICE( INTEL,		INTEL_82450GX,	"82450GX Orion P6"),
 	DEVICE(	KTI,		KTI_ET32P2,	"ET32P2"),
+	DEVICE( ADAPTEC,	ADAPTEC_7810,	"AIC-7810 RAID"),
 	DEVICE( ADAPTEC,	ADAPTEC_7850,	"AIC-7850"),
 	DEVICE( ADAPTEC,	ADAPTEC_7855,	"AIC-7855"),
 	DEVICE( ADAPTEC,	ADAPTEC_5800,	"AIC-5800"),
@@ -481,7 +515,9 @@
 	DEVICE( ADAPTEC,	ADAPTEC_7882,	"AIC-7882U"),
 	DEVICE( ADAPTEC,	ADAPTEC_7883,	"AIC-7883U"),
 	DEVICE( ADAPTEC,	ADAPTEC_7884,	"AIC-7884U"),
+	DEVICE( ADAPTEC,	ADAPTEC_1030,	"ABA-1030 DVB receiver"),
   	DEVICE( ATRONICS,	ATRONICS_2015,	"IDE-2015PL"),
+	DEVICE( TIGERJET,	TIGERJET_300,	"Tiger300 ISDN"),
 	DEVICE( ARK,		ARK_STING,	"Stingray"),
 	DEVICE( ARK,		ARK_STINGARK,	"Stingray ARK 2000PV"),
 	DEVICE( ARK,		ARK_2000MT,	"2000MT")
@@ -658,6 +694,7 @@
 	      case PCI_VENDOR_ID_WINBOND:	return "Winbond";
 	      case PCI_VENDOR_ID_DATABOOK:	return "Databook";
 	      case PCI_VENDOR_ID_PLX:		return "PLX";
+	      case PCI_VENDOR_ID_MADGE:		return "Madge Networks";
 	      case PCI_VENDOR_ID_3COM:		return "3Com";
 	      case PCI_VENDOR_ID_SMC:		return "SMC";
 	      case PCI_VENDOR_ID_AL:		return "Acer Labs";
@@ -665,6 +702,7 @@
 	      case PCI_VENDOR_ID_SURECOM:	return "Surecom";
 	      case PCI_VENDOR_ID_NEOMAGIC:	return "Neomagic";
 	      case PCI_VENDOR_ID_ASP:		return "Advanced System Products";
+	      case PCI_VENDOR_ID_MACRONIX:	return "Macronix";
 	      case PCI_VENDOR_ID_CERN:		return "CERN";
 	      case PCI_VENDOR_ID_NVIDIA:	return "NVidia";
 	      case PCI_VENDOR_ID_IMS:		return "IMS";
@@ -699,17 +737,23 @@
 	      case PCI_VENDOR_ID_AURAVISION:	return "Auravision";
 	      case PCI_VENDOR_ID_IKON:		return "Ikon";
 	      case PCI_VENDOR_ID_ZORAN:		return "Zoran";
+	      case PCI_VENDOR_ID_KINETIC:	return "Kinetic";
 	      case PCI_VENDOR_ID_COMPEX:	return "Compex";
 	      case PCI_VENDOR_ID_RP:		return "Comtrol";
 	      case PCI_VENDOR_ID_CYCLADES:	return "Cyclades";
 	      case PCI_VENDOR_ID_O2:		return "O2 Micro";
 	      case PCI_VENDOR_ID_3DFX:		return "3Dfx";
-	      case PCI_VENDOR_ID_STALLION:	return "Stallion Technologies";
 	      case PCI_VENDOR_ID_SIGMADES:	return "Sigma Designs";
+	      case PCI_VENDOR_ID_CCUBE:		return "C-Cube";
+	      case PCI_VENDOR_ID_DIPIX:		return "Dipix";
+	      case PCI_VENDOR_ID_STALLION:	return "Stallion Technologies";
 	      case PCI_VENDOR_ID_OPTIBASE:	return "Optibase";
+	      case PCI_VENDOR_ID_SATSAGEM:	return "SatSagem";
+	      case PCI_VENDOR_ID_HUGHES:	return "Hughes";
 	      case PCI_VENDOR_ID_ENSONIQ:	return "Ensoniq";
 	      case PCI_VENDOR_ID_PICTUREL:	return "Picture Elements";
 	      case PCI_VENDOR_ID_NVIDIA_SGS:	return "NVidia/SGS Thomson";
+	      case PCI_VENDOR_ID_CBOARDS:	return "ComputerBoards";
 	      case PCI_VENDOR_ID_SYMPHONY:	return "Symphony";
 	      case PCI_VENDOR_ID_TEKRAM:	return "Tekram";
 	      case PCI_VENDOR_ID_3DLABS:	return "3Dlabs";
@@ -720,6 +764,7 @@
 	      case PCI_VENDOR_ID_KTI:		return "KTI";
 	      case PCI_VENDOR_ID_ADAPTEC:	return "Adaptec";
 	      case PCI_VENDOR_ID_ATRONICS:	return "Atronics";
+	      case PCI_VENDOR_ID_TIGERJET:	return "TigerJet";
 	      case PCI_VENDOR_ID_ARK:		return "ARK Logic";
 	      default:				return "Unknown vendor";
 	}
@@ -744,7 +789,7 @@
 static int sprint_dev_config(struct pci_dev *dev, char *buf, int size)
 {
 	unsigned long base;
-	unsigned int l, class_rev, bus, devfn;
+	unsigned int class_rev, bus, devfn;
 	unsigned short vendor, device, status;
 	unsigned char bist, latency, min_gnt, max_lat;
 	int reg, len = 0;
@@ -835,12 +880,7 @@
 		if (len + 40 > size) {
 			return -1;
 		}
-		pcibios_read_config_dword(bus, devfn,
-				PCI_BASE_ADDRESS_0 + (reg << 2), &l);
-		if (l == 0xffffffff)
-			base = 0;
-		else
-			base = l;
+		base = dev->base_address[reg];
 		if (!base)
 			continue;
 
@@ -863,12 +903,7 @@
 			      case PCI_BASE_ADDRESS_MEM_TYPE_1M:
 				type = "20 bit"; break;
 			      case PCI_BASE_ADDRESS_MEM_TYPE_64:
-				type = "64 bit";
-				/* read top 32 bit address of base addr: */
-				reg += 4;
-				pcibios_read_config_dword(bus, devfn, reg, &l);
-				base |= ((u64) l) << 32;
-				break;
+				type = "64 bit"; break;
 			}
 			len += sprintf(buf + len,
 				       "\n      %srefetchable %s memory at "
diff -u --recursive --new-file v2.1.99/linux/drivers/pci/pci.c linux/drivers/pci/pci.c
--- v2.1.99/linux/drivers/pci/pci.c	Sat May  2 14:19:53 1998
+++ linux/drivers/pci/pci.c	Sun May  3 11:30:01 1998
@@ -1,5 +1,5 @@
 /*
- *	$Id: pci.c,v 1.79 1998/04/17 16:25:24 mj Exp $
+ *	$Id: pci.c,v 1.84 1998/05/02 19:22:06 mj Exp $
  *
  *	PCI Bus Services
  *
@@ -68,11 +68,48 @@
 }
 
 
+int
+pci_read_config_byte(struct pci_dev *dev, u8 where, u8 *val)
+{
+	return pcibios_read_config_byte(dev->bus->number, dev->devfn, where, val);
+}
+
+int
+pci_read_config_word(struct pci_dev *dev, u8 where, u16 *val)
+{
+	return pcibios_read_config_word(dev->bus->number, dev->devfn, where, val);
+}
+
+int
+pci_read_config_dword(struct pci_dev *dev, u8 where, u32 *val)
+{
+	return pcibios_read_config_dword(dev->bus->number, dev->devfn, where, val);
+}
+
+int
+pci_write_config_byte(struct pci_dev *dev, u8 where, u8 val)
+{
+	return pcibios_write_config_byte(dev->bus->number, dev->devfn, where, val);
+}
+
+int
+pci_write_config_word(struct pci_dev *dev, u8 where, u16 val)
+{
+	return pcibios_write_config_word(dev->bus->number, dev->devfn, where, val);
+}
+
+int
+pci_write_config_dword(struct pci_dev *dev, u8 where, u32 val)
+{
+	return pcibios_write_config_dword(dev->bus->number, dev->devfn, where, val);
+}
+
+
 void
 pci_set_master(struct pci_dev *dev)
 {
-	unsigned short cmd;
-	unsigned char lat;
+	u16 cmd;
+	u8 lat;
 
 	pci_read_config_word(dev, PCI_COMMAND, &cmd);
 	if (! (cmd & PCI_COMMAND_MASTER)) {
@@ -89,16 +126,43 @@
 	}
 }
 
+__initfunc(void pci_read_bases(struct pci_dev *dev, unsigned int howmany))
+{
+	unsigned int reg;
+	u32 l;
+
+	for(reg=0; reg<howmany; reg++) {
+		pci_read_config_dword(dev, PCI_BASE_ADDRESS_0 + (reg << 2), &l);
+		if (l == 0xffffffff)
+			continue;
+		dev->base_address[reg] = l;
+		if ((l & PCI_MEMORY_RANGE_TYPE_MASK) == PCI_BASE_ADDRESS_MEM_TYPE_64) {
+			reg++;
+			pci_read_config_dword(dev, PCI_BASE_ADDRESS_0 + (reg << 2), &l);
+			if (l) {
+#if BITS_PER_LONG == 64
+				dev->base_address[reg-1] |= ((unsigned long) l) << 32;
+#else
+				printk("PCI: Unable to handle 64-bit address for device %02x:%02x\n",
+					dev->bus->number, dev->devfn);
+				dev->base_address[reg-1] = 0;
+#endif
+			}
+		}
+	}
+}
+
 
 __initfunc(unsigned int pci_scan_bus(struct pci_bus *bus))
 {
 	unsigned int devfn, l, max, class;
 	unsigned char cmd, irq, tmp, hdr_type, is_multi = 0;
-	struct pci_dev *dev;
+	struct pci_dev *dev, **bus_last;
 	struct pci_bus *child;
 	int reg;
 
 	DBG("pci_scan_bus for bus %d\n", bus->number);
+	bus_last = &bus->devices;
 	max = bus->secondary;
 	for (devfn = 0; devfn < 0xff; ++devfn) {
 		if (PCI_FUNC(devfn) && !is_multi) {
@@ -111,8 +175,8 @@
 
 		pcibios_read_config_dword(bus->number, devfn, PCI_VENDOR_ID, &l);
 		/* some broken boards return 0 if a slot is empty: */
-		if (l == 0xffffffff || l == 0x00000000) {
-			hdr_type = 0;
+		if (l == 0xffffffff || l == 0x00000000 || l == 0x0000ffff || l == 0xffff0000) {
+			is_multi = 0;
 			continue;
 		}
 
@@ -133,11 +197,12 @@
 		pcibios_read_config_dword(bus->number, devfn, PCI_CLASS_REVISION, &class);
 		class >>= 8;				    /* upper 3 bytes */
 		dev->class = class;
+		class >>= 8;
 		dev->hdr_type = hdr_type;
 
 		switch (hdr_type & 0x7f) {		    /* header type */
 		case PCI_HEADER_TYPE_NORMAL:		    /* standard header */
-			if (class >> 8 == PCI_CLASS_BRIDGE_PCI)
+			if (class == PCI_CLASS_BRIDGE_PCI)
 				goto bad;
 			/*
 			 * If the card generates interrupts, read IRQ number
@@ -151,25 +216,19 @@
 			 * read base address registers, again pcibios_fixup() can
 			 * tweak these
 			 */
-			for (reg = 0; reg < 6; reg++) {
-				pcibios_read_config_dword(bus->number, devfn, PCI_BASE_ADDRESS_0 + (reg << 2), &l);
-				dev->base_address[reg] = (l == 0xffffffff) ? 0 : l;
-			}
+			pci_read_bases(dev, 6);
 			pcibios_read_config_dword(bus->number, devfn, PCI_ROM_ADDRESS, &l);
 			dev->rom_address = (l == 0xffffffff) ? 0 : l;
 			break;
 		case PCI_HEADER_TYPE_BRIDGE:		    /* bridge header */
-			if (class >> 8 != PCI_CLASS_BRIDGE_PCI)
+			if (class != PCI_CLASS_BRIDGE_PCI)
 				goto bad;
-			for (reg = 0; reg < 2; reg++) {
-				pcibios_read_config_dword(bus->number, devfn, PCI_BASE_ADDRESS_0 + (reg << 2), &l);
-				dev->base_address[reg] = (l == 0xffffffff) ? 0 : l;
-			}
+			pci_read_bases(dev, 2);
 			pcibios_read_config_dword(bus->number, devfn, PCI_ROM_ADDRESS1, &l);
 			dev->rom_address = (l == 0xffffffff) ? 0 : l;
 			break;
 		case PCI_HEADER_TYPE_CARDBUS:		    /* CardBus bridge header */
-			if (class >> 16 != PCI_BASE_CLASS_BRIDGE)
+			if (class != PCI_CLASS_BRIDGE_CARDBUS)
 				goto bad;
 			for (reg = 0; reg < 2; reg++) {
 				pcibios_read_config_dword(bus->number, devfn, PCI_CB_MEMORY_BASE_0 + (reg << 3), &l);
@@ -201,8 +260,8 @@
 		 * Now insert it into the list of devices held
 		 * by the parent bus.
 		 */
-		dev->sibling = bus->devices;
-		bus->devices = dev;
+		*bus_last = dev;
+		bus_last = &dev->sibling;
 
 #if 0
 		/*
@@ -217,7 +276,7 @@
 		/*
 		 * If it's a bridge, scan the bus behind it.
 		 */
-		if (class >> 8 == PCI_CLASS_BRIDGE_PCI) {
+		if (class == PCI_CLASS_BRIDGE_PCI) {
 			unsigned int buses;
 			unsigned short cr;
 
diff -u --recursive --new-file v2.1.99/linux/drivers/pci/pcisyms.c linux/drivers/pci/pcisyms.c
--- v2.1.99/linux/drivers/pci/pcisyms.c	Thu Apr 23 20:21:33 1998
+++ linux/drivers/pci/pcisyms.c	Sun May  3 11:30:01 1998
@@ -1,5 +1,5 @@
 /*
- *	$Id: pcisyms.c,v 1.4 1998/04/17 16:34:19 mj Exp $
+ *	$Id: pcisyms.c,v 1.7 1998/05/02 19:20:06 mj Exp $
  *
  *	PCI Bus Services -- Exported Symbols
  *
@@ -16,6 +16,12 @@
 EXPORT_SYMBOL(pcibios_write_config_byte);
 EXPORT_SYMBOL(pcibios_write_config_word);
 EXPORT_SYMBOL(pcibios_write_config_dword);
+EXPORT_SYMBOL(pci_read_config_byte);
+EXPORT_SYMBOL(pci_read_config_word);
+EXPORT_SYMBOL(pci_read_config_dword);
+EXPORT_SYMBOL(pci_write_config_byte);
+EXPORT_SYMBOL(pci_write_config_word);
+EXPORT_SYMBOL(pci_write_config_dword);
 EXPORT_SYMBOL(pci_devices);
 EXPORT_SYMBOL(pci_root);
 EXPORT_SYMBOL(pci_find_class);
diff -u --recursive --new-file v2.1.99/linux/drivers/pci/quirks.c linux/drivers/pci/quirks.c
--- v2.1.99/linux/drivers/pci/quirks.c	Sat May  2 14:19:53 1998
+++ linux/drivers/pci/quirks.c	Sun May  3 11:30:01 1998
@@ -1,5 +1,5 @@
 /*
- * $Id: quirks.c,v 1.3 1998/02/06 19:51:42 mj Exp $
+ * $Id: quirks.c,v 1.5 1998/05/02 19:24:14 mj Exp $
  *
  * PCI Chipset-Specific Quirks
  *
@@ -7,8 +7,7 @@
  *
  * This is the right place for all special fixups for on-board
  * devices not depending on system architecture -- for example
- * bus bridges. The only thing implemented in this release is
- * the bridge optimization, but others might appear later.
+ * bus bridges.
  */
 
 #include <linux/config.h>
@@ -88,21 +87,19 @@
 		printk("    %s: ", bridge_optimization[i].type);
 		bmap = &bridge_mapping[pos + i];
 		if (!bmap->addr) {
-			printk("Not supported.");
+			printk("Not supported.\n");
 		} else {
-			pcibios_read_config_byte(dev->bus->number, dev->devfn, bmap->addr, &val);
+			pci_read_config_byte(dev, bmap->addr, &val);
 			if ((val & bmap->mask) == bmap->value)
-				printk("%s.", bridge_optimization[i].on);
+				printk("%s.\n", bridge_optimization[i].on);
 			else {
-				printk("%s.", bridge_optimization[i].off);
-				pcibios_write_config_byte(dev->bus->number, dev->devfn,
-							  bmap->addr,
-							  (val & (0xff - bmap->mask))
-							  + bmap->value);
-				printk("Changed!  Now %s.", bridge_optimization[i].on);
+				printk("%s", bridge_optimization[i].off);
+				pci_write_config_byte(dev,
+						      bmap->addr,
+						      (val & (0xff - bmap->mask)) + bmap->value);
+				printk(" -> %s.\n", bridge_optimization[i].on);
 			}
 		}
-		printk("\n");
 	}
 }
 
@@ -113,27 +110,18 @@
    which can cause problems in combination with the 82441FX/PPro MTRRs */
 __initfunc(static void quirk_passive_release(struct pci_dev *dev, int arg))
 {
-	struct pci_dev *piix3;
+	struct pci_dev *d = NULL;
 	unsigned char dlc;
 
 	/* We have to make sure a particular bit is set in the PIIX3
 	   ISA bridge, so we have to go out and find it. */
-	for (piix3 = pci_devices; ; piix3 = piix3->next) {
-		if (!piix3)
-			return;
-
-		if (piix3->vendor == PCI_VENDOR_ID_INTEL
-		    && piix3->device == PCI_DEVICE_ID_INTEL_82371SB_0)
-			break;
-	}	
-
-	pcibios_read_config_byte(piix3->bus->number, piix3->devfn, 0x82, &dlc);
-
-	if (!(dlc & 1<<1)) {
-		printk("PIIX3: Enabling Passive Release\n");
-		dlc |= 1<<1;
-		pcibios_write_config_byte(piix3->bus->number, piix3->devfn, 
-					  0x82, dlc);
+	while ((d = pci_find_device(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82371SB_0, d))) {
+		pci_read_config_byte(d, 0x82, &dlc);
+		if (!(dlc & 1<<1)) {
+			printk("PIIX3: Enabling Passive Release\n");
+			dlc |= 1<<1;
+			pci_write_config_byte(d, 0x82, dlc);
+		}
 	}
 }
 
@@ -141,7 +129,7 @@
 typedef void (*quirk_handler)(struct pci_dev *, int);
 
 /*
- * Mpping from quirk handler functions to names.
+ * Mapping from quirk handler functions to names.
  */
 
 struct quirk_name {
@@ -185,6 +173,7 @@
 	{ PCI_VENDOR_ID_UMC,	PCI_DEVICE_ID_UMC_UM8891A,	quirk_bridge,	0x01 },
 	{ PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82424,	quirk_bridge,	0x00 },
 	{ PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82434,	quirk_bridge,	0x00 },
+	{ PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82430,	quirk_bridge,	0x00 },
 #endif
 	{ PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82441,	quirk_passive_release,	0x00 },
 };
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/ide-scsi.c linux/drivers/scsi/ide-scsi.c
--- v2.1.99/linux/drivers/scsi/ide-scsi.c	Tue Apr 14 14:29:22 1998
+++ linux/drivers/scsi/ide-scsi.c	Mon May  4 11:37:02 1998
@@ -260,7 +260,7 @@
 	struct request *rq = hwgroup->rq;
 	idescsi_pc_t *pc = (idescsi_pc_t *) rq->buffer;
 	int log = test_bit(IDESCSI_LOG_CMD, &scsi->log);
-	u8 *scsi_buf = pc->scsi_cmd->request_buffer;
+	u8 *scsi_buf;
 
 	if (rq->cmd != IDESCSI_PC_RQ) {
 		ide_end_request (uptodate, hwgroup);
@@ -282,6 +282,7 @@
 			printk ("ide-scsi: %s: suc %lu", drive->name, pc->scsi_cmd->serial_number);
 			if (!test_bit(PC_WRITING, &pc->flags) && pc->actually_transferred && pc->actually_transferred <= 1024 && pc->buffer) {
 				printk(", rst = ");
+				scsi_buf = pc->scsi_cmd->request_buffer;
 				hexdump(scsi_buf, IDE_MIN(16, pc->scsi_cmd->request_bufflen));
 			} else printk("\n");
 		}
@@ -345,7 +346,18 @@
 		if ( temp > pc->request_transfer) {
 			if (temp > pc->buffer_size) {
 				printk (KERN_ERR "ide-scsi: The scsi wants to send us more data than expected - discarding data\n");
-				idescsi_discard_data (drive,bcount);
+				temp = pc->buffer_size - pc->actually_transferred;
+				if (temp) {
+					clear_bit(PC_WRITING, &pc->flags);
+					if (pc->sg)
+						idescsi_input_buffers(drive, pc, temp);
+					else
+						atapi_input_bytes(drive, pc->current_position, temp);
+					printk(KERN_ERR "ide-scsi: transferred %d of %d bytes\n", temp, bcount);
+				}
+				pc->actually_transferred += temp;
+				pc->current_position += temp;
+				idescsi_discard_data (drive,bcount - temp);
 				ide_set_handler(drive, &idescsi_pc_intr, get_timeout(pc));
 				return;
 			}
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/scsi.c linux/drivers/scsi/scsi.c
--- v2.1.99/linux/drivers/scsi/scsi.c	Sat May  2 14:19:53 1998
+++ linux/drivers/scsi/scsi.c	Mon May  4 10:46:11 1998
@@ -1605,6 +1605,7 @@
       if( SCpnt == NULL )
           return;
       
+      spin_lock_irqsave(&io_request_lock, flags);
       atomic_inc(&recursion_depth);
       
       SCnext = SCpnt->bh_next;
@@ -1696,6 +1697,7 @@
       } /* for(; SCpnt...) */
 
       atomic_dec(&recursion_depth);
+      spin_unlock_irqrestore(&io_request_lock, flags);
 
   } /* while(1==1) */
 
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/scsi_error.c linux/drivers/scsi/scsi_error.c
--- v2.1.99/linux/drivers/scsi/scsi_error.c	Tue Mar 17 22:18:14 1998
+++ linux/drivers/scsi/scsi_error.c	Sat May  2 17:58:13 1998
@@ -159,7 +159,7 @@
  *
  * Notes:
  */
-void scsi_times_out (Scsi_Cmnd * SCpnt)
+static void do_scsi_times_out (Scsi_Cmnd * SCpnt)
 {
 
     /* 
@@ -222,6 +222,15 @@
     }
 }
 
+void scsi_times_out (Scsi_Cmnd * SCpnt)
+{
+	unsigned long flags;
+
+	spin_lock_irqsave(&io_request_lock, flags);
+	do_scsi_times_out(SCpnt);
+	spin_unlock_irqrestore(&io_request_lock, flags);
+}
+
 /*
  * Function     scsi_block_when_processing_errors
  *
@@ -264,6 +273,9 @@
 STATIC
 void scsi_eh_times_out (Scsi_Cmnd * SCpnt)
 {
+  unsigned long flags;
+
+  spin_lock_irqsave(&io_request_lock, flags);
   SCpnt->request.rq_status = RQ_SCSI_DONE;
   SCpnt->owner = SCSI_OWNER_ERROR_HANDLER;
   SCpnt->eh_state = SCSI_STATE_TIMEOUT;
@@ -273,7 +285,8 @@
   if (SCpnt->host->eh_action != NULL)
     up(SCpnt->host->eh_action);
   else
-    panic("Missing scsi error handler thread");
+    printk("Missing scsi error handler thread\n");
+  spin_unlock_irqrestore(&io_request_lock, flags);
 }
 
 
@@ -446,6 +459,11 @@
   return SCpnt->eh_state;
 }
 
+/*
+ * This would normally need to get the IO request lock,
+ * but as it doesn't actually touch anything that needs
+ * to be locked we can avoid the lock here..
+ */
 STATIC
 void scsi_sleep_done (struct semaphore * sem)
 {
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/scsi_ioctl.c linux/drivers/scsi/scsi_ioctl.c
--- v2.1.99/linux/drivers/scsi/scsi_ioctl.c	Sat May  2 14:19:53 1998
+++ linux/drivers/scsi/scsi_ioctl.c	Fri May  1 11:19:58 1998
@@ -17,8 +17,13 @@
 #include "hosts.h"
 #include <scsi/scsi_ioctl.h>
 
-#define MAX_RETRIES 5   
-#define MAX_TIMEOUT (9 * HZ)
+#define NORMAL_RETRIES 5   
+#define NORMAL_TIMEOUT (10 * HZ)
+#define FORMAT_UNIT_TIMEOUT (2 * 60 * 60 * HZ)
+#define START_STOP_TIMEOUT (60 * HZ)
+#define MOVE_MEDIUM_TIMEOUT (5 * 60 * HZ)
+#define READ_ELEMENT_STATUS_TIMEOUT (5 * 60 * HZ)
+
 #define MAX_BUF PAGE_SIZE
 
 #define max(a,b) (((a) > (b)) ? (a) : (b))
@@ -61,7 +66,7 @@
 /*
  * 
  * The SCSI_IOCTL_SEND_COMMAND ioctl sends a command out to the SCSI host.
- * The MAX_TIMEOUT and MAX_RETRIES  variables are used.  
+ * The NORMAL_TIMEOUT and NORMAL_RETRIES  variables are used.  
  * 
  * dev is the SCSI device struct ptr, *(int *) arg is the length of the
  * input data, if any, not including the command string & counts, 
@@ -94,7 +99,8 @@
     }
 }   
 
-static int ioctl_internal_command(Scsi_Device *dev, char * cmd)
+static int ioctl_internal_command(Scsi_Device *dev, char * cmd,
+				  int timeout, int retries)
 {
     unsigned long flags;
     int result;
@@ -107,9 +113,7 @@
 	struct semaphore sem = MUTEX_LOCKED;
 	SCpnt->request.sem = &sem;
 	spin_lock_irqsave(&io_request_lock, flags);
-	scsi_do_cmd(SCpnt,  cmd, NULL,  0,
-		    scsi_ioctl_done,  MAX_TIMEOUT,
-		    MAX_RETRIES);
+	scsi_do_cmd(SCpnt,  cmd, NULL,  0, scsi_ioctl_done,  timeout, retries);
 	spin_unlock_irqrestore(&io_request_lock, flags);
 	down(&sem);
         SCpnt->request.sem = NULL;
@@ -250,21 +254,24 @@
     switch (opcode)
       {
       case FORMAT_UNIT:
-	timeout =  2 * 60 * 60 * HZ; /* 2 Hours */
+ 	timeout = FORMAT_UNIT_TIMEOUT;
 	retries = 1;
 	break;
       case START_STOP:
-	timeout =  2 * 60 * HZ;	/* 2 minutes */
-	retries = 1;
+ 	timeout = START_STOP_TIMEOUT;
+ 	retries = NORMAL_RETRIES;
 	break;
       case MOVE_MEDIUM:
+ 	timeout = MOVE_MEDIUM_TIMEOUT;
+ 	retries = NORMAL_RETRIES;
+ 	break;
       case READ_ELEMENT_STATUS:
-	timeout =  5 * 60 * HZ;	/* 5 minutes */
-	retries = 1;
+ 	timeout = READ_ELEMENT_STATUS_TIMEOUT;
+ 	retries = NORMAL_RETRIES;
 	break;
       default:
-	timeout = MAX_TIMEOUT;
-	retries = MAX_RETRIES;
+ 	timeout = NORMAL_TIMEOUT;
+ 	retries = NORMAL_RETRIES;
 	break;
       }
 
@@ -395,7 +402,8 @@
 	scsi_cmd[1] = dev->lun << 5;
 	scsi_cmd[2] = scsi_cmd[3] = scsi_cmd[5] = 0;
 	scsi_cmd[4] = SCSI_REMOVAL_PREVENT;
-	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd);
+	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd,
+				      NORMAL_TIMEOUT, NORMAL_RETRIES);
 	break;
     case SCSI_IOCTL_DOORUNLOCK:
 	if (!dev->removable || !dev->lockable) return 0;
@@ -403,13 +411,31 @@
 	scsi_cmd[1] = dev->lun << 5;
 	scsi_cmd[2] = scsi_cmd[3] = scsi_cmd[5] = 0;
 	scsi_cmd[4] = SCSI_REMOVAL_ALLOW;
-	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd);
+	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd,
+				      NORMAL_TIMEOUT, NORMAL_RETRIES);
     case SCSI_IOCTL_TEST_UNIT_READY:
 	scsi_cmd[0] = TEST_UNIT_READY;
 	scsi_cmd[1] = dev->lun << 5;
 	scsi_cmd[2] = scsi_cmd[3] = scsi_cmd[5] = 0;
 	scsi_cmd[4] = 0;
-	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd);
+	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd,
+				      NORMAL_TIMEOUT, NORMAL_RETRIES);
+	break;
+    case SCSI_IOCTL_START_UNIT:
+	scsi_cmd[0] = START_STOP;
+	scsi_cmd[1] = dev->lun << 5;
+	scsi_cmd[2] = scsi_cmd[3] = scsi_cmd[5] = 0;
+	scsi_cmd[4] = 1;
+	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd,
+				      START_STOP_TIMEOUT, NORMAL_RETRIES);
+	break;
+    case SCSI_IOCTL_STOP_UNIT:
+	scsi_cmd[0] = START_STOP;
+	scsi_cmd[1] = dev->lun << 5;
+	scsi_cmd[2] = scsi_cmd[3] = scsi_cmd[5] = 0;
+	scsi_cmd[4] = 0;
+	return ioctl_internal_command((Scsi_Device *) dev, scsi_cmd,
+				      START_STOP_TIMEOUT, NORMAL_RETRIES);
 	break;
     default :           
 	if (dev->host->hostt->ioctl)
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/scsi_syms.c linux/drivers/scsi/scsi_syms.c
--- v2.1.99/linux/drivers/scsi/scsi_syms.c	Thu Jan  8 20:35:43 1998
+++ linux/drivers/scsi/scsi_syms.c	Sun May  3 11:30:49 1998
@@ -65,6 +65,7 @@
 EXPORT_SYMBOL(print_Scsi_Cmnd);
 EXPORT_SYMBOL(scsi_block_when_processing_errors);
 EXPORT_SYMBOL(scsi_mark_host_reset);
+EXPORT_SYMBOL(scsi_ioctl_send_command);
 #if defined(CONFIG_SCSI_LOGGING) /* { */
 EXPORT_SYMBOL(scsi_logging_level);
 #endif
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/sd.c linux/drivers/scsi/sd.c
--- v2.1.99/linux/drivers/scsi/sd.c	Fri Apr 10 13:03:49 1998
+++ linux/drivers/scsi/sd.c	Fri May  1 11:19:58 1998
@@ -1060,8 +1060,15 @@
     }
 
     inode.i_rdev = full_dev;  /* This is all we really need here */
-    retval = sd_ioctl(&inode, NULL, SCSI_IOCTL_TEST_UNIT_READY, 0);
 
+    /* Using Start/Stop enables differentiation between drive with
+     * no cartridge loaded - NOT READY, drive with changed cartridge -
+     * UNIT ATTENTION, or with same cartridge - GOOD STATUS.
+     * This also handles drives that auto spin down. eg iomega jaz 1GB
+     * as this will spin up the drive.
+     */
+    retval = sd_ioctl(&inode, NULL, SCSI_IOCTL_START_UNIT, 0);
+    
     if(retval){ /* Unable to test, unit probably not ready.  This usually
 		 * means there is no disc in the drive.  Mark as changed,
 		 * and we will figure it out later once the drive is
diff -u --recursive --new-file v2.1.99/linux/drivers/scsi/sr_ioctl.c linux/drivers/scsi/sr_ioctl.c
--- v2.1.99/linux/drivers/scsi/sr_ioctl.c	Thu Feb 12 20:56:10 1998
+++ linux/drivers/scsi/sr_ioctl.c	Sun May  3 17:54:30 1998
@@ -106,8 +106,8 @@
 	    break;
 	case ILLEGAL_REQUEST:
             if (!quiet)
-                printk("sr%d: CDROM (ioctl) reports ILLEGAL REQUEST.\n",
-                       target);
+		printk(KERN_ERR "sr%d: CDROM (ioctl) reports ILLEGAL "
+		       "REQUEST.\n", target);
             if (SCpnt->sense_buffer[12] == 0x20 &&
                 SCpnt->sense_buffer[13] == 0x00) {
                 /* sense: Invalid command operation code */
@@ -121,7 +121,7 @@
 #endif
 	    break;
 	default:
-	    printk("sr%d: CDROM (ioctl) error, command: ", target);
+	    printk(KERN_ERR "sr%d: CDROM (ioctl) error, command: ", target);
 	    print_command(sr_cmd);
 	    print_sense("sr", SCpnt);
             err = -EIO;
diff -u --recursive --new-file v2.1.99/linux/drivers/sound/Makefile linux/drivers/sound/Makefile
--- v2.1.99/linux/drivers/sound/Makefile	Wed Apr  8 19:36:27 1998
+++ linux/drivers/sound/Makefile	Mon May  4 17:39:39 1998
@@ -76,6 +76,9 @@
 
 ifeq ($(CONFIG_GUS),y)
 L_OBJS += gus.o
+  ifeq ($(CONFIG_GUSMAX),y)
+    CONFIG_MSS = y
+  endif
 else
   ifeq ($(CONFIG_GUS),m)
     M_OBJS += gus.o
diff -u --recursive --new-file v2.1.99/linux/drivers/sound/sound_syms.c linux/drivers/sound/sound_syms.c
--- v2.1.99/linux/drivers/sound/sound_syms.c	Wed Apr  8 19:36:27 1998
+++ linux/drivers/sound/sound_syms.c	Mon May  4 11:52:58 1998
@@ -26,6 +26,7 @@
 EXPORT_SYMBOL(note_to_freq);
 EXPORT_SYMBOL(compute_finetune);
 EXPORT_SYMBOL(seq_copy_to_input);
+EXPORT_SYMBOL(seq_input_event);
 EXPORT_SYMBOL(sequencer_init);
 EXPORT_SYMBOL(sequencer_timer);
 
@@ -61,6 +62,7 @@
 EXPORT_SYMBOL(sound_timer_init);
 EXPORT_SYMBOL(sound_timer_interrupt);
 EXPORT_SYMBOL(sound_timer_syncinterval);
+EXPORT_SYMBOL(sound_timer_devs);
 
 /* Locking */
 EXPORT_SYMBOL(sound_locker);
diff -u --recursive --new-file v2.1.99/linux/drivers/sound/sscape.c linux/drivers/sound/sscape.c
--- v2.1.99/linux/drivers/sound/sscape.c	Mon Feb 23 18:12:09 1998
+++ linux/drivers/sound/sscape.c	Mon May  4 11:53:54 1998
@@ -970,7 +970,7 @@
 	if (mss)
 		unload_ss_ms_sound(&config);
 	SOUND_LOCK_END;
-	unload_sscape(&config);
+	unload_sscape(&mpu_config);
 }
 
 #endif
diff -u --recursive --new-file v2.1.99/linux/fs/coda/Makefile linux/fs/coda/Makefile
--- v2.1.99/linux/fs/coda/Makefile	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/Makefile	Mon May  4 17:09:22 1998
@@ -4,7 +4,7 @@
 
 O_TARGET := coda.o
 O_OBJS   := psdev.o cache.o cnode.o inode.o dir.o file.o upcall.o coda_linux.o\
-            symlink.o pioctl.o sysctl.o
+            symlink.o pioctl.o sysctl.o stats.o
 M_OBJS   := $(O_TARGET)
 
 # If you want debugging output, please uncomment the following line
diff -u --recursive --new-file v2.1.99/linux/fs/coda/cache.c linux/fs/coda/cache.c
--- v2.1.99/linux/fs/coda/cache.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/cache.c	Mon May  4 17:09:22 1998
@@ -32,9 +32,6 @@
 static struct coda_cache * coda_cache_find(struct inode *inode);
 
 
-/* Keep various stats */
-struct cfsnc_statistics cfsnc_stat;
-
 /* insert a acl-cache entry in sb list */
 static void coda_ccinsert(struct coda_cache *el, struct super_block *sb)
 {
@@ -295,41 +292,3 @@
 
 
 
-int
-cfsnc_nc_info(char *buffer, char **start, off_t offset, int length, int dummy)
-{
-        int len=0;
-        off_t begin;
-	
-	/* 	cfsnc_gather_stats(); */
-
-	/* this works as long as we are below 1024 characters! */    
-	len += sprintf(buffer,"Coda minicache statistics\n\n");
-	len += sprintf(buffer+len, "cfsnc_hits : %d\n", cfsnc_stat.hits);
-	len += sprintf(buffer+len, "cfsnc_misses : %d\n", cfsnc_stat.misses);
-	len += sprintf(buffer+len, "cfsnc_enters : %d\n", cfsnc_stat.enters);
-	len += sprintf(buffer+len, "cfsnc_dbl_enters : %d\n", cfsnc_stat.dbl_enters);
-	len += sprintf(buffer+len, "cfsnc_long_name_enters : %d\n", cfsnc_stat.long_name_enters);
-	len += sprintf(buffer+len, "cfsnc_long_name_lookups : %d\n", cfsnc_stat.long_name_lookups);
-	len += sprintf(buffer+len, "cfsnc_long_remove : %d\n", cfsnc_stat.long_remove);
-	len += sprintf(buffer+len, "cfsnc_lru_rm : %d\n", cfsnc_stat.lru_rm);
-	len += sprintf(buffer+len, "cfsnc_zapPfids : %d\n", cfsnc_stat.zapPfids);
-	len += sprintf(buffer+len, "cfsnc_zapFids : %d\n", cfsnc_stat.zapFids);
-	len += sprintf(buffer+len, "cfsnc_zapFile : %d\n", cfsnc_stat.zapFile);
-	len += sprintf(buffer+len, "cfsnc_zapUsers : %d\n", cfsnc_stat.zapUsers);
-	len += sprintf(buffer+len, "cfsnc_Flushes : %d\n", cfsnc_stat.Flushes);
-	len += sprintf(buffer+len, "cfsnc_SumLen : %d\n", cfsnc_stat.Sum_bucket_len);
-	len += sprintf(buffer+len, "cfsnc_Sum2Len : %d\n", cfsnc_stat.Sum2_bucket_len);
-	len += sprintf(buffer+len,  "cfsnc_# 0 len : %d\n", cfsnc_stat.Num_zero_len);
-	len += sprintf(buffer+len,  "cfsnc_MaxLen : %d\n", cfsnc_stat.Max_bucket_len);
-	len += sprintf(buffer+len,  "cfsnc_SearchLen : %d\n", cfsnc_stat.Search_len);
-       	begin =  offset;
-       	*start = buffer + begin;
-       	len -= begin;
-	
-        if(len>length)
-                len = length;
-	if (len< 0)
-		len = 0;
-        return len;
-} 
diff -u --recursive --new-file v2.1.99/linux/fs/coda/coda_linux.c linux/fs/coda/coda_linux.c
--- v2.1.99/linux/fs/coda/coda_linux.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/coda_linux.c	Mon May  4 17:09:22 1998
@@ -7,6 +7,7 @@
  * the Coda project. Contact Peter Braam (coda@cs.cmu.edu).
  */
 
+#include <linux/version.h>
 #include <linux/types.h>
 #include <linux/kernel.h>
 #include <linux/sched.h>
diff -u --recursive --new-file v2.1.99/linux/fs/coda/dir.c linux/fs/coda/dir.c
--- v2.1.99/linux/fs/coda/dir.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/dir.c	Mon May  4 17:09:22 1998
@@ -23,6 +23,7 @@
 #include <linux/coda_psdev.h>
 #include <linux/coda_fs_i.h>
 #include <linux/coda_cache.h>
+#include <linux/coda_proc.h>
 
 /* dir inode-ops */
 static int coda_create(struct inode *dir, struct dentry *new, int mode);
@@ -179,6 +180,8 @@
         int error;
  
         ENTRY;
+	coda_vfs_stat.permission++;
+	coda_permission_stat.count++;
 
         if ( mask == 0 ) {
                 EXIT;
@@ -187,6 +190,7 @@
 
 	if ( coda_access_cache == 1 ) {
 		if ( coda_cache_check(inode, mask) ) {
+			coda_permission_stat.hit_count++;
 			return 0; 
 		}
 	}
@@ -221,6 +225,8 @@
 	struct ViceFid newfid;
 	struct coda_vattr attrs;
 
+	coda_vfs_stat.create++;
+
 	CDEBUG(D_INODE, "name: %s, length %d, mode %o\n",name, length, mode);
 
         if (!dir || !S_ISDIR(dir->i_mode)) {
@@ -274,6 +280,8 @@
 	struct ViceFid newfid;
 
 
+	coda_vfs_stat.mkdir++;
+
 	if (!dir || !S_ISDIR(dir->i_mode)) {
 		printk("coda_mkdir: inode is NULL or not a directory\n");
 		return -ENOENT;
@@ -329,6 +337,7 @@
 	int error;
 
         ENTRY;
+	coda_vfs_stat.link++;
 
 	if (coda_isroot(dir_inode) && coda_iscontrol(name, len))
 		return -EPERM;
@@ -373,6 +382,7 @@
         int error=0;
         
         ENTRY;
+	coda_vfs_stat.symlink++;
 
 	if (coda_isroot(dir_inode) && coda_iscontrol(name, len))
 		return -EPERM;
@@ -414,6 +424,7 @@
 	int len = de->d_name.len;
 
 	ENTRY;
+	coda_vfs_stat.unlink++;
 
         dircnp = ITOC(dir);
         CHECK_CNODE(dircnp);
@@ -446,6 +457,8 @@
 	int len = de->d_name.len;
         int error, rehash = 0;
 
+	coda_vfs_stat.rmdir++;
+
 	if (!dir || !S_ISDIR(dir->i_mode)) {
 		printk("coda_rmdir: inode is NULL or not a directory\n");
 		return -ENOENT;
@@ -502,6 +515,8 @@
         struct coda_inode_info *new_cnp, *old_cnp;
         int error, rehash = 0, update = 1;
 ENTRY;
+	coda_vfs_stat.rename++;
+
         old_cnp = ITOC(old_dir);
         CHECK_CNODE(old_cnp);
         new_cnp = ITOC(new_dir);
@@ -565,6 +580,7 @@
 	struct inode *inode=file->f_dentry->d_inode;
 
         ENTRY;
+	coda_vfs_stat.readdir++;
 
         if (!inode || !inode->i_sb || !S_ISDIR(inode->i_mode)) {
                 printk("coda_readdir: inode is NULL or not a directory\n");
@@ -606,6 +622,7 @@
 	unsigned short coda_flags = coda_flags_to_cflags(flags);
 
         ENTRY;
+	coda_vfs_stat.open++;
         
         CDEBUG(D_SPECIAL, "OPEN inode number: %ld, flags %o.\n", 
 	       f->f_dentry->d_inode->i_ino, flags);
@@ -659,6 +676,7 @@
 	unsigned short cflags = coda_flags_to_cflags(flags);
 
         ENTRY;
+	coda_vfs_stat.release++;
 
         cnp =ITOC(i);
         CHECK_CNODE(cnp);
diff -u --recursive --new-file v2.1.99/linux/fs/coda/file.c linux/fs/coda/file.c
--- v2.1.99/linux/fs/coda/file.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/file.c	Mon May  4 17:09:22 1998
@@ -23,6 +23,7 @@
 #include <linux/coda_fs_i.h>
 #include <linux/coda_psdev.h>
 #include <linux/coda_cache.h>
+#include <linux/coda_proc.h>
 
 /* file operations */
 static int coda_readpage(struct file *file, struct page * page);
@@ -83,6 +84,7 @@
         struct coda_inode_info *cii;
 
         ENTRY;
+	coda_vfs_stat.readpage++;
         
         cii = ITOC(coda_inode);
 
@@ -108,6 +110,8 @@
         struct coda_inode_info *cii;
 	int res;
 
+	coda_vfs_stat.file_mmap++;
+
         ENTRY;
 	cii = ITOC(file->f_dentry->d_inode);
 	cii->c_mmcount++;
@@ -126,7 +130,9 @@
         struct file  cont_file;
 	struct dentry cont_dentry;
         int result = 0;
-        ENTRY;
+
+	ENTRY;
+	coda_vfs_stat.file_read++;
 
         cnp = ITOC(coda_inode);
         CHECK_CNODE(cnp);
@@ -167,6 +173,7 @@
         int result = 0;
 
         ENTRY;
+	coda_vfs_stat.file_write++;
 
         cnp = ITOC(coda_inode);
         CHECK_CNODE(cnp);
@@ -205,6 +212,7 @@
 	struct dentry cont_dentry;
         int result = 0;
         ENTRY;
+	coda_vfs_stat.fsync++;
 
 	if (!(S_ISREG(coda_inode->i_mode) || S_ISDIR(coda_inode->i_mode) ||
 	      S_ISLNK(coda_inode->i_mode)))
diff -u --recursive --new-file v2.1.99/linux/fs/coda/psdev.c linux/fs/coda/psdev.c
--- v2.1.99/linux/fs/coda/psdev.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/psdev.c	Mon May  4 17:09:22 1998
@@ -44,7 +44,7 @@
 #include <linux/coda_fs_i.h>
 #include <linux/coda_psdev.h>
 #include <linux/coda_cache.h>
-#include <linux/coda_sysctl.h>
+#include <linux/coda_proc.h>
 
 
 /*
@@ -401,19 +401,106 @@
 
 #ifdef CONFIG_PROC_FS
 
-struct proc_dir_entry proc_coda = {
+struct proc_dir_entry proc_sys_root = {
+        PROC_SYS, 3, "sys",                     /* inode, name */
+        S_IFDIR | S_IRUGO | S_IXUGO, 2, 0, 0,   /* mode, nlink, uid, gid */
+        0, &proc_dir_inode_operations,          /* size, ops */
+        NULL, NULL,                             /* get_info, fill_inode */
+        NULL,                                   /* next */
+        NULL, NULL                              /* parent, subdir */
+};
+
+struct proc_dir_entry proc_fs_coda = {
+        PROC_FS_CODA, 4, "coda",
+        S_IFDIR | S_IRUGO | S_IXUGO, 2, 0, 0,
+        0, &proc_dir_inode_operations,
+	NULL, NULL,
+	NULL,
+	NULL, NULL
+};
+
+struct proc_dir_entry proc_sys_coda = {
         0, 4, "coda",
-        S_IFDIR | S_IRUGO | S_IXUGO | S_IWUSR, 2, 0, 0,
-        0, &proc_net_inode_operations,
+        S_IFDIR | S_IRUGO | S_IXUGO, 2, 0, 0,
+        0, &proc_dir_inode_operations,
+	NULL, NULL,
+	NULL,
+	NULL, NULL
+};
 
+struct proc_dir_entry proc_fs = {
+        PROC_FS, 2, "fs",
+        S_IFDIR | S_IRUGO | S_IXUGO, 2, 0, 0,
+        0, &proc_dir_inode_operations,
+	NULL, NULL,
+	NULL,
+	NULL, NULL
 };
 
+#if 0
 struct proc_dir_entry proc_coda_ncstats =  {
                 0 , 12, "coda-ncstats",
                 S_IFREG | S_IRUGO, 1, 0, 0,
                 0, &proc_net_inode_operations,
                 cfsnc_nc_info
         };
+#endif
+
+struct proc_dir_entry proc_coda_vfs =  {
+                PROC_VFS_STATS , 9, "vfs_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_vfs_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_vfs_control =  {
+                0 , 9, "vfs_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_vfs_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_upcall =  {
+                PROC_UPCALL_STATS , 12, "upcall_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_upcall_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_upcall_control =  {
+                0 , 12, "upcall_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_upcall_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_permission =  {
+                PROC_PERMISSION_STATS , 16, "permission_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_permission_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_permission_control =  {
+                0 , 16, "permission_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_permission_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_cache_inv =  {
+                PROC_CACHE_INV_STATS , 15, "cache_inv_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_cache_inv_stats_get_info
+        };
+
+struct proc_dir_entry proc_coda_cache_inv_control =  {
+                0 , 15, "cache_inv_stats",
+                S_IFREG | S_IRUGO, 1, 0, 0,
+                0, &proc_net_inode_operations,
+                coda_cache_inv_stats_get_info
+        };
 
 #endif
 
@@ -429,9 +516,27 @@
 	memset(coda_super_info, 0, sizeof(coda_super_info));
 	memset(&coda_callstats, 0, sizeof(coda_callstats));
 
+	reset_coda_vfs_stats();
+	reset_coda_upcall_stats();
+	reset_coda_permission_stats();
+	reset_coda_cache_inv_stats();
+
 #ifdef CONFIG_PROC_FS
-	proc_register(&proc_root,&proc_coda);
-	proc_register(&proc_coda, &proc_coda_ncstats);
+	proc_register(&proc_root,&proc_fs);
+	proc_register(&proc_fs,&proc_fs_coda);
+	proc_register(&proc_fs_coda,&proc_coda_vfs);
+	proc_register(&proc_fs_coda,&proc_coda_upcall);
+	proc_register(&proc_fs_coda,&proc_coda_permission);
+	proc_register(&proc_fs_coda,&proc_coda_cache_inv);
+#if 0
+	proc_register(&proc_fs_coda, &proc_coda_ncstats);
+#endif
+	proc_register(&proc_sys_root,&proc_sys_coda);
+	proc_register(&proc_sys_coda,&proc_coda_vfs_control);
+	proc_register(&proc_sys_coda,&proc_coda_upcall_control);
+	proc_register(&proc_sys_coda,&proc_coda_permission_control);
+	proc_register(&proc_sys_coda,&proc_coda_cache_inv_control);
+
 	coda_sysctl_init();
 #endif 
 	return 0;
@@ -476,8 +581,22 @@
 
 #if CONFIG_PROC_FS
         coda_sysctl_clean();
-        proc_unregister(&proc_coda, proc_coda_ncstats.low_ino);
-	proc_unregister(&proc_root, proc_coda.low_ino);
+
+        proc_unregister(&proc_sys_coda, proc_coda_cache_inv_control.low_ino);
+        proc_unregister(&proc_sys_coda, proc_coda_permission_control.low_ino);
+        proc_unregister(&proc_sys_coda, proc_coda_upcall_control.low_ino);
+	proc_unregister(&proc_sys_coda,proc_coda_vfs_control.low_ino);
+	proc_unregister(&proc_sys_root, proc_sys_coda.low_ino);
+
+#if 0
+	proc_unregister(&proc_fs_coda, proc_coda_ncstats.low_ino);
+#endif
+        proc_unregister(&proc_fs_coda, proc_coda_cache_inv.low_ino);
+        proc_unregister(&proc_fs_coda, proc_coda_permission.low_ino);
+        proc_unregister(&proc_fs_coda, proc_coda_upcall.low_ino);
+        proc_unregister(&proc_fs_coda, proc_coda_vfs.low_ino);
+	proc_unregister(&proc_fs, proc_fs_coda.low_ino);
+	proc_unregister(&proc_root, proc_fs.low_ino);
 #endif 
 }
 
diff -u --recursive --new-file v2.1.99/linux/fs/coda/stats.c linux/fs/coda/stats.c
--- v2.1.99/linux/fs/coda/stats.c	Wed Dec 31 16:00:00 1969
+++ linux/fs/coda/stats.c	Tue May  5 10:52:17 1998
@@ -0,0 +1,416 @@
+/*
+ * stats.c
+ * 
+ * CODA operation statistics
+ *
+ * (c) March, 1998 Zhanyong Wan <zhanyong.wan@yale.edu>
+ *
+ */
+
+#include <linux/sched.h>
+#include <linux/mm.h>
+#include <linux/sysctl.h>
+#include <linux/swapctl.h>
+#include <linux/proc_fs.h>
+#include <linux/malloc.h>
+#include <linux/stat.h>
+#include <linux/ctype.h>
+#include <asm/bitops.h>
+#include <asm/segment.h>
+#include <asm/uaccess.h>
+#include <linux/utsname.h>
+
+#include <linux/coda.h>
+#include <linux/coda_linux.h>
+#include <linux/coda_fs_i.h>
+#include <linux/coda_psdev.h>
+#include <linux/coda_cache.h>
+#include <linux/coda_proc.h>
+
+struct coda_vfs_stats		coda_vfs_stat;
+struct coda_permission_stats	coda_permission_stat;
+struct coda_cache_inv_stats	coda_cache_inv_stat;
+struct coda_upcall_stats_entry coda_upcall_stat[CFS_NCALLS];
+
+/* keep this in sync with coda.h! */
+char *coda_upcall_names[] = {
+	"totals      ",   /*  0 */
+	"noop        ",   /*  1 */
+	"root        ",   /*  2 */
+	"sync        ",   /*  3 */
+	"open        ",   /*  4 */
+	"close       ",   /*  5 */
+	"ioctl       ",   /*  6 */
+	"getattr     ",   /*  7 */
+	"setattr     ",   /*  8 */
+	"access      ",   /*  9 */
+	"lookup      ",   /* 10 */
+	"create      ",   /* 11 */
+	"remove      ",   /* 12 */
+	"link        ",   /* 13 */
+	"rename      ",   /* 14 */
+	"mkdir       ",   /* 15 */
+	"rmdir       ",   /* 16 */
+	"readdir     ",   /* 17 */
+	"symlink     ",   /* 18 */
+	"readlink    ",   /* 19 */
+	"fsync       ",   /* 20 */
+	"inactive    ",   /* 21 */
+	"vget        ",   /* 22 */
+	"signal      ",   /* 23 */
+	"replace     ",   /* 24 */
+	"flush       ",   /* 25 */
+	"purgeuser   ",   /* 26 */
+	"zapfile     ",   /* 27 */
+	"zapdir      ",   /* 28 */
+	"zapvnode    ",   /* 28 */
+	"purgefid    ",   /* 30 */
+	"open_by_path"    /* 31 */
+};
+
+
+
+
+void reset_coda_vfs_stats( void )
+{
+	memset( &coda_vfs_stat, 0, sizeof( coda_vfs_stat ) );
+}
+
+#if 0
+static void reset_upcall_entry( struct coda_upcall_stats_entry * pentry )
+{
+	pentry->count = 0;
+	pentry->time_sum = pentry->time_squared_sum = 0;
+}
+#endif
+
+void reset_coda_upcall_stats( void )
+{
+	memset( &coda_upcall_stat, 0, sizeof( coda_upcall_stat ) );
+}
+
+void reset_coda_permission_stats( void )
+{
+	memset( &coda_permission_stat, 0, sizeof( coda_permission_stat ) );
+}
+
+void reset_coda_cache_inv_stats( void )
+{
+	memset( &coda_cache_inv_stat, 0, sizeof( coda_cache_inv_stat ) );
+}
+
+
+void do_time_stats( struct coda_upcall_stats_entry * pentry, 
+		    unsigned long runtime )
+{
+	
+	unsigned long time = runtime * 1000 /HZ;	/* time in ms */
+	CDEBUG(D_SPECIAL, "time: %ld\n", time);
+
+	if ( pentry->count == 0 ) {
+		pentry->time_sum = pentry->time_squared_sum = 0;
+	}
+	
+	pentry->count++;
+	pentry->time_sum += time;
+	pentry->time_squared_sum += time*time;
+}
+
+
+
+void coda_upcall_stats(int opcode, long unsigned runtime) 
+{
+	struct coda_upcall_stats_entry * pentry;
+	
+	if ( opcode < 0 || opcode > CFS_NCALLS - 1) {
+		printk("Nasty opcode %d passed to coda_upcall_stats\n",
+		       opcode);
+		return;
+	}
+		
+	pentry = &coda_upcall_stat[opcode];
+	do_time_stats(pentry, runtime);
+
+        /* fill in the totals */
+	pentry = &coda_upcall_stat[0];
+	do_time_stats(pentry, runtime);
+
+}
+
+unsigned long get_time_average( const struct coda_upcall_stats_entry * pentry )
+{
+	return ( pentry->count == 0 ) ? 0 : pentry->time_sum / pentry->count;
+}
+
+static inline unsigned long absolute( unsigned long x )
+{
+	return x >= 0 ? x : -x;
+}
+
+static unsigned long sqr_root( unsigned long x )
+{
+	unsigned long y = x, r;
+	int n_bit = 0;
+  
+	if ( x == 0 )
+		return 0;
+	if ( x < 0)
+		x = -x;
+
+	while ( y ) {
+		y >>= 1;
+		n_bit++;
+	}
+  
+	r = 1 << (n_bit/2);
+  
+	while ( 1 ) {
+		r = (r + x/r)/2;
+		if ( r*r <= x && x < (r+1)*(r+1) )
+			break;
+	}
+  
+	return r;
+}
+
+unsigned long get_time_std_deviation( const struct coda_upcall_stats_entry * pentry )
+{
+	unsigned long time_avg;
+  
+	if ( pentry->count <= 1 )
+		return 0;
+  
+	time_avg = get_time_average( pentry );
+	return 
+	        sqr_root( (pentry->time_squared_sum / pentry->count) - 
+			    time_avg * time_avg );
+}
+
+int do_reset_coda_vfs_stats( ctl_table * table, int write, struct file * filp,
+			     void * buffer, size_t * lenp )
+{
+	if ( write ) {
+		reset_coda_vfs_stats();
+	}
+  
+	*lenp = 0;
+	return 0;
+}
+
+int do_reset_coda_upcall_stats( ctl_table * table, int write, 
+				struct file * filp, void * buffer, 
+				size_t * lenp )
+{
+	if ( write ) {
+		reset_coda_upcall_stats();
+	}
+  
+	*lenp = 0;
+	return 0;
+}
+
+int do_reset_coda_permission_stats( ctl_table * table, int write, 
+				    struct file * filp, void * buffer, 
+				    size_t * lenp )
+{
+	if ( write ) {
+		reset_coda_permission_stats();
+	}
+  
+	*lenp = 0;
+	return 0;
+}
+
+int do_reset_coda_cache_inv_stats( ctl_table * table, int write, 
+				   struct file * filp, void * buffer, 
+				   size_t * lenp )
+{
+	if ( write ) {
+		reset_coda_cache_inv_stats();
+	}
+  
+	*lenp = 0;
+	return 0;
+}
+
+int coda_vfs_stats_get_info( char * buffer, char ** start, off_t offset,
+			     int length, int dummy )
+{
+	int len=0;
+	off_t begin;
+	struct coda_vfs_stats * ps = & coda_vfs_stat;
+  
+  /* this works as long as we are below 1024 characters! */
+	len += sprintf( buffer,
+			"Coda VFS statistics\n"
+			"===================\n\n"
+			"File Operations:\n"
+			"\tfile_read\t%9d\n"
+			"\tfile_write\t%9d\n"
+			"\tfile_mmap\t%9d\n"
+			"\topen\t\t%9d\n"
+			"\trelase\t\t%9d\n"
+			"\tfsync\t\t%9d\n\n"
+			"Dir Operations:\n"
+			"\treaddir\t\t%9d\n\n"
+			"Inode Operations\n"
+			"\tcreate\t\t%9d\n"
+			"\tlookup\t\t%9d\n"
+			"\tlink\t\t%9d\n"
+			"\tunlink\t\t%9d\n"
+			"\tsymlink\t\t%9d\n"
+			"\tmkdir\t\t%9d\n"
+			"\trmdir\t\t%9d\n"
+			"\trename\t\t%9d\n"
+			"\tpermission\t%9d\n"
+			"\treadpage\t%9d\n",
+
+			/* file operations */
+			ps->file_read,
+			ps->file_write,
+			ps->file_mmap,
+			ps->open,
+			ps->release,
+			ps->fsync,
+
+			/* dir operations */
+			ps->readdir,
+		  
+			/* inode operations */
+			ps->create,
+			ps->lookup,
+			ps->link,
+			ps->unlink,
+			ps->symlink,
+			ps->mkdir,
+			ps->rmdir,
+			ps->rename,
+			ps->permission,
+			ps->readpage );
+  
+	begin = offset;
+	*start = buffer + begin;
+	len -= begin;
+
+	if ( len > length )
+		len = length;
+	if ( len < 0 )
+		len = 0;
+
+	return len;
+}
+
+int coda_upcall_stats_get_info( char * buffer, char ** start, off_t offset,
+				int length, int dummy )
+{
+	int len=0;
+	int i;
+	off_t begin;
+	off_t pos = 0;
+	char tmpbuf[80];
+	int tmplen = 0;
+
+	ENTRY;
+	/* this works as long as we are below 1024 characters! */
+	if ( offset < 80 ) 
+		len += sprintf( buffer,"%-79s\n",	"Coda upcall statistics");
+	if ( offset < 160) 
+		len += sprintf( buffer + len,"%-79s\n",	"======================");
+	if ( offset < 240) 
+		len += sprintf( buffer + len,"%-79s\n",	"upcall\t\t    count\tavg time(ms)\tstd deviation(ms)");
+	if ( offset < 320) 
+		len += sprintf( buffer + len,"%-79s\n",	"------\t\t    -----\t------------\t-----------------");
+	pos = 320; 
+	for ( i = 0 ; i < CFS_NCALLS ; i++ ) {
+		tmplen += sprintf(tmpbuf,"%s\t%9d\t%10ld\t%10ld", 
+				  coda_upcall_names[i],
+				  coda_upcall_stat[i].count, 
+				  get_time_average(&coda_upcall_stat[i]),
+				  coda_upcall_stat[i].time_squared_sum);
+		pos += 80;
+		if ( pos < offset ) 
+			continue; 
+		len += sprintf(buffer + len, "%-79s\n", tmpbuf);
+		if ( len >= length ) 
+			break; 
+	}
+  
+	begin = len- (pos - offset);
+	*start = buffer + begin;
+	len -= begin;
+
+	if ( len > length )
+		len = length;
+	if ( len < 0 )
+		len = 0;
+	EXIT;
+	return len;
+}
+
+int coda_permission_stats_get_info( char * buffer, char ** start, off_t offset,
+				    int length, int dummy )
+{
+	int len=0;
+	off_t begin;
+	struct coda_permission_stats * ps = & coda_permission_stat;
+  
+	/* this works as long as we are below 1024 characters! */
+	len += sprintf( buffer,
+			"Coda permission statistics\n"
+			"==========================\n\n"
+			"count\t\t%9d\n"
+			"hit count\t%9d\n",
+
+			ps->count,
+			ps->hit_count );
+  
+	begin = offset;
+	*start = buffer + begin;
+	len -= begin;
+
+	if ( len > length )
+		len = length;
+	if ( len < 0 )
+		len = 0;
+
+	return len;
+}
+
+int coda_cache_inv_stats_get_info( char * buffer, char ** start, off_t offset,
+				   int length, int dummy )
+{
+	int len=0;
+	off_t begin;
+	struct coda_cache_inv_stats * ps = & coda_cache_inv_stat;
+  
+	/* this works as long as we are below 1024 characters! */
+	len += sprintf( buffer,
+			"Coda cache invalidation statistics\n"
+			"==================================\n\n"
+			"flush\t\t%9d\n"
+			"purge user\t%9d\n"
+			"zap_dir\t\t%9d\n"
+			"zap_file\t%9d\n"
+			"zap_vnode\t%9d\n"
+			"purge_fid\t%9d\n"
+			"replace\t\t%9d\n",
+			ps->flush,
+			ps->purge_user,
+			ps->zap_dir,
+			ps->zap_file,
+			ps->zap_vnode,
+			ps->purge_fid,
+			ps->replace );
+  
+	begin = offset;
+	*start = buffer + begin;
+	len -= begin;
+
+	if ( len > length )
+		len = length;
+	if ( len < 0 )
+		len = 0;
+
+	return len;
+}
+
diff -u --recursive --new-file v2.1.99/linux/fs/coda/symlink.c linux/fs/coda/symlink.c
--- v2.1.99/linux/fs/coda/symlink.c	Tue Mar 10 10:03:33 1998
+++ linux/fs/coda/symlink.c	Mon May  4 17:09:22 1998
@@ -23,6 +23,7 @@
 #include <linux/coda_psdev.h>
 #include <linux/coda_fs_i.h>
 #include <linux/coda_cache.h>
+#include <linux/coda_proc.h>
 
 static int coda_readlink(struct dentry *de, char *buffer, int length);
 static struct dentry *coda_follow_link(struct dentry *, struct dentry *);
@@ -60,7 +61,7 @@
         ENTRY;
 
         cp = ITOC(inode);
-        CHECK_CNODE(cp);
+	coda_vfs_stat.readlink++;
 
         /* the maximum length we receive is len */
         if ( length > CFS_MAXPATHLEN ) 
@@ -93,11 +94,11 @@
 	unsigned int len;
 	char mem[CFS_MAXPATHLEN];
 	char *path;
-ENTRY;
+	ENTRY;
 	CDEBUG(D_INODE, "(%x/%ld)\n", inode->i_dev, inode->i_ino);
 	
         cnp = ITOC(inode);
-        CHECK_CNODE(cnp);
+	coda_vfs_stat.follow_link++;
 
 	len = CFS_MAXPATHLEN;
 	error = venus_readlink(inode->i_sb, &(cnp->c_fid), mem, &len);
diff -u --recursive --new-file v2.1.99/linux/fs/coda/sysctl.c linux/fs/coda/sysctl.c
--- v2.1.99/linux/fs/coda/sysctl.c	Tue Mar 10 10:03:33 1998
+++ linux/fs/coda/sysctl.c	Mon May  4 17:09:22 1998
@@ -26,7 +26,7 @@
 #include <linux/coda_fs_i.h>
 #include <linux/coda_psdev.h>
 #include <linux/coda_cache.h>
-#include <linux/coda_sysctl.h>
+#include <linux/coda_proc.h>
 extern int coda_debug;
 /* extern int cfsnc_use; */
 extern int coda_print_entry;
@@ -47,6 +47,10 @@
 #define CODA_TIMEOUT    3       /* timeout on upcalls to become intrble */
 #define CODA_MC         4       /* use/do not use the access cache */
 #define CODA_HARD       5       /* mount type "hard" or "soft" */
+#define CODA_VFS 	 6       /* vfs statistics */
+#define CODA_UPCALL 	 7       /* upcall statistics */
+#define CODA_PERMISSION	 8       /* permission statistics */
+#define CODA_CACHE_INV 	 9       /* cache invalidation statistics */
 
 
 
@@ -56,6 +60,10 @@
  	{CODA_MC, "accesscache", &coda_access_cache, sizeof(int), 0644, NULL, &coda_dointvec}, 
  	{CODA_TIMEOUT, "timeout", &coda_timeout, sizeof(int), 0644, NULL, &coda_dointvec},
  	{CODA_HARD, "hard", &coda_hard, sizeof(int), 0644, NULL, &coda_dointvec},
+ 	{CODA_VFS, "vfs_stats", NULL, 0, 0644, NULL, &do_reset_coda_vfs_stats},
+ 	{CODA_UPCALL, "upcall_stats", NULL, 0, 0644, NULL, &do_reset_coda_upcall_stats},
+ 	{CODA_PERMISSION, "permission_stats", NULL, 0, 0644, NULL, &do_reset_coda_permission_stats},
+ 	{CODA_CACHE_INV, "cache_inv_stats", NULL, 0, 0644, NULL, &do_reset_coda_cache_inv_stats},
 	{ 0 }
 };
 
diff -u --recursive --new-file v2.1.99/linux/fs/coda/upcall.c linux/fs/coda/upcall.c
--- v2.1.99/linux/fs/coda/upcall.c	Tue Mar 17 22:18:15 1998
+++ linux/fs/coda/upcall.c	Mon May  4 17:09:22 1998
@@ -37,6 +37,11 @@
 #include <linux/coda_psdev.h>
 #include <linux/coda_fs_i.h>
 #include <linux/coda_cache.h>
+#include <linux/coda_proc.h> 
+
+
+static int  coda_upcall(struct coda_sb_info *mntinfo, int inSize, int *outSize, 
+		       union inputArgs *buffer);
 
 #define UPARG(op)\
 do {\
@@ -68,10 +73,11 @@
         union inputArgs *inp;
         union outputArgs *outp;
         int insize, outsize, error;
-ENTRY;
+	ENTRY;
 
         insize = SIZE(root);
         UPARG(CFS_ROOT);
+
 	error = coda_upcall(coda_sbp(sb), insize, &outsize, inp);
 	
 	if (error) {
@@ -92,7 +98,7 @@
 {
         union inputArgs *inp;
         union outputArgs *outp;
-        int insize, outsize, error;
+	        int insize, outsize, error;
 ENTRY;
         insize = SIZE(getattr); 
 	UPARG(CFS_GETATTR);
@@ -458,8 +464,8 @@
 int venus_fsync(struct super_block *sb, struct ViceFid *fid)
 {
         union inputArgs *inp;
-        union outputArgs *outp;
-        int insize, outsize, error;
+        union outputArgs *outp; 
+	int insize, outsize, error;
 	
 	insize=SIZE(fsync);
 	UPARG(CFS_FSYNC);
@@ -476,8 +482,8 @@
 int venus_access(struct super_block *sb, struct ViceFid *fid, int mask)
 {
         union inputArgs *inp;
-        union outputArgs *outp;
-        int insize, outsize, error;
+        union outputArgs *outp; 
+	int insize, outsize, error;
 
 	insize = SIZE(access);
 	UPARG(CFS_ACCESS);
@@ -497,8 +503,8 @@
 		 unsigned int cmd, struct PioctlData *data)
 {
         union inputArgs *inp;
-        union outputArgs *outp;
-        int insize, outsize, error;
+        union outputArgs *outp;  
+	int insize, outsize, error;
 	int iocsize;
 
 	insize = VC_MAXMSGSIZE;
@@ -583,11 +589,13 @@
  * reply and return Venus' error, also POSITIVE. 
  * 
  */
-static inline void coda_waitfor_upcall(struct vmsg *vmp)
+static inline unsigned long coda_waitfor_upcall(struct vmsg *vmp)
 {
 	struct wait_queue	wait = { current, NULL };
+	unsigned long posttime;
 
 	vmp->vm_posttime = jiffies;
+	posttime = jiffies;
 
 	add_wait_queue(&vmp->vm_sleep, &wait);
 	for (;;) {
@@ -616,13 +624,17 @@
 	remove_wait_queue(&vmp->vm_sleep, &wait);
 	current->state = TASK_RUNNING;
 
-	return;
+	CDEBUG(D_SPECIAL, "posttime: %ld, returned: %ld\n", posttime, jiffies-posttime);
+	return 	(jiffies - posttime);
+
 }
 
 
-int coda_upcall(struct coda_sb_info *sbi, int inSize, int *outSize, 
+static int coda_upcall(struct coda_sb_info *sbi, 
+		int inSize, int *outSize, 
 		union inputArgs *buffer) 
 {
+	unsigned long runtime; 
 	struct vcomm *vcommp;
 	union outputArgs *out;
 	struct vmsg *vmp;
@@ -635,7 +647,6 @@
 	}
 	vcommp = sbi->sbi_vcomm;
 
-	clstats(((union inputArgs *)buffer)->ih.opcode);
 
 	if (!vcomm_open(vcommp))
                 return(ENODEV);
@@ -670,7 +681,8 @@
 	 * ENODEV.  */
 
 	/* Go to sleep.  Wake up on signals only after the timeout. */
-	coda_waitfor_upcall(vmp);
+	runtime = coda_waitfor_upcall(vmp);
+	coda_upcall_stats(((union inputArgs *)buffer)->ih.opcode, runtime);
 
 	CDEBUG(D_TIMING, "opc: %d time: %ld uniq: %d size: %d\n",
 	       vmp->vm_opcode, jiffies - vmp->vm_posttime, 
diff -u --recursive --new-file v2.1.99/linux/fs/dcache.c linux/fs/dcache.c
--- v2.1.99/linux/fs/dcache.c	Sat May  2 14:19:53 1998
+++ linux/fs/dcache.c	Sat May  2 14:07:52 1998
@@ -430,12 +430,17 @@
  * more memory, but aren't really sure how much. So we
  * carefully try to free a _bit_ of our dcache, but not
  * too much.
+ *
+ * Priority:
+ *   0 - very urgent: schrink everything
+ *  ...
+ *   6 - base-level: try to shrink a bit.
  */
-void shrink_dcache_memory(void)
+void shrink_dcache_memory(int priority, unsigned int gfp_mask)
 {
 	int count = select_dcache(32, 8);
 	if (count)
-		prune_dcache(count);
+		prune_dcache((count << 6) >> priority);
 }
 
 #define NAME_ALLOC_LEN(len)	((len+16) & ~15)
diff -u --recursive --new-file v2.1.99/linux/fs/namei.c linux/fs/namei.c
--- v2.1.99/linux/fs/namei.c	Sat May  2 14:19:53 1998
+++ linux/fs/namei.c	Fri May  1 11:21:54 1998
@@ -43,17 +43,24 @@
  *
  * The new code replaces the old recursive symlink resolution with
  * an iterative one (in case of non-nested symlink chains).  It does
- * this by looking up the symlink name from the particular filesystem,
- * and then follows this name as if it were a user-supplied one.  This
- * is done solely in the VFS level, such that <fs>_follow_link() is not
- * used any more and could be removed in future.  As a side effect,
- * dir_namei(), _namei() and follow_link() are now replaced with a single
- * function lookup_dentry() that can handle all the special cases of the former
- * code.
+ * this with calls to <fs>_follow_link().
+ * As a side effect, dir_namei(), _namei() and follow_link() are now 
+ * replaced with a single function lookup_dentry() that can handle all 
+ * the special cases of the former code.
  *
  * With the new dcache, the pathname is stored at each inode, at least as
  * long as the refcount of the inode is positive.  As a side effect, the
  * size of the dcache depends on the inode cache and thus is dynamic.
+ *
+ * [29-Apr-1998 C. Scott Ananian] Updated above description of symlink
+ * resolution to correspond with current state of the code.
+ *
+ * Note that the symlink resolution is not *completely* iterative.
+ * There is still a significant amount of tail- and mid- recursion in
+ * the algorithm.  Also, note that <fs>_readlink() is not used in
+ * lookup_dentry(): lookup_dentry() on the result of <fs>_readlink()
+ * may return different results than <fs>_follow_link().  Many virtual
+ * filesystems (including /proc) exhibit this behavior.
  */
 
 /* [24-Feb-97 T. Schoebel-Theuer] Side effects caused by new implementation:
diff -u --recursive --new-file v2.1.99/linux/fs/pipe.c linux/fs/pipe.c
--- v2.1.99/linux/fs/pipe.c	Thu Mar 26 15:57:05 1998
+++ linux/fs/pipe.c	Mon May  4 18:02:09 1998
@@ -54,7 +54,7 @@
 		}
 	} else while (PIPE_EMPTY(*inode) || PIPE_LOCK(*inode)) {
 		if (PIPE_EMPTY(*inode)) {
-			if (!PIPE_WRITERS(*inode))
+			if (!PIPE_WRITERS(*inode) || !count)
 				return 0;
 		}
 		if (signal_pending(current))
diff -u --recursive --new-file v2.1.99/linux/include/asm-alpha/mmu_context.h linux/include/asm-alpha/mmu_context.h
--- v2.1.99/linux/include/asm-alpha/mmu_context.h	Wed Apr  1 20:11:53 1998
+++ linux/include/asm-alpha/mmu_context.h	Mon May  4 12:06:08 1998
@@ -109,7 +109,11 @@
 #endif
 }
 
-#define init_new_context(mm)	do { } while(0)
+extern inline void init_new_context(struct mm_struct *mm)
+{
+	mm->context = 0;
+}
+
 #define destroy_context(mm)	do { } while(0)
 
 #endif
diff -u --recursive --new-file v2.1.99/linux/include/linux/coda_proc.h linux/include/linux/coda_proc.h
--- v2.1.99/linux/include/linux/coda_proc.h	Wed Dec 31 16:00:00 1969
+++ linux/include/linux/coda_proc.h	Mon May  4 17:09:22 1998
@@ -0,0 +1,144 @@
+/*
+ * coda_statis.h
+ * 
+ * CODA operation statistics
+ *
+ * (c) March, 1998
+ * by Michihiro Kuramochi, Zhenyu Xia and Zhanyong Wan
+ * zhanyong.wan@yale.edu
+ *
+ */
+
+#ifndef _CODA_PROC_H
+#define _CODA_PROC_H
+
+void coda_sysctl_init(void);
+void coda_sysctl_clean(void);
+void coda_upcall_stats(int opcode, unsigned long jiffies);
+
+#include <linux/sysctl.h>
+#include <linux/coda_fs_i.h>
+#include <linux/coda.h>
+
+/* these four files are presented to show the result of the statistics:
+ *
+ *	/proc/fs/coda/vfs_stats
+ *		      upcall_stats
+ *		      permission_stats
+ *		      cache_inv_stats
+ *
+ * these four files are presented to reset the statistics to 0:
+ *
+ *	/proc/sys/coda/vfs_stats
+ *		       upcall_stats
+ *		       permission_stats
+ *		       cache_inv_stats
+ */
+
+/* VFS operation statistics */
+struct coda_vfs_stats 
+{
+	/* file operations */
+	int file_read;
+	int file_write;
+	int file_mmap;
+	int open;
+	int release;
+	int fsync;
+
+	/* dir operations */
+	int readdir;
+  
+	/* inode operations */
+	int create;
+	int lookup;
+	int link;
+	int unlink;
+	int symlink;
+	int mkdir;
+	int rmdir;
+	int rename;
+	int permission;
+	int readpage;
+
+	/* symlink operatoins*/
+	int follow_link;
+	int readlink;
+};
+
+struct coda_upcall_stats_entry 
+{
+  int count;
+  unsigned long time_sum;
+  unsigned long time_squared_sum;
+};
+
+
+
+/* cache hits for permissions statistics */
+struct coda_permission_stats 
+{
+	int count;
+	int hit_count;
+};
+
+/* cache invalidation statistics */
+struct coda_cache_inv_stats
+{
+	int flush;
+	int purge_user;
+	int zap_dir;
+	int zap_file;
+	int zap_vnode;
+	int purge_fid;
+	int replace;
+};
+
+/* these global variables hold the actual statistics data */
+extern struct coda_vfs_stats		coda_vfs_stat;
+extern struct coda_permission_stats	coda_permission_stat;
+extern struct coda_cache_inv_stats	coda_cache_inv_stat;
+
+/* reset statistics to 0 */
+void reset_coda_vfs_stats( void );
+void reset_coda_upcall_stats( void );
+void reset_coda_permission_stats( void );
+void reset_coda_cache_inv_stats( void );
+
+/* some utitlities to make it easier for you to do statistics for time */
+void do_time_stats( struct coda_upcall_stats_entry * pentry, 
+		    unsigned long jiffy );
+/*
+double get_time_average( const struct coda_upcall_stats_entry * pentry );
+double get_time_std_deviation( const struct coda_upcall_stats_entry * pentry );
+*/
+unsigned long get_time_average( const struct coda_upcall_stats_entry * pentry );
+unsigned long get_time_std_deviation( const struct coda_upcall_stats_entry * pentry );
+
+/* like coda_dointvec, these functions are to be registered in the ctl_table
+ * data structure for /proc/sys/... files 
+ */
+int do_reset_coda_vfs_stats( ctl_table * table, int write, struct file * filp,
+			     void * buffer, size_t * lenp );
+int do_reset_coda_upcall_stats( ctl_table * table, int write, 
+				struct file * filp, void * buffer, 
+				size_t * lenp );
+int do_reset_coda_permission_stats( ctl_table * table, int write, 
+				    struct file * filp, void * buffer, 
+				    size_t * lenp );
+int do_reset_coda_cache_inv_stats( ctl_table * table, int write, 
+				   struct file * filp, void * buffer, 
+				   size_t * lenp );
+
+/* these functions are called to form the content of /proc/fs/coda/... files */
+int coda_vfs_stats_get_info( char * buffer, char ** start, off_t offset,
+			     int length, int dummy );
+int coda_upcall_stats_get_info( char * buffer, char ** start, off_t offset,
+				int length, int dummy );
+int coda_permission_stats_get_info( char * buffer, char ** start, off_t offset,
+				    int length, int dummy );
+int coda_cache_inv_stats_get_info( char * buffer, char ** start, off_t offset,
+				   int length, int dummy );
+
+
+#endif /* _CODA_PROC_H */
diff -u --recursive --new-file v2.1.99/linux/include/linux/coda_psdev.h linux/include/linux/coda_psdev.h
--- v2.1.99/linux/include/linux/coda_psdev.h	Mon Feb 23 18:12:11 1998
+++ linux/include/linux/coda_psdev.h	Mon May  4 17:09:22 1998
@@ -94,8 +94,6 @@
 int venus_pioctl(struct super_block *sb, struct ViceFid *fid,
 		 unsigned int cmd, struct PioctlData *data);
 int coda_downcall(int opcode, union outputArgs *out, struct super_block *sb);
-int coda_upcall(struct coda_sb_info *mntinfo, int inSize, 
-		int *outSize, union inputArgs *buffer);
 int venus_fsync(struct super_block *sb, struct ViceFid *fid);
 
 
diff -u --recursive --new-file v2.1.99/linux/include/linux/coda_sysctl.h linux/include/linux/coda_sysctl.h
--- v2.1.99/linux/include/linux/coda_sysctl.h	Sun Dec  7 11:51:01 1997
+++ linux/include/linux/coda_sysctl.h	Wed Dec 31 16:00:00 1969
@@ -1,10 +0,0 @@
-/*
- * Sysctl operations for Coda.
- * Original version: (C) 1996 Peter Braam 
- * Rewritten for Linux 2.1: (C) 1997 Carnegie Mellon University
- *
- * Carnegie Mellon encourages users of this code to contribute improvements
- * to the Coda project. Contact Peter Braam <coda@cs.cmu.edu>.
- */
-void coda_sysctl_init(void);
-void coda_sysctl_clean(void);
diff -u --recursive --new-file v2.1.99/linux/include/linux/dcache.h linux/include/linux/dcache.h
--- v2.1.99/linux/include/linux/dcache.h	Wed Jan 14 16:57:09 1998
+++ linux/include/linux/dcache.h	Sat May  2 17:42:39 1998
@@ -131,7 +131,7 @@
 
 /* dcache memory management */
 extern int  select_dcache(int, int);
-extern void shrink_dcache_memory(void);
+extern void shrink_dcache_memory(int, unsigned int);
 extern void check_dcache_memory(void);
 extern void free_inode_memory(int);	/* defined in fs/inode.c */
 
diff -u --recursive --new-file v2.1.99/linux/include/linux/icmpv6.h linux/include/linux/icmpv6.h
--- v2.1.99/linux/include/linux/icmpv6.h	Fri Feb  6 15:33:34 1998
+++ linux/include/linux/icmpv6.h	Mon May  4 17:05:22 1998
@@ -138,9 +138,12 @@
 						    __u32 info, 
 						    struct device *dev);
 
-extern void				icmpv6_init(struct net_proto_family *ops);
+extern int				icmpv6_init(struct net_proto_family *ops);
 extern int				icmpv6_err_convert(int type, int code,
 							   int *err);
+extern void				icmpv6_cleanup(void);
+extern void				icmpv6_param_prob(struct sk_buff *skb,
+							  int code, void *pos);
 #endif
 
 #endif
diff -u --recursive --new-file v2.1.99/linux/include/linux/ipv6.h linux/include/linux/ipv6.h
--- v2.1.99/linux/include/linux/ipv6.h	Fri Feb  6 15:33:34 1998
+++ linux/include/linux/ipv6.h	Mon May  4 17:05:22 1998
@@ -42,6 +42,24 @@
 	 */
 };
 
+
+struct ipv6_opt_hdr {
+	__u8 		nexthdr;
+	__u8 		hdrlen;
+	/* 
+	 * TLV encoded option data follows.
+	 */
+};
+
+#define ipv6_destopt_hdr ipv6_opt_hdr
+#define ipv6_hopopt_hdr  ipv6_opt_hdr
+
+#ifdef __KERNEL__
+#define ipv6_optlen(p)  (((p)->hdrlen+1) << 3)
+#endif
+
+
+
 /*
  *	routing header type 0 (used in cmsghdr struct)
  */
@@ -95,12 +113,12 @@
 
 	/* 
 	 * protocol options 
-	 * usualy carried in IPv6 extension headers
+	 * usually carried in IPv6 extension headers
 	 */
 
 	struct ipv6_rt_hdr		*srcrt;	/* Routing Header */
-
 };
+
 
 #endif
 
diff -u --recursive --new-file v2.1.99/linux/include/linux/pci.h linux/include/linux/pci.h
--- v2.1.99/linux/include/linux/pci.h	Thu Apr 23 20:21:38 1998
+++ linux/include/linux/pci.h	Mon May  4 13:24:12 1998
@@ -1,5 +1,5 @@
 /*
- *	$Id: pci.h,v 1.67 1998/04/16 20:48:33 mj Exp $
+ *	$Id: pci.h,v 1.70 1998/05/02 19:20:03 mj Exp $
  *
  *	PCI defines and function prototypes
  *	Copyright 1994, Drew Eckhardt
@@ -275,6 +275,7 @@
  */
 #define PCI_VENDOR_ID_COMPAQ		0x0e11
 #define PCI_DEVICE_ID_COMPAQ_1280	0x3033
+#define PCI_DEVICE_ID_COMPAQ_TRIFLEX	0x4000
 #define PCI_DEVICE_ID_COMPAQ_SMART2P	0xae10
 #define PCI_DEVICE_ID_COMPAQ_NETEL100	0xae32
 #define PCI_DEVICE_ID_COMPAQ_NETEL10	0xae34
@@ -303,10 +304,14 @@
 #define PCI_DEVICE_ID_ATI_210888CX	0x4358
 #define PCI_DEVICE_ID_ATI_215GB		0x4742
 #define PCI_DEVICE_ID_ATI_215GD		0x4744
+#define PCI_DEVICE_ID_ATI_215GI		0x4749
 #define PCI_DEVICE_ID_ATI_215GP		0x4750
+#define PCI_DEVICE_ID_ATI_215GQ		0x4751
 #define PCI_DEVICE_ID_ATI_215GT		0x4754
 #define PCI_DEVICE_ID_ATI_215GTB	0x4755
 #define PCI_DEVICE_ID_ATI_210888GX	0x4758
+#define PCI_DEVICE_ID_ATI_215LG		0x4c47
+#define PCI_DEVICE_ID_ATI_264LT		0x4c54
 #define PCI_DEVICE_ID_ATI_264VT		0x5654
 
 #define PCI_VENDOR_ID_VLSI		0x1004
@@ -376,7 +381,8 @@
 #define PCI_DEVICE_ID_IBM_MCA		0x0020
 #define PCI_DEVICE_ID_IBM_82351		0x0022
 #define PCI_DEVICE_ID_IBM_SERVERAID	0x002e
-#define PCI_DEVICE_ID_IBM_MPEG2		0x007d
+#define PCI_DEVICE_ID_IBM_TR_WAKE	0x003e
+#define PCI_DEVICE_ID_IBM_3780IDSP	0x007d
 
 #define PCI_VENDOR_ID_WD		0x101c
 #define PCI_DEVICE_ID_WD_7197		0x3296
@@ -408,6 +414,7 @@
 #define PCI_DEVICE_ID_CT_65548		0x00dc
 #define PCI_DEVICE_ID_CT_65550		0x00e0
 #define PCI_DEVICE_ID_CT_65554		0x00e4
+#define PCI_DEVICE_ID_CT_65555		0x00e5
 
 #define PCI_VENDOR_ID_MIRO		0x1031
 #define PCI_DEVICE_ID_MIRO_36050	0x5601
@@ -419,9 +426,11 @@
 #define PCI_DEVICE_ID_FD_36C70		0x0000
 
 #define PCI_VENDOR_ID_SI		0x1039
-#define PCI_DEVICE_ID_SI_6201		0x0001
+#define PCI_DEVICE_ID_SI_5591_AGP	0x0001
 #define PCI_DEVICE_ID_SI_6202		0x0002
 #define PCI_DEVICE_ID_SI_503		0x0008
+#define PCI_DEVICE_ID_SI_ACPI		0x0009
+#define PCI_DEVICE_ID_SI_5597_VGA	0x0200
 #define PCI_DEVICE_ID_SI_6205		0x0205
 #define PCI_DEVICE_ID_SI_501		0x0406
 #define PCI_DEVICE_ID_SI_496		0x0496
@@ -430,6 +439,7 @@
 #define PCI_DEVICE_ID_SI_5511		0x5511
 #define PCI_DEVICE_ID_SI_5513		0x5513
 #define PCI_DEVICE_ID_SI_5571		0x5571
+#define PCI_DEVICE_ID_SI_5591		0x5591
 #define PCI_DEVICE_ID_SI_5597		0x5597
 #define PCI_DEVICE_ID_SI_7001		0x7001
 
@@ -493,6 +503,7 @@
 #define PCI_VENDOR_ID_N9		0x105d
 #define PCI_DEVICE_ID_N9_I128		0x2309
 #define PCI_DEVICE_ID_N9_I128_2		0x2339
+#define PCI_DEVICE_ID_N9_I128_T2R	0x493d
 
 #define PCI_VENDOR_ID_UMC		0x1060
 #define PCI_DEVICE_ID_UMC_UM8673F	0x0101
@@ -510,6 +521,7 @@
 
 #define PCI_VENDOR_ID_PICOP		0x1066
 #define PCI_DEVICE_ID_PICOP_PT86C52X	0x0001
+#define PCI_DEVICE_ID_PICOP_PT80C524	0x8002
 
 #define PCI_VENDOR_ID_APPLE		0x106b
 #define PCI_DEVICE_ID_APPLE_BANDIT	0x0001
@@ -538,7 +550,7 @@
 
 #define PCI_VENDOR_ID_CONTAQ		0x1080
 #define PCI_DEVICE_ID_CONTAQ_82C599	0x0600
-#define PCI_DEVICE_ID_CONTAQ_82C693	0xC693
+#define PCI_DEVICE_ID_CONTAQ_82C693	0xc693
 
 #define PCI_VENDOR_ID_FOREX		0x1083
 
@@ -589,7 +601,11 @@
 #define PCI_VENDOR_ID_PLX		0x10b5
 #define PCI_DEVICE_ID_PLX_9080		0x9080
 
+#define PCI_VENDOR_ID_MADGE		0x10b6
+#define PCI_DEVICE_ID_MADGE_MK2		0x0002
+
 #define PCI_VENDOR_ID_3COM		0x10b7
+#define PCI_DEVICE_ID_3COM_3C339	0x3390
 #define PCI_DEVICE_ID_3COM_3C590	0x5900
 #define PCI_DEVICE_ID_3COM_3C595TX	0x5950
 #define PCI_DEVICE_ID_3COM_3C595T4	0x5951
@@ -597,6 +613,8 @@
 #define PCI_DEVICE_ID_3COM_3C900TPO	0x9000
 #define PCI_DEVICE_ID_3COM_3C900COMBO	0x9001
 #define PCI_DEVICE_ID_3COM_3C905TX	0x9050
+#define PCI_DEVICE_ID_3COM_3C905T4	0x9051
+#define PCI_DEVICE_ID_3COM_3C905B_TX	0x9055
 
 #define PCI_VENDOR_ID_SMC		0x10b8
 #define PCI_DEVICE_ID_SMC_EPIC100	0x0005
@@ -618,6 +636,7 @@
 #define PCI_DEVICE_ID_AL_M5219		0x5219
 #define PCI_DEVICE_ID_AL_M5229		0x5229
 #define PCI_DEVICE_ID_AL_M5237		0x5237
+#define PCI_DEVICE_ID_AL_M7101		0x7101
 
 #define PCI_VENDOR_ID_MITSUBISHI	0x10ba
 
@@ -635,6 +654,10 @@
 #define PCI_DEVICE_ID_ASP_ABP940U	0x1300
 #define PCI_DEVICE_ID_ASP_ABP940UW	0x2300
 
+#define PCI_VENDOR_ID_MACRONIX		0x10d9
+#define PCI_DEVICE_ID_MACRONIX_MX98713	0x0512
+#define PCI_DEVICE_ID_MACRONIX_MX987x5	0x0531
+
 #define PCI_VENDOR_ID_CERN		0x10dc
 #define PCI_DEVICE_ID_CERN_SPSB_PMC	0x0001
 #define PCI_DEVICE_ID_CERN_SPSB_PCI	0x0002
@@ -654,6 +677,7 @@
 
 #define PCI_VENDOR_ID_AMCC		0x10e8
 #define PCI_DEVICE_ID_AMCC_MYRINET	0x8043
+#define PCI_DEVICE_ID_AMCC_PARASTATION	0x8062
 #define PCI_DEVICE_ID_AMCC_S5933	0x807d
 #define PCI_DEVICE_ID_AMCC_S5933_HEPC3	0x809c
 
@@ -664,6 +688,7 @@
 #define PCI_VENDOR_ID_REALTEK		0x10ec
 #define PCI_DEVICE_ID_REALTEK_8029	0x8029
 #define PCI_DEVICE_ID_REALTEK_8129	0x8129
+#define PCI_DEVICE_ID_REALTEK_8139	0x8139
 
 #define PCI_VENDOR_ID_TRUEVISION	0x10fa
 #define PCI_DEVICE_ID_TRUEVISION_T1000	0x000c
@@ -686,6 +711,7 @@
 #define PCI_DEVICE_ID_VIA_82C595_97	0x1595
 #define PCI_DEVICE_ID_VIA_82C586_2	0x3038
 #define PCI_DEVICE_ID_VIA_82C586_3	0x3040
+#define PCI_DEVICE_ID_VIA_86C100A	0x6100
 #define PCI_DEVICE_ID_VIA_82C597_1	0x8597
 
 #define PCI_VENDOR_ID_VORTEX		0x1119
@@ -734,6 +760,7 @@
 #define PCI_DEVICE_ID_IMAGINGTECH_ICPCI	0x0000
 
 #define PCI_VENDOR_ID_PHILIPS		0x1131
+#define PCI_DEVICE_ID_PHILIPS_SAA7145	0x7145
 #define PCI_DEVICE_ID_PHILIPS_SAA7146	0x7146
 
 #define PCI_VENDOR_ID_CYCLONE		0x113c
@@ -756,6 +783,7 @@
 #define PCI_DEVICE_ID_DIGI_CX		0x0006
 #define PCI_DEVICE_ID_DIGI_XRJ		0x0009
 #define PCI_DEVICE_ID_DIGI_EPCJ		0x000a
+#define PCI_DEVICE_ID_DIGI_XR_920	0x0027
 
 #define PCI_VENDOR_ID_MUTECH		0x1159
 #define PCI_DEVICE_ID_MUTECH_MV1000	0x0001
@@ -806,6 +834,9 @@
 #define PCI_DEVICE_ID_ZORAN_36057	0x6057
 #define PCI_DEVICE_ID_ZORAN_36120	0x6120
 
+#define PCI_VENDOR_ID_KINETIC		0x11f4
+#define PCI_DEVICE_ID_KINETIC_2915	0x2915
+
 #define PCI_VENDOR_ID_COMPEX		0x11f6
 #define PCI_DEVICE_ID_COMPEX_ENET100VG4	0x0112
 #define PCI_DEVICE_ID_COMPEX_RL2000	0x1401
@@ -823,7 +854,7 @@
 #define PCI_DEVICE_ID_CYCLOM_Z_Hi	0x0201
 
 #define PCI_VENDOR_ID_ESSENTIAL		0x120f
-#define PCI_DEVICE_ID_ROADRUNNER	0x0001
+#define PCI_DEVICE_ID_ESSENTIAL_ROADRUNNER	0x0001
 
 #define PCI_VENDOR_ID_O2		0x1217
 #define PCI_DEVICE_ID_O2_6832		0x6832
@@ -835,6 +866,10 @@
 #define PCI_VENDOR_ID_SIGMADES		0x1236
 #define PCI_DEVICE_ID_SIGMADES_6425	0x6401
 
+#define PCI_VENDOR_ID_CCUBE		0x123f
+
+#define PCI_VENDOR_ID_DIPIX		0x1246
+
 #define PCI_VENDOR_ID_STALLION		0x124d
 #define PCI_DEVICE_ID_STALLION_ECHPCI832 0x0000
 #define PCI_DEVICE_ID_STALLION_ECHPCI864 0x0002
@@ -847,6 +882,13 @@
 #define PCI_DEVICE_ID_OPTIBASE_VPLEXCC	0x2120
 #define PCI_DEVICE_ID_OPTIBASE_VQUEST	0x2130
 
+#define PCI_VENDOR_ID_SATSAGEM		0x1267
+#define PCI_DEVICE_ID_SATSAGEM_PCR2101	0x5352
+#define PCI_DEVICE_ID_SATSAGEM_TELSATTURBO 0x5a4b
+
+#define PCI_VENDOR_ID_HUGHES		0x1273
+#define PCI_DEVICE_ID_HUGHES_DIRECPC	0x0002
+
 #define PCI_VENDOR_ID_ENSONIQ		0x1274
 #define PCI_DEVICE_ID_ENSONIQ_AUDIOPCI	0x5000
 
@@ -856,6 +898,9 @@
 #define PCI_VENDOR_ID_NVIDIA_SGS	0x12d2
 #define PCI_DEVICE_ID_NVIDIA_SGS_RIVA128 0x0018
 
+#define PCI_VENDOR_ID_CBOARDS		0x1307
+#define PCI_DEVICE_ID_CBOARDS_DAS1602_16 0x0001
+
 #define PCI_VENDOR_ID_SYMPHONY		0x1c1c
 #define PCI_DEVICE_ID_SYMPHONY_101	0x0001
 
@@ -867,6 +912,7 @@
 #define PCI_DEVICE_ID_3DLABS_500TX	0x0002
 #define PCI_DEVICE_ID_3DLABS_DELTA	0x0003
 #define PCI_DEVICE_ID_3DLABS_PERMEDIA	0x0004
+#define PCI_DEVICE_ID_3DLABS_MX		0x0006
 
 #define PCI_VENDOR_ID_AVANCE		0x4005
 #define PCI_DEVICE_ID_AVANCE_ALG2064	0x2064
@@ -916,6 +962,7 @@
 #define PCI_DEVICE_ID_INTEL_82371MX	0x1234
 #define PCI_DEVICE_ID_INTEL_82437MX	0x1235
 #define PCI_DEVICE_ID_INTEL_82441	0x1237
+#define PCI_DEVICE_ID_INTEL_82380FB	0x124b
 #define PCI_DEVICE_ID_INTEL_82439	0x1250
 #define PCI_DEVICE_ID_INTEL_82371SB_0	0x7000
 #define PCI_DEVICE_ID_INTEL_82371SB_1	0x7010
@@ -928,6 +975,9 @@
 #define PCI_DEVICE_ID_INTEL_82371AB_3	0x7113
 #define PCI_DEVICE_ID_INTEL_82443LX_0	0x7180
 #define PCI_DEVICE_ID_INTEL_82443LX_1	0x7181
+#define PCI_DEVICE_ID_INTEL_82443BX_0	0x7190
+#define PCI_DEVICE_ID_INTEL_82443BX_1	0x7191
+#define PCI_DEVICE_ID_INTEL_82443BX_2	0x7192
 #define PCI_DEVICE_ID_INTEL_P6		0x84c4
 #define PCI_DEVICE_ID_INTEL_82450GX	0x84c5
 
@@ -952,6 +1002,7 @@
 #define PCI_DEVICE_ID_ADAPTEC_7882	0x8278
 #define PCI_DEVICE_ID_ADAPTEC_7883	0x8378
 #define PCI_DEVICE_ID_ADAPTEC_7884	0x8478
+#define PCI_DEVICE_ID_ADAPTEC_1030	0x8b78
 
 #define PCI_VENDOR_ID_ATRONICS		0x907f
 #define PCI_DEVICE_ID_ATRONICS_2015	0x2015
@@ -959,6 +1010,9 @@
 #define PCI_VENDOR_ID_HOLTEK		0x9412
 #define PCI_DEVICE_ID_HOLTEK_6565	0x6565
 
+#define PCI_VENDOR_ID_TIGERJET		0xe159
+#define PCI_DEVICE_ID_TIGERJET_300	0x0001
+
 #define PCI_VENDOR_ID_ARK		0xedd8
 #define PCI_DEVICE_ID_ARK_STING		0xa091
 #define PCI_DEVICE_ID_ARK_STINGARK	0xa099
@@ -978,6 +1032,8 @@
 
 #ifdef __KERNEL__
 
+#include <linux/types.h>
+
 /*
  * Error values that may be returned by the PCI bios.
  */
@@ -1084,13 +1140,13 @@
 struct pci_dev *pci_find_slot (unsigned int bus, unsigned int devfn);
 
 #define pci_present pcibios_present
-#define pci_read_config_byte(dev, where, val) pcibios_read_config_byte(dev->bus->number, dev->devfn, where, val)
-#define pci_read_config_word(dev, where, val) pcibios_read_config_word(dev->bus->number, dev->devfn, where, val)
-#define pci_read_config_dword(dev, where, val) pcibios_read_config_dword(dev->bus->number, dev->devfn, where, val)
-#define pci_write_config_byte(dev, where, val) pcibios_write_config_byte(dev->bus->number, dev->devfn, where, val)
-#define pci_write_config_word(dev, where, val) pcibios_write_config_word(dev->bus->number, dev->devfn, where, val)
-#define pci_write_config_dword(dev, where, val) pcibios_write_config_dword(dev->bus->number, dev->devfn, where, val)
-void pci_set_master(struct pci_dev *);
+int pci_read_config_byte(struct pci_dev *dev, u8 where, u8 *val);
+int pci_read_config_word(struct pci_dev *dev, u8 where, u16 *val);
+int pci_read_config_dword(struct pci_dev *dev, u8 where, u32 *val);
+int pci_write_config_byte(struct pci_dev *dev, u8 where, u8 val);
+int pci_write_config_word(struct pci_dev *dev, u8 where, u16 val);
+int pci_write_config_dword(struct pci_dev *dev, u8 where, u32 val);
+void pci_set_master(struct pci_dev *dev);
 
 #endif /* __KERNEL__ */
 #endif /* LINUX_PCI_H */
diff -u --recursive --new-file v2.1.99/linux/include/linux/proc_fs.h linux/include/linux/proc_fs.h
--- v2.1.99/linux/include/linux/proc_fs.h	Sat May  2 14:19:54 1998
+++ linux/include/linux/proc_fs.h	Mon May  4 17:09:22 1998
@@ -51,6 +51,7 @@
 	PROC_PPC_HTAB,
 	PROC_SOUND,
 	PROC_MTRR, /* whether enabled or not */
+	PROC_FS
 };
 
 enum pid_directory_inos {
@@ -203,6 +204,19 @@
 	PROC_BUS_PCI = PROC_MCA_LAST,
 	PROC_BUS_PCI_DEVICES,
 	PROC_BUS_LAST
+};
+
+enum fs_directory_inos {
+	PROC_FS_CODA = PROC_MCA_LAST,
+	PROC_FS_LAST
+};
+
+enum fs_coda_directory_inos {
+	PROC_VFS_STATS = PROC_MCA_LAST,
+	PROC_UPCALL_STATS,
+	PROC_PERMISSION_STATS,
+	PROC_CACHE_INV_STATS,
+	PROC_CODA_FS_LAST
 };
 
 /* Finally, the dynamically allocatable proc entries are reserved: */
diff -u --recursive --new-file v2.1.99/linux/include/linux/swapctl.h linux/include/linux/swapctl.h
--- v2.1.99/linux/include/linux/swapctl.h	Thu Mar 26 15:57:06 1998
+++ linux/include/linux/swapctl.h	Mon May  4 17:04:40 1998
@@ -50,6 +50,15 @@
 typedef freepages_v1 freepages_t;
 extern freepages_t freepages;
 
+typedef struct pager_daemon_v1
+{
+	unsigned int	tries_base;
+	unsigned int	tries_min;
+	unsigned int	swap_cluster;
+} pager_daemon_v1;
+typedef pager_daemon_v1 pager_daemon_t;
+extern pager_daemon_t pager_daemon;
+
 #define SC_VERSION	1
 #define SC_MAX_VERSION	1
 
diff -u --recursive --new-file v2.1.99/linux/include/linux/sysctl.h linux/include/linux/sysctl.h
--- v2.1.99/linux/include/linux/sysctl.h	Sat May  2 14:19:54 1998
+++ linux/include/linux/sysctl.h	Sat May  2 17:45:03 1998
@@ -84,7 +84,8 @@
 	VM_BDFLUSH,		/* struct: Control buffer cache flushing */
 	VM_OVERCOMMIT_MEMORY,	/* Turn off the virtual memory safety limit */
 	VM_BUFFERMEM,		/* struct: Set buffer memory thresholds */
-	VM_PAGECACHE		/* struct: Set cache memory thresholds */
+	VM_PAGECACHE,		/* struct: Set cache memory thresholds */
+	VM_PAGERDAEMON		/* struct: Control kswapd behaviour */
 };
 
 
diff -u --recursive --new-file v2.1.99/linux/include/linux/ufs_fs.h linux/include/linux/ufs_fs.h
--- v2.1.99/linux/include/linux/ufs_fs.h	Wed Apr  1 20:11:54 1998
+++ linux/include/linux/ufs_fs.h	Sun May  3 12:03:35 1998
@@ -255,12 +255,12 @@
 			__s32	fs_contigsumsize;/* size of cluster summary array */
 			__s32	fs_maxsymlinklen;/* max length of an internal symlink */
 			__s32	fs_inodefmt;	/* format of on-disk inodes */
-			__u64	fs_maxfilesize;	/* max representable file size */
+			__u32	fs_maxfilesize[2];/* max representable file size */
 			__u32	fs_qbmask[2];	/* ~usb_bmask */
 			__u32	fs_qfmask[2];	/* ~usb_fmask */
 			__s32	fs_state;	/* file system state time stamp */
 		} fs_44;
-	} fs_u  __attribute__ ((packed));
+	} fs_u;
 	__s32	fs_postblformat;	/* format of positional layout tables */
 	__s32	fs_nrpos;		/* number of rotational positions */
 	__s32	fs_postbloff;		/* (__s16) rotation block list head */
diff -u --recursive --new-file v2.1.99/linux/include/net/ipv6.h linux/include/net/ipv6.h
--- v2.1.99/linux/include/net/ipv6.h	Tue Mar 17 22:18:15 1998
+++ linux/include/net/ipv6.h	Mon May  4 17:06:59 1998
@@ -4,7 +4,7 @@
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>
  *
- *	$Id: ipv6.h,v 1.9 1998/03/08 05:55:20 davem Exp $
+ *	$Id: ipv6.h,v 1.10 1998/04/30 16:24:14 freitag Exp $
  *
  *	This program is free software; you can redistribute it and/or
  *      modify it under the terms of the GNU General Public License
@@ -108,6 +108,8 @@
 	struct frag_queue	*prev;
 
 	__u32			id;		/* fragment id		*/
+	struct in6_addr		saddr;
+	struct in6_addr		daddr;
 	struct timer_list	timer;		/* expire timer		*/
 	struct ipv6_frag	*fragments;
 	struct device		*dev;
@@ -247,6 +249,10 @@
 						  int len);
 
 extern void			ipv6opt_free(struct ipv6_options *opt);
+
+extern struct ipv6_opt_hdr *	ipv6_skip_exthdr(struct ipv6_opt_hdr *hdr, 
+					         u8 *nexthdrp, int len);
+
 
 
 /*
diff -u --recursive --new-file v2.1.99/linux/include/net/ndisc.h linux/include/net/ndisc.h
--- v2.1.99/linux/include/net/ndisc.h	Fri Feb  6 15:35:04 1998
+++ linux/include/net/ndisc.h	Mon May  4 17:06:59 1998
@@ -101,6 +101,8 @@
 						   struct icmp6hdr *hdr,
 						   int len);
 
+extern void			igmp6_cleanup(void);
+
 extern __inline__ struct neighbour * ndisc_get_neigh(struct device *dev, struct in6_addr *addr)
 {
 
diff -u --recursive --new-file v2.1.99/linux/include/net/tcp.h linux/include/net/tcp.h
--- v2.1.99/linux/include/net/tcp.h	Sat May  2 14:19:54 1998
+++ linux/include/net/tcp.h	Mon May  4 17:06:53 1998
@@ -642,7 +642,7 @@
 
 		/* PMTU discovery event has occurred. */
 		sk->mtu = dst->pmtu;
-		sk->mss = sk->mtu - mss_distance;
+		mss_now = sk->mss = sk->mtu - mss_distance;
 	}
 
 	if(tp->sack_ok && tp->num_sacks)
diff -u --recursive --new-file v2.1.99/linux/include/scsi/scsi_ioctl.h linux/include/scsi/scsi_ioctl.h
--- v2.1.99/linux/include/scsi/scsi_ioctl.h	Sat May  2 14:19:54 1998
+++ linux/include/scsi/scsi_ioctl.h	Fri May  1 11:19:58 1998
@@ -5,6 +5,8 @@
 #define SCSI_IOCTL_TEST_UNIT_READY 2
 #define SCSI_IOCTL_BENCHMARK_COMMAND 3
 #define SCSI_IOCTL_SYNC 4			/* Request synchronous parameters */
+#define SCSI_IOCTL_START_UNIT 5
+#define SCSI_IOCTL_STOP_UNIT 6
 /* The door lock/unlock constants are compatible with Sun constants for
    the cdrom */
 #define SCSI_IOCTL_DOORLOCK 0x5380		/* lock the eject mechanism */
diff -u --recursive --new-file v2.1.99/linux/kernel/sysctl.c linux/kernel/sysctl.c
--- v2.1.99/linux/kernel/sysctl.c	Sat May  2 14:19:54 1998
+++ linux/kernel/sysctl.c	Sat May  2 17:44:59 1998
@@ -189,20 +189,22 @@
 
 static ctl_table vm_table[] = {
 	{VM_SWAPCTL, "swapctl", 
-	 &swap_control, sizeof(swap_control_t), 0600, NULL, &proc_dointvec},
+	 &swap_control, sizeof(swap_control_t), 0644, NULL, &proc_dointvec},
 	{VM_SWAPOUT, "swapout_interval",
-	 &swapout_interval, sizeof(int), 0600, NULL, &proc_dointvec},
+	 &swapout_interval, sizeof(int), 0644, NULL, &proc_dointvec},
 	{VM_FREEPG, "freepages", 
-	 &freepages, sizeof(freepages_t), 0600, NULL, &proc_dointvec},
+	 &freepages, sizeof(freepages_t), 0644, NULL, &proc_dointvec},
 	{VM_BDFLUSH, "bdflush", &bdf_prm, 9*sizeof(int), 0600, NULL,
 	 &proc_dointvec_minmax, &sysctl_intvec, NULL,
 	 &bdflush_min, &bdflush_max},
 	{VM_OVERCOMMIT_MEMORY, "overcommit_memory", &sysctl_overcommit_memory,
 	 sizeof(sysctl_overcommit_memory), 0644, NULL, &proc_dointvec},
 	{VM_BUFFERMEM, "buffermem",
-	 &buffer_mem, sizeof(buffer_mem_t), 0600, NULL, &proc_dointvec},
+	 &buffer_mem, sizeof(buffer_mem_t), 0644, NULL, &proc_dointvec},
 	{VM_PAGECACHE, "pagecache",
-	 &page_cache, sizeof(buffer_mem_t), 0600, NULL, &proc_dointvec},
+	 &page_cache, sizeof(buffer_mem_t), 0644, NULL, &proc_dointvec},
+	{VM_PAGERDAEMON, "kswapd",
+	 &pager_daemon, sizeof(pager_daemon_t), 0644, NULL, &proc_dointvec},
 	{0}
 };
 
diff -u --recursive --new-file v2.1.99/linux/mm/Makefile linux/mm/Makefile
--- v2.1.99/linux/mm/Makefile	Wed Jul 16 19:22:51 1997
+++ linux/mm/Makefile	Sun May  3 12:14:31 1998
@@ -9,7 +9,7 @@
 
 O_TARGET := mm.o
 O_OBJS	 := memory.o mmap.o filemap.o mprotect.o mlock.o mremap.o \
-	    vmalloc.o slab.o simp.o\
+	    vmalloc.o slab.o \
 	    swap.o vmscan.o page_io.o page_alloc.o swap_state.o swapfile.o
 
 include $(TOPDIR)/Rules.make
diff -u --recursive --new-file v2.1.99/linux/mm/page_alloc.c linux/mm/page_alloc.c
--- v2.1.99/linux/mm/page_alloc.c	Sat May  2 14:19:54 1998
+++ linux/mm/page_alloc.c	Sun May  3 12:09:15 1998
@@ -125,7 +125,7 @@
 	 * free unfragmented memory.
 	 * Added low/high water marks to avoid thrashing -- Rik.
 	 */
-	if (nr_free_pages > (num_physpages >> 5) + (nr ? 0 : num_physpages >> 6))
+	if (nr_free_pages > (nr ? freepages.low : freepages.high))
 		return nr+1;
 
 	list = free_area + NR_MEM_LISTS;
@@ -282,7 +282,6 @@
 		spin_unlock_irqrestore(&page_alloc_lock, flags);
 		if (!(gfp_mask & __GFP_WAIT))
 			break;
-		shrink_dcache();
 		if (!try_to_free_pages(gfp_mask, SWAP_CLUSTER_MAX))
 			break;
 		gfp_mask &= ~__GFP_WAIT;	/* go through this only once */
@@ -335,15 +334,19 @@
 	int i;
 
 	/*
-	 * select nr of pages we try to keep free for important stuff
-	 * with a minimum of 48 pages. This is totally arbitrary
+	 * Select nr of pages we try to keep free for important stuff
+	 * with a minimum of 48 pages and a maximum of 256 pages, so
+	 * that we don't waste too much memory on large systems.
+	 * This is totally arbitrary.
 	 */
 	i = (end_mem - PAGE_OFFSET) >> (PAGE_SHIFT+7);
 	if (i < 48)
 		i = 48;
+	if (i > 256)
+		i = 256;
 	freepages.min = i;
-	freepages.low = i + (i>>1);
-	freepages.high = i + i;
+	freepages.low = i << 1;
+	freepages.high = freepages.low + i;
 	mem_map = (mem_map_t *) LONG_ALIGN(start_mem);
 	p = mem_map + MAP_NR(end_mem);
 	start_mem = LONG_ALIGN((unsigned long) p);
diff -u --recursive --new-file v2.1.99/linux/mm/swap.c linux/mm/swap.c
--- v2.1.99/linux/mm/swap.c	Thu Mar 26 15:57:06 1998
+++ linux/mm/swap.c	Sat May  2 17:44:59 1998
@@ -44,8 +44,8 @@
  */
 freepages_t freepages = {
 	48,	/* freepages.min */
-	72,	/* freepages.low */
-	96	/* freepages.high */
+	96,	/* freepages.low */
+	144	/* freepages.high */
 };
 
 /* We track the number of pages currently being asynchronously swapped
@@ -76,4 +76,10 @@
 	10,	/* minimum percent page cache */
 	30,	/* borrow percent page cache */
 	75	/* maximum */
+};
+
+pager_daemon_t pager_daemon = {
+	512,	/* base number for calculating the number of tries */
+	SWAP_CLUSTER_MAX,	/* minimum number of tries */
+	SWAP_CLUSTER_MAX,	/* do swap I/O in clusters of this size */
 };
diff -u --recursive --new-file v2.1.99/linux/mm/vmscan.c linux/mm/vmscan.c
--- v2.1.99/linux/mm/vmscan.c	Sat May  2 14:19:54 1998
+++ linux/mm/vmscan.c	Sat May  2 17:44:59 1998
@@ -455,17 +455,20 @@
 	switch (state) {
 		do {
 		case 0:
-			state = 1;
 			if (shrink_mmap(i, gfp_mask))
 				return 1;
+			state = 1;
 		case 1:
-			state = 2;
 			if ((gfp_mask & __GFP_IO) && shm_swap(i, gfp_mask))
 				return 1;
-		default:
-			state = 0;
+			state = 2;
+		case 2:
 			if (swap_out(i, gfp_mask))
 				return 1;
+			state = 3;
+		case 3:
+			shrink_dcache_memory(i, gfp_mask);
+			state = 0;
 		i--;
 		} while ((i - stop) >= 0);
 	}
@@ -545,30 +548,28 @@
 		schedule();
 		swapstats.wakeups++;
 
-		/* This will gently shrink the dcache.. */
-		shrink_dcache_memory();
-	
 		/*
 		 * Do the background pageout: be
 		 * more aggressive if we're really
 		 * low on free memory.
 		 *
-		 * The number of tries is 512 divided by an
-		 * 'urgency factor'. In practice this will mean
-		 * a value of 512 / 8 = 64 pages at a time,
-		 * giving 64 * 4 (times/sec) * 4k (pagesize) =
-		 * 1 MB/s in lowest-priority background
-		 * paging. This number rises to 8 MB/s when the
-		 * priority is highest (but then we'll be woken
-		 * up more often and the rate will be even higher).
-		 * -- Should make this sysctl tunable...
+		 * We try page_daemon.tries_base times, divided by
+		 * an 'urgency factor'. In practice this will mean
+		 * a value of pager_daemon.tries_base / 8 or 4 = 64
+		 * or 128 pages at a time.
+		 * This gives us 64 (or 128) * 4k * 4 (times/sec) =
+		 * 1 (or 2) MB/s swapping bandwidth in low-priority
+		 * background paging. This number rises to 8 MB/s
+		 * when the priority is highest (but then we'll be
+		 * woken up more often and the rate will be even
+		 * higher).
 		 */
-		tries = (512) >> free_memory_available(3);
+		tries = pager_daemon.tries_base >> free_memory_available(3);
 	
 		while (tries--) {
 			int gfp_mask;
 
-			if (++tried > SWAP_CLUSTER_MAX && free_memory_available(0))
+			if (++tried > pager_daemon.tries_min && free_memory_available(0))
 				break;
 			gfp_mask = __GFP_IO;
 			try_to_free_page(gfp_mask);
@@ -576,7 +577,7 @@
 			 * Syncing large chunks is faster than swapping
 			 * synchronously (less head movement). -- Rik.
 			 */
-			if (atomic_read(&nr_async_pages) >= SWAP_CLUSTER_MAX)
+			if (atomic_read(&nr_async_pages) >= pager_daemon.swap_cluster)
 				run_task_queue(&tq_disk);
 
 		}
diff -u --recursive --new-file v2.1.99/linux/net/core/dev.c linux/net/core/dev.c
--- v2.1.99/linux/net/core/dev.c	Sat May  2 14:19:54 1998
+++ linux/net/core/dev.c	Sat May  2 14:22:29 1998
@@ -1764,6 +1764,9 @@
 extern int lapbeth_init(void);
 extern void arcnet_init(void);
 extern void ip_auto_config(void);
+#ifdef CONFIG_8xx
+extern int cpm_enet_init(void);
+#endif /* CONFIG_8xx */
 
 #ifdef CONFIG_PROC_FS
 static struct proc_dir_entry proc_net_dev = {
@@ -1845,6 +1848,9 @@
 #endif
 #if defined(CONFIG_ARCNET)
 	arcnet_init();
+#endif
+#if defined(CONFIG_8xx)
+        cpm_enet_init();
 #endif
 	/*
 	 *	SLHC if present needs attaching so other people see it
diff -u --recursive --new-file v2.1.99/linux/net/ethernet/pe2.c linux/net/ethernet/pe2.c
--- v2.1.99/linux/net/ethernet/pe2.c	Sun Mar 24 22:58:24 1996
+++ linux/net/ethernet/pe2.c	Sat May  2 14:22:29 1998
@@ -11,7 +11,8 @@
 	struct device	*dev = skb->dev;
 
 	skb->protocol = htons (ETH_P_IPX);
-	dev->hard_header(skb, dev, ETH_P_IPX, dest_node, NULL, skb->len);
+	if(dev->hard_header)
+		dev->hard_header(skb, dev, ETH_P_IPX, dest_node, NULL, skb->len);
 }
 
 struct datalink_proto *
diff -u --recursive --new-file v2.1.99/linux/net/ipv4/ip_fw.c linux/net/ipv4/ip_fw.c
--- v2.1.99/linux/net/ipv4/ip_fw.c	Thu Mar 26 15:57:13 1998
+++ linux/net/ipv4/ip_fw.c	Sat May  2 14:22:29 1998
@@ -6,7 +6,7 @@
  *	license in recognition of the original copyright. 
  *				-- Alan Cox.
  *
- *	$Id: ip_fw.c,v 1.34 1998/03/20 09:12:06 davem Exp $
+ *	$Id: ip_fw.c,v 1.35 1998/04/30 16:29:51 freitag Exp $
  *
  *	Ported from BSD to Linux,
  *		Alan Cox 22/Nov/1994.
@@ -62,6 +62,7 @@
  *	Wouter Gadeyne		:	Fixed masquerading support of ftp PORT commands
  *
  *	Juan Jose Ciarlante	:	Masquerading code moved to ip_masq.c
+ *	Andi Kleen :		Print frag_offsets and the ip flags properly.
  *
  *	All the real work was done by .....
  *
@@ -202,6 +203,90 @@
 
 #if defined(CONFIG_IP_ACCT) || defined(CONFIG_IP_FIREWALL)
 
+#ifdef CONFIG_IP_FIREWALL_VERBOSE
+
+/* 
+ *	VERY ugly piece of code which actually makes kernel printf for
+ * 	matching packets. 
+ */
+
+static char *chain_name(struct ip_fw *chain, int mode)
+{
+	switch (mode) { 
+	case IP_FW_MODE_ACCT_IN: return "acct in";
+	case IP_FW_MODE_ACCT_OUT: return "acct out";
+	default:
+		if (chain == ip_fw_fwd_chain) 
+			return "fw-fwd";
+		else if (chain == ip_fw_in_chain)
+			return "fw-in";
+		else
+			return "fw-out"; 
+	}
+}
+
+static char *rule_name(struct ip_fw *f, int mode, char *buf)
+{
+	if (mode == IP_FW_MODE_ACCT_IN || mode == IP_FW_MODE_ACCT_OUT)
+		return "";
+
+	if(f->fw_flg&IP_FW_F_ACCEPT) {
+		if(f->fw_flg&IP_FW_F_REDIR) {
+			sprintf(buf, "acc/r%d ", f->fw_pts[f->fw_nsp+f->fw_ndp]);
+			return buf;
+		} else if(f->fw_flg&IP_FW_F_MASQ)
+			return "acc/masq ";
+		else
+			return "acc ";
+	} else if(f->fw_flg&IP_FW_F_ICMPRPL) {
+		return "rej ";
+	} else {
+		return "deny ";
+	}
+}
+
+static void print_packet(struct iphdr *ip, 
+			 u16 src_port, u16 dst_port, u16 icmp_type,
+			 char *chain, char *rule, char *devname)
+{
+	__u32 *opt = (__u32 *) (ip + 1);
+	int opti;
+	__u16 foff = ntohs(ip->frag_off); 
+
+	printk(KERN_INFO "IP %s %s%s", chain, rule, devname); 
+
+	switch(ip->protocol)
+	{
+	case IPPROTO_TCP:
+		printk(" TCP ");
+		break;
+	case IPPROTO_UDP:
+		printk(" UDP ");
+		break;
+	case IPPROTO_ICMP:
+		printk(" ICMP/%d ", icmp_type);
+		break;
+	default:
+		printk(" PROTO=%d ", ip->protocol);
+		break;
+	}
+	print_ip(ip->saddr);
+	if(ip->protocol == IPPROTO_TCP || ip->protocol == IPPROTO_UDP)
+		printk(":%hu", src_port);
+	printk(" ");
+	print_ip(ip->daddr);
+	if(ip->protocol == IPPROTO_TCP || ip->protocol == IPPROTO_UDP)
+		printk(":%hu", dst_port);
+	printk(" L=%hu S=0x%2.2hX I=%hu FO=0x%4.4hX T=%hu",
+	       ntohs(ip->tot_len), ip->tos, ntohs(ip->id),
+	       foff & IP_OFFSET, ip->ttl); 
+	if (foff & IP_DF) printk(" DF=1");
+	if (foff & IP_MF) printk(" MF=1"); 
+	for (opti = 0; opti < (ip->ihl - sizeof(struct iphdr) / 4); opti++)
+		printk(" O=0x%8.8X", *opt++);
+	printk("\n");	
+}
+#endif
 
 /*
  *	Returns one of the generic firewall policies, like FW_ACCEPT.
@@ -483,68 +568,14 @@
 		}
 
 #ifdef CONFIG_IP_FIREWALL_VERBOSE
-		/*
-		 * VERY ugly piece of code which actually
-		 * makes kernel printf for matching packets...
-		 */
-
 		if (f->fw_flg & IP_FW_F_PRN)
 		{
-			__u32 *opt = (__u32 *) (ip + 1);
-			int opti;
+			char buf[16]; 
 
-			if(mode == IP_FW_MODE_ACCT_IN)
-				printk(KERN_INFO "IP acct in ");
-			else if(mode == IP_FW_MODE_ACCT_OUT)
-				printk(KERN_INFO "IP acct out ");
-			else {
-				if(chain == ip_fw_fwd_chain)
-					printk(KERN_INFO "IP fw-fwd ");
-				else if(chain == ip_fw_in_chain)
-					printk(KERN_INFO "IP fw-in ");
-				else
-					printk(KERN_INFO "IP fw-out ");
-				if(f->fw_flg&IP_FW_F_ACCEPT) {
-					if(f->fw_flg&IP_FW_F_REDIR)
-						printk("acc/r%d ", f->fw_pts[f->fw_nsp+f->fw_ndp]);
-					else if(f->fw_flg&IP_FW_F_MASQ)
-						printk("acc/masq ");
-					else
-						printk("acc ");
-				} else if(f->fw_flg&IP_FW_F_ICMPRPL)
-					printk("rej ");
-				else
-					printk("deny ");
-			}
-			printk(rif ? rif->name : "-");
-			switch(ip->protocol)
-			{
-				case IPPROTO_TCP:
-					printk(" TCP ");
-					break;
-				case IPPROTO_UDP:
-					printk(" UDP ");
-					break;
-				case IPPROTO_ICMP:
-					printk(" ICMP/%d ", icmp_type);
-					break;
-				default:
-					printk(" PROTO=%d ", ip->protocol);
-					break;
-			}
-			print_ip(ip->saddr);
-			if(ip->protocol == IPPROTO_TCP || ip->protocol == IPPROTO_UDP)
-				printk(":%hu", src_port);
-			printk(" ");
-			print_ip(ip->daddr);
-			if(ip->protocol == IPPROTO_TCP || ip->protocol == IPPROTO_UDP)
-				printk(":%hu", dst_port);
-			printk(" L=%hu S=0x%2.2hX I=%hu F=0x%4.4hX T=%hu",
-				ntohs(ip->tot_len), ip->tos, ntohs(ip->id),
-				ip->frag_off, ip->ttl);
-			for (opti = 0; opti < (ip->ihl - sizeof(struct iphdr) / 4); opti++)
-				printk(" O=0x%8.8X", *opt++);
-			printk("\n");
+			print_packet(ip, src_port, dst_port, icmp_type,
+				     chain_name(chain, mode), 
+				     rule_name(f, mode, buf), 
+				     rif ? rif->name : "-");
 		}
 #endif		
 		if (mode != IP_FW_MODE_CHK) {
diff -u --recursive --new-file v2.1.99/linux/net/ipv4/tcp_input.c linux/net/ipv4/tcp_input.c
--- v2.1.99/linux/net/ipv4/tcp_input.c	Sat May  2 14:19:55 1998
+++ linux/net/ipv4/tcp_input.c	Sat May  2 14:22:29 1998
@@ -5,7 +5,7 @@
  *
  *		Implementation of the Transmission Control Protocol(TCP).
  *
- * Version:	$Id: tcp_input.c,v 1.114 1998/04/28 06:42:22 davem Exp $
+ * Version:	$Id: tcp_input.c,v 1.116 1998/05/02 14:50:11 davem Exp $
  *
  * Authors:	Ross Biro, <bir7@leland.Stanford.Edu>
  *		Fred N. van Kempen, <waltje@uWalt.NL.Mugnet.ORG>
@@ -421,33 +421,6 @@
 	return 1;
 }
 
-#if 0 /* Not working yet... -DaveM */
-static void tcp_compute_tsack(struct sock *sk, struct tcp_opt *tp)
-{
-	struct sk_buff *skb = skb_peek(&sk->write_queue);
-	__u32 tstamp = tp->rcv_tsecr;
-	int fack_count = 0;
-
-	while((skb != NULL) &&
-	      (skb != tp->send_head) &&
-	      (skb != (struct sk_buff *)&sk->write_queue)) {
-		if(TCP_SKB_CB(skb)->when == tstamp) {
-			__u8 sacked = TCP_SKB_CB(skb)->sacked;
-
-			sacked |= TCPCB_SACKED_ACKED;
-			if(sacked & TCPCB_SACKED_RETRANS)
-				tp->retrans_out--;
-			TCP_SKB_CB(skb)->sacked = sacked;
-		}
-		if(!before(TCP_SKB_CB(skb)->when, tstamp))
-			fack_count++;
-		skb = skb->next;
-	}
-	if(fack_count > tp->fackets_out)
-		tp->fackets_out = fack_count;
-}
-#endif
-
 #define FLAG_DATA		0x01 /* Incoming frame contained data.		*/
 #define FLAG_WIN_UPDATE		0x02 /* Incoming ACK was a window update.	*/
 #define FLAG_DATA_ACKED		0x04 /* This ACK acknowledged new data.		*/
@@ -481,13 +454,6 @@
 	if (ack == tp->snd_una && tp->packets_out && (not_dup == 0)) {
 		/* This is the standard reno style fast retransmit branch. */
 
-#if 0	/* Not working yet... -DaveM */
-		/* If not doing SACK, but doing timestamps, compute timestamp
-		 * based pseudo-SACKs when we see duplicate ACKs.
-		 */
-		if(!tp->sack_ok && tp->saw_tstamp)
-			tcp_compute_tsack(sk, tp);
-#endif
                 /* 1. When the third duplicate ack is received, set ssthresh 
                  * to one half the current congestion window, but no less 
                  * than two segments. Retransmit the missing segment.
@@ -611,6 +577,7 @@
 
 	while((skb=skb_peek(&sk->write_queue)) && (skb != tp->send_head)) {
 		struct tcp_skb_cb *scb = TCP_SKB_CB(skb); 
+		__u8 sacked = scb->sacked;
 		
 		/* If our packet is before the ack sequence we can
 		 * discard it as it's confirmed to have arrived at
@@ -626,22 +593,12 @@
 		 * connection startup slow start one packet too
 		 * quickly.  This is severely frowned upon behavior.
 		 */
+		if(sacked & TCPCB_SACKED_RETRANS && tp->retrans_out)
+			tp->retrans_out--;
 		if(!(scb->flags & TCPCB_FLAG_SYN)) {
-			__u8 sacked = scb->sacked;
-
 			acked |= FLAG_DATA_ACKED;
-			if(sacked & TCPCB_SACKED_RETRANS) {
+			if(sacked & TCPCB_SACKED_RETRANS)
 				acked |= FLAG_RETRANS_DATA_ACKED;
-
-				/* XXX The race is, fast retrans frame -->
-				 * XXX retrans timeout sends older frame -->
-				 * XXX ACK arrives for fast retrans frame -->
-				 * XXX retrans_out goes negative --> splat.
-				 * XXX Please help me find a better way -DaveM
-				 */
-				if(tp->retrans_out)
-					tp->retrans_out--;
-			}
 			if(tp->fackets_out)
 				tp->fackets_out--;
 		} else {
diff -u --recursive --new-file v2.1.99/linux/net/ipv4/tcp_ipv4.c linux/net/ipv4/tcp_ipv4.c
--- v2.1.99/linux/net/ipv4/tcp_ipv4.c	Sat May  2 14:19:55 1998
+++ linux/net/ipv4/tcp_ipv4.c	Sat May  2 14:22:29 1998
@@ -5,7 +5,7 @@
  *
  *		Implementation of the Transmission Control Protocol(TCP).
  *
- * Version:	$Id: tcp_ipv4.c,v 1.142 1998/04/30 12:00:45 davem Exp $
+ * Version:	$Id: tcp_ipv4.c,v 1.145 1998/05/02 12:47:13 davem Exp $
  *
  *		IPv4 specific functions
  *
@@ -48,7 +48,6 @@
 
 #include <linux/config.h>
 #include <linux/types.h>
-#include <linux/stddef.h>
 #include <linux/fcntl.h>
 #include <linux/random.h>
 #include <linux/init.h>
@@ -61,12 +60,15 @@
 #include <asm/segment.h>
 
 #include <linux/inet.h>
+#include <linux/stddef.h>
 
 extern int sysctl_tcp_timestamps;
 extern int sysctl_tcp_window_scaling;
 extern int sysctl_tcp_sack;
 extern int sysctl_tcp_syncookies;
 extern int sysctl_ip_dynaddr;
+extern __u32 sysctl_wmem_max;
+extern __u32 sysctl_rmem_max;
 
 /* Check TCP sequence numbers in ICMP packets. */
 #define ICMP_MIN_LENGTH 8
@@ -166,17 +168,21 @@
 	return tb;
 }
 
+#ifdef CONFIG_IP_TRANSPARENT_PROXY
 /* Ensure that the bound bucket for the port exists.
  * Return 0 on success.
  */
 static __inline__ int tcp_bucket_check(unsigned short snum)
 {
-	if (tcp_bound_hash[tcp_bhashfn(snum)] == NULL &&
-			tcp_bucket_create(snum) == NULL)
+	struct tcp_bind_bucket *tb = tcp_bound_hash[tcp_bhashfn(snum)];
+	for( ; (tb && (tb->port != snum)); tb = tb->next)
+		;
+	if(tb == NULL && tcp_bucket_create(snum) == NULL)
 		return 1;
 	else
 		return 0;
 }
+#endif
 
 static int tcp_v4_verify_bind(struct sock *sk, unsigned short snum)
 {
@@ -215,10 +221,21 @@
 				result = 1;
 		}
 	}
-	if((result == 0) &&
-	   (tb == NULL) &&
-	   (tcp_bucket_create(snum) == NULL))
-		result = 1;
+	if(result == 0) {
+		if(tb == NULL) {
+			if(tcp_bucket_create(snum) == NULL)
+				result = 1;
+		} else {
+			/* It could be pending garbage collection, this
+			 * kills the race and prevents it from disappearing
+			 * out from under us by the time we use it.  -DaveM
+			 */
+			if(tb->owners == NULL && !(tb->flags & TCPB_FLAG_LOCKED)) {
+				tb->flags = TCPB_FLAG_LOCKED;
+				tcp_dec_slow_timer(TCP_SLT_BUCKETGC);
+			}
+		}
+	}
 go_like_smoke:
 	SOCKHASH_UNLOCK();
 	return result;
@@ -1308,6 +1325,11 @@
 	if (!newsk) 
 		goto exit;
 
+	if (newsk->rcvbuf < (3 * newsk->mtu))
+		newsk->rcvbuf = min ((3 * newsk->mtu), sysctl_rmem_max);
+	if (newsk->sndbuf < (3 * newsk->mtu))
+		newsk->sndbuf = min ((3 * newsk->mtu), sysctl_wmem_max);
+ 
 	sk->tp_pinfo.af_tcp.syn_backlog--;
 	sk->ack_backlog++;
 
diff -u --recursive --new-file v2.1.99/linux/net/ipv4/tcp_timer.c linux/net/ipv4/tcp_timer.c
--- v2.1.99/linux/net/ipv4/tcp_timer.c	Sat May  2 14:19:55 1998
+++ linux/net/ipv4/tcp_timer.c	Sat May  2 14:22:29 1998
@@ -5,7 +5,7 @@
  *
  *		Implementation of the Transmission Control Protocol(TCP).
  *
- * Version:	$Id: tcp_timer.c,v 1.50 1998/04/14 09:08:59 davem Exp $
+ * Version:	$Id: tcp_timer.c,v 1.51 1998/05/02 15:19:26 davem Exp $
  *
  * Authors:	Ross Biro, <bir7@leland.Stanford.Edu>
  *		Fred N. van Kempen, <waltje@uWalt.NL.Mugnet.ORG>
@@ -448,26 +448,24 @@
 	 */
 	if(tp->sack_ok) {
 		struct sk_buff *skb = skb_peek(&sk->write_queue);
-		__u8 toclear = TCPCB_SACKED_ACKED;
 
-		if(tp->retransmits == 0)
-			toclear |= TCPCB_SACKED_RETRANS;
 		while((skb != NULL) &&
 		      (skb != tp->send_head) &&
 		      (skb != (struct sk_buff *)&sk->write_queue)) {
-			TCP_SKB_CB(skb)->sacked &= ~(toclear);
+			TCP_SKB_CB(skb)->sacked &=
+				~(TCPCB_SACKED_ACKED | TCPCB_SACKED_RETRANS);
 			skb = skb->next;
 		}
-		tp->fackets_out = 0;
 	}
 
 	/* Retransmission. */
 	tp->retrans_head = NULL;
+	tp->fackets_out = 0;
+	tp->retrans_out = 0;
 	if (tp->retransmits == 0) {
 		/* remember window where we lost
 		 * "one half of the current window but at least 2 segments"
 		 */
-		tp->retrans_out = 0;
 		tp->snd_ssthresh = max(tp->snd_cwnd >> (1 + TCP_CWND_SHIFT), 2);
 		tp->snd_cwnd = (1 << TCP_CWND_SHIFT);
 	}
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/exthdrs.c linux/net/ipv6/exthdrs.c
--- v2.1.99/linux/net/ipv6/exthdrs.c	Tue Mar 17 22:18:16 1998
+++ linux/net/ipv6/exthdrs.c	Sat May  2 14:22:29 1998
@@ -4,8 +4,9 @@
  *
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>
+ *	Andi Kleen		<ak@muc.de>
  *
- *	$Id: exthdrs.c,v 1.5 1998/02/12 07:43:39 davem Exp $
+ *	$Id: exthdrs.c,v 1.6 1998/04/30 16:24:20 freitag Exp $
  *
  *	This program is free software; you can redistribute it and/or
  *      modify it under the terms of the GNU General Public License
@@ -34,6 +35,10 @@
 #include <net/ip6_route.h>
 #include <net/addrconf.h>
 
+#include <asm/uaccess.h>
+
+#define swap(a,b) do { typeof (a) tmp; tmp = (a); (a) = (b); (b) = (tmp); } while(0)
+
 /*
  *	inbound
  */
@@ -135,7 +140,7 @@
  */
 
 int ipv6opt_bld_rthdr(struct sk_buff *skb, struct ipv6_options *opt,
-		      struct in6_addr *addr, int proto)		      
+		      struct in6_addr *addr)		      
 {
 	struct rt0_hdr *phdr, *ihdr;
 	int hops;
@@ -153,8 +158,76 @@
 
 	ipv6_addr_copy(phdr->addr + (hops - 1), addr);
 	
-	phdr->rt_hdr.nexthdr = proto;
-
+	phdr->rt_hdr.nexthdr = proto; 
 	return NEXTHDR_ROUTING;
 }
 #endif
+
+/* 
+ * find out if nexthdr is an extension header or a protocol
+ */
+
+static __inline__ int ipv6_ext_hdr(u8 nexthdr)
+{
+	/* 
+	 * find out if nexthdr is an extension header or a protocol
+	 */
+	return ( (nexthdr == NEXTHDR_HOP)	||
+		 (nexthdr == NEXTHDR_ROUTING)	||
+		 (nexthdr == NEXTHDR_FRAGMENT)	||
+		 (nexthdr == NEXTHDR_ESP)	||
+		 (nexthdr == NEXTHDR_AUTH)	||
+		 (nexthdr == NEXTHDR_NONE)	||
+		 (nexthdr == NEXTHDR_DEST) );
+		 
+}
+
+/*
+ * Skip any extension headers. This is used by the ICMP module.
+ *
+ * Note that strictly speaking this conflicts with RFC1883 4.0:
+ * ...The contents and semantics of each extension header determine whether 
+ * or not to proceed to the next header.  Therefore, extension headers must
+ * be processed strictly in the order they appear in the packet; a
+ * receiver must not, for example, scan through a packet looking for a
+ * particular kind of extension header and process that header prior to
+ * processing all preceding ones.
+ * 
+ * We do exactly this. This is a protocol bug. We can't decide after a
+ * seeing an unknown discard-with-error flavour TLV option if it's a 
+ * ICMP error message or not (errors should never be send in reply to
+ * ICMP error messages).
+ * 
+ * But I see no other way to do this. This might need to be reexamined
+ * when Linux implements ESP (and maybe AUTH) headers.
+ */
+struct ipv6_opt_hdr *ipv6_skip_exthdr(struct ipv6_opt_hdr *hdr, 
+				      u8 *nexthdrp, int len)
+{
+	u8 nexthdr = *nexthdrp;
+
+	while (ipv6_ext_hdr(nexthdr)) {
+		int hdrlen; 
+		
+		if (nexthdr == NEXTHDR_NONE)
+			return NULL;
+		if (len < sizeof(struct ipv6_opt_hdr)) /* be anal today */
+			return NULL;
+
+		hdrlen = ipv6_optlen(hdr); 
+		if (len < hdrlen)
+			return NULL; 
+
+		nexthdr = hdr->nexthdr;
+		hdr = (struct ipv6_opt_hdr *) ((u8*)hdr + hdrlen);
+		len -= hdrlen;
+	}
+
+	/* Hack.. Do the same for AUTH headers? */
+	if (nexthdr == NEXTHDR_ESP) 
+		return NULL; 
+
+	*nexthdrp = nexthdr;
+	return hdr;
+}
+
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/icmp.c linux/net/ipv6/icmp.c
--- v2.1.99/linux/net/ipv6/icmp.c	Thu Mar 26 15:57:13 1998
+++ linux/net/ipv6/icmp.c	Sat May  2 14:22:30 1998
@@ -5,7 +5,7 @@
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>
  *
- *	$Id: icmp.c,v 1.15 1998/03/21 07:28:03 davem Exp $
+ *	$Id: icmp.c,v 1.17 1998/05/01 10:31:41 davem Exp $
  *
  *	Based on net/ipv4/icmp.c
  *
@@ -21,6 +21,8 @@
  *	Changes:
  *
  *	Andi Kleen		:	exception handling
+ *	Andi Kleen			add rate limits. never reply to a icmp.
+ *					add more length checks and other fixes.
  */
 
 #define __NO_VERSION__
@@ -51,6 +53,7 @@
 #include <net/transp_v6.h>
 #include <net/ip6_route.h>
 #include <net/addrconf.h>
+#include <net/icmp.h>
 
 #include <asm/uaccess.h>
 #include <asm/system.h>
@@ -129,6 +132,62 @@
 	return 0; 
 }
 
+
+/* 
+ * Slightly more convenient version of icmpv6_send.
+ */
+void icmpv6_param_prob(struct sk_buff *skb, int code, void *pos)
+{
+	int offset = (u8*)pos - (u8*)skb->nh.ipv6h; 
+	
+	icmpv6_send(skb, ICMPV6_PARAMPROB, code, offset, skb->dev);
+	kfree_skb(skb);
+}
+
+static inline int is_icmp(struct ipv6hdr *hdr, int len)
+{
+	__u8 nexthdr = hdr->nexthdr; 
+
+	if (!ipv6_skip_exthdr((struct ipv6_opt_hdr *)(hdr+1), &nexthdr, len))
+		return 0; 
+	return nexthdr == IPPROTO_ICMP; 
+}
+
+int sysctl_icmpv6_time = 1*HZ; 
+
+/* 
+ * Check the ICMP output rate limit 
+ */
+static inline int icmpv6_xrlim_allow(struct sock *sk, int type,
+				     struct flowi *fl)
+{
+#if 0
+	struct dst_entry *dst; 
+	int allow = 0;
+#endif
+	/* Informational messages are not limited. */
+	if (type & 0x80)
+		return 1; 
+
+#if 0 /* not yet, first fix routing COW */
+
+	/* 
+	 * Look up the output route.
+	 * XXX: perhaps the expire for routing entries cloned by
+	 * this lookup should be more aggressive (not longer than timeout).
+	 */
+	dst = ip6_route_output(sk, fl, 1);
+	if (dst->error) 
+		ipv6_statistics.Ip6OutNoRoutes++;
+	else 
+		allow = xrlim_allow(dst, sysctl_icmpv6_time);
+	dst_release(dst);
+	return allow;
+#else
+	return 1;
+#endif
+}
+
 /*
  *	an inline helper for the "simple" if statement below
  *	checks if parameter problem report is caused by an
@@ -214,6 +273,24 @@
 		return;
 	}
 
+	/* 
+	 *	Never answer to a ICMP packet.
+	 */
+	if (is_icmp(hdr, (u8*)skb->tail - (u8*)hdr)) {
+		printk(KERN_DEBUG "icmpv6_send: no reply to icmp\n"); 
+		return;
+	}
+
+	fl.proto = IPPROTO_ICMPV6;
+	fl.nl_u.ip6_u.daddr = &hdr->saddr;
+	fl.nl_u.ip6_u.saddr = saddr;
+	fl.oif = iif;
+	fl.uli_u.icmpt.type = type;
+	fl.uli_u.icmpt.code = code;
+
+	if (!icmpv6_xrlim_allow(sk, type, &fl)) 
+		return; 
+
 	/*
 	 *	ok. kick it. checksum will be provided by the 
 	 *	getfrag_t callback.
@@ -248,13 +325,6 @@
 
 	msg.len = len;
 
-	fl.proto = IPPROTO_ICMPV6;
-	fl.nl_u.ip6_u.daddr = &hdr->saddr;
-	fl.nl_u.ip6_u.saddr = saddr;
-	fl.oif = iif;
-	fl.uli_u.icmpt.type = type;
-	fl.uli_u.icmpt.code = code;
-
 	ip6_build_xmit(sk, icmpv6_getfrag, &msg, &fl, len, NULL, -1,
 		       MSG_DONTWAIT);
 
@@ -312,21 +382,6 @@
 	dst_release(xchg(&sk->dst_cache, NULL));
 }
 
-static __inline__ int ipv6_ext_hdr(u8 nexthdr)
-{
-	/* 
-	 * find out if nexthdr is an extension header or a protocol
-	 */
-	return ( (nexthdr == NEXTHDR_HOP)	||
-		 (nexthdr == NEXTHDR_ROUTING)	||
-		 (nexthdr == NEXTHDR_FRAGMENT)	||
-		 (nexthdr == NEXTHDR_ESP)	||
-		 (nexthdr == NEXTHDR_AUTH)	||
-		 (nexthdr == NEXTHDR_NONE)	||
-		 (nexthdr == NEXTHDR_DEST) );
-		 
-}
-
 static void icmpv6_notify(struct sk_buff *skb,
 			  int type, int code, unsigned char *buff, int len,
 			  struct in6_addr *saddr, struct in6_addr *daddr, 
@@ -335,39 +390,22 @@
 	struct ipv6hdr *hdr = (struct ipv6hdr *) buff;
 	struct inet6_protocol *ipprot;
 	struct sock *sk;
-	char * pbuff;
+	struct ipv6_opt_hdr *pb;
 	__u32 info = 0;
 	int hash;
 	u8 nexthdr;
 
-	/* now skip over extension headers */
-
 	nexthdr = hdr->nexthdr;
 
-	pbuff = (char *) (hdr + 1);
+	pb = (struct ipv6_opt_hdr *) (hdr + 1);
 	len -= sizeof(struct ipv6hdr);
+	if (len < 0)
+		return;
 
-	while (ipv6_ext_hdr(nexthdr)) {
-		int hdrlen;
-
-		if (nexthdr == NEXTHDR_NONE)
-			return;
-
-		nexthdr = *pbuff;
-
-		/* Header length is size in 8-octet units, not
-		 * including the first 8 octets.
-		 */
-		hdrlen = *(pbuff+1);
-		hdrlen = (hdrlen + 1) << 3;
-
-		if (hdrlen > len)
-			return;
-		
-		/* Now this is right. */
-		pbuff += hdrlen;
-		len -= hdrlen;
-	}
+	/* now skip over extension headers */
+	pb = ipv6_skip_exthdr(pb, &nexthdr, len);
+	if (!pb)
+		return;
 
 	hash = nexthdr & (MAX_INET_PROTOS - 1);
 
@@ -378,7 +416,7 @@
 			continue;
 
 		if (ipprot->err_handler) 
-			ipprot->err_handler(skb, type, code, pbuff, info,
+			ipprot->err_handler(skb, type, code, (u8*)pb, info,
 					    saddr, daddr, ipprot);
 		return;
 	}
@@ -391,7 +429,7 @@
 		return;
 
 	while((sk = raw_v6_lookup(sk, nexthdr, daddr, saddr))) {
-		rawv6_err(sk, type, code, pbuff, saddr, daddr);
+		rawv6_err(sk, type, code, (char*)pb, saddr, daddr);
 		sk = sk->next;
 	}
 }
@@ -514,7 +552,7 @@
 	return 0;
 }
 
-__initfunc(void icmpv6_init(struct net_proto_family *ops))
+__initfunc(int icmpv6_init(struct net_proto_family *ops))
 {
 	struct sock *sk;
 	int err;
@@ -528,11 +566,11 @@
 	icmpv6_socket->state = SS_UNCONNECTED;
 	icmpv6_socket->type=SOCK_RAW;
 
-	if((err=ops->create(icmpv6_socket, IPPROTO_ICMPV6))<0)
+	if((err=ops->create(icmpv6_socket, IPPROTO_ICMPV6))<0) {
 		printk(KERN_DEBUG 
 		       "Failed to create the ICMP6 control socket.\n");
-
-	MOD_DEC_USE_COUNT;
+		return 1;
+	}
 
 	sk = icmpv6_socket->sk;
 	sk->allocation = GFP_ATOMIC;
@@ -542,6 +580,16 @@
 
 	ndisc_init(ops);
 	igmp6_init(ops);
+	return 0; 
+}
+
+void icmpv6_cleanup(void)
+{
+	inet6_del_protocol(&icmpv6_protocol);
+#if 0
+	ndisc_cleanup();
+#endif
+	igmp6_cleanup();
 }
 
 static struct icmp6_err {
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/ip6_input.c linux/net/ipv6/ip6_input.c
--- v2.1.99/linux/net/ipv6/ip6_input.c	Tue Mar 17 22:18:16 1998
+++ linux/net/ipv6/ip6_input.c	Sat May  2 14:22:30 1998
@@ -6,7 +6,7 @@
  *	Pedro Roque		<roque@di.fc.ul.pt>
  *	Ian P. Morris		<I.P.Morris@soton.ac.uk>
  *
- *	$Id: ip6_input.c,v 1.8 1998/02/12 07:43:43 davem Exp $
+ *	$Id: ip6_input.c,v 1.9 1998/04/30 16:24:24 freitag Exp $
  *
  *	Based in linux/net/ipv4/ip_input.c
  *
@@ -69,12 +69,6 @@
 	u8 type;
 	u8 len;
 };
-
-struct ipv6_destopt_hdr {
-	u8 nexthdr;
-	u8 hdrlen;
-};
-
 
 struct tlvtype_proc {
 	u8	type;
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/ipv6_sockglue.c linux/net/ipv6/ipv6_sockglue.c
--- v2.1.99/linux/net/ipv6/ipv6_sockglue.c	Thu Mar 26 15:57:13 1998
+++ linux/net/ipv6/ipv6_sockglue.c	Sat May  2 14:22:30 1998
@@ -7,7 +7,7 @@
  *
  *	Based on linux/net/ipv4/ip_sockglue.c
  *
- *	$Id: ipv6_sockglue.c,v 1.18 1998/03/20 09:12:18 davem Exp $
+ *	$Id: ipv6_sockglue.c,v 1.19 1998/04/30 16:24:26 freitag Exp $
  *
  *	This program is free software; you can redistribute it and/or
  *      modify it under the terms of the GNU General Public License
@@ -242,7 +242,7 @@
 	ipv6_sysctl_unregister();	
 #endif
 	ip6_route_cleanup();
-	ndisc_cleanup();
+	icmpv6_cleanup();
 	addrconf_cleanup();	
 }
 #endif
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/mcast.c linux/net/ipv6/mcast.c
--- v2.1.99/linux/net/ipv6/mcast.c	Thu Mar 26 15:57:13 1998
+++ linux/net/ipv6/mcast.c	Sat May  2 14:22:30 1998
@@ -5,7 +5,7 @@
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>	
  *
- *	$Id: mcast.c,v 1.14 1998/03/20 09:12:18 davem Exp $
+ *	$Id: mcast.c,v 1.15 1998/04/30 16:24:28 freitag Exp $
  *
  *	Based on linux/ipv4/igmp.c and linux/ipv4/ip_sockglue.c 
  *
@@ -619,8 +619,6 @@
 		printk(KERN_DEBUG 
 		       "Failed to create the IGMP6 control socket.\n");
 
-	MOD_DEC_USE_COUNT;
-
 	sk = igmp6_socket->sk;
 	sk->allocation = GFP_ATOMIC;
 	sk->num = 256;			/* Don't receive any data */
@@ -632,3 +630,9 @@
 #endif
 }
 
+void igmp6_cleanup(void)
+{
+#ifdef CONFIG_PROC_FS
+	remove_proc_entry("net/igmp6", 0); 
+#endif
+}
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/ndisc.c linux/net/ipv6/ndisc.c
--- v2.1.99/linux/net/ipv6/ndisc.c	Thu Mar 26 15:57:13 1998
+++ linux/net/ipv6/ndisc.c	Sat May  2 14:22:30 1998
@@ -1152,9 +1152,6 @@
 		printk(KERN_DEBUG 
 		       "Failed to create the NDISC control socket.\n");
 
-	/* Eeeh... What is it? --ANK */
-	MOD_DEC_USE_COUNT;
-
 	sk = ndisc_socket->sk;
 	sk->allocation = GFP_ATOMIC;
 	sk->net_pinfo.af_inet6.hop_limit = 255;
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/reassembly.c linux/net/ipv6/reassembly.c
--- v2.1.99/linux/net/ipv6/reassembly.c	Tue Mar 17 22:18:16 1998
+++ linux/net/ipv6/reassembly.c	Sat May  2 14:22:30 1998
@@ -5,7 +5,7 @@
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>	
  *
- *	$Id: reassembly.c,v 1.9 1998/02/12 07:43:48 davem Exp $
+ *	$Id: reassembly.c,v 1.10 1998/04/30 16:24:32 freitag Exp $
  *
  *	Based on: net/ipv4/ip_fragment.c
  *
@@ -15,6 +15,11 @@
  *      2 of the License, or (at your option) any later version.
  */
 
+/* 
+ *	Fixes:	
+ *	Andi Kleen	Make it work with multiple hosts.
+ *			More RFC compliance.
+ */
 #include <linux/errno.h>
 #include <linux/types.h>
 #include <linux/socket.h>
@@ -39,8 +44,9 @@
 
 static struct frag_queue ipv6_frag_queue = {
 	&ipv6_frag_queue, &ipv6_frag_queue,
-	0, {0}, NULL, NULL,
-	0
+	0, {{{0}}}, {{{0}}},
+	{0}, NULL, NULL,
+	0, 0, NULL
 };
 
 static void			create_frag_entry(struct sk_buff *skb, 
@@ -72,12 +78,11 @@
 	 *	one it's the kmalloc for a struct ipv6_frag.
 	 *	Feel free to try other alternatives...
 	 */
-	reasm_queue(fq, *skb, fhdr);
-
 	if ((fhdr->frag_off & __constant_htons(0x0001)) == 0) {
 		fq->last_in = 1;
 		fq->nhptr = nhptr;
 	}
+	reasm_queue(fq, *skb, fhdr);
 
 	if (fq->last_in) {
 		if ((nh = reasm_frag_1(fq, skb)))
@@ -90,18 +95,27 @@
 	return 0;
 }
 
-int ipv6_reassembly(struct sk_buff **skb, struct device *dev, __u8 *nhptr,
+int ipv6_reassembly(struct sk_buff **skbp, struct device *dev, __u8 *nhptr,
 		    struct ipv6_options *opt)
 {
-	struct frag_hdr *fhdr = (struct frag_hdr *) ((*skb)->h.raw);
+	struct sk_buff *skb = *skbp; 
+	struct frag_hdr *fhdr = (struct frag_hdr *) (skb->h.raw);
 	struct frag_queue *fq;
-	
+	struct ipv6hdr *hdr;
+
+	if ((u8 *)(fhdr+1) > skb->tail) {
+		icmpv6_param_prob(skb, ICMPV6_HDR_FIELD, skb->h.raw);
+		return 0;
+	}
+	hdr = skb->nh.ipv6h;
 	for (fq = ipv6_frag_queue.next; fq != &ipv6_frag_queue; fq = fq->next) {
-		if (fq->id == fhdr->identification)
-			return reasm_frag(fq, skb, nhptr,fhdr);
+		if (fq->id == fhdr->identification && 
+		    !ipv6_addr_cmp(&hdr->saddr, &fq->saddr) &&
+		    !ipv6_addr_cmp(&hdr->daddr, &fq->daddr))
+			return reasm_frag(fq, skbp, nhptr,fhdr);
 	}
 	
-	create_frag_entry(*skb, dev, nhptr, fhdr);
+	create_frag_entry(skb, dev, nhptr, fhdr);
 
 	return 0;
 }
@@ -154,6 +168,7 @@
 			      struct frag_hdr *fhdr)
 {
 	struct frag_queue *fq;
+	struct ipv6hdr *hdr; 
 
 	fq = (struct frag_queue *) kmalloc(sizeof(struct frag_queue), 
 					   GFP_ATOMIC);
@@ -167,6 +182,10 @@
 
 	fq->id = fhdr->identification;
 
+	hdr = skb->nh.ipv6h;
+	ipv6_addr_copy(&fq->saddr, &hdr->saddr);
+	ipv6_addr_copy(&fq->daddr, &hdr->daddr);
+
 	fq->dev = dev;
 
 	/* init_timer has been done by the memset */
@@ -193,14 +212,14 @@
 
 
 static void reasm_queue(struct frag_queue *fq, struct sk_buff *skb, 
-			struct frag_hdr *fhdr)
+				     struct frag_hdr *fhdr)
 {
 	struct ipv6_frag *nfp, *fp, **bptr;
 
 	nfp = (struct ipv6_frag *) kmalloc(sizeof(struct ipv6_frag), 
 					   GFP_ATOMIC);
 
-	if (nfp == NULL) {
+	if (nfp == NULL) {		
 		kfree_skb(skb);
 		return;
 	}
@@ -209,6 +228,10 @@
 	nfp->len = (ntohs(skb->nh.ipv6h->payload_len) -
 		    ((u8 *) (fhdr + 1) - (u8 *) (skb->nh.ipv6h + 1)));
 
+	if ((u32)nfp->offset + (u32)nfp->len > 65536) {
+		icmpv6_param_prob(skb,ICMPV6_HDR_FIELD, (u8*)&fhdr->frag_off); 
+		goto err;
+	}
 
 	nfp->skb  = skb;
 	nfp->fhdr = fhdr;
@@ -224,19 +247,37 @@
 	}
 	
 	if (fp && fp->offset == nfp->offset) {
-		if (fp->len != nfp->len) {
-			/* this cannot happen */
+		if (nfp->len != fp->len) {
 			printk(KERN_DEBUG "reasm_queue: dup with wrong len\n");
 		}
 
 		/* duplicate. discard it. */
-		kfree_skb(skb);
-		kfree(nfp);
-		return;
+		goto err;
 	}
 	
 	*bptr = nfp;
 	nfp->next = fp;
+
+#ifdef STRICT_RFC
+	if (fhdr->frag_off & __constant_htons(0x0001)) {
+		/* Check if the fragment is rounded to 8 bytes.
+		 * Required by the RFC.
+		 */
+		if (nfp->len & 0x7) {
+			printk(KERN_DEBUG "fragment not rounded to 8bytes\n");
+
+			icmpv6_param_prob(skb, ICMPV6_HDR_FIELD, 
+					  &skb->nh.ipv6h->payload_len);
+			goto err;
+		}
+	}
+#endif 
+
+	return;
+
+err:
+	kfree(nfp);
+	kfree_skb(skb);
 }
 
 /*
@@ -303,6 +344,8 @@
 	/*
 	 *	FIXME: If we don't have a checksum we ought to be able
 	 *	to defragment and checksum in this pass. [AC]
+	 *	Note that we don't really know yet whether the protocol
+	 *	needs checksums at all. It might still be a good idea. -AK
 	 */
 	for(fp = fq->fragments; fp; ) {
 		struct ipv6_frag *back;
diff -u --recursive --new-file v2.1.99/linux/net/ipv6/tcp_ipv6.c linux/net/ipv6/tcp_ipv6.c
--- v2.1.99/linux/net/ipv6/tcp_ipv6.c	Sat May  2 14:19:55 1998
+++ linux/net/ipv6/tcp_ipv6.c	Sat May  2 14:22:30 1998
@@ -5,7 +5,7 @@
  *	Authors:
  *	Pedro Roque		<roque@di.fc.ul.pt>	
  *
- *	$Id: tcp_ipv6.c,v 1.78 1998/04/16 16:29:22 freitag Exp $
+ *	$Id: tcp_ipv6.c,v 1.80 1998/05/02 12:47:15 davem Exp $
  *
  *	Based on: 
  *	linux/net/ipv4/tcp.c
@@ -123,10 +123,21 @@
 				result = 1;
 		}
 	}
-	if((result == 0) &&
-	   (tb == NULL) &&
-	   (tcp_bucket_create(snum) == NULL))
-		result = 1;
+	if(result == 0) {
+		if(tb == NULL) {
+			if(tcp_bucket_create(snum) == NULL)
+				result = 1;
+		} else {
+			/* It could be pending garbage collection, this
+			 * kills the race and prevents it from disappearing
+			 * out from under us by the time we use it.  -DaveM
+			 */
+			if(tb->owners == NULL && !(tb->flags & TCPB_FLAG_LOCKED)) {
+				tb->flags = TCPB_FLAG_LOCKED;
+				tcp_dec_slow_timer(TCP_SLT_BUCKETGC);
+			}
+		}
+	}
 go_like_smoke:
 	SOCKHASH_UNLOCK();
 	return result;
@@ -731,7 +742,7 @@
 		isn = tcp_v6_init_sequence(sk,skb);
 
 	/*
-	 *	There are no SYN attacks on IPv6, yet...
+	 *	There are no SYN attacks on IPv6, yet...	
 	 */
 	if (BACKLOG(sk) >= BACKLOGMAX(sk)) {
 		printk(KERN_DEBUG "droping syn ack:%d max:%d\n",
diff -u --recursive --new-file v2.1.99/linux/net/netsyms.c linux/net/netsyms.c
--- v2.1.99/linux/net/netsyms.c	Sat May  2 14:19:55 1998
+++ linux/net/netsyms.c	Sat May  2 14:22:30 1998
@@ -458,7 +458,7 @@
 EXPORT_SYMBOL(qdisc_new_estimator);
 EXPORT_SYMBOL(qdisc_kill_estimator);
 #endif
-#ifdef CONFIG_NET_POLICE
+#ifdef CONFIG_NET_CLS_POLICE
 EXPORT_SYMBOL(tcf_police);
 EXPORT_SYMBOL(tcf_police_locate);
 EXPORT_SYMBOL(tcf_police_destroy);
diff -u --recursive --new-file v2.1.99/linux/scripts/Configure linux/scripts/Configure
--- v2.1.99/linux/scripts/Configure	Tue Apr 14 14:29:27 1998
+++ linux/scripts/Configure	Sun May  3 17:52:06 1998
@@ -53,10 +53,6 @@
 #
 # 090398 Axel Boldt (boldt@math.ucsb.edu) - allow for empty lines in help
 # texts.
-#
-# 100498 Riley Williams (rhw@bigfoot.com) - added ability to display
-# blank lines in help texts: Any line consisting only of a single dot
-# will be displayed blank.
 
 #
 # Make sure we're really running bash.
@@ -107,7 +103,7 @@
      then
 	  echo; echo "  Sorry, no help available for this option yet.";echo
      else
-	  (echo; echo "$text") | sed 's/^\.$//' | ${PAGER:-more}
+	  (echo; echo "$text") | ${PAGER:-more}
      fi
   else
      echo;
diff -u --recursive --new-file v2.1.99/linux/scripts/Menuconfig linux/scripts/Menuconfig
--- v2.1.99/linux/scripts/Menuconfig	Tue Apr 14 14:29:27 1998
+++ linux/scripts/Menuconfig	Sun May  3 17:52:06 1998
@@ -47,13 +47,6 @@
 #
 # 090398 Axel Boldt (boldt@math.ucsb.edu) - allow for empty lines in help
 # texts.
-#----------------------------------------------------------------------------
-#
-# 10 Apr 1998 - Added ability to display blank lines in help text: Any line
-#               which only contains a single dot will be displayed blank.
-#               Author: Riley Williams <rhw@bigfoot.com>
-#
-#----------------------------------------------------------------------------
 
 
 #
@@ -301,7 +294,7 @@
           echo "There is no help available for this kernel option."
 	  return 1
      else
-	  echo "$text" | sed 's/^\.$//'
+	  echo "$text"
      fi
   else
 	 echo "There is no help available for this kernel option."