# LAST EDIT: Mon Dec 04 by Roman Hodek (Roman.Hodek@informatik.uni-erlangen.de)
#
# This version of the Linux/68k kernel configuration help texts
# corresponds to the kernel versions 1.2.13pl4.
#
# Information about what a kernel is, what it does, how to patch and
# compile it and much more is contained in the Kernel-HOWTO, available
# via anonymous ftp from sunsite.unc.edu in the directory
# /pub/Linux/docs/HOWTO. 
#
# Format: description<nl>variable<nl>helptext<nl><nl>. The help texts
# must not contain empty lines. No variable should occur twice; if it
# does, only the first occurance will be used by Configure. The lines
# in a help text should be indented two positions. Lines starting with
# `#' are ignored. Use emacs' kfill.el to edit this file or you lose.
#
# 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 by Axel Boldt and governed by our beloved little Copyleft
# virus, the GNU Public License. This essentially means that you can
# do with them whatever you want unless you try to restrict someone
# else's right to do whatever they want.
#
# Send comments to Axel Boldt <boldt@math.ucsb.edu> (mainstream
# version) or Roman.Hodek@informatik.uni-erlangen.de (m68k version)

Amiga support
CONFIG_AMIGA
  Include for Amiga machines with an 680x0.
  You may select more than one machine type, the resulting kernel will
  run on all choosen machines. That's called a "generic kernel", but
  these are much bigger in general than machine specific kernels.

Atari support
CONFIG_ATARI
  Include for Atari machines or compatibles with an 680x0.
  You may select more than one machine type, the resulting kernel will
  run on all choosen machines. That's called a "generic kernel", but
  these are much bigger in general than machine specific kernels.

Macintosh support
CONFIG_MAC
  Include for Apple Macintosh machines with an 680x0. Sorry, Macs
  aren't supported yet!

68040 floating point software package
CONFIG_FPSP_040
#####
##### ToDo
#####

Floppy support
CONFIG_BLK_DEV_FD
  If you want to use your floppy disk drive(s) under Linux, say
  Y. Saying N makes usually sense only if you want to keep users from
  using a disk drive.

Amiga Gayle IDE harddisk support
CONFIG_AMIGA_IDE
#####
##### ToDo
#####

Amiga AutoConfig Identification
CONFIG_ZORRO
  Say Y if you want to identify all found AutoConfig (Zorro) Expansion
  Devices at boot time. This device list is also accessible with
  "cat /proc/zorro", so you want to say Y to the /proc filesystem below,
  if you say Y here.

Atari Falcon IDE harddisk support
CONFIG_ATARI_FALCON_IDE
  Say Y for support of the IDE interface of the Falcon or some
  compatible IDE port (e.g. Medusa, TOS-Card)

Atari ACSI support
CONFIG_ATARI_ACSI
  Say Y for support of the Atari ACSI bus. This includes currently
  disks and CD-ROMs. Tapes seem to work occasionally.

Probe all LUNs on each ACSI device
CONFIG_ACSI_MULTI_LUN
  If you have an ACSI device that supports more than one LUN (Logical
  Unit Number), e.g. a CD jukebox, you should say Y here so that all
  will be found by the ACSI driver. An ACSI device with multiple LUNs
  acts logically like multiple devices. The vast majority of ACSI/SCSI
  devices have only one LUN, and so most people can say N here.

Atari SLM laser printer support
CONFIG_ATARI_SLM
  Y to include a driver for the Atari SLM laser printer. ACSI support
  is also required, since the SLM uses the ACSI driver's bus
  primitives. The driver currently allocates a static buffer of 1 MB,
  even if no printer is detected (this is to go away in future). So
  don't include it if you don't need it, else you'll waste a
  non-neglectible amount of memory.

Atari DMA sound support
CONFIG_ATARI_DMA_SOUND
  Include support for the Atari DMA sound shifter in the TT/MegaSTE or
  in the Falcon.

Networking support
CONFIG_NET
  Unless you really know what you are doing, you should say Y
  here. The reason is that some programs need it even if you configure
  a stand-alone machine that won't be connected to any other computer.
  If you have recently upgraded from an older kernel, you should
  consider updating your networking tools too; read net/README for
  details. 

