--- title: "FreeBSD 4.4-RELEASE i386 Hardware Notes" sidenav: download --- ++++

The FreeBSD Documentation Project



1 Introduction

This document contains the hardware compatability notes for FreeBSD 4.4-RELEASE on the i386 hardware platform. It lists devices known to work on this platform, as well as some notes on boot-time kernel customization that may be useful when attempting to configure support for new devices.

Note: This document includes information specific to the i386 hardware platform. Versions of the hardware compatability notes for other architectures will differ in some details.


2 Supported Processors and Motherboards

FreeBSD for the i386 currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to Pentium 4 class machines (though the 386sx is not recommended).


3 Supported Devices

$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.13.2.14 2001/09/06 23:17:00 bmah Exp $

This section describes the devices currently known to be supported by with FreeBSD on the i386 platform. Other configurations may also work, but simply have not been tested yet. Feedback, updates, and corrections to this list are encouraged.

Where possible, the drivers applicable to each device or class of devices is listed. If the driver in question has a manual page in the FreeBSD base distribution (most should), it is referenced here.


3.1 Disk Controllers

IDE/ATA controllers ( ata(4) driver)



Adaptec SCSI Controllers



Adaptec 2100S/32x0S/34x0S SCSI RAID controllers ( asr(4) driver)

Adaptec 2000S/2005S Zero-Channel RAID controllers ( asr(4) driver)

Adaptec 2400A ATA-100 RAID controller ( asr(4) driver)

Adaptec FSA family RAID controllers ( aac(4) driver)



AdvanSys SCSI controllers (all models, adv(4) and adw(4) drivers)

BusLogic MultiMaster ``W'' Series Host Adapters ( bt(4) driver):



BusLogic MultiMaster ``C'' Series Host Adapters ( bt(4) driver):



BusLogic MultiMaster ``S'' Series Host Adapters ( bt(4) driver):



BusLogic MultiMaster ``A'' Series Host Adapters ( bt(4) driver):



Note: BusLogic/Mylex ``Flashpoint'' adapters are not yet supported.

Note: AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported.

Note: The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported.

DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers ( dpt(4) driver)

DPT SmartRAID V and VI SCSI RAID controllers ( asr(4) driver)



AMI MegaRAID Express and Enterprise family RAID controllers ( amr(4) driver)



Note: Booting from these controllers is supported. EISA adapters are not supported.

Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware ( mlx(4) driver)



Note: Booting from these controllers is supported. EISA adapters are not supported.

Mylex PCI to SCSI RAID controllers with 6.x firmware ( mly(4) driver)



Note: Compatible Mylex controllers not listed should work, but have not been verified.

3ware Escalade ATA RAID controllers ( twe(4) driver)



LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000, 53C1000R PCI SCSI controllers, either embedded on motherboard or on add-on boards ( ncr(4) and sym(4) drivers)



NCR 53C500 based PC-Card SCSI host adapters (ncv driver)



TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters (stg driver)



Qlogic controllers and variants ( isp(4) driver)



DTC 3290 EISA SCSI controller in 1542 emulation mode.

Tekram DC390 and DC390T controllers, maybe other cards based on the AMD 53c974 as well ( amd(4) driver)

Workbit Ninja SCSI-3 based PC-Card SCSI host adapters (nsp driver)



Parallel to SCSI interfaces ( vpo(4) driver)



With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, 8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM drives. WORM devices that support CD-ROM commands are supported for read-only access by the CD-ROM drivers (such as cd(4)). WORM/CD-R/CD-RW writing support is provided by cdrecord(1), which is a part of the sysutils/cdrtools port in the Ports Collection.

The following CD-ROM type systems are supported at this time:



The following drivers were supported under the old SCSI subsystem, but are not yet supported under the new CAM SCSI subsystem:



The following device is unmaintained:




3.2 Ethernet Interfaces

Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast Ethernet controller chip ( sf(4) driver)



Allied-Telesis AT1700 and RE2000 cards ( fe(4) driver)

Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets ( ti(4) driver)



