From 7cfe00c079fc5e6996aff9ad21295b4ca70b0016 Mon Sep 17 00:00:00 2001 From: Hiroki Sato Date: Fri, 18 Jan 2008 17:05:09 +0000 Subject: [PATCH] Remove ia64 docs. --- en/releases/6.3R/Makefile | 5 +- en/releases/6.3R/hardware-ia64.html | 2999 ----------------------- en/releases/6.3R/hardware.sgml | 3 +- en/releases/6.3R/installation-ia64.html | 895 ------- en/releases/6.3R/installation.sgml | 3 +- en/releases/6.3R/relnotes-ia64.html | 608 ----- en/releases/6.3R/relnotes.sgml | 3 +- 7 files changed, 4 insertions(+), 4512 deletions(-) delete mode 100644 en/releases/6.3R/hardware-ia64.html delete mode 100644 en/releases/6.3R/installation-ia64.html delete mode 100644 en/releases/6.3R/relnotes-ia64.html diff --git a/en/releases/6.3R/Makefile b/en/releases/6.3R/Makefile index eadec6a9f1..1b894d2b75 100644 --- a/en/releases/6.3R/Makefile +++ b/en/releases/6.3R/Makefile @@ -1,4 +1,4 @@ -# $FreeBSD: www/en/releases/6.3R/Makefile,v 1.1 2007/11/25 05:26:46 kensmith Exp $ +# $FreeBSD: www/en/releases/6.3R/Makefile,v 1.2 2008/01/17 16:13:58 hrs Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" @@ -20,20 +20,17 @@ DOCS+= schedule.sgml DATA+= errata.html DATA+= hardware-alpha.html DATA+= hardware-amd64.html -DATA+= hardware-ia64.html DATA+= hardware-i386.html DATA+= hardware-pc98.html DATA+= hardware-sparc64.html DATA+= installation-alpha.html DATA+= installation-amd64.html -DATA+= installation-ia64.html DATA+= installation-i386.html DATA+= installation-pc98.html DATA+= installation-sparc64.html DATA+= readme.html DATA+= relnotes-alpha.html DATA+= relnotes-amd64.html -DATA+= relnotes-ia64.html DATA+= relnotes-i386.html DATA+= relnotes-pc98.html DATA+= relnotes-sparc64.html diff --git a/en/releases/6.3R/hardware-ia64.html b/en/releases/6.3R/hardware-ia64.html deleted file mode 100644 index 4a50bd273a..0000000000 --- a/en/releases/6.3R/hardware-ia64.html +++ /dev/null @@ -1,2999 +0,0 @@ - - - - -FreeBSD/ia64 6.3-RELEASE Hardware Notes - - - - - -
-
-

FreeBSD/ia64 6.3-RELEASE Hardware -Notes

- -

The FreeBSD Documentation Project

- -

Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The -FreeBSD Documentation Project

- -
-
- -
-
-
Table of Contents
- -
1 Introduction
- -
2 Supported Processors and Motherboards
- -
-
-
2.1 Supported Devices Overview
-
-
- -
3 Supported Devices
- -
-
-
3.1 Disk Controllers
- -
3.2 Ethernet Interfaces
- -
3.3 Token Ring Interfaces
- -
3.4 FDDI Interfaces
- -
3.5 ATM Interfaces
- -
3.6 Wireless Network Interfaces
- -
3.7 Miscellaneous Networks
- -
3.8 ISDN Interfaces
- -
3.9 Serial Interfaces
- -
3.10 Sound Devices
- -
3.11 Camera and Video Capture Devices
- -
3.12 USB Devices
- -
3.13 IEEE 1394 (Firewire) Devices
- -
3.14 Bluetooth Devices
- -
3.15 Cryptographic Accelerators
- -
3.16 Miscellaneous
-
-
-
-
- -
-
-

This is a preliminary document. It is incomplete, and in need of additional content. -Please send additional information on IA-64 processors, motherboards, and various devices -working on FreeBSD to the FreeBSD IA64 -porting mailing list.

-
-
- -
-
-

1 Introduction

- -

This document contains the hardware compatibility notes for FreeBSD 6.3-RELEASE on the -IA-64 hardware platform (also referred to as FreeBSD/ia64 6.3-RELEASE). 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 IA-64 hardware -platform. Versions of the hardware compatibility notes for other architectures will -differ in some details.

-
-
- -

More information on FreeBSD/ia64 is contained on the FreeBSD/ia64 -Project page.

-
- -
-
-

2 Supported Processors and -Motherboards

- -

Currently supported processors are the Itanium and the Itanium 2.

- -

Supported chipsets include:

- -
    -
  • -

    HP zx1

    -
    • - -
  • -

    Intel 460GX

    -
    • - -
  • -

    Intel E8870

    -
    • -
- -

Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are -supported.

- -
-
-

2.1 Supported Devices Overview

- -

Most devices that can be found in or are compatible with ia64 machines are fully -supported. The notable exception is the VGA console. The FreeBSD support for VGA consoles -is at this time too much based on PC hardware and not all ia64 machines have chipsets -that provide sufficient PC legacy support. As such -syscons(4) can -not be enabled and the use of a serial console is required.

-
-
- -
-
-

3 Supported Devices

- -$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.282.2.17 -2007/09/13 16:25:43 brueffer Exp $ - -

This section describes the devices currently known to be supported by with FreeBSD on -the IA-64 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. Information on specific models of supported devices, -controllers, etc. can be found in the manual pages.

- -
-
-

Note: The device lists in this document are being generated automatically from -FreeBSD manual pages. This means that some devices, which are supported by multiple -drivers, may appear multiple times.

-
-
- -
-
-

3.1 Disk Controllers

- -

IDE/ATA controllers ( -ata(4) -driver)

- -

Controllers supported by the -aac(4) driver -include:

- -
    -
  • -

    Adaptec AAC-364

    -
    • - -
  • -

    Adaptec RAID 3085

    -
    • - -
  • -

    Adaptec RAID 31205

    -
    • - -
  • -

    Adaptec RAID 31605

    -
    • - -
  • -

    Adaptec RAID 5085

    -
    • - -
  • -

    Adaptec RAID 51205

    -
    • - -
  • -

    Adaptec RAID 51245

    -
    • - -
  • -

    Adaptec RAID 51605

    -
    • - -
  • -

    Adaptec RAID 51645

    -
    • - -
  • -

    Adaptec RAID 52445

    -
    • - -
  • -

    Adaptec RAID 5405

    -
    • - -
  • -

    Adaptec RAID 5445

    -
    • - -
  • -

    Adaptec RAID 5805

    -
    • - -
  • -

    Adaptec SAS RAID 3405

    -
    • - -
  • -

    Adaptec SAS RAID 3805

    -
    • - -
  • -

    Adaptec SAS RAID 4000SAS

    -
    • - -
  • -

    Adaptec SAS RAID 4005SAS

    -
    • - -
  • -

    Adaptec SAS RAID 4800SAS

    -
    • - -
  • -

    Adaptec SAS RAID 4805SAS

    -
    • - -
  • -

    Adaptec SATA RAID 2020SA ZCR

    -
    • - -
  • -

    Adaptec SATA RAID 2025SA ZCR

    -
    • - -
  • -

    Adaptec SATA RAID 2026ZCR

    -
    • - -
  • -

    Adaptec SATA RAID 2410SA

    -
    • - -
  • -

    Adaptec SATA RAID 2420SA

    -
    • - -
  • -

    Adaptec SATA RAID 2610SA

    -
    • - -
  • -

    Adaptec SATA RAID 2620SA

    -
    • - -
  • -

    Adaptec SATA RAID 2810SA

    -
    • - -
  • -

    Adaptec SATA RAID 2820SA

    -
    • - -
  • -

    Adaptec SATA RAID 21610SA

    -
    • - -
  • -

    Adaptec SCSI RAID 2020ZCR

    -
    • - -
  • -

    Adaptec SCSI RAID 2025ZCR

    -
    • - -
  • -

    Adaptec SCSI RAID 2120S

    -
    • - -
  • -

    Adaptec SCSI RAID 2130S

    -
    • - -
  • -

    Adaptec SCSI RAID 2130SLP

    -
    • - -
  • -

    Adaptec SCSI RAID 2230SLP

    -
    • - -
  • -

    Adaptec SCSI RAID 2200S

    -
    • - -
  • -

    Adaptec SCSI RAID 2240S

    -
    • - -
  • -

    Adaptec SCSI RAID 3230S

    -
    • - -
  • -

    Adaptec SCSI RAID 3240S

    -
    • - -
  • -

    Adaptec SCSI RAID 5400S

    -
    • - -
  • -

    Dell CERC SATA RAID 2

    -
    • - -
  • -

    Dell PERC 2/Si

    -
    • - -
  • -

    Dell PERC 2/QC

    -
    • - -
  • -

    Dell PERC 3/Si

    -
    • - -
  • -

    Dell PERC 3/Di

    -
    • - -
  • -

    Dell PERC 320/DC

    -
    • - -
  • -

    HP ML110 G2 (Adaptec SATA RAID 2610SA)

    -
    • - -
  • -

    HP NetRAID 4M

    -
    • - -
  • -

    IBM ServeRAID 8i

    -
    • - -
  • -

    IBM ServeRAID 8k

    -
    • - -
  • -

    IBM ServeRAID 8s

    -
    • - -
  • -

    ICP RAID ICP5045BL

    -
    • - -
  • -

    ICP RAID ICP5085BL

    -
    • - -
  • -

    ICP RAID ICP5085SL

    -
    • - -
  • -

    ICP RAID ICP5125BR

    -
    • - -
  • -

    ICP RAID ICP5125SL

    -
    • - -
  • -

    ICP RAID ICP5165BR

    -
    • - -
  • -

    ICP RAID ICP5165SL

    -
    • - -
  • -

    ICP RAID ICP5445SL

    -
    • - -
  • -

    ICP RAID ICP5805BL

    -
    • - -
  • -

    ICP RAID ICP5805SL

    -
    • - -
  • -

    ICP ICP5085BR SAS RAID

    -
    • - -
  • -

    ICP ICP9085LI SAS RAID

    -
    • - -
  • -

    ICP ICP9047MA SATA RAID

    -
    • - -
  • -

    ICP ICP9067MA SATA RAID

    -
    • - -
  • -

    ICP ICP9087MA SATA RAID

    -
    • - -
  • -

    ICP ICP9014RO SCSI RAID

    -
    • - -
  • -

    ICP ICP9024RO SCSI RAID

    -
    • - -
  • -

    Legend S220

    -
    • - -
  • -

    Legend S230

    -
    • - -
  • -

    Sun STK RAID REM

    -
    • - -
  • -

    Sun STK RAID EM

    -
    • - -
  • -

    SG-XPCIESAS-R-IN

    -
    • - -
  • -

    SG-XPCIESAS-R-EX

    -
    • - -
  • -

    AOC-USAS-S4i

    -
    • - -
  • -

    AOC-USAS-S8i

    -
    • - -
  • -

    AOC-USAS-S4iR

    -
    • - -
  • -

    AOC-USAS-S8iR

    -
    • - -
  • -

    AOC-USAS-S8i-LP

    -
    • - -
  • -

    AOC-USAS-S8iR-LP

    -
    • -