System V IPC
CONFIG_SYSVIPC
  InterProcessCommunication 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 enable this. You can find
  documentation about IPC in ipc.info, which is contained in
  sunsite.unc.edu:/pub/Linux/docs/man/info.tar.gz (available via ftp,
  user: anonymous; 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"). Enabling this option enlarges your kernel by about
  7kB. Just say Y.

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
  enlarge it by about 2kB. ELF support under Linux is quickly
  replacing the traditional Linux a.out format 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 http://sable.ox.ac.uk/~jo95004/elf.html
  (To browse the WWW, you need to have access to a machine on the
  Internet that has one of the programs lynx, netscape or Mosaic).  If
  you find that after upgrading to Linux kernel 1.3 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
  (available via ftp (user: anonymous) from
  tsx-11.mit.edu:/pub/linux/packages/GCC). Also note that ELF binary
  support was broken in kernel versions 1.3.0 - 1.3.2. Either use a
  newer 1.3 kernel or one of the stable 1.2 versions. 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.

Compile kernel as ELF - if your GCC is ELF-GCC
CONFIG_KERNEL_ELF
  The gcc version 2.7.0 and newer produces the new ELF binary format
  as default. If you have such a compiler (try "gcc -v"), say Y
  here, otherwise N.
  It is possible, albeit almost pointless, to compile the kernel in
  a.out format even if your compiler produces ELF as default. For
  that, you would have to say N here and change the variables LD and
  CC in the toplevel Makefile. Similarly, if your compiler produces
  a.out by default but is able to produce ELF, you can compile the
  kernel in ELF by saying Y here and editing the variables CC
  and LD in the toplevel Makefile.

Set version information on all symbols for modules
CONFIG_MODVERSIONS
  Kernel modules are pieces of code which can be inserted in or
  removed from the running kernel, using the programs insmod and
  rmmod. This is described in the file
  Documentation/modules.txt. Usually, modules have to be recompiled
  whenever you switch to a new kernel. Enabling this option allows you
  to keep using the same modules even after compiling a new kernel;
  this requires the program modprobe. All the software needed for
  module support is in the modules package in
  sunsite.unc.edu:/pub/Linux/kernel, available via ftp (user:
  anonymous). NOTE1: if you say Y here but don't have the program
  genksyms (which is also contained in the above mentioned modules
  package), then the building of your kernel will fail. NOTE2: if you
  say Y here, then you cannot say Y to the PPP driver, below; the only
  option is to compile it as a module (PPP is a protocol for sending
  internet traffic over telephone lines). Therefore, N is a safe bet.

TCP/IP networking
CONFIG_INET
  These are the protocols used on the Internet and on most local
  Ethernets. The safest is to say Y here (which will enlarge your
  kernel by about 35 kB), since some programs (e.g. the X window
  system) use TCP/IP even if your machine is not connected to any
  other computer. You will get the so-called loopback device which
  allows you to ping yourself (great fun, that!). This option is also
  necessary if you want to use the full power of 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 the Term-HOWTO, available via ftp (user: anonymous)
  on sunsite.unc.edu:/pub/Linux/docs/HOWTO).  Short answer:
  say Y.

IP: forwarding/gatewaying
CONFIG_IP_FORWARD
  People who want to use their Linux box as the router for a local
  network (i.e. the computer responsible for distributing Internet
  traffic to and from the machines in the local network and the
  subnetworks) should say Y here (thereby enlarging their kernel by
  about 5 kB). Note that in this case, you possibly have two ethernet
  devices in your computer: one for the "outside world" and one for
  your local net. The kernel is not able to recognize both at boot
  time without help; for details read the
  Multiple-Ethernet-mini-HOWTO, available via ftp (user: anonymous) in
  sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini.  If your box is
  connected to two networks, it may still make sense to say N here,
  namely if you want to turn your box into a firewall protecting a
  local network from the internet. The Firewall-HOWTO tells you how to
  do this. If your setup is more complex, say you are connected to
  three networks and you want to act as a firewall between two of them
  and route traffic for the others, you need to say Y here and enable
  IP firewalling below. If you intend to use IP masquerading (i.e. IP
  traffic from one of the local computers and destined for an outside
  host is changed by your box so that it appears to come from you),
  you'll have to say Y here and also to IP firewalling and IP
  masquerading below. You should say Y here also if you want to
  configure your box as a SLIP (the protocol for sending internet
  traffic over telephone lines) or PPP (a better SLIP) server for
  other people to dial into and your box is connected to a local
  network at the same time. You would then most likely use proxy-ARP
  (Address Resolution Protocol), explained in the Proxy-Arp mini howto
  on sunsite in /pub/Linux/docs/HOWTO/mini. If unsure, say N.