AMD PCnet NICs ( lnc(4) and pcn(4) drivers)



SMC 83c17x (EPIC)-based Ethernet NICs ( tx(4) driver)



SMC Ethernet NICs ( ed(4) driver)



RealTek RTL 8002 Pocket Ethernet ( rdp(4) driver)

RealTek 8129/8139 Fast Ethernet NICs ( rl(4) driver)



Lite-On 82c168/82c169 PNIC Fast Ethernet NICs ( dc(4) driver)



Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs ( dc(4) driver)



Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs ( dc(4) driver)



Winbond W89C840F Fast Ethernet NICs ( wb(4) driver)



VIA Technologies VT3043 ``Rhine I'' and VT86C100A ``Rhine II'' Fast Ethernet NICs ( vr(4) driver)



Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs ( sis(4) driver)

National Semiconductor DP83815 Fast Ethernet NICs ( sis(4) driver)



National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs ( nge(4) driver)



Sundance Technologies ST201 PCI Fast Ethernet NICs ( ste(4) driver)



SysKonnect SK-984x PCI Gigabit Ethernet cards ( sk(4) drivers)



Texas Instruments ThunderLAN PCI NICs ( tl(4) driver)



ADMtek Inc. AL981-based PCI Fast Ethernet NICs ( dc(4) driver)

ADMtek Inc. AN985-based PCI Fast Ethernet NICs ( dc(4) driver)



ADMtek Inc. AN986-based USB Ethernet NICs ( aue(4) driver)



CATC USB-EL1210A-based USB Ethernet NICs ( cue(4) driver)



Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs ( kue(4) driver)



ASIX Electronics AX88140A PCI NICs ( dc(4) driver)



DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) ( le(4) driver)

DEC EtherWORKS III NICs (DE203, DE204, and DE205) ( le(4) driver)

DEC Etherworks NICs (DE305) ( ed(4) driver)

DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs ( de(4) driver)



DEC/Intel 21143 based Fast Ethernet NICs ( dc(4) driver)



Davicom DM9100 and DM9102 PCI Fast Ethernet NICs ( dc(4) driver)



Fujitsu MB86960A/MB86965A based Fast Ethernet NICs ( fe(4) driver)



HP PC Lan+ cards (model numbers: 27247B and 27252A) ( ed(4) driver)

Intel EtherExpress NICs



Isolan AT 4141-0 (16 bit)

Isolink 4110 (8 bit)

Novell NE1000, NE2000, and NE2100 Ethernet interface ( ed(4) driver)

Novell NE2000 clones ( ed(4) driver)



3Com Ethernet and Fast Ethernet NICs



Crystal Semiconductor CS89x0-based NICs ( cs(4) driver)



NE2000 compatible PC-Card (PCMCIA) Ethernet and FastEthernet cards ( ed(4) driver)



Megahertz X-Jack Ethernet PC-Card CC-10BT (sn driver)

Xircom CreditCard adapters (16 bit) and workalikes (xe driver)



National Semiconductor DP8393X (SONIC) Ethernet cards (snc driver)



Gigabit Ethernet cards based on the Level 1 LXT1001 NetCellerator controller ( lge(4) driver)



Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990) chipset ( txp(4) driver)




3.3 FDDI Interfaces

DEC DEFPA/DEFEA FDDI NICs ( fpa(4) driver)


3.4 ATM Interfaces

Efficient Networks, Inc. ENI-155p ATM PCI Adapters (hea driver)

FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa driver)

The ATM support in FreeBSD supports the following signaling protocols:



Support for the IETF ``Classical IP and ARP over ATM'' model is provided, compliant with the following RFCs and Internet Drafts:



Support for an ATM sockets interface is also provided.


3.5 Wireless Network Interfaces

NCR / AT&T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards ( wl(4) driver)

Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes ( wi(4) driver)

Note: The ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver.



Aironet 802.11 wireless adapters ( an(4) driver)



Raytheon Raylink 2.4GHz wireless adapters ( ray(4) driver)



AMD Am79C930 and Harris (Intersil) based 802.11 cards (awi driver)




3.6 ISDN Interfaces

