Stage 1: Move a bunch of docs out from under sysinstall and other

less than accessible places.

14 files changed, 1541 insertions, 0 deletions

diff --git a/release/ABOUT.TXT b/release/texts/ABOUT.TXT
index 008a60c..008a60c 100644
--- a/release/ABOUT.TXT
+++ b/release/texts/ABOUT.TXT
diff --git a/release/ERRATA.TXT b/release/texts/ERRATA.TXT
index 239787f..239787f 100644
--- a/release/ERRATA.TXT
+++ b/release/texts/ERRATA.TXT
diff --git a/release/README.TXT b/release/texts/FLOPPIES.TXT
index 2d3e9a4..2d3e9a4 100644
--- a/release/README.TXT
+++ b/release/texts/FLOPPIES.TXT
diff --git a/release/sysinstall/help/hardware.hlp b/release/texts/HARDWARE.TXT
index 4916da2..4916da2 100644
--- a/release/sysinstall/help/hardware.hlp
+++ b/release/texts/HARDWARE.TXT
diff --git a/release/sysinstall/help/install.hlp b/release/texts/INSTALL.TXT
index dfc1697..dfc1697 100644
--- a/release/sysinstall/help/install.hlp
+++ b/release/texts/INSTALL.TXT
diff --git a/release/LAYOUT.TXT b/release/texts/LAYOUT.TXT
index ece4acb..ece4acb 100644
--- a/release/LAYOUT.TXT
+++ b/release/texts/LAYOUT.TXT
diff --git a/release/sysinstall/help/readme.hlp b/release/texts/README.TXT
index 5167040..5167040 100644
--- a/release/sysinstall/help/readme.hlp
+++ b/release/texts/README.TXT
diff --git a/release/sysinstall/help/relnotes.hlp b/release/texts/RELNOTES.TXT
index 0d50346..0d50346 100644
--- a/release/sysinstall/help/relnotes.hlp
+++ b/release/texts/RELNOTES.TXT
diff --git a/release/sysinstall/help/trouble.hlp b/release/texts/TROUBLE.TXT
index ca374ca..ca374ca 100644
--- a/release/sysinstall/help/trouble.hlp
+++ b/release/texts/TROUBLE.TXT
diff --git a/release/sysinstall/help/upgrade.hlp b/release/texts/UPGRADE.TXT
index 8b7b893..8b7b893 100644
--- a/release/sysinstall/help/upgrade.hlp
+++ b/release/texts/UPGRADE.TXT
diff --git a/release/sysinstall/help/XF86.hlp b/release/texts/XFREE86.TXT
index 4757fb0..4757fb0 100644
--- a/release/sysinstall/help/XF86.hlp
+++ b/release/texts/XFREE86.TXT
diff --git a/release/texts/i386/HARDWARE.TXT b/release/texts/i386/HARDWARE.TXT
new file mode 100644
index 0000000..4916da2
--- /dev/null
+++ b/release/texts/i386/HARDWARE.TXT
@@ -0,0 +1,514 @@
+Table of Contents
+-----------------
+0.  Document Conventions
+1.  Default Configuration (GENERIC kernel)
+2.  Using UserConfig to change FreeBSD kernel settings
+3.  LINT - other possible configurations
+4.  Supported Hardware
+
+See TROUBLE.TXT for Q&A on known hardware problems.
+
+=========================================================================
+
+0.      Document Conventions
+--      --------------------
+
+We have `underlined' text which represents user input with `-' symbols
+throughout this document to differentiate it from the machine output.
+
+1.      Default (GENERIC) Configuration
+--      -------------------------------
+
+The following table contains a list of all of the devices that are
+present in the GENERIC kernel. This is the essential part of the 
+operating system that is placed in your root partition during the 
+installation process.  A compressed version of the GENERIC kernel is
+also used on the installation floppy diskette and DOS boot image.
+
+The table describes the various parameters used by the driver to
+communicate with the hardware in your system.  There are four
+parameters in the table, though not all are used by each and every
+device:
+
+   Port   The starting I/O port used by the device, shown in hexadecimal.
+
+   IOMem  The lowest (or starting) memory address used by the device,
+          also shown in hexadecimal.
+
+   IRQ    The interrupt the device uses to alert the driver to an event,
+          given in decimal.
+
+   DRQ    The DMA (direct memory access) channel the device uses to move
+          data to and from main memory, also given in decimal.
+
+If an entry in the table has `n/a' for a value then it means that the
+parameter in question does not apply to that device.  A value of `dyn'
+means that the correct value should be determined automatically by the
+kernel when the system boots and that you don't need to worry about
+it.
+
+If an entry is marked with an *, it means that support is currently
+not available for it but should be back as soon as someone converts
+the driver to work within the new 3.0 framework.
+
+FreeBSD GENERIC kernel:
+
+        Port    IRQ     DRQ     IOMem   Description
+        ----    ---     ---     -----   ---------------------------------
+fdc0    3f0     6       2       n/a     Floppy disk controller
+wdc0    1f0     14      n/a     n/a     IDE/MFM/RLL disk controller
+wdc1    170     15      n/a     n/a     IDE/MFM/RLL disk controller
+
+adv0    n/a     n/a     n/a     n/a     AdvanSys ADP-9xx SCSI controller
+ncr0    n/a     n/a     n/a     n/a     NCR PCI SCSI controller
+bt0     330     dyn     dyn     dyn     Buslogic SCSI controller
+uha0    330     dyn     6       dyn     Ultrastore 14f
+aha0    330     dyn     5       dyn     Adaptec 154x/1535 SCSI controller
+ahb0    dyn     dyn     dyn     dyn     Adaptec 174x SCSI controller
+ahc0    dyn     dyn     dyn     dyn     Adaptec 274x/284x/294x SCSI controller
+aic0*   340     11      dyn     dyn     Adaptec 152x/AIC-6360 SCSI
+                                        controller
+amd0    n/a     n/a     n/a     n/a     Tekram DC-390(T) / AMD 53c974 PCI SCSI
+dpt     n/a     n/a     n/a     n/a     DPT RAID SCSI controllers.
+nca0*   1f88    10      dyn     dyn     ProAudioSpectrum cards
+sea0*   dyn     5       dyn     c8000   Seagate ST01/02 8 bit controller
+
+wt0     300     5       1       dyn     Wangtek and Archive QIC-02/QIC-36
+
+psm0    60      12      n/a     n/a     PS/2 Mouse
+
+mcd0    300     10      n/a     n/a     Mitsumi CD-ROM
+matcd0  230     n/a     n/a     n/a     Matsushita/Panasonic CD-ROM
+scd0    230     n/a     n/a     n/a     Sony CD-ROM
+
+sio0    3f8     4       n/a     n/a     Serial Port 0 (COM1)
+sio1    2f8     3       n/a     n/a     Serial Port 1 (COM2)
+
+lpt0    dyn     7       n/a     n/a     Printer Port 0
+lpt1    dyn     dyn     n/a     n/a     Printer Port 1
+
+de0     n/a     n/a     n/a     n/a     DEC DC21x40 PCI based cards
+                                        (including 21140 100bT cards)
+ed0     280     10      dyn     d8000   WD & SMC 80xx; Novell NE1000 &
+                                        NE2000; 3Com 3C503; HP PC Lan+
+eg0     310     5       dyn     dyn     3Com 3C505
+ep0     300     10      dyn     dyn     3Com 3C509
+ex0     dyn     dyn     dyn     n/a     Intel EtherExpress Pro/10 cards
+fe0     300     dyn     n/a     n/a     Allied-Telesis AT1700, RE2000 and
+                                        Fujitsu FMV-180 series cards.
+fxp0    dyn     dyn     n/a     dyn     Intel EtherExpress Pro/100B
+rl0     dyn     dyn     n/a     dyn     RealTek 8129/8139 fast ethernet
+tl0     dyn     dyn     n/a     dyn     TI TNET100 'ThunderLAN' cards.
+ie0     300     10      dyn     d0000   AT&T StarLAN 10 and EN100;
+                                        3Com 3C507; NI5210
+ix0     300     10      dyn     d0000   Intel EtherExpress cards
+ex0     dyn     dyn     dyn     dyn     Intel EtherExpress Pro/10 cards
+le0     300     5       dyn     d0000   Digital Equipment EtherWorks
+                                        2 and EtherWorks 3
+lnc0    280     10      n/a     dyn     Lance/PCnet cards
+                                        (Isolan, Novell NE2100, NE32-VL,
+					 some PCnet-PCI cards)
+vx0     dyn     dyn     n/a     dyn     3Com 3c59x ((Fast) Etherlink III)
+xl0     dyn     dyn     n/a     dyn     3Com 3c900, 3c905 and 3c905B
+                                        ((Fast) Etherlink XL)
+cs0     0x300   dyn     n/a     n/a     Crystal Semiconductor CS89x0-based
+                                        cards.
+ze0     300     5       n/a     d8000   IBM/National Semiconductor
+                                        PCMCIA Ethernet Controller
+zp0     300     10      n/a     d8000   3Com 3c589 Etherlink III
+                                        PCMCIA Ethernet Controller
+--- End of table ---
+
+
+If the hardware in your computer is not set to the same settings as
+those shown in the table and the item in conflict is not marked 'dyn',
+you will have to either reconfigure your hardware or use UserConfig
+to reconfigure the kernel to match the way your hardware is currently set
+(see the next section).
+
+If the settings do not match, the kernel may be unable to locate
+or reliably access the devices in your system.
+
+
+2.      Using UserConfig to change FreeBSD kernel settings
+--      --------------------------------------------------
+
+The FreeBSD kernel on the install floppy contains drivers for every
+piece of hardware that could conceivably be used to install the rest
+of the system with.  Unfortunately, PC hardware being what it is, some
+of these devices can be difficult to detect accurately, and for some,
+the process of detecting another can cause irreversible confusion.
+
+To make this process easier, FreeBSD provides UserConfig.  With this
+UserConfig, the user can configure and disable device drivers before
+the kernel is loaded, avoiding potential conflicts, and eliminating
+the need to reconfigure hardware to suit the default driver settings.
+
+Once FreeBSD is installed, it will remember the changes made using
+UserConfig, so that they only need be made once.
+
+It is important to disable drivers that are not relevant to a system
+in order to minimize the possibility of interference, which can cause
+problems that are difficult to track down.
+
+UserConfig features a command line interface for users with serial
+consoles or a need to type commands, and a full screen 'visual'
+interface, which provides point-and-shoot configuration functionality.
+
+Here is a sample UserConfig screen shot in 'visual' mode:
+
+---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port--
+ Storage :  (Collapsed)
+ Network :
+  NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters    CONF  ed0       5  0x280
+  NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters    CONF  ed1       5  0x300 
+ Communications : (Collapsed)
+ Input : (Collapsed)
+ Multimedia :
+---Inactive Drivers-------------------------------------------Dev--------------
+ Storage :
+ Network : (Collapsed)
+ Communications :
+ Input :
+ Multimedia :
+ PCI :
+
+---Parameters-for-device-ed0---------------------------------------------------
+ Port address : 0x280      Memory address : 0xd8000
+ IRQ number   : 5          Memory size    : 0x2000
+ Flags        : 0x0000
+-------------------------------------------------------------------------------
+  IO Port address (Hexadecimal, 0x1-0x2000)
+  [TAB]   Change fields           [Q]   Save device parameters
+
+
+  The screen is divided into four sections :
+
+ - Active Drivers.  Listed here are the device drivers that are currently
+   enabled, and their basic parameters.
+ - Inactive Drivers.  These drivers are present, but are disabled.
+ - Parameter edit field.  This area is used for editing driver parameters.
+ - Help area.  Keystroke help is displayed here.
+
+One of the Active and Inactive lists is always in use, and the current
+entry in the list will be shown with a highlight bar.  If there are
+more entries in a list than can be shown, it will scroll.  The bar can
+be moved up and down using the cursor keys, and moved between lists
+with the TAB key.
+
+Drivers in the Active list may be marked "CONF".  This indicates that
+one or more of their parameters conflicts with another device, and
+indicates a potential for problems.  The total number of conflicts is
+displayed at the top of the screen.
+
+As a general rule, conflicts should be avoided, either by disabling
+conflicting devices that are not present in the system, or by altering
+their configuration so that they match the installed hardware.
+
+In the list areas, drivers are grouped by their basic function.
+Groups can be 'Collapsed' to simplify the display (this is the default
+state for all groups).  If a group is collapsed, it will be shown with
+'(Collapsed)' in the list, as above.  To Expand a Collapsed group,
+position the highlight bar over the group heading and press Enter.  To
+Collapse it again, repeat the process.
+
+When a device driver in the Active list is highlighted, its full
+parameters are displayed in the Parameter edit area.  Note that not
+all drivers use all possible parameters, and some hardware supported
+by drivers may not use all the parameters the driver supports.
+
+To disable a driver, go to the Active list, Expand the group it is in,
+highlight the driver and press Del.  The driver will move to its group
+in the Inactive list.  (If the group is collapsed or off the screen,
+you may not see the driver in its new location.)
+
+To enable a driver, go to the Inactive list, Expand the group it is
+in, highlight the driver and press Enter.  The highlight will move to
+the Active list, and the driver you have just enabled will be
+highlighted, ready to be configured.
+
+To configure a driver, go to the Active list, Expand the group it is
+in, highlight the driver and press Enter.  The cursor will move to the
+Parameter edit area, and the device's parameters may be edited.
+
+While editing parameters, the TAB and cursor keys can be used to move
+between fields.  Most numeric values (except IRQ) are entered in
+hexadecimal, as indicated by the '0x' at the beginning of the field.
+The allowable values for a given field are show in the Key Help area
+when the field is active.
+
+To finish configuring a driver, press 'Q'.
+
+Note that PCI and EISA devices can be probed reliably, therefore they
+are not shown in the table above nor can their settings be changed
+using UserConfig.  PCI drivers may be seen in the "PCI Devices" section
+in the Active Devices list, if you wish to check for their presence.
+
+
+3.      LINT - other possible configurations
+--      ------------------------------------
+
+The following drivers are not in the GENERIC kernel but remain
+available to those who do not mind compiling a custom kernel (see
+section 6 of FreeBSD.FAQ).  The LINT configuration file
+(/sys/i386/conf/LINT) also contains prototype entries for just about
+every device supported by FreeBSD and is a good general reference.
+
+The device names and a short description of each are listed below. The port
+numbers, etc, are not meaningful here since you will need to compile a
+custom kernel to gain access to these devices anyway and can thus
+adjust the addresses to match the hardware in your computer in the process.
+The LINT file contains prototype entries for all of the below which you
+can easily cut-and-paste into your own file (or simply copy LINT and edit
+it to taste):
+
+ctx:    Cortex-I frame grabber
+cx:     Cronyx/Sigma multiport sync/async
+cy:     Cyclades high-speed serial driver
+el:     3Com 3C501
+fea:    DEV DEFEA EISA FDDI adapter
+fpa:    DEC DEFPA PCI FDDI adapter
+gp:     National Instruments AT-GPIB and AT-GPIB/TNT board
+gsc:    Genius GS-4500 hand scanner
+gus:    Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX
+gusxvi: Gravis Ultrasound 16-bit PCM
+hea:    Efficient ENI-155p ATM PCI adapter
+hfa:    FORE PCA-200E ATM PCI adapter
+joy:    Joystick
+labpc:  National Instrument's Lab-PC and Lab-PC+
+meteor: Matrox Meteor frame-grabber card
+bktr:   Brooktree Bt848 based frame-grabber cards.
+mpu:    Roland MPU-401 stand-alone card
+mse:    Microsoft, Logitech, ATI bus mouse ports
+mss:    Microsoft Sound System
+nic:    Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards
+opl:    Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum
+pas:    ProAudioSpectrum PCM and MIDI
+pca:    PCM audio ("/dev/audio") through your PC speaker
+pcm:    PCM audio on most modern ISA audio codecs
+psm:    PS/2 mouse port
+rc:     RISCom/8 multiport card
+sb:     SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum
+sbmidi: SoundBlaster 16 MIDI interface
+sbxvi:  SoundBlaster 16
+si:     Specialix SI/XIO/SX (old and enhanced ISA, PCI, EISA) serial
+spigot: Creative Labs Video Spigot video-acquisition board
+uart:   Stand-alone 6850 UART for MIDI
+wds:    Western Digital WD7000 IDE
+
+--- end of list ---
+
+
+4.      Supported Hardware
+--      ------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all peripherals currently known to work with
+FreeBSD.  Other configurations may also work, we have simply not as yet
+received confirmation of this.
+
+
+4.1.    Disk Controllers
+----    ----------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 1535 ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
+controllers.
+Adaptec AIC7850/AIC7895 on-board SCSI controllers.
+
+Support for the following controllers is rather weak:
+Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
+Adaptec 152x series ISA SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
+and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, such being necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset, and in such cases you *will* also be able to boot from them.
+   Check your system/board documentation for more details.
+
+
+AdvanSys (Advanced Systems) ABP510/542/5150 ISA and ABP5140/5142 ISA PnP
+cards, ABP842/852 VLB cards, and ABP920/930/930U/930UA/950/960/960U/970/970U
+PCI cards.
+
+** Note:  The ADP510/5140/5150 boards were shipped by HP with the 4020i
+   CD-R drive but with NO BIOS, so these models cannot control boot devices
+   though they can be used for any secondary SCSI device.  Also note that the
+   ABP5140/5142 boards were rebadged by SIIG as the "SpeedMaster i540/i542"
+
+
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
+controllers:
+        ASUS SC-200
+        Data Technology DTC3130 (all variants)
+        NCR cards (all)
+        Symbios cards (all)
+        Tekram DC390W, 390U and 390F
+        Tyan S1365
+
+Tekram DC390 and DC390T controllers (maybe other cards based on the
+AMD 53c974 as well).
+
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+WD7000 SCSI controller.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT and 8mm Exabyte) and CD ROM drives.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(mcd)   Mitsumi proprietary interface (all models, driver is rather stale)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface.
+
+
+4.2.    Network cards
+----    -------------
+
+Allied-Telesis AT1700 and RE2000 cards
+
+AMD PCnet/PCI (79c970 & 53c974 or 79c974)
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+Texas Instruments ThunderLAN PCI NICs, including the following:
+  Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
+  Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
+  Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
+  Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Efficient ENI-155p ATM PCI
+
+FORE PCA-200E ATM PCI
+
+Fujitsu MB86960A/MB86965A
+
+HP PC Lan+ cards (model numbers: 27247B and 27252A).
+
+Intel EtherExpress (not recommended due to driver instability)
+Intel EtherExpress Pro/10
+Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
+(Fast) Etherlink III / (Fast) Etherlink XL
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+
+4.3.    Misc
+----    ----
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+ARNET (now Digiboard) Sync 570/i high-speed serial.
+
+Boca BB1004 4-Port serial card (Modems NOT supported)
+Boca IOAT66 6-Port serial card (Modems supported)
+Boca BB1008 8-Port serial card (Modems NOT supported)
+Boca BB2016 16-Port serial card (Modems supported)
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
+
+Specialix SI/XIO/SX multiport serial cards, with both the older
+SIHOST2.x and the new "enhanced" (transputer based, aka JET) host cards.
+ISA, EISA and PCI are supported.
+
+Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
+ONboard 4/16 and Brumby.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+Connectix QuickCam
+Matrox Meteor Video frame grabber
+Creative Labs Video Spigot frame grabber
+Cortex1 frame grabber
+Various Frame grabbers based on Brooktree Bt848 chip.
+
+HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
+
+Bus mice
+
+PS/2 mice
+
+Standard PC Joystick
+
+X-10 power controllers
+
+GPIB and Transputer drivers.
+
+Genius and Mustek hand scanners.
+
+Floppy tape drives (some rather old models only, driver rather stale)
+
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
diff --git a/release/texts/i386/INSTALL.TXT b/release/texts/i386/INSTALL.TXT
new file mode 100644
index 0000000..dfc1697
--- /dev/null
+++ b/release/texts/i386/INSTALL.TXT
@@ -0,0 +1,513 @@
++=====================  Installing FreeBSD  ==========================+
+|                                                                     |
+| Table of Contents:                                                  |
+|                                                                     |
+| 0.0     Quick Start:                                                |
+|         0.1     Installing FreeBSD from CDROM or the Internet.      |
+|                                                                     |
+| 1.0     Detail on various installation types:                       |
+|         1.1     Installing from a network CDROM                     |
+|         1.2     Installing from Floppies                            |
+|         1.3     Installing from a DOS partition                     |
+|         1.4     Installing from QIC/SCSI tape                       |
+|         1.5     Installing over a network using NFS or FTP          |
+|                 1.5.1   NFS Installation tips                       |
+|                 1.5.2   FTP Installation tips                       |
+|                                                                     |
+| 2.0     DOS User's Q&A section.                                     |
+|         2.1     How do I make space for FreeBSD?                    |
+|         2.2     Can I use compressed DOS filesystems from FreeBSD?  |
+|         2.3     Can I use DOS extended partitions?                  |
+|         2.4     Can I run DOS executables under FreeBSD?            |
+|                                                                     |
++=====================================================================+
+
+Author:         Jordan K. Hubbard
+Last updated:   Tue Mar 24 00:56:14 PST 1998
+
+0.0     Quick Start
+---     -----------
+
+This manual documents the process of making a new installation of
+FreeBSD on your machine.  If you are upgrading from a previous
+release of FreeBSD, please see the file UPGRADE.TXT for important
+information on upgrading.  If you are not familiar with configuring
+PC hardware for FreeBSD, you should also read the HARDWARE.TXT file -
+it contains important information which may save you a lot of grief.
+
+If you're new to FreeBSD then you should also read EVERYTHING listed
+in the Documentation menu on the boot floppy.  It may seem like a lot
+to read, but the time you spend now reading the documents will be made
+up many times over because you were adequately prepared. Also, you will
+know the types of information available should you get stuck later.
+Once the system is installed, you can also revisit this menu and use a 
+WEB browser to read the installed FAQ (Frequently Asked Questions) and 
+Handbook HTML documentation sets for FreeBSD.  You can also use the 
+browser to visit other WEB sites on the net (like http://www.freebsd.org)
+if you have an Internet connection. See ABOUT.TXT for more information
+on the resources available to you.
+
+The best laid plans sometimes go awry, so if you run into trouble take a 
+look at TROUBLE.TXT which contains valuable troubleshooting information.
+
+DISCLAIMER: While FreeBSD does its best to safeguard against
+accidental loss of data, it's still more than possible to WIPE OUT
+YOUR ENTIRE DISK with this installation!  Please do not proceed to the
+final FreeBSD installation menu unless you've adequately backed up any
+important data first!  We really mean it!
+
+FreeBSD requires a 386 or better processor to run (sorry, there is no
+support for '286 processors), 5 megs of RAM to install and 4 megs of
+ram to run. You will need at least 80 megs of free hard drive space.
+See below for ways of shrinking existing DOS partitions in order to
+install FreeBSD.
+
+
+0.1     Installing FreeBSD from CDROM or the Internet
+---     ---------------------------------------------
+
+The easiest type of installation is from CD.  If you have a supported
+CDROM drive and a FreeBSD installation CD from Walnut Creek CDROM,
+there are 3 ways of starting the installation from it:
+
+        1. If your system supports bootable CDROM media (usually an option
+           which can be selectively enabled in the controller's setup menu
+           or in the PC BIOS for some systems) and you have it enabled,
+           FreeBSD 2.2.1 and later CDs support the "El Torrito" bootable
+           CD standard.  Simply put the installation CD in your CDROM drive
+           and boot the system to begin installation.
+
+        2. If you have drivers which allow you to see your CDROM drive
+           from from DOS, first disable any fancy memory managers you may
+           have configured, change directory to the CDROM (E:\ in the example
+           below) and then type this:
+
+                E> install
+
+           and you should boot directly into the FreeBSD installation.
+
+           If either steps fail, please go on to step 3.
+
+        3. Build a FreeBSD boot floppy from the floppies/boot.flp
+           file in a FreeBSD distribution.  Either simply use the
+           ``makeflp.bat'' script from DOS or read floppies/README.TXT
+           for more information on creating bootable floppies under
+           different operating systems.  Then you simply boot
+           from the floppy and you should go into the FreeBSD
+           installation.
+
+If you don't have a CDROM and would like to simply install over the
+net using PPP, slip or a dedicated connection, simply fetch the
+<FreeBSD-release>/floppies/boot.flp file from:
+
+        ftp://ftp.freebsd.org/pub/FreeBSD
+
+or one of its many mirrors (http://www.freebsd.org/handbook/mirrors.html)
+and follow step 3 above.  You should also read the floppies/README.TXT
+file as it contains important information for downloaders.
+
+Once you have a boot floppy made, please go to section 1.5 of this
+document for additional tips on installing via FTP or NFS.
+
+
+1.0     Detail on various installation types
+---     ------------------------------------
+
+Once you've gotten yourself to the initial installation screen
+somehow, you should be able to follow the various menu prompts and go
+from there.  If you've never used the FreeBSD installation before, you
+are also encouraged to read some of the documentation in the the
+Documentation submenu as well as the general "Usage" instructions on
+the first menu.
+
+   REMEMBER:  If you get stuck at a screen, hit F1 for the online
+   documentation for that section.
+
+If you've never installed FreeBSD before, or even if you have, the
+"Novice" installation mode is the most recommended since it makes sure
+that you'll visit all the various important checklist items along the
+way.  If you're much more comfortable with the FreeBSD installation
+process and know _exactly_ what you want to do, use the Express or
+Custom installation options.  If you're upgrading an existing system,
+use the Upgrade option.
+
+The FreeBSD installer supports the direct use of floppy, DOS, tape,
+CDROM, FTP, NFS and UFS partitions as installation media, further tips
+on installing from each type of media listed below.
+
+
+1.1     Installing from a network CDROM
+---     -------------------------------
+
+If you simply wish to install from a local CDROM drive then see the
+Quick Start section.  If you don't have a CDROM drive on your system
+and wish to use a FreeBSD distribution CD in the CDROM drive of
+another system to which you have network connectivity, there are
+several ways of going about it:
+
+1. If you would be able to FTP install FreeBSD directly from the CDROM
+   drive in some FreeBSD machine, it's quite easy: You simply add the
+   following line to the password file (using the vipw command):
+
+        ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
+And anyone else on your network will now be able to chose a Media type
+of FTP and type in: ``ftp://<machine with CDROM drive>'' after picking
+"Other" in the ftp sites menu.
+
+2. If you would rather use NFS to export the CDROM directly to the
+   machine(s) you'll be installing from, you need to first add an
+   entry to the /etc/exports file (on the machine with the CDROM drive)
+   which looks something like this:
+
+        /cdrom          -ro             ziggy.foo.com
+
+   To allow the machine "ziggy.foo.com" to mount the CDROM directly
+   via NFS during installation.  The machine with the CDROM must also
+   be configured as an NFS server, of course, and if you're not sure how
+   to do that then an NFS installation is probably not the best choice
+   for you unless you're willing to read up on rc.conf(5) and configure
+   things appropriately.  Assuming that this part goes smoothly, you
+   should be able to enter:  <cdrom-host>:/cdrom as the path for an NFS
+   installation when the target machine is installed.
+
+
+1.2     Installing from Floppies
+---     ------------------------
+
+If you must install from floppy disks, either due to unsupported
+hardware or just because you enjoy doing things the hard way, you must
+first prepare some floppies for the install.
+
+First, make a boot floppy as described in floppies/README.TXT
+
+Second, read the file LAYOUT.TXT and pay special attention to the
+"Distribution format" section since it describes which files you're
+going to need to put onto floppy and which you can safely skip.
+
+Next you will need, at minimum, as many 1.44MB floppies as it takes to
+hold all files in the bin (binary distribution) directory.  If you're
+preparing these floppies under DOS, then THESE floppies *must* be
+formatted using the MS-DOS FORMAT command.  If you're using Windows,
+use the Windows File Manager format command.
+
+Don't trust Factory Preformatted floppies!  Format them again
+yourself, just to make sure.  Many problems reported by our users in
+the past have resulted from the use of improperly formatted media,
+which is why I'm taking such special care to mention it here!
+
+If you're creating the floppies from another FreeBSD machine, a format
+is still not a bad idea though you don't need to put a DOS filesystem
+on each floppy.  You can use the `disklabel' and `newfs' commands to
+put a UFS filesystem on a floppy, as the following sequence of
+commands illustrates:
+
+        fdformat -f 1440 fd0.1440
+        disklabel -w -r fd0.1440 floppy3
+        newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0
+
+After you've formatted the floppies for DOS or UFS, you'll need to
+copy the files onto them.  The distribution files are split into
+chunks conveniently sized so that 5 of them will fit on a conventional
+1.44MB floppy.  Go through all your floppies, packing as many files as
+will fit on each one, until you've got all the distributions you want
+packed up in this fashion.  Each distribution should go into its own
+subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa,
+a:\bin\bin.ab, ...
+
+IMPORTANT NOTE: The bin.inf file also needs to go on the first floppy
+of the bin set since it is read by the installation program in order
+to figure out how many additional pieces to look for when fetching and
+concatenating the distribution.  When putting distributions onto
+floppies, the <distname>.inf file MUST occupy the first floppy of each
+distribution set!
+
+Once you come to the Media screen of the install, select "Floppy" and
+you'll be prompted for the rest.
+
+
+1.3     Installing from a DOS partition
+---     -------------------------------
+
+To prepare for installation from an MS-DOS partition you should simply
+copy the files from the distribution into a directory called
+"FREEBSD" on the Primary DOS partition ("Drive C:").  For example, to do
+a minimal installation of FreeBSD from DOS using files copied from the
+CDROM, you might do something like this:
+
+        C:\> MD C:\FREEBSD
+        C:\> XCOPY /S E:\BIN C:\FREEBSD\BIN
+
+Assuming that `E:' was where your CD was mounted.
+
+For as many `DISTS' as you wish to install from DOS (and you have free
+space for), install each one in a directory under `C:\FREEBSD' - the
+BIN dist is only the minimal requirement.
+
+IMPORTANT NOTE: Though you can do all of the above by hand if you
+really want to, all of it is much more easily accomplished now by
+Robert Nordier's "setup.exe" program.  It will give you a menu of
+distribution choices, verify that you have enough free space and do
+all the copying to C:\FREEBSD for you automatically.
+
+Once you've copied the directories or run setup.exe and let it do all
+the work for you, you can simply launch the installation from DOS by
+running the install.bat script (NOTE: Some memory managers don't like
+this - disable QEMM or EMM386 if they're running before trying this)
+or making a boot floppy as described in section 0.1.
+
+
+1.4     Installing from QIC/SCSI Tape
+---     -----------------------------
+
+When installing from tape, the installation program expects the files
+to be simply tar'ed onto it, so after fetching all of the files for
+the distributions you're interested in, simply tar them onto the tape
+with a command something like this:
+
+        cd /where/you/have/your/dists
+        tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2
+
+When you go to do the installation, you should also make sure that you
+leave enough room in some temporary directory (which you'll be allowed
+to choose) to accommodate the FULL contents of the tape you've
+created.  Due to the non-random access nature of tapes, this method of
+installation requires quite a bit of temporary storage!  You should
+expect to require as much temporary storage as you have stuff written
+on tape.
+
+SPECIAL NOTE: When going to do the installation, the tape must be in
+the drive *before* booting from the boot floppy.  The installation
+"probe" may otherwise fail to find it.
+
+Now create a boot floppy as described in section 0.1 and proceed with
+the installation.
+
+
+1.5     Installing over a network using FTP or NFS
+---     ------------------------------------------
+
+After making a boot floppy as described in the first section, you can
+load the rest of the installation over a network using one of 3 types
+of connections:
+
+        Serial port:    SLIP / PPP
+        Parallel port:  PLIP (using ``laplink'' style cable)
+        Ethernet:       A standard Ethernet controller (including
+                        certain PCCARD devices).
+
+Serial Port
+-----------
+
+SLIP support is rather primitive, and is limited primarily to
+hard-wired links, such as a serial cable running between two
+computers.  The link must be hard-wired because the SLIP installation
+doesn't currently offer a dialing capability.  If you need to dial out
+with a modem or otherwise dialog with the link before connecting to
+it, then I recommend that the PPP utility be used instead.
+
+If you're using PPP, make sure that you have your Internet Service
+Provider's IP address and DNS information handy as you'll need to know
+it fairly early in the installation process.  You may also need to
+know your own IP address, though PPP supports dynamic address
+negotiation and may be able to pick up this information directly from
+your ISP if they support it.
+
+You will also need to know how to use the various "AT commands" for
+dialing out with your particular brand of modem as the PPP dialer
+provides only a very simple terminal emulator.
+
+
+Parallel Port
+-------------
+
+If a hard-wired connection to another FreeBSD (2.0R or later) or Linux
+machine is available, you might also consider installing over a
+"laplink" style parallel port cable.  The data rate over the parallel
+port is much higher than what is typically possible over a serial line
+(up to 50k/sec), thus resulting in a quicker installation.  It's not
+typically necessary to use "real" IP addresses when using a
+point-to-point parallel cable in this way and you can generally just
+use RFC 1918 style addresses for the ends of the link (e.g. 10.0.0.1,
+10.0.0.2, etc).
+
+IMPORTANT NOTE: If you use a Linux machine rather than a FreeBSD
+machine as your PLIP peer, you will also have to specify "link0" in
+the TCP/IP setup screen's ``extra options for ifconfig'' field.
+
+
+Ethernet
+--------
+
+FreeBSD supports most common PC Ethernet cards, a table of supported
+cards (and their required settings) being provided as part of the
+FreeBSD Hardware Guide (see the Documentation menu on the boot floppy
+or the top level directory of the CDROM).  If you are using one of the
+supported PCMCIA Ethernet cards, also be sure that it's plugged in
+_before_ the laptop is powered on!  FreeBSD does not, unfortunately,
+currently support "hot insertion" of PCMCIA cards during installation.
+
+You will also need to know your IP address on the network, the
+"netmask" value for your address class and the name of your machine.
+Your system administrator can tell you which values are appropriate to
+your particular network setup.  If you will be referring to other
+hosts by name rather than IP address, you'll also need a name server
+and possibly the address of a gateway (if you're using PPP, it's your
+provider's IP address) to use in talking to it.
+
+If you do not know the answers to these questions then you should
+really probably talk to your system administrator _first_ before
+trying this type of installation!  Using a randomly chosen IP address
+or netmask on a live network will almost certainly get you shot at
+dawn.
+
+Once you have a network connection of some sort working, the
+installation can continue over NFS or FTP.
+
+
+1.5.1   NFS installation tips
+-----   ---------------------
+
+        NFS installation is fairly straight-forward: Simply copy the
+        FreeBSD distribution files you want onto a server somewhere
+        and then point the NFS media selection at it.
+
+        If this server supports only "privileged port" access (as is
+        generally the default for Sun and Linux workstations), you
+        will need to set this option in the Options menu before
+        installation can proceed.
+
+        If you have a poor quality Ethernet card which suffers from very
+        slow transfer rates, you may also wish to toggle the appropriate
+        Options flag.
+
+        In order for NFS installation to work, the server must also support
+        "subdir mounts", e.g. if your FreeBSD 2.2 distribution directory
+        lives on:  ziggy:/usr/archive/stuff/FreeBSD
+        Then ziggy will have to allow the direct mounting of
+        /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff.
+
+        In FreeBSD's /etc/exports file this is controlled by the
+        ``-alldirs'' option.  Other NFS servers may have different
+        conventions.  If you are getting `Permission Denied' messages
+        from the server then it's likely that you don't have this
+        properly enabled!
+
+
+1.5.2   FTP Installation tips
+-----   ---------------------
+
+        FTP installation may be done from any mirror site containing a
+        reasonably up-to-date version of FreeBSD.  A full menu of
+        reasonable choices for almost any location in the world is
+        provided in the FTP site menu during installation.
+
+        If you are installing from some other FTP site not listed in
+        this menu, or you are having troubles getting your name server
+        configured properly, you can also specify your own URL by
+        selecting the ``Other'' choice in that menu.  A URL can
+        contain a hostname or an IP address, so the following would
+        work in the absence of a name server:
+
+                ftp://192.216.191.11/pub/FreeBSD/2.2-RELEASE
+
+        There are two FTP installation modes you can use:
+
+           o FTP:
+
+             For all FTP transfers, use the standard "Active" mode for
+             transfers.  This will not work through most firewalls but
+             will often work best with older ftp servers that do not
+             support passive mode.  If your connection hangs with
+             passive mode, try this one!
+
+           o FTP Passive:
+
+             For all FTP transfers, use "Passive" mode.  This allows
+             the user to pass through firewalls that do not allow
+             incoming connections on random port addresses.
+
+        NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY'
+        CONNECTIONS, WHERE A PROXY FTP SERVER IS LISTENING ON A
+        DIFFERENT PORT!
+
+        In such instances, you should specify the URL as something like:
+
+                ftp://foo.bar.com:1234/pub/FreeBSD
+
+        Where "1234" is the port number of the proxy ftp server.
+
+
+2.0     DOS user's Question and Answer section
+---     --------------------------------------
+
+2.1     Help!  I have no space!  Do I need to delete everything first?
+---     --------------------------------------------------------------
+
+If your machine is already running DOS and has little or no free space
+available for FreeBSD's installation, all is not lost!  You may find
+the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD
+CDROM or on the various FreeBSD ftp sites, to be quite useful.
+
+FIPS allows you to split an existing DOS partition into two pieces,
+preserving the original partition and allowing you to install onto the
+second free piece.  You first "defrag" your DOS partition, using the
+DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS.  It
+will prompt you for the rest of the information it needs.  Afterwards,
+you can reboot and install FreeBSD on the new partition.  Also note
+that FIPS will create the second partition as a "clone" of the first,
+so you'll actually see that you now have two DOS Primary partitions
+where you formerly had one.  Don't be alarmed!  You can simply delete
+the extra DOS Primary partition (making sure it's the right one by
+examining its size! :)
+
+NOTE: FIPS does NOT currently work with FAT32 or VFAT style partitions
+as used by newer versions of Windows 95.  To split up such a
+partition, you will need a commercial product such as Partition Magic
+3.0.  Sorry, but this is just the breaks if you've got a Windows
+partition hogging your whole disk and you don't want to reinstall from
+scratch.
+
+2.2     Can I use compressed DOS filesystems from FreeBSD?
+---     --------------------------------------------------
+
+No.  If you are using a utility such as Stacker(tm) or
+DoubleSpace(tm), FreeBSD will only be able to use whatever portion of
+the filesystem you leave uncompressed.  The rest of the filesystem
+will show up as one large file (the stacked/dblspaced file!).  DO NOT
+REMOVE THAT FILE as you will probably regret it greatly!
+
+It is probably better to create another uncompressed DOS extended
+partition and use this for communications between DOS and FreeBSD if
+such is your desire.
+
+
+2.3     Can I mount my DOS extended partitions?
+---     ---------------------------------------
+
+Yes. DOS extended partitions are mapped in at the end of the other
+``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5, your E:
+drive /dev/sd0s6, and so on. This example assumes, of course, that
+your extended partition is on SCSI drive 0. For IDE drives, substitute
+``wd'' for ``sd'' appropriately. You otherwise mount extended
+partitions exactly like you would mount any other DOS drive, e.g.:
+
+mount -t msdos /dev/sd0s5 /dos_d
+
+
+2.4     Can I run DOS binaries under FreeBSD?
+---     -------------------------------------
+
+Ongoing work with BSDI's doscmd utility is bringing this much closer to
+being a reality in FreeBSD 3.0, though it still has some rough edges.
+If you're interested in working on this, please send mail to
+emulation@FreeBSD.org and indicate that you're interested in joining
+this ongoing effort!
+
+There is also a neat utility called "pcemu" in the ports collection
+which emulates an 8088 and enough BIOS services to run DOS text mode
+applications.  It requires the X Window System (provided as XFree86
+3.2) to operate.
+
+
+---- End of Installation Guide ---
diff --git a/release/texts/i386/RELNOTES.TXT b/release/texts/i386/RELNOTES.TXT
new file mode 100644
index 0000000..0d50346
--- /dev/null
+++ b/release/texts/i386/RELNOTES.TXT
@@ -0,0 +1,514 @@
+                                 RELEASE NOTES
+                          FreeBSD Release 3.0-SNAP
+
+This is a 3.0-CURRENT release SNAPshot of FreeBSD, currently
+on its way to a follow-on release for 3.0 which was released
+on October 16th, 1998.
+
+Any installation failures or crashes should be reported by using the
+send-pr command (those preferring a WEB based interface can also see
+http://www.freebsd.org/send-pr.html).
+
+For information about FreeBSD and the layout of the 3.0-RELEASE
+directory (especially if you're installing from floppies!), see
+ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
+HARDWARE.TXT files.
+
+For the latest of these 3.0-current snapshots, you should always see:
+
+        ftp://current.freebsd.org/pub/FreeBSD
+
+If you wish to get the latest post-3.0-RELEASE technology.
+
+Table of contents:
+------------------
+1. What's new since 3.0-RELEASE
+   1.1 KERNEL CHANGES
+   1.2 SECURITY FIXES
+   1.3 USERLAND CHANGES
+
+2. Supported Configurations
+   2.1 Disk Controllers
+   2.2 Ethernet cards
+   2.3 ATM
+   2.4 Misc
+
+3. Obtaining FreeBSD
+   3.1 FTP/Mail
+   3.2 CDROM
+
+4. Upgrading from previous releases of FreeBSD
+
+5. Reporting problems, making suggestions, submitting code
+6. Acknowledgements
+
+
+1. What's new since 3.0-RELEASE
+---------------------------------
+All changes described here are unique to the 3.0 branch unless
+specifically marked as [MERGED] features.
+
+1.1. KERNEL CHANGES
+-------------------
+
+1.2. SECURITY FIXES
+-------------------
+
+1.3. USERLAND CHANGES
+---------------------
+
+2. Supported Configurations
+---------------------------
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all peripherals currently known to work with
+FreeBSD.  Other configurations may also work, we have simply not as yet
+received confirmation of this.
+
+
+2.1. Disk Controllers
+---------------------
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 1535 ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series
+EISA/VLB/PCI SCSI controllers.
+Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers.
+
+AdvanSys SCSI controllers (all models).
+
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+DPT SCSI/RAID controllers (most variants).
+
+SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
+controllers:
+        ASUS SC-200
+        Data Technology DTC3130 (all variants)
+        NCR cards (all)
+        Symbios cards (all)
+        Tekram DC390W, 390U and 390F
+        Tyan S1365
+
+
+QLogic SCSI and Fibre Channel controllers.
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
+tape drives (including DAT and 8mm Exabyte), medium changers, processor
+target devices and CDROM drives.  WORM devices that support CDROM commands
+are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
+writing support is provided by cdrecord, which is in the ports tree.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface
+
+SCSI TAPE SUPPORT:
+
+  The CAM SCSI tape driver doesn't yet handle older (and many times broken)
+  tape drives very well.  If you've got an older SCSI-1 tape drive, like an
+  Exabyte 8200 or older QIC-type tape drive, it may not work properly with
+  the CAM tape driver.  This is obviously a known problem, and we're
+  working on it.
+
+  Newer tape drives that are mostly SCSI-2 compliant should work fine.
+  e.g., DAT (DDS-1, 2 and 3), DLT, and newer Exabyte 8mm drives should
+  work fine.
+
+  If you want to find out if your particular tape drive is supported, the
+  best way to find out is to try it!
+
+The following drivers were supported under the old SCSI subsystem, but are
+NOT YET supported under the new CAM SCSI subsystem:
+
+  Tekram DC390 and DC390T controllers (maybe other cards based on the
+  AMD 53c974 as well).
+
+  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+  UltraStor 14F, 24F and 34F SCSI controllers.
+
+  Seagate ST01/02 SCSI controllers.
+
+  Future Domain 8xx/950 series SCSI controllers.
+
+  WD7000 SCSI controller.
+
+  Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
+  Adaptec 152x series ISA SCSI controllers
+  Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
+  and SoundBlaster SCSI cards.
+
+  [ Note:  There is work-in-progress to port the AIC-6260/6360 and
+    UltraStor drivers to the new CAM SCSI framework, but no estimates on
+    when or if they will be completed. ]
+
+Unmaintained drivers, they might or might not work for your hardware:
+
+  Floppy tape interface (Colorado/Mountain/Insight)
+
+  (mcd)   Mitsumi proprietary CD-ROM interface (all models)
+
+2.2. Ethernet cards
+-------------------
+Allied-Telesis AT1700 and RE2000 cards
+
+AMD PCnet/PCI (79c970 & 53c974 or 79c974)
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra.  SMC Etherpower II.
+
+RealTek 8129/8139 fast ethernet NICs including the following:
+  Allied Telesyn AT2550
+  Genius GF100TXR (RTL8139)
+  NDC Communications NE100TX-E
+  OvisLink LEF-8129TX
+  OvisLink LEF-8139TX
+  Netronix Inc. EA-1210 NetEther 10/100
+  KTX-9130TX 10/100 Fast Ethernet
+
+Texas Instruments ThunderLAN PCI NICs, including the following:
+  Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
+  Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
+  Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
+  Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu MB86960A/MB86965A
+
+HP PC Lan+ cards (model numbers: 27247B and 27252A).
+
+Intel EtherExpress 16
+Intel EtherExpress Pro/10
+Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
+(Fast) Etherlink III / (Fast) Etherlink XL
+
+Toshiba ethernet cards
+
+Crystal Semiconductor CS89x0-based NICs, including:
+  IBM Etherjet ISA
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+2.3 ATM
+-------
+
+   o ATM Host Interfaces
+        - FORE Systems, Inc. PCA-200E ATM PCI Adapters
+        - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
+
+   o ATM Signalling Protocols
+        - The ATM Forum UNI 3.1 signalling protocol
+        - The ATM Forum UNI 3.0 signalling protocol
+        - The ATM Forum ILMI address registration
+        - FORE Systems's proprietary SPANS signalling protocol
+        - Permanent Virtual Channels (PVCs)
+
+   o IETF "Classical IP and ARP over ATM" model
+        - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
+        - RFC 1577, "Classical IP and ARP over ATM"
+        - RFC 1626, "Default IP MTU for use over ATM AAL5"
+        - RFC 1755, "ATM Signaling Support for IP over ATM"
+        - RFC 2225, "Classical IP and ARP over ATM"
+        - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
+        - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
+                "A Distributed ATMARP Service Using SCSP"
+
+   o ATM Sockets interface
+
+2.4. Misc
+---------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+ARNET (now Digiboard) Sync 570/i high-speed serial.
+
+Boca BB1004 4-Port serial card (Modems NOT supported)
+Boca IOAT66 6-Port serial card (Modems supported)
+Boca BB1008 8-Port serial card (Modems NOT supported)
+Boca BB2016 16-Port serial card (Modems supported)
+
+Comtrol Rocketport card.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
+
+Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
+ONboard 4/16 and Brumby.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards. (snd driver)
+
+Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
+Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
+
+Connectix QuickCam
+Matrox Meteor Video frame grabber
+Creative Labs Video Spigot frame grabber
+Cortex1 frame grabber
+Hauppauge Wincast/TV boards (PCI)
+STB TV PCI
+Intel Smart Video Recorder III
+Various Frame grabbers based on Brooktree Bt848 chip.
+
+HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
+
+PS/2 mice
+
+Standard PC Joystick
+
+X-10 power controllers
+
+GPIB and Transputer drivers.
+
+Genius and Mustek hand scanners.
+
+Xilinx XC6200 based reconfigurable hardware cards compatible with
+the HOT1 from Virtual Computers (www.vcc.com)
+
+Support for Dave Mills experimental Loran-C receiver.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
+
+3. Obtaining FreeBSD
+--------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+3.1. FTP/Mail
+-------------
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the official FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the site closest (in
+networking terms) to you.  Additional mirror sites are always welcome!
+Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
+become an official mirror site.
+
+If you do not have access to the Internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
+to get more information on how to fetch files using this mechanism.
+Please do note, however, that this will end up sending many *tens of
+megabytes* through the mail and should only be employed as an absolute
+LAST resort!
+
+
+3.2. CDROM
+----------
+
+FreeBSD 3.0-RELEASE and 2.2.x-RELEASE CDs may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
+
+Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp from:
+
+        ftp://ftp.cdrom.com/cdrom/catalog
+
+Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
+FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
+FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
+separate).  With a subscription, you will automatically receive updates as
+they are released.  Your credit card will be billed when each disk is
+shipped and you may cancel your subscription at any time without further
+obligation.
+
+Shipping (per order not per disc) is $5 in the US, Canada or Mexico
+and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
+Express or checks in U.S. Dollars and ship COD within the United
+States.  California residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+4. Upgrading from previous releases of FreeBSD
+----------------------------------------------
+
+If you're upgrading from a previous release of FreeBSD, most likely
+it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
+following issues may affect you, depending of course on your chosen
+method of upgrading.  There are two popular ways of upgrading
+FreeBSD distributions:
+
+        o Using sources, via /usr/src
+        o Using sysinstall's (binary) upgrade option.
+
+In the case of using sources, there are simply two targets you need to
+be aware of: The standard ``world'' target, which will upgrade a 2.x
+system to 3.0, or the ``aout-to-elf'' target, which will both upgrade
+and convert the system to ELF binary format.
+In the case of using the binary upgrade option, the system will go
+straight to 3.0/ELF but also populate the /<basepath>/lib/aout
+directories for backwards compatibility with older binaries.
+
+In either case, going to ELF will mean that you'll have somewhat
+smaller binaries and access to a lot more compiler goodies which have
+been already been ported to other ELF environments (our older and
+somewhat crufty a.out format being largely unsupported by most other
+software projects), but on the downside you'll also have access to far
+fewer ports and packages since many of those have not been adapted to
+ELF yet.  This will occur in time, but those who wish to retain access
+to the greatest number of packages and 3rd-party binaries should
+probably stick with a.out.
+
+The kernel is also still in a.out format at this time so that older
+LKMs and library interfaces can continue to work, but a full
+transition to ELF will occur at some point after 3.0-RELEASE.  Those
+wishing to generate dynamic kernel components should therefore use the
+newer KLD mechanism rather than the older LKM format - the LKM format
+is not long for this world and will soon be unsupported!
+
+[ other important upgrading notes should go here]
+
+
+5. Reporting problems, making suggestions, submitting code.
+-----------------------------------------------------------
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached, if you can!).
+
+The preferred method to submit bug reports from a machine with
+Internet mail connectivity is to use the send-pr command or use the CGI
+script at http://www.freebsd.org/send-pr.html.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.  Bugs filed in this way are also visible on our WEB site
+in the support section and are therefore valuable both as bug reports
+and as "signposts" for other users concerning potential problems to
+watch out for.
+
+If, for some reason, you are unable to use the send-pr command to
+submit a bug report, you can try to send it to:
+
+                freebsd-bugs@FreeBSD.org
+
+Note that send-pr itself is a shell script that should be easy to move
+even onto a totally different system.  We much prefer if you could use
+this interface, since it make it easier to keep track of the problem
+reports.  However, before submitting, please try to make sure whether
+the problem might have already been fixed since.
+
+
+Otherwise, for any questions or tech support issues, please send mail to:
+
+                freebsd-questions@FreeBSD.org
+
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more desired
+enhancements than we'll ever be able to manage by ourselves!  To
+contact us on technical matters, or with offers of help, please send
+mail to:
+
+                freebsd-hackers@FreeBSD.org
+
+
+Please note that these mailing lists can experience *significant*
+amounts of traffic and if you have slow or expensive mail access and
+are only interested in keeping up with significant FreeBSD events, you
+may find it preferable to subscribe instead to:
+
+                freebsd-announce@FreeBSD.org
+
+
+All of the mailing lists can be freely joined by anyone wishing
+to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
+`help' on a line by itself somewhere in the body of the message.  This
+will give you more information on joining the various lists, accessing
+archives, etc.  There are a number of mailing lists targeted at
+special interest groups not mentioned here, so send mail to majordomo
+and ask about them!
+
+
+6. Acknowledgements
+-------------------
+
+FreeBSD represents the cumulative work of many dozens, if not
+hundreds, of individuals from around the world who have worked very
+hard to bring you this release.  For a complete list of FreeBSD
+project staffers, please see:
+
+        http://www.freebsd.org/handbook/staff.html
+
+or, if you've loaded the doc distribution:
+
+        file:/usr/share/doc/handbook/staff.html
+
+
+Special mention to:
+
+        The donors listed at http://www.freebsd.org/handbook/donors.html
+
+        Justin M. Seger <jseger@freebsd.org> for almost single-handedly
+        converting the ports collection to ELF.
+
+        Doug Rabson <dfr@freebsd.org> and John Birrell <jb@freebsd.org>
+        for making FreeBSD/alpha happen and to the NetBSD project for
+        substantial indirect aid.
+
+        Peter Wemm <peter@freebsd.org> for the new kernel module system
+        (with substantial aid from Doug Rabson).
+
+        And to the many thousands of FreeBSD users and testers all over the
+        world, without whom this release simply would not have been possible.
+
+We sincerely hope you enjoy this release of FreeBSD!
+
+                        The FreeBSD Project