IP: multicasting
CONFIG_IP_MULTICAST
  This is code for addressing several networked computers at once,
  enlarging your kernel by about 2 kB. Some versions of gated, the
  program which constantly updates a networked computer's routing
  tables, require that this option be compiled in. You also need
  multicasting if you intend to participate in the MBONE, a high
  bandwidth network on top of the internet which carries audio and
  video broadcasts. Information about the multicast capabilities of
  the various network cards is contained in
  drivers/net/README.multicast. For most people, it's safe to say N.

IP: firewalling
CONFIG_IP_FIREWALL
  A firewall is a computer which protects a local network from the
  rest of the internet: all traffic to and from computers on the local
  net is inspected by the firewall first. If you want to enlarge your
  kernel by about 2kB and configure your Linux box as a firewall for a
  local network, say Y here. You will need to read the FIREWALL-HOWTO,
  available via ftp (user: anonymous) in
  sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also, you will have to use
  the ipfw tool from the net-tools package, available via ftp (user:
  anonymous) from
  ftp.linux.org.uk:/pub/linux/Networking/PROGRAMS/NetTools. It allows
  selective blocking of internet traffic based on type, origin and
  destination.  You need to enable IP firewalling in order to be able
  to use IP masquerading (i.e. IP traffic from one of the local
  computers and destined for an outside host is changed by your box so
  that it appears to come from you). Chances are that you don't want
  this, so say N.

IP: accounting
CONFIG_IP_ACCT
  This keeps track of your IP network traffic and produces some
  statistics. Usually, you only want to say Y here if your box will be
  a router or a firewall for some local network, in which case you
  naturally should have said Y to IP forwarding/gatewaying resp. IP
  firewalling. The data is accessible with "cat /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
  ipfw from the net-tools package, available via ftp (user:
  anonymous) from
  ftp.linux.org.uk:/pub/Linux/Networking/PROGRAMS/NetTools.  Also, you
  might want to have a look at the net-acct package, available via ftp
  (user: anonymous) from
  sunsite.unc.edu:/pub/Linux/system/Network/management. Most people
  say N, however.

PC/TCP compatibility mode
CONFIG_INET_PCTCP
  If you have been having difficulties telneting to your Linux machine
  from a DOS system that uses (broken) PC/TCP networking software, try
  enabling this option.  Everyone else says N.

Reverse ARP
CONFIG_INET_RARP
  Since you asked: if there are diskless machines on your network that
  know their hardware ethernet address but don't know their IP
  addresses upon startup, they send out a Reverse
  AddressResolutionProtocol request to find out their own IP
  addresses. If you want your Linux box to be able to *answer* such
  requests, say Y here; you'd use the program rarp ("man rarp"). 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.  If you don't understand a
  word, say N and rest in peace.

Assume subnets are local
CONFIG_INET_SNARL
  Say Y if you are on a subnetted network with all machines connected
  by Ethernet segments only, as this option optimizes network access
  for this special case. If there are other connections, e.g. SLIP
  links, between machines of your IP network, say N.  If in doubt, say
  Y.

Disable NAGLE algorithm (normally enabled)
CONFIG_TCP_NAGLE_OFF
  The NAGLE algorithm works by requiring an acknowledgment before
  sending small IP frames (= packets).  This keeps tiny packets from
  telnet and rlogin from congesting Wide Area Networks.  You may wish
  to disable it if you run your X-server from across the network, or
  if multiple byte key sequences are delayed. Most people strongly
  recommend to say N here, though, thereby leaving NAGLE enabled.