AcerISDN P10 ISA PnP (experimental)

Asuscom ISDNlink 128K ISA

ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)

AVM



Creatix



Dr. Neuhaus Niccy Go@ and compatibles

Dynalink IS64PH

Eicon Diehl DIVA 2.0 and 2.02

ELSA



ITK ix1 Micro ( < V.3, non-PnP version )

Sedlbauer Win Speed

Siemens I-Surf 2.0

TELEINT ISDN SPEED No.1 (experimental)

Teles



Traverse Technologies NETjet-S PCI

USRobotics Sportster ISDN TA intern

Winbond W6692 based PCI cards


3.7 Multi-port Serial Interfaces

AST 4 port serial card using shared IRQ

ARNET serial cards ( ar(4) driver)



Boca multi-port serial cards



Comtrol Rocketport card (rp driver)

Cyclades Cyclom-y serial board ( cy(4) driver)

STB 4 port card using shared IRQ

DigiBoard intelligent serial cards ( dgb(4) driver)



SDL Communication serial boards



Stallion Technologies multiport 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) ( si(4) driver)


3.8 Audio Devices

Advance ( sbc(4) driver)



CMedia sound chips



Crystal Semiconductor ( csa(4) driver)



ENSONIQ ( pcm(4) driver)



ESS



ForteMedia fm801

Gravis ( gusc(4) driver)



Intel 443MX, 810, 815, and 815E integrated sound devices ( pcm(4) driver)

MSS/WSS Compatible DSPs ( pcm(4) driver)

NeoMagic 256AV/ZX ( pcm(4) driver)

OPTi 931/82C931 ( pcm(4) driver)

S3 Sonicvibes

Creative Technologies SoundBlaster series ( sbc(4) driver)



Trident 4DWave DX/NX ( pcm(4) driver)

VIA Technologies VT82C686A

Yamaha




3.9 Camera and Video Capture Devices

Brooktree Bt848/849/878/879-based frame grabbers ( bktr(4) driver)



Connectix QuickCam

Cortex1 frame grabber (ctx driver)

Creative Labs Video Spigot frame grabber (spigot driver)

Matrox Meteor Video frame grabber ( meteor(4) driver)


3.10 USB Devices

A range of USB peripherals are supported; devices known to work are listed in this section. Owing to the generic nature of most USB devices, with some exceptions any device of a given class will be supported, even if not explicitly listed here.

Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.

Host Controllers ( ohci(4) and uhci(4) drivers)



USB host controllers (PCI)



Hubs



Keyboards ( ukbd(4) driver)



Miscellaneous



Modems (umodem driver)



Mice ( ums(4) driver)



Printers and parallel printer conversion cables (ulpt driver)



Scanners (through SANE) ( uscanner(4) driver)



Storage ( umass(4) driver)




3.11 Miscellaneous

FAX-Modem/PCCARD



Floppy drives ( fd(4) driver)

Genius and Mustek hand scanners

GPB and Transputer drivers

HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives

Keyboards including:



Loran-C receiver (Dave Mills experimental hardware, loran driver).

Mice including:



Parallel ports

PC-compatible joysticks ( joy(4) driver)

PHS Data Communication Card/PCCARD



Serial ports

X-10 power controllers ( tw(4) driver)

Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (xrpu driver).


4 Boot-time Kernel Configuration

This section describes the boot-time configuration of the FreeBSD kernel.


4.1 Default 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.
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.
IOMem The lowest (or starting) memory address used by the device, also shown in hexadecimal.
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 (post-4.0) framework.