- -

The -ahc(4) driver -supports the following SCSI host adapter chips and SCSI controller cards:

- -
    -
  • -

    Adaptec AIC7770 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7850 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7860 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7870 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7880 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7890 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7891 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7892 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7895 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7896 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7897 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7899 host adapter chip

    -
    • - -
  • -

    Adaptec 274X(W)

    -
    • - -
  • -

    Adaptec 274X(T)

    -
    • - -
  • -

    Adaptec 284X

    -
    • - -
  • -

    Adaptec 2910

    -
    • - -
  • -

    Adaptec 2915

    -
    • - -
  • -

    Adaptec 2920

    -
    • - -
  • -

    Adaptec 2930C

    -
    • - -
  • -

    Adaptec 2930U2

    -
    • - -
  • -

    Adaptec 2940

    -
    • - -
  • -

    Adaptec 2940J

    -
    • - -
  • -

    Adaptec 2940N

    -
    • - -
  • -

    Adaptec 2940U

    -
    • - -
  • -

    Adaptec 2940AU

    -
    • - -
  • -

    Adaptec 2940UW

    -
    • - -
  • -

    Adaptec 2940UW Dual

    -
    • - -
  • -

    Adaptec 2940UW Pro

    -
    • - -
  • -

    Adaptec 2940U2W

    -
    • - -
  • -

    Adaptec 2940U2B

    -
    • - -
  • -

    Adaptec 2950U2W

    -
    • - -
  • -

    Adaptec 2950U2B

    -
    • - -
  • -

    Adaptec 19160B

    -
    • - -
  • -

    Adaptec 29160B

    -
    • - -
  • -

    Adaptec 29160N

    -
    • - -
  • -

    Adaptec 3940

    -
    • - -
  • -

    Adaptec 3940U

    -
    • - -
  • -

    Adaptec 3940AU

    -
    • - -
  • -

    Adaptec 3940UW

    -
    • - -
  • -

    Adaptec 3940AUW

    -
    • - -
  • -

    Adaptec 3940U2W

    -
    • - -
  • -

    Adaptec 3950U2

    -
    • - -
  • -

    Adaptec 3960

    -
    • - -
  • -

    Adaptec 39160

    -
    • - -
  • -

    Adaptec 3985

    -
    • - -
  • -

    Adaptec 4944UW

    -
    • - -
  • -

    NEC PC-9821Xt13 (PC-98)

    -
    • - -
  • -

    NEC RvII26 (PC-98)

    -
    • - -
  • -

    NEC PC-9821X-B02L/B09 (PC-98)

    -
    • - -
  • -

    NEC SV-98/2-B03 (PC-98)

    -
    • - -
  • -

    Many motherboards with on-board SCSI support

    -
    • -
- -

The -ahd(4) driver -supports the following:

- -
    -
  • -

    Adaptec AIC7901 host adapter chip

    -
    • - -
  • -

    Adaptec AIC7901A host adapter chip

    -
    • - -
  • -

    Adaptec AIC7902 host adapter chip

    -
    • - -
  • -

    Adaptec 29320 host adapter

    -
    • - -
  • -

    Adaptec 39320 host adapter

    -
    • - -
  • -

    Many motherboards with on-board SCSI support

    -
    • -
- -

Controllers supported by the -amr(4) driver -include:

- -
    -
  • -

    MegaRAID SATA 150-4

    -
    • - -
  • -

    MegaRAID SATA 150-6

    -
    • - -
  • -

    MegaRAID SATA 300-4X

    -
    • - -
  • -

    MegaRAID SATA 300-8X

    -
    • - -
  • -

    MegaRAID SCSI 320-1E

    -
    • - -
  • -

    MegaRAID SCSI 320-2E

    -
    • - -
  • -

    MegaRAID SCSI 320-4E

    -
    • - -
  • -

    MegaRAID SCSI 320-0X

    -
    • - -
  • -

    MegaRAID SCSI 320-2X

    -
    • - -
  • -

    MegaRAID SCSI 320-4X

    -
    • - -
  • -

    MegaRAID SCSI 320-0

    -
    • - -
  • -

    MegaRAID SCSI 320-1

    -
    • - -
  • -

    MegaRAID SCSI 320-2

    -
    • - -
  • -

    MegaRAID SCSI 320-4

    -
    • - -
  • -

    MegaRAID Series 418

    -
    • - -
  • -

    MegaRAID i4 133 RAID

    -
    • - -
  • -

    MegaRAID Elite 1500 (Series 467)

    -
    • - -
  • -

    MegaRAID Elite 1600 (Series 493)

    -
    • - -
  • -

    MegaRAID Elite 1650 (Series 4xx)

    -
    • - -
  • -

    MegaRAID Enterprise 1200 (Series 428)

    -
    • - -
  • -

    MegaRAID Enterprise 1300 (Series 434)

    -
    • - -
  • -

    MegaRAID Enterprise 1400 (Series 438)

    -
    • - -
  • -

    MegaRAID Enterprise 1500 (Series 467)

    -
    • - -
  • -

    MegaRAID Enterprise 1600 (Series 471)

    -
    • - -
  • -

    MegaRAID Express 100 (Series 466WS)

    -
    • - -
  • -

    MegaRAID Express 200 (Series 466)

    -
    • - -
  • -

    MegaRAID Express 300 (Series 490)

    -
    • - -
  • -

    MegaRAID Express 500 (Series 475)

    -
    • - -
  • -

    Dell PERC

    -
    • - -
  • -

    Dell PERC 2/SC

    -
    • - -
  • -

    Dell PERC 2/DC

    -
    • - -
  • -

    Dell PERC 3/DCL

    -
    • - -
  • -

    Dell PERC 3/QC

    -
    • - -
  • -

    Dell PERC 4/DC

    -
    • - -
  • -

    Dell PERC 4/IM

    -
    • - -
  • -

    Dell PERC 4/SC

    -
    • - -
  • -

    Dell PERC 4/Di

    -
    • - -
  • -

    Dell PERC 4e/DC

    -
    • - -
  • -

    Dell PERC 4e/Di

    -
    • - -
  • -

    Dell PERC 4e/Si

    -
    • - -
  • -

    Dell PERC 4ei

    -
    • - -
  • -

    HP NetRAID-1/Si

    -
    • - -
  • -

    HP NetRAID-3/Si (D4943A)

    -
    • - -
  • -

    HP Embedded NetRAID

    -
    • - -
  • -

    Intel RAID Controller SRCS16

    -
    • - -
  • -

    Intel RAID Controller SRCU42X

    -
    • -
- -

Controllers supported by the -ciss(4) driver -include:

- -
    -
  • -

    Compaq Smart Array 5300

    -
    • - -
  • -

    Compaq Smart Array 532

    -
    • - -
  • -

    Compaq Smart Array 5i

    -
    • - -
  • -

    HP Smart Array 5312

    -
    • - -
  • -

    HP Smart Array 6i

    -
    • - -
  • -

    HP Smart Array 641

    -
    • - -
  • -

    HP Smart Array 642

    -
    • - -
  • -

    HP Smart Array 6400

    -
    • - -
  • -

    HP Smart Array 6400 EM

    -
    • - -
  • -

    HP Smart Array E200

    -
    • - -
  • -

    HP Smart Array E200i

    -
    • - -
  • -

    HP Smart Array P400

    -
    • - -
  • -

    HP Smart Array P400i

    -
    • - -
  • -

    HP Smart Array P600

    -
    • - -
  • -

    HP Smart Array P800

    -
    • - -
  • -

    HP Modular Smart Array 20 (MSA20)

    -
    • - -
  • -

    HP Modular Smart Array 500 (MSA500)

    -
    • -
- -

The -dpt(4) driver -provides support for the following RAID adapters:

- -
    -
  • -

    DPT Smart Cache Plus

    -
    • - -
  • -

    Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)

    -
    • - -
  • -

    Smart RAID II (PM3?2?, PM3021, PM3222)

    -
    • - -
  • -

    Smart Cache III (PM2?3?)

    -
    • - -
  • -

    Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)

    -
    • - -
  • -

    Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)

    -
    • - -
  • -

    Smart RAID IV

    -
    • -
- -

Controllers supported by the -iir(4) driver -include:

- -
    -
  • -

    Intel RAID Controller SRCMR

    -
    • - -
  • -

    Intel Server RAID Controller U3-l (SRCU31a)

    -
    • - -
  • -

    Intel Server RAID Controller U3-1L (SRCU31La)

    -
    • - -
  • -

    Intel Server RAID Controller U3-2 (SRCU32)

    -
    • - -
  • -

    All past and future releases of Intel and ICP RAID Controllers.

    -
    • -
- -
    -
  • -

    Intel RAID Controller SRCU21 (discontinued)

    -
    • - -
  • -

    Intel RAID Controller SRCU31 (older revision, not compatible)

    -
    • - -
  • -

    Intel RAID Controller SRCU31L (older revision, not compatible)

    -
    • -
- -

The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.

- -

Cards supported by the -isp(4) driver -include:

- -
    -
  • -

    ISP1000

    -
    • - -
  • -

    ISP1020

    -
    • - -
  • -

    ISP1040

    -
    • - -
  • -

    Qlogic 1240

    -
    • - -
  • -

    Qlogic 1020

    -
    • - -
  • -

    Qlogic 1040

    -
    • - -
  • -

    Qlogic 1080

    -
    • - -
  • -

    Qlogic 1280

    -
    • - -
  • -

    Qlogic 12160

    -
    • - -
  • -

    Qlogic 210X

    -
    • - -
  • -

    Qlogic 220X

    -
    • - -
  • -

    Qlogic 2300

    -
    • - -
  • -

    Qlogic 2312

    -
    • - -
  • -

    Qlogic 234X

    -
    • - -
  • -

    Qlogic 2322

    -
    • - -
  • -

    Qlogic 200

    -
    • - -
  • -

    Qlogic 2422

    -
    • - -
  • -

    Qlogic 2432

    -
    • -