The IPX protocol
CONFIG_IPX
  This is support for the Novell networking protocol. You need it if
  you want to access Novell Netware servers from within the Linux DOS
  emulator dosemu (read the DOSEMU-HOWTO, available via ftp (user:
  anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO). It's very
  limited and won't make your Linux box into a Novell server. It would
  enlarge your kernel by about 5 kB. 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 one of the
  programs lynx, netscape or Mosaic). Unless you have Novell computers
  on your local network, say N.

Amateur Radio AX.25 Level 2
CONFIG_AX25
  This is the protocol used for computer communication over amateur
  radio. It is either used by itself for point-to-point links, or to
  carry other protocols such as tcp/ip. To use it, you need a device
  that connects your Linux box to your amateur radio. You can either
  use a low speed TNC (a Terminal Node Controller acts as a kind of
  modem connecting your computer's serial port to your radio's
  microphone input and speaker output) supporting the KISS protocol or
  the much faster Ottawa PI card (to enable support for this card,
  you'll have to answer Y to the question about ALPHA test drivers,
  below) or the Z8530 SCC cards; the latter two require an additional
  radio modem.  In order to use AX.25, you need to get a set of
  supporting software tools via ftp (user: anonymous) from
  sunacm.swan.ac.uk:/pub/misc/Linux/Radio/. 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
  HAM-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
  source. More information about digital amateur radio in general is
  on the WWW at
  http://www.cis.ohio-state.edu/hypertext/faq/usenet/radio/ham-radio/digital-faq/faq.html
  (To browse the WWW, you need to have access to a machine on the
  Internet that has one of the programs lynx, netscape or
  Mosaic). AX.25 support is actively being developed, so it's best to
  get the very latest 1.3 kernel if you intend to use this.

SCSI support?
CONFIG_SCSI
  If you want to use an SCSI harddisk, SCSI tapedrive, SCSI CDROM or
  any other SCSI device under Linux, say Y and make sure that you know
  the name of your SCSI host adaptor (the card inside your computer
  that "speaks" the SCSI protocol), because you will be asked for
  it. And 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). If you want to compile it as a
  module, say M here and read Documentation/modules.txt.

SCSI disk support
CONFIG_BLK_DEV_SD
  If you want to use an SCSI harddisk under Linux, say Y and read the
  SCSI-HOWTO, 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). If you want to compile it as a module, say M here and read
  Documentation/modules.txt.
  
SCSI tape support
CONFIG_CHR_DEV_ST
  If you want to use an 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). If you want to compile
  it as a module, say M here and read Documentation/modules.txt.

SCSI CDROM support
CONFIG_BLK_DEV_SR
  If you want to use an 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 enable the
  ISO9660 filesystem later. 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.

SCSI generic support
CONFIG_CHR_DEV_SG
  If you want to use SCSI scanners, synthesizers or CD-writers or just
  about anything having "SCSI" in its name, say Y here. Those won't be
  supported by the kernel directly, so you need some additional
  software which knows how to talk to these things using the SCSI
  protocol. Chances are that you'll have to write that 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.

Probe all LUNs on each SCSI device
CONFIG_SCSI_MULTI_LUN
  If you have an SCSI device that supports more than one LUN (Logical
  Unit Number), e.g. a CD jukebox, you should say Y here so that all
  will be found by the SCSI driver. An SCSI device with multiple LUNs
  acts logically like multiple SCSI devices. The vast majority of SCSI
  devices have only one LUN, and so most people can say N here.

A3000 WD33C93A support
CONFIG_A3000_SCSI
#####
##### ToDo
#####

A2091 WD33C93A support
CONFIG_A2091_SCSI
#####
##### ToDo
#####

GVP Series II WD33C93A support
CONFIG_GVP11_SCSI
#####
##### ToDo
#####

Atari native SCSI support
CONFIG_ATARI_SCSI
  Y here will include the driver for the built-in SCSI host adaptor of
  Ataris. There are two flavors of this: TT style (also e.g. in the
  Medusa) and Falcon style. There is only one driver for this two
  versions, the differences are handled at run-time.

Use longer delay for Toshiba CD-ROMs
CONFIG_ATARI_SCSI_TOSHIBA_DELAY
  The Toshiba CD-ROMs have been proven to need a longer delay in a
  certain place of the SCSI protocol (15us instead of 2us). Saying Y
  here makes the Atari SCSI driver use the longer delay. This won't
  affect any other SCSI devices, but may hurt performance a little
  bit. So say N if you don't have a Toshiba CD-ROM attached. If
  somehow in doubt, say Y, it doesn't break anything.