Device Port IRQ DRQ IOMem Description
fdc0 3f0 6 2 n/a Floppy disk controller
ata0 170 14 n/a n/a ATA/ATAPI controller
ata1 170 15 n/a n/a ATA/ATAPI controller
atadisk0 n/a n/a n/a n/a ATA disk drives
atapicd0 n/a n/a n/a n/a ATAPI CDROM drives
atapifd0 n/a n/a n/a n/a ATAPI floppy drives
atapist0 n/a n/a n/a n/a ATAPI tape drives
adv0 n/a n/a n/a n/a AdvanSys Narrow SCSI controllers
adw0 n/a n/a n/a n/a AdvanSys Wide SCSI controllers
amd0 n/a n/a n/a n/a AMD 53C974 (Tekram DC390(T))
ncr0 n/a n/a n/a n/a NCR PCI SCSI controller
bt0 330 dyn dyn dyn Buslogic SCSI controller
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/AIC-6260 SCSI controller
isp0 dyn dyn dyn dyn QLogic 10X0, 1240 Ultra SCSI, 1080/1280 Ultra2 SCSI, 12160 Ultra3 SCSI, 2X00 Fibre Channel SCSI controller
dpt0 dyn dyn n/a n/a DPT RAID SCSI controllers
amr0 dyn dyn n/a n/a AMI MegaRAID controllers
mlx0 dyn dyn n/a dyn Mylex DAC960 RAID controllers
twe0 dyn dyn n/a n/a 3ware Escalade RAID controllers
asr0 dyn dyn dyn dyn DPT SmartRaid V, VI, and Adaptec SCSI RAID
mly0 dyn dyn dyn dyn Mylex AcceleRAID/eXtremeRAID
aac dyn dyn dyn dyn Adaptec FSA family PCI SCSI RAID
ncv dyn dyn n/a n/a NCR 53C500 based PC-Card SCSI
nsp dyn dyn n/a dyn Workbit Ninja SCSI-3 based PC-Card SCSI
stg dyn dyn n/a n/a TMC 18C30/50 based ISA/PC-Card SCSI
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)
ppc0 dyn 7 n/a n/a Printer ports
dc0 n/a n/a n/a n/a DEC/Intel 21143 cards and workalikes
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+
ep0 300 10 dyn dyn 3Com 3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572, 3C574X, 3C579, 3C589
ex0 dyn dyn dyn n/a Intel EtherExpress Pro/10 cards
fe0 300 dyn n/a n/a Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180 series cards.
fxp0 dyn dyn n/a dyn Intel EtherExpress Pro/100B and Intel PRO/100+ Management Adapter
ie0 300 10 dyn d0000 AT&T StarLAN 10 and EN100; 3Com 3C507; NI5210; Intel EtherExpress (8/16,16[TP]) 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)
pcn0 dyn dyn n/a dyn AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA cards
rl0 dyn dyn n/a dyn RealTek 8129/8139 fast ethernet
sf0 dyn dyn n/a dyn Adaptec AIC-6915 fast ethernet
sis0 dyn dyn n/a dyn SiS 900/SiS 7016 fast ethernet
sn0 0x300 10 n/a n/a SMC 91xx ethernet
ste0 dyn dyn n/a dyn Sundance ST201 fast ethernet
tl0 dyn dyn n/a dyn TI TNET100 'ThunderLAN' cards.
tx0 dyn dyn n/a dyn SMC 9432 'Epic' fast ethernet
wb0 dyn dyn n/a dyn Winbond W89C840F PCI based cards.
vr0 dyn dyn n/a dyn VIA VT3043/VT86C100A PCI based cards.
vx0 dyn dyn n/a dyn 3Com 3c59x ((Fast) Etherlink III)
xe0 dyn dyn n/a dyn Xircom CreditCard adapters (16 bit)
xl0 dyn dyn n/a dyn 3Com 3c900, 3c905, 3c905B, 3c905C, 3c980, 3cSOHO100 ((Fast) Etherlink XL)
cs0 0x300 dyn n/a n/a Crystal Semiconductor CS89x0-based cards.


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.


4.2 Using UserConfig to change FreeBSD kernel settings

Note: The markup for this section leaves a lot to be desired.

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 tool 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 :
    
    
    ---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:



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, Microchannel and EISA devices can be probed reliably, therefore they are not shown in the table above nor can their settings be changed using UserConfig.


This file, and other release-related documents, can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/.

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.

All users of FreeBSD 4-STABLE should subscribe to the <stable@FreeBSD.org> mailing list.

For questions about this documentation, e-mail <doc@FreeBSD.org>.



++++