- -

The -mfi(4) driver -supports the following hardware:

- -
    -
  • -

    LSI MegaRAID SAS 8408E

    -
    • - -
  • -

    LSI MegaRAID SAS 8480E

    -
    • - -
  • -

    Dell PERC5/i

    -
    • -
- -

Controllers supported by the -mlx(4) driver -include:

- -
    -
  • -

    Mylex DAC960P

    -
    • - -
  • -

    Mylex DAC960PD / DEC KZPSC (Fast Wide)

    -
    • - -
  • -

    Mylex DAC960PDU

    -
    • - -
  • -

    Mylex DAC960PL

    -
    • - -
  • -

    Mylex DAC960PJ

    -
    • - -
  • -

    Mylex DAC960PG

    -
    • - -
  • -

    Mylex DAC960PU / DEC PZPAC (Ultra Wide)

    -
    • - -
  • -

    Mylex AcceleRAID 150 (DAC960PRL)

    -
    • - -
  • -

    Mylex AcceleRAID 250 (DAC960PTL1)

    -
    • - -
  • -

    Mylex eXtremeRAID 1100 (DAC1164P)

    -
    • - -
  • -

    RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA -(3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)

    -
    • -
- -

All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is -always advisable to upgrade to the most recent firmware available for the controller. -Compatible Mylex controllers not listed should work, but have not been verified.

- -

Controllers supported by the -mly(4) driver -include:

- -
    -
  • -

    Mylex AcceleRAID 160

    -
    • - -
  • -

    Mylex AcceleRAID 170

    -
    • - -
  • -

    Mylex AcceleRAID 352

    -
    • - -
  • -

    Mylex eXtremeRAID 2000

    -
    • - -
  • -

    Mylex eXtremeRAID 3000

    -
    • -
- -

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

- -

The following controllers are supported by the -mpt(4) -driver:

- -
    -
  • -

    LSI Logic 53c1030, LSI Logic LSI2x320-X (Single and Dual Ultra320 SCSI)

    -
    • - -
  • -

    LSI Logic AS1064, LSI Logic AS1068

    -
    • - -
  • -

    LSI Logic FC909 (1Gb/s Fibre Channel)

    -
    • - -
  • -

    LSI Logic FC909A (Dual 1Gb/s Fibre Channel)

    -
    • - -
  • -

    LSI Logic FC919, LSI Logic 7102XP-LC (Single 2Gb/s Fibre Channel)

    -
    • - -
  • -

    LSI Logic FC929, LSI Logic FC929X, LSI Logic 7202XP-LC (Dual 2Gb/s Fibre Channel)

    -
    • - -
  • -

    LSI Logic FC949X (Dual 4Gb/s Fibre Channel)

    -
    • - -
  • -

    LSI Logic FC949ES (Dual 4Gb/s Fibre Channel PCI-Express)

    -
    • -
- -

The Ultra 320 SCSI controller chips supported by the -mpt(4) driver -can be found onboard on many systems including:

- -
    -
  • -

    Dell PowerEdge 1750 thru 2850

    -
    • - -
  • -

    IBM eServer xSeries 335

    -
    • -
- -

These systems also contain Integrated Raid Mirroring and Integrated Raid Mirroring -Enhanced which this driver also supports. The SAS controller chips are also present on -many new AMD/Opteron based systems, like the Sun 4100. Note that this controller can -drive both SAS and SATA drives or a mix of them at the same time. The Integrated Raid -Mirroring available for these controllers is poorly supported at best. The Fibre Channel -controller chipset are supported by a broad variety of speeds and systems. The Apple -Fibre Channel HBA is in fact the FC949ES card. This driver also supports target mode for -Fibre Channel cards. This support may be enabled by setting the desired role of the core -via the LSI Logic firmware utility that establishes what roles the card can take on - no -separate compilation is required.

- -

The -sym(4) driver -provides support for the following Symbios/LSI Logic PCI SCSI controllers:

- -
    -
  • -

    53C810

    -
    • - -
  • -

    53C810A

    -
    • - -
  • -

    53C815

    -
    • - -
  • -

    53C825

    -
    • - -
  • -

    53C825A

    -
    • - -
  • -

    53C860

    -
    • - -
  • -

    53C875

    -
    • - -
  • -

    53C876

    -
    • - -
  • -

    53C895

    -
    • - -
  • -

    53C895A

    -
    • - -
  • -

    53C896

    -
    • - -
  • -

    53C897

    -
    • - -
  • -

    53C1000

    -
    • - -
  • -

    53C1000R

    -
    • - -
  • -

    53C1010-33

    -
    • - -
  • -

    53C1010-66

    -
    • - -
  • -

    53C1510D

    -
    • -
- -

The SCSI controllers supported by -sym(4) can be -either embedded on a motherboard, or on one of the following add-on boards:

- -
    -
  • -

    ASUS SC-200, SC-896

    -
    • - -
  • -

    Data Technology DTC3130 (all variants)

    -
    • - -
  • -

    DawiControl DC2976UW

    -
    • - -
  • -

    Diamond FirePort (all)

    -
    • - -
  • -

    I-O DATA SC-UPCI (PC-98)

    -
    • - -
  • -

    Logitec LHA-521UA (PC-98)

    -
    • - -
  • -

    NCR cards (all)

    -
    • - -
  • -

    Symbios cards (all)

    -
    • - -
  • -

    Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W

    -
    • - -
  • -

    Tyan S1365

    -
    • -
- -

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:

- -
    -
  • -

    SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (cd(4))

    -
    • - -
  • -

    ATAPI IDE interface ( -acd(4))

    -
    • -
- -
-
-
- -
-
-

3.2 Ethernet Interfaces

- -

Adapters supported by the -aue(4) driver -include:

- -
    -
  • -

    Abocom UFE1000, DSB650TX_NA

    -
    • - -
  • -

    Accton USB320-EC, SpeedStream

    -
    • - -
  • -

    ADMtek AN986, AN8511

    -
    • - -
  • -

    Billionton USB100, USB100LP, USB100EL, USBE100

    -
    • - -
  • -

    Corega Ether FEther USB-T, FEther USB-TX, FEther USB-TXS

    -
    • - -
  • -

    D-Link DSB-650, DSB-650TX, DSB-650TX-PNA

    -
    • - -
  • -

    Elecom LD-USBL/TX

    -
    • - -
  • -

    Elsa Microlink USB2Ethernet

    -
    • - -
  • -

    HP hn210e

    -
    • - -
  • -

    I-O Data USB ETTX

    -
    • - -
  • -

    Kingston KNU101TX

    -
    • - -
  • -

    LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, -USB100TX, USB100H1

    -
    • - -
  • -

    MELCO LUA-TX, LUA2-TX

    -
    • - -
  • -

    Netgear FA101

    -
    • - -
  • -

    Planex UE-200TX

    -
    • - -
  • -

    Sandberg USB to Network Link (model number 133-06)

    -
    • - -
  • -

    Siemens Speedstream

    -
    • - -
  • -

    SmartBridges smartNIC

    -
    • - -
  • -

    SMC 2202USB

    -
    • - -
  • -

    SOHOware NUB100

    -
    • -
- -

The -bge(4) driver -provides support for various NICs based on the Broadcom BCM570x family of Gigabit -Ethernet controller chips, including the following:

- -
    -
  • -

    3Com 3c996-SX (1000baseSX)

    -
    • - -
  • -

    3Com 3c996-T (10/100/1000baseTX)

    -
    • - -
  • -

    Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)

    -
    • - -
  • -

    Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)

    -
    • - -
  • -

    Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)

    -
    • - -
  • -

    IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)

    -
    • - -
  • -

    HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)

    -
    • - -
  • -

    HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)

    -
    • - -
  • -

    HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)

    -
    • - -
  • -

    HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)

    -
    • - -
  • -

    Netgear GA302T (10/100/1000baseTX)

    -
    • - -
  • -

    SysKonnect SK-9D21 (10/100/1000baseTX)

    -
    • - -
  • -

    SysKonnect SK-9D41 (1000baseSX)

    -
    • -
- -

The -cue(4) driver -supports CATC USB-EL1210A based USB Ethernet adapters including:

- -
    -
  • -

    Belkin F5U011/F5U111

    -
    • - -
  • -

    CATC Netmate

    -
    • - -
  • -

    CATC Netmate II

    -
    • - -
  • -

    SmartBridges SmartLink

    -
    • -
- -

The dc(4) driver provides -support for the following chipsets:

- -
    -
  • -

    DEC/Intel 21143

    -
    • - -
  • -

    ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II

    -
    • - -
  • -

    ASIX Electronics AX88140A and AX88141

    -
    • - -
  • -

    Conexant LANfinity RS7112 (miniPCI)

    -
    • - -
  • -

    Davicom DM9009, DM9100, DM9102 and DM9102A

    -
    • - -
  • -

    Lite-On 82c168 and 82c169 PNIC

    -
    • - -
  • -

    Lite-On/Macronix 82c115 PNIC II

    -
    • - -
  • -

    Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732

    -
    • - -
  • -

    Xircom X3201 (cardbus only)

    -
    • -
- -

The following NICs are known to work with the dc(4) driver at this -time:

- -
    -
  • -

    3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)

    -
    • - -
  • -

    Abocom FE2500

    -
    • - -
  • -

    Accton EN1217 (98715A)

    -
    • - -
  • -

    Accton EN2242 MiniPCI

    -
    • - -
  • -

    Adico AE310TX (98715A)

    -
    • - -
  • -

    Alfa Inc GFC2204 (ASIX AX88140A)

    -
    • - -
  • -

    Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, -non-MII)

    -
    • - -
  • -

    Built in DE500-BA on DEC Alpha workstations (21143, non-MII)

    -
    • - -
  • -

    Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, -MII)

    -
    • - -
  • -

    Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)

    -
    • - -
  • -

    CNet Pro110B (ASIX AX88140A)

    -
    • - -
  • -

    CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)

    -
    • - -
  • -

    Compex RL100-TX (98713 or 98713A)

    -
    • - -
  • -

    D-Link DFE-570TX (21143, MII, quad port)

    -
    • - -
  • -

    Digital DE500-BA 10/100 (21143, non-MII)

    -
    • - -
  • -

    ELECOM Laneed LD-CBL/TXA (ADMtek AN985)

    -
    • - -
  • -

    Hawking CB102 CardBus

    -
    • - -
  • -

    IBM EtherJet Cardbus Adapter

    -
    • - -
  • -

    Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)

    -
    • - -
  • -

    Jaton XpressNet (Davicom DM9102)

    -
    • - -
  • -

    Kingston KNE100TX (21143, MII)

    -
    • - -
  • -

    Kingston KNE110TX (PNIC 82c169)

    -
    • - -
  • -

    LinkSys LNE100TX (PNIC 82c168, 82c169)

    -
    • - -
  • -

    LinkSys LNE100TX v2.0 (PNIC II 82c115)

    -
    • - -
  • -

    LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)

    -
    • - -
  • -

    Matrox FastNIC 10/100 (PNIC 82c168, 82c169)

    -
    • - -
  • -

    Melco LGY-PCI-TXL

    -
    • - -
  • -

    Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)

    -
    • - -
  • -

    Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)

    -
    • - -
  • -

    NDC SOHOware SFA110A (98713A)

    -
    • - -
  • -

    NDC SOHOware SFA110A Rev B4 (98715AEC-C)

    -
    • - -
  • -

    NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)

    -
    • - -
  • -

    Netgear FA511

    -
    • - -
  • -

    PlaneX FNW-3602-T (ADMtek AN985)

    -
    • - -
  • -

    SMC EZ Card 10/100 1233A-TX (ADMtek AN985)

    -
    • - -
  • -

    SVEC PN102-TX (98713)

    -
    • - -
  • -

    Xircom Cardbus Realport

    -
    • - -
  • -

    Xircom Cardbus Ethernet 10/100

    -
    • - -
  • -

    Xircom Cardbus Ethernet II 10/100

    -
    • -
- -

Adapters supported by the de(4) driver -include:

- -
    -
  • -

    Adaptec ANA-6944/TX

    -
    • - -
  • -

    Cogent EM100FX and EM440TX

    -
    • - -
  • -

    Corega FastEther PCI-TX

    -
    • - -
  • -

    D-Link DFE-500TX

    -
    • - -
  • -

    DEC DE435, DEC DE450, and DEC DE500

    -
    • - -
  • -

    ELECOM LD-PCI2T, LD-PCITS

    -
    • - -
  • -

    I-O DATA LA2/T-PCI

    -
    • - -
  • -

    SMC Etherpower 8432, 9332 and 9334

    -
    • - -
  • -

    ZNYX ZX3xx

    -
    • -
- -

The em(4) driver supports -Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, -82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller -chips:

- -
    -
  • -

    Intel PRO/1000 CT Network Connection (82547)

    -
    • - -
  • -

    Intel PRO/1000 F Server Adapter (82543)

    -
    • - -
  • -

    Intel PRO/1000 Gigabit Server Adapter (82542)

    -
    • - -
  • -

    Intel PRO/1000 GT Desktop Adapter (82541PI)

    -
    • - -
  • -

    Intel PRO/1000 MF Dual Port Server Adapter (82546)

    -
    • - -
  • -

    Intel PRO/1000 MF Server Adapter (82545)

    -
    • - -
  • -

    Intel PRO/1000 MF Server Adapter (LX) (82545)

    -
    • - -
  • -

    Intel PRO/1000 MT Desktop Adapter (82540)

    -
    • - -
  • -

    Intel PRO/1000 MT Desktop Adapter (82541)

    -
    • - -
  • -

    Intel PRO/1000 MT Dual Port Server Adapter (82546)

    -
    • - -
  • -

    Intel PRO/1000 MT Quad Port Server Adapter (82546EB)

    -
    • - -
  • -

    Intel PRO/1000 MT Server Adapter (82545)

    -
    • - -
  • -

    Intel PRO/1000 T Desktop Adapter (82544)

    -
    • - -
  • -

    Intel PRO/1000 T Server Adapter (82543)

    -
    • - -
  • -

    Intel PRO/1000 XF Server Adapter (82544)

    -
    • - -
  • -

    Intel PRO/1000 XT Server Adapter (82544)

    -
    • -
- -

Adapters supported by the -fxp(4) driver -include:

- -
    -
  • -

    Intel EtherExpress PRO/10

    -
    • - -
  • -

    Intel InBusiness 10/100

    -
    • - -
  • -

    Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter

    -
    • - -
  • -

    Intel PRO/100+ Management Adapter

    -
    • - -
  • -

    Intel PRO/100 VE Desktop Adapter

    -
    • - -
  • -

    Intel PRO/100 M Desktop Adapter

    -
    • - -
  • -

    Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters

    -
    • - -
  • -

    Contec C-NET(PI)-100TX (PC-98)

    -
    • - -
  • -

    NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)

    -
    • - -
  • -

    NEC PC-9821X-B06 (PC-98)

    -
    • - -
  • -

    Many on-board network interfaces on Intel motherboards

    -
    • -
- -

The -hme(4) driver -supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server -models. Cards supported by the -hme(4) driver -include:

- -
    -
  • -

    Sun PCI SunSwift Adapter

    -
    • - -
  • -

    Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)

    -
    • - -
  • -

    Sun PCI Sun100BaseT Adapter 2.0

    -
    • - -
  • -

    Sun SBus Sun100BaseT 2.0

    -
    • - -
  • -

    Sun PCI Quad FastEthernet Controller

    -
    • - -
  • -

    Sun SBus Quad FastEthernet Controller

    -
    • -
- -

The -kue(4) driver -supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:

- -
    -
  • -

    3Com 3c19250

    -
    • - -
  • -

    3Com 3c460 HomeConnect Ethernet USB Adapter

    -
    • - -
  • -

    ADS Technologies USB-10BT

    -
    • - -
  • -

    AOX USB101

    -
    • - -
  • -

    ATen UC10T

    -
    • - -
  • -

    Abocom URE 450

    -
    • - -
  • -

    Corega USB-T

    -
    • - -
  • -

    D-Link DSB-650C

    -
    • - -
  • -

    Entrega NET-USB-E45, NET-HUB-3U1E

    -
    • - -
  • -

    I/O Data USB ETT

    -
    • - -
  • -

    Kawasaki DU-H3E

    -
    • - -
  • -

    LinkSys USB10T

    -
    • - -
  • -

    Netgear EA101

    -
    • - -
  • -

    Peracom USB Ethernet Adapter

    -
    • - -
  • -

    Psion Gold Port USB Ethernet adapter

    -
    • - -
  • -

    SMC 2102USB, 2104USB

    -
    • -
- -

The -pcn(4) driver -supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, -PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:

- -
    -
  • -

    AMD Am79C971 PCnet-FAST

    -
    • - -
  • -

    AMD Am79C972 PCnet-FAST+

    -
    • - -
  • -

    AMD Am79C973/Am79C975 PCnet-FAST III

    -
    • - -
  • -

    AMD Am79C976 PCnet-PRO

    -
    • - -
  • -

    AMD Am79C978 PCnet-Home

    -
    • - -
  • -

    Allied-Telesis LA-PCI

    -
    • -
- -

The re(4) driver supports -RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, and RTL8101E based Fast Ethernet and -Gigabit Ethernet adapters including:

- -
    -
  • -

    Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)

    -
    • - -
  • -

    Compaq Evo N1015v Integrated Ethernet (8139C+)

    -
    • - -
  • -

    Corega CG-LAPCIGT Gigabit Ethernet (8169S)

    -
    • - -
  • -

    D-Link DGE-528(T) Gigabit Ethernet (8169S)

    -
    • - -
  • -

    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

    -
    • - -
  • -

    LevelOne GNC-0105T (8169S)

    -
    • - -
  • -

    LinkSys EG1032 (32-bit PCI)

    -
    • - -
  • -

    PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)

    -
    • - -
  • -

    Xterasys XN-152 10/100/1000 NIC (8169)

    -
    • -
- -

Adapters supported by the rl(4) driver -include:

- -
    -
  • -

    Accton “Cheetah” EN1207D (MPX 5030/5038; RealTek 8139 clone)

    -
    • - -
  • -

    Allied Telesyn AT2550

    -
    • - -
  • -

    Allied Telesyn AT2500TX

    -
    • - -
  • -

    Belkin F5D5000

    -
    • - -
  • -

    BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)

    -
    • - -
  • -

    Compaq HNE-300

    -
    • - -
  • -

    CompUSA no-name 10/100 PCI Ethernet NIC

    -
    • - -
  • -

    Corega FEther CB-TXD

    -
    • - -
  • -

    Corega FEtherII CB-TXD

    -
    • - -
  • -

    D-Link DFE-528TX

    -
    • - -
  • -

    D-Link DFE-530TX+

    -
    • - -
  • -

    D-Link DFE-538TX

    -
    • - -
  • -

    D-Link DFE-690TXD

    -
    • - -
  • -

    Edimax EP-4103DL CardBus

    -
    • - -
  • -

    Encore ENL832-TX 10/100 M PCI

    -
    • - -
  • -

    Farallon NetLINE 10/100 PCI

    -
    • - -
  • -

    Genius GF100TXR

    -
    • - -
  • -

    GigaFast Ethernet EE100-AXP

    -
    • - -
  • -

    KTX-9130TX 10/100 Fast Ethernet

    -
    • - -
  • -

    LevelOne FPC-0106TX

    -
    • - -
  • -

    Longshine LCS-8038TX-R

    -
    • - -
  • -

    NDC Communications NE100TX-E

    -
    • - -
  • -

    Netronix Inc. EA-1210 NetEther 10/100

    -
    • - -
  • -

    Nortel Networks 10/100BaseTX

    -
    • - -
  • -

    OvisLink LEF-8129TX

    -
    • - -
  • -

    OvisLink LEF-8139TX

    -
    • - -
  • -

    Peppercon AG ROL-F

    -
    • - -
  • -

    Planex FNW-3603-TX

    -
    • - -
  • -

    Planex FNW-3800-TX

    -
    • - -
  • -

    SMC EZ Card 10/100 PCI 1211-TX

    -
    • - -
  • -

    SOHO (PRAGMATIC) UE-1211C

    -
    • -
- -

Adapters supported by the sf(4) driver -include:

- -
    -
  • -

    ANA-62011 64-bit single port 10/100baseTX adapter

    -
    • - -
  • -

    ANA-62022 64-bit dual port 10/100baseTX adapter

    -
    • - -
  • -

    ANA-62044 64-bit quad port 10/100baseTX adapter

    -
    • - -
  • -

    ANA-69011 32-bit single port 10/100baseTX adapter

    -
    • - -
  • -

    ANA-62020 64-bit single port 100baseFX adapter

    -
    • -
- -

The -sis(4) driver -supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and -embedded controllers, as well as Fast Ethernet adapters based on the National -Semiconductor DP83815 (MacPhyter) and DP83816 chips. Supported adapters include:

- -
    -
  • -

    @Nifty FNECHARD IFC USUP-TX

    -
    • - -
  • -

    MELCO LGY-PCI-TXC

    -
    • - -
  • -

    Netgear FA311-TX (DP83815)

    -
    • - -
  • -

    Netgear FA312-TX (DP83815)

    -
    • - -
  • -

    SiS 630, 635, and 735 motherboard chipsets

    -
    • - -
  • -

    Soekris Engineering net45xx, net48xx, lan1621, and lan1641

    -
    • -
- -

The -txp(4) driver -supports the following cards:

- -
    -
  • -

    3Com 3CR990-TX-95

    -
    • - -
  • -

    3Com 3CR990-TX-97

    -
    • - -
  • -

    3Com 3cR990B-TXM

    -
    • - -
  • -

    3Com 3CR990SVR95

    -
    • - -
  • -

    3Com 3CR990SVR97

    -
    • - -
  • -

    3Com 3cR990B-SRV

    -
    • -
- -

The vx(4) driver supports -the following cards:

- -
    -
  • -

    3Com 3c590 EtherLink III PCI

    -
    • - -
  • -

    3Com 3c592 EtherLink III EISA

    -
    • - -
  • -

    3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode

    -
    • - -
  • -

    3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode

    -
    • -
- -

The xl(4) driver supports -the following hardware:

- -
    -
  • -

    3Com 3c900-TPO

    -
    • - -
  • -

    3Com 3c900-COMBO

    -
    • - -
  • -

    3Com 3c905-TX

    -
    • - -
  • -

    3Com 3c905-T4

    -
    • - -
  • -

    3Com 3c900B-TPO

    -
    • - -
  • -

    3Com 3c900B-TPC

    -
    • - -
  • -

    3Com 3c900B-FL

    -
    • - -
  • -

    3Com 3c900B-COMBO

    -
    • - -
  • -

    3Com 3c905B-T4

    -
    • - -
  • -

    3Com 3c905B-TX

    -
    • - -
  • -

    3Com 3c905B-FX

    -
    • - -
  • -

    3Com 3c905B-COMBO

    -
    • - -
  • -

    3Com 3c905C-TX

    -
    • - -
  • -

    3Com 3c980, 3c980B, and 3c980C server adapters

    -
    • - -
  • -

    3Com 3cSOHO100-TX OfficeConnect adapters

    -
    • - -
  • -

    3Com 3c450 HomeConnect adapters

    -
    • - -
  • -

    3Com 3c555, 3c556 and 3c556B mini-PCI adapters

    -
    • - -
  • -

    3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, -3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters

    -
    • - -
  • -

    3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded -adapters

    -
    • -
- -

Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a -built-in proprietary modem. Neither the xl(4) driver nor any -other driver supports this modem.

-
- -
-
-

3.3 Token Ring Interfaces

-
- -
-
-

3.4 FDDI Interfaces

-
- -
-
-

3.5 ATM Interfaces

-
- -
-
-

3.6 Wireless Network Interfaces

- -

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter ( -ipw(4) -driver)

- -

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network -adapters ( -iwi(4) -driver)

-
- -
-
-

3.7 Miscellaneous -Networks

-
- -
-
-

3.8 ISDN Interfaces

-
- -
-
-

3.9 Serial Interfaces

- -

The -uart(4) driver -supports the following classes of UARTs:

- -
    -
  • -

    NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 -UARTs

    -
    • - -
  • -

    SAB82532: Siemens SAB 82532 based serial communications controllers in asynchronuous -mode.

    -
    • - -
  • -

    Z8530: Zilog 8530 based serial communications controllers in asynchronuous mode.

    -
    • -
- -

PCI-Based multi-port serial boards ( -puc(4) -driver)

- -
    -
  • -

    Diva Serial (GSP) Multiport UART

    -
    • -
- -
-
-
- -
-
-

3.10 Sound Devices

-
- -
-
-

3.11 Camera and Video Capture -Devices

-
- -
-
-

3.12 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.

-
-
- -
-
-

Note: USB Bluetooth adapters can be found in Bluetooth -section.

-
-
- -

The -ohci(4) driver -supports all OHCI v1.0 compliant controllers including:

- -
    -
  • -

    AcerLabs M5237 (Aladdin-V)

    -
    • - -
  • -

    AMD-756

    -
    • - -
  • -

    OPTi 82C861 (FireLink)

    -
    • - -
  • -

    NEC uPD 9210

    -
    • - -
  • -

    CMD Tech 670 (USB0670)

    -
    • - -
  • -

    CMD Tech 673 (USB0673)

    -
    • - -
  • -

    NVIDIA nForce3

    -
    • - -
  • -

    Sun PCIO-2 (RIO USB)

    -
    • -
- -

The -uhci(4) driver -supports all UHCI v1.1 compliant controllers including:

- -
    -
  • -

    Intel 82371AB/EB (PIIX4)

    -
    • - -
  • -

    Intel 82371SB (PIIX3)

    -
    • - -
  • -

    VIA 83C572

    -
    • -
- -

USB 2.0 controllers using the EHCI interface ( -ehci(4) -driver)

- -

Hubs

- -

Keyboards ( -ukbd(4) -driver)

- -

Mice ( -ums(4) -driver)

- -

The -umct(4) driver -supports the following adapters:

- -
    -
  • -

    Belkin F5U109

    -
    • - -
  • -

    Belkin F5U409

    -
    • - -
  • -

    D-Link DU-H3SP USB BAY Hub

    -
    • - -
  • -

    Magic Control Technology USB-232

    -
    • - -
  • -

    Sitecom USB-232

    -
    • -
-
- -
-
-

3.13 IEEE 1394 (Firewire) -Devices

- -

The -fwohci(4) driver -provides support for PCI/CardBus FireWire interface cards. The driver supports the -following IEEE 1394 OHCI chipsets:

- -
    -
  • -

    Adaptec AHA-894x/AIC-5800

    -
    • - -
  • -

    Apple Pangea

    -
    • - -
  • -

    Apple UniNorth

    -
    • - -
  • -

    Intel 82372FB

    -
    • - -
  • -

    IOGEAR GUF320

    -
    • - -
  • -

    Lucent / Agere FW322/323

    -
    • - -
  • -

    NEC uPD72861

    -
    • - -
  • -

    NEC uPD72870

    -
    • - -
  • -

    NEC uPD72871/2

    -
    • - -
  • -

    NEC uPD72873

    -
    • - -
  • -

    NEC uPD72874

    -
    • - -
  • -

    National Semiconductor CS4210

    -
    • - -
  • -

    Ricoh R5C551

    -
    • - -
  • -

    Ricoh R5C552

    -
    • - -
  • -

    Sony CX3022

    -
    • - -
  • -

    Sony i.LINK (CXD1947)

    -
    • - -
  • -

    Sony i.LINK (CXD3222)

    -
    • - -
  • -

    Sun PCIO-2 (RIO 1394)

    -
    • - -
  • -

    Texas Instruments PCI4410A

    -
    • - -
  • -

    Texas Instruments PCI4450

    -
    • - -
  • -

    Texas Instruments PCI4451

    -
    • - -
  • -

    Texas Instruments TSB12LV22

    -
    • - -
  • -

    Texas Instruments TSB12LV23

    -
    • - -
  • -

    Texas Instruments TSB12LV26

    -
    • - -
  • -

    Texas Instruments TSB43AA22

    -
    • - -
  • -

    Texas Instruments TSB43AB21/A/AI/A-EP

    -
    • - -
  • -

    Texas Instruments TSB43AB22/A

    -
    • - -
  • -

    Texas Instruments TSB43AB23

    -
    • - -
  • -

    Texas Instruments TSB82AA2

    -
    • - -
  • -

    VIA Fire II (VT6306)

    -
    • -
-
- -
-
-

3.14 Bluetooth Devices

-
- -
-
-

3.15 Cryptographic -Accelerators

-
- -
-
-

3.16 Miscellaneous

- -

Keyboards including:

- - - -
-
-

Pointing devices including:

- -
    -
  • -

    Serial mice and compatible devices

    -
    • - -
  • -

    USB mice ( -ums(4) -driver)

    -
    • -
- -
-
-

Note: -moused(8) has -more information on using pointing devices with FreeBSD. Information on using pointing -devices with Xorg can be found at http://www.x.org/.

-
-
- -
-
-
-
-
- -
-

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

- -

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

- -

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