Verbose SCSI error reporting (kernel size +=12K)
CONFIG_SCSI_CONSTANTS
  The error messages regarding your SCSI hardware will be easier to
  understand if you enable this; it will enlarge your kernel by about
  12KB. If in doubt, say Y.

Network device support?
CONFIG_NETDEVICES
  You can say N here in case you don't intend to connect to any other
  computer at all or 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
  the Term-HOWTO).  You'll have to say Y if your computer contains a
  network card that you want to use under linux (make sure you know
  its name because you will be asked for it and read the
  Ethernet-HOWTO; also, if you plan to use more than one network card
  under linux, read the Multiple-Ethernet-mini-HOWTO, available from
  sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to use
  SLIP (Serial Line Internet Protocol is the protocol used to send
  Internet traffic over telephone lines or nullmodem cables) or CSLIP
  (compressed SLIP) or PPP (better and newer variant of SLIP) or PLIP
  (Parallel Line Internet Protocol is mainly used to create a mini
  network by connecting the parallel ports of two local machines) or
  AX.25/KISS (protocol for sending internet traffic over radio links).
  Make sure to read the NET-2-HOWTO.  Eventually, you will have to
  read Olaf Kirch's excellent book "Network Administrator's Guide", to
  be found in sunsite.unc.edu:/pub/Linux/docs/LDP.  If unsure, say Y.

Dummy net driver support
CONFIG_DUMMY
  This is essentially a loopback device (i.e. traffic you send to this
  device is immediately returned back to you) with a configurable IP
  address different from the usual 127.0.0.1. Can be used to give you
  more than one IP address or make your currently inactive SLIP
  address seem like a real address. If you use SLIP or PPP, you might
  want to enable it. 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 comes often
  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.
  
SLIP (serial line) support
CONFIG_SLIP
  Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
  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
  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 the Term-HOWTO). SLIP support
  will enlarge your kernel by about 4kB. If unsure, say N.  If you
  want to compile this as a module ( = code which can be inserted in
  and removed from the running kernel whenever you want), say M here
  and read Documentation/modules.txt as well as
  Documentation/networking/net-modules.txt.
  
CSLIP compressed headers
CONFIG_SLIP_COMPRESSED
  This protocol is faster than SLIP because it uses compression on the
  TCP/IP headers (not on the data itself), but it has to be supported
  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.

16 channels instead of 4 
CONFIG_SLIP_LOTS
  Saying Y here will allow you to have up to 16 SLIP connections
  running in parallel. This is mainly useful if you intend your linux
  box to act as a dial-in SLIP server. Most people can say N.

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
  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. 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
  the Term-HOWTO). 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 only
  compile it as a module. 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 unsure, say N.

16 channels instead of 4 
CONFIG_PPP_LOTS
  Saying Y here will allow you to have up to 16 PPP connections
  running in parallel. This is mainly useful if you intend your linux
  box to act as a dial-in PPP server. Most people can say N.

Ariadne support
CONFIG_ARIADNE
  Y includes support for the Village Tronic Ariadne Ethernet board for
  the Amiga.

A2065 support
CONFIG_A2065
  Y includes support for the Commodore/Ameristar A2065 Ethernet board
  for the Amiga.

Hydra support
CONFIG_HYDRA
  Y includes support for the Hydra Systems Amiganet Ethernet board for
  the Amiga.

Atari Lance support
CONFIG_ATARILANCE
  Y includes support for Lance-based Ethernet boards in the Atari.
  These are: the RieblCard in a TT or MegaSTE (via VME bus) or in an
  older ST (over the MegaBus), and the PAM internal boards (also VME).

Standard (minix) fs support
CONFIG_MINIX_FS
  Minix is a simple operating system used in many classes about
  OS's. The minix filesystem (= method to organize files on a harddisk
  partition or a floppy disk) was the original filesystem for Linux,
  has been superseded by the second extended filesystem ext2fs but is
  still used for root/boot and other floppies or ram disks since it is
  leaner. You don't want to use it on your harddisk because of certain
  built-in restrictions. This option will enlarge your kernel by about
  25 kB. Everyone should say Y so that they are able to read this
  common floppy format.  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. Note that the filesystem of your root
  partition cannot be compiled as a module.

