diff options
| author | ache <ache@FreeBSD.org> | 2001-06-11 01:48:17 +0000 |
|---|---|---|
| committer | ache <ache@FreeBSD.org> | 2001-06-11 01:48:17 +0000 |
| commit | 7ec2d96d826c0a27e33b398a0c5c7031ea625ee0 (patch) | |
| tree | 5c884e74d177881b32634b53f8b6bd7454b5f352 /release | |
| parent | a1920be1e09a2fef5c10cf9a45a9dc58c531bfea (diff) | |
| download | FreeBSD-src-7ec2d96d826c0a27e33b398a0c5c7031ea625ee0.zip FreeBSD-src-7ec2d96d826c0a27e33b398a0c5c7031ea625ee0.tar.gz | |
ISO_* -> ISO* rename
Diffstat (limited to 'release')
51 files changed, 6 insertions, 10821 deletions
diff --git a/release/doc/Makefile b/release/doc/Makefile index 911ab9d..e5919e8 100644 --- a/release/doc/Makefile +++ b/release/doc/Makefile @@ -6,7 +6,7 @@ .if defined(RELNOTES_LANG) && !empty(RELNOTES_LANG) SUBDIR = ${RELNOTES_LANG} .else -SUBDIR = en_US.ISO_8859-1 +SUBDIR = en_US.ISO8859-1 .endif RELN_ROOT?= ${.CURDIR} diff --git a/release/doc/README b/release/doc/README index 8803ce0..c6f51b5 100644 --- a/release/doc/README +++ b/release/doc/README @@ -45,7 +45,7 @@ share/sgml/release.ent this file when rolling new revisions; these should take effect in all documents. -en_US.ISO_8859-1/share/sgml/release.dsl +en_US.ISO8859-1/share/sgml/release.dsl Language-dependent stylesheet for en, but also the default for translations if they don't override the settings here. This stylesheet sets the email footer at the bottom of HTML pages, @@ -123,5 +123,5 @@ Release builders can set which language gets built with the RELNOTES_LANG variable; note that this is different from the DOC_LANG variable because (at least intially) most languages will have localized DocProj files but not localized release notes. -The default language, if none is specified, is en_US.ISO_8859-1. +The default language, if none is specified, is en_US.ISO8859-1. diff --git a/release/doc/en_US.ISO_8859-1/Makefile b/release/doc/en_US.ISO_8859-1/Makefile deleted file mode 100644 index 7911dbf..0000000 --- a/release/doc/en_US.ISO_8859-1/Makefile +++ /dev/null @@ -1,14 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/.. - -SUBDIR = relnotes -SUBDIR+= hardware -SUBDIR+= readme -SUBDIR+= errata -SUBDIR+= installation - -COMPAT_SYMLINK = en - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/errata/Makefile b/release/doc/en_US.ISO_8859-1/errata/Makefile deleted file mode 100644 index 87801ca..0000000 --- a/release/doc/en_US.ISO_8859-1/errata/Makefile +++ /dev/null @@ -1,14 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/errata/article.sgml b/release/doc/en_US.ISO_8859-1/errata/article.sgml deleted file mode 100644 index b803c13..0000000 --- a/release/doc/en_US.ISO_8859-1/errata/article.sgml +++ /dev/null @@ -1,110 +0,0 @@ -<!-- - $FreeBSD$ - - FreeBSD errata document. Unlike some of the other RELNOTESng - files, this file should remain as a single SGML file, so that - the dollar FreeBSD dollar header has a meaningful modification - time. This file is all but useless without a datestamp on it, - so we'll take some extra care to make sure it has one. - - (If we didn't do this, then the file with the datestamp might - not be the one that received the last change in the document.) - ---> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -]> - -<article> - <articleinfo> - -<!-- XXX Change release.current to release.prev when there's --> -<!-- XXX a release on this branch. --> - - <title>&os; &release.current; Errata</title> - - <corpauthor> - The &os; Project - </corpauthor> - - <pubdate>$FreeBSD$</pubdate> - - <copyright> - <year>2000</year> - <year>2001</year> - <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> - </copyright> - </articleinfo> - - <abstract> - -<!-- XXX Change release.current to release.prev when there's --> -<!-- XXX a release on this branch. --> - - <para>This document lists errata that pertain to the most - recently-released version of &os; (&release.current;). It includes - both security advisories that pertain this release, as well as - items relating to the software or documentation, discovered after - the release, that could affect its operation or usability. - - <note> - <para>At this time, &release.current; has no errata, because - there have not been any releases on the &release.branch; - branch since the last branchpoint. (The first such release will - be &release.next;.) - This file exists to provide a clean template for - newly-created branches. (Clearly this notice should not exist - on any branched version of this file.)</para> - </note> - - </para> - </abstract> - - <sect1> - <title>Introduction</title> - - <para>If you read no other documentation before installing this - version of &os;, you should <emphasis>read - the errata</emphasis> for this release so that you don't stumble - over problems which have already been found and fixed. Any - version of this - <filename>ERRATA.TXT</filename> file actually distributed with the - release is out of - date by definition, but other copies are kept updated on the net and - should be consulted as the <quote>current errata</quote> for your - release. These other copies of the errata are located at <ulink - url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink>, - as well as any sites which keep up-to-date mirrors of this - location).</para> - - <para>Source and binary snapshots of &release.current; also - contain up-to-date copies of this document (as of the time of the - snapshot).</para> - - <para>Any changes to this file are also automatically emailed to the - &a.current;.</para> - - <para>For a list of all &os; CERT security advisories, see <ulink - url="http://www.freebsd.org/security"></ulink> or <ulink - url="ftp://ftp.freebsd.org/pub/FreeBSD/CERT/"></ulink>.</para> - - </sect1> - - <sect1> - <title>Security Advisories</title> - <para></para> - </sect1> - - <sect1> - <title>System Update Information</title> - <para></para> - </sect1> -</article> diff --git a/release/doc/en_US.ISO_8859-1/hardware/Makefile b/release/doc/en_US.ISO_8859-1/hardware/Makefile deleted file mode 100644 index dca8380..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/Makefile +++ /dev/null @@ -1,9 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -SUBDIR = alpha -SUBDIR+= i386 - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/hardware/alpha/Makefile b/release/doc/en_US.ISO_8859-1/hardware/alpha/Makefile deleted file mode 100644 index 69e9a3c..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/alpha/Makefile +++ /dev/null @@ -1,19 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= proc-alpha.sgml -SRCS+= ../common/hw.ent -SRCS+= ../common/artheader.sgml -SRCS+= ../common/dev.sgml -SRCS+= ../common/config.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/hardware/alpha/article.sgml b/release/doc/en_US.ISO_8859-1/hardware/alpha/article.sgml deleted file mode 100644 index 8081a3f..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/alpha/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "alpha"> - -]> - -<article> - &artheader; - §.intro; - §.proc.alpha; - §.dev; - §.config; -</article> diff --git a/release/doc/en_US.ISO_8859-1/hardware/alpha/proc-alpha.sgml b/release/doc/en_US.ISO_8859-1/hardware/alpha/proc-alpha.sgml deleted file mode 100644 index f34ace5..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/alpha/proc-alpha.sgml +++ /dev/null @@ -1,3039 +0,0 @@ -<!-- - $FreeBSD$ ---> -<sect1> - <sect1info> - <pubdate>$FreeBSD$</pubdate> - </sect1info> - - <title>Supported processors and motherboards</title> - - <para>This section is maintained by &a.wilko;.</para> - - <para>Additions, corrections and constructive criticism are invited. In - particular information on system quirks is more than welcome.</para> - - <sect2> - <title>Overview</title> - - <para>This document tries to provide a starting point for those - who want to run &os; on an Alpha-based machine. It is - aimed at providing background information on the various hardware - designs. It is not a replacement for the systems manuals.</para> - - <para>The information is structured as follows: - <itemizedlist> - <listitem> - <para>general hardware requirements to run &os; on alpha;</para> - </listitem> - <listitem> - <para>system specific information for each of the - systems/boards supported by &os;;</para> - </listitem> - <listitem> - <para>information on expansion boards for &os;, - including things that differ from what is in the generic - supported hardware list.</para> - </listitem> - </itemizedlist> - </para> - - <note> - <para>You will see references to DEC, Digital Equipment Corporation and - Compaq used more or less interchangeably. Now that Compaq has acquired - Digital Equipment it would be more correct to refer to Compaq only. - Given the fact that you will see the mix of names everywhere I don't - bother.</para> - </note> - - <note> - <para>SRM commands will be in <userinput>UPPER CASE</userinput>. - Lower case input is also acceptible to SRM. Upper case is used for - clarity. - </note> - </sect2> - - <sect2> - <title>In general, what do you need to run &os; on an Alpha?</title> - - <para>Obviously you will need an Alpha machine that &os; - knows about. Alpha machines are NOT like PCs. There are - considerable differences between the various core logic chip sets and - mainboard designs. This means that a kernel needs to know the - intimate details of a particular machine before it can run on - it. Throwing some odd <filename>GENERIC</filename> kernel at - unknown hardware is almost guaranteed to fail miserably.</para> - - <para>For a machine even to be considered for &os; use please - make sure it has the SRM console firmware installed. Or at least - make sure that SRM console firmware is available for the - particular machine type. If &os; does not currently support - your machine type, there is a good chance that this will change at - some point in time, assuming SRM is available. All bets are off when - SRM console firmware is not available.</para> - - <para>Machines with the ARC or AlphaBIOS console firmware were - intended for WindowsNT. Some have SRM console firmware available - in the system ROMs which you only have to select (via an ARC or - AlphaBIOS menu). In other cases you will have to re-flash the ROMs - with SRM code. Check on - http://ftp.digital.com/pub/DEC/Alpha/firmware to see what is - available for your particular system. In any case: no SRM means - <emphasis>no</emphasis> - &os; (or NetBSD, OpenBSD, Tru64 Unix or OpenVMS for that - matter). With the demise of WindowsNT/alpha a lot of former NT - boxes are sold on the second hand market. They have little or no - trade-in value when they are NT-only from the console firmware - perspective. So, be suspicious if the price appears too good.</para> - - <para>Known non-SRM machines are: - <itemizedlist> - <listitem> - <para>Digital XL series</para> - </listitem> - <listitem> - <para>Digital XLT series</para> - </listitem> - <listitem> - <para>Samsung PC164UX</para> - </listitem> - <listitem> - <para>Samsung 164B</para> - </listitem> - </itemizedlist> - </para> - - <para>To complicate things a bit further: Digital used to have so - called <quote>white-box</quote> Alpha machines destined as NT-only - and <quote>blue-box</quote> Alpha machines destined for OpenVMS - and Digital Unix. These names are based on the color of the - cabinets, <quote>FrostWhite</quote> and <quote>TopGunBlue</quote> - respectively. Although you could put the SRM console firmware on a - whitebox, OpenVMS and Digital Unix will refuse to boot on - them. &os; in post-4.0-RELEASE will run on both the white and the - blue-box variants. Before someone asks: the white ones had a - rather different (read: cheaper) Digital price tag.</para> - - <para>As part of the SRM you will get the so called OSF/1 PAL code - (OSF/1 being the initial name of Digital's UNIX offering on - Alpha). The PAL code can be thought of as a software abstraction - layer between the hardware and the operating system. It uses - normal CPU instruction plus a handful of privileged instructions - specific for PAL use. PAL is not microcode. The ARC console - firmware contains a different PAL code, geared towards WinNT and - in no way suitable for use by &os; (or more generic: Unix or - OpenVMS). Before someone asks: Linux/alpha brings its own PAL - code, allowing it to boot on ARC and AlphaBIOS. There are various - reasons why this is not a very good idea in the eyes of the *BSD - folks. I don't want to go into details here. If you are interested - in the gory details search the &os; and NetBSD web sites.</para> - - <para>There is another pitfall ahead: you will need a disk adapter - that the SRM console firmware recognizes in order to be able to boot from - a disk. What is acceptable to SRM as a boot adapter is - unfortunately highly system and SRM version dependent. For older PCI - based machines it means you will need either a NCR/Symbios - 53C810 based adapter, or a Qlogic 1020/1040 based adapter. Some - machines come with a SCSI chip embedded on the mainboard. Newer - machine designs and SRM versions will be able to work with more modern - SCSI chips/adapters. Check out the machine specific info - below. Please note that the rest of this discussion only refers to - Symbios chips, this is meant to include the older chips that still - have NCR stamped on them. Symbios bought NCR sometime.</para> - - <para>The problem might bite those who have machines that started - their lives as WindowsNT boxes. The ARC or AlphaBIOS knows about - <emphasis>other</emphasis> adapter types that it can boot from - than the SRM. For example you can boot from an Adaptec 2940UW with - ARC/AlphaBios but (generally) not with SRM. Some newer machine types have - introduced Adaptec boot support. Please consult the machine - specific section for details.</para> - - <para>Most adapters that cannot be booted from work fine for - data-only disks. The differences between SRM and ARC could also - get you pre-packaged IDE CDROMs and hard drives in some (former - WindowsNT) systems. SRM versions exist (depends on the machine type) - that can boot from IDE disks and CDROMs. Check the machine - specific section for details.</para> - - <para>&os; 4.0 and later can be booted from the - distribution CDROM. Earlier versions needed booting from a - 2 disk floppy set.</para> - - <para>If you don't have/want a local disk drive you can boot via - the Ethernet. This assumes an Ethernet adapter/chip that is - recognized by the SRM console. Generally speaking this boils down to - either a 21040 or 21142 or 21143 based Ethernet interface. Older - machines or SRM versions may not recognize the 21142 / 21143 Fast - Ethernet chips, you are then limited to using 10Mbit Ethernet for net - booting those machines. Non-DEC cards based on said chips will - generally (but are not guaranteed to) work. Note that Intel took - over the 21x4x chips when it bought Digital Semiconductor. So you - might see an Intel logo on them these days. Recent machine designs - have SRM support for Intel 8255x Ethernet chips.</para> - - <para>Alpha machines can be run with SRM on a graphics console or - on a serial console. ARC can also be run on a serial consoles if need - be. VT100 emulation with 8 bit controls should at least allow you - to switch from ARC/AlphaBIOS to SRM mode without having to install a - graphics card first.</para> - - <para>If you want to run your Alpha machine without a monitor/graphics - card just don't connect a keyboard/mouse to the machine. Instead - hook up a serial terminal[emulator] to serial port #1. The SRM - will talk 9600N81 to you. This can also be really practical for - debugging purposes. Beware: some/most (?) SRMs will also present - you with a console prompt at serial port #2. The booting kernel, - however, will display the boot messages on serial port #1 and will - also put the console there. <emphasis>This can be extremely - confusing.</emphasis></para> - - <para>Most PCI based Alphas can use ordinary PC-type VGA - cards. The SRM contains enough smarts to make that work. It does - not, however, mean that each and every PCI VGA card out on the - street will work in an Alpha machine. Things like S3 Trio64, - Mach64, and Matrox Millennium generally work. Old ET4000 based ISA - cards have also worked for me. But ask around first before buying. - Please note that TGA cards are not currently supported as &os; console - display cards.</para> - - <para>Most PCI devices from the PC-world will also work in - &os; PCI-based machines. Check the - <filename>/sys/alpha/conf/GENERIC</filename> file for the latest word - on this. Check the appropriate machine type's - discussion in case you want to use PCI cards that have PCI bridge - chips on them. In some cases you might encounter problems with - PCI cards not handling PCI parity correctly. This can lead to - panics. PCI parity checking can be disabled using the following - SRM command: >>> <userinput>SET PCI_PARITY OFF</userinput>. - This is not a &os; problem, all operating systems running on - Alpha hardware will need this workaround.</para> - - <para>If your system (also) contains EISA expansion slots you will - need to run the EISA Configuration Utility (ECU) after you have - installed EISA cards or after you have upgraded your - console firmware.</para> - - <para>For Alpha CPUs you will find multiple generations. The - original Alpha design is the 21064. It was produced in a chip - process called MOS4, chips made in this process are nicknamed - EV4. Newer CPUs are 21164, 21264 etc. You will see designations - like EV4S, EV45, EV5, EV56, EV6, EV67. The EVs with double digit - numbers are slightly improved versions. For example EV45 has an - improved FPU and 16 kByte on-chip separate I & D caches compared - to the EV4 on which it is based. Rule of thumb: the higher the - digit immediately following <quote>EV</quote> the more desirable - (read: faster / more modern).</para> - - <para>For memory you want at least 32 Mbytes. I have had - &os; run on a 16 Mbyte system but you will not enjoy - that. Kernel build times halved when I went to 32 Mbytes. Note that - the SRM console steals 2Mbyte from the total system memory (and keeps - it). For more serious work 64 Mbytes or more are recommended.</para> - - <para>While on the subject of memory: pay close attention to the - type of memory your machine uses. There are very different memory - configurations and requirements for the various machines.</para> - - <para>Final word: I expect the above to sound a bit daunting to - the first-time Alpha user. Don't be daunted too much. And do feel - free to ask questions if something is not clear after reading this - document.</para> - - </sect2> - - <sect2> - <title>System-specific information</title> - - <para>Below is an overview of the hardware that &os; runs on. This list - will definitely grow, a look in - <filename>/sys/alpha/conf/GENERIC</filename> can be enlightening.</para> - - <para>Alpha machines are often best known by their project code name. - Where known these are listed below in parentheses.</para> - - <sect3> - <title>AXPpci33 (<quote>NoName</quote>)</title> - - <para>The NoName is a baby-AT mainboard based on the 21066 LCA - (Low Cost Alpha) processor. NoName was originally designed for - OEM-use. The LCA chip includes almost all of the logic to drive - a PCI bus and the memory subsystem. All of this makes for a - low-priced design.</para> - - <para>Due to the limited memory interface the system is not - particularly fast in case of cache misses. As long as you stay - inside the on-chip cache the CPU is comparable to a 21064 (first - generation Alpha). These boards should be very cheap to obtain - these days. It is a full-fledged 64 bit CPU, just don't expect - miracles as far as speed goes.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz. - 21068 CPUs are also possible, but are even slower.</para> - </listitem> - <listitem> - <para>on-board Bcache / L2 cache: 0, 256k or 1 Mbyte (uses - DIL chips)</para> - </listitem> - <listitem> - <para>PS/2 mouse & keyboard port OR 5pin DIN keyboard (2 - mainboard models)</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>bus width: 64 bits</para> - </listitem> - <listitem> - <para>PS/2 style 72 pin 36 bit Fast Page Mode SIMMs</para> - </listitem> - <listitem> - <para>70ns or better</para> - </listitem> - <listitem> - <para>installed in pairs of 2 - </listitem> - <listitem> - <para>4 SIMM sockets</para> - </listitem> - <listitem> - <para>uses ECC</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>512kB Flash ROM for the console code.</para> - </listitem> - <listitem> - <para>2 16550A serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>floppy interface</para> - </listitem> - <listitem> - <para>1 embedded IDE interface</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>3 32 bit PCI slots (1 shared with ISA)</para> - </listitem> - <listitem> - <para>5 ISA slots (1 shared with PCI)</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>embedded Fast SCSI using a Symbios 53C810 chip</para> - </listitem> - </itemizedlist> - </para> - - <para>NoNames can either have SRM <emphasis>or</emphasis> ARC console - firmware in their Flash ROM. The Flash ROM is not big enough to - hold both ARC and SRM at the same time and allow software - selection of alternate console code. But you only need SRM - anyway.</para> - - <para>Cache for the NoNames are 15 or 20 ns DIL chips. For a 256 - kByte cache you want to check your junked 486 mainboard. Chips - for a 1 Mbyte cache are a rarer breed unfortunately. Getting at - least a 256kByte cache is recommended performance - wise. Cache-less they are really slow.</para> - - <para>The NoName mainboard has a PC/AT-standard power - connector. It also has a power connector for 3.3 Volts. No need - to rush out to get a new power supply. The 3.3 Volts is only - needed in case you run 3.3 Volts PCI expansion boards. These are - quite rare.</para> - - <para>The IDE interface is supported by &os; and requires a - line in the kernel configuration file as follows:</para> - - <programlisting>device ata0 at isa? port IO_WD1 irq 14</programlisting> - - <para>The SRM console unfortunately <emphasis> cannot boot</emphasis> - from IDE disks. This means you will have to use a SCSI disk as - the boot device.</para> - - <para>Make sure you use true 36 bit SIMMs, and only FPM (Fast - Page Mode) DRAM. EDO DRAM or SIMMs with fake parity <emphasis>will not - work</emphasis>. The board uses the 4 extra bits for ECC. 33 - bit FPM SIMMs will for the same reason not work.</para> - - <para>Given the choice, get the PS/2-variant mainboard. Apart - from giving you a mouse port as bonus it is directly supported - by Tru64 Unix in case you ever want or need to run it. The - <quote>DIN-plug</quote>-variant should work OK for &os;.</para> - - <para>The <ulink - url="ftp://ftp.digital.com/pub/DEC/axppci/design_guide.ps"> - OEM manual</ulink> is recommended reading.</para> - - <para>The kernel configuration file for a NoName kernel must - contain:</para> - - <programlisting>options DEC_AXPPCI_33 -cpu EV4</programlisting> - - </sect3> - - <sect3> - <title>Universal Desktop Box (UDB or <quote>Multia</quote>)</title> - - <note><para>Multia can be either Intel or Alpha CPU based. We - assume Alpha based ones here for obvious reasons.</para></note> - - <para>Multia is a small desktop box intended as a sort of - personal workstation. They come in a considerable number of - variations, check closely what you get.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz</para> - </listitem> - <listitem> - <para>on-board Bcache / L2 cache: COAST-like 256 kByte - cache module; 233MHz models have 512kByte of cache; - 166MHz models have soldered-on 256kB caches</para> - </listitem> - <listitem> - <para>PS/2 mouse & keyboard port</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>bus width: 64 bits</para> - </listitem> - <listitem> - <para>PS/2 style 72 pin 36 bit Fast Page Mode SIMMs</para> - </listitem> - <listitem> - <para>70ns or better</para> - </listitem> - <listitem> - <para>SIMMs are installed in pairs of 2 - </listitem> - <listitem> - <para>4 SIMM sockets</para> - </listitem> - <listitem> - <para>uses ECC</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>2 16550A serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>floppy interface</para> - </listitem> - <listitem> - <para>Intel 82378ZB PCI to ISA bridge</para> - </listitem> - <listitem> - <para>1 embedded 21040 based 10Mbit Ethernet, AUI and - 10base2 connector</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>1 32 bit PCI slot</para> - </listitem> - <listitem> - <para>2 PCMCIA slots</para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para>on-board Crystal CS4231 or AD1848 sound chip</para> - </listitem> - <listitem> - <para>embedded Fast SCSI, using a Symbios 53C810[A] chip on the - PCI riser card</para> - </listitem> - </itemizedlist> - </para> - - <para>Multia has enough Flash ROM to store both SRM and ARC code - at the same time and allow software selection of one of them.</para> - - <para>Multia has only one 32 bit PCI slot for expansion, and it - is only suitable for a small form factor PCI card. By - sacrificing the PCI slot space you can mount a 3.5" hard disk - drive. Mounting stuff may have come with your Multia. Adding a - 3.5" disk is <emphasis>not</emphasis> a recommended upgrade - due to the limited power rating of the power supply - and the extremely marginal cooling of - the system box.</para> - - <para>Multia also has 2 PCMCIA expansion slots. These are - currently not supported by &os;.</para> - - <para>The CPU might or might not be socketed, check this before - considering CPU upgrade hacks. The low-end Multias have a - soldered-in CPU.</para> - - <para>It comes with a TGA based graphics on-board. TGA is not - currently suitable for console use with &os;. This means you will have - to run Multia using a serial console. Note that the boot of the - installation disk will appear to work fine using the TGA - console, but then switches to using the serial port. This is - even mentioned during by installer (but never read by the human - doing the install). Your keyboard appears dead from that point - on.</para> - - <para>Multia has 2 serial ports but routes both of them to the - outside world on a single 25 pin sub-D connector. The Multia FAQ - explains how to build your own Y-cable to allow both ports to be - used.</para> - - <para>Although the Multia SRM supports booting from floppy this - can be problematic. Typically the errors look like: - - <screen> - *** Soft Error - Error #10 - FDC: Data overrun or underrun - </screen> - - This is not a &os; problem, it is a SRM problem. The best available - workaround to install &os; is to boot from a SCSI CDROM.</para> - - <para>Sound works fine using &man.pcm.4; driver and a line in the - kernel configuration file as follows for the Crystal CS4231 - chip:</para> - - <programlisting>device pcm0 at isa? port 0x530 irq 9 drq 3 flags 0x15</programlisting> - - <para>I have not yet been successful in getting my Multia with - the AD1848 to play any sound.</para> - - <para>While verifying playback I was reminded of the lack of CPU - power of the 166MHz CPU. MP3 only plays acceptable using 22kHz - down-sampling.</para> - - <para>Multias are somewhat notorious for dying of heat - strokes. The very compact box does not really allow access to cooling air. - Please use the Multia on its vertical stand, - don't put it horizontally (<quote>pizza style</quote>). Replacing the - fan with something which pushes around more air is really - recommended. You can also cut one of the wires to the fan speed - sensor. Once cut, the fan runs at a (loud) full speed. - Beware of PCI cards with high power consumption. - If your system has died you might want to check the - Multia-Heat-Death pages at the - <ulink url="http://www.netbsd.org/">NetBSD Web site</ulink> - for help in reviving it.</para> - - <para>The Intel 82378ZB PCI to ISA bridge enables the use of an - IDE disk. This requires a line in the kernel configuration file - as follows:</para> - - <programlisting>device ata0 at isa? port IO_WD1 irq 14</programlisting> - - <para>The IDE connector pin spacing is thought for 2.5" laptop - disks. A 3.5" IDE disk would not fit in the case anyway. At - least not without sacrificing your only PCI slot. The SRM - console unfortunately does not know how to boot from IDE - disks. You will need to use a SCSI disk as the bootdisk.</para> - - <para>In case you want to change the internal hard drive: the - internal flat cable running from the PCI riser board to the - <emphasis>2.5"</emphasis> - hard drive has a finer pitch than the standard SCSI flat - cables. Otherwise it would not fit on the 2.5" drives. There are - also riser cards that have a standard-pitch SCSI cable attached - to it, which will fit an ordinary SCSI disk.</para> - - <para>Again, I recommend against trying to cram a replacement - hard disk inside. Use the external SCSI connector and put your - disk in an external enclosure. Multias run hot enough as-is. In - most cases you will have the external high density 50-pin SCSI - connector but some Multia models came without disk and may lack - the connector. Something to check before buying one.</para> - - <para>The kernel configuration file for a Multia kernel must - contain: - - <programlisting>options DEC_AXPPCI_33 -cpu EV4</programlisting></para> - - <para>Recommended reading on Multia can be found at - <ulink url="http://www.netbsd.org/Ports/alpha/multiafaq.html"> - http://www.netbsd.org/Ports/alpha/multiafaq.html</ulink> - or <ulink url="http://www.brouhaha.com/~eric/computers/udb.html"> - http://www.brouhaha.com/~eric/computers/udb.html</ulink>.</para> - - </sect3> - - <sect3> - <title>Personal Workstation (<quote>Miata</quote>)</title> - - <para>The Miata is a small tower machine intended to be put - under a desk. There are multiple Miata variants. The original - Miata is the MX5 model. Because it suffers from a number of - hardware design flaws a redesign was done, yielding the - MiataGL. Unfortunately the variants are not easily distinguishable - at first sight from the outside of the case. - An easy check is to see if the back of the machine sports two - USB connectors. If yes, it is a MiataGL. MX5 models tend to be - more common in the used system market place.</para> - - <para>System designations look like <quote>Personal Workstation - 433a</quote>. Personal Workstation, being a bit of a mouthful, - is often abbreviated to PWS. This means it has a 433 MHz CPU, - and started life as a WinNT workstation (the trailing - <quote>a</quote>). Systems designated from day 1 to run Tru64 - Unix or OpenVMS will sport <quote>433au</quote>. WinNT-Miatas - are likely to come pre-configured with an IDE CDROM drive. So, - in general systems are named like PWS[433,500,600]a[u]. - - <para>There was also a Miata model with a special CPU cooling - system by Kryotech. The Kryotech has a special cooling system - and is housed in a different enclosure.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21164A EV56 Alpha CPU at 433, 500 or 600MHz</para> - </listitem> - <listitem> - <para>21174 Core Logic (<quote>Pyxis</quote>) chip set</para> - </listitem> - <listitem> - <para>on-board Bcache / L3 cache: 0, 2 or 4 Mbytes (uses a - cache module)</para> - </listitem> - <listitem><para>memory:</para> - <para><itemizedlist> - <listitem> - <para>bus width: 128 bits wide, ECC protected</para> - </listitem> - <listitem> - <para>unbuffered 72 bit wide SDRAMs DIMMs, - installed in pairs of 2</para> - </listitem> - <listitem> - <para>6 DIMM sockets</para> - </listitem> - <listitem> - <para>maximum memory 1.5 GBytes</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>on-board Fast Ethernet: - <itemizedlist> - <listitem> - <para>MX5 uses a 21142 or 21143 Ethernet chip, - dependent on the version of the PCI riser card</para> - </listitem> - <listitem> - <para>MiataGL has a 21143 chip</para> - </listitem> - <listitem> - <para>the bulkhead can be 10/100 Mbit UTP, or - 10 Mbit UTP/BNC</para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para>2 on-board [E]IDE disk interfaces, based on - the CMD646 (MX5) or the Cypress 82C693 (MiataGL)</para> - </listitem> - <listitem> - <para>1 Ultra-Wide SCSI Qlogic 1040 [MiataGL only]</para> - </listitem> - <listitem> - <para>2 64-bit PCI slots</para> - </listitem> - <listitem> - <para>3 32-bit PCI slots (behind a DEC PCI-PCI bridge chip)</para> - </listitem> - <listitem> - <para>3 ISA slots (physically shared with the 32 bit PCI slots, - via an Intel 82378IB PCI to ISA bridge chip)</para> - </listitem> - <listitem> - <para>2 16550A serial port</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>PS/2 keyboard & mouse port</para> - </listitem> - <listitem> - <para>USB interface [MiataGL only]</para> - </listitem> - <listitem> - <para>embedded sound based on an ESS1888 chip</para> - </listitem> - </itemizedlist> - </para> - - <para>The Miata logic is divided into two printed circuit - boards. The lower board in the bottom of the machine has the - PCI and ISA slots and things like the sound chip etc. The top - board has the CPU, the Pyxis chip, memory etc. Note that MX5 - and the MiataGL use a different PCI riser board. This means - that you cannot just upgrade to a MiataGL CPU board (with the - newer Pyxis chip) but that you will also need a different - riser board. Apparently an MX5 riser with a MiataGL CPU board - will work but it is definitely not a supported or tested - configuration. Everything else (cabinet, wiring, etc.) is - identical for MX5 and MiataGL.</para> - - <para>MX5 has problems with DMA via the 2 64-bit PCI slots - when this DMA crosses a page boundary. The 32 bit slots don't - have this problem because the PCI-PCI bridge chip does not - allow the offending transfers. The SRM code knows about the - problem and refuses to start the system if there is a PCI card - in one of the 64bit slots that it does not know about. Cards - that are <quote>known good</quote> to the SRM are allowed to - be used in the 64bit slots.</para> - - <para>If you want to fool the SRM you can type <userinput>set - pci_device_override</userinput> at the SRM prompt. Just don't - complain if your data mysteriously gets mangled.</para> - - <para>The complete command is: - - <screen><prompt>>>></prompt> <userinput>SET PCI_DEVICE_OVERRIDE <replaceable><vendor_id></replaceable><replaceable><device_id></replaceable></userinput></screen></para> - - <para>For example: - -<screen><prompt>>>></prompt> <userinput>SET PCI_DEVICE_OVERRIDE 88c15333</userinput></screen></para> - - <para>The most radical approach is to use: - -<screen><prompt>>>></prompt> <userinput>SET PCI_DEVICE_OVERRIDE -1</userinput></screen></para> - - <para>This disables PCI ID checking altogether, so that you - can install any PCI card without its ID getting - checked. For this to work you need a reasonable current SRM version. - <important><para>Do this on your own risk..</para></important></para> - - <para>The &os; kernel reports it when it sees a buggy Pyxis chip: -<screen>Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1 -Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1<BWEN> -Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets...</screen></para> - - <para>A MiataGL probes as: -<screen>Jan 3 12:22:32 miata /kernel: cia0: Pyxis, pass 1 -Jan 3 12:22:32 miata /kernel: cia0: extended capabilities: 1<BWEN> -Jan 3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> on cia0</screen></para> - - <para>MiataGL does not have the DMA problems of the MX5. PCI - cards that make the MX5 SRM choke when installed in the 64bit - slots are accepted without problems by the MiataGL SRM.</para> - - <para>The latest mainboard revisions of MX5 contain a hardware - workaround for the bug. The SRM does not know about the ECO - and will complain about unknown cards as before. So does the - &os; kernel by the way.</para> - - <para>The Miata SRM can boot from IDE CDROM drives. IDE harddisk - boot is known to work for both MiataGL and MX5 disks, so you - can root &os; from an IDE disk. Speeds on MX5 are around 14 - Mbytes/sec assuming a suitable drive. Miata's CMD646 chip will - support up to WDMA2 mode as the chip is too buggy for use - with UDMA.</para> - - <para>Miata MX5s generally use Qlogic 1040 based SCSI adapters. - These are bootable by the SRM console. Note that Adaptec cards - are <emphasis>not</emphasis> bootable by the Miata SRM console.</para> - - <para>The MiataGL has a faster PCI-PCI bridge chip on the PCI - riser card than some of the MX5 riser card versions. Some of - the MX5 risers have the <emphasis>same</emphasis> chip as the - MiataGL. All in all there is a lot of variation.</para> - - <para>Not all VGA cards will work behind the PCI-PCI - bridge. This manifests itself as no video at all. Workaround - is to put the VGA card <quote>before</quote> the bridge, in - one of the 64 bit PCI slots.</para> - - <para>Both MX5 and MiataGL have an on-board sound chip, an - ESS1888. It emulates a SoundBlaster and can be enabled by - putting -<programlisting>device pcm0 -device sbc0</programlisting> - in your kernel configuration file.</para> - - <para>in case your Miata has the optional cache board - installed make sure it is firmly seated. A slightly loose - cache has been observed to cause weird crashes (not surprising - obviously, but maybe not so obvious when troubleshooting). The - cache module is identical between MX5 and MiataGL.</para> - - <para>Installing a 2Mb cache module achieves, apart from a - 10-15% speed increase (based on buildworld elapsed time), a - <emphasis>decrease</emphasis> for PCI DMA read bandwidth from - 64bit PCI cards. A benchmark on a 64-bit Myrinet card resulted - in a decrease from 149 Mbytes/sec to 115 Mbytes/sec. Something - to keep in mind when doing really high speed things with 64 - bit PCI adapters.</para> - - <para>If you experience SRM errors like - - <screen>ERROR: scancode 0xa3 not supported on PCXAL</screen> - - after halting &os; you should update your SRM firmware to V7.2-1 or - later. This SRM version is first available on the Firmware - Update CD V5.7, or on <ulink - url="http://www.compaq.com/">http://www.compaq.com/</ulink> This SRM - problem is fixed on both Miata MX5 and Miata GL.</para> - - <para>USB is supported by &os; 4.1 and later.</para> - - <para>Disconnect the power cord before dismantling the - machine, the soft-power switch keeps part of the logic powered - <emphasis>even</emphasis> when the machine is switched off.</para> - - <para>The kernel configuration file for a Miata kernel must - contain: - - <programlisting>options DEC_ST550 -cpu EV5</programlisting></para> - </sect3> - - <sect3> - <title>DEC3000 family (the <quote>Bird</quote> machines)</title> - - <para>The DEC3000 series were among the first Alpha machines - ever produced. They are based on an I/O bus called the - TurboChannel (TC) bus. These machines are built like tanks - (watch your back).</para> - - <para>DEC3000 can be subdivided in DEC3000/500-class and - DEC3000/300-class. The DEC3000/500-class is the early high-end - workstation/server Alpha family. Servers use serial consoles, - workstations have graphics tubes. DEC3000/300-class is the - lower-cost workstation class.</para> - - <para>DEC3000/500-class are quite fast (considering their age) - thanks to the good memory design. DEC3000/300 is crippled - compared to DEC3000/500 because of its much narrower memory - bus.</para> - - <para>They are called <quote>Birds</quote> because their - internal DEC code names were bird names: - - <informaltable> - <tgroup cols=3 align=left> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="2*"> - <tbody> - <row> - <entry>DEC3000/400</entry> - <entry>Sandpiper</entry> - <entry>133MHz CPU, desktop</entry> - </row> - <row> - <entry>DEC3000/500</entry> - <entry>Flamingo</entry> - <entry>150MHz CPU, floor standing</entry> - </row> - <row> - <entry>DEC3000/500X</entry> - <entry>Hot Pink</entry> - <entry>200MHz CPU, floor standing</entry> - </row> - <row> - <entry>DEC3000/600</entry> - <entry>Sandpiper+</entry> - <entry>175MHz CPU, desktop</entry> - </row> - <row> - <entry>DEC3000/700</entry> - <entry>Sandpiper45</entry> - <entry>225MHz CPU, floor standing</entry> - </row> - <row> - <entry>DEC3000/800</entry> - <entry>Flamingo Ultra</entry> - <entry>200MHz CPU, floor standing</entry> - </row> - <row> - <entry>DEC3000/900</entry> - <entry>Flamingo45</entry> - <entry>275MHz CPU, floor standing</entry> - </row> - <row> - <entry>DEC3000/300</entry> - <entry>Pelican</entry> - <entry>150MHz CPU, desktop, 2 TC slots</entry> - </row> - <row> - <entry>DEC3000/300X</entry> - <entry>Pelican+</entry> - <entry>175MHz CPU, desktop, 2 TC slots</entry> - </row> - <row> - <entry>DEC3000/300LX</entry> - <entry>Pelican+</entry> - <entry>125MHz CPU, desktop, 2 TC slots</entry> - </row> - <row> - <entry>DEC3000/300L</entry> - <entry></entry> - <entry>100MHz CPU, desktop, no TC slots</entry> - </row> - </tbody> - </tgroup> - </informaltable> - </para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21064 CPU (100 to 200 MHz) or 21064A CPU (225 to 275 - MHz)</para> - </listitem> - <listitem> - <para>memory DEC3000/500 class: - <itemizedlist> - <listitem> - <para>bus width: 256 bit, with ECC</para> - </listitem> - <listitem> - <para>proprietary 100pin SIMMs</para> - </listitem> - <listitem> - <para>installed in sets of 8</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>memory DEC3000/300 class:<itemizedlist> - <listitem> - <para>bus width: 64 bit, with ECC</para> - </listitem> - <listitem> - <para>PS/2 style 72pin 36 bit FPM SIMMs 70ns or better</para> - </listitem> - <listitem> - <para>used in pairs of 2</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>Bcache / L2 cache: varying sizes, 512 kB to 2 Mbyte</para> - </listitem> - <listitem> - <para>built-in 10Mbit Ethernet based on a Lance 7990 chip, - AUI and UTP</para> - </listitem> - <listitem> - <para>one or two SCSI buses based on a NCR53C94 or a - NCR53CF94-2 chip</para> - </listitem> - <listitem> - <para>2 serial ports based on Zilog 8530 (one usable as a - serial console)</para> - </listitem> - <listitem> - <para>embedded ISDN interface</para> - </listitem> - <listitem> - <para>on-board 8 bit sound</para> - </listitem> - <listitem> - <para>8 bit graphics on-board or via a TC card (depending - on model)</para> - </listitem> - </itemizedlist> - </para> - - <para>Currently DEC3000 machines can only be used diskless on - &os;. The reason for this is that the SCSI drivers needed - for the TC SCSI adapters were not brought into CAM that the - recent &os; versions use. TC option cards for single (PMAZ-A) or - dual fast SCSI (PMAZC-AA) are also available. These cards currently - have no drivers on &os; either.<para> - - <para>DEC3000/300 has 5 MBytes/sec SCSI on-board. This bus is - used for both internal and external devices. DEC3000/500 has 2 - SCSI buses. One is for internal devices only, the other one is - for external devices only.<para> - - <para>Floppy devices found in the DEC3000s are attached to the - SCSI bus (via a bridge card). This makes it possible to boot from them - using the same device names as ordinary SCSI hard-disks, for example: - <screen><prompt>>>></prompt> <userinput>BOOT DKA300</userinput></screen> - </para> - - <para>The 3000/300 series has a half-speed TurboChannel compared - to the other 3000 machines. Some TC expansion cards have - troubles with the half-speed bus. Caveat emptor.</para> - - <para>The embedded ISDN interface is not supported on &os;.</para> - - <para>DEC3000/300-class uses standard 36 bit, 72 pin Fast Page - Mode SIMMs. EDO SIMMs, 32 or 33 bit SIMMs all will not work in - Pelicans. For 32Mbyte SIMMs to work on the DEC3000/300-class - the presence detect bits/pins of the SIMM must correspond to - what the machine expects. If they don't, the SIMM is - <quote>seen</quote> as a 8 Mbyte SIMM. 8 Mbyte and 32 Mbyte - SIMMs can be mixed, as long as the pairs themselves are - identical.</para> - - <para>When you find yourself in need of fixing 32Mbyte SIMMs - that lack correct presence bits the following info might be of - use:</para> - - <para>There are four presence detection bits on PS/2 SIMMs. Two - of the bits indicate the access time. The other two indicate - the memory size.</para> - - <para>At one end of the SIMM there are two rows of four solder - pads. One row is connected to Vss (GND) and the other is - connected to pins 67 (PRD1), 68 (PRD2), 69 (PRD3), 70 - (PRD4).</para> - - <para>If you bridge a pair of pads with a small resistor or a - drop of solder you ground that particular bit. - - <informaltable> - <tgroup cols=3 align=left> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="2*"> - <thead> - <row> - <entry>PRD1</entry> - <entry>PRD2</entry> - <entry>Memory Size</entry> - </row> - </thead> - <tbody> - <row> - <entry>GND</entry> - <entry>GND</entry> - <entry>4 or 64 Mbyte</entry> - </row> - <row> - <entry>Open</entry> - <entry>GND</entry> - <entry>2 or 32 Mbyte</entry> - </row> - <row> - <entry>GND</entry> - <entry>Open</entry> - <entry>1 or 16 Mbyte</entry> - </row> - <row> - <entry>Open</entry> - <entry>Open</entry> - <entry>8 Mbyte</entry> - </row> - </tbody> - </tgroup> - </informaltable> - - <informaltable> - <tgroup cols=3 align=left> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="2*"> - <thead> - <row> - <entry>PRD3</entry> - <entry>PRD4</entry> - <entry>Access Time</entry> - </row> - </thead> - <tbody> - <row> - <entry>GND</entry> - <entry>GND</entry> - <entry>50 or 100 nsec</entry> - </row> - <row> - <entry>Open</entry> - <entry>GND</entry> - <entry>80 nsec</entry> - </row> - <row> - <entry>GND</entry> - <entry>Open</entry> - <entry>70 nsec</entry> - </row> - <row> - <entry>Open</entry> - <entry>Open</entry> - <entry>60 nsec</entry> - </row> - </tbody> - </tgroup> - </informaltable> - </para> - - <para>DEC3000/500-class can use 2, 4, 8, 16 and 32 Mbyte 100pin - SIMMs. Note that the maximum memory size varies from system to - system, desktop machines have sacrificed box size for less - memory SIMM sockets. Given enough sockets and enough SIMMs you - can get to 512 Mbytes maximum. This is one of the main - differences between floor standing and desktop machines, the - latter have far less SIMM sockets.</para> - - <para>The sound hardware is not supported on any of the Birds.</para> - - <para>There is no X-Windows version available for the TC - machines. DEC3000/300 needs a serial console. DEC3000/500-class - might work with a graphical console. I ran mine with a serial - console so I cannot verify this.</para> - - <para>Birds can be obtained from surplus sales etc. As they are - not PCI based they are no longer actively maintained. TC - expansion boards can be difficult to obtain these days and - support for them is not too good unless you write/debug the code - yourself. Programming information for TC boards is hard to - find. Birds are recommended only if a. you can get them cheap - and b. if you prepared to work on the code to support them - better.</para> - - <para>For the DEC3000/[4-9]00 series machines the kernel config - file must contain: - <programlisting>options DEC_3000_500 -cpu EV4</programlisting> - </para> - - <para>For the DEC3000/300 (<quote>Pelican</quote>) machines the - kernel config file must contain: - <programlisting>options DEC_3000_300 -cpu EV4</programlisting> - </para> - </sect3> - - <sect3> - <title>Evaluation Board 64plus (<quote>EB64+</quote>), Aspen - Alpine</title> - - <para>In its attempts to popularize the Alpha CPU DEC produced a number - of so called Evaluation Boards. The EB64+ family of evaluation - boards has the following feature set:</para> - - <para><itemizedlist> - <listitem> - <para>21064 or 21064A CPU, 150 to 275 MHz</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>memory buswidth: 128 bit</para> - </listitem> - <listitem> - <para>PS/2 style 72 pin 33 bit Fast Page Mode SIMMs</para> - </listitem> - <listitem> - <para>70ns or better</para> - </listitem> - <listitem> - <para>installed in sets of 4</para> - </listitem> - <listitem> - <para>8 SIMM sockets</para> - </listitem> - <listitem> - <para>uses parity memory</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>Bcache / L2 cache: 512 kByte, 1 Mbyte or 2 Mbytes</para> - </listitem> - <listitem> - <para>21072 (<quote>APECS</quote>) chip set</para> - </listitem> - <listitem> - <para>Intel 82378ZB PCI to ISA bridge chip (<quote>Saturn</quote>) - </para> - </listitem> - <listitem> - <para>dual 16550A serial ports</para> - </listitem> - <listitem> - <para>Symbios 53C810 Fast-SCSI</para> - </listitem> - <listitem> - <para>embedded 10 Mbit Ethernet</para> - </listitem> - <listitem> - <para>2 PCI slots</para> - </listitem> - <listitem> - <para>3 ISA slots</para> - </listitem> - </itemizedlist></para> - - <para>Aspen Alpine is slightly different, but is close enough to the - EB64+ to run an EB64+ SRM EPROM (mine did..). The Aspen Alpine does - not have an embedded Ethernet, has 3 instead of 2 PCI slots. It comes - with 2 Mbytes of cache already soldered onto the mainboard. It has - jumpers to select the use of 60, 70 or 80ns SIMM speeds.</para> - - <para>36 bits SIMMs work fine, 3 bits simply remain unused. Note - the systems use Fast Page Mode memory, not EDO memory.</para> - - <para>The SRM console code is housed in an UV-erasable EPROM. No - easy flash SRM upgrades for the EB64+ The latest SRM version available - for EB64+ is quite ancient anyway.</para> - - <para>The EB64+ SRM can boot both 53C810 and Qlogic1040 SCSI adapters. - Pitfall for the Qlogic is that the firmware that is down-loaded by - the SRM onto the Qlogic chip is very old. There are no updates for the - EB64+ SRM available. So you are stuck with old Qlogic bits too. - I have had quite some problems when I wanted to use Ultra-SCSI drives - on the Alpine with Qlogic. The &os; kernel can be compiled to include - a much newer Qlogic firmware revision. This is not the default because - it adds hundreds of kBytes worth of bloat to the kernel. In &os; 4.1 - and later the isp firmware is contained in a kernel loadable module. - All of this might mean that you need to use a non-Qlogic adapter to - boot from.</para> - - <para>For the EB64+ class machines the kernel config file must contain: - <programlisting>options DEC_EB64PLUS -cpu EV4</programlisting></para> - - </sect3> - - <sect3> - <title>Evaluation Board 164 (<quote>EB164, PC164, PC164LX, - PC164SX</quote>) family</title> - - <para>EB164 is a newer design evaluation board, based on the 21164A - CPU. This design has been used to <quote>spin off</quote> multiple variations, - some of which are used by OEM manufacturers/assembly shops. Samsung - did its own PC164LX which has only 32 bit PCI, whereas the Digital - variant has 64 bit PCI.</para> - - <para><itemizedlist> - <listitem> - <para>21164A, multiple speed variants [EB164, PC164, PC164LX]</para> - </listitem> - <listitem> - <para>21164PC [only on PC164SX]</para> - </listitem> - <listitem> - <para>21174 (Alcor) chip set</para> - </listitem> - <listitem> - <para>Bcache / L3 cache: EB164 uses special cache-SIMMs</para> - </listitem> - <listitem> - <para>memory bus: 128 bit / 256 bit</para> - </listitem> - <listitem> - <para>memory:<itemizedlist> - <listitem> - <para>PS/2 style SIMMs in sets of 4 or 8</para> - </listitem> - <listitem> - <para>36 bit, Fast Page Mode, uses ECC, [EB164 / PC164]</para> - </listitem> - <listitem> - <para>SDRAM DIMMs in sets of 2, uses ECC [PC164SX / PC164LX] - </para> - </listitem></itemizedlist> - </para> - </listitem> - <listitem> - <para>2 16550A serial ports</para> - </listitem> - <listitem> - <para>PS/2 style keyboard & mouse</para> - </listitem> - <listitem> - <para>floppy controller</para> - </listitem> - <listitem> - <para>parallel port</para> - </listitem> - <listitem> - <para>32 bits PCI</para> - </listitem> - <listitem> - <para>64 bits PCI [some models]</para> - </listitem> - <listitem> - <para>ISA slots via an Intel 82378ZB PCI to ISA bridge chip</para> - </listitem> - </itemizedlist></para> - - <para>Using 8 SIMMs for a 256bit wide memory can yield interesting - speedups over a 4 SIMM/128bit wide memory. Obviously all 8 SIMMs must - be of the same type to make this work. The system must be explicitly - setup to use the 8 SIMM memory arrangement. You must have 8 SIMMs, - 4 SIMMs distributed over 2 banks will not work.</para> - - <para>The SRM can boot from Qlogic 10xx boards or the Symbios 53C810[A]. - Newer Symbios 810 revisions like the Symbios 810AE are not recognized by - the SRM on PC164. PC164 SRM does not appear to recognize a Symbios 53C895 - based host adapter (tested with a Tekram DC-390U2W). On the other hand - some no-name Symbios 53C985 board has been reported to work. - Cards like the Tekram DC-390F (Symbios875 based) have been confirmed to - work fine on the PC164. Unfortunately this seems to be dependent on the - actual version of the chip/board.</para> - - <para>Symbios 53C825[a] will also work as boot adapter. Diamond - FirePort, although based on Symbios chips, is not bootable by the - PC164SX SRM. PC164SX is reported to boot fine with Symbios825, - Symbios875 and Symbios876 based cards. In addition, Adaptec - 2940U and 2940UW are reported to work for booting (verified on - SRM V5.7-1). Adaptec 2930U2 and 2940U2[W] do not work.</para> - - <para>164LX and 164SX with SRM firmware version 5.8 or later can boot - from Adaptec 2940-series adapters.</para> - - <para>In summary: this family of machines is <quote>blessed</quote> with a - challenging compatibility as far as SCSI adapters go.</para> - - <para>On PC164 the SRM sometimes seems to loose its variable settings. - <quote>For PC164, current superstition says that, to avoid losing settings, - you want to first downgrade to SRM 4.x and then upgrade to 5.x.</quote> - One sample error that was observed was: - <screen>ERROR: ISA table corrupt!</screen> - A sequence of a downgrade to SRM4.9, an <screen><prompt>>>> -</prompt> <userinput>ISACFG -INIT</userinput></screen> - followed by <screen><prompt>>>> </prompt><userinput>INIT</userinput></screen> - made the problem go away. Some PC164 owners report they have never seen - the problem. </para> - - <para>On PC164SX the AlphaBIOS allows you a selection to select SRM to - be used as console on the next power up. This selection does - not appear to have any effect. In other words, you will get the - AlphaBIOS regardless of what you select. The fix is to reflash the - console ROM with the SRM code for PC164SX. This will overwrite the - AlphaBIOS and will get you the SRM console you desire. The SRM code - can be found on the Compaq Web site.</para> - - <para>PC164 can boot from IDE disks assuming your SRM version is - recent enough.</para> - - <para>EB164 needs a power supply that supplies 3.3 Volts. PC164 does - not implement the PS_ON signal that ATX power supplies need to switch on. - A simple switch pulling this signal to ground allows you to run a - standard ATX power supply.</para> - - <para>For the EB164 class machines the kernel config file must - contain: - <programlisting>options DEC_EB164 -cpu EV5</programlisting></para> - </sect3> - - <sect3> - <title>AlphaStation 200 (<quote>Mustang</quote>) and 400 - (<quote>Avanti</quote>) series</title> - - <para>The Digital AlphaStation 200 and 400 series systems are early - low end PCI based workstations. The 200 and 250 series are - desktop boxes, the 400 series is a desk-side mini-tower.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21064 or 21064A CPU at speeds of 166 up to 333 MHz</para> - </listitem> - <listitem> - <para>DECchip 21071-AA core logic chip-set</para> - </listitem> - <listitem> - <para>Bcache / L2 cache: 512 Kbytes (200 and 400 series) - or 2048KBytes (250 series)</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>64 bit bus width</para> - </listitem> - <listitem> - <para>8 to 384 MBytes of RAM</para> - </listitem> - <listitem> - <para>70 ns or better Fast Page DRAM</para> - </listitem> - <listitem> - <para>in three pairs (200 and 400 series)</para> - </listitem> - <listitem> - <para>in two quads, so banks of four. (250 series)</para> - </listitem> - <listitem> - <para>the memory subsystem uses parity</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>PS/2 keyboard and mouse port</para> - </listitem> - <listitem> - <para>two 16550 serial ports</para> - </listitem> - <listitem> - <para>parallel port</para> - </listitem> - <listitem> - <para>floppy disk interface</para> - </listitem> - <listitem> - <para>32 bit PCI expansion slots (3 for the AS400-series, - 2 for the AS200 & 250-series)</para> - </listitem> - <listitem> - <para>ISA expansion slots (4 for the AS400-series, - 2 for the AS200 & 250-series) - (some ISA/PCI slots are physically shared)</para> - </listitem> - <listitem> - <para>embedded 21040-based Ethernet (200 & 250 series)</para> - </listitem> - <listitem> - <para>embedded Symbios 53c810 Fast SCSI-2 chip</para> - </listitem> - <listitem> - <para>Intel 82378IB (<quote>Saturn</quote>) PCI-ISA bridge chip</para> - </listitem> - <listitem> - <para>graphics is embedded TGA or PCI VGA (model dependent)</para> - </listitem> - <listitem> - <para>16 bit sound (on 200 & 250 series)</para> - </listitem> - </itemizedlist></para> - - <para>The systems use parity memory SIMMs, but these do not need 36 bit - wide SIMMs. 33 bit wide SIMMs are sufficient, 36 bit SIMMs are - acceptable too. EDO or 32 bit SIMMs will not work. 4, 8, 16, 32 and - 64 Mbyte SIMMs are supported.</para> - - <para>The AS200 & AS250 sound hardware is reported to work OK assuming - you have the following line in your kernel config file: - <programlisting>device pcm0 at isa? port 0x530 irq 9 drq 0 flags 0x10011</programlisting></para> - - <para>AlphaStation 200 & 250 series have an automatic SCSI terminator. - This means that as soon as you plug a cable onto the external SCSI - connector the internal terminator of the system is disabled. It also - means that you should not leave unterminated cables plugged into - the machine.</para> - - <para>AlphaStation 400 series have an SRM variable that controls - termination. In case you have external SCSI devices connected you - must set this SRM variable using - <screen><prompt>>>></prompt> <userinput>SET CONTROL_SCSI_TERM EXTERNAL</userinput>.</screen> </para> - - <para>If only internal SCSI devices are present use: - <screen><prompt>>>></prompt> <userinput>SET CONTROL_SCSI_TERM INTERNAL</userinput></screen></para> - - <para>For the AlphaStation-[24][05]00 machines the kernel config file - must contain: - <programlisting>options DEC_2100_A50 -cpu EV4</programlisting></para> - </sect3> - - <sect3> - <title>AlphaStation 500 and 600 (<quote>Alcor</quote> & - <quote>Maverick</quote> for EV5, <quote>Bret</quote> for EV56)</title> - - <para>AS500 and 600 were the high-end EV5 / PCI based workstations. - EV6 based machines have in the meantime taken their place as front - runners. AS500 is a desktop in a dark blue case (TopGun blue), - AS600 is a sturdy desk-side box. AS600 has a nice LCD panel to observe - the early stages of SRM startup.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21164 EV5 CPU at 266, 300, 333, 366, 400, 433, 466, or - 500 MHz (AS500) or at 266, 300 or 333 MHz (AS600)<para> - </listitem> - <listitem> - <para>21171 or 21172 (Alcor) core logic chip-set</para> - </listitem> - <listitem><para>Cache: - <itemizedlist> - <listitem> - <para>2 or 4 Mb L3 / Bcache (AS600 at 266 MHz)</para> - </listitem> - <listitem> - <para>4 Mb L3 / Bcache (AS600 at 300 MHz)</para> - </listitem> - <listitem> - <para>2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz version only)</para> - </listitem> - <listitem> - <para>2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM slots)</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>memory buswidth: 256 bits - </listitem> - <listitem><para>AS500 memory: - <itemizedlist> - <listitem> - <para>industry standard 72 bit wide buffered DIMMs</para> - </listitem> - <listitem> - <para>8 DIMM slots</para> - </listitem> - <listitem> - <para>installed in sets of 4</para> - </listitem> - <listitem> - <para>maximum memory is 1 GB (512 Mb max on 333 MHz CPUs)</para> - </listitem> - <listitem> - <para>uses ECC </para> - </listitem> - </itemizedlist></para> - <listitem><para>AS600 memory: - <itemizedlist> - <listitem> - <para>industry standard 36 bit Fast Page Mode SIMMs</para> - </listitem> - <listitem> - <para>32 SIMM slots</para> - </listitem> - <listitem> - <para>installed in sets of 8</para> - </listitem> - <listitem> - <para>maximum memory is 1 GB</para> - </listitem> - <listitem> - <para>uses ECC</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>Qlogic 1020 based wide SCSI bus (1 bus/chip for AS500, - 2 buses/chip for AS600)</para> - </listitem> - <listitem> - <para>21040 based 10 Mbit Ethernet adapter, both Thinwire - and UTP connectors</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>AS500: - <itemizedlist> - <listitem> - <para>3 32-bit PCI slots</para> - </listitem> - <listitem> - <para>1 64-bit PCI slot</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>AS600: - <itemizedlist> - <listitem> - <para>2 32-bit PCI slot</para> - </listitem> - <listitem> - <para>3 64-bit PCI slots</para> - </listitem> - <listitem> - <para>1 PCI/EISA physically shared slot</para> - </listitem> - <listitem> - <para>3 EISA slots</para> - </listitem> - <listitem> - <para>1 PCI and 1 EISA slot are occupied by default</para> - </listitem> - </itemizedlist></para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para>21050 PCI-to-PCI bridge chip</para> - </listitem> - <listitem> - <para>Intel 82375EB PCI-EISA bridge (AS600 only)</para> - </listitem> - <listitem> - <para>2 16550A serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>16 bit audio Windows Sound System, in a dedicated slot (AS500) - in EISA slot (AS600, this is an ISA card)</para> - </listitem> - <listitem> - <para>PS/2 keyboard and mouse port</para> - </listitem> - </itemizedlist></para> - - <para>Early machines had Fast SCSI interfaces, later ones are Ultra - SCSI capable. AS500 shares its single SCSI bus with internal and external - devices. For a Fast SCSI bus you are limited to 1.8 meters bus - length external to the box. +++ This is what some DEC docs suggest. - Did they ever go UltraSCSI?</para> - - <para>AS600 has one Qlogic SCSI chip dedicated to the internal devices - whereas the other Qlogic SCSI chip is dedicated to external SCSI devices. - </para> - - <para>In AS500 DIMMs are installed in sets of 4, in <quote>physically - interleaved</quote> layout. So, a bank of 4 DIMMs is <emphasis>not</emphasis> - 4 physically adjacent DIMMs.</para> - - <para>In AS600 the memory SIMMs are placed onto two memory daughter - cards. SIMMs are installed in sets of 8. Both memory daughter cards must - be populated identically.</para> - - <para>AS600 has a peculiarity for its PCI slots. AS600 (or rather the - PCI expansion card containing the SCSI adapters) does not allow I/O port - mapping, therefore all devices behind it must use memory mapping. If you - have problems getting the Qlogic SCSI adapters to work, add the following - option to <filename>/boot/loader.rc</filename>: - - <screen><userinput>set isp_mem_map=0xff</userinput></screen> - - This may need to be typed at the boot loader prompt before booting the - installation kernel.</para> - - <para>For the AlphaStation-[56]00 machines the kernel config file - must contain: - <programlisting>options DEC_KN20AA -cpu EV5</programlisting></para> - - </sect3> - - <sect3> - <title>AlphaServer 1000 (<quote>Mikasa</quote>), - 1000A (<quote>Noritake</quote>) and 800</title> - - <para>The AlphaServer 1000 and 800 range of machines are intended as - departmental servers. They come in quite some variations in packaging - and mainboard/cpu. Generally speaking there are 21064 (EV4) CPU based - machines and 21164 (EV5) based ones. The CPU is on a daughter card, and - the type of CPU (EV4 or EV5) must match the mainboard in use.</para> - - <para>AlphaServer 800 has a much smaller mini tower case, it lacks the - StorageWorks SCSI hot-plug chassis. The main difference between AS1000 - and AS1000A is that AS1000A has 7 PCI slots whereas AS1000 only has 3 - PCI slots and has EISA slots instead.</para> - - <para>AS800 with an EV5/400 MHz CPU was later re-branded to become a - <quote>DIGITAL Server 3300[R]</quote>, AS800 with an EV5/500 MHz - CPU was later re-branded to become a - <quote>DIGITAL Server 3305[R]</quote>.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21064 EV4[5] CPU at 200, 233 or 266 MHz - 21164 EV5[6] CPU at 300, 333 or 400 MHz (or 500 MHz for - AS800 only)</para> - </listitem> - <listitem> - <para>memory:<itemizedlist> - <listitem> - <para>buswidth: 128 bit with ECC</para> - </listitem> - <listitem><para>AS1000[A]: - <itemizedlist> - <listitem> - <para>72pin 36 bit Fast Page Mode SIMMs, 70ns or better</para> - </listitem> - <listitem> - <para>16 (EV5 machines) or 20 (EV4 machines) SIMM slots</para> - </listitem> - <listitem> - <para>max memory is 1 GB</para> - </listitem> - <listitem> - <para>uses ECC</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>AS800: Uses 60ns 3.3Volts EDO DIMMs</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>embedded VGA (on some mainboard models)</para> - </listitem> - <listitem> - <para>3 PCI, 2 EISA, 1 64-bit PCI/EISA combo (AS800)</para> - </listitem> - <listitem> - <para>7 PCI, 2 EISA (AS1000A)</para> - </listitem> - <listitem> - <para>2 PCI, 1 EISA/PCI, 7 EISA (AS1000)</para> - </listitem> - <listitem> - <para>embedded SCSI based on Symbios 810 [AS1000] or - Qlogic 1020 [AS1000A]</para> - </listitem> - </itemizedlist></para> - - <para>AS1000 based machines come in multiple enclosure types. Floor - standing, rack-mount, with or without StorageWorks SCSI chassis etc. - The electronics are the same.</para> - - <para>AS1000-systems: All EV4 based machines use standard PS/2 style - 36 bit 72pin SIMMs in sets of 5. The fifth SIMM is used for ECC. - All EV5 based machines use standard PS/2 style 36 bit 72pin SIMMs in sets - of 4. The ECC is done based on the 4 extra bits per SIMM - (4 bits out of 36). The EV5 mainboards have 16 SIMM slots, - the EV4 mainboards have 20 slots.</para> - - <para> AS800 machines use DIMMs in sets of 4. DIMM installation must - start in slots marked bank 0. A bank is four physically adjacent slots. - The biggest size DIMMs must be installed in bank 0 in case 2 banks - of different DIMM sizes are used. Max memory size is 2GB. Note - that these are EDO DIMMs.</para> - - <para>The AS1000/800 are somewhat stubborn when it comes to serial - consoles. They need - <screen>>>> <userinput>SET CONSOLE SERIAL</userinput></screen> - before they go for - a serial console. Pulling the keyboard from the machine is not sufficient, - like it is on most other Alpha models. Going back to a graphical console - needs - <screen>>>> <userinput>SET CONSOLE GRAPHICS</userinput></screen> - at the serial console.</para> - - <para>For AS800 you want to check if your Ultra-Wide SCSI is indeed - in Ultra mode. This can be done using the - <filename>EEROMCFG.EXE</filename> utility that is - on the Console Firmware Upgrade CDROM.</para> - - <para>For the AlphaServer1000/1000A/800 machines the kernel config - file must contain: - - <programlisting>options DEC_1000A -cpu EV4 # depends on the CPU model installed -cpu EV5 # depends on the CPU model installed</programlisting> - </para> - - </sect3> - - <sect3> - <title>DS10/VS10/XP900 (<quote>Webbrick</quote>) / XP1000 - (<quote>Monet</quote>) / DS10L (<quote>Slate</quote>)</title> - - <para>Webbrick and Monet are high performance workstations/servers - based on the EV6 CPU and the Tsunami chipset. Tsunami is also used in - much higher-end systems and as such has plenty of performance to offer. - DS10, VS10 and XP900 are different names for essentially the same system. - The differences are the software and options that are supported. DS10L - is a DS10 based machine in a 1U high rackmount enclosure. DS10L is - intended for ISPs and for HPTC clusters (e.g. Beowulf)</para> - - <sect4> - <title><quote>Webbrick / Slate</quote></title> - - <itemizedlist> - <listitem> - <para>21264 EV6 CPU at 466 MHz</para> - </listitem> - <listitem> - <para>L2 / Bcache: 2MB, ECC protected</para> - </listitem> - <listitem> - <para>memory bus: 128 bit via crossbar, 1.3GB/sec memory - bandwith</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>industry standard 200 pin 83 MHz buffered - ECC SDRAM DIMMs</para> - </listitem> - <listitem> - <para>4 DIMM slots for DS10; 2GB max memory</para> - </listitem> - <listitem> - <para>2 DIMM slots for DS10L; 1GB max memory</para> - </listitem> - <listitem> - <para>DIMMs are installed in pairs of 2</para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para>21271 Core Logic chipset (<quote>Tsunami</quote>)</para> - </listitem> - <listitem> - <para>2 on-board 21143 Fast Ethernet controllers</para> - </listitem> - <listitem> - <para>AcerLabs M5237 (Aladdin-V) USB controller</para> - </listitem> - <listitem> - <para>AcerLabs M1533 PCI-ISA bridge</para> - </listitem> - <listitem> - <para>AcerLabs Aladdin ATA-33 controller </para> - </listitem> - <listitem> - <para>embedded dual EIDE </para> - </listitem> - <listitem> - <para>expansion: 3 64-bit PCI slots and 1 32-bit PCI slot. - DS10L has a single 64bit PCI slot</para> - </listitem> - <listitem> - <para>2 16550A serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>2 USB</para> - </listitem> - <listitem> - <para>PS/2 keyboard & mouse port</para> - </listitem> - </itemizedlist> - - <para>The system has a smart power controller. This means that parts - of the system remain powered when it is switched off (like an ATX-style - PC power supply). Before servicing the machine remove the - power cord.</para> - - <para>Webbrick is shipped in a desktop-style case similar to the older - 21164 <quote>Maverick</quote> workstations but this case offers much better access - to the components. If you intend to build a farm you can rackmount them - in a 19-inch rack; they are 3U high. Slate is 1U high but has only - one PCI slot.</para> - - <para>DS10 has 4 DIMM slots. DIMMs are installed as pairs. Please note - that DIMM pairs are not installed in adjacent DIMM sockets but rather - physically interleaved. DIMM sizes of 32, 64, 128, 256 and 512 Mbytes - are supported.</para> - - <para>When 2 pairs of identical-sized DIMMs are installed DS10 will - use memory interleaving for increased performance. DS10L, which has - only 2 DIMM slots cannot do interleaving.</para> - - <para>Starting with SRM firmware version 5.9 you can boot from - Adaptec 2940-series adapters in addition to the usual set of Qlogic - and Symbios/NCR adapters.</para> - - <para>The base model comes with a FUJITSU 9.5GB ATA disk as its boot - device. &os; works just fine using EIDE disks on Webbrick. DS10 has - 2 IDE interfaces on the mainboard. Machines destined for Tru64 Unix or - VMS are standard equipped with Qlogic-driven Ultra-SCSI disks</para> - - <para>On the PCI bus 32 and 64 bit cards are supported, in 3.3V and - 5V variants.</para> - - <para>The USB interfaces are supported in &os; 4.1 and later.</para> - - <para>The kernel config file must contain: - <programlisting>options DEC_ST6600 -cpu EV5</programlisting></para> - - <note><para>Contrary to expectation there is no <literal>cpu EV6</literal> - defined for inclusion in the kernel config file. - The <literal>cpu EV5</literal> is mandatory to keep &man.config.8; - happy.</para></note> - </sect4> - - <sect4> - <title><quote>Monet</quote></title> - - <itemizedlist> - <listitem> - <para>21264 EV6 at 500 MHz - 21264 EV67 at 500 or 667 MHz (XP1000G, codenamed Brisbane) - CPU is mounted on a daughter-card which is field-upgradable</para> - </listitem> - <listitem> - <para>L2 / Bcache: 4MB, ECC protected</para> - </listitem> - <listitem> - <para>memory bus: 256 bit</para> - </listitem> - <listitem> - <para>memory: 128 or 256 Mbytes 100 MHz (PC100) 168 pin - JEDEC standard, registered ECC SDRAM DIMMs</para> - </listitem> - <listitem> - <para>21271 Core Logic chip-set (<quote>Tsunami</quote>)</para> - </listitem> - <listitem> - <para>1 on-board 21143 Ethernet controller</para> - </listitem> - <listitem> - <para>Cypress 82C693 USB controller</para> - </listitem> - <listitem> - <para>Cypress 82C693 PCI-ISA bridge</para> - </listitem> - <listitem> - <para>Cypress 82C693 controller</para> - </listitem> - <listitem> - <para>expansion: 2 independent PCI buses, driven by high-speed I/O - channels called <quote>hoses</quote>: - <itemizedlist> - <listitem> - <para>hose 0: (the upper 3 slots) - 2 64-bit PCI slots - 1 32-bit PCI slot - </para> - </listitem> - <listitem> - <para>hose 1: (the bottom 2 slots) - 2 32-bit PCI slots (behind a 21154 PCI-PCI bridge) - </para> - </listitem> - <listitem> - <para>2 of the 64-bit PCI slots are for - full-length cards</para> - </listitem> - <listitem> - <para>all of the 32-bit PCI slots are for short cards</para> - </listitem> - <listitem> - <para>1 of the 32-bit PCI slots is physically shared - with an ISA slot</para> - </listitem> - <listitem> - <para>all PCI slots run at 33MHz</para> - </listitem> - </itemizedlist></para> - </listitem> - <listitem> - <para>1 Ultra-Wide SCSI port based on a Qlogic 1040 chip - </listitem> - <listitem> - <para>2 16550A serial port - </listitem> - <listitem> - <para>1 parallel port - </listitem> - <listitem> - <para>PS/2 keyboard & mouse port - </listitem> - <listitem> - <para>embedded 16-bit ESS ES1888 sound chip - </listitem> - <listitem> - <para>2 USB ports - </listitem> - <listitem> - <para>graphics options: ELSA Gloria Synergy or - DEC/Compaq PowerStorm 3D accelerator cards</para> - </listitem> - </itemizedlist> - - <para>Monet is housed in a mini-tower like enclosure quite similar - to the Miata box.</para> - - <para>The on-board Qlogic UW-SCSI chip supports up to 4 internal - devices. There is no external connector for the on-board SCSI.</para> - - <para>For 500 MHz CPUs 83 MHz DIMMs will do. Compaq specifies PC100 - DIMMs for all CPU speeds. DIMMs are installed in sets of 4, starting - with the DIMM slots marked <quote>0</quote> Memory capacity is max 4 GB. - DIMMs are installed <quote>physically interleaved</quote>, note the - markings of the - slots. Memory bandwidth of Monet is twice that of Webbrick. The DIMMs - live on the CPU daughter-card. Note that the system uses ECC RAM so you - need DIMMs with 72 bits (not the generic PC-class 64 bit DIMMs)</para> - - <para>The EIDE interface is usable / SRM bootable so &os; can be rooted - on an EIDE disk. Although the Cypress chip has potential for 2 - EIDE channels Monet uses only one of them.</para> - - <para>The USB interface is supported by &os;.If you experience - problems trying to use the USB interface please check if - the SRM variable <varname>usb_enable</varname> is set to - <literal>on</literal>. You can change this by - performing: - <screen><prompt>>>></prompt> <userinput>SET USB_ENABLE ON</userinput></screen></para> - - <important><para>Don"t try to use Symbios-chip based SCSI - adapters in the PCI slots connected to hose 1. There is a - not-yet-found &os; bug that prevents this from working - correctly.</para></important> - - <important><para>Not all VGA cards will work behind the PCI-PCI - bridge (so in slots 4 and 5). Only cards that implement - VGA-legacy addressing - correctly will work. Workaround is to put the VGA card - <quote>before</quote> the bridge.</para></important> - - <para>The sound chip is not currently supported with &os;. </para> - - <para>The kernel config file must contain: - <programlisting>options DEC_ST6600 -cpu EV5</programlisting></para> - - <note><para>Contrary to expectation there is no - <literal>cpu EV6</literal> defined for inclusion in the kernel - config file. The <literal>cpu EV5</literal> is mandatory to - keep &man.config.8; happy.</para></note> - - </sect4> - </sect3> - - <sect3> - <title>DS20/DS20E (<quote>Goldrush</quote>)</title> - - <para>Features: - <itemizedlist> - <listitem> - <para>21264 EV6 CPU at 500 or 670 MHz</para> - </listitem> - <listitem> - <para>dual CPU capable machine</para> - </listitem> - <listitem> - <para>L2 / Bcache: 4 Mbytes per CPU</para> - </listitem> - <listitem> - <para>memory bus: dual 256 bit wide with crossbar switch</para> - </listitem> - <listitem> - <para>memory: - <itemizedlist> - <listitem> - <para>SDRAM DIMMs</para> - </listitem> - <listitem> - <para>installed in sets of 4</para> - </listitem> - <listitem> - <para>16 DIMM slots, max. 4GB</para> - </listitem> - <listitem> - <para>uses ECC</para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para>21271 Core Logic chip-set - (<quote>Tsunami</quote>)</para> - </listitem> - <listitem> - <para>embedded Adaptec ? Wide Ultra SCSI</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>2 independent PCI buses, driven - by high-speed I/O channels called <quote>hoses</quote></para> - </listitem> - <listitem> - <para>6 64-bit PCI slots, 3 per hose</para> - </listitem> - <listitem> - <para>1 ISA slot</para> - </listitem> - </itemizedlist> - </para> - </listitem> - </itemizedlist> - </para> - - <para>DS20 needs - <screen>>>> <userinput>SET CONSOLE SERIAL</userinput></screen> - before it goes for a serial console. Pulling the keyboard from - the machine is not sufficient. Going back to a graphical console - needs >>> - <screen><userinput>SET CONSOLE GRAPHICS</userinput></screen> - at the serial console. - Confusing is the fact that you will get SRM console - output on the graphics console with the console set to serial, - but when &os; boots it honors the <literal>CONSOLE</literal> - variable setting and all the boot messages as well as the login - prompt will go to the serial port.</para> - - <para>The DS20 is housed in a fat cube-like enclosure. The - enclosure also contains a StorageWorks SCSI hot-swap shelf for a - maximum of seven 3.5" SCSI devices. The DS20E is in a sleeker - case, and lacks the StorageWorks shelf.</para> - - <para>The embedded Adaptec SCSI chip on the DS20 is disabled and - is therefore not usable under &os;.</para> - - <para>Starting with SRM firmware version 5.9 you can boot from - Adaptec 2940-series adapters in addition to the usual set of - Qlogic and Symbios/NCR adapters. This unfortunately does not - include the embedded Adaptec SCSI chips.</para> - - <para>If you are using banks of DIMMs of different sizes the - biggest DIMMs should be installed in the DIMM slots marked - <literal>0</literal> on the mainboard. The DIMM slots should be - filled <quote>in order</quote> so after bank 0 install in bank 1 - and so on.</para> - - <para>Don't try to use Symbios-chip based SCSI adapters in the - PCI slots connected to hose 1. There is a not-yet-found &os; bug - that prevents this from working correctly. DS20 ships by default - with a Symbios on hose 1 so you have to move this card before - you can install/boot &os; on it.</para> - - <para>The kernel config file must contain: - <programlisting>options DEC_ST6600 -cpu EV5</programlisting> - </para> - - <note><para>Contrary to expectation there is no <literal>cpu EV6</literal> - defined for inclusion in the kernel config file. - The <literal>cpu EV5</literal> is mandatory to keep &man.config.8; - happy.</para></note> - </sect3> - - <sect3> - <title>AlphaPC 264DP / UP2000</title> - - <para>UP2000 is built by Alpha Processor Inc.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21264 EV6 CPU at 670 MHz</para> - </listitem> - <listitem> - <para>dual CPU capable</para> - </listitem> - <listitem> - <para>L2 / Bcache: 4 Mbytes per CPU</para> - </listitem> - <listitem> - <para>memory bus: 256 bit</para> - </listitem> - <listitem> - <para>memory: SDRAM DIMMs installed in sets of 4, uses - ECC, 16 DIMM slots, max. 4GB</para> - </listitem> - <listitem> - <para>21272 Core Logic chip-set (<quote>Tsunami</quote>)</para> - </listitem> - <listitem> - <para>embedded Adaptec AIC7890/91 Wide Ultra SCSI</para> - </listitem> - <listitem> - <para>2 embedded IDE based on Cypress 82C693 chips</para> - </listitem> - <listitem> - <para>embedded USB via Cypress 82C693</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>2 independent PCI buses, driven - by high-speed I/O channels called <quote>hoses</quote></para> - </listitem> - <listitem> - <para>6 64-bit PCI slots, 3 per hose</para> - </listitem> - <listitem> - <para>1 ISA slot</para> - </listitem> - </itemizedlist> - </para> - </listitem> - </itemizedlist> - </para> - - <para>Currently a maximum of 2GB memory is supported by &os;.</para> - - <para>The on-board Adaptec is not bootable but works with &os; - 4.0 and later as a datadisk-only SCSI bus.</para> - - <para>Busmaster DMA is supported on the first IDE interface - only.</para> - - <para>The kernel config file must contain: - <programlisting>options DEC_ST6600 -cpu EV5</programlisting> - </para> - - <note><para>Contrary to expectation there is no <literal>cpu - EV6</literal> defined for inclusion in the kernel config - file. The <literal>cpu EV5</literal> is mandatory to keep - &man.config.8; happy.</para></note> - </sect3> - - <sect3> - <title>AlphaServer 2000 (<quote>DemiSable</quote>), 2100 - (<quote>Sable</quote>), 2100A (<quote>Lynx</quote>)</title> - - <para>The AlphaServer 2[01]00 machines are intended as departmental - servers. This is medium iron. They are multi-CPU machines, up to 2 - CPUs (AS2000) or 4 CPUs (2100[A]) can be installed. Both floor-standing - and 19" rackmount boxes exist. Rackmount variations have - different numbers of I/O expansion slots, different max number - of CPUs and different maximum memory size. Some of the boxes come - with an integral StorageWorks shelf to house hot-swap SCSI disks. - There was an upgrade program available to convert your Sable - machine into a Lynx by swapping the I/O backplane (the C-bus - backplane remains). CPU upgrades were available as well.</para> - - <itemizedlist> - <listitem> - <para>21064 EV4[5] CPU[s] at 200, 233, 275 MHz or - 21164 EV5[6] CPU[s]s at 250, 300, 375, 400 MHz</para> - </listitem> - <listitem> - <para>cache: varies in size with the CPU model; 1, 4 or - 8Mbyte per CPU</para> - </listitem> - <listitem> - <para>embedded floppy controller driving a 2.88 Mbytes drive</para> - </listitem> - <listitem> - <para>embedded 10Mbit 21040 Ethernet [AS2100 only]</para> - </listitem> - <listitem> - <para>2 serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>PS/2 style keyboard & mouse port</para> - </listitem> - </itemizedlist> - - <para>The CPUs spec-ed as 200 MHz are in reality running at - 190 MHz. Maximum number of CPUs is 4. All CPUs must be of the - same type/speed.</para> - - <para>If any of the processors are ever marked as failed, they will - remain marked as failed even after they have been replaced (or reseated) - until you issue the command <screen><prompt>>>></prompt> <userinput>CLEAR_ERROR ALL</userinput></screen> - on the SRM console and power-cycle the machine. This may be true - for other modules (IO and memory) as well, but it has not been verified. - </para> - - <para>The machines use dedicated memory boards. These boards live on - a 128 bit C-bus shared with the CPU boards. DemiSable supports up - to 1GB, Sable up to 2GB. One of the memory bus slots can either - hold a CPU or a memory card. A 4 CPU machine can have a maximum of - 2 memory boards.</para> - - <para>Some memory board models house SIMMs. These are called SIMM - carriers. There are also memory modules that have soldered-on memory - chips instead of SIMMs. These are called <quote>flat memory - modules</quote>.</para> - - <para>SIMM boards are used in sets of eight 72-pin 36 bit FPM - memory of 70ns or faster. SIMM types supported are 1Mb x36 bit - (4 Mbyte) and 4Mb x36 bit (16 Mbyte). Each memory board can house - 4 banks of SIMMs. SIMM sizes can not be mixed on a single memory - board. The first memory module must be filled with SIMMs before - starting to fill the next memory module. Note that the spacing - between the slots is not that big, so make sure your SIMMs fit - physically (before buying them..)</para> - - <para>Both Lynx and Sable are somewhat stubborn when it comes to serial - consoles. They need - <screen><prompt>>>></prompt> <userinput> SET CONSOLE SERIAL</userinput></screen> - before they go for a serial console. - Pulling the keyboard from the machine is not sufficient, like it is - on many other Alpha models. Going back to a graphical console needs - <screen><prompt>>>></prompt> <userinput>SET CONSOLE GRAPHICS - </userinput></screen> at the serial console. On Lynx keep the VGA card in - one of the primary PCI slots. EISA VGA cards are not slot sensitive. - </para> - - <para>The machines are equipped with a small OCP - (Operator Control Panel) LCD screen. On this screen the self-test - messages are displayed during system initialization. You can put - your own little text there by using the SRM: - <screen><prompt>>>></prompt> <userinput>SET OCP_TEXT "FreeBSD" - </userinput></screen> is the recommended setting. - - <para>The SRM - <screen><prompt>>>></prompt> <userinput>SHOW FRU</userinput></screen> - command produces an overview of your configuration - with module serial numbers, hardware revisions and error log counts. - </para> - - <para>Both Sable, DemiSable and Lynx have Symbios 810 based - Fast SCSI on-board. Check if it is set to Fast SCSI speed - by - <screen><prompt>>>></prompt> <userinput>SHOW PKA0_FAST</userinput></screen>. - When set to 1 it is negotiating for Fast speeds. - <screen><prompt>>>></prompt> <userinput>SET PKA0_FAST 1</userinput></screen> - enables Fast SCSI speeds.</para> - - <para>AS2100[A] come equipped with a StorageWorks 7 slot SCSI - cage. A second cage can be added inside the cabinet. AS2000 - has a single 7 slot SCSI cage, which cannot be expanded with - an additional one. Note that the slot locations in these cages - map differently to SCSI IDs compared to the standard StorageWorks - shelves. Slot IDs from top to bottom are 0, 4, 1, 5, 2, 6, 3 - when using a single bus configuration.</para> - - <para>The cage can also be set to provide two independent SCSI - buses. This is used for embedded RAID controllers like the - KZPSC (Mylex DAC960). Slot ID assignments for split bus are, - from top to bottom: 0A, 0B, 1A, 1B, 2A, 2B, 3A, 3B. - Where A and B signify a SCSI bus. In a single bus configuration the - terminator module on the back of the SCSI cage is on the TOP. The jumper - module is on the BOTTOM. For split bus operation these two modules are - reversed. The terminator can be distinguished from the jumper - by noting the chips on the terminator. The jumper does not have - any active components on it.</para> - - <para>DemiSable has 7 EISA slots and 3 PCI slots. Sable has - 8 EISA and 3 PCI slots. Lynx, being newer, has 8 PCI - and 3 EISA slots. The Lynx PCI slots are grouped in - sets of 4. The 4 PCI slots closest to the CPU/memory - slots are the primary slots, so logically before the PCI bridge chip. - Note that contrary to expectation the primary PCI slots are the highest - numbered ones (PCI4 - PCI7).</para> - - <para>Make sure you run the EISA Configuration Utility (from floppy) - when adding/change expansion cards in EISA slots or after - upgrading your console firmware. This is done by inserting the - ECU floppy and typing - <screen><prompt>>>></prompt> <userinput>RUNECU</userinput></screen> - - <note><para>EISA slots are currently unsupported, but the Compaq Qvision - EISA VGA adapter is treated as an ISA device. It therefore - works OK as a console.</para></note> - - <para>A special Extended I/O module for use on the C-bus was - planned-for. If they ever saw daylight is unknown. In any case - &os; has never been verified with an ExtIO module.</para> - - <para>The machines can be equipped with redundant power supplies. Note - that the enclosure is equipped with interlock switches that switch - off power when the enclosure is opened. The system's cooling - fans are speed controlled. When the machine has more than 2 - CPUs and more than 1 memory board dual power supplies - are mandatory.</para> - - <para>The kernel config file must contain: - -<programlisting>options DEC_2100_A500 -cpu EV4 #dependent on CPU model installed -cpu EV5 #dependent on CPU model installed</programlisting> - </para> - - </sect3> - - <sect3> - <title>AlphaServer 4x00 (<quote>Rawhide</quote>)</title> - - <para>The AlphaServer 4x00 machines are intended as small enterprise - servers. Expect a 30" high pedestal cabinet or alternatively - the same system box in a 19" rack. This is medium iron, not - a typical hobbyist system. Rawhides are multi-CPU machines, up to - 4 CPUs can be in a single machine. Basic disk storage is housed in - one or two StorageWorks shelves at the bottom of the pedestal. The - Rawhides intended for the NT market are designated DIGITAL - Server 7300 (5/400 CPU), DIGITAL Server 7305 (5/533 CPU). A - trailing R on the part-number means a rackmount variant.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21164 EV5 CPUs at 266, 300 MHz or 21164A EV56 - CPUs at 400, 466, 533, 600 and 666 Mhz</para> - </listitem> - <listitem> - <para>cache: 4 Mbytes per CPU. EV5 300 MHz was also - available cache-less. 8 Mbytes for EV5 600Mhz</para> - </listitem> - <listitem> - <para>memory bus: 128 bit with ECC</para> - </listitem> - <listitem> - <para>embedded floppy controller</para> - </listitem> - <listitem> - <para>2 serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>PS/2 style keyboard & mouse port</para> - </listitem> - </itemizedlist> - </para> - - <para>Rawhide uses a maximum of 8 RAM modules. These modules are used - in pairs and supply 72 bits to the bus (this includes ECC bits). - Memory can be EDO RAM or synchronous DRAM. A fully populated Rawhide - has 4 pairs of memory modules. Given the choice use SDRAM for - best performance. The highest capacity memory board must be in - memory slot 0. A mix of memory board sizes is allowed. A mix - of EDO and SDRAM is also reported as working (assuming you don't - try to mix EDO and SDRAM in one module pair). A mix of EDO and SDRAM - results in the <emphasis>entire</emphasis> memory subsystem running at - the slower EDO timing</para> - - <para>Rawhide has an embedded Symbios 810 chip that gives you a - narrow fast-SCSI bus. Generally only the SCSI CDROM is driven by - this interface.</para> - - <para>Rawhides are available with a 8 64-bit PCI / 3 EISA - slot expansion backplanes (called <quote>Saddle</quote> modules). There - are 2 separate PCI buses, PCI0 and PCI1. PCI0 has 1 dedicated - PCI slot and (shared) 3 PCI/EISA slots. PCI0 also has a - PCI/EISA bridge that drives things like the serial and - parallel ports, keyboard/mouse etc. PCI1 has 4 PCI slots - and an Symbios 810 SCSI chip. VGA console cards must be installed - in a slot connected to PCI0.</para> - - <para>The current &os; implementation has problems in handling - PCI bridges. There is currently a limited fix in place which allows - for single level, single device PCI bridges. The fix allows the use of - the Digital supplied Qlogic SCSI card which sits behind - a 21054 PCI bridge chip.<para> - - <note><para>EISA slots are currently unsupported, but the Compaq Qvision - EISA VGA adapter is treated as an ISA device. It therefore works - OK as a console.<para></note> - - <para>Rawhide employs an I2C based power controller system. If - you want to be sure all power is removed from the system remove the - mains cables from the system.</para> - - <para>The kernel config file must contain: -<programlisting>options DEC_KN300 -cpu EV5</programlisting></para> - - </sect3> - - <sect3> - <title>AlphaServer 1200 (<quote>Tincup</quote>) and AlphaStation - 1200 (<quote>DaVinci</quote>)</title> - - <para>The AlphaServer 1200 machine is the successor to the - AlphaServer 1000A. It uses the same enclosure the 1000A uses, - but the logic is based on the AlphaServer 4000 design. These - are multi-CPU machines, up to 2 CPUs can be in a single machine. - Basic disk storage is housed in a StorageWorks shelves - The AS1200 intended for the NT market were designated DIGITAL - Server 5300 (5/400 CPU) and DIGITAL Server 5305 (5/533 CPU).</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21164A EV56 CPUs at 400 or 533 Mhz</para> - </listitem> - <listitem> - <para>cache: 4 Mbytes per CPU</para> - </listitem> - <listitem> - <para>memory bus: 128 bit with ECC, DIMM memory on two - memory daughter boards</para> - </listitem> - <listitem> - <para>embedded floppy controller</para> - </listitem> - <listitem> - <para>2 serial ports</para> - </listitem> - <listitem> - <para>1 parallel port</para> - </listitem> - <listitem> - <para>PS/2 style keyboard & mouse port</para> - </listitem> - </itemizedlist> - </para> - - <para>AS1200 uses 2 memory daughter cards. On each of these cards - are 8 DIMM slots. DIMMs must be installed in pairs. The maximum - memory size is 4 GBytes. Slots must be filled in order and slot - 0 must contain the largest size DIMM if different sized DIMMs are - used. AS1200 employs fixed starting addresses for DIMMs, each - DIMM pair starts at a 512 Mbyte boundary. This means that if - DIMMs smaller than 256 Mbyte are used the system's physical memory - map will contain <quote>holes</quote>. Supported DIMM sizes are 64 Mbytes - and 256 Mbytes. The DIMMs are 72 bit SDRAM based, as the - system employs ECC.</para> - - <note><para>&os; currently supports up to 2GBytes</para></note> - - <para>AS1200 has an embedded Symbios 810 drive Fast SCSI bus.</para> - - <para>Tincup has 5 64-bit PCI slots, one 1 32-bit PCI slot and one - EISA slot (which is physically shared with one of the 64-bit PCI slots). - There are 2 separate PCI buses, PCI0 and PCI1. PCI0 has the 32-bit PCI - slot and the 2 top-most 64-bit PCI slots. PCI0 also has an Intel 82375EB - PCI/EISA bridge that drives things like the serial and parallel ports, - keyboard/mouse etc. PCI1 has 4 64-bit PCI slots and an Symbios 810 - SCSI chip. VGA console cards must be installed in a slot - connected to PCI0.</para> - - <para>The system employs an I2C based power controller system. - If you want to be sure all power is removed from the system remove - the mains cables from the system. Tincup uses dual power supplies - in load-sharing mode and not as a redundancy pair.</para> - - <para>The kernel config file must contain: -<programlisting>options DEC_KN300 -cpu EV5</programlisting> - </para> - </sect3> - - <sect3> - <title>AlphaServer 8200 and 8400 (<quote>TurboLaser</quote>)</title> - - <para>The AlphaServer 8200 and 8400 machines are enterprise servers. - Expect a tall 19" cabinet (8200) or fat (8400) 19" rack. - This is big iron, not a hobbyist system. TurboLasers are multi-CPU - machines, up to 12 CPUs can be in a single machine. The TurboLaser - System Bus (TLSB) allows 9 nodes on the AS8400 and 5 nodes on - the AS8200. TLSB is 256 bit data, 40 bit address allowing 2.1 - GBytes/sec. Nodes on the TLSB can be CPUs, memory or I/O. A - maximum of 3 I/O ports are supported on a TLSB.</para> - - <para>Basic disk storage is housed in a StorageWorks shelf. - AS8400 uses 3 phase power, AS8200 uses single phase power.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21164 EV5/EV56 CPUs at up to 467 MHz or 21264 EV67 CPUs at - up to 625 MHz</para> - </listitem> - <listitem> - <para>one or two CPUs per CPU module</para> - </listitem> - <listitem> - <para>cache: 4Mbytes B-cache per CPU</para> - </listitem> - <listitem> - <para>memory bus: 256 bit with ECC</para> - </listitem> - <listitem> - <para>memory: big memory modules that plug into the TLSB, - which in turn hold special SIMM modules. Memory modules come - in varying sizes, up to 4 GBytes a piece. Uses ECC (8 bits - per 64 bits of data) 7 memory modules max for AS8400, - 3 modules max for AS8200. Maximum memory is 28 GBytes.</para> - </listitem> - <listitem> - <para>expansion: 3 system <quote>I/O ports</quote> that allow up to - 12 I/O channels each I/O channel can connect to - XMI, Futurebus+ or PCI boxes - </listitem> - </itemizedlist> - </para> - - <para>&os; supports (and has been tested with) up to 2 GBytes - of memory on TurboLaser. There is a trade-off to be made between - TLSB slots occupied by memory modules and TLSB slots occupied by - CPU modules. For example you can have 28GBytes of memory but only - 2 CPUs (1 module) at the same time.</para> - - <para>Only PCI expansion is supported on &os;. XMI or - Futurebus+ (which are AS8400 only) are both unsupported.</para> - - <para>The I/O port modules are designated KFTIA or KFTHA. The - I/O port modules supply so called <quote>hoses</quote> that connect to - up to 4 (KFTHA) PCI buses or 1 PCI bus (KFTIA). KFTIA has - embedded dual 10baseT Ethernet, single FDDI, 3 SCSI Fast - Wide Differential SCSI buses and a single Fast Wide Single Ended - SCSI bus. The FWSE SCSI is intended for the CDROM.</para> - - <para>KFTHA can drive via each of its 4 hoses a DWLPA or DWLPB - box. The DWLPx house a 12 slots 32 bit PCI backplane. Physically - the 12 slots are 3 4-slot buses but to the software it appears - as a single 12 slots PCI bus. A fully expanded AS8x00 can have - 3 (I/O ports) times 4 (hoses) times 12 (PCI slots/DWLPx) = - 144 PCI slots. The maximum bandwidth per KFTHA is 500 - Mbytes/second. DWLPA can also house 8 EISA cards, 2 slots - are PCI-only, 2 slots are EISA only. Of the 12 slots 2 - are always occupied by an I/O and connector module. DWLPB are the - prefered I/O boxes.</para> - - <para>For best performance distribute high bandwidth - (FibreChannel, Gigabit Ethernet) over multiple hoses and/or - multiple KFTHA/KFTIA.</para> - - <para>Currently PCI expansion cards containing PCI bridges are - not usable with &os;. Don't use them at this time.</para> - - <para>The single ended narrow SCSI bus on the KFTIA will turn up as - the <emphasis>fourth</emphasis> SCSI bus. The 3 fast-wide - differential SCSI buses of the KFTIA precede it. </para> - - <para>AS8x00 are generally run with serial consoles. Some - newer machines might have a graphical console of some sorts - but &os; has only been tested on a serial console.</para> - - <para>For serial console usage either change - <filename>/etc/ttys</filename> to have: - - <programlisting>console "/usr/libexec/getty std.9600" unknown on secure</programlisting> - -as the console entry, or add - - <programlisting>zs0 "/usr/libexec/getty std.9600" unknown on secure</programlisting> - -and make the zs node: - - <screen><userinput>cd /dev ; sh MAKEDEV zs0</userinput></screen> - </para> - - <para>For the AlphaServer 8x00 machines the kernel config file - must contain: - <programlisting>options DEC_KN8AE # Alpha 8200/8400 (Turbolaser) -cpu EV5</programlisting></para> - - <para>Contrary to expectation there is no <literal>cpu - EV6</literal> defined for inclusion in the kernel config - file. The <literal>cpu EV5</literal> is mandatory to keep - &man.config.8; happy.</para> - </sect3> - - <sect3> - <title>Alpha Processor Inc. UP1000</title> - - <para>The UP1000 is an ATX mainboard based on the 21264a - CPU which itself lives in a Slot B module. It is normally housed - in an ATX tower enclosure.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21264a Alpha CPU at 600 or 700 MHz in a Slot B - module (includes cooling fans)</para> - </listitem> - <listitem> - <para>memory bus: 128 bits to the L2 cache, - 64 bits from Slot B to the AMD-751</para> - </listitem> - <listitem> - <para>on-board Bcache / L2 cache: 2MB (600Mhz) or - 4MB (700Mhz)</para> - </listitem> - <listitem> - <para>AMD AMD-751 (<quote>Irongate</quote>) - system controller chip</para> - </listitem> - <listitem> - <para>Acer Labs M1543C PCI-ISA bridge controller / - super-IO chip</para> - </listitem> - <listitem> - <para>PS/2 mouse & keyboard port</para> - </listitem> - <listitem> - <para>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots - DIMM sizes supported are 64, 128 or 256 Mb in size</para> - </listitem> - <listitem> - <para>2 16550A serial port</para> - </listitem> - <listitem> - <para>1 ECP/EPP parallel port</para> - </listitem> - <listitem> - <para>floppy interface</para> - </listitem> - <listitem> - <para>2 embedded Ultra DMA33 IDE interface</para> - </listitem> - <listitem> - <para>2 USB ports</para> - </listitem> - <listitem> - <para>expansion: - <itemizedlist> - <listitem> - <para>4 32 bit PCI slots</para> - </listitem> - <listitem> - <para>2 ISA slots</para> - </listitem> - <listitem> - <para>1 AGP slot</para> - </listitem> - </itemizedlist> - </listitem> - </itemizedlist> - </para> - - <para>Slot B is a box-like enclosure that houses a - daughter-board for the CPU and cache. It has 2 small fans for - cooling. Loud fans..</para> - - <para>The machine needs ECC capable DIMMs, so 72 bit ones. - This does not appear to be documented in the UP1000 docs. The - system accesses the serial EEPROM on the DIMMs via the SM bus. - Note that if only a single DIMM is used it must be installed in - slot <emphasis>2</emphasis>. This is a bit counter-intuitive.</para> - - <para>The UP1000 needs a 400Watt ATX power supply according - to the manufacturer. This might be a bit overly - conservative/pessimistic judging from the power consumption of - the board & cpu. But as always you will have to take your - expansion cards and peripherals into account. The M1543C chip - contains power management functionality & temperature monitoring - (via I2C / SM bus).</para> - - <para>Chances are that your UP1000 comes by default with - AlphaBios only. The SRM console firmware is available from - the Alpha Processor Inc. website. It is currently available in - a beta version which was successfully used during the port of &os; - to the UP1000. </para> - - <para>The embedded Ultra DMA EIDE ports are bootable by the - SRM console.</para> - - <para>UP1000 SRM can boot off an Adaptec 294x adapter. Under high - I/O load conditions machine lockups have been observed using - the Adaptec 294x. A Symbios 875 based card works just fine, - using the sym driver. Most likely other cards based on the Symbios - chips that the sym driver supports will work as well.</para> - - <para>The USB interfaces are disabled by the SRM console and - have not (yet) been tested with &os;.</para> - - <para>For the UP1000 the kernel config file must contain: - <programlisting>options API_UP1000 # UP1000, UP1100 (Nautilus) -cpu EV5</programlisting> - </para> - - </sect3> - - <sect3> - <title>Alpha Processor Inc. UP1100</title> - - <para>The UP1100 is an ATX mainboard based on the 21264a CPU running - at 600 MHz. It is normally housed in an ATX tower enclosure.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21264a Alpha EV6 CPU at 600 or 700 MHz</para> - </listitem> - <listitem> - <para>memory bus: 100MHz 64-bit (PC-100 SDRAM), 800 MB/s memory - bandwidth</para> - </listitem> - <listitem> - <para>on-board Bcache / L2 cache: 2Mb</para> - </listitem> - <listitem> - <para>AMD AMD-751 (<quote>Irongate</quote>) system controller - chip</para> - </listitem> - <listitem> - <para>Acer Labs M1535D PCI-ISA bridge controller / - super-IO chip</para> - </listitem> - <listitem> - <para>PS/2 mouse & keyboard port</para> - </listitem> - <listitem> - <para>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 DIMM slots - DIMM sizes supported are 64, 128 or 256 Mb in size</para> - </listitem> - <listitem> - <para>2 16550A serial port</para> - </listitem> - <listitem> - <para>1 ECP/EPP parallel port</para> - </listitem> - <listitem> - <para>floppy interface</para> - </listitem> - <listitem> - <para>2 embedded Ultra DMA66 IDE interface</para> - </listitem> - <listitem> - <para>2 USB port</para> - </listitem> - <listitem> - <para>expansion: 3 32 bit PCI slots and 1 AGP2x slot</para> - </listitem> - </itemizedlist> - </para> - - <para>SRM console code comes standard with the UP1100. The SRM lives - in 2Mbytes of flash ROM.</para> - - <para>The machine needs ECC capable DIMMs, so 72 bit ones. - This does not appear to be documented in the UP1100 docs. The - system accesses the serial EEPROM on the DIMMs via the SM bus. - Note that if only a single DIMM is used it must be installed in - slot <emphasis>2</emphasis>. This is a bit counter-intuitive.</para> - - <para>The UP1100 needs a 400Watt ATX power supply according to - the manufacturer. This might be a bit overly conservative/pessimistic - judging from the power consumption of the board & cpu. But as - always you will have to take your expansion cards and - peripherals into account. The M1535D chip contains power - management functionality & temperature monitoring - (via I2C / SM bus using a LM75 thermal sensor).</para> - - <para>The UP1100 has an on-board 21143 10/100Mbit Ethernet - interface.</para> - - <para>The UP1100 is equipped with a SoundBlaster compatible audio - interface. Whether it works with &os; is as of yet unknown.</para> - - <para>The embedded Ultra DMA EIDE ports are bootable by - the SRM console.</para> - - <para>The UP1100 has 3 USB ports, 2 going external and one connected - to the AGP port.</para> - - <para>For the UP1100 the kernel config file must contain: - <programlisting>options API_UP1000 # UP1000, UP1100 (Nautilus) -cpu EV5</programlisting> - </para> - - <para>Contrary to expectation there is no <literal>cpu - EV6</literal> defined for inclusion in the kernel config - file. The <literal>cpu EV5</literal> is mandatory to keep - &man.config.8; happy.</para> - - </sect3> - - <sect3> - <title>Alpha Processor Inc. CS20</title> - - <para>The CS20 is a 19", 1U high rackmount server based - on the 21264[ab] CPU. It can have a maximum of 2 CPUs.</para> - - <para>Features: - <itemizedlist> - <listitem> - <para>21264a Alpha CPU at 667 MHz or 21264b 833 MHz - (max. 2 CPUs)</para> - </listitem> - <listitem> - <para>memory bus: 100MHz 256-bit wide</para> - </listitem> - <listitem> - <para>21271 Core Logic chipset (<quote>Tsunami</quote>)</para> - </listitem> - <listitem> - <para>Acer Labs M1533 PCI-ISA bridge controller / super-IO chip - </para> - </listitem> - <listitem> - <para>PS/2 mouse & keyboard port</para> - </listitem> - <listitem> - <para>memory: 168-pin PC100 PLL buffered/registered SDRAM DIMMS, - 8 DIMM slots, uses ECC memory, min 256 Mbytes / - max 2 GBytes of memory</para> - </listitem> - <listitem> - <para>2 16550A serial port</para> - </listitem> - <listitem> - <para>1 ECP/EPP parallel port</para> - </listitem> - <listitem> - <para>ALI M1543C Ultra DMA66 IDE interface</para> - </listitem> - <listitem> - <para>embedded dual Intel 82559 10/100Mbit Ethernet</para> - </listitem> - <listitem> - <para>embedded Symbios 53C1000 Ultra160 SCSI controller</para> - </listitem> - <listitem> - <para>expansion: 2 64 bit PCI slots (2/3 length)</para> - </listitem> - </itemizedlist> - </para> - - <para>SRM console code comes standard with the CS20. The SRM - lives in 2Mbytes of flash ROM.</para> - - <para>The CS20 needs ECC capable DIMMs. Note that it - uses <emphasis>buffered</emphasis> DIMMs.</para> - - <para>The CS20 has an I2C based internal monitoring system for things - like temperature, fans, voltages etc. The I2C also supports - <quote>wake on LAN</quote>.</para> - - <para>Each PCI slot is connected to it's own independent PCI bus - on the Tsunami.</para> - - <para>The embedded Ultra DMA EIDE ports are bootable by the - SRM console.</para> - - <para>The CS20 has an embedded slim-line IDE CD drive. There is - a front-accessible bay for a 1" high 3.5" SCSI hard-disk - drive with SCA connector.</para> - - <para>Note that there is no floppy disk drive (or a connector to - add one).</para> - - <para>The kernel config file must contain: - <programlisting>options DEC_ST6600 -cpu EV5</programlisting></para> - - <para>Contrary to expectation there is no <literal>cpu - EV6</literal> defined for inclusion in the kernel config - file. The <literal>cpu EV5</literal> is mandatory to keep - &man.config.8; happy.</para> - </sect3> - </sect2> - - <sect2> - <title>Supported Hardware Overview</title> - - <para>A word of caution: the installed base for &os; is not - nearly as large as for &os;/Intel. This means that the enormous - variation of PCI/ISA expansion cards out there has much less - chance of having been tested on alpha than on Intel. This is not - to imply they are doomed to fail, just that the chance of running - into something never tested before is much higher. - <filename>GENERIC</filename> - contains things that are known to work on Alpha only.</para> - - <para>The PCI and ISA expansion busses are fully supported. Turbo - Channel is not in <filename>GENERIC</filename> and has limited - support (see the relevant machine model info). The MCA bus is not - supported. The EISA bus is not supported for use with EISA - expansion cards as the EISA support code is lacking. ISA cards in - EISA slots are reported to work. The Compaq Qvision EISA VGA card - is driven in ISA mode and works OK as a console.</para> - - <para>1.44 Mbyte and 1.2 Mbyte floppy drives are supported. - 2.88 Mbyte drives sometimes found in Alpha machines are supported up to - 1.44Mbyte.</para> - - <para>ATA and ATAPI (IDE) devices are supported via the &man.ata.4; - driver framework. As most people run their Alphas with SCSI disks - it is not as well tested as SCSI. Be aware of boot-ability - restrictions for IDE disks. See the machine specific information.</para> - - <para>There is full SCSI support via the CAM layer for Adaptec - 2940x (AIC7xxx chip-based), Qlogic family and Symbios. Be aware of - the machine-specific boot-ability issues for the various adapter - types.</para> - - <para>The Qlogic QL2x00 FibreChannel host adapters are fully - supported.</para> - - <para>If you want to boot your Alpha over the Ethernet you will - obviously need an Ethernet card that the SRM console - recognizes. This generally means you need a board with an 21x4x - Ethernet chip as that is what Digital used. These chips are driven - by the &os; &man.de.4; (older driver) or &man.dc.4; (newer - driver). Some new SRM versions are known to recognize the Intel - 8255x Ethernet chips as driven by the &os; &man.fxp.4; driver. But - beware: the &man.fxp.4; driver is reported not to work correctly - with &os; (although it works excellently on &os;/x86).</para> - - <para>DEC DEFPA PCI FDDI network adapters are supported on alpha.</para> - - <para>In general the SRM console emulates a VGA-compatibility mode - on PCI VGA cards. This is, however, not guaranteed to work by - Compaq/DEC for each and every card type out there. When the SRM - thinks the VGA is acceptable &os; will be able to use it. The - console driver works just like on a &os;/intel machine. The TGA - video graphics which is embedded on for example Multia does - <emphasis>not</emphasis> - work with &os;. TGA based PCI cards are also <emphasis>not</emphasis> - supported. Please note that VESA modes are not supported on Alpha, - so that leaves you with 80x25 consoles.</para> - - <para>The <quote>PC standard</quote> serial ports found on most - Alphas are supported. For TurboChannel machines the serial ports - are also supported.</para> - - <para>ISDN (i4b) is not supported on &os;/alpha.</para> - </sect2> - - <sect2> - <title>Acknowledgments</title> - - <para>In compiling this file I used multiple information sources, - but <ulink url="http://www.netbsd.org/">the NetBSD Web - site</ulink> proved to be an invaluable source of information. If - it wasn't for NetBSD/alpha there probably would not be a - &os;/alpha in the first place.</para> - - <para>People who kindly helped me create this section: - <itemizedlist> - <listitem> - <para>&a.gallatin;</para> - </listitem> - <listitem> - <para>&a.chuckr;</para> - </listitem> - <listitem> - <para>&a.mjacob;</para> - </listitem> - <listitem> - <para>&a.msmith;</para> - </listitem> - <listitem> - <para>&a.obrien;</para> - </listitem> - <listitem> - <para>Christian Weisgerber</para> - </listitem> - <listitem> - <para>Kazutaka YOKOTA</para> - </listitem> - <listitem> - <para>Nick Maniscalco</para> - </listitem> - <listitem> - <para>Eric Schnoebelen</para> - </listitem> - <listitem> - <para>Peter van Dijk</para> - </listitem> - <listitem> - <para>Peter Jeremy</para> - </listitem> - <listitem> - <para>Dolf de Waal</para> - </listitem> - <listitem> - <para>Wim Lemmers, ex-Compaq</para> - </listitem> - <listitem> - <para>Wouter Brackman, Compaq</para> - </listitem> - <listitem> - <para>Lodewijk van den Berg, Compaq</para> - </listitem> - </itemizedlist> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/hardware/common/artheader.sgml b/release/doc/en_US.ISO_8859-1/hardware/common/artheader.sgml deleted file mode 100644 index 1e03991..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/common/artheader.sgml +++ /dev/null @@ -1,13 +0,0 @@ -<!-- $FreeBSD$ --> - -<articleinfo> - <title>&os; &release.current; &arch; Hardware Notes</title> - - <corpauthor>The FreeBSD Documentation Project</corpauthor> - - <copyright> - <year>2000</year> - <year>2001</year> - <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> - </copyright> -</articleinfo> diff --git a/release/doc/en_US.ISO_8859-1/hardware/common/config.sgml b/release/doc/en_US.ISO_8859-1/hardware/common/config.sgml deleted file mode 100644 index 0077f2b..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/common/config.sgml +++ /dev/null @@ -1,776 +0,0 @@ -<!-- $FreeBSD$ --> - -<sect1> - - <title>Boot-time Kernel Configuration</title> - - <para>This section describes the boot-time configuration of the - &os; kernel.</para> - - <note> - <para>How architecture-dependent is this?</para> - </note> - - <sect2> - - <title>Default Configuration</title> - - <para>The following table contains a list of all of the devices - that are present in the <filename>GENERIC</filename> kernel. This - is the essential part of the operating system that is placed in - your root partition during the installation process. A compressed - version of the <filename>GENERIC</filename> kernel is also used on - the installation floppy diskette and DOS boot image.</para> - - <para>The table describes the various parameters used by the - driver to communicate with the hardware in your system. There are - four parameters in the table, though not all are used by each and - every device: - - <informaltable frame=none> - <tgroup cols=2 align=left> - <colspec colwidth="*"> - <colspec colwidth="5*"> - <tbody> - <row> - <entry>Port</entry> - <entry>The starting I/O port used by the device, shown in hexadecimal.</entry> - </row> - <row> - <entry>IRQ</entry> - <entry>The interrupt the device uses to alert the driver to an event, - given in decimal.</entry> - </row> - <row> - <entry>DRQ</entry> - <entry>The DMA (direct memory access) channel the device uses to move - data to and from main memory, also given in decimal.</entry> - </row> - <row> - <entry>IOMem</entry> - <entry>The lowest (or starting) memory address used by the device, - also shown in hexadecimal.</entry> - </row> - </tbody> - </tgroup> - </informaltable> - - If an entry in the table has `n/a' for a value then it means that - the parameter in question does not apply to that device. A value - of `dyn' means that the correct value should be determined - automatically by the kernel when the system boots and that you - don't need to worry about it.</para> - - <para>If an entry is marked with an *, it means that support is - currently not available for it but should be back as soon as - someone converts the driver to work within the new (post-4.0) - framework.</para> - - <para> - <informaltable frame=none> - <tgroup cols=6 align=left> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="*"> - <colspec colwidth="5*"> - <thead> - <row> - <entry>Device</entry> - <entry>Port</entry> - <entry>IRQ</entry> - <entry>DRQ</entry> - <entry>IOMem</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry>fdc0</entry> - <entry>3f0</entry> - <entry>6</entry> - <entry>2</entry> - <entry>n/a</entry> - <entry>Floppy disk controller</entry> - </row> - - <row> - <entry>ata0</entry> - <entry>170</entry> - <entry>14</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATA/ATAPI controller</entry> - </row> - - <row> - <entry>ata1</entry> - <entry>170</entry> - <entry>15</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATA/ATAPI controller</entry> - </row> - - <row> - <entry>atadisk0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATA disk drives</entry> - </row> - - <row> - <entry>atapicd0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATAPI CDROM drives</entry> - </row> - - <row> - <entry>atapifd0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATAPI floppy drives</entry> - </row> - - <row> - <entry>atapist0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>ATAPI tape drives</entry> - </row> - - <row> - <entry>adv0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>AdvanSys Narrow SCSI controllers</entry> - </row> - - <row> - <entry>adw0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>AdvanSys Wide SCSI controllers</entry> - </row> - - <row> - <entry>amd0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>AMD 53C974 (Tekram DC390(T))</entry> - </row> - - <row> - <entry>ncr0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>NCR PCI SCSI controller</entry> - </row> - - <row> - <entry>bt0</entry> - <entry>330</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Buslogic SCSI controller</entry> - </row> - - <row> - <entry>aha0</entry> - <entry>330</entry> - <entry>dyn</entry> - <entry>5</entry> - <entry>dyn</entry> - <entry>Adaptec 154x/1535 SCSI controller</entry> - </row> - - <row> - <entry>ahb0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Adaptec 174x SCSI controller</entry> - </row> - - <row> - <entry>ahc0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Adaptec 274x/284x/294x SCSI controller</entry> - </row> - - <row> - <entry>aic0</entry> - <entry>340</entry> - <entry>11</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Adaptec 152x/AIC-6360/AIC-6260 SCSI controller</entry> - </row> - - <row> - <entry>isp0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>QLogic 10X0, 1240 Ultra SCSI, 1080/1280 Ultra2 SCSI, 12160 Ultra3 SCSI, 2X00 Fibre Channel SCSI controller</entry> - </row> - - <row> - <entry>dpt0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>DPT RAID SCSI controllers</entry> - </row> - - <row> - <entry>amr0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>AMI MegaRAID controllers</entry> - </row> - - <row> - <entry>mlx0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Mylex DAC960 RAID controllers</entry> - </row> - - <row> - <entry>twe0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>3ware Escalade RAID controllers</entry> - </row> - - <row> - <entry>asr0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>DPT SmartRaid V, VI, and Adaptec SCSI RAID</entry> - </row> - - <row> - <entry>mly0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Mylex AcceleRAID/eXtremeRAID</entry> - </row> - - <row> - <entry>aac</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>Adaptec FSA family PCI SCSI RAID</entry> - </row> - - <row> - <entry>ncv</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>NCR 53C500 based PC-Card SCSI</entry> - </row> - - <row> - <entry>nsp</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Workbit Ninja SCSI-3 based PC-Card SCSI</entry> - </row> - - <row> - <entry>stg</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>TMC 18C30/50 based ISA/PC-Card SCSI</entry> - </row> - - <row> - <entry>wt0</entry> - <entry>300</entry> - <entry>5</entry> - <entry>1</entry> - <entry>dyn</entry> - <entry>Wangtek and Archive QIC-02/QIC-36</entry> - </row> - - <row> - <entry>psm0</entry> - <entry>60</entry> - <entry>12</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>PS/2 Mouse</entry> - </row> - - <row> - <entry>mcd0</entry> - <entry>300</entry> - <entry>10</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Mitsumi CD-ROM</entry> - </row> - - <row> - <entry>matcd0</entry> - <entry>230</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Matsushita/Panasonic CD-ROM</entry> - </row> - - <row> - <entry>scd0</entry> - <entry>230</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Sony CD-ROM</entry> - </row> - - <row> - <entry>sio0</entry> - <entry>3f8</entry> - <entry>4</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Serial Port 0 (COM1)</entry> - </row> - - <row> - <entry>sio1</entry> - <entry>2f8</entry> - <entry>3</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Serial Port 1 (COM2)</entry> - </row> - - <row> - <entry>ppc0</entry> - <entry>dyn</entry> - <entry>7</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Printer ports</entry> - </row> - - <row> - <entry>dc0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>DEC/Intel 21143 cards and workalikes</entry> - </row> - - <row> - <entry>de0</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>DEC DC21x40 PCI based cards (including 21140 100bT cards)</entry> - </row> - - <row> - <entry>ed0</entry> - <entry>280</entry> - <entry>10</entry> - <entry>dyn</entry> - <entry>d8000</entry> - <entry>WD & SMC 80xx; Novell NE1000 & NE2000; 3Com 3C503; HP PC Lan+</entry> - </row> - - <row> - <entry>ep0</entry> - <entry>300</entry> - <entry>10</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>3Com 3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572, 3C574X, 3C579, 3C589</entry> - </row> - - <row> - <entry>ex0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>Intel EtherExpress Pro/10 cards</entry> - </row> - - <row> - <entry>fe0</entry> - <entry>300</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180 series cards.</entry> - </row> - - <row> - <entry>fxp0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Intel EtherExpress Pro/100B and Intel PRO/100+ Management Adapter</entry> - </row> - - <row> - <entry>ie0</entry> - <entry>300</entry> - <entry>10</entry> - <entry>dyn</entry> - <entry>d0000</entry> - <entry>AT&T StarLAN 10 and EN100; 3Com 3C507; NI5210; Intel EtherExpress (8/16,16[TP]) cards</entry> - </row> - - <row> - <entry>le0</entry> - <entry>300</entry> - <entry>5</entry> - <entry>dyn</entry> - <entry>d0000</entry> - <entry>Digital Equipment EtherWorks 2 and EtherWorks 3</entry> - </row> - - <row> - <entry>lnc0</entry> - <entry>280</entry> - <entry>10</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL, some PCnet-PCI cards)</entry> - </row> - - <row> - <entry>pcn0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA cards</entry> - </row> - - <row> - <entry>rl0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>RealTek 8129/8139 fast ethernet</entry> - </row> - - <row> - <entry>sf0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Adaptec AIC-6915 fast ethernet</entry> - </row> - - <row> - <entry>sis0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>SiS 900/SiS 7016 fast ethernet</entry> - </row> - - <row> - <entry>sn0</entry> - <entry>0x300</entry> - <entry>10</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>SMC 91xx ethernet</entry> - </row> - - <row> - <entry>ste0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Sundance ST201 fast ethernet</entry> - </row> - - <row> - <entry>tl0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>TI TNET100 'ThunderLAN' cards.</entry> - </row> - - <row> - <entry>tx0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>SMC 9432 'Epic' fast ethernet</entry> - </row> - - <row> - <entry>wb0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Winbond W89C840F PCI based cards.</entry> - </row> - - <row> - <entry>vr0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>VIA VT3043/VT86C100A PCI based cards.</entry> - </row> - - <row> - <entry>vx0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>3Com 3c59x ((Fast) Etherlink III)</entry> - </row> - - <row> - <entry>xe0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>Xircom CreditCard adapters (16 bit)</entry> - </row> - - <row> - <entry>xl0</entry> - <entry>dyn</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>dyn</entry> - <entry>3Com 3c900, 3c905, 3c905B, 3c905C, 3c980, 3cSOHO100 ((Fast) Etherlink XL)</entry> - </row> - - <row> - <entry>cs0</entry> - <entry>0x300</entry> - <entry>dyn</entry> - <entry>n/a</entry> - <entry>n/a</entry> - <entry>Crystal Semiconductor CS89x0-based cards.</entry> - </row> - - </tbody> - </tgroup> - </informaltable> - </para> - - <para>If the hardware in your computer is not set to the same - settings as those shown in the table and the item in conflict is - not marked 'dyn', you will have to either reconfigure your - hardware or use UserConfig to reconfigure the kernel to match the - way your hardware is currently set (see the next section).</para> - - <para>If the settings do not match, the kernel may be unable to - locate or reliably access the devices in your system.</para> - - </sect2> - - <sect2> - <title>Using UserConfig to change FreeBSD kernel settings</title> - - <note> - <para>The markup for this section leaves a lot to be desired.</para> - </note> - - <para>The FreeBSD kernel on the install floppy contains drivers - for every piece of hardware that could conceivably be used to - install the rest of the system with. Unfortunately, PC hardware - being what it is, some of these devices can be difficult to detect - accurately, and for some, the process of detecting another can - cause irreversible confusion.</para> - - <para>To make this process easier, FreeBSD provides UserConfig. - With this tool the user can configure and disable device drivers - before the kernel is loaded, avoiding potential conflicts, and - eliminating the need to reconfigure hardware to suit the default - driver settings.</para> - - <para>Once FreeBSD is installed, it will remember the changes made using - UserConfig, so that they only need be made once.</para> - - <para>It is important to disable drivers that are not relevant to - a system in order to minimize the possibility of interference, - which can cause problems that are difficult to track down.</para> - - <para>UserConfig features a command line interface for users with - serial consoles or a need to type commands, and a full screen - <quote>visual</quote> interface, which provides point-and-shoot - configuration functionality.</para> - - <para>Here is a sample UserConfig screen shot in - <quote>visual</quote> mode:</para> - -<screen>---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port-- - Storage : (Collapsed) - Network : - NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280 - NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300 - Communications : (Collapsed) - Input : (Collapsed) - Multimedia : ----Inactive Drivers-------------------------------------------Dev-------------- - Storage : - Network : (Collapsed) - Communications : - Input : - Multimedia : - - ----Parameters-for-device-ed0--------------------------------------------------- - Port address : 0x280 Memory address : 0xd8000 - IRQ number : 5 Memory size : 0x2000 - Flags : 0x0000 -------------------------------------------------------------------------------- - IO Port address (Hexadecimal, 0x1-0x2000) - [TAB] Change fields [Q] Save device parameters</screen> - - <para>The screen is divided into four sections: - <itemizedlist> - <listitem> - <para>Active Drivers. Listed here are the device drivers - that are currently enabled, and their basic - parameters.</para> - </listitem> - <listitem> - <para>Inactive Drivers. These drivers are present, but are - disabled.</para> - </listitem> - <listitem> - <para>Parameter edit field. This area is used for editing - driver parameters.</para> - </listitem> - <listitem> - <para>Help area. Keystroke help is displayed here.</para> - </listitem> - </itemizedlist> - </para> - - <para>One of the Active and Inactive lists is always in use, and - the current entry in the list will be shown with a highlight bar. - If there are more entries in a list than can be shown, it will - scroll. The bar can be moved up and down using the cursor keys, - and moved between lists with the TAB key.</para> - - <para>Drivers in the Active list may be marked - <literal>CONF</literal>. This indicates that one or more of their - parameters conflicts with another device, and indicates a - potential for problems. The total number of conflicts is - displayed at the top of the screen.</para> - - <para>As a general rule, conflicts should be avoided, either by - disabling conflicting devices that are not present in the system, - or by altering their configuration so that they match the - installed hardware.</para> - - <para>In the list areas, drivers are grouped by their basic - function. Groups can be <literal>Collapsed</literal> to simplify - the display (this is the default state for all groups). If a - group is collapsed, it will be shown with - <literal>Collapsed</literal> in the list, as above. To Expand a - Collapsed group, position the highlight bar over the group heading - and press Enter. To Collapse it again, repeat the process.</para> - - <para>When a device driver in the Active list is highlighted, its - full parameters are displayed in the Parameter edit area. Note - that not all drivers use all possible parameters, and some - hardware supported by drivers may not use all the parameters the - driver supports.</para> - - <para>To disable a driver, go to the Active list, Expand the group - it is in, highlight the driver and press Del. The driver will - move to its group in the Inactive list. (If the group is - collapsed or off the screen, you may not see the driver in its new - location.)</para> - - <para>To enable a driver, go to the Inactive list, Expand the - group it is in, highlight the driver and press Enter. The - highlight will move to the Active list, and the driver you have - just enabled will be highlighted, ready to be configured.</para> - - <para>To configure a driver, go to the Active list, Expand the - group it is in, highlight the driver and press Enter. The cursor - will move to the Parameter edit area, and the device's parameters - may be edited.</para> - - <para>While editing parameters, the TAB and cursor keys can be - used to move between fields. Most numeric values (except IRQ) are - entered in hexadecimal, as indicated by the '0x' at the beginning - of the field. The allowable values for a given field are show in - the Key Help area when the field is active.</para> - - <para>To finish configuring a driver, press 'Q'.</para> - - <para>Note that PCI, Microchannel and EISA devices can be probed - reliably, therefore they are not shown in the table above nor can - their settings be changed using UserConfig.</para> - </sect2> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/hardware/common/dev.sgml b/release/doc/en_US.ISO_8859-1/hardware/common/dev.sgml deleted file mode 100644 index 3de824d..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/common/dev.sgml +++ /dev/null @@ -1,2284 +0,0 @@ -<!-- - - The "Supported Devices" section of the release notes. - Generally processor-independent, with conditional text - inclusion handling any architecture-dependent text. - - Within each subsection describing a class of hardware - (i.e. Ethernet interfaces), list broad groups of devices - alphabetically as paragraphs sorted alphabetically (frequently - these groups will be arranged by manufacturer, i.e. 3Com - Ethernet interfaces). In cases where a group of devices - consists of multiple models (such as the 3C501, 3C503, etc.), - least each specific model or set of closely-related models as - a separate item in an itemized list, sorted alphabetically. - Where applicable, a "Miscellaneous" section may follow all - other named sections. - - These guidelines are not hard-and-fast rules, and exceptions - will occur. Following these guidelines (vague as they may be) - is highly recommendations to try to keep the formatting of - this section consistent. - - We give manpage references using the &man entities where - possible. If a driver has no manpage (and consequently no - &man entity, we simply give the name of the driver). - Please avoid doing &man entity conversions unless you - know for sure that an entity and manpage exist; sweeps through - this file to fix "missed" conversions are likely to break the - build. - - $FreeBSD$ - ---> - -<sect1> - <sect1info> - <pubdate>$FreeBSD$</pubdate> - </sect1info> - - <title>Supported Devices</title> - - <para>This section describes the devices currently known to be - supported by with &os; on the &arch; platform. Other configurations - may also work, but simply have not been tested yet. Feedback, - updates, and corrections to this list are encouraged.</para> - - <para>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 &os; base distribution (most should), it is referenced here.</para> - - <sect2> - <title>Disk Controllers</title> - <para>IDE/ATA controllers (&man.ata.4 driver) - <itemizedlist> - <listitem> - <para>Acerlabs Aladdin</para> - </listitem> - <listitem> - <para>AMD 756</para> - </listitem> - <listitem> - <para>CMD 646, 648 ATA66, and 649 ATA100</para> - </listitem> - <listitem> - <para>Cypress 82C693</para> - </listitem> - <listitem> - <para>Cyrex 5530</para> - </listitem> - <listitem> - <para>HighPoint HPT366, HPT370</para> - </listitem> - <listitem> - <para>Intel PIIX, PIIX3, PIIX4</para> - </listitem> - <listitem> - <para>Intel ICH, ICH2</para> - </listitem> - <listitem> - <para>Promise ATA100 OEM chip (pdc20265)</para> - </listitem> - <listitem> - <para>Promise Fasttrak-33, -66, -100</para> - </listitem> - <listitem> - <para>Promise Ultra-33, -66, -100</para> - </listitem> - <listitem> - <para>ServerWorks ROSB4 ATA33</para> - </listitem> - <listitem> - <para>SiS 5591</para> - </listitem> - <listitem> - <para>VIA 82C586, 82C686a, 82C686b</para> - </listitem> - </itemizedlist> - </para> - <para>Adaptec SCSI Controllers - <itemizedlist> - <listitem> - <para>Adaptec 1535 ISA SCSI controllers</para> - </listitem> - <listitem> - <para>Adaptec 154x series ISA SCSI controllers - (&man.aha.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>Adaptec 164x series MCA SCSI controllers (&man.aha.4; - driver)</para> - </listitem> - <listitem arch="i386"> - <para>Adaptec 174x series EISA SCSI controller in standard - and enhanced mode (&man.aha.4; and &man.ahb.4; dirver)</para> - </listitem> - <listitem> - <para>Adaptec 19160/274x/284x/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x - series EISA/VLB/PCI SCSI controllers, including - Narrow/Wide/Twin/Ultra/Ultra2 variants (&man.ahc.4; - driver)</para> - </listitem> - <listitem> - <para>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, AIC7880, - and AIC789x on-board - SCSI controllers (&man.ahc.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>Adaptec 1510 series ISA SCSI controllers (not for - bootable devices)</para> - </listitem> - <listitem arch="i386"> - <para>Adaptec 152x series ISA SCSI controllers (&man.aha.4; - driver)</para> - </listitem> - <listitem arch="i386"> - <para>Adaptec AIC-6260 and AIC-6360 based boards, which - includes the AHA-152x and SoundBlaster SCSI cards - (&man.aic.4; driver)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Adaptec 2100S, 3200S, and 3400S SCSI RAID - controllers (&man.asr.4; driver)</para> - - <para arch="i386">Adaptec 2400A ATA-100 RAID controller - (&man.asr.4; driver)</para> - - <para arch="i386">Adaptec FSA family RAID controllers (&man.aac.4; driver) - <itemizedlist> - <listitem> - <para>Adaptec AAC-2622</para> - </listitem> - <listitem> - <para>Adaptec AAC-364</para> - </listitem> - <listitem> - <para>Adaptec AAC-3642</para> - </listitem> - <listitem> - <para>Dell PERC 2/QC</para> - </listitem> - <listitem> - <para>Dell PERC 2/Si</para> - </listitem> - <listitem> - <para>Dell PERC 3/Di</para> - </listitem> - <listitem> - <para>Dell PERC 3/QC</para> - </listitem> - <listitem> - <para>Dell PERC 3/Si</para> - </listitem> - <listitem> - <para>HP NetRAID-4M</para> - </listitem> - </itemizedlist> - </para> - - <para>AdvanSys SCSI controllers (all models, &man.adv.4; and - &man.adw.4; drivers)</para> - - <para>BusLogic MultiMaster <quote>W</quote> Series Host Adapters - (&man.bt.4; driver): - <itemizedlist> - <listitem> - <para>BT-948</para> - </listitem> - <listitem> - <para>BT-958</para> - </listitem> - <listitem> - <para>BT-958D</para> - </listitem> - </itemizedlist> - </para> - - <para>BusLogic MultiMaster <quote>C</quote> Series Host Adapters - (&man.bt.4; driver): - <itemizedlist> - <listitem> - <para>BT-946C</para> - </listitem> - <listitem> - <para>BT-956C</para> - </listitem> - <listitem> - <para>BT-956CD</para> - </listitem> - <listitem> - <para>BT-445C</para> - </listitem> - <listitem> - <para>BT-747C</para> - </listitem> - <listitem> - <para>BT-757C</para> - </listitem> - <listitem> - <para>BT-757CD</para> - </listitem> - <listitem> - <para>BT-545C</para> - </listitem> - <listitem> - <para>BT-540CF</para> - </listitem> - </itemizedlist> - </para> - - <para>BusLogic MultiMaster <quote>S</quote> Series Host Adapters - (&man.bt.4; driver): - <itemizedlist> - <listitem> - <para>BT-445S</para> - </listitem> - <listitem> - <para>BT-747S</para> - </listitem> - <listitem> - <para>BT-747D</para> - </listitem> - <listitem> - <para>BT-757S</para> - </listitem> - <listitem> - <para>BT-757D</para> - </listitem> - <listitem> - <para>BT-545S</para> - </listitem> - <listitem> - <para>BT-542D</para> - </listitem> - <listitem> - <para>BT-742A</para> - </listitem> - <listitem> - <para>BT-542B</para> - </listitem> - </itemizedlist> - </para> - - <para>BusLogic MultiMaster <quote>A</quote> Series Host Adapters - (&man.bt.4; driver): - <itemizedlist> - <listitem> - <para>BT-742A</para> - </listitem> - <listitem> - <para>BT-542B</para> - </listitem> - </itemizedlist> - </para> - - <note> - <para>BusLogic/Mylex <quote>Flashpoint</quote> adapters are not yet - supported.</para> - </note> - <note> - <para>AMI FastDisk controllers that are true BusLogic - MultiMaster clones are also supported.</para> - </note> - - <note arch="i386"> - <para>The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B - and SDC3211F Microchannel (MCA) bus adapters are also - supported.</para> - </note> - - <para>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and - SmartRAID IV SCSI/RAID controllers (&man.dpt.4; driver)</para> - - <para arch="i386">DPT SmartRAID V and VI SCSI RAID controllers - (&man.asr.4; driver) - <itemizedlist> - <listitem> - <para>PM1554</para> - </listitem> - <listitem> - <para>PM2554</para> - </listitem> - <listitem> - <para>PM2654</para> - </listitem> - <listitem> - <para>PM2865</para> - </listitem> - <listitem> - <para>PM2754</para> - </listitem> - <listitem> - <para>PM3755</para> - </listitem> - <listitem> - <para>PM3757</para> - </listitem> - </itemizedlist> - </para> - - <para>AMI MegaRAID Express and Enterprise family RAID controllers - (&man.amr.4; driver) - <itemizedlist> - <listitem> - <para>MegaRAID Series 418</para> - </listitem> - <listitem> - <para>MegaRAID Enterprise 1200 (Series 428)</para> - </listitem> - <listitem> - <para>MegaRAID Enterprise 1300 (Series 434)</para> - </listitem> - <listitem> - <para>MegaRAID Enterprise 1400 (Series 438)</para> - </listitem> - <listitem> - <para>MegaRAID Enterprise 1500 (Series 467)</para> - </listitem> - <listitem> - <para>MegaRAID Enterprise 1600 (Series 471)</para> - </listitem> - <listitem> - <para>MegaRAID Elite 1500 (Series 467)</para> - </listitem> - <listitem> - <para>MegaRAID Elite 1600 (Series 493)</para> - </listitem> - <listitem> - <para>MegaRAID Express 100 (Series 466WS)</para> - </listitem> - <listitem> - <para>MegaRAID Express 200 (Series 466)</para> - </listitem> - <listitem> - <para>MegaRAID Express 300 (Series 490)</para> - </listitem> - <listitem> - <para>MegaRAID Express 500 (Series 475)</para> - </listitem> - <listitem> - <para>Dell PERC</para> - </listitem> - <listitem> - <para>Dell PERC 2/SC</para> - </listitem> - <listitem> - <para>Dell PERC 2/DC</para> - </listitem> - <listitem> - <para>Dell PERC 3/DCL</para> - </listitem> - <listitem> - <para>HP NetRaid-1si</para> - </listitem> - <listitem> - <para>HP NetRaid-3si</para> - </listitem> - <listitem> - <para>HP Embedded NetRaid</para> - </listitem> - </itemizedlist> - </para> - - <note arch="i386"> - <para>Booting from these controllers is supported. EISA - adapters are not supported.</para> - </note> - - <note arch="alpha"> - <para>Booting from these controllers is not supported due to SRM - limitations.</para> - </note> - - <para>Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x - and 5.x firmware (&man.mlx.4; driver) - <itemizedlist> - <listitem> - <para>DAC960P</para> - </listitem> - <listitem> - <para>DAC960PD</para> - </listitem> - <listitem> - <para>DAC960PDU</para> - </listitem> - <listitem> - <para>DAC960PL</para> - </listitem> - <listitem> - <para>DAC960PJ</para> - </listitem> - <listitem> - <para>DAC960PG</para> - </listitem> - <listitem> - <para>AcceleRAID 150</para> - </listitem> - <listitem> - <para>AcceleRAID 250</para> - </listitem> - <listitem> - <para>eXtremeRAID 1100</para> - </listitem> - </itemizedlist> - </para> - <note> - <para>Booting from these controllers is supported. EISA adapters - are not supported.</para> - - <para arch="alpha">Booting from these controllers is not - supported due to SRM limitations. This list includes - controllers sold by Digital/Compaq in Alpha systems in the - StorageWorks family, e.g. KZPSC or KZPAC.</para> - </note> - - <para arch="i386">Mylex PCI to SCSI RAID controllers with 6.x firmware - (&man.mly.4; driver) - <itemizedlist> - <listitem> - <para>AcceleRAID 160</para> - </listitem> - <listitem> - <para>AcceleRAID 170</para> - </listitem> - <listitem> - <para>AcceleRAID 352</para> - </listitem> - <listitem> - <para>eXtremeRAID 2000</para> - </listitem> - <listitem> - <para>eXtremeRAID 3000</para> - </listitem> - </itemizedlist> - </para> - <note> - <para>Compatible Mylex controllers not listed should work, but - have not been verified.</para> - </note> - - <para>3ware Escalade ATA RAID controllers (&man.twe.4; driver) - <itemizedlist> - <listitem> - <para>5000 series</para> - </listitem> - - <listitem arch="i386"> - <para>6000 series</para> - </listitem> - - <listitem arch="i386"> - <para>7000 series</para> - </listitem> - </itemizedlist> - </para> - - <para>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825, - 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, 53C895, 53C895a, - 53C896, 53C1010-33, 53C1010-66, 53C1000, 53C1000R PCI - SCSI controllers, either embedded on motherboard or on add-on - boards (&man.ncr.4; and &man.sym.4; drivers) - <itemizedlist> - <listitem> - <para>ASUS SC-200, SC-896</para> - </listitem> - <listitem> - <para>Data Technology DTC3130 (all variants)</para> - </listitem> - <listitem> - <para>DawiControl DC2976UW</para> - </listitem> - <listitem> - <para>Diamond FirePort (all)</para> - </listitem> - <listitem> - <para>NCR cards (all)</para> - </listitem> - <listitem> - <para>Symbios cards (all)</para> - </listitem> - <listitem> - <para>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and - 390U3W</para> - </listitem> - <listitem> - <para>Tyan S1365</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">NCR 53C500 based PC-Card SCSI host adapters (ncv - driver) - <itemizedlist> - <listitem> - <para>IO DATA PCSC-DV</para> - </listitem> - <listitem> - <para>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004</para> - </listitem> - <listitem> - <para>Macnica Miracle SCSI-II mPS110</para> - </listitem> - <listitem> - <para>Media Intelligent MSC-110, MSC-200</para> - </listitem> - <listitem> - <para>NEC PC-9801N-J03R</para> - </listitem> - <listitem> - <para>New Media Corporation BASICS SCSI</para> - </listitem> - <listitem> - <para>Qlogic Fast SCSI</para> - </listitem> - <listitem> - <para>RATOC REX-9530, REX-5572 (as SCSI only)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">TMC 18C30, 18C50 based ISA/PC-Card SCSI host - adapters (stg driver) - <itemizedlist> - <listitem> - <para>Future Domain SCSI2GO</para> - </listitem> - <listitem> - <para>IBM SCSI PCMCIA Card</para> - </listitem> - <listitem> - <para>ICM PSC-2401 SCSI</para> - </listitem> - <listitem> - <para>Melco IFC-SC</para> - </listitem> - <listitem> - <para>RATOC REX-5536, REX-5536AM, REX-5536M, - REX-9836A</para> - </listitem> - </itemizedlist> - </para> - - <para>Qlogic controllers and variants (&man.isp.4; driver) - <itemizedlist> - <listitem> - <para>Qlogic 1020, 1040 SCSI and Ultra SCSI host - adapters</para> - </listitem> - <listitem> - <para>Qlogic 1240 dual Ultra SCSI controllers</para> - </listitem> - <listitem> - <para>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD - controllers</para> - </listitem> - <listitem> - <para>Qlogic 12160 Ultra3 LVD controllers</para> - </listitem> - <listitem> - <para>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI - controllers</para> - </listitem> - <listitem> - <para>Performance Technology SBS440 ISP1000 variants</para> - </listitem> - <listitem> - <para>Performance Technology SBS450 ISP1040 variants</para> - </listitem> - <listitem> - <para>Performance Technology SBS470 ISP2100 variants</para> - </listitem> - <listitem> - <para>Antares Microsystems P-0033 ISP2100 variants</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">DTC 3290 EISA SCSI controller in 1542 emulation mode.</para> - - <para>Tekram DC390 and DC390T controllers, maybe other cards based - on the AMD 53c974 as well (&man.amd.4; driver)</para> - - <para arch="i386">Workbit Ninja SCSI-3 based PC-Card SCSI host - adapters (nsp driver) - <itemizedlist> - <listitem> - <para>Alpha-Data AD-PCS201</para> - </listitem> - <listitem> - <para>IO DATA CBSC16</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Parallel to SCSI interfaces (&man.vpo.4; driver) - <itemizedlist> - <listitem> - <para>AIC 7110 SCSI controller (built-in to Iomega ZIP drive)</para> - </listitem> - <listitem> - <para>Iomega Jaz Traveller interface</para> - </listitem> - <listitem> - <para>Iomega MatchMaker SCSI interface (built-in to Iomega - ZIP+ drive)</para> - </listitem> - </itemizedlist> - </para> - - <para>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 &man.cd.4;). WORM/CD-R/CD-RW writing support is provided - by &man.cdrecord.1;, which is in the Ports Collection.</para> - - <para>The following CD-ROM type systems are supported at this - time: - <itemizedlist> - <listitem> - <para>SCSI interface (also includes ProAudio Spectrum and - SoundBlaster SCSI) (&man.cd.4;)</para> - </listitem> - <listitem arch="i386"> - <para>Matsushita/Panasonic (Creative SoundBlaster) - proprietary interface (562/563 models) (&man.matcd.4;)</para> - </listitem> - <listitem arch="i386"> - <para>Sony proprietary interface (all models) (&man.scd.4;)</para> - </listitem> - <listitem> - <para>ATAPI IDE interface (&man.acd.4;)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">The following drivers were supported under the old SCSI - subsystem, but are not yet supported under the new CAM SCSI - subsystem: - <itemizedlist> - <listitem> - <para>NCR5380/NCR53400 (<quote>ProAudio Spectrum</quote>) - SCSI controller</para> - </listitem> - <listitem> - <para>UltraStor 14F, 24F and 34F SCSI controllers. - <note> - <para>There is work-in-progress to port the - UltraStor driver to the new CAM SCSI framework, but no - estimates on when or if it will be completed.</para> - </note> - </para> - </listitem> - <listitem> - <para>Seagate ST01/02 SCSI controllers</para> - </listitem> - <listitem> - <para>Future Domain 8xx/950 series SCSI controllers</para> - </listitem> - <listitem> - <para>WD7000 SCSI controller</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">The following device is unmaintained: - <itemizedlist> - <listitem> - <para>Mitsumi proprietary CD-ROM interface (all - models) (&man.mcd.4;)</para> - </listitem> - </itemizedlist> - </para> - - </sect2> - <sect2 id="ethernet"> - <title>Ethernet Interfaces</title> - - <para>Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec - AIC-6915 Fast Ethernet controller chip (&man.sf.4 driver) - <itemizedlist> - <listitem> - <para>ANA-62011 64-bit single port 10/100baseTX adapter</para> - </listitem> - <listitem> - <para>ANA-62022 64-bit dual port 10/100baseTX adapter</para> - </listitem> - <listitem> - <para>ANA-62044 64-bit quad port 10/100baseTX adapter</para> - </listitem> - <listitem> - <para>ANA-69011 32-bit single port 10/100baseTX - adapter</para> - </listitem> - <listitem> - <para>ANA-62020 64-bit single port 100baseFX adapter</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Allied-Telesis AT1700 and RE2000 cards - (&man.fe.4; driver)</para> - - <para>Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon - 1 and Tigon 2 chipsets (&man.ti.4; driver) - <itemizedlist> - <listitem> - <para>3Com 3c985-SX (Tigon 1 and 2)</para> - </listitem> - <listitem> - <para>Alteon AceNIC (Tigon 1 and 2)</para> - </listitem> - <listitem> - <para>Alteon AceNIC 1000baseT (Tigon 2)</para> - </listitem> - <listitem> - <para>Asante PCI 1000BASE-SX Gigabit Ethernet Adapter</para> - </listitem> - <listitem> - <para>Asante GigaNIX1000T Gigabit Ethernet Adapter</para> - </listitem> - <listitem> - <para></para> - </listitem> - <listitem> - <para>DEC/Compaq EtherWORKS 1000</para> - </listitem> - <listitem> - <para>Farallon PN9000SX</para> - </listitem> - <listitem> - <para>NEC Gigabit Ethernet</para> - </listitem> - <listitem> - <para>Netgear GA620 (Tigon 2)</para> - </listitem> - <listitem> - <para>Netgear GA620T (Tigon 2, 1000baseT)</para> - </listitem> - <listitem> - <para>Silicon Graphics Gigabit Ethernet</para> - </listitem> - </itemizedlist> - </para> - - <para>AMD PCnet NICs (&man.lnc.4; and &man.pcn.4; drivers) - <itemizedlist> - <listitem> - <para>AMD PCnet/PCI (79c970 & 53c974 or 79c974)</para> - </listitem> - <listitem> - <para>AMD PCnet/FAST</para> - </listitem> - <listitem> - <para>PCnet/FAST+</para> - </listitem> - <listitem> - <para>PCnet/FAST III</para> - </listitem> - <listitem> - <para>PCnet/PRO</para> - </listitem> - <listitem> - <para>PCnet/Home</para> - </listitem> - <listitem> - <para>HomePNA</para> - </listitem> - </itemizedlist> - </para> - -<!-- XXX tx.4 XXX --> - - <para arch="i386">SMC Ethernet NICs (&man.ed.4; driver) - <itemizedlist> - <listitem> - <para>Elite 16 WD8013 Ethernet interface</para> - </listitem> - <listitem> - <para>Most WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, - WD8003SBT and WD8013EBT based clones</para> - </listitem> - <listitem> - <para>SMC Elite Ultra</para> - </listitem> - <listitem> - <para>SMC Etherpower II</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">RealTek RTL 8002 Pocket Ethernet (&man.rdp.4; - driver)</para> - - <para>RealTek 8129/8139 Fast Ethernet NICs (&man.rl.4; driver) - <itemizedlist> - <listitem> - <para>Accton <quote>Cheetah</quote> EN1207D (MPX 5030/5038; - RealTek 8139 clone)</para> - </listitem> - <listitem> - <para>Allied Telesyn AT2550</para> - </listitem> - <listitem> - <para>Allied Telesyn AT2500TX</para> - </listitem> - <listitem> - <para>Genius GF100TXR (RTL8139)</para> - </listitem> - <listitem> - <para>KTX-9130TX 10/100 Fast Ethernet</para> - </listitem> - <listitem> - <para>NDC Communications NE100TX-E</para> - </listitem> - <listitem> - <para>Netronix Inc. EA-1210 NetEther 10/100</para> - </listitem> - <listitem> - <para>OvisLink LEF-8129TX</para> - </listitem> - <listitem> - <para>OvisLink LEF-8139TX</para> - </listitem> - <listitem> - <para>SMC EZ Card 10/100 PCI 1211-TX</para> - </listitem> - </itemizedlist> - </para> - - <para>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>Kingston KNE110TX</para> - </listitem> - <listitem> - <para>LinkSys EtherFast LNE100TX</para> - </listitem> - <listitem> - <para>Matrox FastNIC 10/100</para> - </listitem> - <listitem> - <para>NetGear FA310-TX Rev. D1</para> - </listitem> - </itemizedlist - </para> - - <para>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast - Ethernet NICs (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>Accton EN1217 (98715A)</para> - </listitem> - <listitem> - <para>Adico AE310TX (98715A)</para> - </listitem> - <listitem> - <para>Compex RL100-TX (98713 or 98713A)</para> - </listitem> - <listitem> - <para>CNet Pro120A (98713 or 98713A)</para> - </listitem> - <listitem> - <para>CNet Pro120B (98715)</para> - </listitem> - <listitem> - <para>NDC Communications SFA100A (98713A)</para> - </listitem> - <listitem> - <para>SVEC PN102TX (98713)</para> - </listitem> - </itemizedlist> - </para> - - <para>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs - (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>LinkSys EtherFast LNE100TX Version 2</para> - </listitem> - </itemizedlist> - </para> - - <para>Winbond W89C840F Fast Ethernet NICs (&man.wb.4; driver) - <itemizedlist> - <listitem> - <para>Trendware TE100-PCIE</para> - </listitem> - </itemizedlist> - </para> - - <para>VIA Technologies VT3043 <quote>Rhine I</quote> and VT86C100A - <quote>Rhine II</quote> Fast Ethernet NICs (&man.vr.4; driver) - <itemizedlist> - <listitem> - <para>AOpen/Acer ALN-320</para> - </listitem> - <listitem> - <para>D-Link DFE-530TX</para> - </listitem> - <listitem> - <para>Hawking Technologies PN102TX</para> - </listitem> - </itemizedlist> - </para> - - <para>Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast - Ethernet NICs (&man.sis.4; driver)</para> - - <para>National Semiconductor DP83815 Fast Ethernet NICs - (&man.sis.4; driver) - <itemizedlist> - <listitem> - <para>NetGear FA311-TX</para> - </listitem> - <listitem> - <para>NetGear FA312-TX</para> - </listitem> - </itemizedlist> - </para> - - <para>National Semiconductor DP83820 and DP83821 Gigabit Ethernet - NICs (&man.nge.4 driver) - <itemizedlist> - <listitem> - <para>Addtron AEG320T</para> - </listitem> - <listitem> - <para>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</para> - </listitem> - <listitem> - <para>D-Link DGE-500T</para> - </listitem> - <listitem> - <para>SMC EZ Card 1000 (SMC9462TX)</para> - </listitem> - </itemizedlist> - </para> - - <para>Sundance Technologies ST201 PCI Fast Ethernet NICs - (&man.ste.4; driver) - <itemizedlist> - <listitem> - <para>D-Link DFE-550TX</para> - </listitem> - </itemizedlist> - </para> - - <para>SysKonnect SK-984x PCI Gigabit Ethernet cards (&man.sk.4 drivers) - <itemizedlist> - <listitem> - <para>SK-9821 1000baseT copper, single port</para> - </listitem> - <listitem> - <para>SK-9822 1000baseT copper, dual port</para> - </listitem> - <listitem> - <para>SK-9841 1000baseLX single mode fiber, single port</para> - </listitem> - <listitem> - <para>SK-9842 1000baseLX single mode fiber, dual port</para> - </listitem> - <listitem> - <para>SK-9843 1000baseSX multimode fiber, single port</para> - </listitem> - <listitem> - <para>SK-9844 1000baseSX multimode fiber, dual port</para> - </listitem> - </itemizedlist> - </para> - - <para>Texas Instruments ThunderLAN PCI NICs (&man.tl.4; driver) - <itemizedlist> - <listitem> - <para>Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 - Dual-Port</para> - </listitem> - <listitem> - <para>Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI - UTP/Coax, 10/100 TX UTP</para> - </listitem> - <listitem> - <para>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</para> - </listitem> - <listitem> - <para>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP</para> - </listitem> - <listitem> - <para>Racore 8165 10/100baseTX</para> - </listitem> - <listitem> - <para>Racore 8148 10baseT/100baseTX/100baseFX - multi-personality</para> - </listitem> - </itemizedlist> - </para> - - <para>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (&man.dc.4; - driver)</para> - - <para>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (&man.dc.4; - driver) - <itemizedlist> - <listitem> - <para>LinkSys EtherFast LNE100TX v4.0/4.1</para> - </listitem> - </itemizedlist> - </para> - - <para>ADMtek Inc. AN986-based USB Ethernet NICs (&man.aue.4; driver) - <itemizedlist> - <listitem> - <para>Billionton USB100</para> - </listitem> - <listitem> - <para>D-Link DSB-650TX</para> - </listitem> - <listitem> - <para>LinkSys USB100TX</para> - </listitem> - <listitem> - <para>Melco Inc. LUA-TX</para> - </listitem> - <listitem> - <para>SMC 2202USB</para> - </listitem> - </itemizedlist> - </para> - - <para>CATC USB-EL1210A-based USB Ethernet NICs (&man.cue.4; driver) - <itemizedlist> - <listitem> - <para>Belkin F5U011</para> - </listitem> - <listitem> - <para>Belkin F5U111</para> - </listitem> - <listitem> - <para>CATC Netmate</para> - </listitem> - <listitem> - <para>CATC Netmate II</para> - </listitem> - </itemizedlist> - </para> - - <para>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs - (&man.kue.4; driver) - <itemizedlist> - <listitem> - <para>3Com 3c19250</para> - </listitem> - <listitem> - <para>Abocom URE 450</para> - </listitem> - <listitem> - <para>ADS Technologies USB-10BT</para> - </listitem> - <listitem> - <para>ATen UC10T</para> - </listitem> - <listitem> - <para>Corega USB-T</para> - </listitem> - <listitem> - <para>D-Link DSB-650</para> - </listitem> - <listitem> - <para>Entrega NET-USB-E45</para> - </listitem> - <listitem> - <para>LinkSys USB10T</para> - </listitem> - <listitem> - <para>Netgear EA101</para> - </listitem> - <listitem> - <para>Peracom USB Ethernet Adapter</para> - </listitem> - <listitem> - <para>SMC 2102USB</para> - </listitem> - <listitem> - <para>SMC 2104USB</para> - </listitem> - </itemizedlist> - </para> - - <para>ASIX Electronics AX88140A PCI NICs (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>Alfa Inc. GFC2204</para> - </listitem> - <listitem> - <para>CNet Pro110B</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">DEC EtherWORKS II NICs (DE200, DE201, DE202, and - DE422) (&man.le.4; driver)</para> - - <para arch="i386">DEC EtherWORKS III NICs (DE203, DE204, and DE205) - (&man.le.4; driver)</para> - - <para>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 - based NICs (&man.de.4; driver) - <itemizedlist> - <listitem> - <para>Asante</para> - </listitem> - <listitem> - <para>Cogent EM100FX and EM440TX</para> - </listitem> - <listitem> - <para>DEC DE425, DE435, DE450, and DE500</para> - </listitem> - <listitem> - <para>SMC Etherpower 8432T, 9332, and 9334</para> - </listitem> - <listitem> - <para>ZYNX ZX 3xx</para> - </listitem> - </itemizedlist> - </para> - - <para>DEC/Intel 21143 based Fast Ethernet NICs (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>DEC DE500-BA</para> - </listitem> - <listitem> - <para>Compaq Presario 7900 series built-in Ethernet</para> - </listitem> - <listitem> - <para>D-Link DFE-570TX</para> - </listitem> - <listitem> - <para>Kingston KNE100TX</para> - </listitem> - <listitem> - <para>LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet</para> - </listitem> - </itemizedlist> - </para> - - <para>Davicom DM9100 and DM9102 PCI Fast Ethernet NICs (&man.dc.4; driver) - <itemizedlist> - <listitem> - <para>Jaton Corporation XpressNet</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Fujitsu MB86960A/MB86965A based Fast Ethernet NICs - (&man.fe.4; driver) - <itemizedlist> - <listitem> - <para>CONTEC C-NET(PC)C Ethernet</para> - </listitem> - <listitem> - <para>Eiger Labs EPX-10BT</para> - </listitem> - <listitem> - <para>Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 - Ethernet PCMCIA</para> - </listitem> - <listitem> - <para>Fujitsu Towa LA501 Ethernet</para> - </listitem> - <listitem> - <para>HITACHI HT-4840-11</para> - </listitem> - <listitem> - <para>NextCom J Link NC5310</para> - </listitem> - <listitem> - <para>RATOC REX-5588, REX-9822, REX-4886, REX-R280</para> - </listitem> - <listitem> - <para>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">HP PC Lan+ cards (model numbers: 27247B and 27252A) - (&man.ed.4; driver)</para> - - <para>Intel EtherExpress NICs - <itemizedlist> - <listitem arch="i386"> - <para>Intel EtherExpress 16 (&man.ie.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>Intel EtherExpress Pro/10 and Pro/10+ Ethernet - (&man.ex.4; driver)</para> - </listitem> - <listitem> - <para>Intel EtherExpress Pro/100B PCI Fast Ethernet - (&man.fxp.4; driver)</para> - </listitem> - <listitem> - <para>Intel PRO/1000, PRO/1000-F, and PRO/1000-T Gigabit Ethernet - (&man.wx.4; driver)</para> - </listitem> - <listitem> - <para>Intel InBusiness 10/100 PCI Network Adapter - (&man.fxp.4 driver)</para> - </listitem> - <listitem> - <para>Intel PRO/100+ Management Adapter (&man.fxp.4 driver)</para> - </listitem> - </itemizedlist> - </para> - -<!-- XXX ie.4 cards that are not 3C507 or EtherExpress 16 XXX --> - - <para>Isolan AT 4141-0 (16 bit)</para> - - <para>Isolink 4110 (8 bit)</para> - - <para>Novell NE1000, NE2000, and NE2100 Ethernet interface - (&man.ed.4; driver)</para> - - <para>Novell NE2000 clones (&man.ed.4; driver) - <itemizedlist> - <listitem> - <para>NetVin 5000</para> - </listitem> - <listitem> - <para>RealTek 8029</para> - </listitem> - <listitem> - <para>Surecom NE-34</para> - </listitem> - <listitem> - <para>VIA VT86C926</para> - </listitem> - <listitem> - <para>Winbond W89C940</para> - </listitem> - </itemizedlist> - </para> - - <para>3Com Ethernet and Fast Ethernet NICs - <itemizedlist> - <listitem> - <para>3C450-TX HomeConnect adapter (&man.xl.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>3C501 (&man.el.4; driver)</para> - </listitem> - <listitem> - <para>3C503 Etherlink II (&man.ed.4; driver)</para> - </listitem> - <listitem> - <para>3c505 Etherlink/+</para> - </listitem> - <listitem arch="i386"> - <para>3C507 Etherlink 16/TP (&man.ie.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>3C509 (&man.ep.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>3C529 MCA (&man.ep.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>3C579 EISA (&man.ep.4; driver)</para> - </listitem> - <listitem> - <para>3C589/589B/589C/589D/589E/XE589ET/574TX/574B - PC-card/PCMCIA (&man.ep.4; driver)</para> - </listitem> - <listitem arch="i386"> - <para>3C590/592/595 (&man.vx.4; driver)</para> - </listitem> - <listitem> - <para>3C900/905/905B/905C PCI (&man.xl.4; driver)</para> - </listitem> - <listitem> - <para>3C556/556B MiniPCI (&man.xl.4; driver)</para> - </listitem> - <listitem> - <para>3C575TX/575B/XFE575BT/575C/656/656B/656C (Cardbus)</para> - </listitem> - <listitem> - <para>EISA (Fast) Etherlink III / (Fast) Etherlink XL</para> - </listitem> - <listitem> - <para>3c980/3c980B Fast Etherlink XL server adapter - (&man.xl.4; driver)</para> - </listitem> - <listitem> - <para>3cSOHO100-TX OfficeConnect adapter (&man.xl.4; driver)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Crystal Semiconductor CS89x0-based NICs - (&man.cs.4; driver) - <itemizedlist> - <listitem> - <para>IBM Etherjet ISA</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">NE2000 compatible PC-Card (PCMCIA) Ethernet and - FastEthernet cards (&man.ed.4; driver) - <itemizedlist> - <listitem> - <para>AR-P500 Ethernet card</para> - </listitem> - <listitem> - <para>Accton EN2212/EN2216/UE2216(OEM)</para> - </listitem> - <listitem> - <para>Allied Telesis CentreCOM LA100-PCM_V2</para> - </listitem> - <listitem> - <para>AmbiCom 10BaseT card</para> - </listitem> - <listitem> - <para>BayNetworks NETGEAR FA410TXC Fast Ethernet</para> - </listitem> - <listitem> - <para>CNet BC40 adapter</para> - </listitem> - <listitem> - <para>COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD</para> - </listitem> - <listitem> - <para>Compex Net-A adapter</para> - </listitem> - <listitem> - <para>CyQ've ELA-010</para> - </listitem> - <listitem> - <para>D-Link DE-650/660</para> - </listitem> - <listitem> - <para>Danpex EN-6200P2</para> - </listitem> - <listitem> - <para>Elecom Laneed LD-CDL/TX</para> - </listitem> - <listitem> - <para>IO DATA PCLATE</para> - </listitem> - <listitem> - <para>IBM Creditcard Ethernet I/II</para> - </listitem> - <listitem> - <para>IC-CARD Ethernet/IC-CARD+ Ethernet</para> - </listitem> - <listitem> - <para>Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card - (PCMPC100 V2)</para> - </listitem> - <listitem> - <para>Melco LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX</para> - </listitem> - <listitem> - <para>NDC Ethernet Instant-Link</para> - </listitem> - <listitem> - <para>National Semiconductor InfoMover NE4100</para> - </listitem> - <listitem> - <para>Network Everywhere Ethernet 10BaseT PC Card</para> - </listitem> - <listitem> - <para>Planex FNW-3600-T</para> - </listitem> - <listitem> - <para>Socket LP-E</para> - </listitem> - <listitem> - <para>Surecom EtherPerfect EP-427</para> - </listitem> - <listitem> - <para>TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card</para> - </listitem> - <listitem> - <para>Telecom Device SuperSocket RE450T</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Megahertz X-Jack Ethernet PC-Card CC-10BT (sn - driver)</para> - - <para arch="i386">Xircom X3201 (Cardbus) based Ethernet cards, including the following: - <itemizedlist> - <listitem> - <para>IBM EtherJet Cardbus Adapter</para> - </listitem> - <listitem> - <para>Intel PRO/100 Mobile Cardbus (versions that use the - X3201 chipset)</para> - </listitem> - <listitem> - <para>Xircom Cardbus Realport</para> - </listitem> - <listitem> - <para>Xircom Cardbus Ethernet 10/100</para> - </listitem> - <listitem> - <para>Xircom Cardbus Ethernet II 10/100</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Xircom CreditCard adapters (16 bit) and - workalikes (xe driver) - <itemizedlist> - <listitem> - <para>Accton EN2226/Fast EtherCard (16-bit verison)</para> - </listitem> - <listitem> - <para>Compaq Netelligent 10/100 PC Card</para> - </listitem> - <listitem> - <para>Intel EtherExpress PRO/100 Mobile Adapter (16-bit - verison)</para> - </listitem> - <listitem> - <para>Xircom 10/100 Network PC Card adapter</para> - </listitem> - <listitem> - <para>Xircom Realport card + modem(Ethernet part)</para> - </listitem> - <listitem> - <para>Xircom CreditCard Ethernet 10/100</para> - </listitem> - <listitem> - <para>Xircom CreditCard 10Base-T <quote>CreditCard Ethernet - Adapter IIps</quote> (PS-CE2-10)</para> - </listitem> - <listitem> - <para>Xircom CreditCard Ethernet 10/100 + modem (Ethernet - part)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">National Semiconductor DP8393X (SONIC) Ethernet - cards (snc driver) - <itemizedlist> - <listitem> - <para>NEC PC-9801-83, -84, -103, and -104</para> - </listitem> - <listitem> - <para>NEC PC-9801N-25 and -J02R</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Gigabit Ethernet cards based on the Level 1 - LXT1001 NetCellerator controller (&man.lge.4; driver) - <itemizedlist> - <listitem> - <para>D-Link DGE=500SX</para> - </listitem> - <listitem> - <para>SMC TigerCard 1000 (SMC9462SX)</para> - </listitem> - </itemizedlist> - </para> - - </sect2> - - <sect2> - <title>FDDI Interfaces</title> - <para>DEC DEFPA/DEFEA FDDI NICs (&man.fpa.4; driver)</para> - </sect2> - - <sect2> - <title>ATM Interfaces</title> - <para>Efficient Networks, Inc. ENI-155p ATM PCI Adapters - (hea driver)</para> - <para>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa driver)</para> - <para>The ATM support in &os; supports the following signaling - protocols: - <itemizedlist> - <listitem> - <para>The ATM Forum UNI 3.1 signaling protocol</para> - </listitem> - <listitem> - <para>The ATM Forum UNI 3.0 signaling protocol</para> - </listitem> - <listitem> - <para>The ATM Forum ILMI address registration</para> - </listitem> - <listitem> - <para>FORE Systems' proprietary SPANS signaling protocol</para> - </listitem> - <listitem> - <para>Permanent Virtual Channels (PVCs)</para> - </listitem> - </itemizedlist> - </para> - <para>Support for the IETF <quote>Classical IP and ARP over - ATM</quote> model is provided, compliant with the following RFCs - and Internet Drafts: - <itemizedlist> - <listitem> - <para>RFC 1483, <quote>Multiprotocol Encapsulation over ATM - Adaptation Layer 5</quote></para> - </listitem> - <listitem> - <para>RFC 1577, <quote>Classical IP and ARP over ATM</quote></para> - </listitem> - <listitem> - <para>RFC 1626, <quote>Default IP MTU for use over ATM - AAL5</quote></para> - </listitem> - <listitem> - <para>RFC 1755, <quote>ATM Signaling Support for IP over ATM</quote></para> - </listitem> - <listitem> - <para>RFC 2225, <quote>Classical IP and ARP over ATM</quote></para> - </listitem> - <listitem> - <para>RFC 2334, <quote>Server Cache Synchronization Protocol - (SCSP)</quote></para> - </listitem> - <listitem> - <para>Internet Draft - <filename>draft-ietf-ion-scsp-atmarp-00.txt</filename>, <quote>A - Distributed ATMARP Service Using SCSP</quote></para> - </listitem> - </itemizedlist> - </para> - <para>Support for an ATM sockets interface is also provided.</para> - </sect2> - <sect2> - <title>Wireless Network Interfaces</title> - - <para arch="i386">NCR / AT&T / Lucent Technologies WaveLan T1-speed - ISA/radio LAN cards (&man.wl.4; driver)</para> - - <para arch="i386">Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA - standard speed (2Mbps) and turbo speed (6Mbps) wireless network - adapters and workalikes (&man.wi.4; driver) - <note> - <para>The ISA versions of these adapters are actually PCMCIA - cards combined with an ISA to PCMCIA bridge card, so both kinds - of devices work with the same driver.</para> - </note> - <itemizedlist> - <listitem> - <para>NCR WaveLAN/IEEE 802.11</para> - </listitem> - <listitem> - <para>3COM 3crwe737A AirConnect Wireless LAN PC Card</para> - </listitem> - <listitem> - <para>Addtron AWA100</para> - </listitem> - <listitem> - <para>Cabletron RoamAbout 802.11 DS</para> - </listitem> - <listitem> - <para>Compaq WL100</para> - </listitem> - <listitem> - <para>Corega KK Wireless LAN PCC-11</para> - </listitem> - <listitem> - <para>ELECOM Air@Hawk/LD-WL11/PCC</para> - </listitem> - <listitem> - <para>Farallon Skyline 11Mbps Wireless</para> - </listitem> - <listitem> - <para>ICOM SL-1100</para> - </listitem> - <listitem> - <para>Laneed Wireless card</para> - </listitem> - <listitem> - <para>Melco Airconnect WLI-PCM-L11</para> - </listitem> - <listitem> - <para>NEC Wireless Card CMZ-RT-WP</para> - </listitem> - <listitem> - <para>PLANEX GeoWave/GW-NS110</para> - </listitem> - <listitem> - <para>TDK LAK-CD011WL</para> - </listitem> - </itemizedlist> - </para> - - <para>Aironet 802.11 wireless adapters (&man.an.4; driver) - <itemizedlist> - <listitem> - <para>Aironet 4500/4800 series - (PCMCIA, PCI, and ISA adapters are all supported)</para> - </listitem> - <listitem> - <para>Cisco Systems Aironet 340, 341, and 342</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Raytheon Raylink 2.4GHz wireless adapters (&man.ray.4; driver) - <itemizedlist> - <listitem> - <para>Webgear Aviator</para> - </listitem> - <listitem> - <para>Webgear Aviator Pro</para> - </listitem> - <listitem> - <para>Raylink PC Card</para> - </listitem> - </itemizedlist> - </para> - - <para>AMD Am79C930 and Harris (Intersil) based 802.11 cards (awi driver) - <itemizedlist> - <listitem> - <para>BayStack 650 and 660</para> - </listitem> - <listitem> - <para>Farallon SkyLINE Wireless</para> - </listitem> - <listitem> - <para>Icom SL-200</para> - </listitem> - <listitem> - <para>Melco WLI-PCM</para> - </listitem> - <listitem> - <para>NEL SSMagic</para> - </listitem> - <listitem> - <para>Netwave AirSurfer Plus and AirSurfer Pro</para> - </listitem> - <listitem> - <para>ZoomAir 4000</para> - </listitem> - </itemizedlist> - </para> - - </sect2> - - <sect2 arch="i386"> - <title>ISDN Interfaces</title> - <para>AcerISDN P10 ISA PnP (experimental)</para> - <para>Asuscom ISDNlink 128K ISA</para> - <para>ASUSCOM P-IN100-ST-D (and other Winbond W6692-based cards)</para> - <para>AVM - <itemizedlist> - <listitem> - <para>A1</para> - </listitem> - <listitem> - <para>B1 ISA (tested with V2.0)</para> - </listitem> - <listitem> - <para>B1 PCI (tested with V4.0)</para> - </listitem> - <listitem> - <para>Fritz!Card classic</para> - </listitem> - <listitem> - <para>Fritz!Card PnP</para> - </listitem> - <listitem> - <para>Fritz!Card PCI</para> - </listitem> - <listitem> - <para>T1</para> - </listitem> - </itemizedlist> - </para> - <para>Creatix - <itemizedlist> - <listitem> - <para>ISDN-S0</para> - </listitem> - <listitem> - <para>ISDN-S0 P&P</para> - </listitem> - </itemizedlist> - </para> - <para>Dr. Neuhaus Niccy Go@ and compatibles</para> - <para>Dynalink IS64PH</para> - <para>Eicon Diehl DIVA 2.0 and 2.02</para> - <para>ELSA - <itemizedlist> - <listitem> - <para>ELSA PCC-16</para> - </listitem> - <listitem> - <para>QuickStep 1000pro ISA</para> - </listitem> - <listitem> - <para>MicroLink ISDN/PCI</para> - </listitem> - <listitem> - <para>QuickStep 1000pro PCI</para> - </listitem> - </itemizedlist> - </para> - <para>ITK ix1 Micro ( < V.3, non-PnP version )</para> - <para>Sedlbauer Win Speed</para> - <para>Siemens I-Surf 2.0</para> - <para>TELEINT ISDN SPEED No.1 (experimental)</para> - <para>Teles - <itemizedlist> - <listitem> - <para>S0/8</para> - </listitem> - <listitem> - <para>S0/16</para> - </listitem> - <listitem> - <para>S0/16.3</para> - </listitem> - <listitem> - <para>S0/16.3 PnP</para> - </listitem> - <listitem> - <para>16.3c ISA PnP (experimental)</para> - </listitem> - <listitem> - <para>Teles PCI-TJ</para> - </listitem> - </itemizedlist> - </para> - <para>Traverse Technologies NETjet-S PCI</para> - <para>USRobotics Sportster ISDN TA intern</para> - <para>Winbond W6692 based PCI cards</para> - </sect2> - - <sect2> - <title>Multi-port Serial Interfaces</title> - <para>AST 4 port serial card using shared IRQ</para> - - <para arch="i386">ARNET serial cards (&man.ar.4; driver) - <itemizedlist> - <listitem> - <para>ARNET 8 port serial card using shared IRQ</para> - </listitem> - <listitem> - <para>ARNET (now Digiboard) Sync 570/i high-speed serial</para> - </listitem> - </itemizedlist> - </para> - - <para>Boca multi-port serial cards - <itemizedlist> - <listitem> - <para>Boca BB1004 4-Port serial card (Modems - <emphasis>not</emphasis> supported)</para> - </listitem> - <listitem> - <para>Boca IOAT66 6-Port serial card (Modems supported)</para> - </listitem> - <listitem> - <para>Boca BB1008 8-Port serial card (Modems - <emphasis>not</emphasis> supported)</para> - </listitem> - <listitem> - <para>Boca BB2016 16-Port serial card (Modems supported)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Comtrol Rocketport card (rp driver)</para> - - <para arch="i386">Cyclades Cyclom-y serial board (&man.cy.4; driver)</para> - - <para>STB 4 port card using shared IRQ</para> - - <para>DigiBoard intelligent serial cards (&man.dgb.4; driver) - <itemizedlist> - <listitem> - <para>DigiBoard PC/Xe series</para> - </listitem> - <listitem> - <para>DigiBoard PC/Xi series</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">SDL Communication serial boards - <itemizedlist> - <listitem> - <para>SDL Communications Riscom/8 Serial Board (rc driver)</para> - </listitem> - <listitem> - <para>SDL Communications RISCom/N2 and N2pci high-speed sync - serial boards (&man.sr.4; driver)</para> - </listitem> - </itemizedlist> - </para> - - <para arch="i386">Stallion Technologies multiport serial boards - <itemizedlist> - <listitem> - <para>EasyIO (&man.stl.4; driver)</para> - </listitem> - <listitem> - <para>EasyConnection 8/32 (&man.stl.4; driver)</para> - </listitem> - <listitem> - <para>EasyConnection 8/64 (&man.stli.4; driver)</para> - </listitem> - <listitem> - <para>ONboard 4/16 (&man.stli.4; driver)</para> - </listitem> - <listitem> - <para>Brumby (&man.stli.4; driver)</para> - </listitem> - </itemizedlist> - </para> - - <para>Specialix SI/XIO/SX multiport serial cards, with both the - older SIHOST2.x and the new <quote>enhanced</quote> (transputer - based, aka JET) host cards (ISA, EISA and PCI are supported) - (&man.si.4; driver)</para> - - </sect2> - <sect2> - <title>Audio Devices</title> - <para>Advance (&man.sbc.4; driver) - <itemizedlist> - <listitem> - <para>Asound 100 and 110</para> - </listitem> - <listitem> - <para>Logic ALS120 and ALS4000</para> - </listitem> - </itemizedlist> - </para> - <para>CMedia sound chips - <itemizedlist> - <listitem> - <para>CMI8338/CMI8738</para> - </listitem> - </itemizedlist> - </para> - <para>Crystal Semiconductor (&man.csa.4; driver) - <itemizedlist> - <listitem> - <para>CS461x/462x Audio Accelerator</para> - </listitem> - <listitem> - <para>CS428x Audio Controller</para> - </listitem> - </itemizedlist> - </para> - <para>ENSONIQ (&man.pcm.4; driver) - <itemizedlist> - <listitem> - <para>AudioPCI ES1370/1371</para> - </listitem> - </itemizedlist> - </para> - <para>ESS - <itemizedlist> - <listitem> - <para>ES1868, ES1869, ES1879 and ES1888 (&man.sbc.4; driver)</para> - </listitem> - <listitem> - <para>Maestro-1, Maestro-2, and Maestro-2E</para> - </listitem> - <listitem> - <para>Maestro-3/Allegro</para> - <note> - <para>The Maestro-3/Allegro cannot be compiled into the - &os; kernel due to licensing restrictions, it cannot be - compiled into the kernel. To use this driver, add - the following line to - <filename>/boot/loader.conf</filename>:</para> - - <screen><userinput>maestro3_load="YES"</userinput></screen> - </note> - </listitem> - </itemizedlist> - </para> - <para>ForteMedia fm801</para> - <para>Gravis (&man.gusc.4; driver) - <itemizedlist> - <listitem> - <para>UltraSound MAX</para> - </listitem> - <listitem> - <para>UltraSound PnP</para> - </listitem> - </itemizedlist> - </para> - <para>MSS/WSS Compatible DSPs (&man.pcm.4; driver)</para> - <para>NeoMagic 256AV/ZX (&man.pcm.4; driver)</para> - <para>OPTi 931/82C931 (&man.pcm.4; driver)</para> - <para>S3 Sonicvibes</para> - <para>Creative Technologies SoundBlaster series (&man.sbc.4; driver) - <itemizedlist> - <listitem> - <para>SoundBlaster</para> - </listitem> - <listitem> - <para>SoundBlaster Pro</para> - </listitem> - <listitem> - <para>SoundBlaster AWE-32</para> - </listitem> - <listitem> - <para>SoundBlaster AWE-64</para> - </listitem> - <listitem> - <para>SoundBlaster AWE-64 GOLD</para> - </listitem> - <listitem> - <para>SoundBlaster ViBRA-16</para> - </listitem> - </itemizedlist> - </para> - <para>Trident 4DWave DX/NX (&man.pcm.4; driver)</para> - <para>VIA Technologies VT82C686A</para> - <para>Yamaha - <itemizedlist> - <listitem> - <para>DS1</para> - </listitem> - <listitem> - <para>DS1e</para> - </listitem> - </itemizedlist> - </para> - </sect2> - <sect2> - <title>Camera and Video Capture Devices</title> - <para>Brooktree Bt848/849/878/879-based frame grabbers (&man.bktr.4; - driver) - <itemizedlist> - <listitem> - <para>AverMedia cards</para> - </listitem> - <listitem> - <para>Hauppauge Wincast TV and WinTV boards (PCI)</para> - </listitem> - <listitem> - <para>Intel Smart Video Recorder III</para> - </listitem> - <listitem> - <para>Miro PC TV</para> - </listitem> - <listitem> - <para>STB TV PCI</para> - </listitem> - <listitem> - <para>Video Highway XTreme</para> - </listitem> - <listitem> - <para>VideoLogic Captivator PCI</para> - </listitem> - </itemizedlist> - </para> - <para>Connectix QuickCam</para> - <para arch="i386">Cortex1 frame grabber (ctx driver)</para> - <para arch="i386">Creative Labs Video Spigot frame grabber (spigot driver)</para> - <para>Matrox Meteor Video frame grabber (&man.meteor.4; driver)</para> - </sect2> - - <sect2 id="usb"> - <title>USB Devices</title> - - <para>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.</para> - - <note> - <para>USB Ethernet adapters can be found in the section listing <link - linkend="ethernet">Ethernet interfaces</link>.</para> - </note> - - <para>Host Controllers (&man.ohci.4; and &man.uhci.4; drivers) - <itemizedlist> - <listitem> - <para>ALi Aladdin-V</para> - </listitem> - <listitem> - <para>AMD-756</para> - </listitem> - <listitem> - <para>CMD Tech 670 & 673</para> - </listitem> - <listitem> - <para>Intel 82371SB (PIIX3)</para> - </listitem> - <listitem> - <para>Intel 82371AB and EB (PIIX4)</para> - </listitem> - <listitem> - <para>Intel 82801AA (ICH)</para> - </listitem> - <listitem> - <para>Intel 82801AB (ICH0)</para> - </listitem> - <listitem> - <para>Intel 82801BA/BAM (ICH2)</para> - </listitem> - <listitem> - <para>Intel 82443MX</para> - </listitem> - <listitem> - <para>NEC uPD 9210</para> - </listitem> - <listitem> - <para>OPTi 82C861 (FireLink)</para> - </listitem> - <listitem> - <para>SiS 5571</para> - </listitem> - <listitem> - <para>VIA 83C572 USB</para> - </listitem> - <listitem> - <para>UHCI or OHCI compliant motherboard chipsets (no - exceptions known)</para> - </listitem> - </itemizedlist> - </para> - <para>USB host controllers (PCI) - <itemizedlist> - <listitem> - <para>ADS Electronics PCI plug-in card (2 ports)</para> - </listitem> - <listitem> - <para>Entrega PCI plug-in card (4 ports)</para> - </listitem> - </itemizedlist> - </para> - <para>Hubs - <itemizedlist> - <listitem> - <para>Andromeda hub</para> - </listitem> - <listitem> - <para>MacAlly self powered hub (4 ports)</para> - </listitem> - <listitem> - <para>NEC hub</para> - </listitem> - </itemizedlist> - </para> - <para>Keyboards (&man.ukbd.4; driver) - <itemizedlist> - <listitem> - <para>Apple iMac keyboard</para> - </listitem> - <listitem> - <para>BTC BTC7935 keyboard with PS/2 mouse port</para> - </listitem> - <listitem> - <para>Cherry G81-3504 keyboard</para> - </listitem> - <listitem> - <para>Logitech M2452 keyboard</para> - </listitem> - <listitem> - <para>MacAlly iKey keyboard</para> - </listitem> - <listitem> - <para>Microsoft keyboard</para> - </listitem> - </itemizedlist> - </para> - <para>Miscellaneous - <itemizedlist> - <listitem> - <para>ActiveWire I/O Board</para> - </listitem> - <listitem> - <para>Rio500 MP3 player (&man.urio.4; driver)</para> - </listitem> - </itemizedlist> - </para> - <para>Modems (umodem driver) - <itemizedlist> - <listitem> - <para>3Com 5605</para> - </listitem> - <listitem> - <para>Metricom Ricochet GS USB wireless modem</para> - </listitem> - </itemizedlist> - </para> - <para>Mice (&man.ums.4; driver) - <itemizedlist> - <listitem> - <para>Agiler Mouse 29UO</para> - </listitem> - <listitem> - <para>Apple iMac Mouse</para> - </listitem> - <listitem> - <para>Belkin Mouse</para> - </listitem> - <listitem> - <para>Chic mouse</para> - </listitem> - <listitem> - <para>Cypress mouse</para> - </listitem> - <listitem> - <para>Genius Niche mouse</para> - </listitem> - <listitem> - <para>Kensington Mouse-in-a-Box</para> - </listitem> - <listitem> - <para>Logitech wheel mouse (3 buttons)</para> - </listitem> - <listitem> - <para>Logitech PS/2 / USB mouse (3 buttons)</para> - </listitem> - <listitem> - <para>MacAlly mouse (3 buttons)</para> - </listitem> - <listitem> - <para>Microsoft IntelliMouse (3 buttons)</para> - </listitem> - <listitem> - <para>Trust Ami Mouse (3 buttons)</para> - </listitem> - </itemizedlist> - </para> - <para>Printers and parallel printer conversion cables (ulpt driver) - <itemizedlist> - <listitem> - <para>ATen parallel printer adapter</para> - </listitem> - <listitem> - <para>Belkin F5U002 parallel printer adapter</para> - </listitem> - <listitem> - <para>Entrega USB-to-parallel printer adapter</para> - </listitem> - </itemizedlist> - </para> - <para>Scanners (through SANE) (&man.uscanner.4; driver) - <itemizedlist> - <listitem> - <para>Perfection 636U</para> - </listitem> - <listitem> - <para>HP ScanJet 4100C, 5200C, 6300C</para> - </listitem> - </itemizedlist> - </para> - <para>Storage (&man.umass.4; driver) - <itemizedlist> - <listitem> - <para>Iomega USB Zip 100Mb (primitive support still)</para> - </listitem> - <listitem> - <para>Matshita CF-VFDU03 floppy drive</para> - </listitem> - <listitem> - <para>Microtech USB-SCSI-HD 50 USB to SCSI cable</para> - </listitem> - <listitem> - <para>Panasonic floppy drive</para> - </listitem> - <listitem> - <para>Y-E Data floppy drive (720/1.44/2.88Mb)</para> - </listitem> - </itemizedlist> - </para> - </sect2> - - <sect2> - <title>Miscellaneous</title> - - <para arch="i386">FAX-Modem/PCCARD - <itemizedlist> - <listitem> - <para>Melco IGM-PCM56K/IGM-PCM56KH</para> - </listitem> - <listitem> - <para>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)</para> - </listitem> - </itemizedlist> - </para> - - <para>Floppy drives (&man.fd.4; driver)</para> - <para>Genius and Mustek hand scanners</para> - <para>GPB and Transputer drivers</para> - <para>HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R - drives</para> - <para>Keyboards including: - <itemizedlist> - <listitem> - <para>AT-style keyboards</para> - </listitem> - <listitem> - <para>PS/2 keyboards</para> - </listitem> - <listitem arch="i386"> - <para>USB keyboards (specific instances are listed in the - section describing <link linkend="usb">USB devices</link>)</para> - </listitem> - </itemizedlist> - </para> - <para>Loran-C receiver (Dave Mills experimental hardware, loran driver).</para> - <para>Mice including: - <itemizedlist> - <listitem arch="i386"> - <para>Bus mice (&man.mse.4; driver)</para> - </listitem> - <listitem> - <para>PS/2 mice (&man.psm.4; driver)</para> - </listitem> - <listitem> - <para>Serial mice</para> - </listitem> - <listitem arch="i386"> - <para>USB mice (specific instances are listed in the - section describing <link linkend="usb">USB devices</link>)</para> - </listitem> - </itemizedlist> - </para> - - <para>Parallel ports</para> - - <para>PC-compatible joysticks (&man.joy.4 driver)</para> - - <para arch="i386">PHS Data Communication Card/PCCARD - <itemizedlist> - <listitem> - <para>NTT DoCoMo P-in Comp@ct</para> - </listitem> - <listitem> - <para>Panasonic KX-PH405</para> - </listitem> - <listitem> - <para>SII MC-P200</para> - </listitem> - </itemizedlist> - </para> - - <para>Serial ports</para> - - <para arch="i386">X-10 power controllers (&man.tw.4 driver)</para> - - <para>Xilinx XC6200-based reconfigurable hardware cards compatible - with the HOT1 from <ulink url="http://www.vcc.com/">Virtual - Computers</ulink> (xrpu driver).</para> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/hardware/common/hw.ent b/release/doc/en_US.ISO_8859-1/hardware/common/hw.ent deleted file mode 100644 index eca9bc8..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/common/hw.ent +++ /dev/null @@ -1,15 +0,0 @@ -<!-- -*- sgml -*- --> -<!-- $FreeBSD$ --> - -<!-- Text constants which probably don't need to be changed.--> - -<!-- Files to be included --> - -<!ENTITY artheader SYSTEM "../common/artheader.sgml"> -<!ENTITY sect.intro SYSTEM "../common/intro.sgml"> -<!ENTITY sect.proc.alpha SYSTEM "../alpha/proc-alpha.sgml"> -<!ENTITY sect.proc.i386 SYSTEM "../i386/proc-i386.sgml"> -<!ENTITY sect.proc.ia64 SYSTEM "../ia64/proc-ia64.sgml"> -<!ENTITY sect.dev SYSTEM "../common/dev.sgml"> -<!ENTITY sect.config SYSTEM "../common/config.sgml"> - diff --git a/release/doc/en_US.ISO_8859-1/hardware/common/intro.sgml b/release/doc/en_US.ISO_8859-1/hardware/common/intro.sgml deleted file mode 100644 index 5d86673..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/common/intro.sgml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- $FreeBSD$ --> - -<sect1> - <title>Introduction</title> - - <para>This document contains the hardware compatability notes for - &os; &release.current; on the &arch; hardware platform. It lists - devices known to work on this platform, as well as some notes on - boot-time kernel customization that may be useful when attempting to - configure support for new devices.</para> - - <note> - <para>This document includes information specific to the &arch; - hardware platform. Versions of the hardware compatability notes - for other architectures will differ in some details.</para> - </note> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/hardware/i386/Makefile b/release/doc/en_US.ISO_8859-1/hardware/i386/Makefile deleted file mode 100644 index 7e02d19..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/i386/Makefile +++ /dev/null @@ -1,19 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= proc-i386.sgml -SRCS+= ../common/hw.ent -SRCS+= ../common/artheader.sgml -SRCS+= ../common/dev.sgml -SRCS+= ../common/config.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/hardware/i386/article.sgml b/release/doc/en_US.ISO_8859-1/hardware/i386/article.sgml deleted file mode 100644 index 8255e0de..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/i386/article.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "i386"> - -]> - -<article> - &artheader; - §.intro; - §.proc.i386; - §.dev; - §.config; -</article> diff --git a/release/doc/en_US.ISO_8859-1/hardware/i386/proc-i386.sgml b/release/doc/en_US.ISO_8859-1/hardware/i386/proc-i386.sgml deleted file mode 100644 index c2c56ff..0000000 --- a/release/doc/en_US.ISO_8859-1/hardware/i386/proc-i386.sgml +++ /dev/null @@ -1,11 +0,0 @@ -<!-- - $FreeBSD$ ---> -<sect1> - <title>Supported Processors and Motherboards</title> - - <para>&os; for the i386 currently runs on a wide variety of ISA, - VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to - Pentium 4 class machines (though the 386sx is not - recommended).</para> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/Makefile b/release/doc/en_US.ISO_8859-1/installation/Makefile deleted file mode 100644 index dca8380..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/Makefile +++ /dev/null @@ -1,9 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -SUBDIR = alpha -SUBDIR+= i386 - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/installation/alpha/Makefile b/release/doc/en_US.ISO_8859-1/installation/alpha/Makefile deleted file mode 100644 index 19de1c1..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/alpha/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= ../common/artheader.sgml -SRCS+= ../common/install.sgml -SRCS+= ../common/floppies.sgml -SRCS+= ../common/layout.sgml -SRCS+= ../common/trouble.sgml -SRCS+= ../common/upgrade.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml b/release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml deleted file mode 100644 index c334c28..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml +++ /dev/null @@ -1,27 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "alpha"> - -]> - -<article> -&artheader; -§.install; -§.layout; -§.floppies; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml b/release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml deleted file mode 100644 index 63c7f1f..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml +++ /dev/null @@ -1,15 +0,0 @@ -<!-- $FreeBSD$ --> - -<articleinfo> - <title>&os; &release.current; &arch; Installation Instructions</title> - - <corpauthor> - The &os; Project - </corpauthor> - - <copyright> - <year>2000</year> - <year>2001</year> - <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> - </copyright> -</articleinfo> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml b/release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml deleted file mode 100644 index 99b8da3..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml +++ /dev/null @@ -1,83 +0,0 @@ -<!-- $FreeBSD$ --> - -<sect1 id="floppies"> - <title>Floppy Disk Image Instructions</title> - - <para>For a normal CDROM or network installation, all you need to - copy onto actual floppies from the <filename>floppies/</filename> directory are the - <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> - images (for 1.44MB floppies).</para> - - <para>Getting these images over the network is easy. simply fetch - the - <replaceable>release</replaceable><filename>/floppies/kern.flp</filename> - and - <replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename> - files from <ulink - url="ftp://ftp.freebsd.org/pub/FreeBSD">ftp://ftp.freebsd.org/pub/FreeBSD</ulink> - or one of the many mirrors listed at <ulink - url="http://www.freebsd.org/handbook/mirrors.html">http://www.freebsd.org/handbook/mirrors.html</ulink>. - </para> - - <para>Get two blank, freshly formatted floppies and image copy - <filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other. These images are - <emphasis>not</emphasis> DOS files! You cannot simply copy them to a DOS or UFS floppy - as regular files, you need to <quote>image</quote> copy them to the floppy with - <filename>fdimage.exe</filename> under DOS (see the - <filename>tools</filename> directory on your CDROM or &os; FTP - mirror) or the &man.dd.1; command in UNIX.</para> - - <para>For example, to create the kernel floppy image from DOS, you'd - do something like this:</para> - - <screen><userinput>C> fdimage kern.flp a:</userinput></screen> - - <para>Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory - somewhere. You would do the same for <filename>mfsroot.flp</filename>, of course.</para> - - <para>If you're creating the boot floppy from a UNIX machine, you - may find that:</para> - - <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen> - - <para>or</para> - - <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen> - - <para>work well, depending on your hardware and operating system - environment (different versions of UNIX have totally different names - for the floppy drive).</para> - - <para arch="alpha">If you're on an alpha machine that can network-boot its - floppy images or you have a 2.88MB or LS-120 floppy capable of - taking a 2.88MB image on an x86 machine, you may wish to use - the older (but now twice as large) <filename>boot.flp</filename> image which we also - provide. That contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on - a single floppy, essentially. This file should also be used as the - boot file for those mastering <quote>El Torito</quote> bootable CD images. See - the &man.mkisofs.8; command for more information.</para> - - <para>Going to two installation boot floppies is a step we - definitely would have rather avoided but we simply no longer could - due to general code bloat and &os;'s many new device drivers in - <filename>GENERIC</filename>.</para> - - <para>One positive side-effect of this new organizational scheme, - however, is that it also allows one to easily make one's own - <filename>kern.flp</filename> or <filename>mfsroot.flp</filename> floppies - should a need to customize some aspect of the installation process - or use a custom kernel for an otherwise unsupported piece of - hardware arise. As long as the kernel is compiled with - <literal>options MFS</literal> and <literal>options - MFS_ROOT</literal>, it will properly look for and boot an - <filename>mfsroot.flp</filename> image in memory when run (see how - <filename>/boot/loader.rc</filename> in - <filename>kern.flp</filename> does its thing). The - <filename>mfsroot.flp</filename> image is also just a gzip'd - filesystem image which is used as root, something which can be made - rather easily using &man.vnconfig.8;. If none of that makes any - sense to you then don't worry about it - just use the - <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> - images as described above.</para> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/install.ent b/release/doc/en_US.ISO_8859-1/installation/common/install.ent deleted file mode 100644 index 773b7d2..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/install.ent +++ /dev/null @@ -1,15 +0,0 @@ -<!-- -*- sgml -*- --> - -<!-- $FreeBSD$ --> - -<!-- Text constants which probably don't need to be changed.--> - -<!-- Files to be included --> - -<!ENTITY artheader SYSTEM "artheader.sgml"> -<!ENTITY sect.install SYSTEM "install.sgml"> -<!ENTITY sect.layout SYSTEM "layout.sgml"> -<!ENTITY sect.floppies SYSTEM "floppies.sgml"> -<!ENTITY sect.upgrade SYSTEM "upgrade.sgml"> -<!ENTITY sect.trouble SYSTEM "trouble.sgml"> - diff --git a/release/doc/en_US.ISO_8859-1/installation/common/install.sgml b/release/doc/en_US.ISO_8859-1/installation/common/install.sgml deleted file mode 100644 index 776d916..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/install.sgml +++ /dev/null @@ -1,801 +0,0 @@ -<!-- - -$FreeBSD$ - -install.sgml - -This file has architecture-dependent installation instructions, culled -from {alpha,i386}/INSTALL.TXT. - ---> - -<sect1> - <title>Installing &os;</title> - - <sect2 id="quickstart"> - <title>Quick Start</title> - - <para>This manual documents the process of making a new - installation of &os; on your machine. If you are upgrading - from a previous release of &os;, please see <xref - linkend="upgrading"> - for important information on upgrading. If you are - not familiar with configuring hardware for &os;, you should - also read the <filename>HARDWARE.TXT</filename> file - it contains important - information which may save you a lot of grief.</para> - - <para>If you're new to &os; then you should also read - <emphasis>everything</emphasis> listed in the Documentation menu - of the installer. It may seem like a lot to read, but the time - you spend now reading the documents will be made up many times - over because you were adequately prepared. Also, you will know the - types of information available should you get stuck later. Once - the system is installed, you can also revisit this menu and use a - Web browser to read the installed FAQ (Frequently Asked Questions) - and Handbook HTML documentation sets for &os;. Note that on-line - versions of the <ulink - url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink - url="http://www.freebsd.org/handbook/">Handbook</ulink> are also - available from the <ulink - url="http://www.freebsd.org/">FreeBSD Project Web - site</ulink>, if you have an Internet connection. See - <filename>README.TXT</filename> for more information on the - resources available to you.</para> - - <para>The best laid plans sometimes go awry, so if you run into - trouble take a look at <xref linkend="trouble">, which contains - valuable troubleshooting information. You should also read - <filename>ERRATA.TXT</filename> before installing and follow the - pointers there carefully since this will stop you from falling - over any problems which have reported in the interim for your - particular release.</para> - - <important> - <para>While &os; does its best to safeguard against - accidental loss of data, it's still more than possible to - <emphasis>wipe out your entire disk</emphasis> - with this installation if you make a - mistake! Please do not proceed to the final &os; - installation menu unless you've adequately backed up any - important data first! We really mean it!</para> - </important> - - <para arch="i386">&os; for the &arch; requires a 386 or better - processor to run (sorry, there is no support for 286 processors) - and at least 5 megs of RAM to install and 4 megs of RAM to - run. You will need at least 100MB of free hard drive space for the - most minimal installation. See below for ways of shrinking - existing DOS partitions in order to install &os;.</para> - - <para arch="alpha">&os; for the &arch; supports the alpha platforms - described in <filename>HARDWARE.TXT</filename>.</para> - - <para arch="alpha">You will need a dedicated disk for - FreeBSD/alpha. It is not possible to share a disk with another - operating system at this time. This disk will need to be attached - to a SCSI controller which is supported by the SRM firmware or an - IDE disk assuming the SRM in your machine supports booting from - IDE disks.</para> - - <para arch="alpha">Your root filesystem MUST be the first - partition (partition <literal>a</literal>) on the disk to be - bootable.</para> - - <para arch="alpha">You will need the SRM console firmware for your - platform. In some cases, it is possible to switch between - AlphaBIOS (or ARC) firmware and SRM. In others it will be - necessary to download new firmware from the vendor's Web - site.</para> - - <sect3> - <title>Installing &os; from CDROM or the Internet</title> - - <para arch="i386">The easiest type of installation is from - CDROM. If you have a supported CDROM drive and a &os; - installation CDROM, there are 2 ways of starting the - installation from it: - <itemizedlist> - <listitem> - <para>If your system supports bootable CDROM media - (usually an option which can be selectively enabled in the - controller's setup menu or in the PC BIOS for some - systems) and you have it enabled, &os; supports the - <quote>El Torrito</quote> bootable CD standard. Simply - put the installation CD in your CDROM drive and boot the - system to begin installation.</para> - </listitem> - <listitem> - <para>Build a set of &os; boot floppies from the - <filename>floppies/</filename> directory in every &os; - distribution. Either simply use the - <filename>makeflp.bat</filename> script from DOS or read - <xref linkend="floppies"> for more information on creating - the bootable floppies under different operating systems. - Then you simply boot from the first floppy and you should - soon be in the &os; installation.</para> - </listitem> - </itemizedlist> - </para> - - <para arch="alpha">The easiest type of installation is from - CDROM. If you have a supported CDROM drive and a FreeBSD - installation CDROM, you can boot FreeBSD directly from the - CDROM. Insert the CDROM into the drive and type the following - command to start the installation (substituting the name of the - appropriate CDROM drive if necessary): - - <screen>>>><userinput>boot dka0</userinput></screen> - </para> - - <para arch="alpha">Alternatively you can boot the installation - from floppy disk. You should start the installation by building - a set of FreeBSD boot floppy from the files - <filename>floppies/kern.flp</filename> and - <filename>floppies/mfsroot.flp</filename> using the instructions - found in <xref linkend="floppies">. From the SRM console prompt - (<literal>>>></literal>), just insert the - <filename>kern.flp</filename> floppy and type the following - command to start the installation: - - <screen>>>><userinput>boot dva0</userinput></screen> - </para> - - <para arch="alpha">Insert the <filename>mfsroot.flp</filename> - floppy when prompted and you will end up at the first screen of - the install program.</para> - - <para>If you don't have a CDROM and would like to simply install - over the net using PPP, SLIP or a dedicated connection, see - <xref linkend="floppies"> for instructions on - making boot floppies. Then please go to - <xref linkend="ftpnfs"> for additional tips on installing - via FTP or NFS.</para> - - </sect3> - </sect2> - <sect2> - <title>Detail on various installation types</title> - - <para>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 &os; - installation before, you are also encouraged to read some of the - documentation in the the Documentation submenu as well as the - general <quote>Usage</quote> instructions on the first menu.</para> - - <note> - <para>If you get stuck at a screen, hit the <keycap>F1</keycap> key for online - documentation relevant to that specific section.</para> - </note> - - <para>If you've never installed &os; before, or even if you - have, the <quote>Standard</quote> 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 &os; installation process and know <emphasis>exactly</emphasis> what you - want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If - you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para> - - <para>The &os; 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.</para> - - <para arch="alpha">Once the install procedure has finished, you will be able - to start &os;/&arch; by typing something like this to the SRM - prompt: - <screen>>>><userinput>boot dkc0</userinput></screen> - </para> - - <para arch="alpha">This instructs the firmware to boot the specified disk. To - find the SRM names of disks in your machine, use the <literal>show - device</literal> command: - - <screen>>>><userinput>show device</userinput> -dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 -dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658 -dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015 -dva0.0.0.0.1 DVA0 -ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01 -pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27 -pqa0.0.0.4.0 PQA0 PCI EIDE -pqb0.0.1.4.0 PQB0 PCI EIDE</screen> - </para> - - <para arch="alpha">This example is from a Digital Personal Workstation 433au - and shows three disks attached to the machine. The first is a - CDROM called <devicename>dka0</devicename> and the other two are - disks and are called <devicename>dkc0</devicename> and - <devicename>dkc100</devicename> repectively.</para> - - <para arch="alpha">You can specify which kernel file to load and what boot - options to use with the <option>-file</option> and - <option>-flags</option> options, for example: - <screen><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen> - </para> - - <para arch="alpha">To make &os;/&arch; boot automatically, use these commands: - - <screen><prompt>>>></prompt> <userinput>set boot_osflags a</userinput> -<prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput> -<prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen> - </para> - - <sect3> - <title>Installing from a Network CDROM</title> - - <para>If you simply wish to install from a local CDROM drive - then see <xref linkend="quickstart">. If you don't have a CDROM - drive on your system and wish to use a &os; distribution CD - in the CDROM drive of another system to which you have network - connectivity, there are also several ways of going about it:</para> - - <itemizedlist> - <listitem> - <para>If you would be able to FTP install &os; directly - from the CDROM drive in some &os; machine, it's quite - easy: You simply add the following line to the password file - (using the &man.vipw.8; command):</para> - - <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen> - - <para>On the machine on which you are running the install, - go to the Options menu and set Release Name to - <literal>any</literal>. You may then choose a Media type of - <literal>FTP</literal> and type in - <filename>ftp://<replaceable>machine</replaceable></filename> - after picking <quote>URL</quote> in the ftp sites - menu.</para> - - <warning> - <para>This may allow anyone on the local network (or Internet) to - make <quote>anonymous FTP</quote> connections to this - machine, which may not be desirable.</para> - </warning> - </listitem> - - <listitem> - <para>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 - <filename>/etc/exports</filename> file (on the machine with - the CDROM drive). The example below allows the machine - <hostid role="hostname">ziggy.foo.com</hostid> to mount the - CDROM directly via NFS during installation:</para> - - <screen>/cdrom -ro ziggy.foo.com</screen> - - <para>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 &man.rc.conf.5; and configure things - appropriately. Assuming that this part goes smoothly, you - should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for - an NFS installation when the target machine is installed, - e.g. <filename>wiggy:/cdrom</filename>.</para> - </listitem> - </itemizedlist> - </sect3> - - <sect3> - <title>Installing from Floppies</title> - - <para>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.</para> - - <para>First, make your boot floppies as described in - <xref linkend="floppies">.</para> - - <para>Second, peruse <xref linkend="layout"> and pay special attention - to the <quote>Distribution Format</quote> section since it describes which - files you're going to need to put onto floppy and which you can - safely skip.</para> - - <para>Next you will need, at minimum, as many 1.44MB floppies as - it takes to hold all files in the <filename>bin</filename> - (binary distribution) directory. If you're preparing these - floppies under DOS, then these floppies - <emphasis>must</emphasis> be formatted using the MS-DOS - <filename>FORMAT</filename> command. If you're using Windows, - use the Windows File Manager format command.</para> - - <important> - <para>Don't trust <quote>factory preformatted</quote> - floppies! Format them again yourself, just to make sure. - Many problems reported by users in the past have resulted - from the use of improperly formatted media.</para> - </important> - - <para>If you're creating the floppies from another &os; - 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 - &man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a - floppy, as the following sequence of commands illustrates: - <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput> -&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput> -&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen> - </para> - - <para>After you've formatted the floppies for DOS or UFS, you'll - need to copy the files onto them. The distribution files are - split into chunks conveniently sized so that 5 of them will fit - on a conventional 1.44MB floppy. Go through all your floppies, - packing as many files as will fit on each one, until you've got - all the distributions you want packed up in this fashion. Each - distribution should go into its own subdirectory on the floppy, - e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para> - - <important> - <para>The <filename>bin.inf</filename> file also needs to go on the first floppy of - the <filename>bin</filename> 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 - <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first - floppy of each distribution set! This is also covered in - <filename>README.TXT</filename>.</para> - </important> - - <para>Once you come to the Media screen of the install, select - <quote>Floppy</quote> and you'll be prompted for the rest.</para> - </sect3> - - <sect3 arch="i386"> - <title>Installing from a DOS partition</title> - - <para>To prepare for installation from an MS-DOS partition you - should simply copy the files from the distribution into a - directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from - DOS using files copied from the CDROM, you might do something - like this:</para> - - <screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput> -<prompt>C:\></prompt <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN</userinput></screen> - - <para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para> - - <para>For as many distributions as you wish to install from DOS (and - you have free space for), install each one in a directory under - <filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para> - - <para>Once you've copied the directories, you can simply launch - the installation from floppies as normal and select <quote>DOS</quote> as - your media type when the time comes.</para> - </sect3> - - <sect3> - <title>Installing from QIC/SCSI Tape</title> - - <para>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 &man.tar.1; to get them onto the tape with a command something like - this:</para> - - <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput> -&prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen> - - <para>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 <emphasis>full</emphasis> - 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.</para> - - <note> - <para>When going to do the installation, the tape must be in - the drive <emphasis>before</emphasis> booting from the boot floppies. The - installation <quote>probe</quote> may otherwise fail to find it.</para> - </note> - - <para>Now create a boot floppy as described in <xref linkend="quickstart"> and - proceed with the installation.</para> - </sect3> - - <sect3 id="ftpnfs"> - <title>Installing over a Network using FTP or NFS</title> - - <para>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.</para> - - <sect4> - <title>Serial Port</title> - - <para>SLIP support is rather primitive, and is limited - primarily to hard-wired links, such as a serial cable running - between two computers. The link must be hard-wired because - the SLIP installation doesn't currently offer a dialing - capability. If you need to dial out with a modem or otherwise - dialog with the link before connecting to it, then I recommend - that the PPP utility be used instead.</para> - - <para>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.</para> - - <para>You will also need to know how to use the various <quote>AT - commands</quote> for dialing out with your particular brand of modem - as the PPP dialer provides only a very simple terminal - emulator.</para> - </sect4> - - <sect4> - <title>Parallel Port</title> - - <para>If a hard-wired connection to another &os; or Linux - machine is available, you might also consider installing over - a <quote>laplink</quote> 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 - <quote>real</quote> 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. <hostid - role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>, - etc).</para> - - <important> - <para>If you use a Linux machine rather than a &os; - machine as your PLIP peer, you will also have to specify - <option>link0</option> in the TCP/IP setup screen's <quote>extra options for - ifconfig</quote> field in order to be compatible with Linux's - slightly different PLIP protocol.</para> - </important> - - </sect4> - - <sect4> - <title>Ethernet</title> - - <para>&os; supports most common PC Ethernet cards, a table - of supported cards (and their required settings) being - provided as part of the &os; Hardware Guide (see the - Documentation menu on the boot floppy or the top level - directory of the CDROM). If you are using one of the - supported PCMCIA Ethernet cards, also be sure that it's - plugged in <emphasis>before</emphasis> the laptop is powered on! &os; does - not, unfortunately, currently support <quote>hot insertion</quote> of - PCMCIA cards during installation.</para> - - <para>You will also need to know your IP address on the - network, the <option>netmask</option> 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.</para> - - <para>If you do not know the answers to these questions then - you should really probably talk to your system administrator - <emphasis>first</emphasis> before trying this type of - installation! Using a randomly chosen IP address or netmask - on a live network will almost certainly get you shot at - dawn.</para> - - <para>Once you have a network connection of some sort working, the - installation can continue over NFS or FTP.</para> - </sect4> - - <sect4> - <title>NFS installation tips</title> - - <para>NFS installation is fairly straight-forward: Simply copy - the &os; distribution files you want onto a server - somewhere and then point the NFS media selection at it.</para> - - <para>If this server supports only <quote>privileged port</quote> access (this is - generally the default for Sun and Linux workstations), you - will need to set this option in the Options menu before - installation can proceed.</para> - - <para>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.</para> - - <para>In order for NFS installation to work, the server must - also support <quote>subdir mounts</quote>, e.g. if your &os; - distribution directory lives on - <filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then - <hostid role="hostname">wiggy</hostid> will have to allow - the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just - <filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para> - - <para>In FreeBSD's <filename>/etc/exports</filename> file this is controlled by the - <option>-alldirs</option> option. Other NFS servers may have different - conventions. If you are getting <literal>Permission Denied</literal> messages - from the server then it's likely that you don't have this - properly enabled!</para> - </sect4> - - <sect4> - <title>FTP Installation tips</title> - - <para>FTP installation may be done from any mirror site containing a - reasonably up-to-date version of &os;. A full menu of - reasonable choices for almost any location in the world is - provided in the FTP site menu during installation.</para> - - <para>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 <quote>URL</quote> 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:</para> - - <screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen> - - <para>There are three FTP installation modes you can use: - <itemizedlist> - <listitem> - <para>FTP: This method uses the standard - <quote>Active</quote> 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!</para> - </listitem> - <listitem> - <para>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.</para> - </listitem> - <listitem> - <para>FTP via an HTTP proxy: This option instructs &os; - 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.</para> - - <para>In the rare case that you have an FTP proxy that - does not go through HTTP, you can specify the URL as - something like:</para> - - <screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen> - - <para>In the URL above, <replaceable>port</replaceable> - is the port number of the proxy FTP server.</para> - </listitem> - </itemizedlist> - - </sect4> - </sect3> - <sect3> - <title>Tips for Serial Console Users</title> - - <para>If you'd like to install &os; on a machine using just a - serial port (e.g. you don't have or wish to use a VGA card), - please follow these steps:</para> - - <procedure> - <step> - <para>Connect some sort of ANSI (vt100) compatible terminal - or terminal emulation program to the <devicename>COM1</devicename> port of the PC you - are installing &os; onto.</para> - </step> - <step> - <para>Unplug the keyboard (yes, that's correct!) and then - try to boot from floppy or the installation CDROM, depending - on the type of installation media you have, with the - keyboard unplugged.</para> - </step> - <step> - <para>If you don't get any output on your serial console, - plug the keyboard in again and wait for some beeps. If you - are booting from the CDROM, proceed to <xref - linkend="hitspace"> as soon as you - hear the beep.</para> - </step> - <step> - <para>For a floppy boot, the first beep means to remove the - <filename>kern.flp</filename> floppy and insert the - <filename>mfsroot.flp</filename> floppy, after - which you should press <keycap>Enter</keycap> and wait for another beep.</para> - </step> - <step id="hitspace"> - <para>Hit the space bar, then enter</para> - - <screen><userinput>boot -h</userinput></screen> - - <para>and you should now definitely be seeing everything on - the serial port. If that still doesn't work, check your - serial cabling as well as the settings on your terminal - emulation program or actual terminal device. It should be - set for 9600 baud, 8 bits, no parity.</para> - </step> - </procedure> - </sect3> - </sect2> - - <sect2> - <title>Question and Answer Section for &arch; Architecture Users</title> - - <qandaset arch="i386"> - <qandaentry> - <question> - <para>Help! I have no space! Do I need to delete - everything first?</para> - </question> - <answer> - <para>If your machine is already running DOS and has little - or no free space available for &os;'s installation, all is - not lost! You may find the <application>FIPS</application> - utility, provided in the <filename>tools/</filename> - subdirectory on the &os; CDROM or on the various &os; ftp - sites, to be quite useful.</para> - - <para><application>FIPS</application> allows you to split an - existing DOS partition into two pieces, preserving the - original partition and allowing you to install onto the - second free piece. You first <quote>defrag</quote> your DOS - partition, using the DOS 6.xx <filename>DEFRAG</filename> - utility or the <application>Norton Disk Tools</application>, - then run FIPS. It will - prompt you for the rest of the information it needs. - Afterwards, you can reboot and install &os; on the new - partition. Also note that FIPS will create the second - partition as a <quote>clone</quote> of the first, so you'll - actually see that you now have two DOS Primary partitions - where you formerly had one. Don't be alarmed! You can - simply delete the extra DOS Primary partition (making sure - it's the right one by examining its size! :)</para> - - <para><application>FIPS</application> does NOT currently - work with FAT32 or VFAT style partitions as used by newer - versions of Windows 95. To split up such a partition, you - will need a commercial product such as - <application>Partition Magic</application>. Sorry, but this - is just the breaks if you've got a Windows partition hogging - your whole disk and you don't want to reinstall from - scratch.</para> - - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I use compressed DOS filesystems from - &os;?</para> - </question> - - <answer> - <para>No. If you are using a utility such as - <application>Stacker</application>(tm) or - <application>DoubleSpace</application>(tm), &os; will only - be able to use whatever portion of the filesystem you leave - uncompressed. The rest of the filesystem will show up as - one large file (the stacked/dblspaced file!). <emphasis>Do - not remove that file</emphasis> as you will probably regret - it greatly!</para> - - <para>It is probably better to create another uncompressed DOS - extended partition and use this for communications between - DOS and &os; if such is your desire.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I mount my DOS extended partitions?</para> - </question> - - <answer> - <para>Yes. DOS extended partitions are mapped in at the end - of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might - be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This - example assumes, of course, that your extended partition is - on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for - <literal>da</literal> appropriately. You otherwise mount extended - partitions exactly like you would mount any other DOS drive, - e.g.:</para> - - <screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I run DOS binaries under &os;?</para> - </question> - - <answer> - <para>Ongoing work with BSDI's &man.doscmd.1; utility will - suffice in many cases, though - it still has some rough edges. If you're interested in - working on this, please send mail to the &a.emulation - and indicate that you're interested in joining this ongoing - effort!</para> - - <para>There is also a neat utility called <filename>pcemu</filename> in the - &os; Ports Collection which emulates an 8088 and enough BIOS - services to run DOS text mode applications. It requires the - X Window System (XFree86) to operate.</para> - </answer> - </qandaentry> - </qandaset> - - <qandaset arch="alpha"> - <qandaentry> - <question> - <para>Can I boot from the ARC or Alpha BIOS Console?</para> - </question> - - <answer> - <para>No. &os;, like Compaq Tru64 and VMS, will only boot - from the SRM console.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Help! I have no space! Do I need to delete - everything first?</para> - </question> - - <answer> - <para>Unfortunately, yes.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I mount my Compaq Tru64 or VMS extended partitions?</para> - </question> - - <answer> - <para>No, not at this time.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for Compaq Tru64 (OSF/1) binaries?</para> - </question> - - <answer> - <para>&os; can run Tru64 applications very well using the - <filename>emulators/osf1_base</filename> port/package.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for Linux binaries?</para> - </question> - - <answer> - <para>At the moment, &os; cannot run AlphaLinux. Support is - currently being worked on.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>What about support for NT Alpha binaries?</para> - </question> - - <answer> - <para>&os; is not able to run NT applications natively, - although it has the ability to mount NT partitions.</para> - </answer> - </qandaentry> - </qandaset> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/layout.sgml b/release/doc/en_US.ISO_8859-1/installation/common/layout.sgml deleted file mode 100644 index 3e2b5ca..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/layout.sgml +++ /dev/null @@ -1,133 +0,0 @@ -<!-- - $FreeBSD$ - - This section contains the contents of the old LAYOUT.TXT file. ---> -<sect1 id="layout"> - <title>Distribution Format</title> - - <para>A typical &os; distribution directory looks something like this:</para> - -<screen> -ABOUT.TXT bin compat3x games proflibs -HARDWARE.TXT compat1x info src tools -INSTALL.TXT compat20 dict manpages packages -README.TXT compat21 crypto doc -RELNOTES.TXT compat22 floppies ports -XF86336</screen> - - <para>If you want to do a CDROM, FTP or NFS installation from this - distribution directory, all you need to do is make the 1.44MB boot - floppies from the floppies directory (see - <xref linkend="floppies"> for instructions on how to - do this), boot them and follow the instructions. The rest of the - data needed during the installation will be obtained automatically - based on your selections. If you've never installed &os; before, - you also want to read the entirety of this document (the - installation instructions) file.</para> - - <para>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 each item in more detail: - <orderedlist> - <listitem> - <para>The <filename>*.TXT</filename> files obviously contain - documentation (this file is <filename>INSTALL.TXT</filename>) and should be read - before starting an installation.</para> - </listitem> - <listitem> - <para>The <filename>XF86336</filename> directory contains the - XFree86 project's 3.3.6 release and consists of a series of - gzip'd tar files which contain each component of the XFree86 - distribution.</para> - </listitem> - <listitem> - <para>The <filename>bin</filename>, <filename>dict</filename>, <filename>crypto</filename>, <filename>doc</filename>, <filename>games</filename>, <filename>info</filename>, <filename>manpages</filename>, - <filename>proflibs</filename>, and <filename>src</filename> directories contain the primary distribution - components of &os; itself and are split into smaller files - for easy packing onto floppies (should that be - necessary).</para> - </listitem> - <listitem> - <para>The <filename>compat1x</filename>, <filename>compat20</filename>, <filename>compat21</filename>, <filename>compat22</filename>, and <filename>compat3x</filename> - 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 - <filename>install.sh</filename> scripts.</para> - </listitem> - <listitem> - <para>The <filename>floppies/</filename> subdirectory contains the floppy - installation images; further information on using them can be - found in <xref linkend="floppies">.</para> - </listitem> - <listitem> - <para>The <filename>packages</filename> and <filename>ports</filename> directories contain the &os; - packages and ports collections. Packages may be installed from - the packages directory by running the command:</para> - - <screen>&prompt.root;<userinput>/stand/sysinstall configPackages</userinput></screen> - - <para>Packages can also be installed by feeding individual - filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para> - - <para>The ports collection may be installed like any other - distribution and requires about 100MB unpacked. More - information on the ports collection may be obtained from - <ulink url="http://www.freebsd.org/ports/">http://www.freebsd.org/ports/</ulink> or locally from - <filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename> - distribution.</para> - </listitem> - <listitem> - <para>Last of all, the <filename>tools</filename> 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.</para> - </listitem> - </orderedlist> - </para> - - <para>A typical distribution (we'll use the <filename>info</filename> distribution as an - example) looks like this internally:</para> - -<screen>CHECKSUM.MD5 info.ab info.ad info.inf install.sh -info.aa info.ac info.ae info.mtree</screen> - - <para>The <filename>CHECKSUM.MD5</filename> 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 <filename>info.a*</filename> files - are split, gzip'd tar files, the contents of which can be viewed by - doing:</para> - - <screen>&prompt.root; <userinput>cat info.a* | tar tvzf -</userinput></screen> - - <para>During installation, they are automatically concatenated and - extracted by the installation procedure.</para> - - <para>The <filename>info.inf</filename> 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 <filename>.inf</filename> file <emphasis>must</emphasis> occupy the first - floppy of each distribution set!</para> - - <para>The <filename>info.mtree</filename> file is another non-essential file which is - provided for user reference. It contains the MD5 signatures of the - <emphasis>unpacked</emphasis> distribution files and can be later - used with the &man.mtree.8; program to verify the installation - permissions and checksums against any possible modifications to the - file. When used with the <filename>bin</filename> distribution, - this can be an excellent way of detecting trojan horse attacks on - your system.</para> - - <para>Finally, the <filename>install.sh</filename> 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:</para> - - <screen>&prompt.root; <userinput>cd /cdrom/info</userinput> -&prompt.root; <userinput>sh install.sh</userinput></screen> - - <para>And that's all there is to it! Each distribution contains its - own <filename>install.sh</filename> file for this.</para> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/trouble.sgml b/release/doc/en_US.ISO_8859-1/installation/common/trouble.sgml deleted file mode 100644 index 8c3cf58..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/trouble.sgml +++ /dev/null @@ -1,529 +0,0 @@ -<!-- - $FreeBSD$ - - This file contains the comments of the old TROUBLE.TXT file. ---> -<sect1 id="trouble"> - <title>Troubleshooting</title> - - <sect2 id="repairing"> - <title>Repairing an Existing &os; Installation</title> - - <para>&os; releases 2.2.1 and later feature a - <quote>Fixit</quote> option in the top menu of the boot floppy. - To use it, you will also need either a - <filename>fixit.flp</filename> image floppy, generated in the same - fashion as the boot floppy, or the 2nd CDROM from Walnut Creek - CDROM's &os; distribution.</para> - - <para>To invoke fixit, simply boot the - <filename>kern.flp</filename> floppy, choose the - <quote>Fixit</quote> item and insert the fixit floppy or CDROM - when asked. You will then be placed into a shell with a wide - variety of commands available (in the <filename>/stand</filename> - and <filename>/mnt2/stand</filename> directories) for checking, - repairing and examining file systems and their contents. Some - UNIX administration experience <emphasis>is</emphasis> required to - use the fixit option!</para> - </sect2> - - <sect2> - <title>Common Installation Problems, Q&A</title> - - <qandaset> - <qandaentry> - <question> - <para>I go to boot from the hard disk for the first time - after installing &os;, the kernel loads and probes my - hardware, but stops with messages like:</para> - - <screen>changing root device to wd1s1a panic: cannot mount root</screen> - <para>What is wrong? What can I do?</para> - - <para>What is this - <literal>bios_drive:interface(unit,partition)kernel_name</literal> - thing that is displayed with the boot help?</para> - </question> - <answer> - <para>There is a longstanding problem in the case where the - boot disk is not the first disk in the system. The BIOS - uses a different numbering scheme to &os;, and working - out which numbers correspond to which is difficult to get - right.</para> - - <para>In the case where the boot disk is not the first disk - in the system, &os; can need some help finding it. There - are two common situations here, and in both of these cases, - you need to tell &os; where the root filesystem is. You - do this by specifying the BIOS disk number, the disk type - and the &os; disk number for that type.</para> - - <para>The first situation is where you have two IDE disks, - each configured as the master on their respective IDE - busses, and wish to boot &os; from the second disk. The - BIOS sees these as disk 0 and disk 1, while &os; sees - them as <devicename>wd0</devicename> and - <devicename>wd2</devicename>.</para> - - <para>&os; is on BIOS disk 1, of type - <literal>wd</literal> and the &os; disk number is 2, so - you would say:</para> - - <screen><userinput>1:wd(2,a)kernel</userinput></screen> - - <para>Note that if you have a slave on the primary bus, the - above is not necessary (and is effectively wrong).</para> - - <para>The second situation involves booting from a SCSI disk - when you have one or more IDE disks in the system. In this - case, the &os; disk number is lower than the BIOS disk - number. If you have two IDE disks as well as the SCSI disk, - the SCSI disk is BIOS disk 2, type <literal>da</literal> and - &os; disk number 0, so you would say:</para> - - <screen><userinput>2:da(0,a)kernel</userinput></screen> - - <para>To tell &os; that you want to boot from BIOS disk - 2, which is the first SCSI disk in the system. If you only - had one IDE disk, you would use '1:' instead.</para> - - <para>Once you have determined the correct values to use, - you can put the command exactly as you would have typed it - in the <filename>/boot.config</filename> file using a - standard text editor. Unless instructed otherwise, &os; - will use the contents of this file as the default response - to the <literal>boot:</literal> prompt.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I go to boot from the hard disk for the first time - after installing &os;, but the Boot Manager prompt just - prints <literal>F?</literal> at the boot menu each time but - the boot won't go any further.</para> - </question> - <answer> - <para>The hard disk geometry was set incorrectly in the - Partition editor when you installed &os;. Go back into - the partition editor and specify the actual geometry of your - hard disk. You must reinstall &os; again from the - beginning with the correct geometry.</para> - - <para>If you are failing entirely in figuring out the - correct geometry for your machine, here's a tip: Install a - small DOS partition at the beginning of the disk and install - &os; after that. The install program will see the DOS - partition and try to infer the correct geometry from it, - which usually works.</para> - - <para>The following tip is no longer recommended, but is left here - for reference:</para> - - <blockquote> - <para>If you are setting up a truly dedicated &os; - server or workstation where you don't care for (future) - compatibility with DOS, Linux or another operating system, - you've also got the option to use the entire disk (`A' in - the partition editor), selecting the non-standard option - where &os; occupies the entire disk from the very first - to the very last sector. This will leave all geometry - considerations aside, but is somewhat limiting unless - you're never going to run anything other than &os; on a - disk.</para> - </blockquote> - </answer> - </qandaentry> - </qandaset> - </sect2> - <sect2> - <title>Known Hardware Problems, Q&A</title> - - <note> - <para>Please send hardware tips for this section to &a.jkh;.</para> - </note> - - <qandaset> - <qandaentry> - <question> - <para>The &man.mcd.4; driver keeps thinking that it has - found a device and this stops my Intel EtherExpress card - from working.</para> - </question> - <answer> - <para>Use the UserConfig utility (see - <filename>HARDWARE.TXT</filename>) and disable the probing - of the <devicename>mcd0</devicename> and - <devicename>mcd1</devicename> devices. Generally speaking, - you should only leave the devices that you will be using - enabled in your kernel.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>&os; claims to support the 3Com PCMCIA card, but my - card isn't recognized when it's plugged into my - laptop.</para> - </question> - <answer> - <para>There are a couple of possible problems. First of - all, &os; does not support multi-function cards, so if - you have a combo Ethernet/modem card (such as the 3C562), it - won't work. The default driver for the 3C589 card was - written just like all of the other drivers in &os;, and - depend on the card's own configuration data stored in NVRAM - to work. You must correctly configure &os;'s driver to - match the IRQ, port, and IOMEM stored in NVRAM.</para> - - <para>Unfortunately, the only program capable of reading - them is the 3COM supplied DOS program. This program must be - run on a absolutely clean system (no other drivers must be - running), and the program will whine about CARD-Services not - being found, but it will continue. This is necessary to - read the NVRAM values. You want to know the IRQ, port, and - IOMEM values (the latter is called the CIS tuple by 3COM). - The first two can be set in the program, the third is - un-settable, and can only be read. Once you have these - values, set them in UserConfig and your card will be - recognized.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>&os; finds my PCMCIA network card, but no packets - appear to be sent even though it claims to be working.</para> - </question> - <answer> - <para>Many PCMCIA cards have the ability to use either the - 10-Base2 (BNC) or 10-BaseT connectors for connecting to the - network. The driver is unable to <quote>auto-select</quote> - the correct connector, so you must tell it which connector - to use. In order to switch between the two connectors, the - link flags must be set. Depending on the model of the card, - <option>-link0 link1</option> or <option>-link0 - -link1</option> will choose the correct network connector. - You can set these in &man.sysinstall.8; by using the - <literal>Extra options to ifconfig:</literal> field in the - network setup screen.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>The system finds my &man.ed.4; network card, but I - keep getting device timeout errors.</para> - </question> - <answer> - <para>Your card is probably on a different IRQ from what is - specified in the kernel configuration. The ed driver does - not use the `soft' configuration by default (values entered - using EZSETUP in DOS), but it will use the software - configuration if you specify <literal>?</literal> in the IRQ field of your - kernel config file.</para> - - <para>Either move the jumper on the card to a hard - configuration setting (altering the kernel settings if - necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal> - in your kernel config file. This will tell the kernel to - use the soft configuration.</para> - - <para>Another possibility is that your card is at IRQ 9, - which is shared by IRQ 2 and frequently a cause of problems - (especially when you have a VGA card using IRQ 2! :). You - should not use IRQ 2 or 9 if at all possible.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have a Matsushita/Panasonic drive but it isn't - recognized by the system.</para> - </question> - <answer> - <para>Make certain that the I/O port that the &man.matcd.4; driver - is set to is correct for the host interface card you have. - (Some SoundBlaster DOS drivers report a hardware I/O port - address for the CD-ROM interface that is 0x10 lower than it - really is.)</para> - - <para>If you are unable to determine the settings for the - card by examining the board or documentation, you can use - UserConfig to change the 'port' address (I/O port) to -1 and - start the system. This setting causes the driver to look at - a number of I/O ports that various manufacturers use for - their Matsushita/Panasonic/Creative CD-ROM interfaces. Once - the driver locates the address, you should run UserConfig - again and specify the correct address. Leaving the 'port' - parameter set to -1 increases the amount of time that it - takes the system to boot, and this could interfere with - other devices.</para> - - <para>The double-speed Matsushita CR-562 and CR-563 are the - only drives that are supported.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I booted the install floppy on my IBM ThinkPad (tm) - laptop, and the keyboard is all messed up.</para> - </question> - <answer> - <para>Older IBM laptops use a non-standard keyboard - controller, so you must tell the keyboard driver (atkbd0) to - go into a special mode which works on the ThinkPads. Change - the atkbd0 'Flags' to 0x4 in UserConfig and it should work - fine. (Look in the Input Menu for 'Keyboard'.)</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When I try to boot the install floppy, I see the - following message and nothing seems to be happening. I - cannot enter anything from the keyboard either.</para> - - <screen>Keyboard: no</screen> - </question> - <answer> - <para>Due to lack of space, full support for old XT/AT - (84-key) keyboards is no longer available in the bootblocks. - Some notebook computers may also have this type of keyboard. - If you are still using this kind of hardware, you will see - the above message appears when you boot from the CD-ROM or - an install floppy.</para> - - <para>As soon as you see this message, hit the space bar, - and you will see the prompt:</para> - -<screen>>> FreeBSD/i386 BOOT -Default: x:xx(x,x)/boot/loader -boot:</screen> - - <para>Then enter <userinput>-Dh</userinput>, and things - should proceed normally.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have a Matsushita/Panasonic CR-522, a - Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is - not recognized even when the correct I/O port is set.</para> - </question> - <answer> - <para>These CD-ROM drives are currently not supported by - &os;. The command sets for these drives are not compatible - with the double-speed CR-562 and CR-563 drives.</para> - - <para>The single-speed CR-522 and CR-523 drives can be - identified by their use of a CD-caddy. </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I'm trying to install from a tape drive but all I get - is something like this on the screen:</para> - - <screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen> - </question> - <answer> - <para>There's a limitation in the current &man.sysinstall.8; - that the tape <emphasis>must</emphasis> be in the drive - while &man.sysinstall.8; is started or it won't be detected. - Try again with the tape in the drive the whole time.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I've installed &os; onto my system, but it hangs - when booting from the hard drive with the message:</para> - - <screen>Changing root to /dev/da0a</screen> - </question> - <answer> - <para>his problem may occur in a system with a 3com 3c509 - Ethernet adapter. The &man.ep.4; device driver appears to - be sensitive to probes for other devices that also use - address 0x300. Boot your &os; system by power cycling - the machine (turn off and on). At the - <literal>Boot:</literal> prompt specify the - <option>-c</option>. This will invoke UserConfig (see - <xref linkend="repairing"> above). - Use the <literal>disable</literal> - command to disable the device probes for all devices at - address 0x300 except the ep0 driver. On exit, your machine - should successfully boot &os;.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>My system can not find my Intel EtherExpress 16 card.</para> - </question> - <answer> - <para>You must set your Intel EtherExpress 16 card to be - memory mapped at address 0xD0000, and set the amount of - mapped memory to 32K using the Intel supplied - <filename>softset.exe</filename> program.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When installing on an EISA HP Netserver, my on-board - AIC-7xxx SCSI controller isn't detected.</para> - </question> - <answer> - <para>This is a known problem, and will hopefully be fixed - in the future. In order to get your system installed at - all, boot with the <option>-c</option> option into - UserConfig, but <emphasis>don't</emphasis> use the pretty - visual mode but the plain old CLI mode. Type: - - <screen><userinput>eisa 12</userinput> -<userinput>quit</userinput></screen> - - at the prompt. (Instead of `quit', you might also - type `visual', and continue the rest of the configuration - session in visual mode.) While it's recommended to compile - a custom kernel, dset now also understands to save - this value.</para> - - <para>Refer to the FAQ topic 3.16 for an explanation of the - problem, and for how to continue. Remember that you can - find the FAQ on your local system in /usr/share/doc/FAQ, - provided you have installed the `doc' distribution.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have a Panasonic AL-N1 or Rios Chandler Pentium - machine and I find that the system hangs before ever getting - into the installation now.</para> - </question> - <answer> - <para>Your machine doesn't like the new - <literal>i586_copyout</literal> and - <literal>i586_copyin</literal> code for some reason. To - disable this, boot the installation boot floppy and when it - comes to the very first menu (the choice to drop into kernel - UserConfig mode or not) choose the command-line interface - (<quote>expert mode</quote>) version and type the following - at it: - - <screen><userinput>flags npx0 1</userinput></screen> - - Then proceed normally to boot. This will be saved - into your kernel, so you only need to do it once.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have this CMD640 IDE controller that is said to be - broken.</para> - </question> - <answer> - <para>Yes, it is. &os; does not support this controller - except through the legacy wdc driver.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>On a Compaq Aero notebook, I get the message <quote>No - floppy devices found! Please check ...</quote> when trying to - install from floppy.</para> - </question> - <answer> - <para>With Compaq being always a little different from other - systems, they do not announce their floppy drive in the CMOS - RAM of an Aero notebook. Therefore, the floppy disk driver - assumes there is no drive configured. Go to the UserConfig - screen, and set the Flags value of the fdc0 device to 0x1. - This pretends the existence of the first floppy drive (as a - 1.44 MB drive) to the driver without asking the CMOS at - all.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When I go to boot my Intel AL440LX - (<quote>Atlanta</quote>) -based system from the hard disk the - first time, it stops with a <literal>Read Error</literal> - message.</para> - </question> - <answer> - <para>There appears to be a bug in the BIOS on at least some - of these boards, this bug results in the &os; bootloader - thinking that it is booting from a floppy disk. This is - only a problem if you are not using the BootEasy boot - manager. Slice the disk in <quote>compatible</quote>mode - and install BootEasy during the &os; installation to - avoid the bug, or upgrade the BIOS (see Intel's website for - details).</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When installing on an Dell Poweredge XE, Dell - proprietary RAID controller DSA (Dell SCSI Array) isn't - recognized.</para> - </question> - <answer> - <para>Configure the DSA to use AHA-1540 emulation using EISA - configuration utility. After that &os; detects the DSA - as an Adaptec AHA-1540 SCSI controller, with irq 11 and port - 340. Under emulation mode system will use DSA RAID disks, - but you cannot use DSA-specific features such as watching - RAID health.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>My Ethernet adapter is detected as an AMD PCnet-FAST - (or similar) but it doesn't work. (Eg. onboard Ethernet on - IBM Netfinity 5xxx or 7xxx)</para> - </question> - <answer> - <para>The &man.lnc.4; driver is currently faulty, and will - often not work correctly with the PCnet-FAST and - PCnet-FAST+. You need to install a different Ethernet - adapter.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>I have an IBM EtherJet PCI card, it is detected by the - &man.fxp.4; driver correctly, but the lights on the card don't - come on and it doesn't connect to the network.</para> - </question> - <answer> - <para>We don't understand why this happens. Neither do IBM - (we asked them). The card is a standard Intel EtherExpress - Pro/100 with an IBM label on it, and these cards normally - work just fine. You may see these symptoms only in some IBM - Netfinity servers. The only solution is to install a - different Ethernet adapter.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When I configure the network during installation on an - IBM Netfinity 3500, the system freezes.</para> - </question> - <answer> - <para>There is a problem with the onboard Ethernet in the - Netfinity 3500 which we have not been able to identify at - this time. It may be related to the SMP features of the - system being misconfigured. You will have to install - another Ethernet adapter and avoid attempting to configure - the onboard adapter at any time.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>When I install onto a drive managed by a Mylex PCI - RAID controller, the system fails to boot (eg. with a - <literal>read error</literal> message).</para> - </question> - <answer> - <para>There is a bug in the Mylex driver which results in it - ignoring the <quote>8GB</quote> geometry mode setting in the - BIOS. Use the 2GB mode instead.</para> - </answer> - </qandaentry> - </qandaset> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/common/upgrade.sgml b/release/doc/en_US.ISO_8859-1/installation/common/upgrade.sgml deleted file mode 100644 index 93e80bf..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/common/upgrade.sgml +++ /dev/null @@ -1,255 +0,0 @@ -<!-- - $FreeBSD$ - - This section contains the contents of the old UPGRADE.TXT - file. ---> -<sect1 id="upgrading"> - <title>Upgrading &os;</title> - - <para>These instructions describe a procedure for doing a binary - upgrade from an older version of &os;.</para> - - <warning> - <para>While the &os; upgrade procedure does its best to - safeguard against accidental loss of data, it is still more than - possible to <emphasis>wipe out your entire disk</emphasis> with - this installation! Please do not accept the final confirmation - request unless you have adequately backed up any important data - files.</para> - </warning> - - <important> - <para>These notes assume that you are using the version of - &man.sysinstall.8; supplied with the version of &os; to which you - intend to upgrade. Using a mismatched version of &man.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 &man.sysinstall.8; from - an existing installation to upgrade to a newer version of - &os;. This is <emphasis>not</emphasis> recommended.</para> - - <para>Furthermore, if you are upgrading from &os; 2.2.5 or - earlier, see <xref linkend="fstab"> for important details regarding changes - to the <filename>/etc/fstab</filename> file required during the upgrade procedure.</para> - </important> - - <sect2> - <title>Introduction</title> - - <para>The upgrade procedure replaces distributions selected by the - user with those corresponding to the new &os; release. It - preserves standard system configuration data, as well as user - data, installed packages and other software.</para> - - <para>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.</para> - - <sect3> - <title>Upgrade Overview</title> - - <para>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.</para> - - <para>System configuration is preserved by retaining and - restoring the previous version of the following files:</para> - - <para><filename>Xaccel.ini</filename>, -<filename>adduser.conf</filename>, -<filename>aliases</filename>, -<filename>aliases.db</filename>, -<filename>amd.map</filename>, -<filename>crontab</filename>, -<filename>csh.cshrc</filename>, -<filename>csh.login</filename>, -<filename>csh.logout</filename>, -<filename>daily</filename>, -<filename>disktab</filename>, -<filename>dm.conf</filename>, -<filename>exports</filename>, -<filename>fbtab</filename>, -<filename>fstab</filename>, -<filename>ftpusers</filename>, -<filename>gettytab</filename>, -<filename>gnats</filename>, -<filename>group</filename>, -<filename>hosts</filename>, -<filename>hosts.equiv</filename>, -<filename>hosts.lpd</filename>, -<filename>inetd.conf</filename>, -<filename>kerberosIV</filename>, -<filename>localtime</filename>, -<filename>login.access</filename>, -<filename>mail.rc</filename>, -<filename>make.conf</filename>, -<filename>manpath.config</filename>, -<filename>master.passwd</filename>, -<filename>mib.txt</filename>, -<filename>modems</filename>, -<filename>monthly</filename>, -<filename>motd</filename>, -<filename>namedb</filename>, -<filename>networks</filename>, -<filename>nsswitch.conf</filename>, -<filename>passwd</filename>, -<filename>phones</filename>, -<filename>ppp</filename>, -<filename>printcap</filename>, -<filename>profile</filename>, -<filename>protocols</filename>, -<filename>pwd.db</filename>, -<filename>rc</filename>, -<filename>rc.firewall</filename>, -<filename>rc.i386</filename>, -<filename>rc.local</filename>, -<filename>rc.network</filename>, -<filename>rc.conf</filename>, -<filename>remote</filename>, -<filename>resolv.conf</filename>, -<filename>rmt</filename>, -<filename>security</filename>, -<filename>sendmail.cf</filename>, -<filename>services</filename>, -<filename>shells</filename>, -<filename>skeykeys</filename>, -<filename>spwd.db</filename>, -<filename>supfile,</filename> -<filename>syslog.conf</filename>, -<filename>termcap</filename>, -<filename>ttys</filename>, -<filename>uucp</filename>, -<filename>weekly</filename></para> - - <para>The versions of these files which correspond to the new - version are moved to <filename>/etc/upgrade/</filename>. 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.</para> - - <para>During the upgrade procedure, the administrator is - prompted for a location into which all files from - <filename>/etc/</filename> are saved. In the event that local - modifications have been made to other files, they may be - subsequently retrieved from this location.</para> - - </sect3> - </sect2> - - <sect2> - <title>Procedure</title> - - <para>This section details the upgrade procedure. Particular - attention is given to items which substantially differ from a - normal installation.</para> - - <sect3> - <title>Backup</title> - - <para>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.</para> - </sect3> - - <sect3> - <title>Mount Filesystems</title> - - <para>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. <emphasis>Do not</emphasis>set the <quote>newfs - flag</quote> for any filesystems, as this will cause data - loss.</para> - </sect3> - - <sect3> - <title>Select Distributions</title> - - <para>When selecting distributions, there are no constraints - on which must be selected. As a general rule, the <literal>bin</literal> - distribution should be selected for an update, and the <literal>man</literal> - distribution if manpages are already installed. Other - distributions may be selected beyond those originally - installed if the administrator wishes to add additional - functionality.</para> - </sect3> - - <sect3 id="fstab"> - <title>After Installation</title> - - <para>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 - <filename>/etc/rc.conf</filename> and - <filename>/etc/fstab</filename> files should be checked.</para> - - <para>Read the following, but <emphasis>do not</emphasis> update - <filename>/etc/fstab</filename> as described below until the new - system has booted correctly. The upgrade procedure replaces the - previous &os; kernel with a <filename>GENERIC</filename> kernel, - and a custom kernel may need to be generated to suit the local - system configuration.</para> - - <important> - <para>&os; 2.2.6 introduced a change in the naming of the - device from which the root filesystem is mounted. This - change affects all systems, however user intervention is - only required for systems undergoing an upgrade installation - from a version prior to &os; 2.2.6.</para> - - <para>Previously, the root filesystem was always mounted from - the compatibility slice, while other partitions on the same - disk were mounted from their true slice. This might, for - example, have resulted in an <filename>/etc/fstab</filename> - file like:</para> - -<screen># Device Mountpoint FStype Options Dump Pass# -/dev/wd0s2b none swap sw 0 0 -/dev/wd0a / ufs rw 1 1 -/dev/wd0s2f /local0 ufs rw 1 1 -/dev/wd0s2e /usr ufs rw 1 1</screen> - - <para>For &os; 2.2.6 and later, this format changes so that - the device for <filename>/</filename> is consistent with - others. Also, the driver for the ATA-drives has changed from - &man.wd.4; to &man.ad.4;, so the new file could look something - like:</para> - -<screen># Device Mountpoint FStype Options Dump Pass# -/dev/ad0s2b none swap sw 0 0 -/dev/ad0s2a / ufs rw 1 1 -/dev/ad0s2f /local0 ufs rw 1 1 -/dev/ad0s2e /usr ufs rw 1 1</screen> - - <para>If <filename>/etc/fstab</filename> is not updated - manually in this case, the system will issue a warning message - whenever <filename>/</filename> is mounted (normally at - startup) indicating the change that must be made. In - addition, trouble may be experienced if the root filesystem is - not correctly unmounted, whereby the root filesystem will not - be marked clean at the next reboot.</para> - - <para>This change should be made as soon as the upgraded - system has been successfully rebooted.</para> - </important> - </sect3> - </sect2> - - <sect2> - <title>Alternative Upgrade Techniques</title> - - <para>Those interested in an upgrade method that allows more - flexibility and sophistication should take a look at the - <quote>Upgrading FreeBSD from source</quote> tutorial found at - http://www.freebsd.org/docs.html. This method requires reliable - network connectivity, extra disk space and spare time, but has - advantages for networks and other more complex - installations.</para> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/installation/i386/Makefile b/release/doc/en_US.ISO_8859-1/installation/i386/Makefile deleted file mode 100644 index 19de1c1..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/i386/Makefile +++ /dev/null @@ -1,20 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= ../common/artheader.sgml -SRCS+= ../common/install.sgml -SRCS+= ../common/floppies.sgml -SRCS+= ../common/layout.sgml -SRCS+= ../common/trouble.sgml -SRCS+= ../common/upgrade.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/installation/i386/article.sgml b/release/doc/en_US.ISO_8859-1/installation/i386/article.sgml deleted file mode 100644 index 007a794..0000000 --- a/release/doc/en_US.ISO_8859-1/installation/i386/article.sgml +++ /dev/null @@ -1,27 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/install.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "i386"> - -]> - -<article> -&artheader; -§.install; -§.layout; -§.floppies; -§.upgrade; -§.trouble; -</article> diff --git a/release/doc/en_US.ISO_8859-1/readme/Makefile b/release/doc/en_US.ISO_8859-1/readme/Makefile deleted file mode 100644 index 5dd73b9..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/Makefile +++ /dev/null @@ -1,25 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# -# SRCS lists the individual SGML files that make up the document. Changes -# to any of these files will force a rebuild -# - -# SGML content -SRCS+= article.sgml -SRCS+= artheader.sgml -SRCS+= intro.sgml -SRCS+= about.sgml -SRCS+= obtaining.sgml -SRCS+= problems.sgml -SRCS+= ack.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/readme/about.sgml b/release/doc/en_US.ISO_8859-1/readme/about.sgml deleted file mode 100644 index 1a33d14..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/about.sgml +++ /dev/null @@ -1,102 +0,0 @@ -<!-- - -$FreeBSD$ - -about.sgml - -General information about FreeBSD. Most contents of this file -come from the old ABOUT.TXT. - ---> - -<sect1> - <title>About &os;</title> - - <para>What is &os;? &os; is an operating system based on 4.4 BSD - Lite for Intel, AMD, Cyrix or NexGen <quote>x86</quote> based PC - hardware and Compaq (formerly DEC) Alpha computers. Versions for - the IA64 and PowerPC architectures are currently under - development as well. &os; works with a - very wide variety of PC peripherals and configurations and can be - used for everything from software development to Internet Service - Provision.</para> - - <para>This release of &os; contains everything you need to run - such a system, including full source code for everything. With the - source distribution installed you can literally recompile the entire - system from scratch with one command, making it ideal for students, - researchers or folks who simply want to see how it all works.</para> - - <para>A large collection of third party ported software (the - <quote>Ports Collection</quote>) is also provided to make it easier - for you to obtain and install all your favorite traditional UNIX - utilities for &os;. Over 5000 ports, from editors to programming - languages to graphical applications, make &os; a powerful and - comprehensive operating environment that extends far beyond what's - provided by many commercial versions of UNIX.</para> - - <para>For more documentation on this system it is recommended that - you purchase The Complete FreeBSD, available from local bookstores - and from The FreeBSD Mall (<ulink - url="http://www.freebsdmall.com">http://www.freebsdmall.com</ulink>), - as well as the 4.4BSD Document Set from O'Reilly Associates and the - USENIX Association, ISBN 1-56592-082-1. We have no connection with - O'Reilly, we're just satisfied customers!</para> - - <para>If you're new to &os; then you should also read - <emphasis>everything</emphasis> - listed in the Documentation menu on the boot floppy. It may seem - like a lot to read, but you should at least acquaint yourself with - the types of information available should you later get stuck. Once - the system is installed, you can also revisit this menu and use a - Web browser to read the installed FAQ (Frequently Asked Questions) - and Handbook HTML documentation sets for &os;. Note that on-line - versions of the <ulink - url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink - url="http://www.freebsd.org/handbook/">Handbook</ulink> are also - available from the <ulink - url="http://www.freebsd.org/">FreeBSD Project Web - site</ulink>, if you have an Internet connection. See - <filename>README.TXT</filename> for more information on the - resources available to you.</para> - - <note> - <para>If you read no other documentation before installing a given - version of &os;, you should at least by all means <emphasis>read - the errata</emphasis> for that release so that you don't stumble - over problems which have already been found and fixed. The - <filename>ERRATA.TXT</filename> file accompanying your release (it - should be right next to this file) is obviously already out of - date by definition, but other copies are kept updated on the net - and should be consulted as the <quote>current errata</quote> for - your release (this is also what your - <filename>ERRATA.TXT</filename> file says, by the way). These - other copies of the errata are located at: - - <orderedlist> - <listitem> - <para><ulink url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink></para> - </listitem> - <listitem> - <para>ftp://ftp.freebsd.org/pub/FreeBSD/releases/your-release/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this - location).</para> - </listitem> - </orderedlist> - </para> - </note> - - <warning> - - <para>While &os; does its best to safeguard against accidental - loss of data, it's still more than possible to <emphasis>wipe out - your entire disk</emphasis> - with this installation! Please do not proceed to the - final &os; installation menu unless you've adequately backed up - any important data first! We really mean it!</para> - - </warning> -</sect1> - - - diff --git a/release/doc/en_US.ISO_8859-1/readme/ack.sgml b/release/doc/en_US.ISO_8859-1/readme/ack.sgml deleted file mode 100644 index 7b135a2..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/ack.sgml +++ /dev/null @@ -1,29 +0,0 @@ -<!-- - -$FreeBSD$ - -ack.sgml - -This file is the Acknowledgments section of the old RELNOTES.TXT. - ---> - -<sect1> - <title>Acknowledgments</title> - - <para>&os; represents the cumulative work of many hundreds, if not - thousands, of individuals from around the world who have worked very - hard to bring you this release. For a complete list of &os; - project staffers, please see:</para> - - <para><ulink url="http://www.freebsd.org/handbook/staff.html">http://www.freebsd.org/handbook/staff.html</ulink></para> - - <para>or, if you've loaded the doc distribution:</para> - - <para><filename>/usr/share/doc/handbook/staff.html</filename></para> - - <para>Special thanks also go to the many thousands of &os; users and - testers all over the world, without whom this release simply would - not have been possible.</para> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/readme/artheader.sgml b/release/doc/en_US.ISO_8859-1/readme/artheader.sgml deleted file mode 100644 index a167f56..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/artheader.sgml +++ /dev/null @@ -1,13 +0,0 @@ -<!-- $FreeBSD$ --> - -<articleinfo> - <title>&os; &release.current; README</title> - - <corpauthor>The &os; Project</corpauthor> - - <copyright> - <year>2000</year> - <year>2001</year> - <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> - </copyright> -</articleinfo> diff --git a/release/doc/en_US.ISO_8859-1/readme/article.sgml b/release/doc/en_US.ISO_8859-1/readme/article.sgml deleted file mode 100644 index 2652850..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/article.sgml +++ /dev/null @@ -1,22 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "readme.ent"> %sections; -]> - -<article> -&artheader; -§.intro; -§.about; -§.obtaining; -§.problems; -§.ack; -</article> diff --git a/release/doc/en_US.ISO_8859-1/readme/intro.sgml b/release/doc/en_US.ISO_8859-1/readme/intro.sgml deleted file mode 100644 index 13f84f6..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/intro.sgml +++ /dev/null @@ -1,86 +0,0 @@ -<!-- - -$FreeBSD$ - -intro.sgml - -Introduction to the README file. Most text here comes from the -old README.TXT (the file with Chuck in ASCII art). - ---> - -<sect1> - <title>Introduction</title> - - <para>This is a binary snapshot of &os; &release.current;, the - &release.branch; branch that is currently moving towards - &release.next;.</para> - - <para>Feedback or offers to help with anything you see in this - release are most welcome and should be sent to one of the - appropriate mailing lists, as listed in <xref linkend="contacting">.</para> - - <sect2> - <title>Target Audience</title> - - <para>This release is aimed primarily at early-adopters and the - various other folks who want to get involved with the ongoing - development of &os; and are willing to deal with a few bumps in - the road. We do our best to ensure that each snapshot works as - advertised, but tracking -CURRENT is a process which frequently - has its off days.</para> - - <para>If you're both technically proficient and know exactly what - you're getting into here (e.g. you've been following -CURRENT) - then this snapshot is probably for you. If you're more interested - in doing business with &os; than in playing with the cutting - edge of technology, however, then 3.x or 4.x is almost certainly - your best bet.</para> - - <para>If you're a developer/hobbiest and not interested in QA'd - releases so much as simply keeping up to date on the latest &os; - technology, you can also install one of our - <quote>snapshot</quote> releases. - </para> - </sect2> - - <sect2> - <title>For More Information</title> - - <para>A number of other files provide more specific information - about this distribution. - - <itemizedlist> - <listitem> - <para><filename>README.TXT</filename>: This file, which - gives some general information about &os; as well as some - cursory notes about installation..</para> - </listitem> - <listitem> - <para><filename>RELNOTES.TXT</filename>: The release notes, - showing what's new and different in &os; &release.current; - compared to &os; &release.prev;.</para> - </listitem> - <listitem> - <para><filename>HARDWARE.TXT</filename>: The hardware - compatability list, showing devices with which &os; has been - tested and is known to work.</para> - </listitem> - <listitem> - <para><filename>ERRATA.TXT</filename>: Release errata. - Late-breaking, post-release information can be found in this - file. Read this file! It will tell you where to look for - the latest information on problems which have been found and - fixed since this release was created (and may bite - you).</para> - </listitem> - </itemizedlist> - - </para> - - <para>Most information is also available from the - Documentation menu during installation.</para> - - </sect2> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/readme/obtaining.sgml b/release/doc/en_US.ISO_8859-1/readme/obtaining.sgml deleted file mode 100644 index d90be98..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/obtaining.sgml +++ /dev/null @@ -1,102 +0,0 @@ -<!-- - -$FreeBSD$ - -obtaining.sgml - -Information on getting a copy of FreeBSD. This text used to -be the "Obtaining FreeBSD" section of RELNOTES.TXT. ---> - -<sect1> - <title>Obtaining &os;</title> - - <para>You may obtain &os; in a variety of ways. This section - focuses on those ways that are primarily of use for obtaining a - complete &os; distribution, rather than updating an existing - installation. More information can be found in the <ulink - url="http://www.freebsd.org/handbook/mirrors.html"><quote>Obtaining - FreeBSD</quote></ulink> appendix to the <ulink - url="http://www.freebsd.org/handbook/">FreeBSD - Handbook</ulink>.</para> - - <sect2> - <title>CDROM</title> - <para>&os; 4.x-RELEASE and 3.x-RELEASE may be ordered on - CDROM from: - <address> - BSDi - <street>4041 Pike Lane, Suite D</street> - <city>Concord</city> <state>CA</state> <postcode>94520</postcode> - <country>USA</country> - <phone>+1-800-786-9907</phone> - <phone>+1-925-674-0783</phone> - <fax>+1-925-674-0821 (FAX)</fax></address> - </para> - - <para>Orders may also be placed via the Internet from - <email>orders@cdrom.com</email> or <ulink - url="http://www.cdrom.com/">http://www.cdrom.com/</ulink>. A - current catalog can be obtained via ftp from <ulink - url="ftp://ftp.cdrom.com/cdrom/catalog">ftp://ftp.cdrom.com/cdrom/catalog</ulink>.</para> - - <para>As of this writing, the cost per -RELEASE CDROM set is $39.95 - (US Dollars) or $24.95 with a &os; - subscription. &os; SNAPshot CDROM sets, when available, are $39.95 or - $14.95 with a &os;-SNAP subscription (-RELEASE and -SNAP - subscriptions are entirely separate). With a subscription, you - will automatically receive updates as they are released. Your - credit card will be billed when each disk is shipped and you may - cancel your subscription at any time without further - obligation.</para> - - <para>Shipping (per order not per disk) is $5.00 in the United - States, Canada or Mexico and $9.00 overseas. BSDi accepts Visa, - Mastercard, Discover, American Express or checks in U.S. Dollars - and ships COD within the United States. California residents - please add 8.25% sales tax.</para> - - <para>Should you be dissatisfied for any reason, the CDROM comes with - an unconditional return policy.</para> - </sect2> - - <sect2> - <title>FTP</title> - - <para>You can use FTP to retrieve &os; and any or all of its - optional packages from <ulink - url="ftp://ftp.freebsd.org/">ftp://ftp.freebsd.org/</ulink>, which - is the - official &os; release site.</para> - - <para>For other locations that mirror the &os; software see the - file <filename>MIRROR.SITES</filename>. - Please FTP the distribution from the site - closest (in networking terms) to you. Additional mirror sites are - always welcome! - Contact <email>freebsd-admin@FreeBSD.org</email> for more - details if you'd like to become an official mirror site.</para> - - <para>Mirrors generally contain the floppy disk images necessary - to begin an installation, as well as the distribution files needed - for the install process itself. Some mirrors also contain some of - the ISO images necessary to create a CDROM of a &os; release.</para> - - </sect2> - - <sect2> - <title>Email</title> - - <para>If you do not have access to the Internet and electronic - mail is your only recourse, then you may still fetch the files by - sending mail to <email>ftpmail@ftpmail.vix.com</email> - putting - the keyword <literal>help</literal> in your message to get more - information on how to fetch files from a &os; FTP archive using - this mechanism. Please do note, however, that this will end up - sending many <emphasis>tens of megabytes</emphasis> through the - mail and should only be employed as an absolute - <emphasis>last</emphasis> resort!</para> - </sect2> -</sect1> - - diff --git a/release/doc/en_US.ISO_8859-1/readme/problems.sgml b/release/doc/en_US.ISO_8859-1/readme/problems.sgml deleted file mode 100644 index 03f1a59..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/problems.sgml +++ /dev/null @@ -1,78 +0,0 @@ -<!-- - -$FreeBSD$ - -problems.sgml - -Information on contacting the FreeBSD project, originally from -RELNOTES.TXT. - ---> - -<sect1 id="contacting"> - <title>Reporting Problems, Making Suggestions, and Submitting - Code</title> - - <para>Your suggestions, bug reports and contributions of code are - always valued — please do not hesitate to report any problems you - may find (preferably with a fix attached, if you can!).</para> - - <para>The preferred method to submit bug reports from a machine with - Internet mail connectivity is to use the &man.send-pr.1; command or - use the CGI script at <ulink - url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>. - Bug reports will be dutifully filed by our faithful bugfiler program - and you can be sure that we'll do our best to respond to all - reported bugs as soon as possible. Bugs filed in this way are also - visible on our Web site in the support section and are therefore - valuable both as bug reports and as <quote>signposts</quote> for - other users concerning potential problems to watch out for.</para> - - <para>If, for some reason, you are unable to use &man.send-pr.1; to - submit a bug report, you can try to send it to the &a.bugs;.</para> - - <para>Note that &man.send-pr.1; itself is a shell script that should - be easy to move even onto a totally different system. We much - prefer if you could use this interface, since it make it easier to - keep track of the problem reports. However, before submitting, - please try to make sure whether the problem might have already been - fixed since.</para> - - <para>Otherwise, for any questions or tech support issues, please send - mail to the &a.questions;.</para> - - <para>If you're tracking the -current development efforts, you - <emphasis>must</emphasis> join the &a.current;, in order to keep - abreast of recent developments and changes that may affect the way - you use and maintain the system. - - <para>Additionally, being a volunteer effort, we are always happy to - have extra hands willing to help — there are already far more - desired enhancements than we'll ever be able to manage by ourselves! - To contact us on technical matters, or with offers of help, please - send mail to the &a.hackers;.</para> - - <para>Please note that these mailing lists can experience - <emphasis>significant</emphasis> amounts of traffic and if you have - slow or expensive mail access and are only interested in keeping up - with significant FreeBSD events, you may find it preferable to - subscribe instead to the &a.announce;.</para> - - <para>All of the mailing lists can be freely joined by anyone - wishing to do so. Send mail to &a.majordomo; - and include the keyword <literal>help</literal> on a line by itself - somewhere in the body of the message. This will give you more - information on joining the various lists, accessing archives, etc. - There are a number of mailing lists targeted at special interest - groups not mentioned here; more information can be obtained either - through majordomo or the <ulink - url="http://www.freebsd.org/support.html#mailing-list">mailing lists - section</ulink> of the FreeBSD Web site.</para> - - <important> - <para>Do <emphasis>not</emphasis> send email to the lists asking to - be subscribed. Use the &a.majordomo; address - instead.</para> - </important> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/readme/readme.ent b/release/doc/en_US.ISO_8859-1/readme/readme.ent deleted file mode 100644 index c63fe15..0000000 --- a/release/doc/en_US.ISO_8859-1/readme/readme.ent +++ /dev/null @@ -1,14 +0,0 @@ -<!-- -*- sgml -*- --> -<!-- $FreeBSD$ --> - -<!-- Text constants which probably don't need to be changed.--> - -<!-- Files to be included --> - -<!ENTITY artheader SYSTEM "artheader.sgml"> -<!ENTITY sect.intro SYSTEM "intro.sgml"> -<!ENTITY sect.about SYSTEM "about.sgml"> -<!ENTITY sect.obtaining SYSTEM "obtaining.sgml"> -<!ENTITY sect.problems SYSTEM "problems.sgml"> -<!ENTITY sect.ack SYSTEM "ack.sgml"> - diff --git a/release/doc/en_US.ISO_8859-1/relnotes/Makefile b/release/doc/en_US.ISO_8859-1/relnotes/Makefile deleted file mode 100644 index dca8380..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/Makefile +++ /dev/null @@ -1,9 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../.. - -SUBDIR = alpha -SUBDIR+= i386 - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/relnotes/alpha/Makefile b/release/doc/en_US.ISO_8859-1/relnotes/alpha/Makefile deleted file mode 100644 index 2c0390b..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/alpha/Makefile +++ /dev/null @@ -1,18 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= ../common/relnotes.ent -SRCS+= ../common/artheader.sgml -SRCS+= ../common/new.sgml -SRCS+= ../common/upgrading.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/relnotes/alpha/article.sgml b/release/doc/en_US.ISO_8859-1/relnotes/alpha/article.sgml deleted file mode 100644 index 99cdc4b..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/alpha/article.sgml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "alpha"> - -]> - -<article> - &artheader; - §.intro; - §.new; - §.upgrading; -</article> diff --git a/release/doc/en_US.ISO_8859-1/relnotes/common/artheader.sgml b/release/doc/en_US.ISO_8859-1/relnotes/common/artheader.sgml deleted file mode 100644 index 104657b..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/common/artheader.sgml +++ /dev/null @@ -1,13 +0,0 @@ -<!-- $FreeBSD$ --> - -<articleinfo> - <title>&os; &release.current; &arch; Release Notes</title> - - <corpauthor>The FreeBSD Project</corpauthor> - - <copyright> - <year>2000</year> - <year>2001</year> - <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> - </copyright> -</articleinfo> diff --git a/release/doc/en_US.ISO_8859-1/relnotes/common/intro.sgml b/release/doc/en_US.ISO_8859-1/relnotes/common/intro.sgml deleted file mode 100644 index 1f765a2..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/common/intro.sgml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- - $FreeBSD$ - - Introduction to the release notes, adapted from the - introduction to the old RELNOTES.TXT. ---> - -<sect1> - <title>Introduction</title> - - <para>This document contains the release notes for &os; &release.current; on - the &arch; hardware platform. It describes new features of &os; - that have been added (or changed) since &release.prev;.</para> - - <para>For information about &os; and the layout of the - distribution directory (especially if you're installing from - floppies!), see <filename>README.TXT</filename>. For installation - instructions, see the <filename>INSTALL.TXT</filename> and - <filename>HARDWARE.TXT</filename> files.</para> - - <para>For the latest of these &release.branch; snapshots, you should always - see:</para> - - <para><ulink url="&release.url;">&release.url;</ulink></para> - -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/relnotes/common/new.sgml b/release/doc/en_US.ISO_8859-1/relnotes/common/new.sgml deleted file mode 100644 index 8e60d54..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/common/new.sgml +++ /dev/null @@ -1,1755 +0,0 @@ -<!-- - - $FreeBSD$ - - The "What's New" section of the release notes. Within - each subsection (i.e. kernel, security, userland), list - items in chronological order, unless necessary to keep - related items together, such as multiple release notes - pertaining to a single program or module. - ---> - -<sect1> - <sect1info> - <pubdate>$FreeBSD$</pubdate> - </sect1info> - - <title>What's New</title> - - <para>This section describes the most user-visible new or changed - features in &os; since &release.prev;. All changes - described here are unique to the &release.branch; branch unless - specifically marked as &merged; features.</para> - - <para>Many additional changes were made to &os; that are not listed - here for lack of space. For example, documentation was corrected - and improved, minor bugs were fixed, insecure coding practices were - audited and corrected, and source code was cleaned up.</para> - - <sect2> - <title>Kernel Changes</title> - - <para>The &man.kqueue.2; event notification facility was added to - the &os; kernel. This is a new interface which is able to - replace &man.poll.2;/&man.select.2, offering improved performance, - as well as the ability to report many different types of events. - Support for monitoring changes in sockets, pipes, fifos, and files - are present, as well as for signals and processes. &merged;</para> - - <para arch="i386">Support for Intel's Wired for Management 2.0 (PXE) - was added to the FreeBSD boot loader. Due to API differences, the - older PXE versions are not supported. This allow network booting - using DHCP. &merged;</para> - - <para>Support for USB devices was added to the - <filename>GENERIC</filename> kernel and to the installation - programs to support USB devices out of the box. Note that SRM - does not support USB devices at the moment, so you must still use - an AT keyboard if you are not using a serial console. &merged;</para> - - <para>POSIX.1b Shared Memory Objects are now supported. The - implementation uses regular files, but automatically enables the - MAP_NOSYNC flag when they are &man.mmap.2;-ed. &merged;</para> - - <para arch="i386">A driver for AGP hardware has been added. &merged;</para> - - <para>The kernel and modules have been moved to the directory - <filename>/boot/kernel</filename>, so they can be easily - manipulated together. The boot loader has been updated to make - this change as seamless as possible.</para> - - <para arch="i386">The i386 boot loader now has support for a - <literal>nullconsole</literal> - console type, for use on systems with neither a video console nor - a serial port. &merged;</para> - - <para>Replaced the <literal>PQ_*CACHE</literal> options with a - single <literal>PQ_CACHESIZE</literal> option to be set to - the cache size in kilobytes. The old options are still supported - for backwards compatibility. &merged;</para> - - <para arch="i386">The <literal>NCPU</literal>, <literal>NAPIC</literal>, - <literal>NBUS</literal>, and <literal>NINTR</literal> kernel - configuration options, for configuring SMP kernels, have been - removed. <literal>NCPU</literal> is now set to a maximum of 16, - and the other, aforementioned options are now - dynamic. &merged;</para> - - <para>&man.devfs.5;, which allows entries in the - <filename>/dev</filename> directory to be built automatically and - supports more flexible attachment of devices, has been largely - reworked. &man.devfs.5; is now enabled by default and can be - disabled by the <literal>NODEVFS</literal> kernel option.</para> - - <para arch="i386">Preliminary Cardbus support under NEWCARD has been added. - This code supports the TI113X, TI12XX, TI125X, Ricoh 5C46/5C47, Topic - 95/97/100 and Cirrus Logic PD683X bridges. 16-bit PC Card support - is not yet functional.</para> - - <para>Write combining for crashdumps has been implemented. This - feature is useful when write caching is disabled on both SCSI and - IDE disks, where large memory dumps could take up to an hour to - complete. &merged;</para> - - <para>Extremely large swap areas (>67 GB) no longer panic the - system.</para> - - <para arch="i386">The &man.ichsmb.4; driver for the Intel 82801AA - (ICH) SMBus controller and compatibles has been - added. &merged;</para> - - <para arch="i386">The &man.uscanner.4; driver for basic USB scanner support - using SANE has been added. See <ulink - url="http://www.mostang.com/sane/">the SANE home page</ulink> for - supported scanners. The HP ScanJet 4100C, 5200C and 6300C are - known to be working.</para> - - <para arch="i386">The umodem driver for USB modems has been added. - Support is provided for the 3Com 5605 and Metricom Ricochet GS - wireless USB modems.</para> - - <para arch="alpha">Support for threads under Linux emulation has been - added.</para> - - <para arch="i386">The pccard driver and &man.pccardc.8; now support multiple - <quote>beep types</quote> upon card insertion and removal. &merged;</para> - - <para>A number of cleanups and enhancements have been applied to - the PCI subsystem. - <filename>/usr/share/misc/pci_vendors</filename> now contains a - vendor/device database, which can be used by - &man.pciconf.8;.</para> - - <para arch="i386">The &man.spic.4; driver, which provides access to the job - dial device on some Sony laptops, has been added.</para> - - <para><quote>sbufs</quote>, null-terminated string data - structures, and their - associated support routines, have been added to the kernel. - Details are in &man.sbuf.9;.</para> - - <para arch="i386">PECOFF (WIN32 Execution file format) support has been - added.</para> - - <para>A VESA S3 linear framebuffer driver has been added.</para> - - <para>The <maketarget>buildkernel</maketarget> target now gets the - name of the configuration(s) to build from the - <varname>KERNCONF</varname> variable, not - <varname>KERNEL</varname>. It is no longer required, in some - cases, for a <maketarget>buildworld</maketarget> to precede a - <maketarget>buildkernel</maketarget>. (The - <maketarget>buildworld</maketarget> is still required when - upgrading across major releases, across - <application>binutil</application> upgrades and when &man.config.8; - changes version.) - </para> - - <para>The &man.random.4; device has been rewritten to use the - <application>Yarrow</application> algorithm. It harvests entropy - from a variety of interrupt sources, including the console - devices, Ethernet and point-to-point network interfaces, and - mass-storage devices. Entropy from the &man.random.4; device is - now periodically saved to files in - <filename>/var/db/entropy</filename>, as well as at - &man.shutdown.8; time.</para> - - <para>The &man.syscons.4; driver now supports keyboard-controlled - pasting, by default bound to - <keycap>Shift</keycap>-<keycap>Insert</keycap>.</para> - - <para>The &man.labpc.4; driver has been removed due to - <quote>bitrot</quote>.</para> - - <para>A new kernel option, <literal>options REGRESSION</literal>, - enables interfaces and functionality intended for use during - correctness and regression testing.</para> - - <para>The <literal>USER_LDT</literal> kernel option is now - activated by default.</para> - - <para>A new &man.ddb.4; command <command>show pcpu</command> lists - some of the per-CPU data.</para> - - <para>A new digi driver has been added to support PCI Xr-based and ISA - Xem Digiboard cards. A new digictl program is (mainly) used to - re-initialise cards that have external port modules attached such as - the PC/Xem.<para> - - <para>The <literal>O_DIRECT</literal> flag has been added to - &man.open.2; and &man.fcntl.2;. Specifying this flag for open - files will attempt to minimize the cache effects of reading and - writing. &merged;</para> - - <para><literal>OLDCARD</literal> and &man.pccardd.8; now support - PCI cards.</para> - - <sect3> - <title>Processor/Motherboard Support</title> - - <para>SMP support has been largely reworked, incorporating code - from BSD/OS 5.0. One of the main features of SMPng (<quote>SMP - Next Generation</quote>) is to allow more processes to run in - kernel, without the need for spin locks that can dramatically - reduce the efficiency of multiple processors. Interrupt - handlers now have contexts associated with them that allow them - to be blocked, which reduces the need to lock out - interrupts.</para> - - <para arch="i386">Support for the 80386 processor has been - removed from the <filename>GENERIC</filename> kernel, as this - code seriously pessimizes performance on other ia32 - processors.</para> - - <para arch="i386">The <literal>I386_CPU</literal> kernel option - to support the 80386 processor is now mutually exclusive with - support for other ia32 processors; this should slightly improve - performance on the 80386 due to the elimination of runtime - processor type checks.</para> - - <para arch="i386">Custom kernels that will run on the 80386 can - still be built by changing the cpu options in the kernel - configuration file to only include - <literal>I386_CPU</literal>.</para> - - <para arch="alpha">AlphaServer 1200 (<quote>Tincup</quote>) has - been tested and works OK. Currently it does not want to boot - from CD or floppy but a transplanted disk that was installed on - another Alpha works well. &merged;</para> - - <para arch="alpha">The API UP1100 mainboard has been verified to work.</para> - - <para arch="alpha">The API CS20 1U high server has been verified to work.</para> - - <para arch="alpha">The DEC3000 series support has been removed from the mfsroot - floppy image so that it fits on a 1.44 Mbyte floppy again. As the - DEC3000 is currently only usable diskless this should not cause - any problems.</para> - - <para arch="alpha">Support for AlphaServer 2100A (<quote>Lynx</quote>) has been - added.</para> - - <para arch="alpha">Kernel code has been added that allows older generation Alpha CPUs - (EV4 and EV5) to emulate instructions of the newer Alpha CPU - generations. This enables the use of binary-only programs like Adobe - Acrobat 4 on EV4 and EV5.</para> - - <para arch="alpha">SMP support for the alpha is now operational.</para> - - </sect3> - - <sect3> - <title>Network Interface Support</title> - - <para>Added support for PCI Ethernet adapters based on the - National Semiconductor DP83815 chipset, including the NetGear - FA311-TX and FA312-TX, in the form of the &man.sis.4; driver.</para> - - <para>The &man.tap.4; driver, a virtual Ethernet device driver for - bridged configurations, has been added. &merged;</para> - - <para>The &man.ti.4; driver now supports the Alteon AceNIC - 1000baseT Gigabit Ethernet and Netgear GA620T 1000baseT Gigabit - cards. &merged;</para> - - <para>The &man.xl.4; driver now supports the 3Com 3C556 and 3C556B - MiniPCI adapters used on some laptops. &merged;</para> - - <para arch="alpha">The &man.ed.4; driver is now supported.</para> - - <para>The &man.pcn.4; driver, which supports the AMD PCnet/FAST, - PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA - adapters, has been added. Although these cards are already - supported by the &man.lnc.4; driver, the &man.pcn.4; driver runs - these chips in 32-bit mode and uses the RX alignment feature to - achieve zero-copy receive. This driver is also - machine-independent, so it will work on both the i386 and alpha - platforms. The &man.lnc.4; driver is still needed to support non-PCI - cards. &merged;</para> - - <para>Support for Fujitsu MB86960A/MB86965A based Ethernet - PC-Cards is back. &merged;</para> - - <para arch="i386">The snc driver for the National Semiconductor - DP8393X (SONIC) Ethernet controller has been added. Currently, - this driver is only used on the PC-98 architecture. &merged;</para> - - <para>The &man.an.4; driver for Cisco Aironet cards now supports - Wired Equivalent Privacy (WEP) encryption, settable via - &man.ancontrol.8;. &merged;</para> - - <para arch="i386">The &man.el.4; driver can now be loaded as a - module.</para> - - <para>The &man.ray.4; driver, which supports the Webgear Aviator - wireless network cards, has been committed. The operation of - &man.ray.4; interfaces can be modified by - &man.raycontrol.8;. &merged;</para> - - <para arch="alpha">The &man.fpa.4; driver now supports Digital's - DEFPA FDDI adaptors on the Alpha.</para> - - <para arch="i386">Linksys Fast Ethernet PCCARD cards supported by the - &man.ed.4; driver now require the addition of flag - <literal>0x80000</literal> to their config line in - &man.pccard.conf.5;. This flag is not optional. These Linksys - cards will not be recognized without it.</para> - - <para>A bug in the &man.ed.4; driver that could cause panics with - very short packets and BPF or bridging active has been - fixed. &merged;</para> - - <para>The &man.fxp.4; driver now requires a <literal>device - miibus</literal> entry in the kernel configuration file. &merged;</para> - - <para>The &man.wx.4; driver now supports the Intel PRO1000-F and - PRO1000-T (10/100/1000) adapters. &merged;</para> - - <para>Added the &man.nge.4; driver, which supports PCI Gigabit - Ethernet adapters based on the National Semiconductor DP83820 - and DP83821 Gigabit Ethernet controller chips, including the - D-Link DGE-500T, SMC EZ Card 1000 (SMC9462TX), Asante - FriendlyNet GigaNIC 1000TA and 1000TPC and Addtron - AEG320T.</para> - - <para>The &man.lge.4; driver has been added to support the Level - 1 LXT1001 NetCellerator Gigabit Ethernet controller chip. This - device is used on some fiber optic GigE cards from SMC, D-Link - and Addtron. Jumbograms and TCP/IP checksum offload on receive - are supported, although hardware VLAN filtering is not.</para> - - <para>The &man.xl.4; driver now supports reception of VLAN - tagged frames (on the <quote>Cyclone</quote> or newer - chipsets). &merged;</para> - - <para>The &man.ti.4; driver correctly masks VLAN tags. &merged;</para> - - </sect3> - - <sect3> - <title>Network Protocols</title> - - <para>Various fixes and improvements to the IPv6 code have been merged in - from the KAME project, including significantly-improved IPSEC - functionality. &merged;</para> - - <para>&man.accept.filter.9;, a kernel feature to reduce overheads - when accepting and reading new connections on listening sockets, - has been added. &merged;</para> - - <para>The &man.ng.mppc.4; and &man.ng.bridge.4; node types have - been added to the netgraph subsystem. The &man.ng.ether.4; node - is now dynamically loadable. Miscellaneous bug fixes and - enhancements have also been made. &merged;</para> - - <para>&man.netgraph.4; has received some updates and bugfixes.</para> - - <para>A new netgraph node type &man.ng.one2many.4; for multiplexing - and demultiplexing packets over multiple links has been added. - &merged;</para> - - <para arch="alpha">SLIP has been removed from the - <filename>mfsroot</filename> floppy image.</para> - - <para>ICMP ECHO and TSTAMP replies are now rate limited. TCP RSTs - generated due to packets sent to open and unopen ports are now - limited by separate counters. Each rate limiting queue now has - its own description.</para> - - <para>ICMP <literal>UNREACH_FILTER_PROHIB</literal> messages can - now RST TCP connections in the <literal>SYN_SENT</literal> state - if the correct sequence numbers are sent back, as controlled by the - <literal>net.inet.tcp.icmp_may_rst</literal> - sysctl.</para> - - <para>TCP has received some bug fixes for its delayed ACK - behavior. &merged;</para> - - <para>TCP now supports the NewReno modification to the TCP Fast Recovery - algorithm. This behavior can be controlled via the - <varname>net.inet.tcp.newreno</varname> sysctl variable. &merged;</para> - - <para>TCP now uses a more aggressive timeout for initial SYN segments; this - allows initial connection attempts to be dropped much - faster. &merged;</para> - - <para>The <literal>TCP_COMPAT_42</literal> kernel option has - been removed.</para> - - <para>TCP now has RFC 1323 extensions enabled by default in - &man.rc.conf.5;. &merged;</para> - - <para>RFC 1323 and RFC 1644 TCP extensions are now disabled for a - connection in progress if no response has been received by the - third SYN segment sent. This behavior tries to work around - (very old) terminal servers with buggy VJ header compression - implementations.</para> - - <para>A new sysctl <literal>net.inet.ip.check_interface</literal>, - which is on by default, causes IP to verify that an incoming - packet arrives on an interface that has an address matching the - packet's destination address. &merged;</para> - - <para>A new sysctl - <literal>net.link.ether.inet.log_arp_wrong_iface</literal> has - been added to control the suppression of logging when ARP replies - arrive on the wrong interface. &merged;</para> - - <para>&man.ipfw.8; now filters correctly in the presence of ECN bits in TCP - segments. &merged;</para> - - <para>&man.ipfw.8; will now avoid the display of dynamic - firewall rules unless the <option>-d</option> flag is passed to - it. The <option>-e</option> lists expired dynamic rules.</para> - - <para>&man.bridge.4; and &man.dummynet.4; have received some - enhancements and bug fixes.</para> - - <para>&man.ipfw.8; has a new feature (<literal>me</literal>) that - allows for packet matching on interfaces with dynamically-changing - IP addresses. &merged;</para> - - <para>&man.ip6fw.8; now has the ability to use a preprocessor - and use the <option>-q</option> (quiet) flag when reading from a - file. &merged;</para> - - <para>A new <literal>options RANDOM_IP_ID</literal> kernel - option causes the ID field of IP packets to be randomized. This - closes a minor information leak which allows a remote observer - to determine the rate at which the machine is generating - packets, since the default behaviour is to increment a counter - for each packet sent.</para> - - <para>IP multicast now works on VLAN devices. Several other - bugs in the VLAN code have also been fixed.</para> - - </sect3> - - <sect3> - <title>Disks and Storage</title> - - <para arch="i386">The &man.twe.4; 3ware ATA RAID driver has added. &merged;</para> - - <para>The &man.ata.4; driver now has support for ATA100 - controllers. In addition, it now supports the ServerWorks ROSB4 - ATA33 chipset, the CMD 648 ATA66 and CMD 649 ATA100 chipsets, and - the Cyrix 5530. &merged;</para> - - <para>To provide more flexible configuration, the various options for the - &man.ata.4; driver are now boot loader tunables, rather than kernel - configure-time options. &merged;</para> - - <para>The &man.ata.4; driver now has support for tagged queuing, - which is enabled by the <literal>hw.ata.tags</literal> loader - tunable. &merged;</para> - - <para>The &man.ata.4; driver now has support for ATA - <quote>pseudo</quote> RAID controllers as the Promise Fasttrak and - HighPoint HPT370 controllers. &merged;</para> - - <para arch="i386">The &man.mly.4; driver, for Mylex PCI to SCSI - AccelRAID and eXtremeRAID controllers with firmware 6.X and - later, has been added. &merged;</para> - - <para arch="i386">The &man.asr.4; driver, which provides support - for the Adaptec SCSI RAID controller family, as well as the DPT - SmartRAID V and VI families, has been added. &merged;</para> - - <para arch="i386">Support for the Adaptec FSA family of PCI-SCSI - RAID controllers has been added, in the form of the &man.aac.4; - driver.</para> - - <para>The &man.ahc.4; driver has received numerous updates, - bugfixes, and enhancements. Among various improvements are - improved compatibility with chips in <quote>RAID Port</quote> mode - and systems with AAA and/or ARO cards installed, as well as - performance improvements. Some bugs were also fixed, including a - rare hang on Ultra2/U160 controllers. &merged;</para> - - <para arch="i386">The ncv, nsp, and stg drivers have - been ported from NetBSD/pc98. They support the NCR 53C50 / - Workbit Ninja SCSI-3 / TMC 18C30, 18C50 based PC-Card/ISA SCSI - controllers. &merged;</para> - - <para>The &man.cd.4; driver now has support for write operations. - This allows writing to DVD-RAM, PD and similar drives that probe - as CD devices. Note that change affects only random-access - writeable devices, not sequential-only writeable devices such as - CD-R drives, which are supported by &man.cdrecord.1; in the Ports - Collection. &merged;</para> - - <para>The &man.vinum.4; volume manager has received some bug fixes and - enhancements.</para> - - <para>&man.md.4;, the memory disk device, has had the - functionality of &man.vn.4; incorporated into it. &man.md.4; - devices can now be configured by &man.mdconfig.8;. &man.vn.4; has - been removed. The Memory Filesystem (MFS) has also been - removed.</para> - - <para>BurnProof(TM) support, for applicable ATAPI CD-ROM burners, is now - supported. &merged;</para> - - <para arch="alpha">A bug that made certain CDROM drives fail to - attach when connected to a SCSI card driven by &man.isp.4; has - been fixed. &merged;</para> - - <para>The &man.isp.4; driver has been updated. &merged;</para> - - <para>The &man.isp.4; driver now supports target mode for Qlogic - SCSI cards, including Ultra2 and Ultra3 and dual bus cards.</para> - - <para>The ida disk driver now has crashdump support. &merged;</para> - - <para>The CAM error recovery code has been updated.</para> - - <para>Some problems in &man.sa.4; error handling have been - fixed, including the <quote>tape drive spinning indefinitely - upon mt stat</quote> problem.</para> - - </sect3> - - <sect3> - <title>Filesystems</title> - - <para>Support for named extended attributes was added to the &os; - kernel. This allows the kernel, and appropriately privileged - userland processes, to tag files and directories with attribute - data. Extended attributes were added to support the TrustedBSD - Project, in particular ACLs, capability data, and mandatory access - control labels (see - <filename>/usr/src/sys/ufs/ufs/README.extattr</filename> for - details).</para> - - <para>Due to a licensing change, softupdates have been integrated - into the main portion of the kernel source tree. As a - consequence, softupdates are now available with the - <filename>GENERIC</filename> kernel. &merged;</para> - - <para>A filesystem snapshot capability has been added to FFS. - Details can be found in - <filename>/usr/src/sys/ufs/ffs/README.snapshot</filename>.</para> - - <para>Softupdates for FFS have received some bug fixes and - enhancements.</para> - - <para>When running with softupdates, &man.statfs.2; and - &man.df.1; will track the number of blocks and files that are - committed to being freed.</para> - - <para>A bug in FFS that could cause superblock corruption on very large - filesystems has been corrected. &merged;</para> - - <para>The Inode Filesystem (IFS) has been added; more information - can be found in - <filename>/usr/src/sys/ufs/ifs/README</filename>.</para> - - <para>The ISO-9660 filesystem now has a hook that supports a loadable - character conversion routine. The - <filename>sysutils/cd9660_unicode</filename> port - contains a set of common conversions.</para> - - <para>&man.kernfs.5; is obsolete and has been retired.</para> - - <para>A bug in the NFS client that caused bogus access times with - <literal>O_EXCL|O_CREAT</literal> opens was fixed. &merged;</para> - - <para>A new NFS hash function (based on the Fowler/Noll/Vo hash - algorithm) has been implemented to improve NFS performance by - increasing the efficiency of the <varname>nfsnode</varname> hash - tables. &merged;</para> - - <para>Client-side NFS locks have been implemented.</para> - - <para>Support for file system Access Control Lists (ACLs) has been - introduced, allowing more fine-grained control of discretionary - access control on files and directories. This support was - integrated from the TrustedBSD Project. More details can be found in - <filename>/usr/src/sys/ufs/ufs/README.acls</filename>.</para> - - <para>The directory layout preference algorithm for FFS has been - changed to improve its speed on large filesystems.</para> - - <para arch="i386">smbfs (CIFS) support in kernel has been - added. &merged;</para> - - <para>For consistency, the fdesc, fifo, null, msdos, portal, - umap, and union filesystems have been renamed to fdescfs, - fifofs, msdosfs, nullfs, portalfs, umapfs, and unionfs. Where - applicable, modules and mount_* programs have been - renamed. Compatability <quote>glue</quote> has been added to - &man.mount.8; so that <literal>msdos</literal> filesystem - entries in &man.fstab.5; will work without changes.</para> - - </sect3> - - <sect3> - <title>Multimedia Support</title> - - <para arch="i386">The &man.pcm.4; driver now supports the ESS Solo 1, - Maestro-1, Maestro-2, and Maestro-2e; Forte Media fm801, ESS - Maestro-2e, and VIA Technologies VT82C686A sound card/chipsets, - and has received some other updates. - Separate drivers for the SoundBlaster 8 and Soundblaster 16 now - replace an older, unified driver. A driver for the CMedia - CMI8338/CMI8738 sound chips has been added. A driver for the - CS4281 sound chip has been added. A driver for the S3 - Sonicvobes chipset has been added. &merged;</para> - - <para arch="i386">A driver for the Advance Logic ALS4000 has been added.</para> - - <para arch="i386">A driver for the - ESS Maestro-3/Allegro has been added, however due to licensing - restrictions, it cannot be compiled into the kernel. &merged; To - use this driver, add the following line to - <filename>/boot/loader.conf</filename>: - - <screen><userinput>snd_maestro3_load="YES"</userinput></screen> - - </para> - - <para>The &man.bktr.4; driver has been updated to 2.18. This - update provides a number of new features: New tuner - types have been added, and improvements to the KLD module and to - memory allocation have been made. Bugs in &man.devfs.5; when - unloading and reloading have been fixed. - Support for new Hauppauge Model 44xxx WinTV Cards (the ones with - no audio mux) has been added.</para> - - <para>When sound modules are built, one can now load all the - drivers and infrastructure by <command>kldload - snd</command>.</para> - - <para>A new API has been added for sound cards with hardware - volume control.</para> - - </sect3> - - <sect3> - <title>Contributed Software</title> - - <para><application>IPFilter</application> has been updated to - 3.4.16. &merged;</para> - - <para>The Forth Inspired Command Language - (<application>FICL</application>) used in the boot loader has - been updated to 2.05.</para> - - <para>ACPI support has been merged in from the - <application>Intel ACPI</application> - project, and updated to the ACPI CA 20010518 release.</para> - - <sect4 arch="i386"> - <title>isdn4bsd</title> - - <para><application>isdn4bsd</application> has been updated to - version 0.96.00.</para> - - <para>The &man.ihfc.4; driver for supporting Cologne Chip - Designs HFC devices under <application>isdn4bsd</application> - has been added.</para> - - <para>The &man.itjc.4; driver for supporting NETjet-S / Teles - PCI-TJ devices under <application>isdn4bsd</application> has - been added.</para> - - <para>Experimental support for the Eicon.Diehl DIVA 2.0 and - 2.02 ISA PnP ISDN cards has been added to the &man.isic.4; - <application>isdn4bsd</application> driver.</para> - - <para>Active CAPI-based ISDN cards manufacured by AVM are now - supported using the &man.i4bcapi.4; and the &man.iavc.4; driver. The - supported cards are the AVM B1 PCI and AVM B1 ISA Basic Rate - cards and the AVM T1 Primary Rate cards.</para> - </sect4> - </sect3> - </sect2> - <sect2> - <title>Security Fixes</title> - - <para>&man.sysinstall.8; now allows the user to select one of three - <quote>security profiles</quote> at install-time. These profiles enable - different levels of system security by enabling or disabling - various system services in &man.rc.conf.5; on new - installs. &merged;</para> - - <para>A bug in which malformed ELF executable images can hang the - system has been fixed (see security advisory - FreeBSD-SA-00:41). &merged;</para> - - <para>A security hole in Linux emulation was fixed (see security - advisory FreeBSD-SA-00:42). &merged;</para> - - <para>&man.rlogind.8;, &man.rshd.8;, and &man.fingerd.8; are now - disabled by default in <filename>/etc/inetd.conf</filename>. This - only affects new installations. &merged;</para> - - <para>String-handling library calls in many programs were fixed to - reduce the possibility of buffer overflow-related exploits. - &merged;</para> - - <para>TCP now uses stronger randomness in choosing its initial sequence - numbers (see security advisory FreeBSD-SA-00:52). &merged;</para> - - <para>Several buffer overflows in &man.tcpdump.1; were corrected - (see security advisory FreeBSD-SA-00:61). &merged;</para> - - <para>A security hole in &man.top.1; was corrected (see security advisory - FreeBSD-SA-00:62). &merged;</para> - - <para>A potential security hole caused by an off-by-one-error in - &man.gethostbyname.3; has been fixed (see security advisory - FreeBSD-SA-00:63). &merged;</para> - - <para>A potential buffer overflow in the &man.ncurses.3; library, - which could cause arbitrary code to be run from within - &man.systat.1;, has been corrected (see security advisory - FreeBSD-SA-00:68). &merged;</para> - - <para>A vulnerability in &man.telnetd.8; that could cause it to - consume large amounts of server resources has been fixed (see - security advisory FreeBSD-SA-00:69). &merged;</para> - - <para>The <literal>nat deny_incoming</literal> command in - &man.ppp.8; now works correctly (see security advisory - FreeBSD-SA-00:70). &merged;</para> - - <para>A vulnerability in &man.csh.1;/&man.tcsh.1; temporary files - that could allow overwriting of arbitrary user-writable files has - been closed (see security advisory FreeBSD-SA-00:76). &merged;</para> - - <para>The &man.ssh.1; binary is no longer SUID root by - default.</para> - - <para>Some fixes were applied to the Kerberos - IV implementation related to environment variables, a - possible buffer overrun, and overwriting ticket files. &merged;</para> - - <para>&man.telnet.1; now does a better job of sanitizing its - environment. &merged;</para> - - <para>Several vulnerabilities in &man.procfs.5; were fixed (see - security advisory FreeBSD-SA-00:77). &merged;</para> - - <para>A bug in <application>OpenSSH</application> in which a - server was unable to disable &man.ssh-agent.1; or - <literal>X11Forwarding</literal> was fixed (see security advisory - FreeBSD-SA-01:01). &merged;</para> - - <para>A bug in &man.ipfw.8; and &man.ip6fw.8; in which inbound TCP - segments could incorrectly be treated as being part of an - <literal>established</literal> connection has been fixed (see - security advisory FreeBSD-SA-01:08). &merged;</para> - - <para>A bug in &man.crontab.1; that could allow users to read any - file on the system in valid &man.crontab.5; syntax has been fixed - (see security advisory FreeBSD-SA-01:09). &merged;</para> - - <para>A vulnerability in &man.inetd.8; that could allow - read-access to the initial 16 bytes of - <groupname>wheel</groupname>-accessible files has been fixed (see security - advisory FreeBSD-SA-01:11). &merged;</para> - - <para>A bug in &man.periodic.8; that used insecure temporary files has been - corrected (see security advisory FreeBSD-SA-01:12). &merged;</para> - - <para>A bug in &man.sort.1; in which an attacker might be able to - cause it to abort processing has been fixed (see security advisory - FreeBSD-SA-01:13). &merged;</para> - - <para>To fix a remotely-exploitable buffer overflow, - <application>BIND</application> has been updated - to 8.2.3 (see security advisory FreeBSD-SA-01:18). &merged;</para> - - <para><application>OpenSSH</application> now has code to prevent - (instead of just mitigating through connection limits) an attack - that can lead to guessing the server key (not host key) by - regenerating the server key when an RSA failure is detected (see - security advisory FreeBSD-SA-01:24). &merged;</para> - - <para>A number of programs have had output formatting strings - corrected so as to reduce the risk of vulnerabilities. &merged;</para> - - <para>A number of programs that use temporary files now do so more - securely. &merged;</para> - - <para>A bug in ICMP that could cause an attacker to disrupt TCP and UDP - <quote>sessions</quote> has been corrected. &merged;</para> - - <para>A bug in &man.timed.8;, which caused it to crash if send - certain malformed packets, has been corrected (see security - advisory FreeBSD-SA-01:28). &merged;</para> - - <para>A bug in &man.rwhod.8;, which caused it to crash if send - certain malformed packets, has been corrected (see security - advisory FreeBSD-SA-01:29). &merged;</para> - - <para>A security hole in FreeBSD's FFS and EXT2FS implementations, - which allowed a race condition that could cause users to have - unauthorized access to data, has been fixed (see security advisory - FreeBSD-SA-01:30). &merged;</para> - - <para>A remotely-exploitable vulnerability in &man.ntpd.8; has - been closed (see security advisory FreeBSD-SA-01:31). &merged;</para> - - <para>A security hole in <application>IPFilter</application>'s - fragment cache has been closed (see - security advisory FreeBSD-SA-01:32). &merged;</para> - - <para>Buffer overflows in &man.glob.3;, which could cause - arbitrary code to be run on an FTP server, have been closed. In - addition, to prevent some forms of DOS attacks, &man.glob.3; - allows specification of a limit on the number of pathname matches - it will return. &man.ftpd.8; now uses this feature (see security - advisory FreeBSD-SA-01:33). &merged;</para> - - <para>Initial sequence numbers in TCP are more thoroughly - randomized (see security advisory FreeBSD-SA-01:39). &merged;</para> - - <para>The new <varname>net.inet.ip.maxfragpackets</varname> sysctl - variable limits the amount of memory that can be consumed by IPv4 - packet fragments, which defends against some denial of service - attacks.</para> - - <para>A vulnerability in the &man.fts.3; routines (used by - applications for recursively traversing a filesystem) could - allow a program to operate on files outside the intended directory - hierarchy. This bug has been fixed (see security advisory - FreeBSD-SA-01:40). &merged;</para> - - <para>&os;'s TCP implementation has been made more resistant to - SYN floods, by eliminating the RST segment normally sent when - removing a connection from the listen queue.</para> - </sect2> - <sect2> - <title>Userland Changes</title> - - <para>&man.cdcontrol.1; now supports a <literal>cdid</literal> - command, which calculates and displays the CD serial number, using - the same algorithm used by the CDDB database. &merged;</para> - - <para>&man.mtree.8; now includes support for a file that lists - pathnames to be excluded when creating and verifying prototypes. - This makes it easier to use &man.mtree.8; as a part of an - intrusion-detection system. &merged;</para> - - <para>&man.ls.1; can produce colorized listings with the - <option>-G</option> flag (and appropriate terminal - support). &merged;</para> - - <para>&man.sysinstall.8; now properly preserves - <filename>/etc/mail</filename> during a binary upgrade. &merged;</para> - - <para>The &man.truncate.1; utility, which truncates or extends the length - of files, has been added. &merged;</para> - - <para>&man.syslogd.8; can take a <option>-n</option> option to - disable DNS queries for every request. &merged;</para> - - <para>&man.kenv.1;, a command to dump the kernel environment, has - been added. &merged;</para> - - <para>The behavior of &man.periodic.8; is now controlled by - <filename>/etc/defaults/periodic.conf</filename> and - <filename>/etc/periodic.conf</filename>. &merged;</para> - - <para arch="i386">&man.boot98cfg.8;, a PC-98 boot manager installation and - configuration utility, has been added. &merged;</para> - - <para>&man.logger.1; can now send messages directly to a remote - syslog. &merged;</para> - - <para arch="i386">&man.gdb.1; now supports hardware watchpoints (using the - kernel's debug register + support that has been introduced in - &os; 4.0). &merged;</para> - - <para>&man.which.1; is now a C program, rather than a Perl - script.</para> - - <para>&man.killall.1; is now a C program, rather than a Perl - script. As a result, its <option>-m</option> option now uses the - regular expression syntax of &man.regex.3;, rather than that of - &man.perl.1;. &merged;</para> - - <para>&man.killall.1; now allows non-root users to kill SUID root - processes that they started, the same as the Perl version did.</para> - - <para>&man.finger.1; now has the ability to support fingering - aliases, via the &man.finger.conf.5; file. &merged;</para> - - <para>&man.finger.1; now has support for a - <filename>.pubkey</filename> file.</para> - - <para>nsswitch support has been merged from NetBSD. By creating - an &man.nsswitch.conf.5; file, FreeBSD can be configured so that - various databases such as &man.passwd.5; and &man.group.5; can be - looked up using flat files, NIS, or Hesiod. The old - <filename>hosts.conf</filename> file is no longer used.</para> - - <para>RSA Security has waived all patent rights to the RSA - algorithm. As a - result, the native <application>OpenSSL</application> - implementation of the RSA algorithm is now activated by default, - and the <filename>rsaref</filename> port and - <filename>librsaUSA</filename> are no longer required for USA - residents. &merged;</para> - - <para>&man.ifconfig.8; command can set the link-layer address - of an interface. &merged;</para> - - <para>&man.ifconfig.8; can now accept addresses in slash/CIDR - notation. &merged;</para> - - <para>&man.ifconfig.8; now has support for setting parameters for - IEEE 802.11 wireless network devices. &man.wi.4; and - &man.an.4; devices are supported, and partial support is provided - for awi devices.</para> - - <para>&man.ifconfig.8; no longer displays the list of supported - media by default. Instead it displays it when the - <option>-m</option> is given.</para> - - <para>&man.setproctitle.3; has been moved from - <filename>libutil</filename> to - <filename>libc</filename>. &merged;</para> - - <para>&man.chio.1; now has the ability to specify elements by - volume tag instead of by their physical location as well as the - ability to return an element to its previous location. &merged;</para> - - <para>&man.sed.1; now takes a <option>-E</option> option for - extended regular expression support. &merged;</para> - - <para>&man.ln.1; now takes an <option>-i</option> option to - request user confirmation before overwriting an existing - file. &merged;</para> - - <para>&man.ln.1; now takes a <option>-h</option> flag to avoid - following a target that is a link, with a <option>-n</option> flag - for compatability with other implementations. &merged;</para> - - <para>Userland &man.ppp.8; has received a number of updates and - bug fixes. &merged;</para> - - <para>&man.make.1; has gained the <literal>:C///</literal> - (regular expression substitution), <literal>:L</literal> - (lowercase), and <literal>:U</literal> (uppercase) variable - modifiers. These were added to reduce the differences between the - &os; and - OpenBSD/NetBSD - &man.make.1 programs. &merged; </para> - - <para>Bugs in &man.make.1;, among which include broken null suffix - behavior, bad assumptions about current directory permissions, and - potential buffer overflows, have been fixed. &merged;</para> - - <para>The &os; <filename>Makefile</filename> infrastructure now - supports the <varname>WARNS</varname> directive from NetBSD. This - directive controls the addition of compiler warning flags to - <varname>CFLAGS</varname> in a relatively compiler-neutral - manner.</para> - - <para>&man.fsck.8; wrappers have been imported; this feature - provides infrastructure for &man.fsck.8; to work on different - types of filesystems (analogous to &man.mount.8;).</para> - - <para>The behavior of &man.fsck.8; when dealing with various - passes (a la <filename>/etc/fstab</filename>) has been modified to - accomodate multiple-disk filesystems.</para> - - <para>&man.style.perl.7;, a style guide for Perl code in the &os; - base system, has been added.</para> - - <para>The <quote>in use</quote> percentage metric displayed by - &man.netstat.1; now really reflects the percentage of network - mbufs used. &merged;</para> - - <para>&man.netstat.1; now has a <option>-W</option> flag that - tells it not to truncate addresses, even if they're too long for - the column they're printed in. &merged;</para> - - <para>&man.netstat.1; now keeps track of input and output packets - on a per-address basis for each interface. &merged;</para> - - <para>&man.sockstat.1; now has <option>-c</option> and - <option>-l</option> flags for listing connected and listening - sockets, respectively. &merged;</para> - - <para>&man.mergemaster.8; has gained some new features, has been - cleaned up somewhat, and is now more cross-platform friendly.</para> - - <para>&man.mergemaster.8; now sources an - <filename>/etc/mergemaster.rc</filename> file and also prompts the - user to run recommended commands (such as - <command>newaliases</command>) as needed. &merged;</para> - - <para>The compiler chain now uses the FSF-supplied C/C++ runtime - initialization code. This change brings about better - compatibility with code generated from the various egcs and gcc - ports, as well as the stock public FSF source. &merged;</para> - - <para>The threads library has gained some signal handling changes, - bug fixes, and performance enhancements (including zero system - call thread switching). &man.gdb.1; thread support has been - updated to match these changes. &merged;</para> - - <para>&man.chflags.1; has moved from <filename>/usr/bin</filename> - to <filename>/bin</filename>.</para> - - <para>Use of the <literal>CSMG_*</literal> macros no longer - require inclusion of - <filename><sys/param.h></filename></para> - - <para>IP Filter is now supported by the - &man.rc.conf.5; boot-time configuration and - initialization. &merged;</para> - - <para>The &man.lastlogin.8; utility, which prints the last login - time of each user, has been imported from - NetBSD. &merged;</para> - - <para>&man.last.1; now implements a <option>-d</option> that - provides a <quote>snapshot</quote> of who was logged in at a - particular date and time</para> - - <para>&man.newfs.8; now implements write combining, which can make - creation of new filesystems up to seven times - faster. &merged;</para> - - <para>&man.newfs.8; now takes a <option>-U</option> option to - enable softupdates on a new filesystem. &merged;</para> - - <para>The default number of cylinders per group in &man.newfs.8; - is now 22, up from 16.</para> - - <para>A number of buffer overflows in &man.config.8; have been - fixed. &merged;</para> - - <para>&man.pwd.1; can now double as &man.realpath.1;, a program to - resolve pathnames to their underlying physical paths. &merged;</para> - - <para>&man.stty.1; now has support for an - <literal>erase2</literal> control character, so that, for example, - both the <keycap>Delete</keycap> and <keycap>Backspace</keycap> - keys can be used to erase characters. &merged;</para> - - <para>The &man.ibcs2.8;, &man.linux.8;, &man.osf1.8;, and &man.svr4.8; - scripts, whose sole purpose was to load emulation - kernel modules, have been removed. The kernel module system will - automatically load them as needed to fulfill dependencies.</para> - - <para>&man.top.1; will now use the full width of its tty.</para> - - <para>&man.growfs.8;, a utility for growing FFS filesystems, has - been added. &man.ffsinfo.8;, a utility for dump all the - meta-information of an existing filesystem, has also been - added.</para> - - <para>&man.indent.1; has gained some new formatting - options. &merged;</para> - - <para>&man.sysinstall.8; now uses some more intuitive defaults - thanks to some new dialog support functions. &merged;</para> - - <para>The default root partition in &man.sysinstall.8; is now - 100MB on the i386 and 120MB on the alpha.</para> - - <para>Shortly after the receipt of a <literal>SIGINFO</literal> - signal (normally control-T from the controlling tty), &man.fsck.ffs.8; - will now output a line indicating the current phase number and - progress information relevant to the current phase. &merged;</para> - - <para>&man.fsck.ffs.8; now supports background filesystem checks - to mounted FFS filesystems with the <option>-B</option> option - (softupdates must be enabled on these filesystems). The - <option>-F</option> flag now determines whether a specified - filesystem needs foreground checking.</para> - - <para>&man.fsck.8; now has support for foreground - (<option>-F</option>) and background (<option>-B</option>) checks. - Traditionally, &man.fsck.8; is invoked before the filesystems are - mounted and all checks are done to completion at that time. If - background checking is available, &man.fsck.8; is invoked twice. - It is first invoked at the traditional time, before the - filesystems are mounted, with the <option>-F</option> flag to do - checking on all the filesystems that cannot do background - checking. It is then invoked a second time, after the system has - completed going multiuser, with the <option>-B</option> flag to do - checking on all the filesystems that can do background checking. - Unlike the foreground checking, the background checking is started - asynchronously so that other system activity can proceed even on - the filesystems that are being checked. Boot-time enabling of - this feature is controlled by the - <varname>background_fsck</varname> option in &man.rc.conf.5;.</para> - - <para>Catching up with most other network utilities in the base - system, &man.lpr.1;, &man.lpd.8;, &man.syslogd.8;, and - &man.logger.1; are now all IPv6-capable. &merged;</para> - - <para arch="i386"><filename>libdisk</filename> can now do - install-time configuration of the &arch; <filename>boot0</filename> - boot loader. &merged;</para> - - <para>The <option>-v</option> option to &man.rm.1; now displays - the entire pathname of a file being removed.</para> - - <para>&man.lpr.1;, &man.lpq.1;, and &man.lpd.8; have received a - few minor enhancements. &merged;</para> - - <para>If the first argument to &man.ancontrol.8; or - &man.wicontrol.8; doesn't start with a <literal>-</literal>, it is - assumed to be an interface.</para> - - <para>&man.rdist.1; has been retired.</para> - - <para>&man.ppp.8; has gained the <literal>tcpmssfixup</literal> - option, which adjusts outgoing TCP SYN packets so that the maximum - receive segment size is no larger than allowed by the interface - MTU.</para> - - <para><filename>libcrypt</filename> and - <filename>libdescrypt</filename> have been unified to provide a - configurable password authentication hash library. Both the md5 - and des hash methods are provided unless the des hash is - specifically compiled out.</para> - - <para>&man.passwd.1; and &man.pw.8; now select the password hash - algorithm at run time. See the <literal>passwd_format</literal> - attribute in <filename>/etc/login.conf</filename>.</para> - - <para>In preparation for meeting SUSv2/POSIX - <filename><sys/select.h></filename> requirements, - <literal>struct selinfo</literal> and related functions have been - moved to <filename><sys/selinfo.h></filename>.</para> - - <para>&man.syslogd.8; now supports a <literal>LOG_CONSOLE</literal> - facility (disabled by - default), which can be used to log <filename>/dev/console</filename> - output. &merged;</para> - - <para>&man.rpcgen.1; now uses <filename>/usr/bin/cpp</filename> - (as on NetBSD), not <filename>/usr/libexec/cpp</filename>.</para> - - <para>Boot-time &man.syscons.4; configuration was moved to a - machine-independent <filename>/etc/rc.syscons</filename>. &merged;</para> - - <para>&man.burncd.8; now supports a <option>-m</option> option for - multisession mode (the default behavior now is to close disks as - single-session). A <option>-l</option> option to take a list of - image files from a filename was also added; <filename>-</filename> - can be used as a filename for <literal>stdin</literal>. &merged;</para> - - <para>&man.dmesg.8; now has a <option>-a</option> option to show - the entire message buffer, including &man.syslogd.8; records and - <filename>/dev/console</filename> output. &merged;</para> - - <para>&man.cdcontrol.1; now uses the <literal>CDROM</literal> - environment variable to pick a default device. &merged;</para> - - <para>&man.cdcontrol.1; now supports <literal>next</literal> and - <literal>prev</literal> commands to skip forwards or backwards a - specified number of tracks while playing an audio CD.</para> - - <para>&man.sysctl.8; now supports a <option>-N</option> option to - print out variable names only.</para> - - <para>&man.sysctl.8; has replaced the <option>-A</option> and - <option>-X</option> options with <option>-ao</option> and - <option>-ax</option> respectively; the former options are now - deprecated. The <option>-w</option> is deprecated as well; it is - not needed to determine the user's intentions.</para> - - <para>&man.sysinstall.8; now lives in <filename>/usr/sbin</filename>, - which simplifies the installation process. The &man.sysinstall.8; - manpage is also installed in a more consistent fashion now.</para> - - <para>&man.config.8; is now better about converting various - warnings that should - have been errors into actual fatal errors with an exit code. This - ensures that <literal>make buildkernel</literal> - doesn't quietly ignore them and - build a bogus kernel without a human to read the errors. &merged;</para> - - <para><filename>libc</filename> is now thread-safe by default; - <filename>libc_r</filename> contains only thread functions.</para> - - <para>&man.find.1; now takes the <option>-empty</option> flag, - which returns true if a file or directory is empty. &merged;</para> - - <para>&man.find.1; now takes the <option>-iname</option> and - <option>-ipath</option> primaries for case-insensitive matches, - and the <option>-regexp</option> and <option>-iregexp</option> - primaries for regular-expression matches. The <option>-E</option> - flag now enables extended regular expressions. &merged;</para> - - <para>&man.find.1; now has the <option>-anewer</option>, - <option>-cnewer</option>, <option>-mnewer</option>, - <option>-okdir</option>, and <option>-newer[acm][acmt]</option> - primaries for comparisons of file timestamps. &merged;</para> - - <para>&man.tftpd.8; now takes the <option>-c</option> and - <option>-C</option> options, which allow the server to - &man.chroot.2; based on the IP address of the connecting client. - &man.tftp.1; and &man.tftpd.8; can now transfer files larger than - 65535 blocks. &merged;</para> - - <para>&man.vidcontrol.1; now accepts a <option>-g</option> - parameter to select custom text geometry in the - <literal>VESA_800x600</literal> raster text mode. &merged;</para> - - <para>&man.ldconfig.8; now checks directory ownerships and - permissions for greater security; these checks can be disabled - with the <option>-i</option> flag. &merged;</para> - - <para>The &man.rfork.thread.3; library call has been added as a - helper function to &man.rfork.2;. Using this function should - avoid the need to implement complex stack swap - code. &merged;</para> - - <para>Significant additions have been made to internationalization - support; &os; now has complete locale support for the - <literal>LC_MONETARY</literal>, <literal>LC_NUMERIC</literal>, and - <literal>LC_MESSAGES</literal> categories. A number of - applications have been updated to take advantage of this - support.</para> - - <para>A <filename>compat4x</filename> distribution has been added - for compatibility with &os; 4-STABLE.</para> - - <para>The - <filename>compat3x</filename> distribution has been updated to - include libraries present in &os; 3.5.1-RELEASE. &merged;</para> - - <para>&man.savecore.8; now supports a <option>-k</option> option - to prevent clearing a crash dump after saving it. It also - attempts to avoid writing large stretches of zeros to crash dump - files to save space and time. &merged;</para> - - <para>&man.savecore.8; now works correctly on machines with 2 GB - or more of RAM. &merged;</para> - - <para>&man.tar.1; now supports the <varname>TAR_RSH</varname> - variable, principally to enable the use of &man.ssh.1; as a - transport. &merged;</para> - - <para>&man.disklabel.8; now supports partition sizes expressed in - kilobytes, megabytes, or gigabytes, in addition to sectors. &merged;</para> - - <para>The pseudo-random number generator implemented by - &man.rand.3; has been improved to provide less biased results.</para> - - <para>&man.login.1; now exports environment variables set by - <application>PAM</application> modules. &merged;</para> - - <para><application>PAM</application> support has been added for - account management and sessions.</para> - - <para>&man.su.1; now uses <application>PAM</application> for - authentication.</para> - - <para>&man.wall.1; now supports a <option>-g</option> flag to - write a message to all users of a given group.</para> - - <para>The new <varname>CPUTYPE</varname> - <filename>make.conf</filename> variable controls the compilation - of processor-specific optimizations in various pieces of code such - as <application>OpenSSL</application>. &merged;</para> - - <para>The default value for &man.cvs.1;'s - <varname>CVS_RSH</varname> variable is now <literal>ssh</literal>, - rather than <literal>rsh</literal>. &merged;</para> - - <para>&man.ipfstat.8; now supports the <option>-t</option> option - to turn on a &man.top.1;-like display. &merged;<para> - - <para><filename>/usr/src/share/examples/BSD_daemon/</filename> now - contains a scalable Beastie graphic. &merged;</para> - - <para>&man.dump.8; now supports inheritance of the - <literal>nodump</literal> flag down a hierarchy. &merged;</para> - - <para>&man.split.1; now has the ability to split a file longer - than 2GB. &merged;</para> - - <para>&man.tail.1; now has the ability to work on files longer - than 2GB. &merged;</para> - - <para>&man.units.1; has received some updates and bugfixes. &merged;</para> - - <para>As part of an ongoing process, many manual pages were - improved, both in terms of their formatting markup and in their - content. &merged;</para> - - <para><command>lprm -</command> now works for remote printer - queues. &merged;</para> - - <para>&man.ftpd.8; now supports a <option>-r</option> flag for - read-only mode and a <option>-E</option> flag to disable - <literal>EPSV</literal>. It also has some fixes to reduce - information leakage and the ability to specify compile-time port - ranges. &merged;</para> - - <para>&man.ping.8; now supports a <option>-m</option> option to - set the TTL of outgoing packets. &merged;</para> - - <para>&man.ping.8; now supports a <option>-A</option> option to - beep when packets are lost.</para> - - <para>A version of Transport Independent RPC - (<application>TI-RPC</application>) has been imported.</para> - - <para>&man.rpcbind.8; has replaced &man.portmap.8;.</para> - - <para>NFS now works over IPv6.</para> - - <para>&man.rpc.lockd.8; has been imported from NetBSD.</para> - - <para>&man.rc.8; now has an framework for handling dependencies between - &man.rc.conf.5; variables. &merged;</para> - - <para>&man.rc.8; now deletes all non-directory files in - <filename>/var/run</filename> and - <filename>/var/spool/lock</filename> at boot time.</para> - - <para>The &man.setfacl.1; and &man.getfacl.1; commands have been - added to manage file system Access Control Lists.</para> - - <para>The default TCP port range used by - <filename>libfetch</filename> for passive FTP retrievals has - changed; this affects the behavior of &man.fetch.1;, which has - gained the <option>-U</option> option to restore the old - behavior. &merged;</para> - - <para>&man.atacontrol.8; has been added to control various aspects - of the &man.ata.4; driver.</para> - - <para><filename>libcrypt</filename> now has support for Blowfish - password hashing. &merged;</para> - - <para>The functions from <filename>libposix1e</filename> have been - integrated into <filename>libc</filename>.</para> - - <para>&man.vidcontrol.1; now allows the user to omit the font size - specification when loading a font, and has some better - error-handling. &merged;</para> - - <para>&man.vidcontrol.1; now supports a <option>-p</option> to - take a snapshot of a &man.syscons.4; video buffer. These - snapshots can be manipulated by some of the - <filename>scr2*</filename> utilities in the Ports - Collection. &merged;</para> - - <para>&man.vidcontrol.1; now supports a <option>-H</option> option - to clear the history buffer for a given tty.</para> - - <para>devinfo, a simple tool to print the device tree and resource usage by - devices, has been added.</para> - - <para>&man.fmtcheck.3;, a function for checking consistency of - format string arguments, has been added.</para> - - <para>&man.nl.1;, a line numbering filter program, has been added.</para> - - <para>&man.c89.1; has been converted from a shell script to a - binary executable, fixing some minor bugs. &merged;</para> - - <para>&man.pax.1; has received a number of enhancements, including - &man.cpio.1; functionality, &man.tar.1; compatability - enhancements, <option>-z</option> and <option>-Z</option> flags - for &man.gzip.1; and &man.compress.1; functionality, and a number - of bug fixes.</para> - - <para>Ukranian language support has been added to the &os; - console. &merged;</para> - - <para>The performance of the ELF dynamic linker &man.rtld.1; has - been improved. &merged;</para> - - <para>&man.fdread.1;, a program to read data from floppy disks, - has been added. It is a counterpart to &man.fdwrite.1; and is - designed to provide a means of recovering at least some data from - bad media, and to obviate for a complex invocation of - &man.dd.1;.</para> - - <para>&man.xargs.1; now supports a <option>-J</option> - <replaceable>replstr</replaceable> option that allows the user to - tell &man.xargs.1; to insert the data read from standard input at - a specific point in the command line arguments rather than at the - end.</para> - - <para>&man.apmd.8; now supports monitoring of the battery state via the - <literal>apm_battery</literal> configuration directive.</para> - - <para>&man.telnet.1; now does autologin and encryption by default; - a new <option>-y</option> option turns off encryption.</para> - - <para>&man.telnet.1; now supports a <option>-u</option> flag to - allow connections to UNIX-domain (<literal>AF_UNIX</literal>) - sockets. &merged;</para> - - <para>The default stripe size in &man.vinum.8; has been changed - from 256KB to 279KB, to spread out superblocks more evenly between - stripes.</para> - - <para>&man.chown.8; now correctly follows symbolic links named as - command line arguments if run without <option>-R</option>.</para> - - <para>&man.chown.8; no longer takes <literal>.</literal> as a - user/group delimeter. This change was made to support usernames - containing a <literal>.</literal>.</para> - - <para>&man.chmod.1; now supports a <option>-h</option> for - changing the mode of a symbolic link.</para> - - <para>&man.install.1; has a number of new features, including the - <option>-b</option> and <option>-B</option> options for backing up - existing target files and the <option>-S</option> option for - <quote>safe</quote> (atomic copy) operation. The - <option>-c</option> (copy) flag is now the default, and the - <option>-D</option> (debugging) flag has been withdrawn.</para> - - <para>&man.whois.1; now directs queries for IP addresses to - ARIN.</para> - - <para>A new utility &man.diskcheckd.8; has been added; it is a - daemon which runs in the background, reading entire disks to find - any read errors on those disks. Its behavior at startup time can - be controlled by the <varname>diskcheckd_enable</varname> variable - in &man.rc.conf.5;.</para> - - <para>&man.fmt.1; has been rewritten; the rewrite fixes a number - of bugs compared to its prior behavior.</para> - - <para>&man.df.1; now takes a <option>-l</option> option to only - display information about locally-mounted filesystems.</para> - - <para>The syntax of &man.inetd.8;'s support for &man.faithd.8; is - now compatable with that of other BSDs. &merged;</para> - - <para>The <literal>ident</literal> protocol support in &man.inetd.8; has - been cleaned up and updated.</para> - - <sect3> - <title>Contributed Software</title> - - <para><application>bc</application> has been updated from 1.04 to - 1.06. &merged;</para> - - <para>The ISC library from the <application>BIND</application> - distribution is now built as - <filename>libisc</filename>. &merged;</para> - - <para><application>Binutils</application> have been upgraded to - 2.11.0. &merged;</para> - - <para><application>cvs</application> has been updated to - 1.11. &merged;</para> - - <para>The &man.ee.1; <application>Easy Editor</application> has - been updated to 1.4.2.</para> - - <para>&man.file.1; has been contribify-ed, and updated to version - 3.35.</para> - - <para>&man.awk.1;, in the form of - <application>gawk</application>, has been upgraded from 3.0.4 to 3.0.6. - This fixes a number of non-critical bugs and includes a few - performance tweaks. &merged;</para> - - <para><application>gcc</application> has been updated to 2.95.3. &merged;</para> - - <para>&man.gcc.1; now uses a unified <filename>libgcc</filename> - rather than a separate one for threaded and non-threaded programs. - <filename>/usr/lib/libgcc_r.a</filename> can be removed. - &merged;</para> - - <para>&man.gcc.1; now supports the environment variable - <varname>GCC_OPTIONS</varname>, which can hold a set of default - options for <application>GCC</application>.</para> - - <para><application>GNATS</application> has been updated to - 3.113.</para> - - <para><application>gperf</application> has been updated to 2.7.2.</para> - - <para><application>groff</application> and its related utilities - have been updated to FSF version 1.17. This import brings in a - new &man.mdoc.7; macro package (sometimes referred to as - <literal>mdocNG</literal>), which removes many of the - limitations of its predecessor. &merged;</para> - - <para><application>Heimdal</application> has been updated to - 0.3e. &merged;</para> - - <para>The <application>ISC DHCP</application> client has been - updated to 2.0pl5. &merged;</para> - - <para><application>Kerberos IV</application> has been updated to - 1.0.5. &merged;</para> - - <para>The &man.more.1; command has been replaced by &man.less.1;, - although it can still be run as - <command>more</command>. <application>less</application> has - been imported at 3.5.8. &merged;</para> - - <para><application>libpcap</application> has been updated to - 0.6.2.</para> - - <para><application>libreadline</application> has been upgraded to - 4.2.</para> - - <para><application>Linux-PAM</application> has been updated to - 0.75. &merged;</para> - - <para>A number of new <application>Linux-PAM</application> modules - have been added, including: <filename>pam_ftp</filename>, - <filename>pam_krb5</filename>, - <filename>pam_nologin</filename>, - <filename>pam_rootok</filename>, - <filename>pam_securetty</filename>, - <filename>pam_wheel</filename>. - - <para><application>ncurses</application> has been updated to - 5.2-20010512.</para> - - <para>The <application>OPIE</application> one-time-password suite - has been updated to 2.32. &merged;</para> - - <para><application>Perl</application> has been updated to version - 5.6.0.</para> - - <para>&man.pim6dd.8; and &man.pim6sd.8; have been removed due to - restrictive licensing conditions. These programs are available - in the ports collection as <filename>net/pim6dd</filename> and - <filename>net/pim6dd</filename>. &merged;</para> - - <para>&man.routed.8; has been updated to version 2.22. &merged;</para> - - <para><application>tcpdump</application> has been updated to - 3.6.2.</para> - - <para>The &man.csh.1; shell has been replaced by &man.tcsh.1;, - although it can still be run as <command>csh</command>. - <application>tcsh</application> has been updated to version - 6.10. &merged;</para> - - <para>&man.traceroute.8; now takes its default maximum TTL value - from the <varname>net.inet.ip.ttl</varname> sysctl - variable.</para> - - <sect4> - <title>OpenSSH</title> - - <para><application>OpenSSH</application> has been upgraded to - 2.1.0, which provides support for the SSH2 protocol, including DSA - keys. Therefore, <application>OpenSSH</application> users in the - US no longer need to rely on the restrictively-licensed - RSAREF toolkit which is required to - handle RSA keys. <application>OpenSSH</application> 2.1 interoperates well with other SSH2 - clients and servers, including the <filename>ssh2</filename> port. - See the <ulink url="http://www.openssh.com/">OpenSSH Web - site</ulink> for more details. &merged;</para> - - <para><application>OpenSSH</application> can now authenticate - using OPIE passwords in SSH1 mode. Support is not yet available - in SSH2 mode. &merged;</para> - - <para><application>OpenSSH</application> has been upgraded to - 2.2.0. &man.ssh-add.1; and &man.ssh-agent.1; can now handle DSA - keys. A server for sftp, interoperable with ssh.com - clients and others has been added. &man.scp.1; can now handle - files larger than 2 GBytes. Interoperability with other SSH2 - clients/servers has been improved. A new feature to limit the - number of outstanding unauthenticated ssh connections in - &man.sshd.8; has been added. &merged;</para> - - <para><application>OpenSSH</application> has been upgraded to - 2.3.0. This version adds support for the Rijndael encryption - algorithm. &merged;</para> - - <para><application>PAM</application> support for - <application>OpenSSH</application> has been added.</para> - - <para>A long-standing bug in <application>OpenSSH</application>, - which sometimes resulted in a dropped session when an - X11-forwarded client was closed, was fixed.</para> - - <para><application>Kerberos</application> compatability has been - added to <application>OpenSSH</application>. &merged;</para> - - <para><application>OpenSSH</application> has been modified to be - more resistant to traffic analysis by requiring that - <quote>non-echoed</quote> characters are still echoed back in a - null packet, as well as by padding passwords sent so as not to - hint at password lengths. &merged;</para> - - <para>&man.sshd.8; is now enabled by default on new - installs. &merged;</para> - - <para>&man.sshd.8; <literal>X11Forwarding</literal> is now turned - on by default on the server (any risk is to the client, where it - is already disabled by default).</para> - - <para>In <filename>/etc/ssh/sshd_config</filename>, the - <literal>ConnectionsPerPeriod</literal> parameter has been - deprecated in favor of <literal>MaxStartups</literal>.</para> - - <para><application>OpenSSH</application> now has a - <literal>VersionAddendum</literal> configuration setting for - &man.sshd.8; to allow changing the part of the - <application>OpenSSH</application> version string after the - main version number.</para> - - <para><application>OpenSSH</application> has been updated to - version 2.9, which adds two new programs, &man.sftp.1; and - &man.ssh-keyscan.1;. Among the various enhancements: The - default protocol is now v2, rekeying of existing SSH sessions - is now supported, and an experimental - <application>SOCKS4</application> proxy has been added to - &man.ssh.1;.</para> - </sect4> - - <sect4> - <title>OpenSSL</title> - - <para><application>OpenSSL</application> has been upgraded to - 0.9.6a.</para> - - <para><application>OpenSSL</application> now has support for - machine-dependent ASM optimizations, activated by the new - <varname>MACHINE_CPU</varname> and/or <varname>CPUTYPE</varname> - <filename>make.conf</filename> variables. &merged;</para> - </sect4> - - <sect4> - <title>sendmail</title> - - <para><application>sendmail</application> has been upgraded from - version 8.9.3 to version 8.11.4. Important changes include: new - default file locations (see - <filename>/usr/src/contrib/sendmail/cf/README</filename>); - &man.newaliases.1; is limited to <username>root</username> and - trusted users; STARTTLS encryption; and the MSA port (587) is - turned on by default. See - <filename>/usr/src/contrib/sendmail/RELEASE_NOTES</filename> for - more information. &merged;</para> - - <para>&man.mail.local.8; is no longer installed as a SUID binary. - If you are using a <filename>/etc/mail/sendmail.cf</filename> from - the default <filename>sendmail.cf</filename> included with &os; - any time after 3.1.0, you are fine. If you are using a - hand-configured <filename>sendmail.cf</filename> and - <command>mail.local</command> for delivery, check to make sure the - <literal>F=S</literal> flag is set on the - <literal>Mlocal</literal> line. Those with - <filename>.mc</filename> files who need to add the flag can do so - by adding the following line to their <filename>.mc</filename> - file and regenerating the <filename>sendmail.cf</filename> - file:</para> - - <programlisting>MODIFY_MAILER_FLAGS(`LOCAL',`+S')dnl</programlisting> - - <para>Note that <literal>FEATURE(`local_lmtp')</literal> already - does this. &merged;</para> - - <para>The default <filename>/etc/mail/sendmail.cf</filename> - disables the SMTP <literal>EXPN</literal> and - <literal>VRFY</literal> commands. &merged;</para> - - <para>&man.vacation.1; has been updated to use the version included with - <application>sendmail</application>. &merged;</para> - - <para>The <application>sendmail</application> configuration - building tools are installed in - <filename>/usr/share/sendmail/cf/</filename>. &merged;</para> - - <para>New <filename>make.conf</filename> options: - <varname>SENDMAIL_MC</varname> and - <varname>SENDMAIL_ADDITIONAL_MC</varname>. See - <filename>/etc/defaults/make.conf</filename> for more - information. &merged;</para> - - <para><filename>/etc/mail/Makefile</filename> now supports: the - new <varname>SENDMAIL_MC</varname> <filename>make.conf</filename> - option; the ability to build <filename>.cf</filename> files from - <filename>.mc</filename> files; generalized map rebuilding; - rebuilding the aliases file; and the ability to stop, start, and - restart <application>sendmail</application>. &merged;</para> - </sect4> - </sect3> - - <sect3> - <title>Ports/Packages Collection</title> - - <para>Version numbers of installed packages have a new - (backward-compatible) syntax, which supports the - <varname>PORTREVISION</varname> and <varname>PORTEPOCH</varname> - variables in Ports Collection <filename>Makefile</filename>s. - These changes help keep track of changes in the ports collection - entries such as security patches or &os;-specific updates, which - aren't reflected in the original, third-party software - distributions. &man.pkg.version.1; can now compare these - new-style version numbers. &merged;</para> - - <para>To improve performance and disk utilization, the <quote>ports - skeletons</quote> in the FreeBSD Ports Collection have been restructured. - Installed ports and packages should not be affected. &merged;</para> - - <para>All packages and ports now contain an <quote>origin</quote> - directive, which makes it easier for programs such as - &man.pkg.version.1; to determine the directory from which a - package was built. &merged;</para> - - <para>&man.pkg.update.1;, a utility to update installed packages - and update their dependencies, has been added. &merged;</para> - - <para>&man.pkg.info.1; now supports globbing against names of - installed packages. The <option>-G</option> option disables this - behavior, and the <option>-x</option> option causes regular - expression matching instead of shell globbing. &merged;</para> - - <para>&man.pkg.info.1; can now accept a <option>-g</option> flag for - verifying an installed package against its recorded checksums (to - see if it's been modified post-installation). Naturally, this - mechanism is only as secure as the contents of - <filename>/var/db/pkg</filename> if it's to be used for auditing - purposes. &merged;</para> - - <para>&man.pkg.create.1; and &man.pkg.add.1; can now work with - packages that have been compressed using - &man.bzip2.1;. &man.pkg.add.1; will use the PACKAGEROOT - environment variable to determine a mirror site for new - packages. &merged;</para> - - <para>&man.pkg.create.1; now records dependencies in dependency - order rather than in the order specified on the command line. - This improves the functioning of <command>pkg_add - -r</command>. &merged;</para> - - <para>&man.pkg.version.1; now has a version number comparison - routine that corresponds to the Porters Handbook. It also has a - <option>-t</option> option for testing address comparisons. - &merged;</para> - - <para>When requested to delete multiple packages, - &man.pkg.delete.1; will now attempt to remove them in dependency - order rather than the order specified on the command - line. &merged;</para> - - <para>&man.pkg.delete.1; now can perform glob/regexp matching of - package names. In addition, it supports a <option>-a</option> - option for removing all packages and a <option>-i</option> option - for &man.rm.1;-style interactive confirmation. &merged;</para> - - <para>&man.pkg.sign.1; and &man.pkg.check.1; have been added to - digitally sign and verify the signatures on binary package - files. &merged;</para> - - <para><application>BSDPAN</application>, a collection of modules - that provides tighter integration of - <application>Perl</application> into the &os; Ports - Collection, has been added.</para> - </sect3> - </sect2> -</sect1> diff --git a/release/doc/en_US.ISO_8859-1/relnotes/common/relnotes.ent b/release/doc/en_US.ISO_8859-1/relnotes/common/relnotes.ent deleted file mode 100644 index 1e8a22d..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/common/relnotes.ent +++ /dev/null @@ -1,16 +0,0 @@ -<!-- -*- sgml -*- --> - -<!-- $FreeBSD$ --> - -<!-- Text constants which probably don't need to be changed.--> - -<!-- The marker for MFCs. --> -<!ENTITY merged "[MERGED]"> - -<!-- Files to be included --> - -<!ENTITY artheader SYSTEM "../common/artheader.sgml"> -<!ENTITY sect.intro SYSTEM "../common/intro.sgml"> -<!ENTITY sect.new SYSTEM "../common/new.sgml"> -<!ENTITY sect.upgrading SYSTEM "../common/upgrading.sgml"> - diff --git a/release/doc/en_US.ISO_8859-1/relnotes/common/upgrading.sgml b/release/doc/en_US.ISO_8859-1/relnotes/common/upgrading.sgml deleted file mode 100644 index 2d6d426..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/common/upgrading.sgml +++ /dev/null @@ -1,41 +0,0 @@ -<!-- - $FreeBSD$ - - Summary information on upgrading FreeBSD. This comes from - the similarly-named section of RELNOTES.TXT. ---> - -<sect1> - <title>Upgrading from previous releases of &os;</title> - - <para>If you're upgrading from a previous release of &os;, - most likely it's 4.X and there may be some issues affecting you, - depending of course on your chosen method of upgrading. There - are two popular ways of upgrading &os; distributions:</para> - - <para> - <itemizedlist> - <listitem> - <para>Using sources, via <filename>/usr/src</filename></para> - </listitem> - <listitem> - <para>Using the binary upgrade option of &man.sysinstall.8;.</para> - </listitem> - </itemizedlist> - </para> - - <para>Please read the <filename>UPGRADE.TXT</filename> file for more - information, preferably <emphasis>before</emphasis> beginning an - upgrade. If you are upgrading from source, please be sure to read - <filename>/usr/src/UPDATING</filename> as well.</para> - - <para>Finally, if you want to use one of various means to track the - -STABLE or -CURRENT branches of &os;, please be sure to consult the - <ulink - url="http://www.freebsd.org/handbook/current-stable.html"><quote>-CURRENT - vs. -STABLE</quote></ulink> section of the <ulink - url="http://www.freebsd.org/handbook/">FreeBSD - Handbook</ulink>.</para> - -</sect1> - diff --git a/release/doc/en_US.ISO_8859-1/relnotes/i386/Makefile b/release/doc/en_US.ISO_8859-1/relnotes/i386/Makefile deleted file mode 100644 index 2c0390b..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/i386/Makefile +++ /dev/null @@ -1,18 +0,0 @@ -# $FreeBSD$ - -RELN_ROOT?= ${.CURDIR}/../../.. - -DOC?= article -FORMATS?= html -INSTALL_COMPRESSED?= gz -INSTALL_ONLY_COMPRESSED?= - -# SGML content -SRCS+= article.sgml -SRCS+= ../common/relnotes.ent -SRCS+= ../common/artheader.sgml -SRCS+= ../common/new.sgml -SRCS+= ../common/upgrading.sgml - -.include "${RELN_ROOT}/share/mk/doc.relnotes.mk" -.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/release/doc/en_US.ISO_8859-1/relnotes/i386/article.sgml b/release/doc/en_US.ISO_8859-1/relnotes/i386/article.sgml deleted file mode 100644 index acf3463..0000000 --- a/release/doc/en_US.ISO_8859-1/relnotes/i386/article.sgml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ -<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> -%man; -<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> -%authors; -<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> -%mlists; -<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> -%release; -<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections; - -<!-- Architecture-specific customization --> - -<!ENTITY arch "i386"> - -]> - -<article> - &artheader; - §.intro; - §.new; - §.upgrading; -</article> diff --git a/release/doc/en_US.ISO_8859-1/share/sgml/release.dsl b/release/doc/en_US.ISO_8859-1/share/sgml/release.dsl deleted file mode 100644 index 2838743..0000000 --- a/release/doc/en_US.ISO_8859-1/share/sgml/release.dsl +++ /dev/null @@ -1,72 +0,0 @@ -<!-- $FreeBSD$ --> - -<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [ -<!ENTITY release.dsl PUBLIC "-//FreeBSD//DOCUMENT Release Notes DocBook Language Neutral Stylesheet//EN" CDATA DSSSL> -<!ENTITY % output.html "IGNORE"> -<!ENTITY % output.print "IGNORE"> -]> - -<style-sheet> - <style-specification use="docbook"> - <style-specification-body> - - <![ %output.html; [ - (define ($email-footer$) - (make sequence - (make element gi: "p" - attributes: (list (list "align" "center")) - (make element gi: "small" - (literal "This file, and other release-related documents, can be downloaded from ") - (create-link (list (list "HREF" (entity-text "release.url"))) - (literal (entity-text "release.url"))) - (literal "."))) - (make element gi: "p" - attributes: (list (list "align" "center")) - (make element gi: "small" - (literal "For questions about FreeBSD, read the ") - (create-link - (list (list "HREF" "http://www.FreeBSD.org/docs.html")) - (literal "documentation")) - (literal " before contacting <") - (create-link - (list (list "HREF" "mailto:questions@FreeBSD.org")) - (literal "questions@FreeBSD.org")) - (literal ">.") - (make element gi: "p" - attributes: (list (list "align" "center")) - (make element gi: "small" - (literal "All users of FreeBSD ") - (literal (entity-text "release.branch")) - (literal " should subscribe to the ") - (literal "<") - (create-link (list (list "HREF" "mailto:current@FreeBSD.org")) - (literal "current@FreeBSD.org")) - (literal "> mailing list."))) - - (make element gi: "p" - attributes: (list (list "align" "center")) - (literal "For questions about this documentation, e-mail <") - (create-link (list (list "HREF" "mailto:doc@FreeBSD.org")) - (literal "doc@FreeBSD.org")) - (literal ">.")))))) - - <!-- Convert " ... " to `` ... '' in the HTML output. --> - (element quote - (make sequence - (literal "``") - (process-children) - (literal "''"))) - - <!-- Generate links to HTML man pages --> - (define %refentry-xref-link% #t) - - <!-- Specify how to generate the man page link HREF --> - (define ($create-refentry-xref-link$ refentrytitle manvolnum) - (string-append "http://www.FreeBSD.org/cgi/man.cgi?query=" - refentrytitle "&" "sektion=" manvolnum)) - ]]> - </style-specification-body> - </style-specification> - - <external-specification id="docbook" document="release.dsl"> -</style-sheet> diff --git a/release/doc/share/mk/doc.relnotes.mk b/release/doc/share/mk/doc.relnotes.mk index 9231b73..8baf92f 100644 --- a/release/doc/share/mk/doc.relnotes.mk +++ b/release/doc/share/mk/doc.relnotes.mk @@ -6,8 +6,8 @@ DOC_PREFIX?= ${RELN_ROOT}/../../../doc EXTRA_CATALOGS+= ${RELN_ROOT}/share/sgml/catalog # Use the appropriate architecture-dependent RELNOTESng stylesheet -DSLHTML?= ${RELN_ROOT}/en_US.ISO_8859-1/share/sgml/release.dsl -DSLPRINT?= ${RELN_ROOT}/en_US.ISO_8859-1/share/sgml/release.dsl +DSLHTML?= ${RELN_ROOT}/en_US.ISO8859-1/share/sgml/release.dsl +DSLPRINT?= ${RELN_ROOT}/en_US.ISO8859-1/share/sgml/release.dsl # XXX using /release/doc as anchor! DESTDIR?= ${DOCDIR}/${.CURDIR:C/^.*\/release\/doc//} diff --git a/release/doc/share/sgml/catalog b/release/doc/share/sgml/catalog index f64bd6e..e456e67 100644 --- a/release/doc/share/sgml/catalog +++ b/release/doc/share/sgml/catalog @@ -10,6 +10,6 @@ PUBLIC "-//FreeBSD//DOCUMENT Release Notes DocBook Language Neutral Stylesheet// "release.dsl" PUBLIC "-//FreeBSD//DOCUMENT Release Notes DocBook Stylesheet//EN" - "../../en_US.ISO_8859-1/share/sgml/release.dsl" + "../../en_US.ISO8859-1/share/sgml/release.dsl" |