- - - diff --git a/en/releases/6.3R/hardware.sgml b/en/releases/6.3R/hardware.sgml index 7ff69254ac..25343265f7 100644 --- a/en/releases/6.3R/hardware.sgml +++ b/en/releases/6.3R/hardware.sgml @@ -1,6 +1,6 @@ - + ]> @@ -18,7 +18,6 @@
  • alpha
  • amd64
  • i386
    • -
  • ia64
  • pc98
  • sparc64
    • diff --git a/en/releases/6.3R/installation-ia64.html b/en/releases/6.3R/installation-ia64.html deleted file mode 100644 index f205bd4484..0000000000 --- a/en/releases/6.3R/installation-ia64.html +++ /dev/null @@ -1,895 +0,0 @@ - - - - -FreeBSD/ia64 6.3-RELEASE Installation Instructions - - - - - -
    -
    -

    FreeBSD/ia64 6.3-RELEASE Installation -Instructions

    - -

    The FreeBSD Project

    - -

    Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The -FreeBSD Documentation Project

    - -
    -
    - -
    -
    -

    This article gives some brief instructions on installing FreeBSD/ia64 6.3-RELEASE, -with particular emphasis given to obtaining a FreeBSD distribution. Some notes on -troubleshooting and frequently-asked questions are also given.

    -
    -
    - -
    -
    -

    1 Installing FreeBSD

    - -

    This section documents the process of installing a new distribution of FreeBSD. These -instructions pay particular emphasis to the process of obtaining the FreeBSD 6.3-RELEASE -distribution and to beginning the installation procedure. The “Installing FreeBSD” chapter of the FreeBSD -Handbook provides more in-depth information about the installation program itself, -including a guided walkthrough with screenshots.

    - -

    If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.

    - -
    -
    -

    1.1 Getting -Started

    - -

    Probably the most important pre-installation step that can be taken is that of reading -the various instruction documents provided with FreeBSD. A roadmap of documents -pertaining to this release of FreeBSD can be found in README.TXT, which can usually be found in the same location as this -file; most of these documents, such as the release notes and the hardware compatibility -list, are also accessible in the Documentation menu of the installer.

    - -

    Note that on-line versions of the FreeBSD FAQ and Handbook are also available from the FreeBSD Project Web site, if you have an Internet connection.

    - -

    This collection of documents may seem daunting, but the time spent reading them will -likely be saved many times over. Being familiar with what resources are available can -also be helpful in the event of problems during installation.

    - -

    The best laid plans sometimes go awry, so if you run into trouble take a look at Section 4, which contains valuable troubleshooting information. You -should also read an updated copy of ERRATA.TXT before -installing, since this will alert you to any problems which have reported in the interim -for your particular release.

    - -
    -
    -

    Important: 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 if you make a mistake. Please do -not proceed to the final FreeBSD installation menu unless you've adequately backed up any -important data first.

    -
    -
    -
    - -
    -
    -

    1.2 Hardware Requirements

    - -

    If you are not familiar with configuring hardware for FreeBSD, you should be sure to -read the HARDWARE.TXT file; it contains important information -on what hardware is supported by FreeBSD.

    -
    - -
    -
    -

    1.3 Floppy Disk Image -Instructions

    -
    - -
    -
    -

    1.4 Installing -FreeBSD from CDROM or the Internet

    -
    - -
    -
    -

    1.5 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 Documentation submenu as well as the general “Usage” instructions on the -first menu.

    - -
    -
    -

    Note: If you get stuck at a screen, press the F1 key for -online documentation relevant to that specific section.

    -
    -
    - -

    If you've never installed FreeBSD before, or even if you have, the -“Standard” 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 are listed below.

    - -
    -
    -

    1.5.1 Installing from a Network -CDROM

    - -

    If you simply wish to install from a local CDROM drive then see Section 1.4. 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 also several ways of going about it:

    - -
      -
    • -

      If you would be able to FTP install FreeBSD directly from the CDROM drive in some -FreeBSD machine, it's quite easy: You ensure an FTP server is running and then simply add -the following line to the password file (using the -vipw(8) -command):

      - -
      -ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
-
      - -

      On the machine on which you are running the install, go to the Options menu and set -Release Name to any. You may then choose a Media type of FTP and type in ftp://machine after picking “URL” in the ftp -sites menu.

      - -
      -
      -

      Warning: This may allow anyone on the local network (or Internet) to make -“anonymous FTP” connections to this machine, which may not be desirable.

      -
      -
      -
      • - -
    • -

      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). The -example below allows the machine ziggy.foo.com to mount the CDROM -directly via NFS during installation:

      - -
      -/cdrom          -ro             ziggy.foo.com
-
      - -

      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, e.g. wiggy:/cdrom.

      -
      • -
    -
    - -
    -
    -

    1.5.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 your boot floppies as described in Section -1.3.

    - -

    Second, peruse Section 2 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.

    - -
    -
    -

    Important: Frequently, floppy disks come “factory preformatted”. -While convenient, many problems reported by users in the past have resulted from the use -of improperly formatted media. Re-format them yourself, just to make sure.

    -
    -
    - -

    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(8) and - -newfs(8) -commands to put a UFS filesystem on a floppy, as the following sequence of commands -illustrates:

    - -
    -# fdformat -f 1440 fd0
-# disklabel -w fd0 floppy3
-# newfs -i 65536 /dev/fd0
-
    - -

    After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto -them. The distribution files are sized so that a floppy disk will hold a single file. -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: 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.5.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 use -tar(1) to get -them onto the tape with a command something like this:

    - -
    -# cd /where/you/have/your/dists