Second extended fs support
CONFIG_EXT2_FS
  This is the de facto standard Linux filesystem (= method to organize
  files on a storage device) for harddisks. You want to say Y, unless
  you intend to use Linux exclusively from inside a DOS partition
  using the umsdos filesystem. The advantage of the latter is that you
  can get away without repartitioning your hard drive (which often
  implies backing everything up and restoring afterwards); the
  disadvantage is that Linux becomes susceptible to DOS viruses and
  that umsdos is somewhat slower than ext2fs. Even if you want to run
  Linux in this fashion, it might be a good idea to have ext2fs
  around: it enables you to read more floppy disks and facilitates the
  transition to a *real* Linux partition later. Another (rare) case
  which doesn't require ext2fs is a diskless Linux box which mounts
  all files over the network using NFS (in this case it's sufficient
  to enable NFS filesystem support below; if you are planning to do
  this, have a look at the package
  /pub/Linux/system/Linux-boot/netboot-nfs.tar.gz, available via ftp
  (user: anonymous) from sunsite.unc.edu, extract with "tar xzvf
  filename"). 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. Default is Y.

msdos fs support
CONFIG_MSDOS_FS
  This allows you to mount MSDOS partitions of your harddrive (unless
  they are compressed; the only way to access compressed MSDOS
  partitions under Linux is with the DOS emulator DOSEMU, described in
  the DOSEMU-HOWTO, available via ftp (user: anonymous) at
  sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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 here. This option will enlarge your kernel by
  about 25 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. Note that the filesystem of your root
  partition cannot be a module.

umsdos: Unix like fs on top of std MSDOS FAT fs
CONFIG_UMSDOS_FS
  Say Y here if you want to run Linux from within an existing DOS
  partition of your harddrive. The advantage of this is that you can
  get away without repartitioning your hard drive (which often implies
  backing everything up and restoring afterwards) and hence you're
  able to quickly try out Linux or show it to your friends; the
  disadvantage is that Linux becomes susceptible to DOS viruses and
  that UMSDOS is somewhat slower than ext2fs.  Another use of umsdos
  is to write files with long unix filenames to MSDOS floppies; it
  also allows unix style 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. 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. Note that the filesystem of
  your root partition cannot be a module.

/proc filesystem support
CONFIG_PROC_FS
  This is a virtual filesystem providing information about the status
  of the system. "Virtual" means that it doesn't take any space on
  your harddisk: the files are created on the fly when you access
  them. Also, you cannot read the files with less or more: you need to
  use cat. The filesystem is explained in the Kernel Hacker's Guide,
  available via ftp (user: anonymous) in
  sunsite.unc.edu:/pub/Linux/docs/LDP.  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 periphery to
  gain the CPU's attention - often a source of trouble if two devices
  are mistakenly configured to use the same IRQ). Several programs
  depend on this, so everyone should say Y here.
  
NFS filesystem support
CONFIG_NFS_FS
  If you are connected to a network (using SLIP, PPP or ethernet, not
  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 the Term-HOWTO, available via
  ftp (user: anonymous) on sunsite.unc.edu:/pub/Linux/docs/HOWTO]) and
  want to mount files residing on another UNIX computer (the NFS
  server) using the NetworkFileSharing protocol, say Y. "Mounting
  files" means that the client can access the files with usual UNIX
  commands as if they were sitting on the client's harddisk. 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, and on its man
  page: "man nfs". There is also a NFS-FAQ in
  sunsite.unc.edu:/pub/Linux/docs/faqs which presumes that you know
  the basics of NFS already. 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). If you want to compile it as a module, say M
  here and read Documentation/modules.txt. If you don't know what all
  this is about, say N.