-# tar cvf /dev/sa0 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.

    - -
    -
    -

    Note: When going to do the installation, the tape must be in the drive before booting from the boot floppies. -The installation “probe” may otherwise fail to find it.

    -
    -
    - -

    Now create a boot floppy as described in Section 1.3 and -proceed with the installation.

    -
    - -
    -
    -

    1.5.5 Installing over a Network using FTP -or NFS

    - -

    After making the boot floppies 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, -parallel port, or Ethernet.

    - -
    -
    -
    1.5.5.1 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 the PPP -utility should 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.

    -
    - -
    -
    -
    1.5.5.2 Parallel Port
    - -

    If a hard-wired connection to another FreeBSD 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: 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 in order to be compatible -with Linux's slightly different PLIP protocol.

    -
    -
    -
    - -
    -
    -
    1.5.5.3 Ethernet
    - -

    FreeBSD supports most common Ethernet cards; a table of supported cards is provided as -part of the FreeBSD Hardware Notes (see HARDWARE.TXT in 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 subnet 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 want to install by FTP via an -HTTP proxy (see below), you will also need the proxy's address.

    - -

    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 is almost guaranteed not to work, and will probably result in a lecture -from said system administrator.

    - -

    Once you have a network connection of some sort working, the installation can continue -over NFS or FTP.

    -
    - -
    -
    -
    1.5.5.4 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 (this is generally -the default for Sun and Linux workstations), you may 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 distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, then wiggy 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.5.5 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 “URL” choice in that menu. A URL can contain a -hostname or an IP address, so something like the following would work in the absence of a -name server:

    - -
    -ftp://216.66.64.162/pub/FreeBSD/releases/ia64/4.2-RELEASE
-
    - -

    There are three FTP installation modes you can use:

    - -
      -
    • -

      FTP: This method uses the standard “Active” mode for transfers, in which -the server initiates a connection to the client. 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.

      -
      • - -
    • -

      FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening -connections to the client. This option is best for users to pass through firewalls that -do not allow incoming connections on random port addresses.

      -
      • - -
    • -

      FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy -for all FTP operations. The proxy will translate the requests and send them to the FTP -server. This allows the user to pass through firewalls that do not allow FTP at all, but -offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP -server.

      - -

      In the rare case that you have an FTP proxy that does not go through HTTP, you can -specify the URL as something like:

      - -
      -ftp://foo.bar.com:port/pub/FreeBSD
-
      - -

      In the URL above, port is the port number of the -proxy FTP server.

      -
      • -
    -
    -
    -
    - -
    -
    -

    1.6 Question and Answer Section for IA-64 -Architecture Users

    -
    -
    - -
    -
    -

    2 Distribution Format

    - -

    A typical FreeBSD distribution directory looks something like this (exact details may -vary depending on version, architecture, and other factors):

    - -
    -ERRATA.HTM      README.TXT      compat1x        dict            kernel
-ERRATA.TXT      RELNOTES.HTM    compat20        doc             manpages
-HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     packages
-HARDWARE.TXT    base            compat22        filename.txt    ports
-INSTALL.HTM     boot            compat3x        floppies        proflibs
-INSTALL.TXT     catpages        compat4x        games           src
-README.HTM      cdrom.inf       crypto          info            tools
-
    - -

    These same files are contained in the first CDROM of a multi-disk set, but they are -laid out slightly differently on the disk. On most architectures, the installation CDROM -also contains a “live filesystem” in addition to the distribution files. The -live filesystem is useful when repairing or troubleshooting an existing FreeBSD -installation (see Section 4 for how to use this).

    - -

    The floppies directory will be of particular interest to -users who are unable to boot from the CDROM media (but are able to read the CDROM by -other means). It is easy to generate a set of 1.44MB boot floppies from the floppies directory (see Section 1.3 for -instructions on how to do this) and use these to start an installation from CDROM, FTP, -or NFS. The rest of the data needed during the installation will be obtained -automatically based on your selections. If you've never installed FreeBSD before, you -also want to read the entirety of this document (the installation instructions) file.

    - -

    If you're trying to do some other type of installation or are merely curious about how -a distribution is organized, what follows is a more thorough description of some of these -items in more detail:

    - -
      -
    1. -

      The *.TXT and *.HTM files contain -documentation (for example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should -be read before starting an installation. The *.TXT files are -plain text, while the *.HTM files are HTML files that can be -read by almost any Web browser. Some distributions may contain documentation in other -formats as well, such as PDF or PostScript.

      -
      2. - -
    2. -

      docbook.css is a Cascading Style Sheet (CSS) file used by -some Web browsers for formatting the HTML documentation.

      -
      3. - -
    3. -

      The base, catpages, crypto, dict, doc, games, info, manpages, proflibs, and src directories contain the -primary distribution components of FreeBSD itself and are split into smaller files for -easy packing onto floppies (should that be necessary).

      -
      4. - -
    4. -

      The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories -contain distributions for compatibility with older releases and are distributed as single -gzip'd tar files - they can be installed during release time or later by running their -install.sh scripts.

      -
      5. - -
    5. -

      The floppies/ subdirectory contains the floppy installation -images; further information on using them can be found in Section -1.3.

      -
      6. - -
    6. -

      The packages and ports directories -contain the FreeBSD Packages and Ports Collections. Packages may be installed from the -packages directory by running the command:

      - -
      -# sysinstall configPackages
-
      - -

      Packages can also be installed by feeding individual filenames in packages/ to the -pkg_add(1) -command.

      - -

      The Ports Collection may be installed like any other distribution and requires about -190MB unpacked. More information on the ports collection may be obtained from http://www.FreeBSD.org/ports/ or -locally from /usr/share/doc/handbook if you've installed the -doc distribution.

      -
      7. - -
    7. -

      Last of all, the tools directory contains various DOS tools -for discovering disk geometries, installing boot managers and the like. It is purely -optional and provided only for user convenience.

      -
      8. -
    - -

    A typical distribution directory (for example, the info -distribution) looks like this internally:

    - -
    -CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
-info.aa         info.ac         info.ae         info.mtree
-
    - -

    The CHECKSUM.MD5 file contains MD5 signatures for each file, -should data corruption be suspected, and is purely for reference. It is not used by the -actual installation and does not need to be copied with the rest of the distribution -files. The info.a* files are split, gzip'd tar files, the -contents of which can be viewed by doing:

    - -
    -# cat info.a* | tar tvzf -
-
    - -

    During installation, they are automatically concatenated and extracted by the -installation procedure.

    - -

    The info.inf file is also necessary since it is read by the -installation program in order to figure out how many pieces to look for when fetching and -concatenating the distribution. When putting distributions onto floppies, the .inf file must occupy the first floppy of each distribution set!

    - -

    The info.mtree file is another non-essential file which is -provided for user reference. It contains the MD5 signatures of the unpacked distribution files and can be -later used with the -mtree(8) program -to verify the installation permissions and checksums against any possible modifications -to the file. When used with the base distribution, this can be -an excellent way of detecting trojan horse attacks on your system.

    - -

    Finally, the install.sh file is for use by those who want to -install the distribution after installation time. To install the info distribution from -CDROM after a system was installed, for example, you'd do:

    - -
    -# cd /cdrom/info
-# sh install.sh
-
    -
    - -
    -
    -

    3 Upgrading FreeBSD

    - -

    These instructions describe a procedure for doing a binary upgrade from an older -version of FreeBSD.

    - -
    -
    -

    Warning: While the FreeBSD upgrade procedure does its best to safeguard against -accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do -not accept the final confirmation request unless you have adequately backed up any -important data files.

    -
    -
    - -
    -
    -

    Important: These notes assume that you are using the version of -sysinstall(8) -supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched -version of -sysinstall(8) is -almost guaranteed to cause problems and has been known to leave systems in an unusable -state. The most commonly made mistake in this regard is the use of an old copy of -sysinstall(8) -from an existing installation to upgrade to a newer version of FreeBSD. This is not recommended.

    -
    -
    - -
    -
    -

    Warning: Binary upgrades to FreeBSD 6.3-RELEASE from FreeBSD 4-STABLE are not -supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence -can be disruptive, but are not removed by a binary upgrade. One notable example is that -an old /usr/include/g++ directory will cause C++ programs to -compile incorrectly (or not at all).

    - -

    These upgrade instructions are provided for the use of users upgrading from relatively -recent FreeBSD 6.3-STABLE snapshots.

    -
    -
    - -
    -
    -

    3.1 Introduction

    - -

    The upgrade procedure replaces distributions selected by the user with those -corresponding to the new FreeBSD release. It preserves standard system configuration -data, as well as user data, installed packages and other software.

    - -

    Administrators contemplating an upgrade are encouraged to study this section in its -entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or -loss of data.

    - -
    -
    -

    3.1.1 Upgrade Overview

    - -

    Upgrading of a distribution is performed by extracting the new version of the -component over the top of the previous version. Files belonging to the old distribution -are not deleted.

    - -

    System configuration is preserved by retaining and restoring the previous version of -the following files:

    - -

    Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

    - -

    The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new -versions and merge components as desired. Note that many of these files are -interdependent, and the best merge procedure is to copy all site-specific data from the -current files into the new.

    - -

    During the upgrade procedure, the administrator is prompted for a location into which -all files from /etc/ are saved. In the event that local -modifications have been made to other files, they may be subsequently retrieved from this -location.

    -
    -
    - -
    -
    -

    3.2 Procedure

    - -

    This section details the upgrade procedure. Particular attention is given to items -which substantially differ from a normal installation.

    - -
    -
    -

    3.2.1 Backup

    - -

    User data and system configuration should be backed up before upgrading. While the -upgrade procedure does its best to prevent accidental mistakes, it is possible to -partially or completely destroy data and configuration information.

    -
    - -
    -
    -

    3.2.2 Mount Filesystems

    - -

    The disklabel editor is entered with the nominated disk's filesystem devices listed. -Prior to commencing the upgrade, the administrator should make a note of the device names -and corresponding mountpoints. These mountpoints should be entered here. Do not set the “newfs flag” -for any filesystems, as this will cause data loss.

    -
    - -
    -
    -

    3.2.3 Select Distributions

    - -

    When selecting distributions, there are no constraints on which must be selected. As a -general rule, the base distribution should be selected for an -update, and the man distribution if manpages are already -installed. Other distributions may be selected beyond those originally installed if the -administrator wishes to add additional functionality.

    -
    - -
    -
    -

    3.2.4 After Installation

    - -

    Once the installation procedure has completed, the administrator is prompted to -examine the new configuration files. At this point, checks should be made to ensure that -the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should -be checked.

    -
    -
    - -
    -
    -

    3.3 Upgrading from Source Code

    - -

    Those interested in an upgrade method that allows more flexibility and sophistication -should take a look at The Cutting Edge in the FreeBSD Handbook. This procedure involves -rebuilding all of FreeBSD from source code. It requires reliable network connectivity, -extra disk space, and time, but has advantages for networks and other more complex -installations. This is roughly the same procedure as is used for track the -STABLE or --CURRENT development branches.

    - -

    /usr/src/UPDATING contains important information on updating -a FreeBSD system from source code. It lists various issues resulting from changes in -FreeBSD that may affect an upgrade.

    -
    -
    - -
    -
    -

    4 Troubleshooting

    - -
    -

    4.1 Repairing an Existing FreeBSD -Installation

    - -

    FreeBSD features a “fixit” option in the top menu of the -sysinstall(8) -installation program. It provides a shell with common programs from the FreeBSD base -system; this environment is useful for repairing or troubleshooting an existing FreeBSD -installation. To use fixit mode, you will also need either the fixit.flp floppy, generated in the same fashion as the boot -floppies, or the “live filesystem” CDROM. In multi-disk FreeBSD -distributions, the live filesystem image is typically located on the installation disk. -Note that some UNIX system administration experience is required to use the fixit -option.

    - -

    Generally, there are two ways of invoking fixit mode. Users who can boot from the -FreeBSD installation CDROM, should do so and then choose the “fixit” item -from the main -sysinstall(8) -menu. Then select the “CDROM/DVD” option from the fixit menu.

    - -

    Users who cannot boot from CDROM, but can boot from floppy disk, require a few more -steps. In addition to the boot.flp and kernX.flp disks required for -installation, create the fixit.flp floppy disk, in the same way -as the other floppy disks. Follow the instructions for booting the installation program -from floppy disk until reaching the main -sysinstall(8) -menu. At that point, choose the “fixit” item from the main -sysinstall(8) -menu. Then select the “Floppy” option from the fixit menu, and insert the fixit.flp floppy disk when prompted to do so.

    - -

    The CDROM and floppy fixit environments are similar, but not identical. Both offer a -shell with a variety of commands available for checking, repairing and examining -filesystems and their contents. The CDROM version of fixit provides all of the commands -and programs available in the FreeBSD base system, through the live filesystem. By -contrast, the floppy fixit environment can only offer a subset of commands due to space -constraints.

    - -

    In the floppy version of fixit, some standalone utilities can be found in /stand or /mnt2/stand. In the CDROM -version of fixit, these same programs can be found in /stand or -/mnt2/rescue (as well as the rest of the programs from the live -filesystem, which can be found under /mnt).

    -
    - -
    -
    -

    4.2 Common Installation Problems for IA-64 -Architecture Users

    -
    -
    -
    - -
    -

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

    - -

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

    - -

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

    - - - diff --git a/en/releases/6.3R/installation.sgml b/en/releases/6.3R/installation.sgml index 90c930e787..e1ba378775 100644 --- a/en/releases/6.3R/installation.sgml +++ b/en/releases/6.3R/installation.sgml @@ -1,6 +1,6 @@ - + ]> @@ -18,7 +18,6 @@
  • alpha
  • amd64
  • i386
    • -
  • ia64
  • pc98
  • sparc64
    • diff --git a/en/releases/6.3R/relnotes-ia64.html b/en/releases/6.3R/relnotes-ia64.html deleted file mode 100644 index 4fd4e51a04..0000000000 --- a/en/releases/6.3R/relnotes-ia64.html +++ /dev/null @@ -1,608 +0,0 @@ - - - - -FreeBSD/ia64 6.3-RELEASE Release Notes - - - - - -
    -
    -

    FreeBSD/ia64 6.3-RELEASE Release -Notes

    - -

    The FreeBSD Project

    - -

    Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, -2008 The FreeBSD Documentation Project

    - -

    $FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v -1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $
    -

    - -
    -

    FreeBSD is a registered trademark of the FreeBSD Foundation.

    - -

    IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks -of International Business Machines Corporation in the United States, other countries, or -both.

    - -

    IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and -Electronics Engineers, Inc. in the United States.

    - -

    Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or -registered trademarks of Intel Corporation or its subsidiaries in the United States and -other countries.

    - -

    Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc -in the United States and other countries. Products bearing SPARC trademarks are based -upon architecture developed by Sun Microsystems, Inc.

    - -

    Many of the designations used by manufacturers and sellers to distinguish their -products are claimed as trademarks. Where those designations appear in this document, and -the FreeBSD Project was aware of the trademark claim, the designations have been followed -by the “™” or the “®” symbol.

    -
    - -
    -
    -

    The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the -FreeBSD base system on the 6.3-STABLE development line. This document lists applicable -security advisories that were issued since the last release, as well as significant -changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also -presented.

    -
    -
    - -
    -
    - -
    -
    -
    Table of Contents
    - -
    1 Introduction
    - -
    2 What's New
    - -
    -
    -
    2.1 Security Advisories
    - -
    2.2 Kernel Changes
    - -
    -
    -
    2.2.1 Boot Loader Changes
    - -
    2.2.2 Hardware Support
    - -
    2.2.3 Network Protocols
    - -
    2.2.4 Disks and Storage
    - -
    2.2.5 File Systems
    -
    -
    - -
    2.3 Userland Changes
    - -
    -
    -
    2.3.1 /etc/rc.d Scripts
    -
    -
    - -
    2.4 Contributed Software
    - -
    2.5 Ports/Packages Collection Infrastructure
    - -
    2.6 Release Engineering and Integration
    - -
    2.7 Documentation
    -
    -
    - -
    3 Upgrading from previous releases of FreeBSD
    -
    -
    - -
    -

    1 Introduction

    - -

    This document contains the release notes for FreeBSD 6.3-RELEASE on the IA-64 hardware -platform. It describes recently added, changed, or deleted features of FreeBSD. It also -provides some notes on upgrading from previous versions of FreeBSD.

    - -

    This distribution of FreeBSD 6.3-RELEASE is a release distribution. It can be found at -ftp://ftp.FreeBSD.org/ or any of its -mirrors. More information on obtaining this (or other) release distributions of FreeBSD -can be found in the “Obtaining FreeBSD” appendix to the FreeBSD -Handbook.

    - -

    All users are encouraged to consult the release errata before installing FreeBSD. The -errata document is updated with “late-breaking” information discovered late -in the release cycle or after the release. Typically, it contains information on known -bugs, security advisories, and corrections to documentation. An up-to-date copy of the -errata for FreeBSD 6.3-RELEASE can be found on the FreeBSD Web site.

    -
    - -
    -
    -

    2 What's New

    - -

    This section describes the most user-visible new or changed features in FreeBSD since -6.2-RELEASE.

    - -

    Typical release note items document recent security advisories issued after -6.2-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, -or contributed software upgrades. They may also list changes to major ports/packages or -release engineering practices. Clearly the release notes cannot list every single change -made to FreeBSD between releases; this document focuses primarily on security advisories, -user-visible changes, and major architectural improvements.

    - -
    -
    -

    2.1 Security Advisories

    - -

    Two remote denials of service in BIND (one involving DNSSEC and one involving -recursive DNS queries) have been fixed. For more information, see security advisory FreeBSD-SA-07:02.bind.

    - -

    Processing of IPv6 type 0 Routing Headers is now controlled by the net.inet6.ip6.rthdr0_allowed sysctl variable, which defaults to -0 (off). For more information, see security advisory FreeBSD-SA-07:03.ipv6.

    - -

    Problems with -libarchive(3) -and -tar(1) handling -corrupted -tar(5) archive -files have been fixed. More details can be found in security advisory FreeBSD-SA-07:05.libarchive.

    - -

    A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has -been corrected. More details can be found in security advisory FreeBSD-SA-07:08.openssl.

    - -

    An flaw that could lead to the disclosure of previously-generated -random(4) data -has been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-07:09.random.

    - -

    Information disclosure issues found in -openpty(3) and - -ptsname(3) have -been corrected. Information regarding this issue can be found in security advisory FreeBSD-SA-08:01.pty.

    - -

    A programming error in -inet_network(3) -Internet address manipulation function that could lead to overwriting a region of memory -with user defined data has been corrected. Information regarding this issue can be found -in security advisory FreeBSD-SA-08:02.libc.

    -
    - -
    -
    -

    2.2 Kernel Changes

    - -

    -acpi(4) now has -support for the HPET time counter.

    - -

    Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts -(MSI-X) has been added to the kernel's PCI support code.

    - -
    -
    -

    2.2.1 Boot Loader Changes

    -
    - -
    -
    -

    2.2.2 Hardware Support

    - -

    An -acpi_dock(4) -driver has been added to provide support for controlling laptop docking station functions -via ACPI.

    - -
    -
    -
    2.2.2.1 Multimedia Support
    - -

    The -snd_envy24(4) -driver has been added to support the Envy24 series of audio chips.

    - -

    The -snd_envy24ht(4) -driver has been added to support the VIA Envy24HT series of audio chips.

    - -

    The -snd_hda(4) -driver has been added. It supports devices that conform to revision 1.0 of the Intel High -Definition Audio specification.

    - -

    The -snd_spicds(4) -driver has been added to support I2S SPI audio codec chips.

    -
    - -
    -
    -
    2.2.2.2 Network Interface Support
    - -

    The -ath(4) driver -has been updated to HAL version 0.9.20.3.

    - -

    The -axe(4) driver -now supports -altq(4).

    - -

    The -cxgb(4) driver -has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio -T3 and T3B chipsets.

    - -

    The -edsc(4) driver, -which provides Ethernet discard network interfaces, has been added.

    - -

    The em(4) driver has been -updated to version 6.7.2 from Intel.

    - -

    The -msk(4) driver -has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II -Gigabit Ethernet controller.

    - -

    The -vge(4) driver -now supports -altq(4).

    - -

    The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and -half-channel support for 802.11a.

    -
    -
    - -
    -
    -

    2.2.3 Network Protocols

    - -

    The -if_bridge(4) -driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).

    - -

    The -lagg(4) driver, -ported from OpenBSD and NetBSD, has been added to support a variety of protocols and -algorithms for link aggregation, failover, and fault tolerance.

    - -

    A new -ng_deflate(4) -NetGraph node type has been added. It implements Deflate PPP compression.

    - -

    The -ng_ppp(4) -Netgraph node is now MPSAFE.

    - -

    A new -ng_pred1(4) -NetGraph node type has been added to implement Predictor-1 PPP compression.

    - -

    A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over -gif(4) tunnels -has been fixed.

    - -

    The net.link.tap.up_on_open sysctl variable has been -added to the -tap(4) driver. -If enabled, new tap devices will marked up upon creation.

    -
    - -
    -
    -

    2.2.4 Disks and Storage

    - -

    The -mpt(4) driver -has been updated to support various new features such as RAID volume and RAID member -state/settings reporting, periodic volume re-synchronization status reporting, and sysctl -variables for volume re-synchronization rate, volume member write cache status, and -volume transaction queue depth.

    - -

    The -mpt(4) driver -now supports SAS HBA (partially), 64-bit PCI, and large data transfer.

    - -

    The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG -passthrough device API, has been added. It is intended to allow programs running under -Linux emulation (as well as native FreeBSD applications) to access the /dev/sg* devices supported by -Linux.

    - -

    The -twa(4) driver -has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's -3ware 9650 series of SATA controllers.

    -
    - -
    -
    -

    2.2.5 File Systems

    - -

    The unionfs file system has been re-implemented. This version solves many crashing and -locking issues compared to the previous implementation. It also adds new -“transparent” and “masquerade” modes for automatically creating -files in the upper file system layer of unions. More information can be found in the -mount_unionfs(8) -manual page.

    -
    -
    - -
    -
    -

    2.3 Userland Changes

    - -

    The -camcontrol(8) -utility now supports a readcap command to display the size of -devices.

    - -

    A bug in -freebsd-update(8), which caused it not to update -SMP kernels correctly, has been fixed.

    - -

    The -fdisk(8) program -now supports a -p flag to print the slice table in fdisk -configuration format.

    - -

    The -freebsd-update(8) utility now supports an upgrade command to perform binary upgrades between different -versions of FreeBSD.

    - -

    The -ftpd(8) utility -now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The -RFC2640 support is optional and can be enabled using the new -8 flag. More information can be found in the -ftpd(8) manual -page.

    - -

    The -ipfwpcap(8) -utility has been added; it captures packets on a -divert(4) socket -and writes them as -pcap(3) (also -known as -tcpdump(1)) -format data to a file or pipe.

    - -

    The -rpc.lockd(8) and - -rpc.statd(8) -programs now accept -p options to indicate which port they -should bind to.

    - -

    The pw(8) program now -supports a -M option to set the permissions of a user's newly -created home directory.

    - -

    The -top(1) program -now supports a -j flag to display the -jail(8) ID for -each process.

    - -

    The -touch(1) utility -now supports a -A flag that allows the access and -modification times of a file be adjusted by a specified value.

    - -

    The -wpa_passphrase(8) utility has been added. It -generates a 256-bit pre-shared WPA key from an ASCII passphrase.

    - -
    -
    -

    2.3.1 /etc/rc.d Scripts

    - -

    The sendmail script can be instructed not to rebuild the -aliases database if it is missing or older than the aliases file. If desired, set the new -rc.conf option sendmail_rebuild_aliases to "NO" to turn off -that functionality.

    - -

    The /etc/rc.d/nfslocking script has been deprecated and will -be removed in a future release. It has been replaced by the /etc/rc.d/lockd and /etc/rc.d/statd -scripts.

    -
    -
    - -
    -
    -

    2.4 Contributed Software

    - -

    awk has been updated from the 24 April 2005 release to the -1 May 2007 release.

    - -

    BIND has been updated from 9.3.3 to 9.3.4-p1.

    - -

    BZIP2 has been updated from 1.0.3 to 1.0.4.

    - -

    GNU Diffutils has been updated from 2.7 to 2.8.7.

    - -

    The GNU version of gzip has been replaced with a modified -version of gzip ported from NetBSD.

    - -

    IPFilter has been updated from 4.1.13 to 4.1.28.

    - -

    less has been updated from v381 to v416.

    - -

    ncurses has been updated from 5.2-20020615 to 5.6-20061217. -ncurses now also has wide character support.

    - -

    netcat has been updated from the version in a 4 February -2005 OpenBSD snapshot to the version included in OpenBSD 4.1.

    - -

    GNU Readline library has been updated from 5.0 to 5.2 patch -2.

    - -

    sendmail has been updated from 8.13.8 to 8.14.2.

    - -

    The timezone database has been updated from the tzdata2006g -release to the tzdata2007k release.

    - -

    TrustedBSD OpenBSM has been updated from 1.0 alpha 12 to -1.0.

    -
    - -
    -
    -

    2.5 Ports/Packages Collection -Infrastructure

    -
    - -
    -
    -

    2.6 Release Engineering and -Integration

    - -

    The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.16.1 to 2.20.1.

    - -

    The supported version of the KDE desktop environment (x11/kde3) has been updated from 3.5.4 to 3.5.7.

    - -

    The supported version of the Xorg windowing system (x11/xorg) has been updated from 6.9.0 to 7.3.0.

    - -

    The default value of X11BASE has been changed from /usr/X11R6 to /usr/local, the default -value of LOCALBASE.

    -
    - -
    -
    -

    2.7 Documentation

    -
    -
    - -
    -
    -

    3 Upgrading from previous releases of -FreeBSD

    - -

    Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or -later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to -FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.

    - -
    -
    -

    Important: Upgrading FreeBSD should, of course, only be attempted after backing -up all data and configuration -files.

    -
    -
    -
    -
    - -
    -

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

    - -

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

    - -

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

    - - - diff --git a/en/releases/6.3R/relnotes.sgml b/en/releases/6.3R/relnotes.sgml index ec8c869869..f687ba9b88 100644 --- a/en/releases/6.3R/relnotes.sgml +++ b/en/releases/6.3R/relnotes.sgml @@ -1,6 +1,6 @@ - + ]> @@ -18,7 +18,6 @@
  • alpha
  • amd64
  • i386
    • -
  • ia64
  • pc98
  • sparc64