ISO9660 cdrom filesystem support
CONFIG_ISO9660_FS
  If you have a CDROM and want to do more with it than just listen to
  audio CDs and watch its LEDs, say Y (and read the CDROM-HOWTO,
  available via ftp (user: anonymous) from
  sunsite.unc.edu:/pub/Linux/docs/HOWTO), thereby enlarging your
  kernel by about 27 kB; otherwise say N.  If you want to compile this
  as a module ( = code which can be inserted in and removed from the
  running kernel whenever you want), say M here and read
  Documentation/modules.txt.

Amiga FFS filesystem support
CONFIG_AFFS_FS
#####
##### ToDo
#####

Parallel printer support
CONFIG_PRINTER
  If you intend to attach a printer to the parallel port of your Linux
  box (as opposed to using a serial printer; if the connector at the
  printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
  read the Printing-HOWTO, available 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. If you intend to use PLIP (Parallel Line
  Internet Protocol is mainly used to create a mini network by
  connecting the parallel ports of two local machines) and a parallel
  printer, you should compile both as modules because the drivers
  don't like each other.

Amiga mouse support
CONFIG_AMIGAMOUSE
  Y includes support for the Amiga mouse (attached to the mouse port 1).
  The Amiga mouse acts as a bus mouse device.

GVP IO-Extender support
CONFIG_GVPIOEXT
#####
##### ToDo
#####

Atari mouse support
CONFIG_ATARIMOUSE
  Y includes support for the Atari mouse (attached to the keyboard).
  The Atari mouse acts as a bus mouse device.

Kernel profiling support
CONFIG_PROFILE
  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 (enable the /proc filesystem!) 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, available via ftp (user: anonymous) from
  sunsite.unc.edu:/pub/Linux/docs/LDP. Mere mortals say N.
 
Profile shift count
CONFIG_PROFILE_SHIFT
  This is used to adjust the granularity with which the addresses of
  executed instructions get recorded in /proc/profile. But since you
  enabled "Kernel profiling support", you must be a kernel hacker and
  hence you know what this is about :-)

# need an empty line after last entry, for sed script in Configure.

#
# This is used by 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
# LocalWords:  cdrom harddisk diskless netboot nfs xzvf ATAPI MB harddrives ide
# LocalWords:  HD harddisks CDROMs IDECD NEC MITSUMI filesystem XT XD PCI bios
# LocalWords:  ISA EISA Microchannel VESA BIOSes bussystem IPC SYSVIPC ipc Ctrl
# LocalWords:  InterProcessCommunication BINFMT Linkable http ac uk jo html GCC
# LocalWords:  netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
# LocalWords:  genksyms INET loopback gatewaying ethernet internet PPP ARP Arp
# LocalWords:  howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
# LocalWords:  proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
# LocalWords:  telneting AddressResolutionProtocol subnetted NAGLE rlogin NOSR
# LocalWords:  Mb SKB IPX Novell Netware dosemu Appletalk DDP ATALK tapedrive
# LocalWords:  SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
# LocalWords:  buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
# LocalWords:  QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
# LocalWords:  unix BBS linux nullmodem CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ
# LocalWords:  Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
# LocalWords:  COM ELPLUS Com EtherLinkIII VLB Arcnet arcnet Cabletron DEPCA DE
# LocalWords:  depca EtherWorks EWRK ewrk SEEQ EtherExpressPro EEXPRESS NI xxx
# LocalWords:  EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
# LocalWords:  PCMCIA cb stanford pcmcia LAN TEC RealTek ATP atp DLINK NetTools
# LocalWords:  TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
# LocalWords:  Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
# LocalWords:  Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
# LocalWords:  LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos harddrive mtools
# LocalWords:  std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
# LocalWords:  hpfs SYSV SCO intel iBCS Wyse WordPerfect tsx mit unixes sysv NR
# LocalWords:  SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
# LocalWords:  PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
# LocalWords:  gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
# LocalWords:  readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
# LocalWords:  misc AIC aic pio nullmodems scc Portmaster eql GIS PhotoCDs MCDX
# LocalWords:  mcdx gscd optcd sjcd ISP soundcard hdparm Workgroups Lan samba
# LocalWords:  filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
# LocalWords:  chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
# LocalWords:  Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
# LocalWords:  Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
# LocalWords:  carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
# LocalWords:  pppd Zilog ZS soundcards SRM bootloader SMP smp ez mainmenu rarp
# LocalWords:  RTNETLINK mknod
