Early Adopter's Guide to + FreeBSD 5.0-RELEASE

2 Supported processors and + motherboards

+

2.1 Overview

2.2 In general, what do you need + to run FreeBSD on an Alpha?

2.3 System-specific + information

+

2.3.1 AXPpci33 + (``NoName'')
2.3.2 Universal Desktop Box + (UDB or ``Multia'')
2.3.3 Personal Workstation + (``Miata'')
2.3.4 Evaluation Board 64 + family
2.3.5 Evaluation Board 164 + (``EB164, PC164, PC164LX, PC164SX'') + family
2.3.6 AlphaStation 200 + (``Mustang'') and 400 (``Avanti'') + series
2.3.7 AlphaStation 500 and + 600 (``Alcor'' & ``Maverick'' for EV5, + ``Bret'' for EV56)
2.3.8 AlphaServer 1000 + (``Mikasa''), 1000A (``Noritake'') and + 800(``Corelle'')
2.3.9 DS10/VS10/XP900 + (``Webbrick'') / XP1000 (``Monet'') / DS10L + (``Slate'')
2.3.10 DS20/DS20E + (``Goldrush'')
2.3.11 AlphaPC 264DP / + UP2000
2.3.12 AlphaServer 2000 + (``DemiSable''), 2100 (``Sable''), 2100A + (``Lynx'')
2.3.13 AlphaServer 4x00 + (``Rawhide'')
2.3.14 AlphaServer 1200 + (``Tincup'') and AlphaStation 1200 + (``DaVinci'')
2.3.15 AlphaServer 8200 + and 8400 (``TurboLaser'')
2.3.16 Alpha Processor + Inc. UP1000
2.3.17 Alpha Processor + Inc. UP1100
2.3.18 Alpha Processor + Inc. CS20, Compaq DS20L

+

2.4 Supported Hardware + Overview

2.5 Acknowledgments

+

+

3.1 Disk Controllers
3.2 Ethernet + Interfaces
3.3 FDDI Interfaces
3.4 ATM Interfaces
3.5 Wireless Network + Interfaces
3.6 Miscellaneous + Networks
3.7 ISDN Interfaces
3.8 Serial Interfaces
3.9 Audio Devices
3.10 Camera and Video Capture + Devices
3.11 USB Devices
3.12 IEEE 1394 (Firewire) + Devices
3.13 Cryptographic + Accelerators
3.14 Miscellaneous

+

+ +

+

+ +

1 Introduction

+ +

This document contains the hardware compatibility notes + for FreeBSD 5.0-DP2 on the Alpha/AXP hardware platform + (also referred to as FreeBSD/alpha 5.0-DP2). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.

+ +

+

+
Note: This document includes information + specific to the Alpha/AXP hardware platform. Versions + of the hardware compatibility notes for other + architectures will differ in some details.
+

+

+ +

+

+ +

2 Supported processors + and motherboards

+ Maintained + by Wilko Bulte. + +

Additions, corrections and constructive criticism are + invited. In particular, information on system quirks is + more than welcome.

+ +

+

+ +

2.1 Overview

+ +

This document tries to provide a starting point for + those who want to run FreeBSD 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.

+ +

The information is structured as follows:

+ +

+
general hardware requirements to run FreeBSD on + alpha;
+
+
system specific information for each of the + systems/boards supported by FreeBSD;
+
+
information on expansion boards for FreeBSD, + including things that differ from what is in the + generic supported hardware list.
+

+ +

+

+
Note: 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.
+

+

+ +

+

+
Note: SRM commands will be in UPPER CASE. Lower case input + is also acceptable to SRM. Upper case is used for + clarity.
+

+

+ +

+

+
Note: Compaq has put information on the Web + for Linux developers that is also very useful for + FreeBSD users. Please check at Linux Alpha Power tools.
+

+

+ +

+

+ +

2.2 In general, what do + you need to run FreeBSD on an Alpha?

+ +

Obviously you will need an Alpha machine that FreeBSD + 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 GENERIC kernel at unknown hardware + is almost guaranteed to fail miserably.

+ +

For a machine even to be considered for FreeBSD 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 + FreeBSD 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.

+ +

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 no FreeBSD (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.

+ +

Known non-SRM machines are:

+ +

+
Digital XL series
+
+
Digital XLT series
+
+
Samsung PC164UX (``Ruffian'')
+
+
Samsung 164B
+

+ +

Machines that have SRM but are not supported by + FreeBSD are:

+ +

+
DECpc 150 (``Jensen'')
+
+
DEC 2000/300 (``Jensen'')
+
+
DEC 2000/500 (``Culzean'')
+
+
AXPvme series (``Medulla'')
+

+ +

To complicate things a bit further: Digital used to + have so called ``white-box'' Alpha machines destined as + NT-only and ``blue-box'' Alpha machines destined for + OpenVMS and Digital Unix. These names are based on the + color of the cabinets, ``FrostWhite'' and ``TopGunBlue'' + respectively. Although you could put the SRM console + firmware on a whitebox, OpenVMS and Digital Unix will + refuse to boot on them. FreeBSD 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.

+ +

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 FreeBSD (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 FreeBSD and NetBSD web sites.

+ +

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.

+ +

The problem might bite those who have machines that + started their lives as WindowsNT boxes. The ARC or + AlphaBIOS knows about other 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.

+ +

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.

+ +

FreeBSD 4.0 and later can be booted from the + distribution CDROM. Earlier versions needed booting from + a 2 disk floppy set.

+ +

In order to be bootable the root partition (partition + a) must be at offset 0 of the disk drive. This means you + have to use the installer's partitioning menu and start + with assigning partition a at offset 0 to the root + partition. Subsequently layout the rest of the partitions + to your liking. If you do not adhere to this rule the + install will proceed just fine, but the system will not + be bootable from the freshly installed disk.

+ +

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.

+ +

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.

+ +

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. + This can be + extremely confusing.

+ +

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.

+ +

Most PCI devices from the PC-world will also work in + FreeBSD PCI-based machines. Check the /sys/alpha/conf/GENERIC 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:

+

+    >>> SET PCI_PARITY OFF
+

+ +

This is not a FreeBSD problem, all operating systems + running on Alpha hardware will need this workaround.

+ +

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.

+ +

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, + EV68. 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 ``EV'' the more + desirable (read: faster / more modern).

+ +

For memory you want at least 32 Mbytes. I have had + FreeBSD 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.

+ +

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.

+ +

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.

+

+ +

+

+ +

2.3 System-specific + information

+ +

Below is an overview of the hardware that FreeBSD runs + on. This list will definitely grow, a look in /sys/alpha/conf/GENERIC can be + enlightening.

+ +

Alpha machines are often best known by their project + code name. Where known these are listed below in + parentheses.

+ +

+

+ +

2.3.1 AXPpci33 + (``NoName'')

+ +

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.

+ +

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.

+ +

Features:

+ +

+
21066 Alpha CPU at 166 MHz or 21066A CPU at + 233MHz. 21068 CPUs are also possible, but are even + slower.
+
+
on-board Bcache / L2 cache: 0, 256k or 1 Mbyte + (uses DIL chips)
+
+
PS/2 mouse & keyboard port OR 5pin DIN + keyboard (2 mainboard models)
+
+
memory:
+ +
- +
  bus width: 64 bits
  +
- +
  PS/2 style 72 pin 36 bit Fast Page Mode + SIMMs
  +
- +
  70ns or better
  +
- +
  installed in pairs of 2
  +
- +
  4 SIMM sockets
  +
- +
  uses ECC
  +
+
+
512kB Flash ROM for the console code.
+
+
2 16550A serial ports
+
+
1 parallel port
+
+
floppy interface
+
+
1 embedded IDE interface
+
+
expansion:
+ +
- +
  3 32 bit PCI slots (1 shared with ISA)
  +
- +
  5 ISA slots (1 shared with PCI)
  +
+
+
embedded Fast SCSI using a Symbios 53C810 + chip
+

+ +

NoNames can either have SRM or 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.

+ +

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.

+ +

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.

+ +

The IDE interface is supported by FreeBSD and + requires a line in the kernel configuration file as + follows:

+

+    device ata
+

+ +

The ATA interface uses irq 14.

+ +

The SRM console unfortunately cannot boot + from IDE disks. This means you will have to use a SCSI + disk as the boot device.

+ +

The NoName is somewhat stubborn when it comes to + serial consoles. It needs

+

+    >>> SET CONSOLE SERIAL
+

+ +

before it goes 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

+

+    >>> SET CONSOLE GRAPHICS
+

+ +

at the serial console.

+ +

There have been reports that you sometimes need to + press Control-Alt-Del to capture + the SRM's attention. I have never seen this myself, but + it is worth trying if you are greeted by a blank screen + after powerup.

+ +

Make sure you use true 36 bit SIMMs, and only FPM + (Fast Page Mode) DRAM. EDO DRAM or SIMMs with fake + parity will + not work. The board uses the 4 extra bits + for ECC. 33 bit FPM SIMMs will for the same reason not + work.

+ +

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 ``DIN-plug''-variant should work + OK for FreeBSD.

+ +

The OEM manual is recommended + reading.

+ +

The kernel configuration file for a NoName kernel + must contain:

+

+    options    DEC_AXPPCI_33           
+    cpu EV4
+

+

+ +

+

+ +

2.3.2 Universal + Desktop Box (UDB or ``Multia'')

+ +

+

+
Note: Multia can be either Intel or Alpha + CPU based. We assume Alpha based ones here for + obvious reasons.
+

+

+ +

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.

+ +

Features:

+ +

+
21066 Alpha CPU at 166 MHz or 21066A CPU at + 233MHz
+
+
on-board Bcache / L2 cache: COAST-like 256 kByte + cache module; 233MHz models have 512kByte of cache; + 166MHz models have soldered-on 256kB caches
+
+
PS/2 mouse & keyboard port
+
+
memory:
+ +
- +
  bus width: 64 bits
  +
- +
  PS/2 style 72 pin 36 bit Fast Page Mode + SIMMs
  +
- +
  70ns or better
  +
- +
  SIMMs are installed in pairs of 2
  +
- +
  4 SIMM sockets
  +
- +
  uses ECC
  +
+
+
2 16550A serial ports
+
+
1 parallel port
+
+
floppy interface
+
+
Intel 82378ZB PCI to ISA bridge
+
+
1 embedded 21040 based 10Mbit Ethernet, AUI and + 10base2 connector
+
+
expansion:
+ +
- +
  1 32 bit PCI slot
  +
- +
  2 PCMCIA slots
  +
+
+
on-board Crystal CS4231 or AD1848 sound chip
+
+
embedded Fast SCSI, using a Symbios 53C810[A] + chip on the PCI riser card
+

+ +

Multia has enough Flash ROM to store both SRM and + ARC code at the same time and allow software selection + of one of them.

+ +

The embeded TGA video adapter is not currently + usable as a FreeBSD console. You will need to use a + serial console.

+ +

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 not a + recommended upgrade due to the limited power rating of + the power supply and the extremely marginal cooling of + the system box.

+ +

Multia also has 2 PCMCIA expansion slots. These are + currently not supported by FreeBSD.

+ +

The CPU might or might not be socketed, check this + before considering CPU upgrade hacks. The low-end + Multias have a soldered-in CPU.

+ +

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.

+ +

Although the Multia SRM supports booting from floppy + this can be problematic. Typically the errors look + like:

+

+    *** Soft Error - Error #10 - FDC: Data overrun or underrun
+

+ +

This is not a FreeBSD problem, it is a SRM problem. + The best available workaround to install FreeBSD is to + boot from a SCSI CDROM.

+ +

There have been reports that you sometimes need to + press Control-Alt-Del to capture + the SRM's attention. I have never seen this myself, but + it is worth trying when you are greeted by a blank + screen after powerup.

+ +

Sound works fine using + pcm(4) driver and a + line in the kernel configuration file as follows for + the Crystal CS4231 chip:

+

+    device pcm
+

+ +

The sound device lives at port 0x530, and uses irq 9 + along with drq 3. You also need to specify flags 0x15 + in the device.hints file.

+ +

I have not yet been successful in getting my Multia + with the AD1848 to play any sound.

+ +

While verifying playback I was reminded of the lack + of CPU power of the 166MHz CPU. MP3 only plays + acceptable using 22kHz down-sampling.

+ +

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 (``pizza + style''). 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 NetBSD Web site for help in reviving it.

+ +

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:

+

+    device ata
+

+ +

The ATA interface uses IRQ 14.

+ +

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 boot disk.

+ +

In case you want to change the internal hard drive: + the internal flat cable running from the PCI riser + board to the 2.5" 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.

+ +

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.

+ +

The kernel configuration file for a Multia kernel + must contain:

+

+    options    DEC_AXPPCI_33
+    cpu EV4
+

+ +

Recommended reading on Multia can be found at http://www.netbsd.org/Ports/alpha/multiafaq.html + or http://www.brouhaha.com/~eric/computers/udb.html.

+

+ +

+

+ +

2.3.3 Personal + Workstation (``Miata'')

+ +

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.

+ +

System designations look like ``Personal Workstation + 433a''. 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 ``a''). Systems designated + from day 1 to run Tru64 Unix or OpenVMS will sport + ``433au''. 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].

+ +

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.

+ +

Features:

+ +

+
21164A EV56 Alpha CPU at 433, 500 or 600MHz
+
+
21174 Core Logic (``Pyxis'') chip set
+
+
on-board Bcache / L3 cache: 0, 2 or 4 Mbytes + (uses a cache module)
+
+
memory:
+ +
- +
  bus width: 128 bits wide, ECC protected
  +
- +
  unbuffered 72 bit wide SDRAMs DIMMs, + installed in pairs of 2
  +
- +
  6 DIMM sockets
  +
- +
  maximum memory 1.5 GBytes
  +
+
+
on-board Fast Ethernet:
+ +
- +
  MX5 uses a 21142 or 21143 Ethernet chip, + dependent on the version of the PCI riser + card
  +
- +
  MiataGL has a 21143 chip
  +
- +
  the bulkhead can be 10/100 Mbit UTP, or 10 + Mbit UTP/BNC
  +
+
+
2 on-board [E]IDE disk interfaces, based on the + CMD646 (MX5) or the Cypress 82C693 (MiataGL)
+
+
1 Ultra-Wide SCSI Qlogic 1040 [MiataGL only]
+
+
2 64-bit PCI slots
+
+
3 32-bit PCI slots (behind a DEC PCI-PCI bridge + chip)
+
+
3 ISA slots (physically shared with the 32 bit + PCI slots, via an Intel 82378IB PCI to ISA bridge + chip)
+
+
2 16550A serial port
+
+
1 parallel port
+
+
PS/2 keyboard & mouse port
+
+
USB interface [MiataGL only]
+
+
embedded sound based on an ESS1888 chip
+

+ +

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.

+ +

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 ``known good'' + to the SRM are allowed to be used in the 64bit + slots.

+ +

If you want to fool the SRM you can type set pci_device_override at the + SRM prompt. Just don't complain if your data + mysteriously gets mangled.

+ +

The complete command is:

+

+    >>> SET PCI_DEVICE_OVERRIDE <vendor_id><device_id>
+

+ +

For example:

+

+    >>> SET PCI_DEVICE_OVERRIDE 88c15333
+

+ +

The most radical approach is to use:

+

+    >>> SET PCI_DEVICE_OVERRIDE -1
+

+ +

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: Do this on your own risk..
+

+

+ +

The FreeBSD kernel reports it when it sees a buggy + Pyxis chip:

+

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

+ +

A MiataGL probes as:

+

+    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
+

+ +

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.

+ +

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 FreeBSD kernel by the way.

+ +

The Miata SRM can boot from IDE CDROM drives. IDE + hard disk boot is known to work for both MiataGL and + MX5 disks, so you can root FreeBSD 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.

+ +

Miata MX5s generally use Qlogic 1040 based SCSI + adapters. These are bootable by the SRM console. Note + that Adaptec cards are not bootable by the Miata SRM + console.

+ +

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 same chip as + the MiataGL. All in all there is a lot of + variation.

+ +

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 ``before'' the + bridge, in one of the 64 bit PCI slots.

+ +

Both MX5 and MiataGL have an on-board sound chip, an + ESS1888. It emulates a SoundBlaster and can be enabled + by putting

+

+    device pcm
+    device  sbc
+

+ +

in your kernel configuration file:

+ +

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.

+ +

Installing a 2Mb cache module achieves, apart from a + 10-15% speed increase (based on buildworld elapsed + time), a decrease 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.

+ +

Although the hardware allows you to install up to + 1.5Gbyte of memory, FreeBSD is limited to 1Gbyte + because the DMA code does not correctly handle memory + above 1Gbyte.

+ +

Moving to a faster CPU is quite simple, swap out the + CPU chip and set the clock multiplier dipswitch to the + speed of the new CPU.

+ +

If you experience SRM errors like

+

+    ERROR: scancode 0xa3 not supported on PCXAL
+

+ +

after halting FreeBSD 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 http://www.compaq.com/ This SRM problem is + fixed on both Miata MX5 and Miata GL.

+ +

USB is supported by FreeBSD 4.1 and later.

+ +

Disconnect the power cord before dismantling the + machine, the soft-power switch keeps part of the logic + powered even when the machine is switched + off.

+ +

The kernel configuration file for a Miata kernel + must contain:

+

+    options    DEC_ST550               
+    cpu EV5
+

+

+ +

+

+ +

2.3.4 Evaluation + Board 64 family

+ +

In its attempts to popularize the Alpha CPU DEC + produced a number of so called Evaluation Boards. + Members of this family are EB64, EB64+, AlphaPC64 + (codename ``Cabriolet''). A non-DEC member of this + family is the Aspen Alpine. The EB64 family of + evaluation boards has the following feature set:

+ +

+
21064 or 21064A CPU, 150 to 275 MHz
+
+
memory:
+ +
- +
  memory buswidth: 128 bit
  +
- +
  PS/2 style 72 pin 33 bit Fast Page Mode + SIMMs
  +
- +
  70ns or better
  +
- +
  installed in sets of 4
  +
- +
  8 SIMM sockets
  +
- +
  uses parity memory
  +
+
+
Bcache / L2 cache: 0, 512 kByte, 1 Mbyte or 2 + Mbytes
+
+
21072 (``APECS'') chip set
+
+
Intel 82378ZB PCI to ISA bridge chip + (``Saturn'')
+
+
dual 16550A serial ports
+
+
parallel printer port
+
+
Symbios 53C810 Fast-SCSI (not on AlphaPC64)
+
+
IDE interface (only on AlphaPC64)
+
+
embedded 10 Mbit Ethernet (not on AlphaPC64)
+
+
2 PCI slots (4 slots on AlphaPC64)
+
+
3 ISA slots
+

+ +

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.

+ +

36 bits SIMMs work fine, 3 bits simply remain + unused. Note the systems use Fast Page Mode memory, not + EDO memory.

+ +

The EB64+ 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.

+ +

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 + FreeBSD 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 FreeBSD 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.

+ +

AlphaPC64 boards generally come with ARC console + firmware. SRM console code can be loaded from floppy + into the Flash ROM.

+ +

The IDE interface of the AlphaPC64 is not bootable + from the SRM console.

+ +

Note that the boards require a power supply that + supplies 3.3 Volts for the CPU.

+ +

For the EB64 family machines the kernel config file + must contain:

+

+    options    DEC_EB64PLUS            
+    cpu EV4
+

+

+ +

+

+ +

2.3.5 Evaluation + Board 164 (``EB164, PC164, PC164LX, PC164SX'') + family

+ +

EB164 is a newer design evaluation board, based on + the 21164A CPU. This design has been used to ``spin + off'' 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.

+ +

+
21164A, multiple speed variants [EB164, PC164, + PC164LX]
+
+
21164PC [only on PC164SX]
+
+
21174 (Alcor) chip set
+
+
Bcache / L3 cache: EB164 uses special + cache-SIMMs
+
+
memory bus: 128 bit / 256 bit
+
+
memory:
+ +
- +
  PS/2 style SIMMs in sets of 4 or 8
  +
- +
  36 bit, Fast Page Mode, uses ECC, [EB164 / + PC164]
  +
- +
  SDRAM DIMMs in sets of 2, uses ECC [PC164SX + / PC164LX]
  +
+
+
2 16550A serial ports
+
+
PS/2 style keyboard & mouse
+
+
floppy controller
+
+
parallel port
+
+
32 bits PCI
+
+
64 bits PCI [some models]
+
+
ISA slots via an Intel 82378ZB PCI to ISA bridge + chip
+

+ +

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. For the + AlphaPC164 you can have a maximum of 1Gbyte of RAM, + using 8 128Mbyte SIMMs. The manual indicates the + maximum is 512 Mbyte.

+ +

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.

+ +

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, Symbios895 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.

+ +

164LX and 164SX with SRM firmware version 5.8 or + later can boot from Adaptec 2940-series adapters.

+ +

In summary: this family of machines is ``blessed'' + with a challenging compatibility as far as SCSI + adapters go.

+ +

On 164SX you can have a maximum of 1 Gbyte of RAM. 4 + regular 256MB PC133 ECC DIMMs are reported to work just + fine. Whether 512MB DIMMs will also work is currently + unknown.

+ +

PCI bridge chips are sometimes not appreciated by + the 164SX, they cause SRM errors and kernel panics in + those cases. This seems to depend on the fact if the + card is recognised, and therefore correctly + initialised, by the SRM console. The 164SX' onboard IDE + interface is quite slow, a Promise card gives a 3-4 + times speed improvement.

+ +

On PC164 the SRM sometimes seems to lose its + variable settings. ``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.'' One + sample error that was observed was:

+

+    ERROR: ISA table corrupt!
+

+ +

A sequence of a downgrade to SRM4.9, an

+

+    >>> ISACFG -INIT
+

+ +

followed by

+

+    >>> INIT
+

+ +

made the problem go away. Some PC164 owners report + they have never seen the problem.

+ +

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.

+ +

164LX can either have the SRM console code or the + AlphaBIOS code in its flash ROM because the flash ROM + is too small to hold both at the same time.

+ +

PC164 can boot from IDE disks assuming your SRM + version is recent enough.

+ +

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.

+ +

For the EB164 class machines the kernel config file + must contain:

+

+    options         DEC_EB164
+    cpu             EV5
+

+

+ +

+

+ +

2.3.6 AlphaStation + 200 (``Mustang'') and 400 (``Avanti'') series

+ +

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.

+ +

Features:

+ +

+
21064 or 21064A CPU at speeds of 166 up to 333 + MHz
+
+
DECchip 21071-AA core logic chip-set
+
+
Bcache / L2 cache: 512 Kbytes (200 and 400 + series) or 2048KBytes (250 series)
+
+
memory:
+ +
- +
  64 bit bus width
  +
- +
  8 to 384 MBytes of RAM
  +
- +
  70 ns or better Fast Page DRAM
  +
- +
  in three pairs (200 and 400 series)
  +
- +
  in two quads, so banks of four. (250 + series)
  +
- +
  the memory subsystem uses parity
  +
+
+
PS/2 keyboard and mouse port
+
+
two 16550 serial ports
+
+
parallel port
+
+
floppy disk interface
+
+
32 bit PCI expansion slots (3 for the + AS400-series, 2 for the AS200 & 250-series)
+
+
ISA expansion slots (4 for the AS400-series, 2 + for the AS200 & 250-series) (some ISA/PCI slots + are physically shared)
+
+
embedded 21040-based Ethernet (200 & 250 + series)
+
+
embedded Symbios 53c810 Fast SCSI-2 chip
+
+
Intel 82378IB (``Saturn'') PCI-ISA bridge + chip
+
+
graphics is embedded TGA or PCI VGA (model + dependent)
+
+
16 bit sound (on 200 & 250 series)
+

+ +

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.

+ +

The AS200 & AS250 sound hardware is reported to + work OK assuming you have the following line in your + kernel config file:

+

+    device pcm
+

+ +

The sound device uses port 0x530, IRQ 9 and drq 0. + You also need to specify flags 0x10011 in the device.hints file.

+ +

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.

+ +

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

+

+    >>> SET CONTROL_SCSI_TERM EXTERNAL.
+

+ +

If only internal SCSI devices are present use:

+

+    >>> SET CONTROL_SCSI_TERM INTERNAL
+

+ +

For the AlphaStation-[24][05]00 machines the kernel + config file must contain:

+

+    options    DEC_2100_A50
+    cpu EV4
+

+

+ +

+

+ +

2.3.7 AlphaStation + 500 and 600 (``Alcor'' & ``Maverick'' for EV5, + ``Bret'' for EV56)

+ +

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.

+ +

Features:

+ +

+
21164 EV5 CPU at 266, 300, 333, 366, 400, 433, + 466, or 500 MHz (AS500) or at 266, 300 or 333 MHz + (AS600)
+
+
21171 or 21172 (Alcor) core logic chip-set
+
+
Cache:
+ +
- +
  2 or 4 Mb L3 / Bcache (AS600 at 266 MHz)
  +
- +
  4 Mb L3 / Bcache (AS600 at 300 MHz)
  +
- +
  2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz + version only)
  +
- +
  2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM + slots)
  +
+
+
memory buswidth: 256 bits
+
+
AS500 memory:
+ +
- +
  industry standard 72 bit wide buffered + DIMMs
  +
- +
  8 DIMM slots
  +
- +
  installed in sets of 4
  +
- +
  maximum memory is 1 GB (512 Mb max on 333 + MHz CPUs)
  +
- +
  uses ECC
  +
+
+
AS600 memory:
+ +
- +
  industry standard 36 bit Fast Page Mode + SIMMs
  +
- +
  32 SIMM slots
  +
- +
  installed in sets of 8
  +
- +
  maximum memory is 1 GB
  +
- +
  uses ECC
  +
+
+
Qlogic 1020 based wide SCSI bus (1 bus/chip for + AS500, 2 buses/chip for AS600)
+
+
21040 based 10 Mbit Ethernet adapter, both + Thinwire and UTP connectors
+
+
expansion:
+ +
- +
  AS500:
  + +
  - +
    3 32-bit PCI slots
    +
  - +
    1 64-bit PCI slot
    +
  +
- +
  AS600:
  + +
  - +
    2 32-bit PCI slot
    +
  - +
    3 64-bit PCI slots
    +
  - +
    1 PCI/EISA physically shared slot
    +
  - +
    3 EISA slots
    +
  - +
    1 PCI and 1 EISA slot are occupied by + default
    +
  +
+
+
21050 PCI-to-PCI bridge chip
+
+
Intel 82375EB PCI-EISA bridge (AS600 only)
+
+
2 16550A serial ports
+
+
1 parallel port
+
+
16 bit audio Windows Sound System, in a + dedicated slot (AS500) in EISA slot (AS600, this is + an ISA card)
+
+
PS/2 keyboard and mouse port
+

+ +

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. The AS500 Qlogic ISP1020A chip can be set + to run in Ultra mode by setting a SRM variable. FreeBSD + however follows the Qlogic chip errata and limits the + bus speed to Fast.

+ +

Beware of ancient SRM versions on AS500. When you + see weird SCSI speeds being reported by FreeBSD + like

+

+    cd0 at isp0 bus 0 target 4 lun 0
+    cd0: <DEC RRD45   DEC 0436> Removable CD-ROM SCSI-2 device
+    cd0: 250.000MB/s transfers (250.000MHz, offset 12)
+

+ +

it is time to do a SRM console firmware upgrade.

+ +

AS600 has one Qlogic SCSI chip dedicated to the + internal devices whereas the other Qlogic SCSI chip is + dedicated to external SCSI devices.

+ +

In AS500 DIMMs are installed in sets of 4, in + ``physically interleaved'' layout. So, a bank of 4 + DIMMs is not 4 physically adjacent + DIMMs.

+ +

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.

+ +

Note that both AS500 and AS600 are EISA machines. + This means you have to run the EISA Configuration + Utility (ECU) from floppy after adding EISA cards or to + change things like the configuration settings of the + onboard I/O. For AS500 which does not have a physical + EISA slot the ECU is used to configure the onboard + sound interface etc.

+ +

AS500 onboard sound can be used by adding a line + like

+

+    device pcm
+

+ +

to the kernel configuration file.

+ +

Using the ECU I configured my AS500 to use IRQ 10, + port 0x530, drq 0. Corresponding entries along with + flags 0x10011 must go into the device.hints file. Note that the flags + value is rather non-standard.

+ +

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 /boot/loader.rc:

+

+    set isp_mem_map=0xff
+

+ +

This may need to be typed at the boot loader prompt + before booting the installation kernel.

+ +

For the AlphaStation-[56]00 machines the kernel + config file must contain:

+

+    options    DEC_KN20AA 
+    cpu EV5
+

+

+ +

+

+ +

2.3.8 AlphaServer + 1000 (``Mikasa''), 1000A (``Noritake'') and + 800(``Corelle'')

+ +

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.

+ +

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.

+ +

AS800 with an EV5/400 MHz CPU was later re-branded + to become a ``DIGITAL Server 3300[R]'', AS800 with an + EV5/500 MHz CPU was later re-branded to become a + ``DIGITAL Server 3305[R]''.

+ +

Features:

+ +

+
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)
+
+
memory:
+ +
- +
  buswidth: 128 bit with ECC
  +
- +
  AS1000[A]:
  + +
  - +
    72pin 36 bit Fast Page Mode SIMMs, 70ns + or better
    +
  - +
    16 (EV5 machines) or 20 (EV4 machines) + SIMM slots
    +
  - +
    max memory is 1 GB
    +
  - +
    uses ECC
    +
  +
- +
  AS800: Uses 60ns 3.3 Volts EDO DIMMs
  +
+
+
embedded VGA (on some mainboard models)
+
+
3 PCI, 2 EISA, 1 64-bit PCI/EISA combo + (AS800)
+
+
7 PCI, 2 EISA (AS1000A)
+
+
2 PCI, 1 EISA/PCI, 7 EISA (AS1000)
+
+
embedded SCSI based on Symbios 810 [AS1000] or + Qlogic 1020 [AS1000A]
+

+ +

AS1000 based machines come in multiple enclosure + types. Floor standing, rack-mount, with or without + StorageWorks SCSI chassis etc. The electronics are the + same.

+ +

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.

+ +

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.

+ +

The AS1000/800 are somewhat stubborn when it comes + to serial consoles. They need

+

+    >>> SET CONSOLE SERIAL
+

+ +

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

+

+    >>> SET CONSOLE GRAPHICS
+

+ +

at the serial console.

+ +

For AS800 you want to check if your Ultra-Wide SCSI + is indeed in Ultra mode. This can be done using the EEROMCFG.EXE utility that is on + the Console Firmware Upgrade CDROM.

+ +

For the AlphaServer1000/1000A/800 machines the + kernel config file must contain:

+

+    options    DEC_1000A
+    cpu EV4     # depends on the CPU model installed
+    cpu EV5     # depends on the CPU model installed
+

+

+ +

+

+ +

2.3.9 + DS10/VS10/XP900 (``Webbrick'') / XP1000 (``Monet'') / + DS10L (``Slate'')

+ +

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)

+ +

+

+ +

2.3.9.1 ``Webbrick + / Slate''

+ +

+
21264 EV6 CPU at 466 MHz
+
+
L2 / Bcache: 2MB, ECC protected
+
+
memory bus: 128 bit via crossbar, 1.3GB/sec + memory bandwidth
+
+
memory:
+ +
- +
  industry standard 200 pin 83 MHz buffered + ECC SDRAM DIMMs
  +
- +
  4 DIMM slots for DS10; 2GB max memory
  +
- +
  2 DIMM slots for DS10L; 1GB max memory
  +
- +
  DIMMs are installed in pairs of 2
  +
+
+
21271 Core Logic chipset (``Tsunami'')
+
+
2 on-board 21143 Fast Ethernet controllers
+
+
AcerLabs M5237 (Aladdin-V) USB controller + (disabled)
+
+
AcerLabs M1533 PCI-ISA bridge
+
+
AcerLabs Aladdin ATA-33 controller
+
+
embedded dual EIDE
+
+
expansion: 3 64-bit PCI slots and 1 32-bit PCI + slot. DS10L has a single 64bit PCI slot
+
+
2 16550A serial ports
+
+
1 parallel port
+
+
2 USB
+
+
PS/2 keyboard & mouse port
+

+ +

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.

+ +

The smart power controller is called the RMC. When + enabled, typing EscapeEscapeRMC on serial port 1 will bring + you to the RMC prompt. RMC allows you to powerup or + powerdown, reset the machine, monitor and set + temperature trip levels etc. RMC has its own builtin + help.

+ +

Webbrick is shipped in a desktop-style case + similar to the older 21164 ``Maverick'' 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.

+ +

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.

+ +

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.

+ +

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.

+ +

The base model comes with a FUJITSU 9.5GB ATA disk + as its boot device. FreeBSD 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

+ +

On the PCI bus 32 and 64 bit cards are supported, + in 3.3V and 5V variants.

+ +

The USB ports are not supported and are disabled + by the SRM console in all recent SRM versions.

+ +

The kernel config file must contain:

+

+    options    DEC_ST6600    
+    cpu EV5
+

+ +

+

+
Note: Contrary to expectation there is + no cpu EV6 defined for + inclusion in the kernel config file. The cpu EV5 is mandatory to keep + + config(8) + happy.
+

+

+ +

+

+ +

2.3.9.2 + ``Monet''

+ +

+
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
+
+
L2 / Bcache: 4MB, ECC protected
+
+
memory bus: 256 bit
+
+
memory: 128 or 256 Mbytes 100 MHz (PC100) 168 + pin JEDEC standard, registered ECC SDRAM + DIMMs
+
+
21271 Core Logic chip-set (``Tsunami'')
+
+
1 on-board 21143 Ethernet controller
+
+
Cypress 82C693 USB controller
+
+
Cypress 82C693 PCI-ISA bridge
+
+
Cypress 82C693 controller
+
+
expansion: 2 independent PCI buses, driven by + high-speed I/O channels called ``hoses'':
+ +
- +
  hose 0: (the upper 3 slots) 2 64-bit PCI + slots 1 32-bit PCI slot
  +
- +
  hose 1: (the bottom 2 slots) 2 32-bit PCI + slots (behind a 21154 PCI-PCI bridge)
  +
- +
  2 of the 64-bit PCI slots are for + full-length cards
  +
- +
  all of the 32-bit PCI slots are for short + cards
  +
- +
  1 of the 32-bit PCI slots is physically + shared with an ISA slot
  +
- +
  all PCI slots run at 33MHz
  +
+
+
1 Ultra-Wide SCSI port based on a Qlogic 1040 + chip
+
+
2 16550A serial port
+
+
1 parallel port
+
+
PS/2 keyboard & mouse port
+
+
embedded 16-bit ESS ES1888 sound chip
+
+
2 USB ports
+
+
graphics options: ELSA Gloria Synergy or + DEC/Compaq PowerStorm 3D accelerator cards
+

+ +

Monet is housed in a mini-tower like enclosure + quite similar to the Miata box.

+ +

The on-board Qlogic UW-SCSI chip supports up to 4 + internal devices. There is no external connector for + the on-board SCSI.

+ +

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 ``0'' Memory capacity is max 4 GB. DIMMs are + installed ``physically interleaved'', 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)

+ +

The EIDE interface is usable / SRM bootable so + FreeBSD can be rooted on an EIDE disk. Although the + Cypress chip has potential for 2 EIDE channels Monet + uses only one of them.

+ +

The USB interface is supported by FreeBSD.If you + experience problems trying to use the USB interface + please check if the SRM variable usb_enable is set to on. You can change this by + performing:

+

+    >>> SET USB_ENABLE ON
+

+ +

+

+
Important: Don"t try to use + Symbios-chip based SCSI adapters in the PCI slots + connected to hose 1. There is a not-yet-found + FreeBSD bug that prevents this from working + correctly.
+

+

+ +

+

+
Important: 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 ``before'' the bridge.
+

+

+ +

The sound chip is not currently supported with + FreeBSD.

+ +

The kernel config file must contain:

+

+    options    DEC_ST6600    
+    cpu EV5
+

+ +

+

+
Note: Contrary to expectation there is + no cpu EV6 defined for + inclusion in the kernel config file. The cpu EV5 is mandatory to keep + + config(8) + happy.
+

+

+ +

+

+ +

2.3.10 DS20/DS20E + (``Goldrush'')

+ +

Features:

+ +

+
21264 EV6 CPU at 500 or 670 MHz
+
+
dual CPU capable machine
+
+
L2 / Bcache: 4 Mbytes per CPU
+
+
memory bus: dual 256 bit wide with crossbar + switch
+
+
memory:
+ +
- +
  SDRAM DIMMs
  +
- +
  installed in sets of 4
  +
- +
  16 DIMM slots, max. 4GB
  +
- +
  uses ECC
  +
+
+
21271 Core Logic chip-set (``Tsunami'')
+
+
embedded Adaptec ? Wide Ultra SCSI
+
+
expansion:
+ +
- +
  2 independent PCI buses, driven by + high-speed I/O channels called ``hoses''
  +
- +
  6 64-bit PCI slots, 3 per hose
  +
- +
  1 ISA slot
  +
+

+ +

DS20 needs

+

+    >>> SET CONSOLE SERIAL
+

+ +

before it goes for a serial console. Pulling the + keyboard from the machine is not sufficient. Going back + to a graphical console needs

+

+    >>> SET CONSOLE GRAPHICS
+

+ +

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 FreeBSD boots + it honors the CONSOLE variable + setting and all the boot messages as well as the login + prompt will go to the serial port.

+ +

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.

+ +

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(s).

+ +

The smart power controller is called the RMC. When + enabled, typing EscapeEscapeRMC on serial port 1 will bring you + to the RMC prompt. RMC allows you to powerup or + powerdown, reset the machine, monitor and set + temperature trip levels etc. RMC has its own builtin + help.

+ +

The embedded Adaptec SCSI chip on the DS20 is + disabled and is therefore not usable under FreeBSD.

+ +

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.

+ +

If you are using banks of DIMMs of different sizes + the biggest DIMMs should be installed in the DIMM slots + marked 0 on the mainboard. The + DIMM slots should be filled ``in order'' so after bank + 0 install in bank 1 and so on.

+ +

Don't try to use Symbios-chip based SCSI adapters in + the PCI slots connected to hose 1. There is a + not-yet-found FreeBSD 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 FreeBSD on it.

+ +

The kernel config file must contain:

+

+    options    DEC_ST6600    
+    cpu EV5
+

+ +

+

+
Note: Contrary to expectation there is no + cpu EV6 defined for + inclusion in the kernel config file. The cpu EV5 is mandatory to keep + config(8) + happy.
+

+

+ +

+

+ +

2.3.11 AlphaPC 264DP + / UP2000

+ +

UP2000 is built by Alpha Processor Inc.

+ +

Features:

+ +

+
21264 EV6 CPU at 670 MHz
+
+
dual CPU capable
+
+
L2 / Bcache: 4 Mbytes per CPU
+
+
memory bus: 256 bit
+
+
memory: SDRAM DIMMs installed in sets of 4, uses + ECC, 16 DIMM slots, max. 4GB
+
+
21272 Core Logic chip-set (``Tsunami'')
+
+
embedded Adaptec AIC7890/91 Wide Ultra SCSI
+
+
2 embedded IDE based on Cypress 82C693 chips
+
+
embedded USB via Cypress 82C693
+
+
expansion:
+ +
- +
  2 independent PCI buses, driven by + high-speed I/O channels called ``hoses''
  +
- +
  6 64-bit PCI slots, 3 per hose
  +
- +
  1 ISA slot
  +
+

+ +

Currently a maximum of 2GB memory is supported by + FreeBSD.

+ +

The on-board Adaptec is not bootable but works with + FreeBSD 4.0 and later as a datadisk-only SCSI bus.

+ +

Busmaster DMA is supported on the first IDE + interface only.

+ +

The kernel config file must contain:

+

+    options    DEC_ST6600    
+    cpu EV5
+

+ +

+

+
Note: Contrary to expectation there is no + cpu EV6 defined for + inclusion in the kernel config file. The cpu EV5 is mandatory to keep + config(8) + happy.
+

+

+ +

+

+ +

2.3.12 AlphaServer + 2000 (``DemiSable''), 2100 (``Sable''), 2100A + (``Lynx'')

+ +

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.

+ +

+
21064 EV4[5] CPU[s] at 200, 233, 275 MHz or + 21164 EV5[6] CPU[s]s at 250, 300, 375, 400 MHz
+
+
cache: varies in size with the CPU model; 1, 4 + or 8Mbyte per CPU
+
+
embedded floppy controller driving a 2.88 Mbytes + drive
+
+
embedded 10Mbit 21040 Ethernet [AS2100 only]
+
+
2 serial ports
+
+
1 parallel port
+
+
PS/2 style keyboard & mouse port
+

+ +

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.

+ +

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

+

+    >>> CLEAR_ERROR ALL
+

+ +

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.

+ +

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.

+ +

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 ``flat memory modules''.

+ +

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

+ +

Both Lynx and Sable are somewhat stubborn when it + comes to serial consoles. They need

+

+    >>> SET CONSOLE SERIAL
+

+ +

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

+

+    >>> SET CONSOLE GRAPHICS
+

+ +

at the serial console. On Lynx keep the VGA card in + one of the primary PCI slots. EISA VGA cards are not + slot sensitive.

+ +

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:

+

+    >>> SET OCP_TEXT "FreeBSD"
+     
+

+ +

The SRM

+

+    >>> SHOW FRU
+

+ +

command produces an overview of your configuration + with module serial numbers, hardware revisions and + error log counts.

+ +

Both Sable, DemiSable and Lynx have Symbios 810 + based Fast SCSI on-board. Check if it is set to Fast + SCSI speed by

+

+    >>> SHOW PKA0_FAST
+

+ +

When set to 1 it is negotiating for Fast speeds.

+

+    >>> SET PKA0_FAST 1
+

+ +

enables Fast SCSI speeds.

+ +

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.

+ +

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.

+ +

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

+ +

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

+

+    >>> RUNECU
+

+ +

+

+
Note: 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.
+

+

+ +

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 FreeBSD has never been verified with an + ExtIO module.

+ +

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.

+ +

The kernel config file must contain:

+

+    options    DEC_2100_A500
+    cpu EV4 #dependent on CPU model installed
+    cpu EV5 #dependent on CPU model installed
+

+

+ +

+

+ +

2.3.13 AlphaServer + 4x00 (``Rawhide'')

+ +

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.

+ +

Features:

+ +

+
21164 EV5 CPUs at 266, 300 MHz or 21164A EV56 + CPUs at 400, 466, 533, 600 and 666 Mhz
+
+
cache: 4 Mbytes per CPU. EV5 300 MHz was also + available cache-less. 8 Mbytes for EV5 600Mhz
+
+
memory bus: 128 bit with ECC
+
+
embedded floppy controller
+
+
2 serial ports
+
+
1 parallel port
+
+
PS/2 style keyboard & mouse port
+

+ +

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 + entire memory subsystem running + at the slower EDO timing

+ +

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.

+ +

Rawhides are available with a 8 64-bit PCI / 3 EISA + slot expansion backplanes (called ``Saddle'' 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.

+ +

The current FreeBSD 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.

+ +

+

+
Note: 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.
+

+

+ +

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.

+ +

The kernel config file must contain:

+

+    options    DEC_KN300
+    cpu EV5
+

+

+ +

+

+ +

2.3.14 AlphaServer + 1200 (``Tincup'') and AlphaStation 1200 + (``DaVinci'')

+ +

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

+ +

Features:

+ +

+
21164A EV56 CPUs at 400 or 533 Mhz
+
+
cache: 4 Mbytes per CPU
+
+
memory bus: 128 bit with ECC, DIMM memory on two + memory daughter boards
+
+
embedded floppy controller
+
+
2 serial ports
+
+
1 parallel port
+
+
PS/2 style keyboard & mouse port
+

+ +

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 ``holes''. + Supported DIMM sizes are 64 Mbytes and 256 Mbytes. The + DIMMs are 72 bit SDRAM based, as the system employs + ECC.

+ +

+

+
Note: FreeBSD currently supports up to + 2GBytes
+

+

+ +

AS1200 has an embedded Symbios 810 drive Fast SCSI + bus.

+ +

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.

+ +

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.

+ +

The kernel config file must contain:

+

+    options    DEC_KN300
+    cpu EV5
+

+

+ +

+

+ +

2.3.15 AlphaServer + 8200 and 8400 (``TurboLaser'')

+ +

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.

+ +

Basic disk storage is housed in a StorageWorks + shelf. AS8400 uses 3 phase power, AS8200 uses single + phase power.

+ +

Features:

+ +

+
21164 EV5/EV56 CPUs at up to 467 MHz or 21264 + EV67 CPUs at up to 625 MHz
+
+
one or two CPUs per CPU module
+
+
cache: 4Mbytes B-cache per CPU
+
+
memory bus: 256 bit with ECC
+
+
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.
+
+
expansion: 3 system ``I/O ports'' that allow up + to 12 I/O channels each I/O channel can connect to + XMI, Futurebus+ or PCI boxes
+

+ +

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

+ +

Only PCI expansion is supported on FreeBSD. XMI or + Futurebus+ (which are AS8400 only) are both + unsupported.

+ +

The I/O port modules are designated KFTIA or KFTHA. + The I/O port modules supply so called ``hoses'' 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.

+ +

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.

+ +

For best performance distribute high bandwidth + (FibreChannel, Gigabit Ethernet) over multiple hoses + and/or multiple KFTHA/KFTIA.

+ +

Currently PCI expansion cards containing PCI bridges + are not usable with FreeBSD. Don't use them at this + time.

+ +

The single ended narrow SCSI bus on the KFTIA will + turn up as the fourth SCSI bus. The 3 fast-wide + differential SCSI buses of the KFTIA precede it.

+ +

AS8x00 are generally run with serial consoles. Some + newer machines might have a graphical console of some + sorts but FreeBSD has only been tested on a serial + console.

+ +

For serial console usage either change /etc/ttys to have:

+

+    console "/usr/libexec/getty std.9600"   unknown   on secure
+

+ +

as the console entry, or add

+

+    zs0     "/usr/libexec/getty std.9600"   unknown   on secure
+

+ +

For the AlphaServer 8x00 machines the kernel config + file must contain:

+

+    options    DEC_KN8AE   # Alpha 8200/8400 (Turbolaser)
+    cpu EV5
+

+ +

Contrary to expectation there is no cpu EV6 defined for inclusion in the + kernel config file. The cpu + EV5 is mandatory to keep + config(8) happy.

+

+ +

+

+ +

2.3.16 Alpha + Processor Inc. UP1000

+ +

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.

+ +

Features:

+ +

+
21264a Alpha CPU at 600 or 700 MHz in a Slot B + module (includes cooling fans)
+
+
memory bus: 128 bits to the L2 cache, 64 bits + from Slot B to the AMD-751
+
+
on-board Bcache / L2 cache: 2MB (600Mhz) or 4MB + (700Mhz)
+
+
AMD AMD-751 (``Irongate'') system controller + chip
+
+
Acer Labs M1543C PCI-ISA bridge controller / + super-IO chip
+
+
PS/2 mouse & keyboard port
+
+
memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 + DIMM slots DIMM sizes supported are 64, 128 or 256 + Mb in size
+
+
2 16550A serial port
+
+
1 ECP/EPP parallel port
+
+
floppy interface
+
+
2 embedded Ultra DMA33 IDE interface
+
+
2 USB ports
+
+
expansion:
+ +
- +
  4 32 bit PCI slots
  +
- +
  2 ISA slots
  +
- +
  1 AGP slot
  +
+

+ +

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

+ +

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 2. This is a + bit counter-intuitive.

+ +

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

+ +

Chances are that your UP1000 comes by default with + AlphaBios only. The SRM console firmware is available + from the Alpha Processor Inc. web site. It is currently + available in a beta version which was successfully used + during the port of FreeBSD to the UP1000.

+ +

The embedded Ultra DMA EIDE ports are bootable by + the SRM console.

+ +

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.

+ +

The USB interfaces are disabled by the SRM console + and have not (yet) been tested with FreeBSD.

+ +

For the UP1000 the kernel config file must + contain:

+

+    options    API_UP1000  # UP1000, UP1100 (Nautilus)
+    cpu EV5
+

+

+ +

+

+ +

2.3.17 Alpha + Processor Inc. UP1100

+ +

The UP1100 is an ATX mainboard based on the 21264a + CPU running at 600 MHz. It is normally housed in an ATX + tower enclosure.

+ +

Features:

+ +

+
21264a Alpha EV6 CPU at 600 or 700 MHz
+
+
memory bus: 100MHz 64-bit (PC-100 SDRAM), 800 + MB/s memory bandwidth
+
+
on-board Bcache / L2 cache: 2Mb
+
+
AMD AMD-751 (``Irongate'') system controller + chip
+
+
Acer Labs M1535D PCI-ISA bridge controller / + super-IO chip
+
+
PS/2 mouse & keyboard port
+
+
memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 + DIMM slots DIMM sizes supported are 64, 128 or 256 + Mb in size
+
+
2 16550A serial port
+
+
1 ECP/EPP parallel port
+
+
floppy interface
+
+
2 embedded Ultra DMA66 IDE interface
+
+
2 USB port
+
+
expansion: 3 32 bit PCI slots and 1 AGP2x + slot
+

+ +

SRM console code comes standard with the UP1100. The + SRM lives in 2Mbytes of flash ROM.

+ +

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 2. This is a + bit counter-intuitive.

+ +

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

+ +

The UP1100 has an on-board 21143 10/100Mbit Ethernet + interface.

+ +

The UP1100 is equipped with a SoundBlaster + compatible audio interface. Whether it works with + FreeBSD is as of yet unknown.

+ +

The embedded Ultra DMA EIDE ports are bootable by + the SRM console.

+ +

The UP1100 has 3 USB ports, 2 going external and one + connected to the AGP port.

+ +

For the UP1100 the kernel config file must + contain:

+

+    options    API_UP1000  # UP1000, UP1100 (Nautilus)
+    cpu EV5
+

+ +

Contrary to expectation there is no cpu EV6 defined for inclusion in the + kernel config file. The cpu + EV5 is mandatory to keep + config(8) happy.

+

+ +

+

+ +

2.3.18 Alpha + Processor Inc. CS20, Compaq DS20L

+ +

The CS20 is a 19", 1U high rackmount server + based on the 21264[ab] CPU. It can have a maximum of 2 + CPUs. Compaq sells the CS20 rebranded as the + AlphaServer DS20L. DS20L has 833MHz CPUs.

+ +

Features:

+ +

+
21264a Alpha CPU at 667 MHz or 21264b 833 MHz + (max. 2 CPUs)
+
+
memory bus: 100MHz 256-bit wide
+
+
21271 Core Logic chipset (``Tsunami'')
+
+
Acer Labs M1533 PCI-ISA bridge controller / + super-IO chip
+
+
PS/2 mouse & keyboard port
+
+
memory: 168-pin PC100 PLL buffered/registered + SDRAM DIMMS, 8 DIMM slots, uses ECC memory, min 256 + Mbytes / max 2 GBytes of memory
+
+
2 16550A serial port
+
+
1 ECP/EPP parallel port
+
+
ALI M1543C Ultra DMA66 IDE interface
+
+
embedded dual Intel 82559 10/100Mbit + Ethernet
+
+
embedded Symbios 53C1000 Ultra160 SCSI + controller
+
+
expansion: 2 64 bit PCI slots (2/3 length)
+

+ +

SRM console code comes standard with the CS20. The + SRM lives in 2Mbytes of flash ROM.

+ +

The CS20 needs ECC capable DIMMs. Note that it uses + buffered DIMMs.

+ +

The CS20 has an I2C based internal monitoring system + for things like temperature, fans, voltages etc. The + I2C also supports ``wake on LAN''.

+ +

Each PCI slot is connected to its own independent + PCI bus on the Tsunami.

+ +

The embedded Ultra DMA EIDE ports are bootable by + the SRM console.

+ +

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.

+ +

Note that there is no floppy disk drive (or a + connector to add one).

+ +

The kernel config file must contain:

+

+    options    DEC_ST6600
+    cpu EV5
+

+ +

Contrary to expectation there is no cpu EV6 defined for inclusion in the + kernel config file. The cpu + EV5 is mandatory to keep + config(8) happy.

+

+ +

+

+ +

2.4 Supported + Hardware Overview

+ +

A word of caution: the installed base for FreeBSD is + not nearly as large as for FreeBSD/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. GENERIC contains things that are known to + work on Alpha only.

+ +

The PCI and ISA expansion busses are fully supported. + Turbo Channel is not in GENERIC + 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.

+ +

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.

+ +

ATA and ATAPI (IDE) devices are supported via the + 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.

+ +

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.

+ +

The Qlogic QL2x00 FibreChannel host adapters are fully + supported.

+ +

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 FreeBSD + de(4) (older driver) or + + dc(4) (newer driver). + Some new SRM versions are known to recognize the Intel + 8255x Ethernet chips as driven by the FreeBSD + fxp(4) driver. But + beware: the + fxp(4) driver is + reported not to work correctly with FreeBSD (although it + works excellently on FreeBSD/x86).

+ +

DEC DEFPA PCI FDDI network adapters are supported on + alpha.

+ +

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 FreeBSD will be able to use it. The + console driver works just like on a FreeBSD/intel + machine. Please note that VESA modes are not supported on + Alpha, so that leaves you with 80x25 consoles.

+ +

In some Alpha machines you will find video adapters + based on TGA chips. The plain TGA adapter does not + emulate VGA and is therefore not usable for a FreeBSD + console. TGA2 cards have a basic VGA compatibility mode + and work fine as FreeBSD consoles.

+ +

The ``PC standard'' serial ports found on most Alphas + are supported.

+ +

ISDN (i4b) is not supported on FreeBSD/alpha.

+

+ +

+

+ +

2.5 + Acknowledgments

+ +

In compiling this file I used multiple information + sources, but the NetBSD Web site proved to be an invaluable + source of information. If it wasn't for NetBSD/alpha + there probably would not be a FreeBSD/alpha in the first + place.

+ +

People who kindly helped me create this section:

+ +

+
Andrew Gallatin <gallatin@FreeBSD.org>
+
+
Chuck Robey <chuckr@FreeBSD.org>
+
+
Matthew Jacob <mjacob@FreeBSD.org>
+
+
Michael Smith <msmith@FreeBSD.org>
+
+
David O'Brien <obrien@FreeBSD.org>
+
+
Christian Weisgerber
+
+
Kazutaka YOKOTA
+
+
Nick Maniscalco
+
+
Eric Schnoebelen
+
+
Peter van Dijk
+
+
Peter Jeremy
+
+
Dolf de Waal
+
+
Wim Lemmers, ex-Compaq
+
+
Wouter Brackman, Compaq
+
+
Lodewijk van den Berg, Compaq
+

+

+ +

+

+ +

3 Supported + Devices

+ $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.114 2002/11/07 22:11:00 bmah Exp $ + +

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

+ +

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

+ +

+

+ +

3.1 Disk + Controllers

+ +

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

+ +

+
Acerlabs Aladdin
+
+
AMD 756 ATA66, 766 ATA100, 768 ATA100
+
+
Cenatek Rocket Drive
+
+
CMD 646, 648 ATA66, and 649 ATA100
+
+
Cypress 82C693
+
+
Cyrix 5530 ATA33
+
+
HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133
+
+
Intel PIIX, PIIX3, PIIX4
+
+
Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100
+
+
nVidia nForce ATA100
+
+
Promise ATA100 OEM chip (pdc20265)
+
+
Promise ATA133 OEM chip (pdc20269)
+
+
Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000
+
+
Promise Ultra-33, -66, -100, -133 TX2/TX2000
+
+
ServerWorks ROSB4 ATA33
+
+
ServerWorks CSB5 ATA66/ATA100
+
+
Sil 0680 UDMA6
+
+
SiS 530, 540, 620
+
+
SiS 630, 633, 635, 645, 730, 733, 735, 740, 745, + 750
+
+
SiS 5591 ATA100
+
+
VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100
+
+
VIA 8233, 8235 ATA133
+

+
+
+ +

Adaptec SCSI Controllers

+ +

+
Adaptec + 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x + series PCI SCSI controllers, including + Narrow/Wide/Twin/Ultra/Ultra2 variants ( + ahc(4) driver)
+
+
Adaptec AIC7770, AIC7850, AIC7860, AIC7870, + AIC7880, and AIC789x on-board SCSI controllers ( + ahc(4) driver)
+

+
+
+ +

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

+ +

+
MegaRAID Series 418
+
+
MegaRAID Enterprise 1200 (Series 428)
+
+
MegaRAID Enterprise 1300 (Series 434)
+
+
MegaRAID Enterprise 1400 (Series 438)
+
+
MegaRAID Enterprise 1500 (Series 467)
+
+
MegaRAID Enterprise 1600 (Series 471)
+
+
MegaRAID Elite 1500 (Series 467)
+
+
MegaRAID Elite 1600 (Series 493)
+
+
MegaRAID Express 100 (Series 466WS)
+
+
MegaRAID Express 200 (Series 466)
+
+
MegaRAID Express 300 (Series 490)
+
+
MegaRAID Express 500 (Series 475)
+
+
Dell PERC
+
+
Dell PERC 2/SC
+
+
Dell PERC 2/DC
+
+
Dell PERC 3/DCL
+
+
HP NetRaid-1si
+
+
HP NetRaid-3si
+
+
HP Embedded NetRaid
+

+ +

+

+
Booting from these controllers is not supported + due to SRM limitations.
+

+

+
+
+ +

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

+ +

+
DAC960P
+
+
DAC960PD
+
+
DAC960PDU
+
+
DAC960PL
+
+
DAC960PJ
+
+
DAC960PG
+
+
AcceleRAID 150
+
+
AcceleRAID 250
+
+
eXtremeRAID 1100
+

+ +

+

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

+

+
+
+ +

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

+ +

+
ASUS SC-200, SC-896
+
+
Data Technology DTC3130 (all variants)
+
+
DawiControl DC2976UW
+
+
Diamond FirePort (all)
+
+
NCR cards (all)
+
+
Symbios cards (all)
+
+
Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, + and 390U3W
+
+
Tyan S1365
+

+
+
+ +

Qlogic controllers and variants ( + isp(4) driver)

+ +

+
Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters
+
+
Qlogic 1240 dual Ultra SCSI controllers
+
+
Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers
+
+
Qlogic 12160 Ultra3 LVD controllers
+
+
Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers
+
+
Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers
+
+
Performance Technology SBS440 ISP1000 variants
+
+
Performance Technology SBS450 ISP1040 variants
+
+
Performance Technology SBS470 ISP2100 variants
+
+
Antares Microsystems P-0033 ISP2100 variants
+

+
+
+ +

LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)

+ +

+
LSI FC909, FC929
+
+
LSI 53c1020, 53c1030
+

+
+
+ +

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

+ +

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

+ +

+
SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) ( + cd(4))
+
+
ATAPI IDE interface ( + acd(4))
+

+
+
+

+ +

+

+ +

3.2 Ethernet + Interfaces

+ +

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

+ +

+
ANA-62011 64-bit single port 10/100baseTX + adapter
+
+
ANA-62022 64-bit dual port 10/100baseTX + adapter
+
+
ANA-62044 64-bit quad port 10/100baseTX + adapter
+
+
ANA-69011 32-bit single port 10/100baseTX + adapter
+
+
ANA-62020 64-bit single port 100baseFX adapter
+

+
+
+ +

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

+ +

+
AMD PCnet/PCI (79c970 & 53c974 or 79c974)
+
+
AMD PCnet/FAST
+
+
Isolan AT 4141-0 (16 bit)
+
+
Isolink 4110 (8 bit)
+
+
PCnet/FAST+
+
+
PCnet/FAST III
+
+
PCnet/PRO
+
+
PCnet/Home
+
+
HomePNA
+

+
+
+ +

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

+ +

+
Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)
+
+
Allied Telesyn AT2550
+
+
Allied Telesyn AT2500TX
+
+
D-Link DFE-530TX+, DFE-538TX
+
+
Farallon NetLINE 10/100 PCI
+
+
Genius GF100TXR (RTL8139)
+
+
KTX-9130TX 10/100 Fast Ethernet
+
+
NDC Communications NE100TX-E
+
+
Netronix Inc. EA-1210 NetEther 10/100
+
+
OvisLink LEF-8129TX
+
+
OvisLink LEF-8139TX
+
+
SMC EZ Card 10/100 PCI 1211-TX
+

+
+
+ +

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

+ +

+
Kingston KNE110TX
+
+
LinkSys EtherFast LNE100TX
+
+
Matrox FastNIC 10/100
+
+
NetGear FA310-TX Rev. D1
+

+
+
+ +

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

+ +

+
Accton EN1217 (98715A)
+
+
Adico AE310TX (98715A)
+
+
Compex RL100-TX (98713 or 98713A)
+
+
CNet Pro120A (98713 or 98713A)
+
+
CNet Pro120B (98715)
+
+
NDC Communications SFA100A (98713A)
+
+
SVEC PN102TX (98713)
+

+
+
+ +

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

+ +

+
LinkSys EtherFast LNE100TX Version 2
+

+
+
+ +

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

+ +

+
Trendware TE100-PCIE
+

+
+
+ +

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

+ +

+
AOpen/Acer ALN-320
+
+
D-Link DFE-530TX
+
+
Hawking Technologies PN102TX
+

+
+
+ +

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

+ +

+
SiS 630, 635 and 735 motherboard chipsets
+

+
+
+ +

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

+ +

+
NetGear FA311-TX
+
+
NetGear FA312-TX
+

+
+
+ +

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

+ +

+
D-Link DFE-550TX
+

+
+
+ +

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

+ +

+
SK-9821 1000baseT copper, single port
+
+
SK-9822 1000baseT copper, dual port
+
+
SK-9841 1000baseLX single mode fiber, single + port
+
+
SK-9842 1000baseLX single mode fiber, dual + port
+
+
SK-9843 1000baseSX multimode fiber, single + port
+
+
SK-9844 1000baseSX multimode fiber, dual port
+

+
+
+ +

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

+ +

+
Compaq Netelligent 10, 10/100, 10/100 + Dual-Port
+
+
Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP
+
+
Compaq NetFlex 3P, 3P Integrated, 3P w/BNC
+
+
Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP
+
+
Racore 8165 10/100baseTX
+
+
Racore 8148 10baseT/100baseTX/100baseFX + multi-personality
+

+
+
+ +

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

+ +

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

+ +

+
LinkSys EtherFast LNE100TX v4.0/4.1
+

+
+
+ +

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

+ +

+
Alfa Inc. GFC2204
+
+
CNet Pro110B
+

+
+
+ +

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

+ +

+
Asante
+
+
Cogent EM100FX and EM440TX
+
+
DEC DE425, DE435, DE450, and DE500
+
+
SMC Etherpower 8432T, 9332, and 9334
+
+
ZYNX ZX 3xx
+

+
+
+ +

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

+ +

+
DEC DE500
+
+
Compaq Presario 7900 series built-in Ethernet
+
+
D-Link DFE-570TX
+
+
Kingston KNE100TX
+
+
LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet
+

+
+
+ +

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

+ +

+
Jaton Corporation XpressNet
+

+
+
+ +

Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs ( + fxp(4) driver)

+ +

+
Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+
Intel InBusiness 10/100 PCI Network Adapter
+
+
Intel PRO/100+ Management Adapter
+
+
Intel Pro/100 VE Desktop Adapter
+
+
Intel Pro/100 M Desktop Adapter
+
+
Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters
+
+
On-board Ethernet NICs on many Intel + motherboards.
+

+
+
+ +

3Com Etherlink XL-based NICs ( + xl(4) driver)

+ +

+
3C900/905/905B/905C PCI
+
+
3C556/556B MiniPCI
+
+
3C450-TX HomeConnect adapter
+
+
3c980/3c980B Fast Etherlink XL server adapter
+
+
3cSOHO100-TX OfficeConnect adapter
+
+
3C575TX/575B/XFE575BT/575C/656/656B/656C + (Cardbus)
+
+
Dell Optiplex GX1 on-board 3C918
+
+
Dell On-board 3C920
+
+
Dell Precision on-board 3C905B
+
+
Dell Latitude laptop docking station embedded + 3C905-TX
+

+
+
+ +

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

+ +

+
3Com 3CR990-TX-95
+
+
3Com 3CR990-TX-97
+
+
3Com 3CR990B-SRV
+
+
3Com 3CR990B-TXM
+
+
3Com 3CR990SVR95
+
+
3Com 3CR990SVR97
+

+
+
+ +

Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips ( + gx(4) and + em(4) drivers), plus + NICs supported by the Intel 82540EM, 82544, 82545EM, and + 82546EB controller chips ( + em(4) driver only)

+ +

+
Intel PRO/1000 Gigabit Ethernet
+

+ +

+

+
Note: The + em(4) driver is + officially supported by Intel, but is only supported + on the i386.
+

+

+
+
+

+ +

+

+ +

3.3 FDDI + Interfaces

+ +

DEC DEFPA PCI ( + fpa(4) driver)

Comtrol Rocketport card ( + rp(4) driver)

+

+ +

+

+ +

3.9 Audio + Devices

+ +

ESS

+ +

+
ES1868, ES1869, ES1879 and ES1888 ( + sbc(4) driver)
+
+
Maestro-1, Maestro-2, and Maestro-2E
+
+
Maestro-3/Allegro
+ +
+
+
Note: The Maestro-3/Allegro cannot be + compiled into the FreeBSD kernel due to licensing + restrictions. To use this driver, add the + following line to /boot/loader.conf:
+
```
+    snd_maestro3_load="YES"
+
```
+
+
+

+
+
+ +

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

+ +

Creative Technologies SoundBlaster series ( + sbc(4) driver)

+ +

+
SoundBlaster
+
+
SoundBlaster Pro
+
+
SoundBlaster AWE-32
+
+
SoundBlaster AWE-64
+
+
SoundBlaster AWE-64 GOLD
+
+
SoundBlaster ViBRA-16
+

+
+
+

+ +

+

+ +

3.10 Camera and Video + Capture Devices

+

+ +

+

+ +

3.11 USB Devices

+ +

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

+ +

+

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

+

+ +

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

+ +

+
ALi Aladdin-V
+
+
AMD-756
+
+
CMD Tech 670 & 673
+
+
Intel 82371SB (PIIX3)
+
+
Intel 82371AB and EB (PIIX4)
+
+
Intel 82801AA (ICH)
+
+
Intel 82801AB (ICH0)
+
+
Intel 82801BA/BAM (ICH2)
+
+
Intel 82443MX
+
+
NEC uPD 9210
+
+
OPTi 82C861 (FireLink)
+
+
SiS 5571
+
+
VIA 83C572 USB
+
+
UHCI or OHCI compliant motherboard chipsets (no + exceptions known)
+

+
+
+ +

Hubs

+ +

+
Andromeda hub
+
+
MacAlly self powered hub (4 ports)
+
+
NEC hub
+

+
+
+ +

Keyboards ( + ukbd(4) driver)

+ +

+
Apple iMac keyboard
+
+
BTC BTC7935 keyboard with PS/2 mouse port
+
+
Cherry G81-3504 keyboard
+
+
Logitech M2452 keyboard
+
+
MacAlly iKey keyboard
+
+
Microsoft keyboard
+
+
Sun Microsystems Type 6 USB keyboard
+

+
+
+ +

Mice ( + ums(4) driver)

+ +

+
Agiler Mouse 29UO
+
+
Apple iMac Mouse
+
+
Belkin Mouse
+
+
Chic mouse
+
+
Cypress mouse
+
+
Genius Niche mouse
+
+
Kensington Mouse-in-a-Box
+
+
Logitech wheel mouse (3 buttons)
+
+
Logitech PS/2 / USB mouse (3 buttons)
+
+
MacAlly mouse (3 buttons)
+
+
Microsoft IntelliMouse (3 buttons)
+
+
Sun Microsystems Type 6 USB Mouse
+
+
Trust Ami Mouse (3 buttons)
+

+
+
+ +

Printers and parallel printer conversion cables ( + ulpt(4) driver)

+ +

+
ATen parallel printer adapter
+
+
Belkin F5U002 parallel printer adapter
+
+
Entrega USB-to-parallel printer adapter
+

+
+
+ +

Storage ( + umass(4) driver)

+ +

+
Matshita CF-VFDU03 floppy drive
+
+
Microtech USB-SCSI-HD 50 USB to SCSI cable
+
+
Panasonic floppy drive
+
+
Y-E Data floppy drive (720/1.44/2.88Mb)
+

+
+
+

+ +

+

+ +

3.12 IEEE 1394 + (Firewire) Devices

+

+ +

+

+ +

3.13 Cryptographic + Accelerators

+

+ +

+

+ +

3.14 + Miscellaneous

+ +

Floppy drives ( + fd(4) driver)

+ +

Keyboards including:

+ +

+
AT-style keyboards
+
+
PS/2 keyboards
+
+
USB keyboards (specific instances are listed in + the section describing USB + devices)
+

+
+
+ +

Mice including:

+ +

+
PS/2 mice ( + psm(4) driver)
+
+
Serial mice
+
+
USB mice (specific instances are listed in the + section describing USB + devices)
+

+
+
+ +

``PC standard'' parallel ports ( + ppc(4) driver)

+

FreeBSD/i386 5.0-DP2 + Hardware Notes

+ +

The FreeBSD Documentation + Project

+ +

+

+ +

+

Table of Contents

2 Supported Processors and + Motherboards

+

3.1 Disk Controllers
3.2 Ethernet + Interfaces
3.3 FDDI Interfaces
3.4 ATM Interfaces
3.5 Wireless Network + Interfaces
3.6 Miscellaneous + Networks
3.7 ISDN Interfaces
3.8 Serial Interfaces
3.9 Audio Devices
3.10 Camera and Video Capture + Devices
3.11 USB Devices
3.12 IEEE 1394 (Firewire) + Devices
3.13 Cryptographic + Accelerators
3.14 Miscellaneous

+

+ +

+

+ +

1 Introduction

+ +

This document contains the hardware compatibility notes + for FreeBSD 5.0-DP2 on the IA-32 hardware platform (also + referred to as FreeBSD/i386 5.0-DP2). It lists devices + known to work on this platform, as well as some notes on + boot-time kernel customization that may be useful when + attempting to configure support for new devices.

+ +

+

+
Note: This document includes information + specific to the IA-32 hardware platform. Versions of + the hardware compatibility notes for other + architectures will differ in some details.
+

+

+ +

+

+ +

2 Supported Processors + and Motherboards

+ +

FreeBSD/i386 runs on a wide variety of ``IBM PC + compatible'' machines. Due to the wide range of hardware + available for this architecture, it is impossible to + exhaustively list all combinations of equipment supported + by FreeBSD. Nevertheless, some general guidelines are + presented here.

+ +

Almost all i386-compatible processors are supported. All + Intel processors beginning with the 80386 are supported, + including the 80386, 80486, Pentium, Pentium Pro, Pentium + II, Pentium III, Pentium 4, and variants thereof, such as + the Xeon and Celeron processors. (While technically + supported, the use of the 80386SX is specifically not + recommended.) All i386-compatible AMD processors are also + supported, including the Am486, Am5x86, K5, K6 (and + variants), Athlon (including Athlon-MP, Athlon-XP, + Athlon-4, and Athlon Thunderbird), and Duron processors. + The AMD Élan SC520 embedded processor is supported. + The Transmeta Crusoe is recognized and supported, as are + i386-compatible processors from Cyrix and NexGen.

+ +

There is a wide variety of motherboards available for + this architecture. Motherboards using the ISA, VLB, EISA, + AGP, and PCI expansion busses are well-supported. There is + some limited support for the MCA (``MicroChannel'') + expansion bus used in the IBM PS/2 line of PCs.

+ +

Symmetric multi-processor (SMP) systems are generally + supported by FreeBSD, although in some cases, BIOS or + motherboard bugs may generate some problems. Perusal of the + archives of the FreeBSD symmetric multiprocessing mailing + list <freebsd-smp@FreeBSD.org> + may yield some clues.

+ +

FreeBSD will generally run on i386-based laptops, albeit + with varying levels of support for certain hardware + features such as sound, graphics, power management, and + PCCARD expansion slots. These features tend to vary in + idiosyncratic ways between machines, and frequently require + special-case support in FreeBSD to work around hardware + bugs or other oddities. When in doubt, a search of the + archives of the FreeBSD laptop computer mailing list <freebsd-mobile@FreeBSD.org> + may be useful.

+

+ +

+

+ +

3 Supported + Devices

+ $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.114 2002/11/07 22:11:00 bmah Exp $ + +

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

+ +

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

+ +

+

+ +

3.1 Disk + Controllers

+ +

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

+ +

+
Acerlabs Aladdin
+
+
AMD 756 ATA66, 766 ATA100, 768 ATA100
+
+
Cenatek Rocket Drive
+
+
CMD 646, 648 ATA66, and 649 ATA100
+
+
Cypress 82C693
+
+
Cyrix 5530 ATA33
+
+
HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133
+
+
Intel PIIX, PIIX3, PIIX4
+
+
Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100
+
+
nVidia nForce ATA100
+
+
Promise ATA100 OEM chip (pdc20265)
+
+
Promise ATA133 OEM chip (pdc20269)
+
+
Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000
+
+
Promise Ultra-33, -66, -100, -133 TX2/TX2000
+
+
ServerWorks ROSB4 ATA33
+
+
ServerWorks CSB5 ATA66/ATA100
+
+
Sil 0680 UDMA6
+
+
SiS 530, 540, 620
+
+
SiS 630, 633, 635, 645, 730, 733, 735, 740, 745, + 750
+
+
SiS 5591 ATA100
+
+
VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100
+
+
VIA 8233, 8235 ATA133
+

+
+
+ +

Adaptec SCSI Controllers

+ +

+
Adaptec 1535 ISA SCSI controllers
+
+
Adaptec 154x series ISA SCSI controllers ( + aha(4) driver)
+
+
Adaptec 164x series MCA SCSI controllers ( + aha(4) driver)
+
+
Adaptec 174x series EISA SCSI controller in + standard and enhanced mode ( + aha(4) and + ahb(4) driver)
+
+
Adaptec 274x series EISA SCSI controllers, + including narrow and wide variants ( + ahc(4) driver)
+
+
Adaptec 284x series VLB SCSI controllers, + including narrow and wide variants ( + ahc(4) driver)
+
+
Adaptec + 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x + series PCI SCSI controllers, including + Narrow/Wide/Twin/Ultra/Ultra2 variants ( + ahc(4) driver)
+
+
Adaptec AIC7770, AIC7850, AIC7860, AIC7870, + AIC7880, and AIC789x on-board SCSI controllers ( + ahc(4) driver)
+
+
Adaptec 1510 series ISA SCSI controllers (not for + bootable devices)
+
+
Adaptec 152x series ISA SCSI controllers ( + aha(4) driver)
+
+
Adaptec AIC-6260 and AIC-6360 based boards, which + includes the AHA-152x and SoundBlaster SCSI cards ( + aic(4) driver)
+

+
+
+ +

Ultra-320 SCSI controllers based on the Adaptec + AIC7901, AIC7901A, and AIC7902 Ultra320 controller chips + ( + ahd(4) driver)

+ +

+
Adaptec 29320, 29320A, 29320B, 29320LP
+
+
Adaptec 39320, 39320D
+

+
+
+ +

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

+ +

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

+ +

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

+ +

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

+ +

+
Adaptec AAC-2622
+
+
Adaptec AAC-364
+
+
Adaptec SCSI RAID 5400S
+
+
Dell PERC 2/QC
+
+
Dell PERC 2/Si
+
+
Dell PERC 3/Di
+
+
Dell PERC 3/QC
+
+
Dell PERC 3/Si
+
+
HP NetRAID-4M
+

+
+
+ +

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

+
+
+ +

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

+ +

+
BT-948
+
+
BT-958
+
+
BT-958D
+

+
+
+ +

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

+ +

+
BT-946C
+
+
BT-956C
+
+
BT-956CD
+
+
BT-445C
+
+
BT-747C
+
+
BT-757C
+
+
BT-757CD
+
+
BT-545C
+
+
BT-540CF
+

+
+
+ +

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

+ +

+
BT-445S
+
+
BT-747S
+
+
BT-747D
+
+
BT-757S
+
+
BT-757D
+
+
BT-545S
+
+
BT-542D
+
+
BT-742A
+
+
BT-542B
+

+
+
+ +

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

+ +

+
BT-742A
+
+
BT-542B
+

+
+
+ +

+

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

+

+ +

+

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

+

+ +

+

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

+

+ +

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

+ +

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

+ +

+
PM1554
+
+
PM2554
+
+
PM2654
+
+
PM2865
+
+
PM2754
+
+
PM3755
+
+
PM3757
+

+
+
+ +

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

+ +

+
MegaRAID Series 418
+
+
MegaRAID Enterprise 1200 (Series 428)
+
+
MegaRAID Enterprise 1300 (Series 434)
+
+
MegaRAID Enterprise 1400 (Series 438)
+
+
MegaRAID Enterprise 1500 (Series 467)
+
+
MegaRAID Enterprise 1600 (Series 471)
+
+
MegaRAID Elite 1500 (Series 467)
+
+
MegaRAID Elite 1600 (Series 493)
+
+
MegaRAID Express 100 (Series 466WS)
+
+
MegaRAID Express 200 (Series 466)
+
+
MegaRAID Express 300 (Series 490)
+
+
MegaRAID Express 500 (Series 475)
+
+
Dell PERC
+
+
Dell PERC 2/SC
+
+
Dell PERC 2/DC
+
+
Dell PERC 3/DCL
+
+
HP NetRaid-1si
+
+
HP NetRaid-3si
+
+
HP Embedded NetRaid
+

+ +

+

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

+

+
+
+ +

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

+ +

+
DAC960P
+
+
DAC960PD
+
+
DAC960PDU
+
+
DAC960PL
+
+
DAC960PJ
+
+
DAC960PG
+
+
AcceleRAID 150
+
+
AcceleRAID 250
+
+
eXtremeRAID 1100
+

+ +

+

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

+

+
+
+ +

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

+ +

+
AcceleRAID 160
+
+
AcceleRAID 170
+
+
AcceleRAID 352
+
+
eXtremeRAID 2000
+
+
eXtremeRAID 3000
+

+ +

+

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

+

+
+
+ +

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

+ +

+
5000 series
+
+
6000 series
+
+
7000 series
+

+
+
+ +

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

+ +

+
ASUS SC-200, SC-896
+
+
Data Technology DTC3130 (all variants)
+
+
DawiControl DC2976UW
+
+
Diamond FirePort (all)
+
+
NCR cards (all)
+
+
Symbios cards (all)
+
+
Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, + and 390U3W
+
+
Tyan S1365
+

+
+
+ +

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

+ +

+
IO DATA PCSC-DV
+
+
KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004
+
+
Macnica Miracle SCSI-II mPS110
+
+
Media Intelligent MSC-110, MSC-200
+
+
NEC PC-9801N-J03R
+
+
New Media Corporation BASICS SCSI
+
+
Qlogic Fast SCSI
+
+
RATOC REX-9530, REX-5572 (as SCSI only)
+

+
+
+ +

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

+ +

+
Future Domain SCSI2GO
+
+
IBM SCSI PCMCIA Card
+
+
ICM PSC-2401 SCSI
+
+
Melco IFC-SC
+
+
RATOC REX-5536, REX-5536AM, REX-5536M, + REX-9836A
+

+
+
+ +

Qlogic controllers and variants ( + isp(4) driver)

+ +

+
Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters
+
+
Qlogic 1240 dual Ultra SCSI controllers
+
+
Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers
+
+
Qlogic 12160 Ultra3 LVD controllers
+
+
Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers
+
+
Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers
+
+
Performance Technology SBS440 ISP1000 variants
+
+
Performance Technology SBS450 ISP1040 variants
+
+
Performance Technology SBS470 ISP2100 variants
+
+
Antares Microsystems P-0033 ISP2100 variants
+

+
+
+ +

DTC 3290 EISA SCSI controller in 1542 emulation + mode.

+ +

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

+ +

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

+ +

+
Alpha-Data AD-PCS201
+
+
IO DATA CBSC16
+

+
+
+ +

Parallel to SCSI interfaces ( + vpo(4) driver)

+ +

+
AIC 7110 SCSI controller (built-in to Iomega ZIP + drive)
+
+
Iomega Jaz Traveller interface
+
+
Iomega MatchMaker SCSI interface (built-in to + Iomega ZIP+ drive)
+

+
+
+ +

SCSI adapters utilizing the Command Interface for + SCSI-3 Support (ciss driver)

+ +

+
Compaq Smart Array 5* series (5300, 5i, 532)
+

+
+
+ +

Intel Integrated RAID Controllers (iir driver)

+ +

+
Intel RAID Controller SRCMR
+
+
ICP Vortex SCSI RAID controllers (all + Wide/Ultra160, 32-bit/64-bit PCI models)
+

+
+
+ +

Promise SuperTrak ATA RAID controllers ( + pst(4) driver)

+ +

+
Promise SuperTrak SX6000 ATA RAID controller
+

+
+
+ +

LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)

+ +

+
LSI FC909, FC929
+
+
LSI 53c1020, 53c1030
+

+
+
+ +

PCI SCSI host adapters using the Tekram TRM-S1040 SCSI + chipset (trm driver)

+ +

+
Tekram DC395U/UW/F
+
+
Tekram DC315U
+

+
+
+ +

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

+ +

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

+ +

+
SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) ( + cd(4))
+
+
Sony proprietary interface (all models) ( + scd(4))
+
+
ATAPI IDE interface ( + acd(4))
+

+
+
+ +

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

+ +

+
NCR5380/NCR53400 (``ProAudio Spectrum'') SCSI + controller
+
+
UltraStor 14F, 24F and 34F SCSI controllers.
+ +
+
+
Note: 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.
+
+
+
+
+
+
Seagate ST01/02 SCSI controllers
+
+
Future Domain 8xx/950 series SCSI controllers
+
+
WD7000 SCSI controller
+

+
+
+ +

The following device is unmaintained:

+ +

+
Mitsumi proprietary CD-ROM interface (all models) + ( + mcd(4))
+

+
+
+

+ +

+

+ +

3.2 Ethernet + Interfaces

+ +

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

+ +

+
ANA-62011 64-bit single port 10/100baseTX + adapter
+
+
ANA-62022 64-bit dual port 10/100baseTX + adapter
+
+
ANA-62044 64-bit quad port 10/100baseTX + adapter
+
+
ANA-69011 32-bit single port 10/100baseTX + adapter
+
+
ANA-62020 64-bit single port 100baseFX adapter
+

+
+
+ +

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

+ +

+
CONTEC C-NET(PC)C PCMCIA Ethernet
+
+
Fujitsu MBH10303, MBH10302 Ethernet PCMCIA
+
+
Fujitsu Towa LA501 Ethernet
+
+
Fujitsu FMV-J182, FMV-J182A
+
+
RATOC REX-5588, REX-9822, REX-4886, and + REX-R280
+
+
Eiger Labs EPX-10BT
+
+
HITACHI HT-4840-11
+
+
NextCom J Link NC5310
+
+
TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
+

+
+
+ +

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

+ +

+
3Com 3c985-SX (Tigon 1 and 2)
+
+
Alteon AceNIC (Tigon 1 and 2)
+
+
Alteon AceNIC 1000baseT (Tigon 2)
+
+
Asante PCI 1000BASE-SX Gigabit Ethernet + Adapter
+
+
Asante GigaNIX1000T Gigabit Ethernet Adapter
+
+
DEC/Compaq EtherWORKS 1000
+
+
Farallon PN9000SX
+
+
NEC Gigabit Ethernet
+
+
Netgear GA620 (Tigon 2)
+
+
Netgear GA620T (Tigon 2, 1000baseT)
+
+
Silicon Graphics Gigabit Ethernet
+

+
+
+ +

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

+ +

+
AMD PCnet/PCI (79c970 & 53c974 or 79c974)
+
+
AMD PCnet/FAST
+
+
Isolan AT 4141-0 (16 bit)
+
+
Isolink 4110 (8 bit)
+
+
PCnet/FAST+
+
+
PCnet/FAST III
+
+
PCnet/PRO
+
+
PCnet/Home
+
+
HomePNA
+

+
+
+ +

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

+ +

+
SMC EtherPower II 9432 series
+

+
+
+ +

National Semiconductor DS8390-based Ethernet NICs, + including Novell NE2000 and clones ( + ed(4) driver)

+ +

+
3C503 Etherlink II ( + ed(4) driver)
+
+
DEC Etherworks DE305
+
+
Hewlett-Packard PC Lan+ 27247B and 27252A
+
+
NetVin 5000
+
+
Novell NE1000, NE2000, and NE2100
+
+
RealTek 8029
+
+
SMC Elite 16 WD8013 Ethernet interface
+
+
SMC Elite Ultra
+
+
SMC WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, + WD8003SBT and WD8013EBT and clones
+
+
Surecom NE-34
+
+
VIA VT86C926
+
+
Winbond W89C940
+

+
+
+ +

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

+ +

+
AR-P500 Ethernet
+
+
Accton EN2212/EN2216/UE2216
+
+
Allied Telesis CentreCOM LA100-PCM_V2
+
+
AmbiCom 10BaseT card
+
+
BayNetworks NETGEAR FA410TXC Fast Ethernet
+
+
CNet BC40 adapter
+
+
COREGA Ether PCC-T/EtherII PCC-T/FEther + PCC-TXF/PCC-TXD
+
+
Compex Net-A adapter
+
+
CyQ've ELA-010
+
+
D-Link DE-650/660
+
+
Danpex EN-6200P2
+
+
Elecom Laneed LD-CDL/TX, LD-CDF, LD-CDS, + LD-10/100CD, LD-CDWA (DP83902A), MACNICA Ethernet ME1 + for JEIDA
+
+
IO DATA PCLATE
+
+
IBM Creditcard Ethernet I/II
+
+
IC-CARD Ethernet/IC-CARD+ Ethernet
+
+
Kingston KNE-PC2, KNE-PCM/x Ethernet
+
+
Linksys EC2T/PCMPC100/PCM100, PCMLM56, EtherFast + 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 + V2)
+
+
Melco + LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX
+
+
NDC Ethernet Instant-Link
+
+
National Semiconductor InfoMover NE4100
+
+
NetGear FA-410TX
+
+
Network Everywhere Ethernet 10BaseT PC Card
+
+
Planex FNW-3600-T
+
+
Socket LP-E
+
+
Surecom EtherPerfect EP-427
+
+
TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card
+
+
Telecom Device SuperSocket RE450T
+

+
+
+ +

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

+ +

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

+ +

+
Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)
+
+
Allied Telesyn AT2550
+
+
Allied Telesyn AT2500TX
+
+
D-Link DFE-530TX+, DFE-538TX
+
+
Farallon NetLINE 10/100 PCI
+
+
Genius GF100TXR (RTL8139)
+
+
KTX-9130TX 10/100 Fast Ethernet
+
+
NDC Communications NE100TX-E
+
+
Netronix Inc. EA-1210 NetEther 10/100
+
+
OvisLink LEF-8129TX
+
+
OvisLink LEF-8139TX
+
+
SMC EZ Card 10/100 PCI 1211-TX
+

+
+
+ +

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

+ +

+
Kingston KNE110TX
+
+
LinkSys EtherFast LNE100TX
+
+
Matrox FastNIC 10/100
+
+
NetGear FA310-TX Rev. D1
+

+
+
+ +

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

+ +

+
Accton EN1217 (98715A)
+
+
Adico AE310TX (98715A)
+
+
Compex RL100-TX (98713 or 98713A)
+
+
CNet Pro120A (98713 or 98713A)
+
+
CNet Pro120B (98715)
+
+
NDC Communications SFA100A (98713A)
+
+
SVEC PN102TX (98713)
+

+
+
+ +

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

+ +

+
LinkSys EtherFast LNE100TX Version 2
+

+
+
+ +

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

+ +

+
Trendware TE100-PCIE
+

+
+
+ +

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

+ +

+
AOpen/Acer ALN-320
+
+
D-Link DFE-530TX
+
+
Hawking Technologies PN102TX
+

+
+
+ +

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

+ +

+
SiS 630, 635 and 735 motherboard chipsets
+

+
+
+ +

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

+ +

+
NetGear FA311-TX
+
+
NetGear FA312-TX
+

+
+
+ +

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

+ +

+
Addtron AEG320T
+
+
Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T + (64-bit PCI)
+
+
Asante FriendlyNet GigaNIC 1000TA and 1000TPC
+
+
D-Link DGE-500T
+
+
LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit + PCI)
+
+
Netgear GA621 and GA622T
+
+
SMC EZ Card 1000 (SMC9462TX)
+
+
Surecom Technology EP-320G-TX
+
+
Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 + (64-bit PCI)
+

+
+
+ +

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

+ +

+
D-Link DFE-550TX
+

+
+
+ +

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

+ +

+
SK-9821 1000baseT copper, single port
+
+
SK-9822 1000baseT copper, dual port
+
+
SK-9841 1000baseLX single mode fiber, single + port
+
+
SK-9842 1000baseLX single mode fiber, dual + port
+
+
SK-9843 1000baseSX multimode fiber, single + port
+
+
SK-9844 1000baseSX multimode fiber, dual port
+

+
+
+ +

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

+ +

+
Compaq Netelligent 10, 10/100, 10/100 + Dual-Port
+
+
Compaq Netelligent 10/100 Proliant
+
+
Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP
+
+
Compaq NetFlex 3P, 3P Integrated, 3P w/BNC
+
+
Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP
+
+
Racore 8165 10/100baseTX
+
+
Racore 8148 10baseT/100baseTX/100baseFX + multi-personality
+

+
+
+ +

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

+ +

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

+ +

+
LinkSys EtherFast LNE100TX v4.0/4.1
+

+
+
+ +

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

+ +

+
Abocom UFE1000, DSB650TX_NA
+
+
Accton USB320-EC, SpeedStream
+
+
ADMtek AN986, AN8511
+
+
Billionton USB100, USB100LP, USB100EL, USBE100
+
+
Corega Ether FEther USB-TX, FEther USB-TXS
+
+
D-Link DSB-650, DSB-650TX, DSB-650TX-PNA
+
+
Elsa Microlink USB2Ethernet
+
+
I/O Data USB ETTX
+
+
Kingston KNU101TX
+
+
LinkSys USB10T, USB10TA, USB10TX, USB100TX, + USB100H1
+
+
Melco Inc. LUA-TX, LUA2-TX
+
+
Siemens Speedstream
+
+
SmartBridges smartNIC
+
+
SMC 2202USB
+
+
SOHOware NUB100
+

+
+
+ +

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

+ +

+
Belkin F5U011, F5U111
+
+
CATC Netmate, Netmate II
+
+
SmartBridges SmartLink
+

+
+
+ +

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

+ +

+
3Com 3c19250
+
+
AOX USB101
+
+
Abocom URE 450
+
+
ADS Technologies USB-10BT
+
+
ATen UC10T
+
+
Corega USB-T
+
+
D-Link DSB-650C
+
+
Entrega NET-USB-E45
+
+
I/O Data USB ETT
+
+
Kawasaki DU-H3E
+
+
LinkSys USB10T
+
+
Netgear EA101
+
+
Peracom USB Ethernet Adapter
+
+
SMC 2102USB, 2104USB
+

+
+
+ +

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

+ +

+
Alfa Inc. GFC2204
+
+
CNet Pro110B
+

+
+
+ +

DEC EtherWORKS II and III NICs ( + le(4) driver)

+ +

+
DE200, DE201, DE202, DE422
+
+
DE203, DE204, DE205
+

+
+
+ +

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

+ +

+
Asante
+
+
Cogent EM100FX and EM440TX
+
+
DEC DE425, DE435, DE450, and DE500
+
+
SMC Etherpower 8432T, 9332, and 9334
+
+
ZYNX ZX 3xx
+

+
+
+ +

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

+ +

+
DEC DE500
+
+
Compaq Presario 7900 series built-in Ethernet
+
+
D-Link DFE-570TX
+
+
Kingston KNE100TX
+
+
LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet
+

+
+
+ +

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

+ +

+
Jaton Corporation XpressNet
+

+
+
+ +

Xircom 3201 (Cardbus) ( + dc(4) driver)

+ +

Conexant LANfinity RS7112 (MiniPCI) ( + dc(4) driver)

+ +

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

+ +

+
CONTEC C-NET(PC)C Ethernet
+
+
Eiger Labs EPX-10BT
+
+
Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 + Ethernet PCMCIA
+
+
Fujitsu Towa LA501 Ethernet
+
+
HITACHI HT-4840-11
+
+
NextCom J Link NC5310
+
+
RATOC REX-5588, REX-9822, REX-4886, REX-R280
+
+
TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
+

+
+
+ +

Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs ( + fxp(4) driver)

+ +

+
Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+
Intel InBusiness 10/100 PCI Network Adapter
+
+
Intel PRO/100+ Management Adapter
+
+
Intel Pro/100 VE Desktop Adapter
+
+
Intel Pro/100 M Desktop Adapter
+
+
Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters
+
+
On-board Ethernet NICs on many Intel + motherboards.
+

+
+
+ +

Intel 82595-based Ethernet NICs ( + ex(4) driver)

+ +

+
Intel EtherExpress Pro/10 and Pro/10+ Ethernet
+
+
Olicom OC2220
+

+
+
+ +

Intel 82586-based Ethernet NICs ( + ie(4) driver)

+ +

+
3Com 3C507 Etherlink 16/TP
+
+
AT&T Starlan 10 and Starlan Fiber
+
+
EN100
+
+
Intel EtherExpress 16
+
+
RACAL Interlan NI5210
+

+
+
+ +

3Com 3C5x9 Etherlink III NICs ( + ep(4) driver)

+ +

+
3C509
+
+
3C529 MCA
+
+
3C579 EISA
+
+
3CXE589EC, 3CXE589ET PCMCIA
+
+
3C589/589B/589C/589D/589E/574TX/574B + PC-card/PCMCIA
+
+
Megahertz 3CCFEM556BI, 3CXEM556, 3CCFEM556B
+
+
OfficeConnect 3CXSH572BT
+
+
Farallon EtherMac
+

+
+
+ +

3Com 3C501 8-bit ISA Ethernet NIC ( + el(4) driver)

+ +

3Com Etherlink XL-based NICs ( + xl(4) driver)

+ +

+
3C900/905/905B/905C PCI
+
+
3C556/556B MiniPCI
+
+
3C450-TX HomeConnect adapter
+
+
3c980/3c980B Fast Etherlink XL server adapter
+
+
3cSOHO100-TX OfficeConnect adapter
+
+
3C575TX/575B/XFE575BT/575C/656/656B/656C + (Cardbus)
+
+
Dell Optiplex GX1 on-board 3C918
+
+
Dell On-board 3C920
+
+
Dell Precision on-board 3C905B
+
+
Dell Latitude laptop docking station embedded + 3C905-TX
+

+
+
+ +

3Com 3C59X series NICs ( + vx(4) driver)

+ +

+
3C590 Etherlink III (PCI)
+
+
3C595 Fast Etherlink III (PCI)
+
+
3C592/3C597 (EISA)
+

+
+
+ +

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

+ +

+
IBM Etherjet ISA
+

+
+
+ +

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

+ +

Xircom X3201 (Cardbus) based Ethernet cards, including + the following:

+ +

+
IBM EtherJet Cardbus Adapter
+
+
Intel PRO/100 Mobile Cardbus (versions that use + the X3201 chipset)
+
+
Xircom Cardbus Realport
+
+
Xircom Cardbus Ethernet 10/100
+
+
Xircom Cardbus Ethernet II 10/100
+

+
+
+ +

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

+ +

+
Accton EN2226/Fast EtherCard (16-bit version)
+
+
Compaq Netelligent 10/100 PC Card
+
+
Intel EtherExpress PRO/100 Mobile Adapter (16-bit + version)
+
+
Xircom 10/100 Network PC Card adapter
+
+
Xircom Realport card + modem(Ethernet part)
+
+
Xircom CreditCard Ethernet 10/100
+
+
Xircom CreditCard 10Base-T ``CreditCard Ethernet + Adapter IIps'' (PS-CE2-10)
+
+
Xircom CreditCard Ethernet 10/100 + modem + (Ethernet part)
+

+
+
+ +

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

+ +

+
D-Link DGE-500SX
+
+
SMC TigerCard 1000 (SMC9462SX)
+

+
+
+ +

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

+ +

+
3Com 3CR990-TX-95
+
+
3Com 3CR990-TX-97
+
+
3Com 3CR990B-SRV
+
+
3Com 3CR990B-TXM
+
+
3Com 3CR990SVR95
+
+
3Com 3CR990SVR97
+

+
+
+ +

Gigabit Ethernet NICs based on the Broadcom BCM570x + ( + bge(4) driver)

+ +

+
3Com 3c996-SX, 3c996-T
+
+
Netgear GA302T
+
+
SysKonnect SK-9D21 and 9D41
+
+
Integrated gigabit Ethernet NICs on DELL PowerEdge + 2550 servers
+
+
Integrated gigabit Ethernet NICs on IBM x235 + servers
+

+
+
+ +

Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips ( + gx(4) and + em(4) drivers), plus + NICs supported by the Intel 82540EM, 82544, 82545EM, and + 82546EB controller chips ( + em(4) driver only)

+ +

+
Intel PRO/1000 Gigabit Ethernet
+

+ +

+

+
Note: The + em(4) driver is + officially supported by Intel, but is only supported + on the i386.
+

+

+
+
+ +

Myson Ethernet NICs (my driver)

+ +

+
Myson MTD80X Based Fast Ethernet Card
+
+
Myson MTD89X Based Gigabit Ethernet Card
+

+
+
+

+ +

+

+ +

3.3 FDDI + Interfaces

+ +

DEC DEFPA PCI ( + fpa(4) driver)

+ +

DEC DEFEA EISA ( + fpa(4) driver)

+

+ +

+

+ +

3.4 ATM + Interfaces

+ +

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

+ +

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

+ +

The ATM support in FreeBSD supports the following + signaling protocols:

+ +

+
The ATM Forum UNI 3.1 signaling protocol
+
+
The ATM Forum UNI 3.0 signaling protocol
+
+
The ATM Forum ILMI address registration
+
+
FORE Systems' proprietary SPANS signaling + protocol
+
+
Permanent Virtual Channels (PVCs)
+

+
+
+ +

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

+ +

+
RFC 1483, ``Multiprotocol Encapsulation over ATM + Adaptation Layer 5''
+
+
RFC 1577, ``Classical IP and ARP over ATM''
+
+
RFC 1626, ``Default IP MTU for use over ATM + AAL5''
+
+
RFC 1755, ``ATM Signaling Support for IP over + ATM''
+
+
RFC 2225, ``Classical IP and ARP over ATM''
+
+
RFC 2334, ``Server Cache Synchronization Protocol + (SCSP)''
+
+
Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, + ``A Distributed ATMARP Service Using SCSP''
+

+
+
+ +

Support for an ATM sockets interface is also + provided.

+

+ +

+

+ +

3.5 Wireless Network + Interfaces

+ +

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

+ +

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

+ +

+

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

+

+ +

+
3COM 3crwe737A AirConnect Wireless LAN PC Card
+
+
Accton airDirect WN3301
+
+
Addtron AWA100
+
+
Adtec ADLINK340APC
+
+
Airway 802.11 Adapter
+
+
Avaya Wireless PC Card
+
+
Blue Concentric Circle CF Wireless LAN Model + WL-379F
+
+
BreezeNET PC-DS.11
+
+
Buffalo WLI-CF-S11G
+
+
Cabletron RoamAbout 802.11 DS
+
+
Compaq WL100, WL110
+
+
Corega KK Wireless LAN PCC-11, PCCA-11, + PCCB-11
+
+
D-Link DWL-650
+
+
Dell TrueMobile 1150 Series
+
+
ELECOM Air@Hawk/LD-WL11/PCC
+
+
ELSA AirLancer MC-11
+
+
Farallon Skyline 11Mbps Wireless
+
+
ICOM SL-1100
+
+
IBM High Rate Wireless LAN PC Card
+
+
Intel PRO/Wireless 2011 LAN PC Card
+
+
IO Data WN-B11/PCM
+
+
Laneed Wireless card
+
+
Linksys Instant Wireless WPC11
+
+
Lucent WaveLAN/IEEE 802.11
+
+
Melco Airconnect WLI-PCM-S11, WLI-PCM-L11
+
+
NCR WaveLAN/IEEE 802.11
+
+
NEC Wireless Card CMZ-RT-WP
+
+
NEC Aterm WL11C (PC-WL/11C)
+
+
NEC PK-WL001
+
+
Netgear MA401
+
+
PLANEX GeoWave/GW-NS110
+
+
Proxim Harmony, RangeLAN-DS
+
+
SMC 2632W, 2602W
+
+
Sony PCWA-C100
+
+
TDK LAK-CD011WL
+
+
Toshiba Wireless LAN Card
+
+
US Robotics Wireless Card 2410
+

+
+
+ +

Aironet 802.11 wireless adapters ( + an(4) driver)

+ +

+
Aironet 4500/4800 series (PCMCIA, PCI, and ISA + adapters are all supported)
+
+
Cisco Systems Aironet 340 and 350 series (PCMCIA, + PCI, and ISA adapters are all supported)
+
+
Xircom Wireless Ethernet adapter (rebadged + Aironet)
+

+
+
+ +

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

+ +

+
Webgear Aviator
+
+
Webgear Aviator Pro
+
+
Raytheon Raylink PC Card
+

+
+
+ +

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

+ +

+
BayStack 650 and 660
+
+
Farallon SkyLINE Wireless
+
+
Icom SL-200
+
+
Melco WLI-PCM
+
+
NEL SSMagic
+
+
Netwave AirSurfer Plus and AirSurfer Pro
+
+
ZoomAir 4000
+

+
+
+

+ +

+

+ +

3.6 Miscellaneous + Networks

+ +

Granch SBNI12 point-to-point communications adapters + (sbni driver)

+ +

+
SBNI12-XX and SBNI12D-XX ISA and PCI
+

+
+
+ +

SMC COM90cx6 ARCNET network adapters (cm driver)

+ +

+
SMC 90c26, 90c56, and 90c66 in 90c56 compatability + mode
+

+
+
+

+ +

+

+ +

3.7 ISDN + Interfaces

+ +

AcerISDN P10 ISA PnP (experimental)

+ +

Asuscom ISDNlink 128K ISA

+ +

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

+ +

AVM

+ +

+
A1
+
+
B1 ISA (tested with V2.0)
+
+
B1 PCI (tested with V4.0)
+
+
Fritz!Card classic
+
+
Fritz!Card PnP
+
+
Fritz!Card PCI
+
+
Fritz!Card PCI, Version 2
+
+
T1
+

+
+
+ +

Creatix

+ +

+
ISDN-S0
+
+
ISDN-S0 P&P
+

+
+
+ +

Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA + PnP

+ +

Dr. Neuhaus Niccy Go@ and compatibles

+ +

Dynalink IS64PPH and IS64PPH+

+ +

Eicon Diehl DIVA 2.0 and 2.02

+ +

ELSA

+ +

+
ELSA PCC-16
+
+
QuickStep 1000pro ISA
+
+
MicroLink ISDN/PCI
+
+
QuickStep 1000pro PCI
+

+
+
+ +

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

+ +

Sedlbauer Win Speed

+ +

Siemens I-Surf 2.0

+ +

TELEINT ISDN SPEED No.1 (experimental)

+ +

Teles

+ +

+
S0/8
+
+
S0/16
+
+
S0/16.3
+
+
S0/16.3 PnP
+
+
16.3c ISA PnP (experimental)
+
+
Teles PCI-TJ
+

+
+
+ +

Traverse Technologies NETjet-S PCI

+ +

USRobotics Sportster ISDN TA intern

+ +

Winbond W6692 based PCI cards

+

+ +

+

+ +

3.8 Serial + Interfaces

+ +

``PC standard'' 8250, 16450, and 16550-based serial + ports ( + sio(4) driver)

+ +

AST 4 port serial card using shared IRQ

+ +

ARNET serial cards ( + ar(4) driver)

+ +

+
ARNET 8 port serial card using shared IRQ
+
+
ARNET (now Digiboard) Sync 570/i high-speed + serial
+

+
+
+ +

Boca multi-port serial cards

+ +

+
Boca BB1004 4-Port serial card (Modems not + supported)
+
+
Boca IOAT66 6-Port serial card (Modems + supported)
+
+
Boca BB1008 8-Port serial card (Modems not + supported)
+
+
Boca BB2016 16-Port serial card (Modems + supported)
+

+
+
+ +

Comtrol Rocketport card ( + rp(4) driver)

+ +

Cyclades Cyclom-Y serial board ( + cy(4) driver)

+ +

STB 4 port card using shared IRQ

+ +

DigiBoard intelligent serial cards ( + dgb(4) driver)

+ +

+
DigiBoard PC/Xe series
+
+
DigiBoard PC/Xi series
+

+
+
+ +

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

+ +

+
Avlab Technology, PCI IO 2S
+
+
Moxa Industio CP-114
+
+
Syba Tech Ltd. PCI-4S2P-550-ECP
+
+
Netmos NM9835 PCI-2S-550
+
+
PCCOM dual port RS232/422/485
+
+
SIIG Cyber Serial Dual PCI 16C550
+

+
+
+ +

SDL Communication serial boards

+ +

+
SDL Communications Riscom/8 Serial Board (rc + driver)
+
+
SDL Communications RISCom/N2 and N2pci high-speed + sync serial boards ( + sr(4) driver)
+

+
+
+ +

Stallion Technologies multiport serial boards

+ +

+
EasyIO ( + stl(4) driver)
+
+
EasyConnection 8/32 ( + stl(4) driver)
+
+
EasyConnection 8/64 ( + stli(4) driver)
+
+
ONboard 4/16 ( + stli(4) driver)
+
+
Brumby ( + stli(4) driver)
+

+
+
+ +

Specialix SI/XIO/SX multiport serial cards, with both + the older SIHOST2.x and the new ``enhanced'' (transputer + based, aka JET) host cards (ISA, EISA and PCI are + supported) ( + si(4) driver)

+

+ +

+

+ +

3.9 Audio + Devices

+ +

Advance ( + sbc(4) driver)

+ +

+
Asound 100 and 110
+
+
Logic ALS120 and ALS4000
+

+
+
+ +

CMedia sound chips

+ +

+
CMI8338/CMI8738
+

+
+
+ +

Crystal Semiconductor ( + csa(4) driver)

+ +

+
CS461x/462x Audio Accelerator
+
+
CS428x Audio Controller
+

+
+
+ +

ENSONIQ ( + pcm(4) driver)

+ +

+
AudioPCI ES1370/1371
+

+
+
+ +

ESS

+ +

+
ES1868, ES1869, ES1879 and ES1888 ( + sbc(4) driver)
+
+
Maestro-1, Maestro-2, and Maestro-2E
+
+
Maestro-3/Allegro
+ +
+
+
Note: The Maestro-3/Allegro cannot be + compiled into the FreeBSD kernel due to licensing + restrictions. To use this driver, add the + following line to /boot/loader.conf:
+
```
+    snd_maestro3_load="YES"
+
```
+
+
+

+
+
+ +

ForteMedia fm801

+ +

Gravis ( + gusc(4) driver)

+ +

+
UltraSound MAX
+
+
UltraSound PnP
+

+
+
+ +

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

+ +

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

+ +

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

+ +

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

+ +

S3 Sonicvibes

+ +

Creative Technologies SoundBlaster series ( + sbc(4) driver)

+ +

+
SoundBlaster
+
+
SoundBlaster Pro
+
+
SoundBlaster AWE-32
+
+
SoundBlaster AWE-64
+
+
SoundBlaster AWE-64 GOLD
+
+
SoundBlaster ViBRA-16
+

+
+
+ +

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

+ +

VIA Technologies VT82C686A

+ +

Yamaha

+ +

+
DS1
+
+
DS1e
+

+
+
+

+ +

+

+ +

3.10 Camera and Video + Capture Devices

+ +

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

+ +

+
AverMedia cards
+
+
Hauppauge Wincast TV and WinTV boards (PCI)
+
+
Intel Smart Video Recorder III
+
+
Miro PC TV
+
+
STB TV PCI
+
+
Video Highway XTreme
+
+
VideoLogic Captivator PCI
+

+
+
+ +

Connectix QuickCam

+ +

Cortex1 frame grabber (ctx driver)

+ +

Creative Labs Video Spigot frame grabber (spigot + driver)

+ +

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

+

+ +

+

+ +

3.11 USB Devices

+ +

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

+ +

+

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

+

+ +

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

+ +

+
ALi Aladdin-V
+
+
AMD-756
+
+
CMD Tech 670 & 673
+
+
Intel 82371SB (PIIX3)
+
+
Intel 82371AB and EB (PIIX4)
+
+
Intel 82801AA (ICH)
+
+
Intel 82801AB (ICH0)
+
+
Intel 82801BA/BAM (ICH2)
+
+
Intel 82443MX
+
+
NEC uPD 9210
+
+
OPTi 82C861 (FireLink)
+
+
SiS 5571
+
+
VIA 83C572 USB
+
+
UHCI or OHCI compliant motherboard chipsets (no + exceptions known)
+

+
+
+ +

USB host controllers (PCI)

+ +

+
ADS Electronics PCI plug-in card (2 ports)
+
+
Entrega PCI plug-in card (4 ports)
+

+
+
+ +

Hubs

+ +

+
Andromeda hub
+
+
MacAlly self powered hub (4 ports)
+
+
NEC hub
+

+
+
+ +

Keyboards ( + ukbd(4) driver)

+ +

+
Apple iMac keyboard
+
+
BTC BTC7935 keyboard with PS/2 mouse port
+
+
Cherry G81-3504 keyboard
+
+
Logitech M2452 keyboard
+
+
MacAlly iKey keyboard
+
+
Microsoft keyboard
+
+
Sun Microsystems Type 6 USB keyboard
+

+
+
+ +

Miscellaneous

+ +

+
ActiveWire I/O Board
+
+
Diamond Rio 500, 600, and 800 MP3 players ( + urio(4) driver)
+
+
D-Link DSB-R100 USB Radio (ufm driver)
+

+
+
+ +

Modems ( + umodem(4) driver)

+ +

+
3Com 5605
+
+
Metricom Ricochet GS USB wireless modem
+

+
+
+ +

Mice ( + ums(4) driver)

+ +

+
Agiler Mouse 29UO
+
+
Apple iMac Mouse
+
+
Belkin Mouse
+
+
Chic mouse
+
+
Cypress mouse
+
+
Genius Niche mouse
+
+
Kensington Mouse-in-a-Box
+
+
Logitech wheel mouse (3 buttons)
+
+
Logitech PS/2 / USB mouse (3 buttons)
+
+
MacAlly mouse (3 buttons)
+
+
Microsoft IntelliMouse (3 buttons)
+
+
Sun Microsystems Type 6 USB Mouse
+
+
Trust Ami Mouse (3 buttons)
+

+
+
+ +

Printers and parallel printer conversion cables ( + ulpt(4) driver)

+ +

+
ATen parallel printer adapter
+
+
Belkin F5U002 parallel printer adapter
+
+
Entrega USB-to-parallel printer adapter
+

+
+
+ +

Serial devices

+ +

+
Belkin F5U103 and F5U120 (ubsa driver)
+
+
e-Tek Labs Kwik232 (ubsa driver)
+
+
GoHubs GoCOM232 (ubsa driver)
+
+
Peracom single port serial adapter (ubsa + driver)
+
+
Prolific PL-2303 serial adapter ( + uplcom(4) + driver)
+
+
SUNTAC Slipper U VS-10U ( + uvscom(4) + driver)
+

+
+
+ +

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

+ +

+
Perfection 636U
+
+
HP ScanJet 4100C, 5200C, 6300C
+

+
+
+ +

Storage ( + umass(4) driver)

+ +

+
Iomega USB Zip 100Mb (primitive support still)
+
+
Matshita CF-VFDU03 floppy drive
+
+
Microtech USB-SCSI-HD 50 USB to SCSI cable
+
+
Panasonic floppy drive
+
+
Y-E Data floppy drive (720/1.44/2.88Mb)
+

+
+
+ +

Handspring Visor and other PalmOS devices ( + uvisor(4) driver)

+ +

+
Handspring Visor
+
+
Palm M125, M500, M505
+
+
Sony Clie 4.0 and 4.1
+

+
+
+

+ +

+

+ +

3.12 IEEE 1394 + (Firewire) Devices

+ +

Host Controllers ( + fwohci(4) driver)

+ +

+
Ricoh R5C552 chipset
+
+
Sony CX3022 chipset
+
+
TI TSB12LV22, LV23, 26 and TSB43AA22 chipsets
+
+
uPD72861 chipset
+
+
VIA VT6306 chipset
+

+
+
+ +

Storage ( + sbp(4) driver)

+ +

+
Apple iPod
+
+
Apple Macintosh G4 (target mode)
+

+
+
+

+ +

+

+ +

3.13 Cryptographic + Accelerators

+ +

Accelerators based on the Hifn 7751, 7811, or 7951 + chipsets ( + hifn(4) driver)

+ +

+
Invertex AEON
+
+
Hifn 7751 reference board
+
+
Global Technologies Group PowerCrypt and + XL-Crypt
+
+
NetSec 7751
+
+
Soekris Engineering vpn1201 and vpn1211
+

+
+
+ +

Accelerators based on the Bluesteel 5501 or 5601 + chipsets ( + ubsec(4) driver)

+ +

Accelerators based on the Broadcom BCM5801, BCM5802, + BCM5805, BCM5820, BCM 5821, BCM5822 chipsets ( + ubsec(4) driver)

+

+ +

+

+ +

3.14 + Miscellaneous

+ +

FAX-Modem/PCCARD

+ +

+
Melco IGM-PCM56K/IGM-PCM56KH
+
+
Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal)
+

+
+
+ +

Floppy drives ( + fd(4) driver)

+ +

Genius and Mustek hand scanners

+ +

GPB and Transputer drivers

+ +

Keyboards including:

+ +

+
AT-style keyboards
+
+
PS/2 keyboards
+
+
USB keyboards (specific instances are listed in + the section describing USB + devices)
+

+
+
+ +

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

+ +

Mice including:

+ +

+
Bus mice ( + mse(4) driver)
+
+
PS/2 mice ( + psm(4) driver)
+
+
Serial mice
+
+
USB mice (specific instances are listed in the + section describing USB + devices)
+

+
+
+ +

``PC standard'' parallel ports ( + ppc(4) driver)

+ +

PC-compatible joysticks ( + joy(4) driver)

+ +

PHS Data Communication Card/PCCARD

+ +

+
NTT DoCoMo P-in Comp@ct
+
+
Panasonic KX-PH405
+
+
SII MC-P200
+

+
+
+ +

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

+ +

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

+

FreeBSD/ia64 5.0-DP2 + Hardware Notes

+ +

The FreeBSD Documentation + Project

+ +

+

+ +

+

Table of Contents

2 Supported Processors and + Motherboards

+

3.1 Disk Controllers
3.2 Ethernet + Interfaces
3.3 FDDI Interfaces
3.4 ATM Interfaces
3.5 Wireless Network + Interfaces
3.6 Miscellaneous + Networks
3.7 ISDN Interfaces
3.8 Serial Interfaces
3.9 Audio Devices
3.10 Camera and Video Capture + Devices
3.11 USB Devices
3.12 IEEE 1394 (Firewire) + Devices
3.13 Cryptographic + Accelerators
3.14 Miscellaneous

+

+ +

+
+ + +
This document is in a very preliminary state. It is + incomplete, and is almost certainly not be an accurate + reflection of reality.
+
+

+ +

+

+ +

1 Introduction

+ +

This document contains the hardware compatibility notes + for FreeBSD 5.0-DP2 on the IA-64 hardware platform (also + referred to as FreeBSD/ia64 5.0-DP2). It lists devices + known to work on this platform, as well as some notes on + boot-time kernel customization that may be useful when + attempting to configure support for new devices.

+ +

+

+
Note: This document includes information + specific to the IA-64 hardware platform. Versions of + the hardware compatibility notes for other + architectures will differ in some details.
+

+

+ +

+

+ +

2 Supported Processors + and Motherboards

+ +

Need to write this section.

+

+ +

+

+ +

3 Supported + Devices

+ $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.114 2002/11/07 22:11:00 bmah Exp $ + +

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

+ +

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

+ +

+

+ +

3.1 Disk + Controllers

+ +

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

+ +

+
Acerlabs Aladdin
+
+
AMD 756 ATA66, 766 ATA100, 768 ATA100
+
+
Cenatek Rocket Drive
+
+
CMD 646, 648 ATA66, and 649 ATA100
+
+
Cypress 82C693
+
+
Cyrix 5530 ATA33
+
+
HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133
+
+
Intel PIIX, PIIX3, PIIX4
+
+
Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100
+
+
nVidia nForce ATA100
+
+
Promise ATA100 OEM chip (pdc20265)
+
+
Promise ATA133 OEM chip (pdc20269)
+
+
Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000
+
+
Promise Ultra-33, -66, -100, -133 TX2/TX2000
+
+
ServerWorks ROSB4 ATA33
+
+
ServerWorks CSB5 ATA66/ATA100
+
+
Sil 0680 UDMA6
+
+
SiS 530, 540, 620
+
+
SiS 630, 633, 635, 645, 730, 733, 735, 740, 745, + 750
+
+
SiS 5591 ATA100
+
+
VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100
+
+
VIA 8233, 8235 ATA133
+

+
+
+ +

Qlogic controllers and variants ( + isp(4) driver)

+ +

+
Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters
+
+
Qlogic 1240 dual Ultra SCSI controllers
+
+
Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers
+
+
Qlogic 12160 Ultra3 LVD controllers
+
+
Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers
+
+
Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers
+
+
Performance Technology SBS440 ISP1000 variants
+
+
Performance Technology SBS450 ISP1040 variants
+
+
Performance Technology SBS470 ISP2100 variants
+
+
Antares Microsystems P-0033 ISP2100 variants
+

+
+
+ +

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

+ +

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

+ +

+
SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) ( + cd(4))
+
+
ATAPI IDE interface ( + acd(4))
+

+
+
+

+ +

+

+ +

3.2 Ethernet + Interfaces

+ +

Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs ( + fxp(4) driver)

+ +

+
Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+
Intel InBusiness 10/100 PCI Network Adapter
+
+
Intel PRO/100+ Management Adapter
+
+
Intel Pro/100 VE Desktop Adapter
+
+
Intel Pro/100 M Desktop Adapter
+
+
Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters
+
+
On-board Ethernet NICs on many Intel + motherboards.
+

+
+
+ +

Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips ( + gx(4) and + em(4) drivers), plus + NICs supported by the Intel 82540EM, 82544, 82545EM, and + 82546EB controller chips ( + em(4) driver only)

+ +

+
Intel PRO/1000 Gigabit Ethernet
+

+ +

+

+
Note: The + em(4) driver is + officially supported by Intel, but is only supported + on the i386.
+

+

+ +

``PC standard'' 8250, 16450, and 16550-based serial + ports ( + sio(4) driver)

+

+ +

+

+ +

3.14 + Miscellaneous

+ +

Keyboards including:

+ +

+
PS/2 keyboards
+

+
+
+ +

Mice including:

+ +

+
PS/2 mice ( + psm(4) driver)
+
+
Serial mice
+

+
+
+

+

FreeBSD/pc98 5.0-DP2 + Hardware Notes

+ +

The FreeBSD Documentation + Project

+ +

+

+ +

+

Table of Contents

2 Supported Systems

+

3.1 Disk Controllers
3.2 Ethernet + Interfaces
3.3 FDDI Interfaces
3.4 ATM Interfaces
3.5 Wireless Network + Interfaces
3.6 Miscellaneous + Networks
3.7 ISDN Interfaces
3.8 Serial Interfaces
3.9 Audio Devices
3.10 Camera and Video Capture + Devices
3.11 USB Devices
3.12 IEEE 1394 (Firewire) + Devices
3.13 Cryptographic + Accelerators
3.14 Miscellaneous

+

+ +

+

+ +

1 Introduction

+ +

This document contains the hardware compatibility notes + for FreeBSD 5.0-DP2 on the NEC PC-98x1 hardware platform + (also referred to as FreeBSD/pc98 5.0-DP2). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.

+ +

+

+
Note: This document includes information + specific to the NEC PC-98x1 hardware platform. Versions + of the hardware compatibility notes for other + architectures will differ in some details.
+

+

+ +

+

+ +

2 Supported + Systems

+ +

NEC PC-98x1 machines

+ +

EPSON PC-x86 machines (compatible with NEC PC-98x1)

+

+ +

+

+ +

3 Supported + Devices

+ $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.114 2002/11/07 22:11:00 bmah Exp $ + +

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

+ +

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

+ +

+

+ +

3.1 Disk + Controllers

+ +

IDE/ATA controllers (wdc driver)

+ +

+
on-board IDE controller
+

+
+
+ +

Adaptec SCSI Controllers

+ +

+
NEC PC-9801-100 and Adaptec AHA-1030P, 1030B( + aic(4) driver)
+
+
NEC PC-9821Xt13 and RvII26 internal, NEC + PC-9821X-B02L/B09, NEC SV-98/2-B03, Adaptec + AHA-2940J, AHA-2940AU and AHA-2940N ( + ahc(4) driver)
+

+
+
+ +

NEC PC-9801-55, 92 and their compatible C-Bus SCSI + interfaces (bs driver)

+ +

+
NEC PC-9801-55, 92 and their compatibles
+ +
ICM IF-2660
+ +
Midori-Denshi MDC-554NA
+ +
Logitec LHA-N151
+ +
+
+
Note: "flags 0x00000" is necessary in + kernel configuration for DMA transfer mode.
+
+
+
+
I-O DATA SC-98II
+ +
+
+
Note: "flags 0x10000" is necessary in + kernel configuration for DMA transfer mode.
+
+
+
+
TEXA HA-55BS2 and later
+ +
Midori-Denshi MDC-926Rs
+ +
+
+
Note: "flags 0x20000" is necessary in + kernel configuration for Bus-master transfer + mode.
+
+
+
+
ELECOM Bus-master SCSI interfaces
+ +
+
+
Note: "flags 0x30000" is necessary in + kernel configuration for Bus-master transfer + mode.
+
+
+
+
All SMIT transfer type SCSI interfaces
+ +
+
+
Note: "flags 0x40000" is necessary in + kernel configuration for SMIT transfer mode.
+
+
+
+
Logitec LHA-20x series
+ +
ICM IF-2766, IF-2766ET, IF-2767 and IF-2769
+ +
+
+
Note: "flags 0x50000" is necessary in + kernel configuration for Bus-master transfer + mode.
+
+
+

+
+
+ +

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

+ +

+
MELCO IFC-USP, RATOC REX-PCI30 and @Nifty FNECHARD + IFC-USUP-TX ( + adv(4) driver)
+

+
+
+ +

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

+ +

+
I-O DATA SC-98/PCI and SC-PCI ( + ncr(4) driver)
+
+
I-O DATA SC-UPCI and Logitec LHA-521UA ( + sym(4) driver)
+

+
+
+ +

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

+ +

+
IO DATA PCSC-DV
+
+
KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004
+
+
Macnica Miracle SCSI-II mPS110
+
+
Media Intelligent MSC-110, MSC-200
+
+
NEC PC-9801N-J03R
+
+
New Media Corporation BASICS SCSI
+
+
Qlogic Fast SCSI
+
+
RATOC REX-9530, REX-5572 (as SCSI only)
+

+
+
+ +

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

+ +

+
Future Domain SCSI2GO
+
+
IBM SCSI PCMCIA Card
+
+
ICM PSC-2401 SCSI
+
+
Melco IFC-SC
+
+
RATOC REX-5536, REX-5536AM, REX-5536M, + REX-9836A
+

+
+
+ +

Qlogic controllers and variants ( + isp(4) driver)

+ +

+
Qlogic SCSI interface
+

+
+
+ +

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

+ +

+
MELCO IFC-DP
+

+
+
+ +

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

+ +

+
Alpha-Data AD-PCS201
+
+
IO DATA CBSC16
+

+
+
+ +

LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)

+ +

+
LSI FC909, FC929
+
+
LSI 53c1020, 53c1030
+

+
+
+ +

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

+ +

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

+ +

+
SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) ( + cd(4))
+
+
ATAPI IDE interface ( + acd(4))
+

+
+
+

+ +

+

+ +

3.2 Ethernet + Interfaces

+ +

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

+ +

+
ANA-62011 64-bit single port 10/100baseTX + adapter
+
+
ANA-62022 64-bit dual port 10/100baseTX + adapter
+
+
ANA-62044 64-bit quad port 10/100baseTX + adapter
+
+
ANA-69011 32-bit single port 10/100baseTX + adapter
+
+
ANA-62020 64-bit single port 100baseFX adapter
+

+
+
+ +

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

+ +

+
CONTEC C-NET(PC)C PCMCIA Ethernet
+
+
Fujitsu MBH10303, MBH10302 Ethernet PCMCIA
+
+
Fujitsu Towa LA501 Ethernet
+
+
Fujitsu FMV-J182, FMV-J182A
+
+
RATOC REX-5588, REX-9822, REX-4886, and + REX-R280
+
+
Eiger Labs EPX-10BT
+
+
HITACHI HT-4840-11
+
+
NextCom J Link NC5310
+
+
TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
+

+
+
+ +

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

+ +

+
3Com 3c985-SX (Tigon 1 and 2)
+
+
Alteon AceNIC (Tigon 1 and 2)
+
+
Alteon AceNIC 1000baseT (Tigon 2)
+
+
Asante PCI 1000BASE-SX Gigabit Ethernet + Adapter
+
+
Asante GigaNIX1000T Gigabit Ethernet Adapter
+
+
DEC/Compaq EtherWORKS 1000
+
+
Farallon PN9000SX
+
+
NEC Gigabit Ethernet
+
+
Netgear GA620 (Tigon 2)
+
+
Netgear GA620T (Tigon 2, 1000baseT)
+
+
Silicon Graphics Gigabit Ethernet
+

+
+
+ +

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

+ +

+
Contec C-NET(98)S
+
+
PCI NIC using AMD AM79C97x (PCnet-PCI/Fast)
+
+
NEC SV-98/2-B05, B06 (PCI)
+
+
Allied-Telesis LA-PCI (PCI)
+

+
+
+ +

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

+ +

+
SMC EtherPower II 9432 series
+

+
+
+ +

National Semiconductor DS8390-based Ethernet NICs, + including Novell NE2000 and clones ( + ed(4) driver)

+ +

+

+
Note: In kernel configuration, you need to + set flag for non-PCI device.
+

+

+ +

+
Novell NE1000, NE2000, and NE2100
+
+
RealTek 8029
+
+
I-O DATA ET2/T-PCI
+
+
MELCO LGY-PCI-TR
+
+
PLANEX ENW-8300-T
+
+
Allied Telesis LA-98 (flags 0x000000)
+
+
Corega Ether98-T (flags 0x000000)
+
+
SMC EtherEZ98 (flags 0x000000)
+
+
ELECOM LD-BDN, LD-NW801G (flags 0x200000)
+
+
PLANEX EN-2298-C (flags 0x200000)
+
+
MELCO EGY-98 (flags 0x300000)
+
+
Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P + (flags 0x300000)
+
+
MELCO LGY-98, LGH-98, IND-SP, IND-SS, LGY-98-N + (110pin) (flags 0x400000)
+
+
MACNICA NE2098 (flags 0x400000)
+
+
ICM IF-2766ET, IF-2771ET, AD-ET2-T, DT-ET-25, + DT-ET-T5, NB-ET-T (110pin) (flags 0x500000)
+
+
D-Link DE-298, DE-298P (flags 0x500000)
+
+
ELECOM LD-98P (flags 0x500000)
+
+
PLANEX EN-2298-T, EN-2298P-T (flags 0x500000)
+
+
Allied Telesis SIC-98, SIU-98, SIC-98NOTE (110pin) + (flags 0x600000)
+
+
Allied Telesis SIU-98-D (flags 0x610000)
+
+
NEC PC-9801-107, 108 (flags 0x800000)
+
+
I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 + (flags 0x900000)
+
+
MACNICA ME98 (flags 0x900000)
+
+
Kansai KLA-98C/T (flags 0x900000)
+
+
NEC PC-9801-77, 78 (flags 0x910000)
+
+
Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) + (flags 0xa00000)
+
+
Contec C-NET(98)E, C-NET(98)L, C-NET(9N)L (110pin) + (flags 0xb00000)
+
+
Logitec LAN-98T (flags 0xb00000)
+
+
Networld 98X3 (flags 0xd00000)
+
+
Accton EN1644(old model), EN1646(old model), + EN2203(old model) (110pin) (flags 0xd00000)
+
+
Networld EC-98X, EP-98X (flags 0xd10000)
+

+
+
+ +

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

+ +

+
AR-P500 Ethernet
+
+
Accton EN2212/EN2216/UE2216
+
+
Allied Telesis CentreCOM LA100-PCM_V2
+
+
AmbiCom 10BaseT card
+
+
BayNetworks NETGEAR FA410TXC Fast Ethernet
+
+
CNet BC40 adapter
+
+
COREGA Ether PCC-T/EtherII PCC-T/FEther + PCC-TXF/PCC-TXD
+
+
Compex Net-A adapter
+
+
CyQ've ELA-010
+
+
D-Link DE-650/660
+
+
Danpex EN-6200P2
+
+
Elecom Laneed LD-CDL/TX, LD-CDF, LD-CDS, + LD-10/100CD, LD-CDWA (DP83902A), MACNICA Ethernet ME1 + for JEIDA
+
+
IO DATA PCLATE
+
+
IBM Creditcard Ethernet I/II
+
+
IC-CARD Ethernet/IC-CARD+ Ethernet
+
+
Kingston KNE-PC2, KNE-PCM/x Ethernet
+
+
Linksys EC2T/PCMPC100/PCM100, PCMLM56, EtherFast + 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 + V2)
+
+
Melco + LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX
+
+
NDC Ethernet Instant-Link
+
+
National Semiconductor InfoMover NE4100
+
+
NetGear FA-410TX
+
+
Network Everywhere Ethernet 10BaseT PC Card
+
+
Planex FNW-3600-T
+
+
Socket LP-E
+
+
Surecom EtherPerfect EP-427
+
+
TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card
+
+
Telecom Device SuperSocket RE450T
+

+
+
+ +

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

+ +

+
Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)
+
+
SOHO(PRAGMATIC) UE-1211C (PCI)
+

+
+
+ +

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

+ +

+
Accton EN1217 (98715A)
+
+
Adico AE310TX (98715A)
+
+
Compex RL100-TX (98713 or 98713A)
+
+
CNet Pro120A (98713 or 98713A)
+
+
CNet Pro120B (98715)
+
+
NDC Communications SFA100A (98713A)
+
+
SVEC PN102TX (98713)
+

+
+
+ +

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

+ +

+
LinkSys EtherFast LNE100TX Version 2
+

+
+
+ +

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

+ +

+
Trendware TE100-PCIE
+

+
+
+ +

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

+ +

+
MELCO LGY-PCI-TXR (PCI)
+
+
CO-100MV (PCI)
+
+
Corega FastEtherII PCI-TX (PCI)
+

+
+
+ +

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

+ +

+
@Nifty FNECHARD IFC-USUP-TX (PCI)
+
+
MELCO LGY-PCI-TXC (PCI)
+

+
+
+ +

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

+ +

+
NetGear FA311-TX
+
+
NetGear FA312-TX
+

+
+
+ +

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

+ +

+
Addtron AEG320T
+
+
Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T + (64-bit PCI)
+
+
Asante FriendlyNet GigaNIC 1000TA and 1000TPC
+
+
D-Link DGE-500T
+
+
LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit + PCI)
+
+
Netgear GA621 and GA622T
+
+
SMC EZ Card 1000 (SMC9462TX)
+
+
Surecom Technology EP-320G-TX
+
+
Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 + (64-bit PCI)
+

+
+
+ +

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

+ +

+
D-Link DFE-550TX
+

+
+
+ +

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

+ +

+
SK-9821 1000baseT copper, single port
+
+
SK-9822 1000baseT copper, dual port
+
+
SK-9841 1000baseLX single mode fiber, single + port
+
+
SK-9842 1000baseLX single mode fiber, dual + port
+
+
SK-9843 1000baseSX multimode fiber, single + port
+
+
SK-9844 1000baseSX multimode fiber, dual port
+

+
+
+ +

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

+ +

+
Compaq Netelligent 10, 10/100, 10/100 + Dual-Port
+
+
Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP
+
+
Compaq NetFlex 3P, 3P Integrated, 3P w/BNC
+
+
Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP
+
+
Racore 8165 10/100baseTX
+
+
Racore 8148 10baseT/100baseTX/100baseFX + multi-personality
+

+
+
+ +

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

+ +

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

+ +

+
LinkSys EtherFast LNE100TX v4.0/4.1
+

+
+
+ +

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

+ +

+
Abocom UFE1000, DSB650TX_NA
+
+
Accton USB320-EC, SpeedStream
+
+
ADMtek AN986, AN8511
+
+
Billionton USB100, USB100LP, USB100EL, USBE100
+
+
Corega Ether FEther USB-TX, FEther USB-TXS
+
+
D-Link DSB-650, DSB-650TX, DSB-650TX-PNA
+
+
Elsa Microlink USB2Ethernet
+
+
I/O Data USB ETTX
+
+
Kingston KNU101TX
+
+
LinkSys USB10T, USB10TA, USB10TX, USB100TX, + USB100H1
+
+
Melco Inc. LUA-TX, LUA2-TX
+
+
Siemens Speedstream
+
+
SmartBridges smartNIC
+
+
SMC 2202USB
+
+
SOHOware NUB100
+

+
+
+ +

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

+ +

+
Belkin F5U011, F5U111
+
+
CATC Netmate, Netmate II
+
+
SmartBridges SmartLink
+

+
+
+ +

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

+ +

+
3Com 3c19250
+
+
AOX USB101
+
+
Abocom URE 450
+
+
ADS Technologies USB-10BT
+
+
ATen UC10T
+
+
Corega USB-T
+
+
D-Link DSB-650C
+
+
Entrega NET-USB-E45
+
+
I/O Data USB ETT
+
+
Kawasaki DU-H3E
+
+
LinkSys USB10T
+
+
Netgear EA101
+
+
Peracom USB Ethernet Adapter
+
+
SMC 2102USB, 2104USB
+

+
+
+ +

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

+ +

+
Alfa Inc. GFC2204
+
+
CNet Pro110B
+

+
+
+ +

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

+ +

+
Asante
+
+
Cogent EM100FX and EM440TX
+
+
DEC DE425, DE435, DE450, and DE500
+
+
SMC Etherpower 8432T, 9332, and 9334
+
+
ZYNX ZX 3xx
+
+
I-O DATA LA2/T-PCI (PCI)
+
+
ELECOM LD-PCI2T, LD-PCITS (PCI)
+
+
Corega FastEther PCI-TX (PCI)
+

+
+
+ +

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

+ +

+
DEC DE500
+
+
Compaq Presario 7900 series built-in Ethernet
+
+
D-Link DFE-570TX
+
+
Kingston KNE100TX
+
+
LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet
+

+
+
+ +

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

+ +

+
Jaton Corporation XpressNet
+

+
+
+ +

Cnet Pro120A (PCI) ( + dc(4) driver)

+ +

MELCO LGY-PCI-TXL (PCI) ( + dc(4) driver)

+ +

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

+ +

+
Allied Telesis RE1000, RE1000Plus, ME1500 + (110pin)
+
+
Contec C-NET(98)P2, C-NET(9N)E (110pin), + C-NET(9N)C(ExtCard)
+
+
Ungermann-Bass Access/PC N98C+(PC85152,PC85142), + Access/NOTE N98 (PC86132) (110pin)
+
+
TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 + (110pin)
+
+
Ratoc REX-9880/9881/9882/9883
+

+
+
+ +

Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs ( + fxp(4) driver)

+ +

+
Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+
Intel PRO/100+ Management Adapter
+
+
Intel Pro/100 VE Desktop Adapter
+
+
Intel Pro/100 M Desktop Adapter
+
+
Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters
+
+
On-board Ethernet NICs on many Intel + motherboards.
+
+
NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal + 100Base-TX (PCI)
+
+
NEC PC-9821X-B06 (PCI)
+
+
Contec C-NET(PI)-100TX (PCI)
+

+
+
+ +

3Com 3C5x9 Etherlink III NICs ( + ep(4) driver)

+ +

+
3Com 3C569, 3C569-TPO, 3C569B, 3C569B-COMBO
+

+
+
+ +

3Com Etherlink XL-based NICs ( + xl(4) driver)

+ +

+
3C900/905/905B/905C PCI
+

+
+
+ +

3Com 3C59X series NICs ( + vx(4) driver)

+ +

+
3C590 Etherlink III (PCI)
+
+
3C595 Fast Etherlink III (PCI)
+

+
+
+ +

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

+ +

+
NEC PC-9801-83, -84, -103, and -104
+
+
NEC PC-9801N-25 and -J02R
+

+
+
+ +

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

+ +

+
D-Link DGE-500SX
+
+
SMC TigerCard 1000 (SMC9462SX)
+

+
+
+ +

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

+ +

+
3Com 3CR990-TX-95
+
+
3Com 3CR990-TX-97
+
+
3Com 3CR990B-SRV
+
+
3Com 3CR990B-TXM
+
+
3Com 3CR990SVR95
+
+
3Com 3CR990SVR97
+

+
+
+ +

Gigabit Ethernet NICs based on the Broadcom BCM570x + ( + bge(4) driver)

+ +

+
3Com 3c996-SX, 3c996-T
+
+
Netgear GA302T
+
+
SysKonnect SK-9D21 and 9D41
+
+
Integrated gigabit Ethernet NICs on DELL PowerEdge + 2550 servers
+
+
Integrated gigabit Ethernet NICs on IBM x235 + servers
+

+
+
+ +

Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips ( + gx(4) and + em(4) drivers), plus + NICs supported by the Intel 82540EM, 82544, 82545EM, and + 82546EB controller chips ( + em(4) driver only)

+ +

+
Intel PRO/1000 Gigabit Ethernet
+

+ +

+

+
Note: The + em(4) driver is + officially supported by Intel, but is only supported + on the i386.
+

+

+
+
+ +

Myson Ethernet NICs (my driver)

+ +

+
Myson MTD80X Based Fast Ethernet Card
+
+
Myson MTD89X Based Gigabit Ethernet Card
+

+
+
+

+ +

+

+ +

3.3 FDDI + Interfaces

+ +

DEC DEFPA PCI ( + fpa(4) driver)

+

+ +

+

+ +

3.4 ATM + Interfaces

+ +

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

+ +

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

+ +

The ATM support in FreeBSD supports the following + signaling protocols:

+ +

+
The ATM Forum UNI 3.1 signaling protocol
+
+
The ATM Forum UNI 3.0 signaling protocol
+
+
The ATM Forum ILMI address registration
+
+
FORE Systems' proprietary SPANS signaling + protocol
+
+
Permanent Virtual Channels (PVCs)
+

+
+
+ +

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

+ +

+
RFC 1483, ``Multiprotocol Encapsulation over ATM + Adaptation Layer 5''
+
+
RFC 1577, ``Classical IP and ARP over ATM''
+
+
RFC 1626, ``Default IP MTU for use over ATM + AAL5''
+
+
RFC 1755, ``ATM Signaling Support for IP over + ATM''
+
+
RFC 2225, ``Classical IP and ARP over ATM''
+
+
RFC 2334, ``Server Cache Synchronization Protocol + (SCSP)''
+
+
Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, + ``A Distributed ATMARP Service Using SCSP''
+

+
+
+ +

Support for an ATM sockets interface is also + provided.

+

+ +

+

+ +

3.5 Wireless Network + Interfaces

+ +

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

+ +

+

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

+

+ +

+
3COM 3crwe737A AirConnect Wireless LAN PC Card
+
+
Accton airDirect WN3301
+
+
Addtron AWA100
+
+
Adtec ADLINK340APC
+
+
Airway 802.11 Adapter
+
+
Avaya Wireless PC Card
+
+
Blue Concentric Circle CF Wireless LAN Model + WL-379F
+
+
BreezeNET PC-DS.11
+
+
Buffalo WLI-CF-S11G
+
+
Cabletron RoamAbout 802.11 DS
+
+
Compaq WL100, WL110
+
+
Corega KK Wireless LAN PCC-11, PCCA-11, + PCCB-11
+
+
D-Link DWL-650
+
+
Dell TrueMobile 1150 Series
+
+
ELECOM Air@Hawk/LD-WL11/PCC
+
+
ELSA AirLancer MC-11
+
+
Farallon Skyline 11Mbps Wireless
+
+
ICOM SL-1100
+
+
IBM High Rate Wireless LAN PC Card
+
+
Intel PRO/Wireless 2011 LAN PC Card
+
+
IO Data WN-B11/PCM
+
+
Laneed Wireless card
+
+
Linksys Instant Wireless WPC11
+
+
Lucent WaveLAN/IEEE 802.11
+
+
Melco Airconnect WLI-PCM-S11, WLI-PCM-L11
+
+
NCR WaveLAN/IEEE 802.11
+
+
NEC Wireless Card CMZ-RT-WP
+
+
NEC Aterm WL11C (PC-WL/11C)
+
+
NEC PK-WL001
+
+
Netgear MA401
+
+
PLANEX GeoWave/GW-NS110
+
+
Proxim Harmony, RangeLAN-DS
+
+
SMC 2632W, 2602W
+
+
Sony PCWA-C100
+
+
TDK LAK-CD011WL
+
+
Toshiba Wireless LAN Card
+
+
US Robotics Wireless Card 2410
+

+
+
+ +

Aironet 802.11 wireless adapters ( + an(4) driver)

+ +

+
Aironet 4500/4800 series (PCMCIA, PCI, and ISA + adapters are all supported)
+
+
Cisco Systems Aironet 340 and 350 series (PCMCIA, + PCI, and ISA adapters are all supported)
+
+
Xircom Wireless Ethernet adapter (rebadged + Aironet)
+

+
+
+ +

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

+ +

+
Webgear Aviator
+
+
Webgear Aviator Pro
+
+
Raytheon Raylink PC Card
+

+
+
+ +

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

+ +

+
BayStack 650 and 660
+
+
Farallon SkyLINE Wireless
+
+
Icom SL-200
+
+
Melco WLI-PCM
+
+
NEL SSMagic
+
+
Netwave AirSurfer Plus and AirSurfer Pro
+
+
ZoomAir 4000
+

+
+
+

+ +

+

+ +

3.6 Miscellaneous + Networks

+

+ +

+

+ +

3.7 ISDN + Interfaces

+

+ +

+

+ +

3.8 Serial + Interfaces

+ +

Internel serial interfaces ( + sio(4) driver)

+ +

+
PC-9801 on-board
+
+
PC-9821 2'nd CCU (flags 0x12000000)
+

+
+
+ +

NEC PC-9861K, PC-9801-101 and Midori-Denshi MDC-926Rs + ( + sio(4) driver)

+ +

+
COM2 (flags 0x01000000)
+
+
COM3 (flags 0x02000000)
+

+
+
+ +

NEC PC-9801-120 ( + sio(4) driver)

+ +

+

+
Note: "flags 0x11000000" is necessary in + kernel configuration.
+

+

+ +

Microcore MC-16550, MC-16550II, MC-RS98 ( + sio(4) driver)

+ +

+

+
Note: "flags 0x14000?01" is necessary in + kernel configuration.
+

+

+ +

Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 + ( + sio(4) driver)

+ +

+

+
Note: "flags 0x15000?01" is necessary in + kernel configuration.
+

+

+ +

Media Intelligent RSB-384 ( + sio(4) driver)

+ +

+

+
Note: "flags 0x16000001" is necessary in + kernel configuration.
+

+

+ +

I-O DATA RSA-98III ( + sio(4) driver)

+ +

+

+
Note: "flags 0x18000?01" is necessary in + kernel configuration.
+

+

+ +

Hayes ESP98 ( + sio(4) driver)

+ +

+

+
Note: "options COM_ESP" and "flags + 0x19000000" are necessary in kernel + configuration.
+

+

+ +

+

+ +

3.9 Audio + Devices

+ +

NEC PC-9801-73, 86 and compatibles (nss driver)

+ +

+
NEC A-MATE internal sound
+
+
Q-Vision WaveStar, WaveMaster
+

+
+
+ +

NEC X-MATE, CanBe, ValueStar internal (mss driver)

+ +

Creative Technologies SoundBlaster(98) ( + sb(4) driver)

+ +

I-O DATA CD-BOX ( + sb(4) driver)

+ +

Software PCM using beep (pca driver)

+ +

MPU-401 and compatible interfaces (mpu driver)

+ +

+
Q-Vision WaveStar
+

+
+
+ +

joystick port of SoundBlaster(98) ( + joy(4) driver)

+

+ +

+

+ +

3.10 Camera and Video + Capture Devices

+ +

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

+ +

+
AverMedia cards
+
+
Hauppauge Wincast TV and WinTV boards (PCI)
+
+
Intel Smart Video Recorder III
+
+
Miro PC TV
+
+
STB TV PCI
+
+
Video Highway XTreme
+
+
VideoLogic Captivator PCI
+

+
+
+

+ +

+

+ +

3.11 USB Devices

+ +

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

+ +

+

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

+

+ +

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

+ +

+
NEC PC-9821V200 etc ( + ohci(4) driver)
+

+
+
+ +

USB host controllers (PCI)

+ +

+
TRY CORPORATION JUS-02 ( + uhci(4) driver)
+

+
+
+ +

Hubs

+ +

+
Andromeda hub
+
+
MacAlly self powered hub (4 ports)
+
+
NEC hub
+

+
+
+ +

Keyboards ( + ukbd(4) driver)

+ +

+
Apple iMac keyboard
+
+
BTC BTC7935 keyboard with PS/2 mouse port
+
+
Cherry G81-3504 keyboard
+
+
Logitech M2452 keyboard
+
+
MacAlly iKey keyboard
+
+
Microsoft keyboard
+
+
Sun Microsystems Type 6 USB keyboard
+

+
+
+ +

Miscellaneous

+ +

+
ActiveWire I/O Board
+
+
Diamond Rio 500, 600, and 800 MP3 players ( + urio(4) driver)
+
+
D-Link DSB-R100 USB Radio (ufm driver)
+

+
+
+ +

Modems ( + umodem(4) driver)

+ +

+
3Com 5605
+
+
Metricom Ricochet GS USB wireless modem
+

+
+
+ +

Mice ( + ums(4) driver)

+ +

+
Agiler Mouse 29UO
+
+
Apple iMac Mouse
+
+
Belkin Mouse
+
+
Chic mouse
+
+
Cypress mouse
+
+
Genius Niche mouse
+
+
Kensington Mouse-in-a-Box
+
+
Logitech wheel mouse (3 buttons)
+
+
Logitech PS/2 / USB mouse (3 buttons)
+
+
MacAlly mouse (3 buttons)
+
+
Microsoft IntelliMouse (3 buttons)
+
+
Sun Microsystems Type 6 USB Mouse
+
+
Trust Ami Mouse (3 buttons)
+

+
+
+ +

Printers and parallel printer conversion cables ( + ulpt(4) driver)

+ +

+
ATen parallel printer adapter
+
+
Belkin F5U002 parallel printer adapter
+
+
Entrega USB-to-parallel printer adapter
+

+
+
+ +

Serial devices

+ +

+
Belkin F5U103 and F5U120 (ubsa driver)
+
+
e-Tek Labs Kwik232 (ubsa driver)
+
+
GoHubs GoCOM232 (ubsa driver)
+
+
Peracom single port serial adapter (ubsa + driver)
+
+
Prolific PL-2303 serial adapter ( + uplcom(4) + driver)
+
+
SUNTAC Slipper U VS-10U ( + uvscom(4) + driver)
+

+
+
+ +

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

+ +

+
Perfection 636U
+
+
HP ScanJet 4100C, 5200C, 6300C
+

+
+
+ +

Storage ( + umass(4) driver)

+ +

+
Iomega USB Zip 100Mb (primitive support still)
+
+
Matshita CF-VFDU03 floppy drive
+
+
Microtech USB-SCSI-HD 50 USB to SCSI cable
+
+
Panasonic floppy drive
+
+
Y-E Data floppy drive (720/1.44/2.88Mb)
+

+
+
+ +

Handspring Visor and other PalmOS devices ( + uvisor(4) driver)

+ +

+
Handspring Visor
+
+
Palm M125, M500, M505
+
+
Sony Clie 4.0 and 4.1
+

+
+
+

+ +

+

+ +

3.12 IEEE 1394 + (Firewire) Devices

+ +

Host Controllers ( + fwohci(4) driver)

+ +

+
Ricoh R5C552 chipset
+
+
Sony CX3022 chipset
+
+
TI TSB12LV22, LV23, 26 and TSB43AA22 chipsets
+
+
uPD72861 chipset
+
+
VIA VT6306 chipset
+

+
+
+ +

Storage ( + sbp(4) driver)

+ +

+
Apple iPod
+
+
Apple Macintosh G4 (target mode)
+

+
+
+

+ +

+

+ +

3.13 Cryptographic + Accelerators

+ +

Accelerators based on the Hifn 7751, 7811, or 7951 + chipsets ( + hifn(4) driver)

+ +

+
Invertex AEON
+
+
Hifn 7751 reference board
+
+
Global Technologies Group PowerCrypt and + XL-Crypt
+
+
NetSec 7751
+
+
Soekris Engineering vpn1201 and vpn1211
+

+
+
+ +

Accelerators based on the Bluesteel 5501 or 5601 + chipsets ( + ubsec(4) driver)

+ +

Accelerators based on the Broadcom BCM5801, BCM5802, + BCM5805, BCM5820, BCM 5821, BCM5822 chipsets ( + ubsec(4) driver)

+

+ +

+

+ +

3.14 + Miscellaneous

+ +

FAX-Modem/PCCARD

+ +

+
Melco IGM-PCM56K/IGM-PCM56KH
+
+
Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal)
+

+
+
+ +

Floppy drives ( + fd(4) driver)

+ +

Keyboards including:

+ +

+
Standard keyboards
+
+
USB keyboards (specific instances are listed in + the section describing USB + devices)
+

+
+
+ +

Mice including:

+ +

+
Bus mice ( + mse(4) driver)
+
+
Serial mice
+
+
USB mice (specific instances are listed in the + section describing USB + devices)
+

+
+
+ +

``PC-9821 standard'' parallel ports ( + ppc(4) driver)

+ +

PHS Data Communication Card/PCCARD

+ +

+
NTT DoCoMo P-in Comp@ct
+
+
Panasonic KX-PH405
+
+
SII MC-P200
+

+
+
+ +

Power Management Controller of NEC PC-98 Note (pmc + driver)

+

FreeBSD/sparc64 5.0-DP2 + Hardware Notes

+ +

The FreeBSD Documentation + Project

+ +

+

+ +

+

Table of Contents

2.2 In general, what do you need + to run FreeBSD on a sparc64

2 Supported Systems

+

2.1 Overview

2.3 System-specific + information

+

2.3.1 Ultra 1
2.3.2 Ultra 2
2.3.3 Ultra 5/10
2.3.4 Ultra 60
2.3.5 Blade 100

+

2.4 Supported Hardware + Overview

+

+

3.1 PCI Hardware
3.2 SBus Hardware
3.3 ISA Hardware
3.4 EBus Hardware
3.5 Unsupported + Hardware

+

4 Acknowledgments

+

+ +

+

+ +

1 Introduction

+ +

This document contains the hardware compatibility notes + for FreeBSD 5.0-DP2 on the UltraSPARC hardware platform + (also referred to as FreeBSD/sparc64 5.0-DP2). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.

+ +

+

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

+

+ +

+

+ +

2 Supported + Systems

+ +

Additions, corrections and constructive criticism are + invited. In particular, information on system quirks is + more than welcome.

+ +

+

+ +

2.1 Overview

+ +

This document tries to provide a starting point for + those who want to run FreeBSD on an UltraSPARC-based + machine. It is aimed at providing background information + on the various hardware designs. It is not a replacement + for the systems manuals.

+ +

The information is structured as follows:

+ +

+
General hardware requirements to run FreeBSD on + sparc64.
+
+
System specific information for each of the + systems/boards supported by FreeBSD.
+
+
Information on expansion boards for FreeBSD, + including things that differ from what is in the + generic supported hardware list.
+

+
+
+

+ +

+

+ +

2.2 In general, what do + you need to run FreeBSD on a sparc64

+ +

FreeBSD/sparc64 requires an UltraSPARC system. + Currently, the newer PCI-based systems are supported + better than the older SBus based systems. The following + systems are known to work to varying degrees:

+ +

+
Sun Ultra 1 workstations
+
+
Sun Ultra 2 workstations
+
+
Sun Ultra 5 workstations
+
+
Sun Ultra 10 workstations
+
+
Sun Ultra 30 workstations
+
+
Sun Ultra 60 workstations
+
+
Sun Blade 100 workstations
+
+
Sun Netra t1 series servers
+
+
Sun Enterprise 220R servers
+
+
Sun Enterprise 250 servers
+
+
Sun Enterprise 420R servers
+

+ +

Ultra 80 and Blade 1000 are expected to work, maybe + with minor modifications. SMP is supported on Ultra 2 and + 60 workstations and Enterprise 220R, 250 and 420R + servers.

+

+ +

+

+ +

2.3 System-specific + information

+ +

Below is an overview of the UltraSPARC hardware that + FreeBSD runs on. The GENERIC kernel configuration file in + /sys/sparc64/conf/GENERIC may + contain additional information about supported + devices.

+ +

+

+ +

2.3.1 Ultra + 1

+ +

UltraSPARC Ultra1-family systems have not been + thoroughly tested with FreeBSD. These systems are not + very well supported, but it is possible to install + FreeBSD onto an Ultra-1e with a hme Ethernet interface.

+

+ +

+

+ +

2.3.2 Ultra + 2

+ +

UltraSPARC Ultra2-family systems include the + following hardware:

+ +

+
1 or 2 UltraSPARC II CPUs
+
+
Built-in Ethernet (hme compatible) interface
+
+
4 SBus slots
+
+
1 UPA Slot
+
+
Serial and Parallel ports
+
+
16-bit audio
+

+

+ +

+

+ +

2.3.3 Ultra + 5/10

+ +

UltraSPARC Ultra5/10-family systems include the + following hardware:

+ +

+
UltraSPARC IIi CPU
+
+
Three PCI busses
+
+
Built-in Ethernet (hme compatible) interface
+
+
Built-in PCI-IDE controller (not yet committed - + in Perforce tree)
+
+
Two PC-AT style `com' ports for the mouse and + keyboard
+
+
Floppy driver controller
+
+
Siemens SAB82532 dual-channel serial ports for + ttya and ttyb
+
+
One CS4231 audio device
+
+
One PC-AT style parallel port
+
+
Sun `ffb' frame buffer (Ultra10 only)
+
+
EBus (Sun proprietary bus for slow devices)
+

+

+ +

+

+ +

2.3.4 Ultra + 60

+ +

Sun Ultra 60 workstations include the following + hardware:

+ +

+
1 or 2 UltraSPARC II CPUs
+
+
4 PCI slots
+
+
2 UPA slots
+
+
+ sym(4)-based + UltraSCSI controller
+
+
Built-in Ethernet (hme compatible) interface
+
+
Serial and Parallel ports
+
+
16-bit audio
+
+
EBus (Sun proprietary bus for slow devices)
+

+

+ +

+

+ +

2.3.5 Blade + 100

+ +

Sun Blade 100 workstations include the following + hardware:

+ +

+
UltraSPARC IIe CPU
+
+
Three PCI busses
+
+
Built-in Ethernet (gem compatible) interface
+
+
Two USB ports (unsupported)
+
+
Two Firewire ports (unsupported)
+
+
Built-in PCI-IDE controller (not yet committed - + in Perforce tree)
+
+
Two PC-AT style `com' ports for the mouse and + keyboard
+
+
Floppy driver controller
+
+
+ sio(4) supported + serial ports for ttya and ttyb
+
+
One CS4231 audio device
+
+
One PC-AT style parallel port
+
+
Built-in PGX64 (ATI) graphics
+
+
EBus (Sun proprietary bus for slow devices)
+
+
ISA bus
+

+

+ +

+

+ +

2.4 Supported Hardware + Overview

+ +

A word of caution: the installed base for + FreeBSD/sparc64 is not nearly as large as for + FreeBSD/Intel. This means that the enormous variation of + PCI/ISA expansion cards out there has much less chance of + having been tested on sparc64 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. GENERIC contains things + that are known to work on sparc64 only.

+ +

The PCI bus is fully supported. SBus support is + limited, but is reported to work well enough to netboot + an SBus-based Ultra 2 workstation.

+ +

1.44 Mbyte floppy drives are not yet supported.

+ +

ATA and ATAPI (IDE) devices are supported via the + ata(4) driver + framework. (not yet committed - in Perforce + tree)

+ +

There is full SCSI support via the CAM layer. However, + only NCR/Symbios cards are currently working. Adaptec + 2940x (AIC 7xxx chip-based) and + isp(4) cards should be + supported soon. Be aware that SCSI cards must contain Sun + FCODE in order to use them as a boot device from + OpenBoot.

+ +

If you want to boot your sparc64 over the Ethernet you + will obviously need an Ethernet card that the OpenBoot + console recognizes.

+ +

hme, gem, and eri based network devices.

+ +

The ``PC standard'' serial ports found on most newer + Sun workstations are supported.

+

+ +

+

+ +

3 Supported + Devices

+ $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/sparc64/dev-sparc64.sgml,v + 1.1 2002/02/25 07:25:38 murray Exp $ + +

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

+ +

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

+ +

+

+ +

3.1 PCI + Hardware

+ +

In general, any device for which there is a driver can + be made to work on sparc64. Some drivers might just work, + others might require some changes (because this is the + first big-endian architecture to be supported by + FreeBSD).

+ +

The following drivers are known to work:

+ +

+
apb (Sun PCI-PCI + bridge)
+
+
generic PCI-PCI bridges
+
+
+ ahc(4) (coming real + soon).
+
+
+ ata(4), atadisk, atapicd (but not atapifd, + atapist)
+
+
gem (Sun GEM/ERI + ethernet, on-board on Blade 100)
+
+
hme (Sun HME ethernet, + on-board on Ultra 5, 10)
+
+
+ sio(4)
+
+
+ sym(4)
+

+

+ +

+

+ +

3.2 SBus + Hardware

+ +

The following drivers have SBus front ends:

+ +

+
hme Ethernet
+
+
mk48txx ('eeprom' device; + time-of-day clock)
+

+

+ +

+

+ +

3.3 ISA + Hardware

+ +

The paragraph about PCI drivers apply to ISA drivers + as well, but with the notable exception that ISA DMA is + not yet supported. This are generally on-board devices; + there are no UltraSPARC boxes with ISA slots that the + authors are aware of.

+ +

The following drivers are known to work:

+ +

+
+ sio(4)
+

+

+ +

+

+ +

3.4 EBus + Hardware

+ +

The EBus is specific to Sun hardware, so drivers need + to have support added to work with these devices. It is + quite similar to ISA, so that ISA drivers can usually be + easily ported, provided that they use the bus space + interface, and not in[bwl]/out[bwl] and related + functions. DMA is not yet supported.

+ +

The following drivers are known to work:

+ +

+
+ sio(4)
+
+
mk48txx ('eeprom' device; + time-of-day clock)
+

+

+ +

+

+ +

3.5 Unsupported + Hardware

+ +

The following hardware, which is built-in in Sun + UltraSPARC boxes, is not currently supported:

+ +

+
graphics/frame buffer devices, keyboards (except + indirectly in text mode using the ofw_console device)
+
+
Siemens sab82532 serial ports (Ultra 5/10; the + keyboard/mouse ports are also RS232 ones and + supported by the sio driver though; a driver, 'se', + is being worked on).
+
+
serial keyboards (except indirectly using the ofw_console device)
+
+
Zilog z8530 serial ports (keyboard/mouse, ttya and + ttyb in Ultra 1 and Ultra 2 boxen)
+
+
fas (Fast SCSI controller builtin in most Ultra 1 + and Ultra 2 boxen)
+
+
USB ports (have issues, should be easy to get to + work though)
+
+
all floppy drives/controllers
+
+
smart card readers (the Blade 100 has one, don't + know much about it)
+
+
FireWire/IEEE1394
+
+
sound cards
+
+
parallel ports
+

+

+ +

+

+ +

4 + Acknowledgments

+ +

This document is based in part on the FreeBSD/Alpha and + NetBSD/sparc64 release documentation. Information about + specific system models was obtained from Sun.

+

FreeBSD/alpha 5.0-DP2 + Installation Instructions

+ +

The FreeBSD Project

+ +

+

+ +

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

+ +

+

+ +

1 Installing + FreeBSD

+ +

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

+ +

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

+ +

+

+ +

1.1 Getting + Started

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+

+
Important: While FreeBSD does its best to + safeguard against accidental loss of data, it's still + more than possible to wipe out your entire disk + with this installation if you make a mistake. Please + do not proceed to the final FreeBSD installation menu + unless you've adequately backed up any important data + first.
+

+

+ +

+

+ +

1.2 Hardware + Requirements

+ +

FreeBSD for the Alpha/AXP supports the platforms + described in HARDWARE.TXT.

+ +

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.

+ +

Your root filesystem MUST be the first partition + (partition a) on the disk to be + bootable.

+ +

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.

+ +

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

+

+ +

+

+ +

1.3 Floppy Disk + Image Instructions

+ +

Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.

+ +

For a normal CDROM or network installation, all you + need to copy onto actual floppies from the floppies/ directory are the kern.flp and mfsroot.flp images (for 1.44MB + floppies).

+ +

Getting these images over the network is easy. Simply + fetch the release/floppies/kern.flp and release/floppies/mfsroot.flp files from http://snapshots.jp.FreeBSD.org/ or one of the + many mirrors listed at FTP Sites section of the Handbook, or + on the http://www.freebsdmirrors.org/ Web pages.

+ +

Get two blank, freshly formatted floppies and image + copy kern.flp onto one and mfsroot.flp onto the other. These + images are not DOS files. You cannot simply + copy them to a DOS or UFS floppy as regular files, you + need to ``image'' copy them to the floppy with fdimage.exe under DOS (see the tools directory on your CDROM or FreeBSD + FTP mirror) or the + dd(1) command in + UNIX.

+ +

For example, to create the kernel floppy image from + DOS, you'd do something like this:

+

+    C> fdimage kern.flp a:
+

+ +

Assuming that you'd copied fdimage.exe and kern.flp into a directory somewhere. You + would do the same for mfsroot.flp, of course.

+ +

If you're creating the boot floppy from a UNIX + machine, you may find that:

+

+    # dd if=floppies/kern.flp of=/dev/rfd0
+

+ +

or

+

+    # dd if=floppies/kern.flp of=/dev/floppy
+

+ +

work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).

+ +

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 single (but twice as large) boot.flp image. It contains the + contents of kern.flp and mfsroot.flp on a single floppy. + This file should also be used as the boot file for those + mastering ``El Torito'' bootable CD images. See the + mkisofs(8) command for + more information.

+

+ +

+

+ +

1.4 + Installing FreeBSD from CDROM or the Internet

+ +

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

+

+    >>>boot dka0
+

+ +

Alternatively you can boot the installation from + floppy disk. You should start the installation by + building a set of FreeBSD boot floppies from the files + floppies/kern.flp and floppies/mfsroot.flp using the + instructions found in Section + 1.3. From the SRM console prompt (>>>), just insert the kern.flp floppy and type the following + command to start the installation:

+

+    >>>boot dva0
+

+ +

Insert the mfsroot.flp + floppy when prompted and you will end up at the first + screen of the install program.

+

+ +

+

+ +

1.5 Detail on various + installation types

+ +

Once you've gotten yourself to the initial + installation screen somehow, you should be able to follow + the various menu prompts and go from there. If you've + never used the FreeBSD installation before, you are also + encouraged to read some of the documentation in the + Documentation submenu as well as the general ``Usage'' + instructions on the first menu.

+ +

+

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

+

+ +

If you've never installed FreeBSD before, or even if + you have, the ``Standard'' installation mode is the most + recommended since it makes sure that you'll visit all the + various important checklist items along the way. If + you're much more comfortable with the FreeBSD + installation process and know exactly what you want to do, + use the ``Express'' or ``Custom'' installation options. + If you're upgrading an existing system, use the + ``Upgrade'' option.

+ +

The FreeBSD installer supports the direct use of + floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as + installation media; further tips on installing from each + type of media are listed below.

+ +

Once the install procedure has finished, you will be + able to start FreeBSD/alpha by typing something like this + to the SRM prompt:

+

+    >>>boot dkc0
+

+ +

This instructs the firmware to boot the specified + disk. To find the SRM names of disks in your machine, use + the show device command:

+

+    >>>show device
+    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
+

+ +

This example is from a Digital Personal Workstation + 433au and shows three disks attached to the machine. The + first is a CDROM called dka0 + and the other two are disks and are called dkc0 and dkc100 respectively.

+ +

You can specify which kernel file to load and what + boot options to use with the -file and -flags + options, for example:

+

+    >>> boot -file kernel.old -flags s
+

+ +

To make FreeBSD/alpha boot automatically, use these + commands:

+

+    >>> set boot_osflags a
+    >>> set bootdef_dev dkc0
+    >>> set auto_action BOOT
+

+ +

+

+ +

1.5.1 Installing + from a Network CDROM

+ +

If you simply wish to install from a local CDROM + drive then see Section + 1.4. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:

+ +

+
If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the + vipw(8) + command):
+
```
+    ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the + install, go to the Options menu and set Release + Name to any. You may then + choose a Media type of FTP + and type in ftp://machine after + picking ``URL'' in the ftp sites menu.
+ +
+
+
Warning: This may allow anyone on the + local network (or Internet) to make ``anonymous + FTP'' connections to this machine, which may + not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM + directly to the machine(s) you'll be installing + from, you need to first add an entry to the /etc/exports file (on the + machine with the CDROM drive). The example below + allows the machine ziggy.foo.com to mount the CDROM + directly via NFS during installation:
+
```
+    /cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be + configured as an NFS server, of course, and if + you're not sure how to do that then an NFS + installation is probably not the best choice for + you unless you're willing to read up on + rc.conf(5) and + configure things appropriately. Assuming that this + part goes smoothly, you should be able to enter: + cdrom-host:/cdrom as + the path for an NFS installation when the target + machine is installed, e.g. wiggy:/cdrom.
+

+

+ +

+

+ +

1.5.2 Installing + from Floppies

+ +

If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.

+ +

First, make your boot floppies as described in Section 1.3.

+ +

Second, peruse Section 2 and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.

+ +

Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the bin (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies must be formatted using the + MS-DOS FORMAT command. If + you're using Windows, use the Windows File Manager + format command.

+ +

+

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

+

+ +

If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the + disklabel(8) and + newfs(8) commands to + put a UFS filesystem on a floppy, as the following + sequence of commands illustrates:

+

+    # fdformat -f 1440 fd0.1440
+    # disklabel -w -r fd0.1440 floppy3
+    # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+

+
Important: The bin.inf file also needs to go on + the first floppy of the bin set since it is read by the + installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the distname.inf file must + occupy the first floppy of each distribution set. + This is also covered in README.TXT.
+

+

+ +

Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.

+

+ +

+

+ +

1.5.4 Installing + from QIC/SCSI Tape

+ +

When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use + tar(1) to get them + onto the tape with a command something like this:

+

+    # cd /where/you/have/your/dists
+    # tar cvf /dev/rsa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also + make sure that you leave enough room in some temporary + directory (which you'll be allowed to choose) to + accommodate the full contents of the tape you've + created. Due to the non-random access nature of tapes, + this method of installation requires quite a bit of + temporary storage. You should expect to require as much + temporary storage as you have stuff written on + tape.

+ +

+

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

+

+ +

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

+

+ +

+

+ +

1.5.5 Installing + over a Network using FTP or NFS

+ +

After making the boot floppies as described in the + first section, you can load the rest of the + installation over a network using one of 3 types of + connections: serial port, parallel port, or + Ethernet.

+ +

+

+ +

1.5.5.1 Serial + Port

+ +

SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.

+ +

If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.

+ +

You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.

+

+ +

+

+ +

1.5.5.2 Parallel + Port

+ +

If a hard-wired connection to another FreeBSD or + Linux machine is available, you might also consider + installing over a ``laplink'' style parallel port + cable. The data rate over the parallel port is much + higher than what is typically possible over a serial + line (up to 50k/sec), thus resulting in a quicker + installation. It's not typically necessary to use + ``real'' IP addresses when using a point-to-point + parallel cable in this way and you can generally just + use RFC 1918 style addresses for the ends of the link + (e.g. 10.0.0.1, 10.0.0.2, etc).

+ +

+

+
Important: If you use a Linux machine + rather than a FreeBSD machine as your PLIP peer, + you will also have to specify link0 in the TCP/IP setup screen's + ``extra options for ifconfig'' field in order to + be compatible with Linux's slightly different + PLIP protocol.
+

+

+ +

+

+ +

1.5.5.3 + Ethernet

+ +

FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see HARDWARE.TXT in the Documentation + menu on the boot floppy or the top level directory of + the CDROM). If you are using one of the supported + PCMCIA Ethernet cards, also be sure that it's plugged + in before the laptop is powered + on. FreeBSD does not, unfortunately, currently + support ``hot insertion'' of PCMCIA cards during + installation.

+ +

You will also need to know your IP address on the + network, the netmask value + for your subnet and the name of your machine. Your + system administrator can tell you which values are + appropriate to your particular network setup. If you + will be referring to other hosts by name rather than + IP address, you'll also need a name server and + possibly the address of a gateway (if you're using + PPP, it's your provider's IP address) to use in + talking to it. If you want to install by FTP via an + HTTP proxy (see below), you will also need the + proxy's address.

+ +

If you do not know the answers to these questions + then you should really probably talk to your system + administrator first before trying this type + of installation. Using a randomly chosen IP address + or netmask on a live network is almost guaranteed not + to work, and will probably result in a lecture from + said system administrator.

+ +

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

+

+ +

+

+ +

1.5.5.4 NFS + installation tips

+ +

NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.

+ +

If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.

+ +

If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, + then wiggy will have to allow + the direct mounting of /usr/archive/stuff/FreeBSD, not just + /usr or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled + by the -alldirs option. Other + NFS servers may have different conventions. If you + are getting Permission + Denied messages from the server then it's likely + that you don't have this properly enabled.

+

+ +

+

+ +

1.5.5.5 FTP + Installation tips

+ +

FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.

+ +

If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:

+

+    ftp://216.66.64.162/pub/FreeBSD/releases/alpha/4.2-RELEASE
+

+ +

There are three FTP installation modes you can + use:

+ +

+
FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.
+
+
FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.
+ +
In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:
+
```
+    ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number + of the proxy FTP server.
+

+
+
+

+

+ +

+

+ +

1.5.6 Tips for + Serial Console Users

+ +

If you'd like to install FreeBSD 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:

+ +

+

+
Connect some sort of ANSI (vt100) compatible + terminal or terminal emulation program to the COM1 port of the PC you + are installing FreeBSD onto.
+
+
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.
+
+
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 step 5 as soon + as you hear the beep.
+
+
For a floppy boot, the first beep means to + remove the kern.flp + floppy and insert the mfsroot.flp floppy, after which + you should press Enter and + wait for another beep.
+
+ + +
Hit the space bar, then enter
+
```
+    boot -h
+
```
+ +
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.
+

+

+ +

+

+ +

1.6 Question and + Answer Section for Alpha/AXP Architecture Users

+ +

+

1.6.1. Can I boot from the ARC + or Alpha BIOS Console?
1.6.2. Help! I have no space! + Do I need to delete everything first?
1.6.3. Can I mount my Compaq + Tru64 or VMS extended partitions?
1.6.4. What about support for + Compaq Tru64 (OSF/1) binaries?
1.6.5. What about support for + Linux binaries?
1.6.6. What about support for + NT Alpha binaries?

+ +

+

1.6.1. Can I boot + from the ARC or Alpha BIOS Console?

+

+ +

+

No. FreeBSD, like Compaq Tru64 and VMS, + will only boot from the SRM console.

+

+ +

+

1.6.2. Help! I have + no space! Do I need to delete everything first?

+

+ +

+

Unfortunately, yes.

+

+ +

+

1.6.3. Can I mount + my Compaq Tru64 or VMS extended partitions?

+

+ +

+

No, not at this time.

+

+ +

+

1.6.4. What about + support for Compaq Tru64 (OSF/1) binaries?

+

+ +

+

FreeBSD can run Tru64 applications very + well using the + emulators/osf1_base + port/package.

+

+ +

+

1.6.5. What about + support for Linux binaries?

+

+ +

+

FreeBSD can run AlphaLinux binaries with + the assistance of the + emulators/linux_base + port/package.

+

+ +

+

1.6.6. What about + support for NT Alpha binaries?

+

+ +

+

FreeBSD is not able to run NT + applications natively, although it has the ability + to mount NT partitions.

+

+ +

+

+ +

2 Distribution + Format

+ +

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

+

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

+ +

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 Section 1.3 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 FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.

+ +

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

+ +

+
The *.TXT and *.HTM files contain documentation (for + example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should be read before + starting an installation. The *.TXT files are plain text, while the + *.HTM files are HTML files + that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, + doc, games, info, + manpages, proflibs, and src directories contain the primary + distribution components of FreeBSD itself and are split + into smaller files for easy packing onto floppies + (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their install.sh scripts.
+
+
The floppies/ subdirectory + contains the floppy installation images; further + information on using them can be found in Section 1.3.
+
+
The packages and ports directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:
+
```
+    #/stand/sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual + filenames in packages/ to the + + pkg_add(1) + command.
+ +
The Ports Collection may be installed like any other + distribution and requires about 100MB unpacked. More + information on the ports collection may be obtained + from http://www.FreeBSD.org/ports/ or locally + from /usr/share/doc/handbook + if you've installed the doc + distribution.
+
+
Last of all, the tools + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.
+

+
+
+ +

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

+

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

+ +

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

+

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

+ +

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

+ +

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

+ +

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

+ +

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

+

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

+

+ +

+

+ +

3 Upgrading + FreeBSD

+ +

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

+ +

+

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

+

+ +

+

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

+

+ +

+

+
Warning: Binary upgrades to FreeBSD 5.0-DP2 + from FreeBSD 4-STABLE are not supported at this time. + There are some files present in a FreeBSD 4-STABLE + whose presence can be disruptive, but are not removed + by a binary upgrade. One notable example is that an old + /usr/include/g++ directory + will cause C++ programs to compile incorrectly (or not + at all).
+ +
+ +
These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.
+

+

+ +

+

+ +

3.1 + Introduction

+ +

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

+ +

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

+ +

+

+ +

3.1.1 Upgrade + Overview

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+

+ +

+

+ +

+ +

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

+ +

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

+ +

+

+ +

+

+ +

4 + Troubleshooting

+ +

+

4.1 Repairing an + Existing FreeBSD Installation

+ +

FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + fixit.flp image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.

+ +

To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit'' + 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 /stand and /mnt2/stand directories) for checking, + repairing and examining filesystems and their contents. + Some UNIX administration experience is required to + use the fixit option.

+

+ +

+

+ +

4.2 Common + Installation Problems for Alpha/AXP Architecture + Users

+

FreeBSD/i386 5.0-DP2 + Installation Instructions

+ +

The FreeBSD Project

+ +

+

+ +

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

+ +

+

+ +

1 Installing + FreeBSD

+ +

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

+ +

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

+ +

+

+ +

1.1 Getting + Started

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+

+
Important: While FreeBSD does its best to + safeguard against accidental loss of data, it's still + more than possible to wipe out your entire disk + with this installation if you make a mistake. Please + do not proceed to the final FreeBSD installation menu + unless you've adequately backed up any important data + first.
+

+

+ +

+

+ +

1.2 Hardware + Requirements

+ +

FreeBSD for the IA-32 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 FreeBSD.

+ +

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

+

+ +

+

+ +

1.3 Floppy Disk + Image Instructions

+ +

Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.

+ +

For a normal CDROM or network installation, all you + need to copy onto actual floppies from the floppies/ directory are the kern.flp and mfsroot.flp images (for 1.44MB + floppies).

+ +

Getting these images over the network is easy. Simply + fetch the release/floppies/kern.flp and release/floppies/mfsroot.flp files from http://snapshots.jp.FreeBSD.org/ or one of the + many mirrors listed at FTP Sites section of the Handbook, or + on the http://www.freebsdmirrors.org/ Web pages.

+ +

Get two blank, freshly formatted floppies and image + copy kern.flp onto one and mfsroot.flp onto the other. These + images are not DOS files. You cannot simply + copy them to a DOS or UFS floppy as regular files, you + need to ``image'' copy them to the floppy with fdimage.exe under DOS (see the tools directory on your CDROM or FreeBSD + FTP mirror) or the + dd(1) command in + UNIX.

+ +

For example, to create the kernel floppy image from + DOS, you'd do something like this:

+

+    C> fdimage kern.flp a:
+

+ +

Assuming that you'd copied fdimage.exe and kern.flp into a directory somewhere. You + would do the same for mfsroot.flp, of course.

+ +

If you're creating the boot floppy from a UNIX + machine, you may find that:

+

+    # dd if=floppies/kern.flp of=/dev/rfd0
+

+ +

or

+

+    # dd if=floppies/kern.flp of=/dev/floppy
+

+ +

work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).

+

+ +

+

+ +

1.4 + Installing FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you + have a supported CDROM drive and a FreeBSD installation + CDROM, there are 2 ways of starting the installation from + it:

+ +

+
If your system supports bootable CDROM media + (usually an option which can be selectively enabled + in the controller's setup menu or in the PC BIOS for + some systems) and you have it enabled, FreeBSD + supports the ``El Torito'' bootable CD standard. + Simply put the installation CD in your CDROM drive + and boot the system to begin installation.
+
+
Build a set of FreeBSD boot floppies from the floppies/ directory in every + FreeBSD distribution. Either simply use the makeflp.bat script from DOS or + read Section 1.3 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 + FreeBSD installation.
+

+
+
+ +

If you don't have a CDROM (or your computer does not + support booting from CDROM) and would like to simply + install over the net using PPP, SLIP or a dedicated + connection. You should start the installation by building + a set of FreeBSD boot floppies from the files floppies/kern.flp and floppies/mfsroot.flp using the + instructions found in Section + 1.3. Restart your computer using the kern.flp disk; when prompted, insert the + mfsroot.flp disk. Then, please + go to Section 1.5.5 for additional + tips on installing via FTP or NFS.

+

+ +

+

+ +

1.5 Detail on various + installation types

+ +

Once you've gotten yourself to the initial + installation screen somehow, you should be able to follow + the various menu prompts and go from there. If you've + never used the FreeBSD installation before, you are also + encouraged to read some of the documentation in the + Documentation submenu as well as the general ``Usage'' + instructions on the first menu.

+ +

+

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

+

+ +

If you've never installed FreeBSD before, or even if + you have, the ``Standard'' installation mode is the most + recommended since it makes sure that you'll visit all the + various important checklist items along the way. If + you're much more comfortable with the FreeBSD + installation process and know exactly what you want to do, + use the ``Express'' or ``Custom'' installation options. + If you're upgrading an existing system, use the + ``Upgrade'' option.

+ +

The FreeBSD installer supports the direct use of + floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as + installation media; further tips on installing from each + type of media are listed below.

+ +

+

+ +

1.5.1 Installing + from a Network CDROM

+ +

If you simply wish to install from a local CDROM + drive then see Section + 1.4. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:

+ +

+
If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the + vipw(8) + command):
+
```
+    ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the + install, go to the Options menu and set Release + Name to any. You may then + choose a Media type of FTP + and type in ftp://machine after + picking ``URL'' in the ftp sites menu.
+ +
+
+
Warning: This may allow anyone on the + local network (or Internet) to make ``anonymous + FTP'' connections to this machine, which may + not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM + directly to the machine(s) you'll be installing + from, you need to first add an entry to the /etc/exports file (on the + machine with the CDROM drive). The example below + allows the machine ziggy.foo.com to mount the CDROM + directly via NFS during installation:
+
```
+    /cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be + configured as an NFS server, of course, and if + you're not sure how to do that then an NFS + installation is probably not the best choice for + you unless you're willing to read up on + rc.conf(5) and + configure things appropriately. Assuming that this + part goes smoothly, you should be able to enter: + cdrom-host:/cdrom as + the path for an NFS installation when the target + machine is installed, e.g. wiggy:/cdrom.
+

+

+ +

+

+ +

1.5.2 Installing + from Floppies

+ +

If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.

+ +

First, make your boot floppies as described in Section 1.3.

+ +

Second, peruse Section 2 and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.

+ +

Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the bin (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies must be formatted using the + MS-DOS FORMAT command. If + you're using Windows, use the Windows File Manager + format command.

+ +

+

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

+

+ +

If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the + disklabel(8) and + newfs(8) commands to + put a UFS filesystem on a floppy, as the following + sequence of commands illustrates:

+

+    # fdformat -f 1440 fd0.1440
+    # disklabel -w -r fd0.1440 floppy3
+    # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+

+
Important: The bin.inf file also needs to go on + the first floppy of the bin set since it is read by the + installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the distname.inf file must + occupy the first floppy of each distribution set. + This is also covered in README.TXT.
+

+

+ +

Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.

+

+ +

+

+ +

1.5.3 Installing + from a DOS partition

+ +

To prepare for installation from an MS-DOS partition + you should simply copy the files from the distribution + into a directory called FREEBSD on the Primary DOS partition + (C:). For example, to do a + minimal installation of FreeBSD from DOS using files + copied from the CDROM, you might do something like + this:

+

+    C:\> MD C:\FREEBSD
+    C:\> XCOPY /S E:\BIN C:\FREEBSD\BIN
+

+ +

Assuming that E: was + where your CD was mounted.

+ +

For as many distributions as you wish to install + from DOS (and you have free space for), install each + one in a directory under C:\FREEBSD - the BIN dist is only the minimal + requirement.

+ +

Once you've copied the directories, you can simply + launch the installation from floppies as normal and + select ``DOS'' as your media type when the time + comes.

+

+ +

+

+ +

1.5.4 Installing + from QIC/SCSI Tape

+ +

When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use + tar(1) to get them + onto the tape with a command something like this:

+

+    # cd /where/you/have/your/dists
+    # tar cvf /dev/rsa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also + make sure that you leave enough room in some temporary + directory (which you'll be allowed to choose) to + accommodate the full contents of the tape you've + created. Due to the non-random access nature of tapes, + this method of installation requires quite a bit of + temporary storage. You should expect to require as much + temporary storage as you have stuff written on + tape.

+ +

+

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

+

+ +

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

+

+ +

+

+ +

1.5.5 Installing + over a Network using FTP or NFS

+ +

After making the boot floppies as described in the + first section, you can load the rest of the + installation over a network using one of 3 types of + connections: serial port, parallel port, or + Ethernet.

+ +

+

+ +

1.5.5.1 Serial + Port

+ +

SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.

+ +

If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.

+ +

You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.

+

+ +

+

+ +

1.5.5.2 Parallel + Port

+ +

If a hard-wired connection to another FreeBSD or + Linux machine is available, you might also consider + installing over a ``laplink'' style parallel port + cable. The data rate over the parallel port is much + higher than what is typically possible over a serial + line (up to 50k/sec), thus resulting in a quicker + installation. It's not typically necessary to use + ``real'' IP addresses when using a point-to-point + parallel cable in this way and you can generally just + use RFC 1918 style addresses for the ends of the link + (e.g. 10.0.0.1, 10.0.0.2, etc).

+ +

+

+
Important: If you use a Linux machine + rather than a FreeBSD machine as your PLIP peer, + you will also have to specify link0 in the TCP/IP setup screen's + ``extra options for ifconfig'' field in order to + be compatible with Linux's slightly different + PLIP protocol.
+

+

+ +

+

+ +

1.5.5.3 + Ethernet

+ +

FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see HARDWARE.TXT in the Documentation + menu on the boot floppy or the top level directory of + the CDROM). If you are using one of the supported + PCMCIA Ethernet cards, also be sure that it's plugged + in before the laptop is powered + on. FreeBSD does not, unfortunately, currently + support ``hot insertion'' of PCMCIA cards during + installation.

+ +

You will also need to know your IP address on the + network, the netmask value + for your subnet and the name of your machine. Your + system administrator can tell you which values are + appropriate to your particular network setup. If you + will be referring to other hosts by name rather than + IP address, you'll also need a name server and + possibly the address of a gateway (if you're using + PPP, it's your provider's IP address) to use in + talking to it. If you want to install by FTP via an + HTTP proxy (see below), you will also need the + proxy's address.

+ +

If you do not know the answers to these questions + then you should really probably talk to your system + administrator first before trying this type + of installation. Using a randomly chosen IP address + or netmask on a live network is almost guaranteed not + to work, and will probably result in a lecture from + said system administrator.

+ +

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

+

+ +

+

+ +

1.5.5.4 NFS + installation tips

+ +

NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.

+ +

If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.

+ +

If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, + then wiggy will have to allow + the direct mounting of /usr/archive/stuff/FreeBSD, not just + /usr or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled + by the -alldirs option. Other + NFS servers may have different conventions. If you + are getting Permission + Denied messages from the server then it's likely + that you don't have this properly enabled.

+

+ +

+

+ +

1.5.5.5 FTP + Installation tips

+ +

FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.

+ +

If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:

+

+    ftp://216.66.64.162/pub/FreeBSD/releases/i386/4.2-RELEASE
+

+ +

There are three FTP installation modes you can + use:

+ +

+
FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.
+
+
FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.
+ +
In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:
+
```
+    ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number + of the proxy FTP server.
+

+
+
+

+

+ +

+

+ +

1.5.6 Tips for + Serial Console Users

+ +

If you'd like to install FreeBSD 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:

+ +

+

+
Connect some sort of ANSI (vt100) compatible + terminal or terminal emulation program to the COM1 port of the PC you + are installing FreeBSD onto.
+
+
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.
+
+
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 step 5 as soon + as you hear the beep.
+
+
For a floppy boot, the first beep means to + remove the kern.flp + floppy and insert the mfsroot.flp floppy, after which + you should press Enter and + wait for another beep.
+
+ + +
Hit the space bar, then enter
+
```
+    boot -h
+
```
+ +
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.
+

+

+ +

+

+ +

1.6 Question and + Answer Section for IA-32 Architecture Users

+ +

+

1.6.1. Help! I have no space! + Do I need to delete everything first?
1.6.2. Can I use compressed + DOS filesystems from FreeBSD?
1.6.3. Can I mount my DOS + extended partitions?
1.6.4. Can I run DOS binaries + under FreeBSD?

+ +

+

1.6.1. Help! I have + no space! Do I need to delete everything first?

+

+ +

+

If your machine is already running DOS + and has little or no free space available for + FreeBSD's installation, all is not lost! You may + find the FIPS utility, + provided in the tools/ + subdirectory on the FreeBSD CDROM or on the various + FreeBSD ftp sites, to be quite useful.

+ +

FIPS allows you to + split an existing DOS partition into two pieces, + preserving the original partition and allowing you + to install onto the second free piece. You first + ``defrag'' your DOS partition, using the DOS 6.xx + DEFRAG utility or the Norton Disk Tools, then run + FIPS. It will prompt you for the rest of the + information it needs. Afterwards, you can reboot + and install FreeBSD on the new partition. Also note + that FIPS will create the second partition as a + ``clone'' of the first, so you'll actually see that + you now have two DOS Primary partitions where you + formerly had one. Don't be alarmed! You can simply + delete the extra DOS Primary partition (making sure + it's the right one by examining its size).

+ +

FIPS does NOT + currently work with NTFS style partitions. To split + up such a partition, you will need a commercial + product such as Partition + Magic. 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.

+

+ +

+

1.6.2. Can I use + compressed DOS filesystems from FreeBSD?

+

+ +

+

No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will + only be able to use whatever portion of the + filesystem you leave uncompressed. The rest of the + filesystem will show up as one large file (the + stacked/dblspaced file!). Do not remove that file + as you will probably regret it greatly!

+ +

It is probably better to create another + uncompressed DOS extended partition and use this + for communications between DOS and FreeBSD if such + is your desire.

+

+ +

+

1.6.3. Can I mount + my DOS extended partitions?

+

+ +

+

Yes. DOS extended partitions are mapped + in at the end of the other ``slices'' in FreeBSD, + e.g. your D: drive + might be /dev/da0s5, your + E: drive /dev/da0s6, and so on. This example + assumes, of course, that your extended partition is + on SCSI drive 0. For IDE drives, substitute ad for da appropriately. You otherwise + mount extended partitions exactly like you would + mount any other DOS drive, e.g.:

+

+    # mount -t msdos /dev/da0s5 /dos_d
+

+

+ +

+

1.6.4. Can I run + DOS binaries under FreeBSD?

+

+ +

+

Ongoing work with BSDI's + 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 FreeBSD-emulation + mailing list <freebsd-emulation@FreeBSD.org> + and indicate that you're interested in joining this + ongoing effort!

+ +

The + emulators/pcemu + port/package in the FreeBSD 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.

+

+ +

+

+ +

2 Distribution + Format

+ +

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

+

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

+ +

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 Section 1.3 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 FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.

+ +

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

+ +

+
The *.TXT and *.HTM files contain documentation (for + example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should be read before + starting an installation. The *.TXT files are plain text, while the + *.HTM files are HTML files + that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, + doc, games, info, + manpages, proflibs, and src directories contain the primary + distribution components of FreeBSD itself and are split + into smaller files for easy packing onto floppies + (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their install.sh scripts.
+
+
The floppies/ subdirectory + contains the floppy installation images; further + information on using them can be found in Section 1.3.
+
+
The packages and ports directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:
+
```
+    #/stand/sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual + filenames in packages/ to the + + pkg_add(1) + command.
+ +
The Ports Collection may be installed like any other + distribution and requires about 100MB unpacked. More + information on the ports collection may be obtained + from http://www.FreeBSD.org/ports/ or locally + from /usr/share/doc/handbook + if you've installed the doc + distribution.
+
+
Last of all, the tools + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.
+

+
+
+ +

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

+

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

+ +

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

+

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

+ +

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

+ +

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

+ +

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

+ +

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

+

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

+

+ +

+

+ +

3 Upgrading + FreeBSD

+ +

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

+ +

+

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

+

+ +

+

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

+

+ +

+

+
Warning: Binary upgrades to FreeBSD 5.0-DP2 + from FreeBSD 4-STABLE are not supported at this time. + There are some files present in a FreeBSD 4-STABLE + whose presence can be disruptive, but are not removed + by a binary upgrade. One notable example is that an old + /usr/include/g++ directory + will cause C++ programs to compile incorrectly (or not + at all).
+ +
+ +
These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.
+

+

+ +

+

+ +

3.1 + Introduction

+ +

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

+ +

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

+ +

+

+ +

3.1.1 Upgrade + Overview

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+

+ +

+

+ +

+ +

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

+ +

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

+ +

+

+ +

+

+ +

4 + Troubleshooting

+ +

+

4.1 Repairing an + Existing FreeBSD Installation

+ +

FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + fixit.flp image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.

+ +

To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit'' + 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 /stand and /mnt2/stand directories) for checking, + repairing and examining filesystems and their contents. + Some UNIX administration experience is required to + use the fixit option.

+

+ +

+

+ +

4.2 Common + Installation Problems for IA-32 Architecture + Users

+ +

+

4.2.1. I go to boot from the + hard disk for the first time after installing + FreeBSD, the kernel loads and probes my hardware, but + stops with messages like:
4.2.2. I go to boot from the + hard disk for the first time after installing + FreeBSD, but the Boot Manager prompt just prints F? at the boot menu each time + but the boot won't go any further.
4.2.3. The mcd(4) driver keeps + thinking that it has found a device and this stops my + Intel EtherExpress card from working.
4.2.4. The system finds my + ed(4) network card, but + I keep getting device timeout errors.
4.2.5. I booted the install + floppy on my IBM ThinkPad (tm) laptop, and the + keyboard is all messed up.
4.2.6. My system can not find + my Intel EtherExpress 16 card.
4.2.7. When installing on an + EISA HP Netserver, my on-board AIC-7xxx SCSI + controller isn't detected.
4.2.8. 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.
4.2.9. I have this CMD640 IDE + controller that is said to be broken.
4.2.10. On a Compaq Aero + notebook, I get the message ``No floppy devices + found! Please check ...'' when trying to install from + floppy.
4.2.11. When installing on an + Dell Poweredge XE, Dell proprietary RAID controller + DSA (Dell SCSI Array) isn't recognized.
4.2.12. I have an IBM + EtherJet PCI card, it is detected by the fxp(4) driver + correctly, but the lights on the card don't come on + and it doesn't connect to the network.
4.2.13. When I configure the + network during installation on an IBM Netfinity 3500, + the system freezes.
4.2.14. When I install onto a + drive managed by a Mylex PCI RAID controller, the + system fails to boot (eg. with a read error message).

+ +

+

4.2.1. I go to boot + from the hard disk for the first time after + installing FreeBSD, the kernel loads and probes my + hardware, but stops with messages like:

+

+    changing root device to ad1s1a panic: cannot mount root
+

+ +

What is wrong? What can I do?

+ +

What is this bios_drive:interface(unit,partition)kernel_name + thing that is displayed with the boot help?

+

+ +

+

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 FreeBSD, and working out which numbers + correspond to which is difficult to get right.

+ +

In the case where the boot disk is not the first + disk in the system, FreeBSD can need some help + finding it. There are two common situations here, + and in both of these cases, you need to tell + FreeBSD where the root filesystem is. You do this + by specifying the BIOS disk number, the disk type + and the FreeBSD disk number for that type.

+ +

The first situation is where you have two IDE + disks, each configured as the master on their + respective IDE busses, and wish to boot FreeBSD + from the second disk. The BIOS sees these as disk 0 + and disk 1, while FreeBSD sees them as ad0 and ad2.

+ +

FreeBSD is on BIOS disk 1, of type ad and the FreeBSD disk number is 2, + so you would say:

+

+    1:ad(2,a)kernel
+

+ +

Note that if you have a slave on the primary + bus, the above is not necessary (and is effectively + wrong).

+ +

The second situation involves booting from a + SCSI disk when you have one or more IDE disks in + the system. In this case, the FreeBSD 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 da + and FreeBSD disk number 0, so you would say:

+

+    2:da(0,a)kernel
+

+ +

To tell FreeBSD 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.

+ +

Once you have determined the correct values to + use, you can put the command exactly as you would + have typed it in the /boot.config file using a standard + text editor. Unless instructed otherwise, FreeBSD + will use the contents of this file as the default + response to the boot: + prompt.

+

+ +

+

4.2.2. I go to boot + from the hard disk for the first time after + installing FreeBSD, but the Boot Manager prompt + just prints F? at the boot + menu each time but the boot won't go any + further.

+

+ +

+

The hard disk geometry was set + incorrectly in the Partition editor when you + installed FreeBSD. Go back into the partition + editor and specify the actual geometry of your hard + disk. You must reinstall FreeBSD again from the + beginning with the correct geometry.

+ +

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 FreeBSD after that. The + install program will see the DOS partition and try + to infer the correct geometry from it, which + usually works.

+ +

The following tip is no longer recommended, but + is left here for reference:

+ + +

+
If you are setting up a truly dedicated + FreeBSD 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 FreeBSD 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 FreeBSD on a disk.
+

+

+ +

+

4.2.3. The mcd(4) driver keeps + thinking that it has found a device and this stops + my Intel EtherExpress card from working.

+

+ +

+

Use the UserConfig utility (see HARDWARE.TXT) and disable the + probing of the mcd0 and + mcd1 devices. Generally + speaking, you should only leave the devices that + you will be using enabled in your kernel.

+

+ +

+

4.2.4. The system + finds my ed(4) network card, + but I keep getting device timeout errors.

+

+ +

+

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 ? in the IRQ field + of your kernel config file.

+ +

Either move the jumper on the card to a hard + configuration setting (altering the kernel settings + if necessary), or specify the IRQ as -1 in UserConfig or ? in your kernel config file. This + will tell the kernel to use the soft + configuration.

+ +

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.

+

+ +

+

4.2.5. I booted the + install floppy on my IBM ThinkPad (tm) laptop, and + the keyboard is all messed up.

+

+ +

+

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'.)

+

+ +

+

4.2.6. My system + can not find my Intel EtherExpress 16 card.

+

+ +

+

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 softset.exe program.

+

+ +

+

4.2.7. When + installing on an EISA HP Netserver, my on-board + AIC-7xxx SCSI controller isn't detected.

+

+ +

+

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 -c option into UserConfig, but + don't use the pretty visual + mode but the plain old CLI mode. Type:

+

+    eisa 12
+    quit
+

+ +

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.

+ +

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.

+

+ +

+

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

+

+ +

+

Your machine doesn't like the new i586_copyout and i586_copyin 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 (``expert mode'') version + and type the following at it:

+

+    flags npx0 1
+

+ +

Then proceed normally to boot. This will be + saved into your kernel, so you only need to do it + once.

+

+ +

+

4.2.9. I have this + CMD640 IDE controller that is said to be + broken.

+

+ +

+

FreeBSD does not support this + controller.

+

+ +

+

4.2.10. On a + Compaq Aero notebook, I get the message ``No floppy + devices found! Please check ...'' when trying to + install from floppy.

+

+ +

+

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.

+

+ +

+

4.2.11. When + installing on an Dell Poweredge XE, Dell + proprietary RAID controller DSA (Dell SCSI Array) + isn't recognized.

+

+ +

+

Configure the DSA to use AHA-1540 + emulation using EISA configuration utility. After + that FreeBSD 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.

+

+ +

+

4.2.12. I have an + IBM EtherJet PCI card, it is detected by the fxp(4) driver + correctly, but the lights on the card don't come on + and it doesn't connect to the network.

+

+ +

+

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.

+

+ +

+

4.2.13. When I + configure the network during installation on an IBM + Netfinity 3500, the system freezes.

+

+ +

+

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.

+

+ +

+

4.2.14. When I + install onto a drive managed by a Mylex PCI RAID + controller, the system fails to boot (eg. with a + read error message).

+

+ +

+

There is a bug in the Mylex driver which + results in it ignoring the ``8GB'' geometry mode + setting in the BIOS. Use the 2GB mode instead.

+

FreeBSD/ia64 5.0-DP2 + Installation Instructions

+ +

The FreeBSD Project

+ +

+

+ +

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

+ +

+

+ +

1 Installing + FreeBSD

+ +

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

+ +

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

+ +

+

+ +

1.1 Getting + Started

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+

+
Important: While FreeBSD does its best to + safeguard against accidental loss of data, it's still + more than possible to wipe out your entire disk + with this installation if you make a mistake. Please + do not proceed to the final FreeBSD installation menu + unless you've adequately backed up any important data + first.
+

+

+ +

+

+ +

1.2 Hardware + Requirements

+ +

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

+

+ +

+

+ +

1.3 Floppy Disk + Image Instructions

+

+ +

+

+ +

1.4 + Installing FreeBSD from CDROM or the Internet

+

+ +

+

+ +

1.5 Detail on various + installation types

+ +

Once you've gotten yourself to the initial + installation screen somehow, you should be able to follow + the various menu prompts and go from there. If you've + never used the FreeBSD installation before, you are also + encouraged to read some of the documentation in the + Documentation submenu as well as the general ``Usage'' + instructions on the first menu.

+ +

+

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

+

+ +

If you've never installed FreeBSD before, or even if + you have, the ``Standard'' installation mode is the most + recommended since it makes sure that you'll visit all the + various important checklist items along the way. If + you're much more comfortable with the FreeBSD + installation process and know exactly what you want to do, + use the ``Express'' or ``Custom'' installation options. + If you're upgrading an existing system, use the + ``Upgrade'' option.

+ +

The FreeBSD installer supports the direct use of + floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as + installation media; further tips on installing from each + type of media are listed below.

+ +

+

+ +

1.5.1 Installing + from a Network CDROM

+ +

If you simply wish to install from a local CDROM + drive then see Section + 1.4. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:

+ +

+
If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the + vipw(8) + command):
+
```
+    ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the + install, go to the Options menu and set Release + Name to any. You may then + choose a Media type of FTP + and type in ftp://machine after + picking ``URL'' in the ftp sites menu.
+ +
+
+
Warning: This may allow anyone on the + local network (or Internet) to make ``anonymous + FTP'' connections to this machine, which may + not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM + directly to the machine(s) you'll be installing + from, you need to first add an entry to the /etc/exports file (on the + machine with the CDROM drive). The example below + allows the machine ziggy.foo.com to mount the CDROM + directly via NFS during installation:
+
```
+    /cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be + configured as an NFS server, of course, and if + you're not sure how to do that then an NFS + installation is probably not the best choice for + you unless you're willing to read up on + rc.conf(5) and + configure things appropriately. Assuming that this + part goes smoothly, you should be able to enter: + cdrom-host:/cdrom as + the path for an NFS installation when the target + machine is installed, e.g. wiggy:/cdrom.
+

+

+ +

+

+ +

1.5.2 Installing + from Floppies

+ +

If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.

+ +

First, make your boot floppies as described in Section 1.3.

+ +

Second, peruse Section 2 and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.

+ +

Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the bin (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies must be formatted using the + MS-DOS FORMAT command. If + you're using Windows, use the Windows File Manager + format command.

+ +

+

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

+

+ +

If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the + disklabel(8) and + newfs(8) commands to + put a UFS filesystem on a floppy, as the following + sequence of commands illustrates:

+

+    # fdformat -f 1440 fd0.1440
+    # disklabel -w -r fd0.1440 floppy3
+    # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+

+
Important: The bin.inf file also needs to go on + the first floppy of the bin set since it is read by the + installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the distname.inf file must + occupy the first floppy of each distribution set. + This is also covered in README.TXT.
+

+

+ +

Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.

+

+ +

+

+ +

1.5.4 Installing + from QIC/SCSI Tape

+ +

When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use + tar(1) to get them + onto the tape with a command something like this:

+

+    # cd /where/you/have/your/dists
+    # tar cvf /dev/rsa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also + make sure that you leave enough room in some temporary + directory (which you'll be allowed to choose) to + accommodate the full contents of the tape you've + created. Due to the non-random access nature of tapes, + this method of installation requires quite a bit of + temporary storage. You should expect to require as much + temporary storage as you have stuff written on + tape.

+ +

+

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

+

+ +

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

+

+ +

+

+ +

1.5.5 Installing + over a Network using FTP or NFS

+ +

After making the boot floppies as described in the + first section, you can load the rest of the + installation over a network using one of 3 types of + connections: serial port, parallel port, or + Ethernet.

+ +

+

+ +

1.5.5.1 Serial + Port

+ +

SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.

+ +

If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.

+ +

You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.

+

+ +

+

+ +

1.5.5.2 Parallel + Port

+ +

If a hard-wired connection to another FreeBSD or + Linux machine is available, you might also consider + installing over a ``laplink'' style parallel port + cable. The data rate over the parallel port is much + higher than what is typically possible over a serial + line (up to 50k/sec), thus resulting in a quicker + installation. It's not typically necessary to use + ``real'' IP addresses when using a point-to-point + parallel cable in this way and you can generally just + use RFC 1918 style addresses for the ends of the link + (e.g. 10.0.0.1, 10.0.0.2, etc).

+ +

+

+
Important: If you use a Linux machine + rather than a FreeBSD machine as your PLIP peer, + you will also have to specify link0 in the TCP/IP setup screen's + ``extra options for ifconfig'' field in order to + be compatible with Linux's slightly different + PLIP protocol.
+

+

+ +

+

+ +

1.5.5.3 + Ethernet

+ +

FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see HARDWARE.TXT in the Documentation + menu on the boot floppy or the top level directory of + the CDROM). If you are using one of the supported + PCMCIA Ethernet cards, also be sure that it's plugged + in before the laptop is powered + on. FreeBSD does not, unfortunately, currently + support ``hot insertion'' of PCMCIA cards during + installation.

+ +

You will also need to know your IP address on the + network, the netmask value + for your subnet and the name of your machine. Your + system administrator can tell you which values are + appropriate to your particular network setup. If you + will be referring to other hosts by name rather than + IP address, you'll also need a name server and + possibly the address of a gateway (if you're using + PPP, it's your provider's IP address) to use in + talking to it. If you want to install by FTP via an + HTTP proxy (see below), you will also need the + proxy's address.

+ +

If you do not know the answers to these questions + then you should really probably talk to your system + administrator first before trying this type + of installation. Using a randomly chosen IP address + or netmask on a live network is almost guaranteed not + to work, and will probably result in a lecture from + said system administrator.

+ +

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

+

+ +

+

+ +

1.5.5.4 NFS + installation tips

+ +

NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.

+ +

If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.

+ +

If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, + then wiggy will have to allow + the direct mounting of /usr/archive/stuff/FreeBSD, not just + /usr or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled + by the -alldirs option. Other + NFS servers may have different conventions. If you + are getting Permission + Denied messages from the server then it's likely + that you don't have this properly enabled.

+

+ +

+

+ +

1.5.5.5 FTP + Installation tips

+ +

FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.

+ +

If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:

+

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

+ +

There are three FTP installation modes you can + use:

+ +

+
FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.
+
+
FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.
+ +
In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:
+
```
+    ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number + of the proxy FTP server.
+

+
+
+

+

+ +

+

+ +

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

+

+ +

+

+ +

2 Distribution + Format

+ +

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

+

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

+ +

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 Section 1.3 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 FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.

+ +

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

+ +

+
The *.TXT and *.HTM files contain documentation (for + example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should be read before + starting an installation. The *.TXT files are plain text, while the + *.HTM files are HTML files + that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, + doc, games, info, + manpages, proflibs, and src directories contain the primary + distribution components of FreeBSD itself and are split + into smaller files for easy packing onto floppies + (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their install.sh scripts.
+
+
The floppies/ subdirectory + contains the floppy installation images; further + information on using them can be found in Section 1.3.
+
+
The packages and ports directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:
+
```
+    #/stand/sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual + filenames in packages/ to the + + pkg_add(1) + command.
+ +
The Ports Collection may be installed like any other + distribution and requires about 100MB unpacked. More + information on the ports collection may be obtained + from http://www.FreeBSD.org/ports/ or locally + from /usr/share/doc/handbook + if you've installed the doc + distribution.
+
+
Last of all, the tools + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.
+

+
+
+ +

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

+

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

+ +

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

+

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

+ +

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

+ +

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

+ +

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

+ +

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

+

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

+

+ +

+

+ +

3 Upgrading + FreeBSD

+ +

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

+ +

+

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

+

+ +

+

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

+

+ +

+

+
Warning: Binary upgrades to FreeBSD 5.0-DP2 + from FreeBSD 4-STABLE are not supported at this time. + There are some files present in a FreeBSD 4-STABLE + whose presence can be disruptive, but are not removed + by a binary upgrade. One notable example is that an old + /usr/include/g++ directory + will cause C++ programs to compile incorrectly (or not + at all).
+ +
+ +
These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.
+

+

+ +

+

+ +

3.1 + Introduction

+ +

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

+ +

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

+ +

+

+ +

3.1.1 Upgrade + Overview

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+

+ +

+

+ +

+ +

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

+ +

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

+ +

+

+ +

+

+ +

4 + Troubleshooting

+ +

+

4.1 Repairing an + Existing FreeBSD Installation

+ +

FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + fixit.flp image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.

+ +

To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit'' + 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 /stand and /mnt2/stand directories) for checking, + repairing and examining filesystems and their contents. + Some UNIX administration experience is required to + use the fixit option.

+

+ +

+

+ +

4.2 Common + Installation Problems for IA-64 Architecture + Users

+

FreeBSD/pc98 5.0-DP2 + Installation Instructions

+ +

The FreeBSD Project

+ +

+

+ +

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

+ +

+

+ +

1 Installing + FreeBSD

+ +

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

+ +

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

+ +

+

+ +

1.1 Getting + Started

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+

+
Important: While FreeBSD does its best to + safeguard against accidental loss of data, it's still + more than possible to wipe out your entire disk + with this installation if you make a mistake. Please + do not proceed to the final FreeBSD installation menu + unless you've adequately backed up any important data + first.
+

+

+ +

+

+ +

1.2 Hardware + Requirements

+ +

FreeBSD for the NEC PC-98x1 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 FreeBSD.

+ +

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

+

+ +

+

+ +

1.3 Floppy Disk + Image Instructions

+ +

Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.

+ +

For a normal CDROM or network installation, all you + need to copy onto actual floppies from the floppies/ directory are the kern.flp and mfsroot.flp images (for 1.44MB floppies) + or kern-small.flp and mfsroot-small.flp images (for 1.2MB + floppies).

+ +

Getting these images over the network is easy. Simply + fetch the release/floppies/kern.flp and release/floppies/mfsroot.flp files from http://snapshots.jp.FreeBSD.org/ or one of the + many mirrors listed at FTP Sites section of the Handbook, or + on the http://www.freebsdmirrors.org/ Web pages.

+ +

Get two blank, freshly formatted floppies and image + copy kern.flp onto one and mfsroot.flp onto the other. These + images are not DOS files. You cannot simply + copy them to a DOS or UFS floppy as regular files, you + need to ``image'' copy them to the floppy with rawrite.exe under DOS (see the tools directory on your CDROM or FreeBSD + FTP mirror) or the + dd(1) command in + UNIX.

+ +

For example, to create the kernel floppy image from + DOS, you'd do something like this:

+

+    A> rawrite
+

+ +

Assuming that you'd copied rawrite.exe and kern.flp into a directory somewhere. You + would do the same for mfsroot.flp, of course.

+ +

If you're creating the boot floppy from a UNIX + machine, you may find that:

+

+    # dd if=floppies/kern.flp of=/dev/rfd0.1440
+

+ +

or

+

+    # dd if=floppies/kern-small.flp of=/dev/rfd0.1200
+

+ +

work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).

+

+ +

+

+ +

1.4 + Installing FreeBSD from CDROM or the Internet

+ +

The easiest type of installation is from CDROM. If you + have a supported CDROM drive and a FreeBSD installation + CDROM, there is a next way of starting the installation + from it:

+ +

+
Build a set of FreeBSD boot floppies from the floppies/ directory in every + FreeBSD distribution. Read Section 1.3 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 FreeBSD + installation.
+

+
+
+ +

If you don't have a CDROM and would like to simply + install over the net using PPP, SLIP or a dedicated + connection. You should start the installation by building + a set of FreeBSD boot floppies from the files floppies/kern.flp and floppies/mfsroot.flp using the + instructions found in Section + 1.3. Restart your computer using the kern.flp disk; when prompted, insert the + mfsroot.flp disk. Then, please + go to Section 1.5.5 for additional + tips on installing via FTP or NFS.

+

+ +

+

+ +

1.5 Detail on various + installation types

+ +

Once you've gotten yourself to the initial + installation screen somehow, you should be able to follow + the various menu prompts and go from there. If you've + never used the FreeBSD installation before, you are also + encouraged to read some of the documentation in the + Documentation submenu as well as the general ``Usage'' + instructions on the first menu.

+ +

+

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

+

+ +

If you've never installed FreeBSD before, or even if + you have, the ``Standard'' installation mode is the most + recommended since it makes sure that you'll visit all the + various important checklist items along the way. If + you're much more comfortable with the FreeBSD + installation process and know exactly what you want to do, + use the ``Express'' or ``Custom'' installation options. + If you're upgrading an existing system, use the + ``Upgrade'' option.

+ +

The FreeBSD installer supports the direct use of + floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as + installation media; further tips on installing from each + type of media are listed below.

+ +

+

+ +

1.5.1 Installing + from a Network CDROM

+ +

If you simply wish to install from a local CDROM + drive then see Section + 1.4. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:

+ +

+
If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the + vipw(8) + command):
+
```
+    ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the + install, go to the Options menu and set Release + Name to any. You may then + choose a Media type of FTP + and type in ftp://machine after + picking ``URL'' in the ftp sites menu.
+ +
+
+
Warning: This may allow anyone on the + local network (or Internet) to make ``anonymous + FTP'' connections to this machine, which may + not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM + directly to the machine(s) you'll be installing + from, you need to first add an entry to the /etc/exports file (on the + machine with the CDROM drive). The example below + allows the machine ziggy.foo.com to mount the CDROM + directly via NFS during installation:
+
```
+    /cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be + configured as an NFS server, of course, and if + you're not sure how to do that then an NFS + installation is probably not the best choice for + you unless you're willing to read up on + rc.conf(5) and + configure things appropriately. Assuming that this + part goes smoothly, you should be able to enter: + cdrom-host:/cdrom as + the path for an NFS installation when the target + machine is installed, e.g. wiggy:/cdrom.
+

+

+ +

+

+ +

1.5.2 Installing + from Floppies

+ +

If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.

+ +

First, make your boot floppies as described in Section 1.3.

+ +

Second, peruse Section 2 and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.

+ +

Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the bin (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies must be formatted using the + MS-DOS FORMAT command. If + you're using Windows, use the Windows File Manager + format command.

+ +

+

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

+

+ +

If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the + disklabel(8) and + newfs(8) commands to + put a UFS filesystem on a floppy, as the following + sequence of commands illustrates:

+

+    # fdformat -f 1440 fd0.1440
+    # disklabel -w -r fd0.1440 floppy3
+    # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+

+
Important: The bin.inf file also needs to go on + the first floppy of the bin set since it is read by the + installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the distname.inf file must + occupy the first floppy of each distribution set. + This is also covered in README.TXT.
+

+

+ +

Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.

+

+ +

+

+ +

1.5.3 Installing + from a DOS partition

+ +

To prepare for installation from an MS-DOS partition + you should simply copy the files from the distribution + into a directory called FREEBSD on the Primary DOS partition + (A:). For example, to do a + minimal installation of FreeBSD from DOS using files + copied from the CDROM, you might do something like + this:

+

+    A:\> MD A:\FREEBSD
+    A:\> XCOPY /S E:\BIN A:\FREEBSD\BIN
+

+ +

Assuming that E: was + where your CD was mounted.

+ +

For as many distributions as you wish to install + from DOS (and you have free space for), install each + one in a directory under A:\FREEBSD - the BIN dist is only the minimal + requirement.

+ +

Once you've copied the directories, you can simply + launch the installation from floppies as normal and + select ``DOS'' as your media type when the time + comes.

+

+ +

+

+ +

1.5.4 Installing + from QIC/SCSI Tape

+ +

When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use + tar(1) to get them + onto the tape with a command something like this:

+

+    # cd /where/you/have/your/dists
+    # tar cvf /dev/rsa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also + make sure that you leave enough room in some temporary + directory (which you'll be allowed to choose) to + accommodate the full contents of the tape you've + created. Due to the non-random access nature of tapes, + this method of installation requires quite a bit of + temporary storage. You should expect to require as much + temporary storage as you have stuff written on + tape.

+ +

+

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

+

+ +

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

+

+ +

+

+ +

1.5.5 Installing + over a Network using FTP or NFS

+ +

After making the boot floppies as described in the + first section, you can load the rest of the + installation over a network using one of 3 types of + connections: serial port, parallel port, or + Ethernet.

+ +

+

+ +

1.5.5.1 Serial + Port

+ +

SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.

+ +

If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.

+ +

You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.

+

+ +

+

+ +

1.5.5.2 Parallel + Port

+ +

If a hard-wired connection to another FreeBSD or + Linux machine is available, you might also consider + installing over a ``laplink'' style parallel port + cable. The data rate over the parallel port is much + higher than what is typically possible over a serial + line (up to 50k/sec), thus resulting in a quicker + installation. It's not typically necessary to use + ``real'' IP addresses when using a point-to-point + parallel cable in this way and you can generally just + use RFC 1918 style addresses for the ends of the link + (e.g. 10.0.0.1, 10.0.0.2, etc).

+ +

+

+
Important: If you use a Linux machine + rather than a FreeBSD machine as your PLIP peer, + you will also have to specify link0 in the TCP/IP setup screen's + ``extra options for ifconfig'' field in order to + be compatible with Linux's slightly different + PLIP protocol.
+

+

+ +

+

+ +

1.5.5.3 + Ethernet

+ +

FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see HARDWARE.TXT in the Documentation + menu on the boot floppy or the top level directory of + the CDROM). If you are using one of the supported + PCMCIA Ethernet cards, also be sure that it's plugged + in before the laptop is powered + on. FreeBSD does not, unfortunately, currently + support ``hot insertion'' of PCMCIA cards during + installation.

+ +

You will also need to know your IP address on the + network, the netmask value + for your subnet and the name of your machine. Your + system administrator can tell you which values are + appropriate to your particular network setup. If you + will be referring to other hosts by name rather than + IP address, you'll also need a name server and + possibly the address of a gateway (if you're using + PPP, it's your provider's IP address) to use in + talking to it. If you want to install by FTP via an + HTTP proxy (see below), you will also need the + proxy's address.

+ +

If you do not know the answers to these questions + then you should really probably talk to your system + administrator first before trying this type + of installation. Using a randomly chosen IP address + or netmask on a live network is almost guaranteed not + to work, and will probably result in a lecture from + said system administrator.

+ +

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

+

+ +

+

+ +

1.5.5.4 NFS + installation tips

+ +

NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.

+ +

If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.

+ +

If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, + then wiggy will have to allow + the direct mounting of /usr/archive/stuff/FreeBSD, not just + /usr or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled + by the -alldirs option. Other + NFS servers may have different conventions. If you + are getting Permission + Denied messages from the server then it's likely + that you don't have this properly enabled.

+

+ +

+

+ +

1.5.5.5 FTP + Installation tips

+ +

FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.

+ +

If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:

+

+    ftp://216.66.64.162/pub/FreeBSD/releases/pc98/4.2-RELEASE
+

+ +

There are three FTP installation modes you can + use:

+ +

+
FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.
+
+
FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.
+ +
In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:
+
```
+    ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number + of the proxy FTP server.
+

+
+
+

+

+ +

+

+ +

1.6 Question and + Answer Section for NEC PC-98x1 Architecture + Users

+

+ +

+

+ +

2 Distribution + Format

+ +

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

+

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

+ +

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 Section 1.3 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 FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.

+ +

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

+ +

+
The *.TXT and *.HTM files contain documentation (for + example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should be read before + starting an installation. The *.TXT files are plain text, while the + *.HTM files are HTML files + that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, + doc, games, info, + manpages, proflibs, and src directories contain the primary + distribution components of FreeBSD itself and are split + into smaller files for easy packing onto floppies + (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their install.sh scripts.
+
+
The floppies/ subdirectory + contains the floppy installation images; further + information on using them can be found in Section 1.3.
+
+
The packages and ports directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:
+
```
+    #/stand/sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual + filenames in packages/ to the + + pkg_add(1) + command.
+ +
The Ports Collection may be installed like any other + distribution and requires about 100MB unpacked. More + information on the ports collection may be obtained + from http://www.FreeBSD.org/ports/ or locally + from /usr/share/doc/handbook + if you've installed the doc + distribution.
+
+
Last of all, the tools + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.
+

+
+
+ +

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

+

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

+ +

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

+

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

+ +

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

+ +

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

+ +

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

+ +

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

+

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

+

+ +

+

+ +

3 Upgrading + FreeBSD

+ +

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

+ +

+

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

+

+ +

+

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

+

+ +

+

+
Warning: Binary upgrades to FreeBSD 5.0-DP2 + from FreeBSD 4-STABLE are not supported at this time. + There are some files present in a FreeBSD 4-STABLE + whose presence can be disruptive, but are not removed + by a binary upgrade. One notable example is that an old + /usr/include/g++ directory + will cause C++ programs to compile incorrectly (or not + at all).
+ +
+ +
These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.
+

+

+ +

+

+ +

3.1 + Introduction

+ +

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

+ +

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

+ +

+

+ +

3.1.1 Upgrade + Overview

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+

+ +

+

+ +

+ +

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

+ +

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

+ +

+

+ +

+

+ +

4 + Troubleshooting

+ +

+

4.1 Repairing an + Existing FreeBSD Installation

+ +

FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + fixit.flp image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.

+ +

To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit'' + 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 /stand and /mnt2/stand directories) for checking, + repairing and examining filesystems and their contents. + Some UNIX administration experience is required to + use the fixit option.

+

+ +

+

+ +

4.2 Common + Installation Problems for NEC PC-98x1 Architecture + Users

+

FreeBSD/sparc64 5.0-DP2 + Installation Instructions

+ +

The FreeBSD Project

+ +

+

+ +

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

+ +

+

+ +

1 Installing + FreeBSD

+ +

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

+ +

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

+ +

+

+ +

1.1 Getting + Started

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+

+
Important: While FreeBSD does its best to + safeguard against accidental loss of data, it's still + more than possible to wipe out your entire disk + with this installation if you make a mistake. Please + do not proceed to the final FreeBSD installation menu + unless you've adequately backed up any important data + first.
+

+

+ +

+

+ +

1.2 Hardware + Requirements

+ +

FreeBSD for the UltraSPARC supports the platforms + described in HARDWARE.TXT.

+ +

You will need a dedicated disk for FreeBSD/sparc64. It + is not possible to share a disk with another operating + system at this time.

+ +

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

+

+ +

+

+ +

1.3 Floppy Disk + Image Instructions

+

+ +

+

+ +

1.4 + Installing FreeBSD from CDROM or the Internet

+ +

Most sparc64 systems are set up to boot automatically + from disk. To install FreeBSD, you need to boot over the + network or from a CDROM, which requires you to break into + the PROM (OpenFirmware).

+ +

To do this, reboot the system, and wait until the boot + message appears. It depends on the model, but should look + about like:

+

+    Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
+    Copyright 1998-2001 Sun Microsystems, Inc.  All rights reserved.
+    OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
+    Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.
+

+ +

If your system proceeds to boot from disk at this + point, you need to press L1+A or Stop+A on the keyboard, or send a BREAK over the serial console (using + for example ~# in + tip(1) or + cu(1)) to get to the + PROM prompt. It looks like this:

+

+    ok         (1)
+    ok {0}     (2)
+

+ +

+

(1): This is the prompt used on systems with just one + CPU.
(2): This is the prompt used on SMP systems, the digit + indicates the number of the active CPU.

+

+ +

At this point, place the CDROM into your drive, and + from the PROM prompt, type boot + cdrom.

+

+ +

+

+ +

1.5 Detail on various + installation types

+ +

Once you've gotten yourself to the initial + installation screen somehow, you should be able to follow + the various menu prompts and go from there. If you've + never used the FreeBSD installation before, you are also + encouraged to read some of the documentation in the + Documentation submenu as well as the general ``Usage'' + instructions on the first menu.

+ +

+

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

+

+ +

If you've never installed FreeBSD before, or even if + you have, the ``Standard'' installation mode is the most + recommended since it makes sure that you'll visit all the + various important checklist items along the way. If + you're much more comfortable with the FreeBSD + installation process and know exactly what you want to do, + use the ``Express'' or ``Custom'' installation options. + If you're upgrading an existing system, use the + ``Upgrade'' option.

+ +

The FreeBSD installer supports the direct use of + floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as + installation media; further tips on installing from each + type of media are listed below.

+ +

+

+ +

1.5.1 Installing + from a Network CDROM

+ +

If you simply wish to install from a local CDROM + drive then see Section + 1.4. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:

+ +

+
If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the + vipw(8) + command):
+
```
+    ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
+
```
+ +
On the machine on which you are running the + install, go to the Options menu and set Release + Name to any. You may then + choose a Media type of FTP + and type in ftp://machine after + picking ``URL'' in the ftp sites menu.
+ +
+
+
Warning: This may allow anyone on the + local network (or Internet) to make ``anonymous + FTP'' connections to this machine, which may + not be desirable.
+
+
+
+
If you would rather use NFS to export the CDROM + directly to the machine(s) you'll be installing + from, you need to first add an entry to the /etc/exports file (on the + machine with the CDROM drive). The example below + allows the machine ziggy.foo.com to mount the CDROM + directly via NFS during installation:
+
```
+    /cdrom          -ro             ziggy.foo.com
+
```
+ +
The machine with the CDROM must also be + configured as an NFS server, of course, and if + you're not sure how to do that then an NFS + installation is probably not the best choice for + you unless you're willing to read up on + rc.conf(5) and + configure things appropriately. Assuming that this + part goes smoothly, you should be able to enter: + cdrom-host:/cdrom as + the path for an NFS installation when the target + machine is installed, e.g. wiggy:/cdrom.
+

+

+ +

+

+ +

1.5.2 Installing + from Floppies

+ +

If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.

+ +

First, make your boot floppies as described in Section 1.3.

+ +

Second, peruse Section 2 and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.

+ +

Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the bin (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies must be formatted using the + MS-DOS FORMAT command. If + you're using Windows, use the Windows File Manager + format command.

+ +

+

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

+

+ +

If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the + disklabel(8) and + newfs(8) commands to + put a UFS filesystem on a floppy, as the following + sequence of commands illustrates:

+

+    # fdformat -f 1440 fd0.1440
+    # disklabel -w -r fd0.1440 floppy3
+    # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0
+

+ +

After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, a:\bin\bin.ab, ...

+ +

+

+
Important: The bin.inf file also needs to go on + the first floppy of the bin set since it is read by the + installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the distname.inf file must + occupy the first floppy of each distribution set. + This is also covered in README.TXT.
+

+

+ +

Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.

+

+ +

+

+ +

1.5.4 Installing + from QIC/SCSI Tape

+ +

When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use + tar(1) to get them + onto the tape with a command something like this:

+

+    # cd /where/you/have/your/dists
+    # tar cvf /dev/rsa0 dist1 .. dist2
+

+ +

When you go to do the installation, you should also + make sure that you leave enough room in some temporary + directory (which you'll be allowed to choose) to + accommodate the full contents of the tape you've + created. Due to the non-random access nature of tapes, + this method of installation requires quite a bit of + temporary storage. You should expect to require as much + temporary storage as you have stuff written on + tape.

+ +

+

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

+

+ +

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

+

+ +

+

+ +

1.5.5 Installing + over a Network using FTP or NFS

+ +

After making the boot floppies as described in the + first section, you can load the rest of the + installation over a network using one of 3 types of + connections: serial port, parallel port, or + Ethernet.

+ +

+

+ +

1.5.5.1 Serial + Port

+ +

SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.

+ +

If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.

+ +

You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.

+

+ +

+

+ +

1.5.5.2 Parallel + Port

+ +

If a hard-wired connection to another FreeBSD or + Linux machine is available, you might also consider + installing over a ``laplink'' style parallel port + cable. The data rate over the parallel port is much + higher than what is typically possible over a serial + line (up to 50k/sec), thus resulting in a quicker + installation. It's not typically necessary to use + ``real'' IP addresses when using a point-to-point + parallel cable in this way and you can generally just + use RFC 1918 style addresses for the ends of the link + (e.g. 10.0.0.1, 10.0.0.2, etc).

+ +

+

+
Important: If you use a Linux machine + rather than a FreeBSD machine as your PLIP peer, + you will also have to specify link0 in the TCP/IP setup screen's + ``extra options for ifconfig'' field in order to + be compatible with Linux's slightly different + PLIP protocol.
+

+

+ +

+

+ +

1.5.5.3 + Ethernet

+ +

FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see HARDWARE.TXT in the Documentation + menu on the boot floppy or the top level directory of + the CDROM). If you are using one of the supported + PCMCIA Ethernet cards, also be sure that it's plugged + in before the laptop is powered + on. FreeBSD does not, unfortunately, currently + support ``hot insertion'' of PCMCIA cards during + installation.

+ +

You will also need to know your IP address on the + network, the netmask value + for your subnet and the name of your machine. Your + system administrator can tell you which values are + appropriate to your particular network setup. If you + will be referring to other hosts by name rather than + IP address, you'll also need a name server and + possibly the address of a gateway (if you're using + PPP, it's your provider's IP address) to use in + talking to it. If you want to install by FTP via an + HTTP proxy (see below), you will also need the + proxy's address.

+ +

If you do not know the answers to these questions + then you should really probably talk to your system + administrator first before trying this type + of installation. Using a randomly chosen IP address + or netmask on a live network is almost guaranteed not + to work, and will probably result in a lecture from + said system administrator.

+ +

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

+

+ +

+

+ +

1.5.5.4 NFS + installation tips

+ +

NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.

+ +

If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.

+ +

If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.

+ +

In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on wiggy:/usr/archive/stuff/FreeBSD, + then wiggy will have to allow + the direct mounting of /usr/archive/stuff/FreeBSD, not just + /usr or /usr/archive/stuff.

+ +

In FreeBSD's /etc/exports file this is controlled + by the -alldirs option. Other + NFS servers may have different conventions. If you + are getting Permission + Denied messages from the server then it's likely + that you don't have this properly enabled.

+

+ +

+

+ +

1.5.5.5 FTP + Installation tips

+ +

FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.

+ +

If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:

+

+    ftp://216.66.64.162/pub/FreeBSD/releases/sparc64/4.2-RELEASE
+

+ +

There are three FTP installation modes you can + use:

+ +

+
FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.
+
+
FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.
+
+
FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.
+ +
In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:
+
```
+    ftp://foo.bar.com:port/pub/FreeBSD
+
```
+ +
In the URL above, port is the port number + of the proxy FTP server.
+

+
+
+

+

+ +

+

+ +

1.6 Question and + Answer Section for UltraSPARC Architecture Users

+

+ +

+

+ +

2 Distribution + Format

+ +

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

+

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

+ +

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 Section 1.3 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 FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.

+ +

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

+ +

+
The *.TXT and *.HTM files contain documentation (for + example, this document is contained in both INSTALL.TXT and INSTALL.HTM) and should be read before + starting an installation. The *.TXT files are plain text, while the + *.HTM files are HTML files + that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.
+
+
docbook.css is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.
+
+
The base, catpages, crypto, dict, + doc, games, info, + manpages, proflibs, and src directories contain the primary + distribution components of FreeBSD itself and are split + into smaller files for easy packing onto floppies + (should that be necessary).
+
+
The compat1x, compat20, compat21, compat22, compat3x, and compat4x directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their install.sh scripts.
+
+
The floppies/ subdirectory + contains the floppy installation images; further + information on using them can be found in Section 1.3.
+
+
The packages and ports directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:
+
```
+    #/stand/sysinstall configPackages
+
```
+ +
Packages can also be installed by feeding individual + filenames in packages/ to the + + pkg_add(1) + command.
+ +
The Ports Collection may be installed like any other + distribution and requires about 100MB unpacked. More + information on the ports collection may be obtained + from http://www.FreeBSD.org/ports/ or locally + from /usr/share/doc/handbook + if you've installed the doc + distribution.
+
+
Last of all, the tools + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.
+

+
+
+ +

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

+

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

+ +

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

+

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

+ +

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

+ +

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

+ +

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

+ +

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

+

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

+

+ +

+

+ +

3 Upgrading + FreeBSD

+ +

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

+ +

+

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

+

+ +

+

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

+

+ +

+

+
Warning: Binary upgrades to FreeBSD 5.0-DP2 + from FreeBSD 4-STABLE are not supported at this time. + There are some files present in a FreeBSD 4-STABLE + whose presence can be disruptive, but are not removed + by a binary upgrade. One notable example is that an old + /usr/include/g++ directory + will cause C++ programs to compile incorrectly (or not + at all).
+ +
+ +
These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.
+

+

+ +

+

+ +

3.1 + Introduction

+ +

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

+ +

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

+ +

+

+ +

3.1.1 Upgrade + Overview

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+

+ +

+

+ +

+ +

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

+ +

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

+ +

+

+ +

+

+ +

4 + Troubleshooting

+ +

+

4.1 Repairing an + Existing FreeBSD Installation

+ +

FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + fixit.flp image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.

+ +

To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit'' + 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 /stand and /mnt2/stand directories) for checking, + repairing and examining filesystems and their contents. + Some UNIX administration experience is required to + use the fixit option.

+

+ +

+

+ +

4.2 Common + Installation Problems for UltraSPARC Architecture + Users

+

FreeBSD 5.0-DP2 + README

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.18 + 2002/10/26 17:00:39 bmah Exp $
+

+

+ +

+
+ + +
This document gives a brief introduction to FreeBSD + 5.0-DP2. It includes some information on how to obtain + FreeBSD, a listing of various ways to contact the FreeBSD + Project, and pointers to some other sources of + information.
+
+

FreeBSD may be obtained in a variety of ways. This + section focuses on those ways that are primarily useful for + obtaining a complete FreeBSD distribution, rather than + updating an existing installation.

+ +

+

+ +

2.1 CDROM and + DVD

+ +

FreeBSD -RELEASE distributions may be ordered on CDROM + or DVD from several publishers. This is frequently the + most convenient way to obtain FreeBSD for new + installations, as it provides a convenient way to quickly + reinstall the system if necessary. Some distributions + include some of the optional, precompiled ``packages'' + from the FreeBSD Ports Collection.

+ +

A list of the CDROM and DVD publishers known to the + project are listed in the ``Obtaining FreeBSD'' appendix to the + Handbook.

+

+ +

+

+ +

2.2 FTP

+ +

You can use FTP to retrieve FreeBSD and any or all of + its optional packages from ftp://ftp.FreeBSD.org/, which is the official + FreeBSD release site, or any of its ``mirrors''.

+ +

Lists of locations that mirror FreeBSD can be found in + the FTP Sites section of the Handbook, or + on the http://www.freebsdmirrors.org/ Web pages. + Finding a close (in networking terms) mirror from which + to download the distribution is highly recommended.

+ +

Additional mirror sites are always welcome. Contact + <freebsd-admin@FreeBSD.org> + for more details on becoming an official mirror site. You + can also find useful information for mirror sites at the + Mirroring FreeBSD article.

+ +

Mirrors generally contain the floppy disk images + necessary to begin an installation, as well as the + distribution files needed for the install process itself. + Many mirrors also contain the ISO images necessary to + create a CDROM of a FreeBSD release.

+

+ +

+

+ +

3 Contacting the + FreeBSD Project

+ +

+

3.1 Email and Mailing + Lists

+ +

For any questions or general technical support issues, + please send mail to the FreeBSD general questions mailing + list <freebsd-questions@FreeBSD.org>.

+ +

If you're tracking the 5-CURRENT development efforts, + you must join the FreeBSD-CURRENT + mailing list <freebsd-current@FreeBSD.org>, + in order to keep abreast of recent developments and + changes that may affect the way you use and maintain the + system.

+ +

Being a largely-volunteer effort, the FreeBSD Project + is always happy to have extra hands willing to + help--there are already far more desired enhancements + than there is time to implement them. To contact the + developers on technical matters, or with offers of help, + please send mail to the FreeBSD technical discussions + mailing list <freebsd-hackers@FreeBSD.org>.

+ +

Please note that these mailing lists can experience + significant amounts of traffic. If + you have slow or expensive mail access, or are only + interested in keeping up with major FreeBSD events, you + may find it preferable to subscribe instead to the + FreeBSD announcements mailing list <freebsd-announce@FreeBSD.org>.

+ +

All of the mailing lists can be freely joined by + anyone wishing to do so. Send mail to <majordomo@FreeBSD.org> + and include the keyword help on + a line by itself somewhere in the body of the message. + This will give you more information on joining the + various lists, accessing archives, etc. There are a + number of mailing lists targeted at special interest + groups not mentioned here; more information can be + obtained either through majordomo or the mailing lists section of the FreeBSD + Web site.

+ +

+

+
Important: Do not send email to the + lists asking to be subscribed. Use the <majordomo@FreeBSD.org> + address instead.
+

+

+ +

+

+ +

3.2 Submitting Problem + Reports

+ +

Suggestions, bug reports and contributions of code are + always valued--please do not hesitate to report any + problems you may find. Bug reports with attached fixes + are of course even more welcome.

+ +

The preferred method to submit bug reports from a + machine with Internet mail connectivity is to use the + send-pr(1) command or + use the Web form at http://www.FreeBSD.org/send-pr.html. ``Problem + Reports'' (PRs) submitted in this way will be filed and + their progress tracked; the FreeBSD developers will do + their best to respond to all reported bugs as soon as + possible. A list of all active PRs is available on the + FreeBSD Web site; this list is useful to see what + potential problems other users have encountered.

+ +

Note that + send-pr(1) itself is a + shell script that should be easy to move even onto a + non-FreeBSD system. Using this interface is highly + preferred. If, for some reason, you are unable to use + send-pr(1) to submit a + bug report, you can try to send it to the FreeBSD problem + reports mailing list <freebsd-bugs@FreeBSD.org>.

+ +

For more information, ``Writing FreeBSD Problem Reports'', + available on the FreeBSD Web site, has a number of + helpful hints on writing and submitting effective problem + reports.

+

+ +

+

+ +

4 Further + Reading

+ +

There are many sources of information about FreeBSD; + some are included with this distribution, while others are + available on-line or in print versions.

+ +

+

+ +

4.1 Release + Documentation

+ +

A number of other files provide more specific + information about this snapshot distribution. These files + are provided in various formats. Most distributions will + include both ASCII text (.TXT) + and HTML (.HTM) renditions. + Some distributions may also include other formats such as + PostScript (.PS) or Portable + Document Format (.PDF).

+ +

+
README.TXT: This file, + which gives some general information about FreeBSD as + well as some cursory notes about obtaining a + distribution.
+
+
EARLY.TXT: A guide for + early adopters of FreeBSD 5.0-RELEASE. Highly + recommended reading for users new to FreeBSD + 5-CURRENT and/or the 5.X series of releases.
+
+
RELNOTES.TXT: The + release notes, showing what's new and different in + FreeBSD 5.0-DP2 compared to the previous release + (FreeBSD 4.0-RELEASE).
+
+
HARDWARE.TXT: The + hardware compatibility list, showing devices with + which FreeBSD has been tested and is known to + work.
+
+
INSTALL.TXT: + Installation instructions for installing FreeBSD from + its distribution media.
+
+
ERRATA.TXT: Release + errata. Late-breaking, post-release information can + be found in this file, which is principally + applicable to releases (as opposed to snapshots). It + is important to consult this file before installing a + release of FreeBSD, as it contains the latest + information on problems which have been found and + fixed since the release was created.
+

+ +

+

+
Note: Several of these documents (in + particular, RELNOTES.TXT, + HARDWARE.TXT, and INSTALL.TXT) contain + information that is specific to a particular hardware + architecture. For example, the alpha release notes + contain information not applicable to the i386, and + vice versa. The architecture for which each document + applies will be listed in that document's title.
+

+

+
+
+ +

On platforms that support + sysinstall(8) + (currently the i386 and alpha), these documents are + generally available via the Documentation menu during + installation. Once the system is installed, you can + revisit this menu by re-running the + sysinstall(8) + utility.

+ +

+

+
Note: It is extremely important to read the + errata for any given release before installing it, to + learn about any ``late-breaking news'' or + post-release problems. The errata file accompanying + each release (most likely right next to this file) is + already out of date by definition, but other copies + are kept updated on the Internet and should be + consulted as the ``current errata'' for this release. + These other copies of the errata are located at http://www.FreeBSD.org/releases/ (as well + as any sites which keep up-to-date mirrors of this + location).
+

+

+ +

+

+ +

4.2 Manual + Pages

+ +

As with almost all UNIX-like operating systems, + FreeBSD comes with a set of on-line manual pages, + accessed through the + man(1) command or + through the hypertext manual pages gateway on the + FreeBSD Web site. In general, the manual pages provide + information on the different commands and APIs available + to the FreeBSD user.

+ +

In some cases, manual pages are written to given + information on particular topics. Notable examples of + such manual pages are + tuning(7) (a guide to + performance tuning), + security(7) (an + introduction to FreeBSD security), and + style(9) (a style guide + to kernel coding).

+

+ +

+

+ +

4.3 Books and + Articles

+ +

Two highly-useful collections of FreeBSD-related + information, maintained by the FreeBSD Project, are the + FreeBSD Handbook and FreeBSD FAQ (Frequently Asked + Questions document). On-line versions of the Handbook and FAQ are always available from the FreeBSD Documentation page or its mirrors. If + you install the doc + distribution set, you can use a Web browser to read the + Handbook and FAQ locally.

+ +

A number of on-line books and articles, also + maintained by the FreeBSD Project, cover + more-specialized, FreeBSD-related topics. This material + spans a wide range of topics, from effective use of the + mailing lists, to dual-booting FreeBSD with other + operating systems, to guidelines for new committers. Like + the Handbook and FAQ, these documents are available from + the FreeBSD Documentation Page or in the doc distribution set.

+ +

A listing of other books and documents about FreeBSD + can be found in the bibliography of the FreeBSD Handbook. + Because of FreeBSD's strong UNIX heritage, many other + articles and books written for UNIX systems are + applicable as well, some of which are also listed in the + bibliography.

+

+ +

+

+ +

5 + Acknowledgments

+ +

FreeBSD represents the cumulative work of many hundreds, + if not thousands, of individuals from around the world who + have worked countless hours to bring about this snapshot. + For a complete list of FreeBSD developers and contributors, + please see ``Contributors to FreeBSD'' on the + FreeBSD Web site or any of its mirrors.

+ +

Special thanks also go to the many thousands of FreeBSD + users and testers all over the world, without whom this + snapshot simply would not have been possible.

+

FreeBSD/alpha 5.0-DP2 + Release Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.452 2002/11/14 17:59:11 bmah Exp $
+

+ +

+

+ + +

The release notes for FreeBSD 5.0-DP2 contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. Both + changes for kernel and userland are listed, as well as + applicable security advisories that were issued since + the last release. Some brief remarks on upgrading are + also presented.

+

+ +

+

Table of Contents

+

+

2.1.1 Processor/Motherboard + Support
2.1.2 Bootloader + Changes
2.1.3 Network Interface + Support
2.1.4 Network + Protocols
2.1.5 Disks and + Storage
2.1.6 Filesystems
2.1.7 PCCARD + Support
2.1.8 Multimedia + Support
2.1.9 Contributed + Software

+

+

2.3.1 Contributed + Software
2.3.2 Ports/Packages + Collection Infrastructure

+

3 Upgrading from previous releases + of FreeBSD

+

+

+ +

+

+ +

1 Introduction

+ +

This document contains the release notes for FreeBSD + 5.0-DP2 on the Alpha/AXP hardware platform. It describes + recently added, changed, or deleted features of FreeBSD. It + also provides some notes on upgrading from previous + versions of FreeBSD.

+ +

The snapshot distribution to which these release notes + apply represents a point along the 5-CURRENT development + branch between 4.0-RELEASE and the future 5.0-RELEASE. Some + pre-built, binary snapshot distributions along this branch + can be found at http://snapshots.jp.FreeBSD.org/.

+

+ +

+

+ +

2 What's New

+ +

This section describes many of the user-visible new or + changed features in FreeBSD since 4.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 4.6-RELEASE). The later items are + marked as [MERGED].

+ +

Typical release note items document new drivers or + hardware support, new commands or options, major bugfixes, + or contributed software upgrades. Applicable security + advisories issued after 4.0-RELEASE are also listed.

+ +

Many additional changes were made to FreeBSD 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.

+ +

+

+ +

2.1 Kernel + Changes

+ +

+ acct(2) has been + changed to open the accounting file in append mode, so + that + accton(8) can be used + to enable accounting to an append-only file. [MERGED]

+ +

A new in-kernel cryptographic framework (see + crypto(4) and + crypto(9)) has been + imported from OpenBSD. It provides a consistent interface + to hardware and software implementations of cryptographic + algorithms for use by the kernel and access to + cryptographic hardware for user-mode applications. + Hardware device drivers are provided to support + hifn-based cards ( + hifn(4)) and + Broadcom-based cards ( + ubsec(4)).

+ +

A new + ddb(4) command show pcpu lists some of the per-CPU + data.

+ +

A devctl device has been + added to allow userland programs to learn when devices + come and go in the device tree (different from the XXX). + This facility is primariliy used by the + devd(8) utility.

+ +

+ devfs(5), which allows + entries in the /dev directory + to be built automatically and supports more flexible + attachment of devices, has been largely reworked. + devfs(5) is now enabled + by default and can be disabled by the NODEVFS kernel option.

+ +

The + devfs(5) ``rule'' + subsystem has been introduced. DEVFS rules permit the + administrator to define certain properties of new device + nodes before they become visible to the userland. Both + static (e.g. /dev/speaker) and + dynamic (e.g. /dev/bpf*, some + removable devices) nodes are supported. Each + devfs(5) mount may have + a different ruleset assigned to it, permitting different + policies to be implemented for things like jails. Rules + and rulesets are manipulated with the + devfs(8) utility.

+ +

The dgm driver has been removed in favor of the digi + driver.

+ +

A new digi driver has been added to support PCI + Xr-based and ISA Xem Digiboard cards. A new + digictl(8) program is + (mainly) used to re-initialize cards that have external + port modules attached such as the PC/Xem.

+ +

An + eaccess(2) system call + has been added, similar to + access(2) except that + the former uses effective credentials rather than real + credentials.

+ +

Each + jail(2) environment can + now run under its own securelevel.

+ +

The tunable sysctl variables for + jail(2) have moved from + jail.* to the security.* hierarchy. Other + security-related sysctl variables have moved from kern.security.* to security.*.

+ +

The kernel environment is now dynamic, and can be + changed via the new + kenv(2) system + call.

+ +

The labpc(4) driver has been removed due to + ``bitrot''.

+ +

The loader and kernel linker now look for files named + linker.hints in each directory + with KLDs for a module name and version to KLD filename + mapping. The new + kldxref(8) utility is + used to generate these files.

+ +

+ lomac(4), a + Low-Watermark Mandatory Access Control security facility, + has been added as a kernel module. It provides a drop-in + security mechanism in addition to the traditional + UID-based security facilities, requiring no additional + configuration from the administrator. Work on this + feature was sponsored by DARPA and NAI Labs.

+ +

FreeBSD now supports an extensible Mandatory Access + Control framework, the TrustedBSD MAC Framework. It + permits loadable kernel modules to link to the kernel at + compile-time, boot-time, or run-time, and augment the + system security policy. The framework permits modules to + express interest in a variety of events, and also + provides common security policy services such as label + storage. A variety of sample policy modules are shipped + in this release, including implementations of fixed and + floating label Biba integrity models, Multi-Level + Security (MLS) with compartments, and a number of + augmented UNIX security models including a file system + firewall. This feature will permit easier development and + maintenance of local and vendor security extensions. The + extensibility service is enabled by adding options MAC to the kernel + configuration.

+ +

+

+
Note: The MAC framework is considered an + experimental feature in this release, and is not + enabled by default
+

+

+
+
+ +

+ mutex(9) profiling code + has been added, enabled by the MUTEX_PROFILING kernel configuration + option. It enables the debug.mutex.prof.* hierarchy of sysctl + variables.

+ +

The P1003_1B kernel option is + no longer used and has been removed.

+ +

The + random(4) device has + been rewritten to use the Yarrow 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 + random(4) device is now + periodically saved to files in /var/db/entropy, as well as at shutdown + time. The semantics of /dev/random have changed; it never blocks + waiting for entropy bits but generates a stream of + pseudo-random data and now behaves exactly as /dev/urandom.

+ +

A new kernel option, options + REGRESSION, enables interfaces and functionality + intended for use during correctness and regression + testing.

+ +

RLIMIT_VMEM support has been + added. This feature defines a new resource limit that + covers a process's entire virtual memory space, including + + mmap(2) space. This + limit can be configured in + login.conf(5) via the + new vmemoryuse variable. + [MERGED]

+ +

A bug in the + sendfile(2) system + call, in which headers counted against the size of the + file to be sent, has been fixed. [MERGED]

+ +

The + syscons(4) driver now + supports keyboard-controlled pasting, by default bound to + Shift-Insert.

+ +

The uaudio driver, for USB audio devices, has been + added. [MERGED]

+ +

The + ucom(4) device driver + has been added, to support USB modems, serial devices, + and other programs that need to look like a tty. The + related + uplcom(4) and + uvscom(4) drivers + provide specific support for the Prolific PL-2303 serial + adapter and the SUNTAC Slipper U VS-10U, respectively. + [MERGED]

+ +

To increase security, the UCONSOLE kernel configuration option has + been removed.

+ +

The USER_LDT kernel option is + now activated by default.

+ +

The + uvisor(4) driver for + connecting Handspring Visors via USB has been added. + [MERGED]

+ +

A VESA S3 linear framebuffer driver has been + added.

+ +

The kernel crashdump infrastructure has been revised, + to support new platforms and in general clean up the + logic in the code. One implication of this change is that + the on-disk format for kernel dumps has changed, and is + now byte-order-agnostic.

+ +

Extremely large swap areas (>67 GB) no longer panic + the system.

+ +

Support for threads under Linux emulation has been + added.

+ +

Linker sets are now self-contained; gensetdefs(8) is + unnecessary and has been removed.

+ +

It is now possible to hardwire kernel environment + variables (such as tuneables) at compile-time using + config(8)'s ENV directive.

+ +

Idle zeroing of pages can be enabled with the vm.idlezero_enable sysctl + variable.

+ +

The FreeBSD kernel scheduler now supports + Kernel-Scheduled Entities (KSEs), which provides support + for multiple threads of execution per process similar to + Scheduler Activations. At this point, the kernel has most + of the changes needed to support threading. The kernel + scheduler can schedule multiple threads per process, but + only on a single CPU at a time. More information can be + found in + kse(2).

+ +

+

+
Note: KSE is a work in progress.
+

+

+
+
+ +

The kernel now has support for multiple low-level + console devices. The new + conscontrol(8) utility + helps to manage the different consoles.

+ +

The console driver has gained support for TGA-based + display adapters.

+ +

The kernel memory allocator is now a slab memory + allocator, similar to that used in Solaris. This is a + SMP-safe memory allocator that has near-linear + performance as the number of CPUs increases. It also + allows for reduced memory fragmentation.

+ +

+

+ +

2.1.1 + Processor/Motherboard Support

+ +

SMP support has been largely reworked, incorporating + code from BSD/OS 5.0. One of the main features of SMPng + (``SMP Next Generation'') 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.

+ +

The API UP1100 mainboard has been verified to + work.

+ +

The API CS20 1U high server has been verified to + work.

+ +

Support for AlphaServer 2100A (``Lynx'') has been + added.

+ +

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.

+ +

SMP support for the Alpha is now operational.

+ +

Support for the following hardware has been removed + from the installation kernel to make it fit on a 1.44MB + floppy again: Multia, NoName, PC64, EB64, Aspen Alpine, + sa (SCSI tape), amr, parallel port support, vx (3c590, + 3c595), pcn (AMD Am79C97x PCI 10/100), sf (Adaptec + AIC-6915), sis (SiS 900/SiS 7016), ste (Sundance ST201 + (D-Link DFE-550TX)), wb (Winbond W89C840F).

+ +

Support for TurboChannel Alphas has been + removed.

+

+ +

+

+ +

2.1.2 Bootloader + Changes

+ +

The kernel and modules have been moved to the + directory /boot/kernel, so + they can be easily manipulated together. The boot + loader has been updated to make this change as seamless + as possible.

+

+ +

+

+ +

2.1.3 Network + Interface Support

+ +

The + dc(4) driver now + supports NICs based on the Xircom 3201 and Conexant + LANfinity RS7112 chips.

+ +

The + ed(4) driver is now + supported.

+ +

The + stf(4) device is now + clonable.

+ +

The + tx(4) driver now + supports true multicast filtering.

+ +

Network devices now automatically appear as special + files in /dev/net. Interface + hardware ioctls (not protocol or routing) can be + performed on these devices. The SIOCGIFCONF ioctl may be performed on + the special /dev/network + node.

+ +

``Zero copy'' support has been added to the + networking stack. This feature can eliminate a copy of + network data between the kernel and userland, which is + one of the more significant bottlenecks in network + throughput. The send-side code should work with almost + any network adapter, while the receive-side code + requires a network adapter with an MTU of at least one + memory page size (for example, jumbo frames on Gigabit + Ethernet). For more information, see + zero_copy(9).

+

+ +

+

+ +

2.1.4 Network + Protocols

+ +

A FAST_IPSEC kernel option + now allows the IPsec implementation to use the kernel + crypo framework, along with its support for hardware + cryptographic acceleration.

+ +

+

+
Note: The FAST_IPSEC and IPSEC options are mutually + exclusive.
+

+

+ +

+

+
Note: The FAST_IPSEC option is, at the moment, + not compatible with IPv6 or the INET6 option.
+

+

+
+
+ +

A + gre(4) driver, which + can encapsulate IP packets using GRE (RFC 1701) or + minimal IP encapsulation for Mobile IP (RFC 2004), has + been added.

+ +

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.

+ +

IP multicast now works on VLAN devices. Several + other bugs in the VLAN code have also been fixed.

+ +

+ ipfw(4) has been + re-implemented (the new version is commonly referred to + as ``IPFW2''). It now uses variable-sized + representation of rules in the kernel, similar to + bpf(4) instructions. + Most of the externally-visible behavior (i.e. through + + ipfw(8)) should be + unchanged., although + ipfw(8) now supports + or connectives between match + fields. [MERGED]

+ +

A new + ng_device(4) netgraph + node type has been added, which creates a device entry + in /dev, to be used as the + entry point to a networking graph.

+ +

The + ng_gif(4) and + ng_gif_demux(4) + netgraph nodes, for operating on + gif(4) devices, have + been added.

+ +

The + ng_ip_input(4) + netgraph node, for queueing IP packets into the main IP + input processing code, has been added.

+ +

A new + ng_l2tp(4) netgraph + node type, which implements the encapsulation layer of + the L2TP protocol as described in RFC 2661, has been + added. [MERGED]

+ +

A new ng_split node type has been added for + splitting a bidirectional packet flow into two + unidirectional flows.

+ +

SLIP has been removed from the mfsroot floppy image.

+ +

The ephemeral port range used for TCP and UDP has + been changed to 49152-65535 (the old default was + 1024-5000). This increases the number of concurrent + outgoing connections/streams.

+ +

The + tcp(4) protocol's + retransmission timer can now be manipulated with two + sysctl variables, net.inet.tcp.rexmit_min and net.inet.tcp.rexmit_slop. The default + has been reduced from one second to 200ms (similar to + the Linux default) in order to better handle hicups + over interactive connections and improve recovery over + lossy fast connections such as wireless links.

+ +

The + tcp(4) protocol now + has the ability to dynamically limit the send-side + window to maximize bandwidth and minimize round trip + times. The feature can be enabled via the net.inet.tcp.inflight_enable sysctl. + [MERGED]

+

+ +

+

+ +

2.1.5 Disks and + Storage

+ +

The + ata(4) driver (along + with + burncd(8)) now + supports writing to media in DVD+RW drives.

+ +

The + ata(4) driver now + supports accessing ATA devices as SCSI devices via the + CAM layer and drivers ( + cd(4), + da(4), + st(4), and + pass(4)). This + feature requires device + atapicam in the kernel configuration. More + information can be found in + atapicam(4). + [MERGED]

+ +

The + ata(4) driver now has + support for the Sil 0680 and VIA 8233/8235 controllers. + [MERGED]

+ +

The + cd(4) driver now + supports the same CDRIOCREADSPEED and CDRIOCWRITESPEED ioctls that the + acd(4) driver uses + for setting the speed of CDROM access.

+ +

The + fdc(4) floppy disk + has undergone a number of enhancements. Density + selection for common settings is now automatic; the + driver is also much more flexible in setting the + densities of various subdevices.

+ +

The + geom(4) disk I/O + request transformation framework has been added; this + extensible framework is designed to support a wide + variety of operations on I/O requests on their way from + the upper kernel to the device drivers.

+ +

+

+
Note: GEOM-enabled kernels no longer + support ``compatability slices''. This feature + (supported on the i386 and pc98 only) allowed a + user to refer to a disk partition without + specifying an MBR slice (e.g. /dev/ad0a); the kernel would + automatically find the first applicable FreeBSD + slice and use it. On GEOM kernels, only the full + partition names (e.g. /dev/ad0s1a) are allowed when + referring to partitions within MBR slices. This + change should affect very few users.
+

+

+
+
+ +

A GEOM Based Disk Encryption module has been added. + It provides denial of access to ``cold disks'', with + four different cryptographic barriers and up to four + changeable pass-phrases. Much more information can be + found in the + gbde(4) manual page. + The + gbde(8) userland + utility provides an operation and management interface + to this module. This feature is not enabled by default; + it requires options GEOM_BDE + to be added to a kernel configuration file.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

The + isp(4) driver is now + proactive about discovering Fibre Channel topology + changes.

+ +

The + isp(4) driver now + supports target mode for Qlogic SCSI cards, including + Ultra2 and Ultra3 and dual bus cards.

+ +

+ md(4), the memory + disk device, has had the functionality of + vn(4) incorporated + into it. + md(4) devices can now + be configured by + mdconfig(8). + vn(4) has been + removed. The Memory Filesystem (MFS) has also been + removed.

+ +

The mpt driver, for supporting the LSI Logic + Fusion/MP architecture Fiber Channel controllers, has + been added. [MERGED]

+ +

The RAIDframe disk driver has been imported from + NetBSD. This driver provides software-based RAID 0, 1, + 4, and 5 capabilities, as well as other functionality. + More information can be found in the + raid(4) driver manual + page. The + raidctl(8) utility is + used to configure and unconfigure disk arrays. This + feature is not enabled by default, and requires device raidframe to be configured + into a kernel.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

Some problems in + sa(4) error handling + have been fixed, including the ``tape drive spinning + indefinitely upon + mt(1) stat'' problem.

+ +

The SCSI_DELAY + configuration parameter can now be set at boot time and + runtime via the kern.cam.scsi_delay tunable/sysctl.

+ +

The trm driver has been added to support SCSI + adapters using the Tekram TRM-S1040 SCSI chipset.

+

+ +

+

+ +

2.1.6 + Filesystems

+ +

Support for named extended attributes was added to + the FreeBSD 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 /usr/src/sys/ufs/ufs/README.extattr for + details).

+ +

A filesystem snapshot capability has been added to + FFS. Details can be found in /usr/src/sys/ufs/ffs/README.snapshot.

+ +

Softupdates for FFS have received some bug fixes and + enhancements.

+ +

When running with softupdates, + statfs(2) and + df(1) will track the + number of blocks and files that are committed to being + freed.

+ +

+ kernfs(5) is obsolete + and has been retired.

+ +

Client-side NFS locks have been implemented.

+ +

The client-side and server-side of the NFS code in + the kernel used to be intertwined in various complex + ways. They have been split apart for ease of + maintenance and further development.

+ +

Support for filesystem 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 /usr/src/sys/ufs/ufs/README.acls.

+ +

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. Compatibility ``glue'' has + been added to + mount(8) so that msdos filesystem entries in + fstab(5) will work + without changes.

+ +

pseudofs, a pseudo-filesystem framework, has been + added. + linprocfs(5) and + procfs(5) have been + modified to use pseudofs.

+ +

Network filesystems (such as NFS and smbfs + filesystems) listed in /etc/fstab can now be properly mounted + during startup initialization; their mounts are + deferred until after the network is initialized.

+ +

Read-only support for the Universal Disk Format + (UDF) has been added. This format is used on + packet-written CD-RWs and most commercial DVD-Video + disks. The + mount_udf(8) command + can be used to mount these disks.

+ +

Basic support has been added for the UFS2 + filesystem. Among its features:

+ +

+
The inode has been expanded to 256 bytes to make + space for 64-bit block pointers.
+
+
A file-creation time field has been added.
+
+
A native extended attributes implementation has + been added, permitting total attribute size stored + on an inode to be up to twice the filesystem block + size. This storage is used for Access Control Lists + and MAC labels, but may also be used by other + system extensions and user applications.
+

+
+
+

+ +

+

+ +

2.1.7 PCCARD + Support

+ +

+

+ +

+

+ +

2.1.8 Multimedia + Support

+ +

A new API has been added for sound cards with + hardware volume control.

+

+ +

+

+ +

2.1.9 Contributed + Software

+ +

The Forth Inspired Command Language (FICL) used in the boot loader has + been updated to 3.02.

+ +

Support for Advanced Configuration and Power + Interface (ACPI), a multi-vendor standard for + configuration and power management, has been added. + This functionality has been provided by the Intel ACPI Component Architecture + project, as of the ACPI CA 20020815 snapshot. Some + backward compatability for applications using the older + APM standard has been provided.

+ +

+

+ +

2.1.9.1 + IPFilter

+ +

IPFilter has been + updated to 3.4.29. [MERGED]

+

+ +

+

+ +

2.1.9.3 + KAME

+

+ +

+

+ +

2.2 Security-Related + Changes

+ +

A bug in which malformed ELF executable images can + hang the system has been fixed (see security advisory + FreeBSD-SA-00:41). [MERGED]

+ +

A security hole in Linux emulation was fixed (see + security advisory FreeBSD-SA-00:42). [MERGED]

+ +

TCP now uses stronger randomness in choosing its + initial sequence numbers (see security advisory + FreeBSD-SA-00:52). [MERGED]

+ +

Several buffer overflows in + tcpdump(1) were + corrected (see security advisory FreeBSD-SA-00:61). + [MERGED]

+ +

A security hole in + top(1) was corrected + (see security advisory FreeBSD-SA-00:62). [MERGED]

+ +

A potential security hole caused by an + off-by-one-error in + gethostbyname(3) has + been fixed (see security advisory FreeBSD-SA-00:63). + [MERGED]

+ +

A potential buffer overflow in the + ncurses(3) library, + which could cause arbitrary code to be run from within + systat(1), has been + corrected (see security advisory FreeBSD-SA-00:68). + [MERGED]

+ +

A vulnerability in + telnetd(8) that could + cause it to consume large amounts of server resources has + been fixed (see security advisory FreeBSD-SA-00:69). + [MERGED]

+ +

The nat deny_incoming command + in + ppp(8) now works + correctly (see security advisory FreeBSD-SA-00:70). + [MERGED]

+ +

A vulnerability in + csh(1)/ + tcsh(1) temporary files + that could allow overwriting of arbitrary user-writable + files has been closed (see security advisory + FreeBSD-SA-00:76). [MERGED]

+ +

Several vulnerabilities in + procfs(5) were fixed + (see security advisory FreeBSD-SA-00:77). [MERGED]

+ +

A bug in OpenSSH in which a + server was unable to disable + ssh-agent(1) or X11Forwarding was fixed (see + security advisory FreeBSD-SA-01:01). [MERGED]

+ +

A bug in + ipfw(8) and + ip6fw(8) in which + inbound TCP segments could incorrectly be treated as + being part of an established + connection has been fixed (see security advisory + FreeBSD-SA-01:08). [MERGED]

+ +

A bug in + crontab(1) that could + allow users to read any file on the system in valid + crontab(5) syntax has + been fixed (see security advisory FreeBSD-SA-01:09). + [MERGED]

+ +

A vulnerability in + inetd(8) that could + allow read-access to the initial 16 bytes of wheel-accessible files has been fixed + (see security advisory FreeBSD-SA-01:11). [MERGED]

+ +

A bug in + periodic(8) that used + insecure temporary files has been corrected (see security + advisory FreeBSD-SA-01:12). [MERGED]

+ +

OpenSSH 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]

+ +

A bug in + timed(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:28). + [MERGED]

+ +

A bug in + rwhod(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:29). + [MERGED]

+ +

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]

+ +

A remotely-exploitable vulnerability in + ntpd(8) has been closed + (see security advisory FreeBSD-SA-01:31). [MERGED]

+ +

A security hole in IPFilter's fragment cache has been + closed (see security advisory FreeBSD-SA-01:32). + [MERGED]

+ +

Buffer overflows in + 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, + glob(3) allows + specification of a limit on the number of pathname + matches it will return. + ftpd(8) now uses this + feature (see security advisory FreeBSD-SA-01:33). + [MERGED]

+ +

Initial sequence numbers in TCP are more thoroughly + randomized (see security advisory FreeBSD-SA-01:39). Due + to some possible compatibility issues, the behavior of + this security fix can be enabled or disabled via the net.inet.tcp.tcp_seq_genscheme + sysctl variable.[MERGED]

+ +

A vulnerability in the + 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]

+ +

A flaw allowed some signal handlers to remain in + effect in a child process after being exec-ed from its + parent. This allowed an attacker to execute arbitrary + code in the context of a setuid binary. This flaw has + been corrected (see security advisory FreeBSD-SA-01:42). + [MERGED]

+ +

A remote buffer overflow in + tcpdump(1) has been + fixed (see security advisory FreeBSD-SA-01:48). + [MERGED]

+ +

A remote buffer overflow in + telnetd(8) has been + fixed (see security advisory FreeBSD-SA-01:49). + [MERGED]

+ +

The new net.inet.ip.maxfragpackets and net.inet.ip6.maxfragpackets sysctl + variables limit the amount of memory that can be consumed + by IPv4 and IPv6 packet fragments, which defends against + some denial of service attacks (see security advisory + FreeBSD-SA-01:52). [MERGED]

+ +

A flaw in the implementation of the + ipfw(8) me rules on point-to-point links has been + corrected. Formerly, me filter + rules would match the remote IP address of a + point-to-point interface in addition to the intended + local IP address (see security advisory + FreeBSD-SA-01:53). [MERGED]

+ +

A vulnerability in + procfs(5), which could + allow a process to read sensitive information from + another process's memory space, has been closed (see + security advisory FreeBSD-SA-01:55). [MERGED]

+ +

The PARANOID hostname + checking in tcp_wrappers now + works as advertised (see security advisory + FreeBSD-SA-01:56). [MERGED]

+ +

A local root exploit in + sendmail(8) has been + closed (see security advisory FreeBSD-SA-01:57). + [MERGED]

+ +

A remote root vulnerability in + lpd(8) has been closed + (see security advisory FreeBSD-SA-01:58). [MERGED]

+ +

A race condition in + rmuser(8) that briefly + exposed a world-readable /etc/master.passwd has been fixed (see + security advisory FreeBSD-SA-01:59). [MERGED]

+ +

A vulnerability in UUCP has + been closed (see security advisory FreeBSD-SA-01:62). All + non-root-owned binaries in + standard system paths now have the schg flag set to prevent exploit vectors + when run by + cron(8), by root, or by a user other then the one + owning the binary. In addition, + uustat(1) is now run + via /etc/periodic/daily/410.status-uucp as + uucp, not root. In FreeBSD -CURRENT, UUCP has since been moved to the Ports + Collection and no longer a part of the base system. + [MERGED]

+ +

A security hole in OpenSSH, + which could allow users to execute code with arbitrary + privileges if UseLogin yes was + set, has been closed. Note that the default value of this + setting is UseLogin no. (See + security advisory FreeBSD-SA-01:63.) [MERGED]

+ +

The use of an insecure temporary directory by + pkg_add(1) could permit + a local attacker to modify the contents of binary + packages while they were being installed. This hole has + been closed. (See security advisory FreeBSD-SA-02:01.) + [MERGED]

+ +

A race condition in + pw(8), which could + expose the contents of /etc/master.passwd, has been eliminated. + (See security advisory FreeBSD-SA-02:02.) [MERGED]

+ +

A bug in + k5su(8) could have + allowed a process that had given up superuser privileges + to regain them. This bug has been fixed. (See security + advisory FreeBSD-SA-02:07.) [MERGED]

+ +

An ``off-by-one'' bug has been fixed in OpenSSH's multiplexing code. This bug + could have allowed an authenticated remote user to cause + + sshd(8) to execute + arbitrary code with superuser privileges, or allowed a + malicious SSH server to execute arbitrary code on the + client system with the privileges of the client user. + (See security advisory FreeBSD-SA-02:13.) [MERGED]

+ +

A programming error in zlib + could result in attempts to free memory multiple times. + The + malloc(3)/ + free(3) routines used + in FreeBSD are not vulnerable to this error, but + applications receiving specially-crafted blocks of + invalid compressed data could be made to function + incorrectly or abort. This zlib bug has been fixed. For a + workaround and solutions, see security advisory FreeBSD-SA-02:18. [MERGED]

+ +

Bugs in the TCP SYN cache (``syncache'') and SYN + cookie (``syncookie'') implementations, which could cause + legitimate TCP/IP traffic to crash a machine, have been + fixed. For a workaround and patches, see security + advisory FreeBSD-SA-02:20. [MERGED]

+ +

A routing table memory leak, which could allow a + remote attacker to exhaust the memory of a target + machine, has been fixed. A workaround and patches can be + found in security advisory FreeBSD-SA-02:21. [MERGED]

+ +

A bug with memory-mapped I/O, which could cause a + system crash, has been fixed. For more information about + a solution, see security advisory FreeBSD-SA-02:22. [MERGED]

+ +

A security hole, in which SUID programs could be made + to read from or write to inappropriate files through + manipulation of their standard I/O file descriptors, has + been fixed. Information regarding a solution can be found + in security advisory FreeBSD-SA-02:23. [MERGED]

+ +

Some unexpected behavior could be allowed with + k5su(8) because it does + not require that an invoking user be a member of the wheel group when attempting to + become the superuser (this is the case with + su(1)). To avoid this + situation, + k5su(8) is now + installed non-SUID by default (effectively disabling it). + More information can be found in security advisory FreeBSD-SA-02:24. [MERGED]

+ +

Multiple vulnerabilities were found in the + bzip2(1) utility, which + could allow files to be overwritten without warning or + allow local users unintended access to files. These + problems have been corrected with a new import of bzip2. For more information, see + security advisory FreeBSD-SA-02:25. [MERGED]

+ +

A bug has been fixed in the implementation of the TCP + SYN cache (``syncache''), which could allow a remote + attacker to deny access to a service when accept filters + (see + accept_filter(9)) were + in use. This bug has been fixed; for more information, + see security advisory FreeBSD-SA-02:26. [MERGED]

+ +

Due to a bug in + rc(8)'s use of shell + globbing, users may be able to remove the contents of + arbitrary files if /tmp/.X11-unix does not exist and the + system can be made to reboot. This bug has been corrected + (see security advisory FreeBSD-SA-02:27). [MERGED]

+ +

A buffer overflow in the resolver, which could be + exploited by a malicious domain name server or an + attacker forging DNS messages, has been fixed. See + security advisory FreeBSD-SA-02:28 for more details. + [MERGED]

+ +

A buffer overflow in + tcpdump(1), which could + be triggered by badly-formed NFS packets, has been fixed. + See security advisory FreeBSD-SA-02:29 for more details. + [MERGED]

+ +

+ ktrace(1) can no longer + trace the operation of formerly privileged processes; + this prevents the leakage of sensitive information that + the process could have obtained before abandoning its + privileges. For a discussion of this issue, see security + advisory FreeBSD-SA-02:30 for more details. + [MERGED]

+ +

A race condition in + pppd(8), which could be + used to change the permissions of an arbitrary file, has + been corrected. For more information, see security + advisory FreeBSD-SA-02:32. [MERGED]

+ +

Multiple buffer overflows in OpenSSL have been corrected, by way of + an upgrade to the base system version of OpenSSL. More details can be found in + security advisory FreeBSD-SA-02:33. [MERGED]

+ +

A heap buffer overflow in the XDR decoder has been + fixed. For more details, see security advisory FreeBSD-SA-02:34. [MERGED]

+ +

A bug that could allow local users to read and write + arbitrary blocks on an FFS filesystem has been corrected. + More details can be found in security advisory FreeBSD-SA-02:35. [MERGED]

+ +

A bug in the NFS server code, which could allow a + remote denial of service attack, has been fixed. Security + advisory FreeBSD-SA-02:36 has more details. + [MERGED]

+ +

A bug that could allow local users to panic a system + using the + kqueue(2) mechanism has + been fixed. More information is contained in security + advisory FreeBSD-SA-02:37. [MERGED]

+ +

Several bounds-checking bugs in system calls, which + could result in some system calls returning a large + portion of kernel memory, have been fixed. More + information can be found in security advisory FreeBSD-SA-02:38. [MERGED]

+ +

A bug that could allow applications using libkvm to leak sensitive file descriptors + has been corrected. (See security advisory FreeBSD-SA-02:39 for more details.) + [MERGED]

+ +

Buffer overflows in kadmind(8) and k5admin have been + corrected. More details can be found in security advisory + FreeBSD-SA-02:40. [MERGED]

+ +

Errors in + smrsh(8), which could + allow users to circumvent restrictions on what programs + can be executed, have been fixed. See FreeBSD-SA-02:41 for details. + [MERGED]

+ +

Buffer overflows in the DNS + resolver(3), which + could cause some applications to fail, have been + corrected. More details are in FreeBSD-SA-02:42. [MERGED]

+ +

Multiple vulnerabilities in BIND have been fixed, as described in + FreeBSD-SA-02:43. [MERGED]

+

+ +

+

+ +

2.3 Userland + Changes

+ +

Support for + a.out(5) format + executables in the compiler toolchain has been largely + removed.

+ +

+

+
Note: This is a work in progress. + Eventually, + a.out(5) support + will resurface in a series of ports/packages.
+

+

+
+
+ +

+ arp(8) now prints [fddi] or [atm] tags for addresses on interfaces of + those types.

+ +

The + asa(1) utility, to + interpret FORTRAN carriage-control characters, has been + added.

+ +

+ at(1) now supports the + -r command-line option to remove + jobs and the -t option to specify + times in POSIX time format.

+ +

The system + awk(1) now refers to BWK awk.

+ +

+ basename(1) now accept + -a and -s + flags, which allow it to perform the + basename(3) function on + multiple files.

+ +

+ biff(1) now accepts a + b argument to enable ``bell + notification'' of new mail (which does not disturb the + terminal contents as biff y + would). [MERGED]

+ +

+ biff(1) now uses the + first terminal associated with the standard input, + standard output or standard error file descriptor, in + that order. Thus, it is possible to use the redirection + facilities of a shell (biff n < + /dev/ttyp1) to toggle the notification for other + terminals.

+ +

+ burncd(8) now supports + Disk At Once (DAO) mode, selectable via the -d flag. [MERGED]

+ +

+ burncd(8) now has the + ability to write VCDs/SVCDs. [MERGED]

+ +

+ burncd(8) now accepts a + value of max for its -s option to set the drive's maximum write + speed.

+ +

+ bzgrep(1), + bzegrep(1), and + bzfgrep(1) have been + added to perform + grep(1)-type operations + on + bzip2(1)-compressed + files.

+ +

+ calendar(1) now takes a + -W option, which operates similar + to -A but without special + treatment at weekends, and a -Foption to change the notion of + ``Friday''.

+ +

+ catman(1) is now a C + program, instead of a Perl script.

+ +

+ cdcontrol(1) now + supports a speed command to set + the maximum speed to be used by the drive (the maximum + possible speed can be selected setting the speed to max).

+ +

A + check_utility_compat(3) + library function has been added to libc, to determine whether certain + FreeBSD base system utilities should behave in FreeBSD + 4-compatible mode or in a ``standard'' mode (default + standard). The configuration is done + malloc(3)-style, with + either an environment variable or a symbolic link.

+ +

+ chflags(1) has moved + from /usr/bin to /bin.

+ +

+ chmod(1) now supports a + -h for changing the mode of a + symbolic link.

+ +

+ chmod(1) now also, when + the mode is modified, prints the old and new modes if the + -v option is specified more than + once.

+ +

+ chown(8) no longer + takes . as a user/group + delimeter. This change was made to support usernames + containing a ..

+ +

Use of the CSMG_* macros no + longer require inclusion of <sys/param.h>

+ +

A compat4x distribution has + been added for compatibility with FreeBSD 4-STABLE.

+ +

+ cp(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A new + csplit(1) utility, + which splits files based on context, has been added.

+ +

+ ctags(1) now creates + tags for typedefs, structs, unions, and enums by default + (implying the -t option). The new + -T reverts to the old + behavior.

+ +

The + daemon(8) program, a + command-line interface to + daemon(3), has been + added. It detaches itself from its controlling terminal + and executes a program specified on the command line. + This allows the user to run an arbitrary program as if it + were written to be a daemon. [MERGED]

+ +

The + devd(8) utility, a + userland daemon that can run arbitrary commands when + devices come and go in the device tree, has been added. + This program is a generalization of some of the + functionality of + pccardd(8).

+ +

+

+
Note: + devd(8) is + work-in-progress.
+

+

+
+
+ +

+ devinfo(8), a simple + tool to print the device tree and resource usage by + devices, has been added.

+ +

diskpart(8) has been declared obsolete, and has been + removed.

+ +

+ dump(8) now supports a + new -S flag to allow it to just + print out the dump size estimates and exit. [MERGED]

+ +

+ expr(1) is now + compliant with POSIX.2-1992 (and thus also with + POSIX.1-2001). Some program depend on the old, historic + behavior and do not properly protect their arguments to + keep them from being misinterpreted as command-line + options. (the + devel/libtool port/package, + used by many GNU programs, is a notable example). The old + behavior can be requested by enabling compatibility mode + for + expr(1) as described in + + check_utility_compat(3).

+ +

+ fbtab(5) now accepts + glob matching patterns for target devices, not just + individual devices and directories.

+ +

+ fdread(1), a program to + read data from floppy disks, has been added. It is a + counterpart to + 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 + dd(1).

+ +

+ finger(1) now has + support for a .pubkey file. + [MERGED]

+ +

+ finger(1) now supports + a -g flag to restrict the + printing of GECOS information to the user's full name + only. [MERGED]

+ +

+ finger(1) now supports + the -4 and -6 flags to specify an address family for + remote queries. [MERGED]

+ +

+ fold(1) now supports a + -b flag to break at byte + positions and a -s flag to break + at word boundaries. [MERGED]

+ +

+ fsck(8) wrappers have + been imported; this feature provides infrastructure for + + fsck(8) to work on + different types of filesystems (analogous to + mount(8)).

+ +

The behavior of + fsck(8) when dealing + with various passes (a la /etc/fstab) has been modified to + accommodate multiple-disk filesystems.

+ +

+ fsck(8) now has support + for foreground (-F) and + background (-B) checks. + Traditionally, + fsck(8) is invoked + before the filesystems are mounted and all checks are + done to completion at that time. If background checking + is available, + fsck(8) is invoked + twice. It is first invoked at the traditional time, + before the filesystems are mounted, with the -F 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 -B 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 background_fsck option in + rc.conf(5).

+ +

+ fsck_ffs(8) now + supports background filesystem checks to mounted FFS + filesystems with the -B option + (softupdates must be enabled on these filesystems). The + -F flag now determines whether a + specified filesystem needs foreground checking.

+ +

+ ftpd(8) now supports + the -m option to permit guest + users to modify existing files if allowed by filesystem + permissions. In particular, this enables guest users to + resume uploads. [MERGED]

+ +

+ ftpd(8) now supports + the -M option to prevent guest + users from creating directories. [MERGED]

+ +

+ ftpd(8) now supports + -o and -O + options to disable the RETR + command; the former for everybody, and the latter only + for guest users. Coupled with -A + and appropriate file permissions, these can be used to + create a relatively safe anonymous FTP drop box for + others to upload to. [MERGED]

+ +

+ ftpd(8) now supports + the -W option to disable logging + FTP sessions to + wtmp(5). [MERGED]

+ +

The + getconf(1) utility has + been added. It prints the values of POSIX or X/Open path + or system configuration variables. [MERGED]

+ +

gifconfig(8) is obsolete and has been removed. Its + functionality is now handled by the tunnel and deletetunnel commands of + ifconfig(8).

+ +

+ gprof(1) now has a -K option to enable dynamic symbol + resolution from the currently-running kernel. With this + change, properly-compiled KLD modules are now able to be + profiled.

+ +

The ibcs(8), linux(8), osf1(8), and 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.

+ +

+ ifconfig(8) now has the + ability to set promiscuous mode on an interface, via the + new promisc flag. [MERGED]

+ +

+ ifconfig(8) now + supports a monitor interface + flag, which blocks transmission of packets on that + interface. This feature is useful for monitoring network + traffic without interacting with the network in + question.

+ +

By default, + inetd(8) is no longer + run by + rc(8) at boot-time, + although + sysinstall(8) gives the + option of enabling it during binary installations. + inetd(8) can also be + enabled by adding the following line to /etc/rc.conf:

+

+    inetd_enable="YES"
+

+ +

+ inetd(8) now has the + capability for limiting the maximum number of + simultaneous invocations of each service from a single IP + address. [MERGED]

+ +

+ ipfw(8) filter rules + can now match on the value of the IPv4 precedence + field.

+ +

+ kbdmap(1) and + vidfont(1) have been + converted from Perl to C.

+ +

+ kenv(1) now has the + ability to set or delete kernel environment + variables.

+ +

The kget(8) utility has been removed (it was only + useful for UserConfig, which is not present in FreeBSD + 5.0-DP2).

+ +

+ killall(1) no longer + tries to kill zombie processes unless the -z flag is specified.

+ +

+ ktrdump(8), a utility + to dump the ktr trace buffer from userland, has been + added.

+ +

+ ldd(1) now supports a + -a flag to list all the objects + that are needed by each loaded object.

+ +

libc is now thread-safe by + default; libc_r contains only + thread functions.

+ +

libstand now has support for + overwriting the contents of a file on a UFS filesystem + (it cannot expand or truncate files because the + filesystem may be dirty or inconsistent).

+ +

libgmp has been superceded + by libmp.

+ +

The functions from libposix1e have been integrated into libc.

+ +

+ lock(1) now accepts a + -v to disable switching VTYs + while the current terminal is locked. This permits + locking the entire console from a single terminal. + [MERGED]

+ +

+ lpc(8) has been + improved; lpc clean is now + somewhat safer, and a new lpc + tclean command has been added to check to see what + files would be removed by lpc + clean. lpc topq has been + reimplemented, and now allows for a much more flexible + specification of which jobs should be moved (such as a + range of job numbers, or a hostname). An lpc bottomq command has been added to move + jobs to the bottom of a print queue, and a new lpc setstatus command can be used to set a + printer's status message. [MERGED]

+ +

The + ls(1) program now + supports a -m flag to list files + across a page, a -p flag to force + printing of a / after + directories, and a -x flag to + sort filenames across a page. [MERGED]

+ +

+ makewhatis(1) is now a + C program, instead of a Perl script.

+ +

+ man(1) is no longer + installed SUID man, in order to + reduce vulnerabilities associated with generating + ``catpages'' (preformatted manual pages cached for + repeated viewing). As a result, + man(1) can no longer + create system catpages on a regular user's behalf. It is + still able to do so if the user has write permissions to + the directory holding catpages (e.g. a user's own + manpages) or if the running user is root.

+ +

The + mdmfs(8) command has + been added; it is a wrapper around + mdconfig(8), + disklabel(8), + newfs(8), and + mount(8) that mimics + the command line option set of the deprecated + mount_mfs(8).

+ +

+ mesg(1) now conforms to + SUSv3. Among other things, it now uses the first terminal + associated with the standard input, standard output or + standard error file descriptor, in that order. Thus, it + is possible to use the redirection facilities of a shell + (mesg n < /dev/ttyp1) to + control write access for other terminals.

+ +

+ mountd(8) and + nfsd(8) have moved from + /sbin to /usr/sbin.

+ +

+ mv(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A number of archaic features of + newfs(8) have been + removed; these implement tuning features that are + essentially useless on modern hard disks. These features + were controlled by the -O, -d, -k, -l, -n, -p, -r, -t, and -x + flags.

+ +

+ newfs(8) now supports a + -O flag to select the creation of + UFS1 or UFS2 filesystems.

+ +

The + newgrp(1) utility to + change to a new group has been added.

+ +

+ newsyslog(8) now + compresses log files using + bzip2(1) by default. + (The former behavior of using + gzip(1) can be + specified in /etc/newsyslog.conf.)

+ +

The + nextboot(8) utility has + been added to specify an alternate kernel and/or boot + flags to be used the next time the machine is booted. A + previous incarnation of this feature first appeared in + FreeBSD 2.2.

+ +

NFS now works over + IPv6.

+ +

+ nice(1) now uses the + -n option to specify the + ``niceness'' of the utility being run. [MERGED]

+ +

nsswitch support has been + merged from NetBSD. By creating an + nsswitch.conf(5) file, + FreeBSD can be configured so that various databases such + as + passwd(5) and + group(5) can be looked + up using flat files, NIS, or Hesiod. If /etc/nsswitch.conf does not exist, it + will be automatically generated from an existing /etc/hosts.conf at system startup + time. The /etc/hosts.conf file + may be used by old executables; it will be automatically + generated from an existing /etc/nsswitch.conf during system startup + if it exists.

+ +

+ od(1) now supports the + -A option to specify the input + address base, the -N option to + specify the number of bytes to dump, the -j option to specify the number of bytes to + skip, the -s option to output + signed decimal shorts, and the -t + option to specify output type. [MERGED]

+ +

PAM support has been added + for account management and sessions.

+ +

PAM configuration is now + specified by files in /etc/pam.d/, rather than a single /etc/pam.conf file. /etc/pam.d/README has more details.

+ +

A + pam_echo(8) echo + service module has been added.

+ +

A + pam_exec(8) program + execution service module has been added.

+ +

A + pam_ftp(8) module has + been added to allow authentication of anonymous FTP + users.

+ +

A + pam_ftpusers(8) module + has been added to perform checks against the + ftpusers(5) file.

+ +

A + pam_ksu(8) module has + been added to do Kerberos 5 authentication and $HOME/.k5login authorization for + su(1).

+ +

A + pam_lastlog(8) module + has been added to record sessions in the + utmp(5), + wtmp(5), and + lastlog(5) + databases.

+ +

A + pam_login_access(8) + module has been added, to allow checking against /etc/login.access.

+ +

The + pam_nologin(8) module, + which can disallow logins using + nologin(5), has been + added.

+ +

The + pam_opie(8) and + pam_opieaccess(8) + modules have been added to control authentication via + opie(4). [MERGED]

+ +

A + pam_passwdqc(8) module + has been added, to check the quality of passwords + submitted during password changes.

+ +

A + pam_rhosts(8) module + has been added to support + rhosts(5) + authentication.

+ +

The + pam_rootok(8) module, + which can be used to authenticate only the superuser, has + been added.

+ +

A + pam_securetty(8) module + has been added to check the ``security'' of a TTY, as + listed in + ttys(5).

+ +

A + pam_self(8) module, + which allows self-authentication of a user, has been + added.

+ +

A + pam_wheel(8) module has + been added to permit authentication to members of a + group, which defaults to wheel.

+ +

The + pathchk(1) utility, + which checks pathnames for validity or portability + between POSIX systems, has been added. [MERGED]

+ +

+ ping(8) now supports a + -o flag to exit after receiving a + reply.

+ +

prefix(8) is obsolete and has been removed. Its + functionality is provided by the eui64 command to + ifconfig(8).

+ +

The + pselect(3) library + function (introduced by POSIX.1 as a slightly stronger + version of + select(2)) has been + added.

+ +

+ pwd(1) now supports the + -L flag to print the logical + current working directory. [MERGED]

+ +

+ quota(1) now takes a + -l flag to suppress quote checks + on NFS filesystems.

+ +

The pseudo-random number generator implemented by + rand(3) has been + improved to provide less biased results.

+ +

+ rcmd(3) now supports + the use of the RSH environment + variable to specify a program to use other than + rsh(1) for remote + execution. As a result, programs such as + dump(8), can use + ssh(1) for remote + transport.

+ +

+ rdist(1) has been + retired from the base system, but is still available from + FreeBSD Ports Collection as + net/44bsd-rdist.

+ +

The + renice(8) command + implements a -n option, which + specifies an increment to be applied to the priority of a + process. [MERGED]

+ +

+ rpcbind(8) has replaced + + portmap(8).

+ +

+ rpcgen(1) now uses /usr/bin/cpp (as on NetBSD), not + /usr/libexec/cpp.

+ +

+ rpc.lockd(8) has been + imported from NetBSD. This daemon provides support for + servicing client NFS locks.

+ +

+ rtld(1) will now print + the names of all objects that cause each object to be + loaded, if the LD_TRACE_LOADED_OBJECTS_ALL environment + variable is defined.

+ +

+ sed(1) now takes a -i option to enable in-place editing + of files. [MERGED]

+ +

The + setfacl(1) and + getfacl(1) commands + have been added to manage filesystem Access Control + Lists.

+ +

+ sh(1) no longer + implements printf as a built-in + command because it was considered less valuable compared + to the other built-in commands (this functionality is, of + course, still available through the + printf(1) + executable).

+ +

+ sh(1) now supports a + -C option to prevent existing + regular files from being overwritten by output + redirection, and a -u to give an + error if an unset variable is expanded. [MERGED]

+ +

The + sh(1) built-in cd command now supports -L and -P flags to + invoke logical or physical modes of operation, + respectively. Logical mode is the default, but the + default can be changed with the physical + sh(1) option. + [MERGED]

+ +

The + sh(1) built-in jobs command now supports a -s flag to output PIDs only and a -l flag to add PIDs to the output. + [MERGED]

+ +

+ sh(1) now supports a + bind built-in command, which + allows the key bindings for the shell's line editor to be + changed.

+ +

The + sh(1) built-in export and readonly commands now support a -p flag to print their output in + ``portable'' format. [MERGED]

+ +

+ sh(1) no longer accepts + invalid constructs as command & && command, && command, or || command. [MERGED]

+ +

+ spkrtest(8) is now a + sh(1) script, rather + than a Perl script.

+ +

+ split(1) now supports a + -a option to specify the number + of letters to use for the suffix of split files. + [MERGED]

+ +

In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, struct selinfo and related functions + have been moved to <sys/selinfo.h>.

+ +

+ su(1) now uses PAM for authentication.

+ +

+ sysctl(8) now accepts a + -d flag to print the descriptions + of variables.

+ +

The default root partition in + sysinstall(8) is now + 100MB on the i386 and pc98, 120MB on the Alpha.

+ +

+ sysinstall(8) now lives + in /usr/sbin, which simplifies + the installation process. The + sysinstall(8) manpage + is also installed in a more consistent fashion now.

+ +

+ sysinstall(8) no longer + mounts the + procfs(5) filesystem by + default on new installs.

+ +

+ tabs(1), a utility to + set terminal tab stops, has been added.

+ +

The + termcap(5) database now + uses the xterm terminal type + from XFree86. As a result, + xterm(1) now supports + color by default and the common workaround of setting TERM to xterm-color is no longer necessary. Use of + the xterm-color terminal type + may result in (benign) warnings from applications.

+ +

+ tftpd(8) now supports + RFC 2349 (TFTP Timeout Interval and Transfer Size + Options); this feature is required by some firmware like + EFI boot managers (at least on HP i2000 Itanium servers) + in order to boot an image using TFTP.

+ +

+ timed(8) now works on + the alpha.

+ +

A version of Transport Independent RPC (TI-RPC) has been imported.

+ +

+ tip(1) has been updated + from OpenBSD, and has the + ability to act as a + cu(1) substitute.

+ +

+ top(1) will now use the + full width of its tty.

+ +

+ touch(1) now takes a + -h option to operate on a + symbolic link, rather than what the link points to.

+ +

+ tr(1) now has basic + support for equivalence classes for locales that support + them. [MERGED]

+ +

+ tr(1) now supports a + -C flag to complement the set of + characters specified by the first string argument.

+ +

+ tunefs(8) now supports + the -a and -l flags to enable and disable the FS_ACLS and FS_MULTILABEL administrative flags on UFS + file system.

+ +

A + ugidfw(8) utility has + been added to manage the rulesets provided by the mac_bsdextended Mandatory Access + Control policy, similar to + ipfw(8).

+ +

UUCP has been removed from + the base system. It can be found in the Ports Collection, + in + net/freebsd-uucp.

+ +

+ unexpand(1) now + supports a -t to specify tabstops + analogous to + expand(1). [MERGED]

+ +

+ usbdevs(8) now supports + a -d flag to show the device + driver associated with each device.

+ +

The base64 capabilities of + uuencode(1) and + uudecode(1) can now be + automatically enabled by invoking these utilities as + b64encode(1) and + b64decode(1) + respectively. [MERGED]

+ +

Functions to implement and manipulate OSF/DCE + 1.1-compliant UUIDs have been added to libc. More information can be found in + uuid(3).

+ +

The + uuidgen(1) utility has + been added. It uses the new + uuidgen(2) system call + to generate one or more Universally Unique Identifiers + compatible with OSF/DCE 1.1 version 1 UUIDs.

+ +

+ vidcontrol(1) now + accepts a -S to allow the user to + disable VTY switching. [MERGED]

+ +

The default stripe size in + vinum(8) has been + changed from 256KB to 279KB, to spread out superblocks + more evenly between stripes.

+ +

+ wc(1) now supports a + -m flag to count characters, + rather than bytes.

+ +

+ whereis(1), formerly a + Perl script, has been rewritten in C. It now supports a + -x flag to suppress the run of + locate(1), and a -q flag suppresses the leading name + of the query.

+ +

+ whereis(1) now supports + a -a flag to report all matches + instead of only the first of each requested type.

+ +

+ which(1) is now a C + program, rather than a Perl script.

+ +

+ who(1) now has a number + of new options: -H shows column + headings; -T shows + mesg(1) state; -m is an equivalent to am i; -u shows idle + time; -q to list names in + columns. [MERGED]

+ +

+ wicontrol(8) now + supports a -l to list the + stations associated in hostap + mode and a -L to list available + access points.

+ +

+ xargs(1) now supports a + -I replstr option that allows the + user to tell + xargs(1) to insert the + data read from standard input at specific points in the + command line arguments rather than at the end. (A + FreeBSD-specific -J option is + similar.) [MERGED]

+ +

+ xargs(1) now supports a + -L option to force its utility + argument to be called after some number of lines. + [MERGED]

+ +

Various routines in the C library now have support for + ``wide'' characters. Among these are character class + functions such as + wctype(3), wide + character I/O functions such as + getwc(3), formatted I/O + functions such as + wprintf(3) and + wscanf(3). Conversion + functions to + multibyte(3) characters + are also supported.

+ +

A number of utilities and libraries were enhanced to + improve their conformance with the Single UNIX + Specification (SUSv3) and IEEE Std 1003.1-2001 + (``POSIX.1''). Specific features added have been listed + in the release notes for each utility. The standards + conformance of each utility or library function is + generally listed in its manual page.

+ +

A number of games have been removed from the base + system. These include: adventure(6), arithmetic(6), + atc(6), backgammon(6), battlestar(6), bs(6), canfield(6), + cribbage(6), fish(6), hack(6), hangman(6), larn(6), + mille(6), phantasia(6), piano(6), pig(6), quiz(6), + rain(6), robots(6), rogue(6), sail(6), snake(6), trek(6), + wargames(6), worm(6), worms(6), wump(6). dm(8), which was + used to control access to games, is no longer necessary, + and has also been removed. The ``utility-like'' games, as + well as + fortune(6), remain.

+ +

+

+
Note: The affected programs will reappear + as a port in the Ports Collection. This note will + contain a pointer to that port, once it has been + committed.
+

+

+
+
+ +

+

+ +

2.3.1 Contributed + Software

+ +

am-utils has been updated + to 6.0.7.

+ +

A 10 February 2002 snapshot of awk from Bell Labs (variously known + as ``BWK awk'' or ``The One True AWK'') has been + imported. It is available as awk or nawk.

+ +

BIND has been updated to + 8.3.3. [MERGED]

+ +

Binutils has been updated + to a pre-release snapshot of 2.13.1 from 11 October + 2002.

+ +

file has been updated to + 3.39.

+ +

gcc has been updated to a + pre-release snapshot of gcc + 3.2.1, from 9 October 2002.

+ +

+

+
Warning: The C++ ABI from gcc 3.2.X is not compatible with + previous versions.
+

+

+
+
+ +

gdb has been updated to + version 5.2.1.

+ +

gperf has been updated to + 2.7.2.

+ +

groff and its related + utilities have been updated to FSF version 1.18.1.

+ +

Heimdal Kerberos has been + updated to a pre-0.5 snapshot from 16 September + 2002.

+ +

The ISC DHCP client has + been updated to 3.0.1RC9.

+ +

The + more(1) command has + been replaced by + less(1), although it + can still be run as more. + [MERGED] Version 371 of less + has been imported.

+ +

An XML processing library, named libbsdxml, has been added for the + benefit of XML-using utilities in the base system. It + is based almost entirely on an import of expat 1.95.5, but is installed under + a different name to avoid conflicts with any versions + of expat installed from the + Ports Collection.

+ +

libpcap has been updated + to 0.7.1. [MERGED]

+ +

libreadline has been + updated to 4.2.

+ +

libz has been updated to + 1.1.4.

+ +

lint has been updated to + snapshot of NetBSD + lint(1) as of 19 July + 2002.

+ +

lukemftp 1.6 beta 2 (the + FTP client from NetBSD) has replaced the FreeBSD + ftp(1) program. Among + its new features are more automation methods, better + standards compliance, transfer rate throttling, and a + customizable command-line prompt. Some environment + variables and command-line arguments have changed.

+ +

The FTP daemon from NetBSD, otherwise known as lukemftpd 1.2 beta 1, has been + imported and is available as + lukemftpd(8). + [MERGED]

+ +

+ m4(1) has been + imported from OpenBSD, as of 26 April 2002. + [MERGED]

+ +

ncurses has been updated + to 5.2-20020615.

+ +

The NTP suite of programs + has been updated to 4.1.1b.

+ +

OpenPAM (``Citronella'' + release) has been imported, replacing Linux-PAM.

+ +

The OPIE + one-time-password suite has been updated to 2.4. It has + completely replaced the functionality of S/Key. [MERGED]

+ +

Perl has been removed + from the FreeBSD base system. It can still be installed + from the FreeBSD Ports Collection or as a binary + package; moving it out of the base system will make + future upgrades and maintenence easier. To reduce the + dependence of the base system on Perl, many utilities + have been rewritten as shell scripts or C programs + (specific notes are made for each affected utility). + /usr/bin/perl is now a + ``wrapper'' program, so that programs expecting to find + a Perl interpreter there will be able to function + correctly.

+ +

+

+
Warning: The Perl removal and package + integration work is ongoing.
+

+

+
+
+ +

GNU ptx has been removed + from the base system. It is not used anywhere in the + base system, and has not been recently updated or + maintained. Users requiring its functionality can + install this utility as a part of the + textproc/textutils + port.

+ +

The rc.d framework from + NetBSD has been imported. It breaks down the system + startup functionality into a number of small, + ``task-oriented'' scripts in /etc/rc.d, with dynamic-determined + ordering of startup scripts performed at boot-time.

+ +

GNU sort has been updated + to the version from GNU + textutils 2.0.21.

+ +

+ stat(1) from NetBSD, as of 5 June 2002 has, + been imported.

+ +

GNU tar has been updated + to 1.13.25. [MERGED]

+ +

tcpdump has been updated + to 3.7.1. [MERGED]

+ +

The + csh(1) shell has been + replaced by + tcsh(1), although it + can still be run as csh. tcsh has been updated to + version 6.12. [MERGED]

+ +

The contributed version of tcp_wrappers now includes the + tcpd(8) helper + daemon. While not strictly necessary in a standard + FreeBSD installation (because + inetd(8) already + incorporates this functionality), this may be useful + for + inetd(8) replacements + such as xinetd. [MERGED]

+ +

texinfo has been updated + to 4.2. [MERGED]

+ +

top has been updated to + version 3.5b12. [MERGED]

+ +

traceroute has been + updated to LBL version 1.4a12.

+ +

The timezone database has been updated to the tzdata2002d release. [MERGED]

+ +

+

+ +

2.3.1.1 + CVS

+ +

cvs has been updated to + 1.11.2. [MERGED]

+

+ +

+

+ +

2.3.1.2 + CVSup

+

+ +

+

+ +

2.3.1.3 + KAME

+

+ +

+

+ +

2.3.1.4 + OpenSSH

+ +

OpenSSH has been + updated to version 3.1. [MERGED] Among the + changes:

+ +

+
The *2 files are + obsolete (for example, ~/.ssh/known_hosts can hold the + contents of ~/.ssh/known_hosts2).
+
+
+ ssh-keygen(1) + can import and export keys using the SECSH Public + Key File Format, for key exchange with several + commercial SSH implementations.
+
+
+ ssh-add(1) now + adds all three default keys.
+
+
+ ssh-keygen(1) + no longer defaults to a specific key type; one + must be specified with the -t option.
+

+
+
+ +

OpenSSH has been + updated to 3.4p1. [MERGED] The main changes are:

+ +

+
A ``privilege separation'' feature, which uses + unprivileged processes to contain and restrict + the effects of future compromises or programming + errors.
+
+
Several bugfixes, including closure of a + security hole that could lead to an integer + overflow and undesired privilege escalation.
+

+
+
+

+ +

+

+ +

2.3.1.5 + OpenSSL

+ +

OpenSSL has been + updated to 0.9.6g. [MERGED]

+

+ +

+

+ +

2.3.1.6 + sendmail

+ +

sendmail has been + updated from version 8.9.3 to version 8.12.6. + Important changes include: + sendmail(8) is no + longer installed as a set-user-ID root binary (now set-group-ID smmsp); new default file + locations (see /usr/src/contrib/sendmail/cf/README); + + newaliases(1) is + limited to root and trusted + users; STARTTLS encryption; and the MSA port (587) is + turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES + for more information. [MERGED]

+ +

By default, + rc(8) no longer + enables sendmail for + inbound SMTP connections. Note that + sysinstall(8) may + override this default for a binary installation, + based on what security profile is selected. This + functionality can also be manually enabled by adding + the following line to /etc/rc.conf:

+

+    sendmail_enable="YES"
+

+ +

The permissions for sendmail alias and map databases + built via /etc/mail/Makefile now default to + mode 0640 to protect against a file locking local + denial of service. It can be changed by setting the + new SENDMAIL_MAP_PERMS make.conf option. [MERGED]

+ +

The permissions for the sendmail statistics file, /var/log/sendmail.st, have been + changed from mode 0644 to mode 0640 to protect + against a file locking local denial of service. + [MERGED]

+

+ +

+

+ +

2.3.2 + Ports/Packages Collection Infrastructure

+ +

BSDPAN, a collection of + modules that provides tighter integration of Perl into the FreeBSD Ports + Collection, has been added.

+ +

For some time, FreeBSD 5.0-CURRENT (as well as some + 4.X releases) included a pkg_update(1) utility to + update installed packages, as well as their + dependencies. This utility has been removed; a superset + of its functionality can be found in the + sysutils/portupgrade + port.

+ +

+ pkg_version(1), + formerly a Perl script, has been rewritten in C.

+ +

The Ports Collection infrastructure now uses XFree86 4.2.1 as the default + version of the X Window System for the purposes of + satisfying dependencies. To return to using XFree86 3.3.6, add the following line + to /etc/make.conf: + [MERGED]

+

+    XFREE86_VERSION=3
+

+ +

The libraries installed by the + emulators/linux_base port + (required for Linux emulation) have been updated; they + now correspond to those included with Red Hat Linux 7.1. [MERGED]

+ +

By default, packages generated by the Ports + Collection (as well as the packages on the FTP sites) + are now compressed using + bzip2(1), rather than + + gzip(1). (Thus, they + now have a .tbz extension, + rather than a .tgz + extension.) The package tools have been updated to + handle the new format.

+

+ +

+

+ +

2.4 Release + Engineering and Integration

+ +

The bin distribution has + been renamed base, in order to + make creation of combined install/recovery disks + easier.

+ +

It is now possible to make releases of FreeBSD + 5-CURRENT on a FreeBSD 4-STABLE host and vice versa. + Cross-architecture (building a release for a target + architecture on a host of a different architecture) + releases are also possible. See + release(7) for details. + [MERGED]

+ +

A third drivers.flp floppy + has been added to floppy releases. It holds loadable + modules containing drivers that do not fit in the kernel + on the kern.flp disk or in the + mfsroot.flp image.

+

+ +

+

+ +

2.5 + Documentation

+ +

A number of formerly-encumbered documents from the 4.4 + BSD Programmer's Supplementary Documents have been + restored to /usr/share/doc/psd. + These include:

+ +

+
The + UNIX Time-Sharing System (01.cacm)
+
+
UNIX + Implementation (02.implement)
+
+
The + UNIX I/O System (03.iosys)
+
+
UNIX + Programming -- Second Edition (04.uprog)
+
+
The C + Programming Language -- Reference Manual + (06.Clang)
+
+
Yacc: + Yet Another Compiler-Compiler (15.yacc)
+
+
Lex -- + A Lexical Analyzer Generator (16.lex)
+
+
The M4 + Macro Processor (17.m4)
+

+ +

Several formerly-encumbered documents from the 4.4 BSD + User's Supplementary Documents have been restored to /usr/share/doc/usd. They + include:

+ +

+
NROFF/TROFF User's Manual (21.troff)
+
+
A TROFF + Tutorial (22.trofftut)
+

+

+ +

+

+ +

3 Upgrading from + previous releases of FreeBSD

+ +

Users with existing FreeBSD systems are highly encouraged + to read the ``Early Adopter's Guide to FreeBSD 5.0''. This + document generally has the filename EARLY.TXT on the distribution media, or any + other place that the release notes can be found. It offers + some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.X versus + running FreeBSD 4.X.

+ +

+

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

+

FreeBSD/i386 5.0-DP2 + Release Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.452 2002/11/14 17:59:11 bmah Exp $
+

+ +

+

+ + +

The release notes for FreeBSD 5.0-DP2 contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. Both + changes for kernel and userland are listed, as well as + applicable security advisories that were issued since + the last release. Some brief remarks on upgrading are + also presented.

+

+ +

+

Table of Contents

+

+

2.1.1 Processor/Motherboard + Support
2.1.2 Bootloader + Changes
2.1.3 Network Interface + Support
2.1.4 Network + Protocols
2.1.5 Disks and + Storage
2.1.6 Filesystems
2.1.7 PCCARD + Support
2.1.8 Multimedia + Support
2.1.9 Contributed + Software

+

+

2.3.1 Contributed + Software
2.3.2 Ports/Packages + Collection Infrastructure

+

3 Upgrading from previous releases + of FreeBSD

+

+

+ +

+

+ +

1 Introduction

+ +

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

+ +

The snapshot distribution to which these release notes + apply represents a point along the 5-CURRENT development + branch between 4.0-RELEASE and the future 5.0-RELEASE. Some + pre-built, binary snapshot distributions along this branch + can be found at http://snapshots.jp.FreeBSD.org/.

+

+ +

+

+ +

2 What's New

+ +

This section describes many of the user-visible new or + changed features in FreeBSD since 4.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 4.6-RELEASE). The later items are + marked as [MERGED].

+ +

Typical release note items document new drivers or + hardware support, new commands or options, major bugfixes, + or contributed software upgrades. Applicable security + advisories issued after 4.0-RELEASE are also listed.

+ +

Many additional changes were made to FreeBSD 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.

+ +

+

+ +

2.1 Kernel + Changes

+ +

Execution of + a.out(5) format + executables now requires the COMPAT_AOUT option in the kernel + configuration or the loading of the aout.ko kernel module.

+ +

+ acct(2) has been + changed to open the accounting file in append mode, so + that + accton(8) can be used + to enable accounting to an append-only file. [MERGED]

+ +

A new in-kernel cryptographic framework (see + crypto(4) and + crypto(9)) has been + imported from OpenBSD. It provides a consistent interface + to hardware and software implementations of cryptographic + algorithms for use by the kernel and access to + cryptographic hardware for user-mode applications. + Hardware device drivers are provided to support + hifn-based cards ( + hifn(4)) and + Broadcom-based cards ( + ubsec(4)).

+ +

A new + ddb(4) command show pcpu lists some of the per-CPU + data.

+ +

A devctl device has been + added to allow userland programs to learn when devices + come and go in the device tree (different from the XXX). + This facility is primariliy used by the + devd(8) utility.

+ +

+ devfs(5), which allows + entries in the /dev directory + to be built automatically and supports more flexible + attachment of devices, has been largely reworked. + devfs(5) is now enabled + by default and can be disabled by the NODEVFS kernel option.

+ +

The + devfs(5) ``rule'' + subsystem has been introduced. DEVFS rules permit the + administrator to define certain properties of new device + nodes before they become visible to the userland. Both + static (e.g. /dev/speaker) and + dynamic (e.g. /dev/bpf*, some + removable devices) nodes are supported. Each + devfs(5) mount may have + a different ruleset assigned to it, permitting different + policies to be implemented for things like jails. Rules + and rulesets are manipulated with the + devfs(8) utility.

+ +

The dgm driver has been removed in favor of the digi + driver.

+ +

A new digi driver has been added to support PCI + Xr-based and ISA Xem Digiboard cards. A new + digictl(8) program is + (mainly) used to re-initialize cards that have external + port modules attached such as the PC/Xem.

+ +

An + eaccess(2) system call + has been added, similar to + access(2) except that + the former uses effective credentials rather than real + credentials.

+ +

Initial support has been added for Firewire devices + (see + firewire(4)). + [MERGED]

+ +

Each + jail(2) environment can + now run under its own securelevel.

+ +

The tunable sysctl variables for + jail(2) have moved from + jail.* to the security.* hierarchy. Other + security-related sysctl variables have moved from kern.security.* to security.*.

+ +

The kernel environment is now dynamic, and can be + changed via the new + kenv(2) system + call.

+ +

The labpc(4) driver has been removed due to + ``bitrot''.

+ +

The loader and kernel linker now look for files named + linker.hints in each directory + with KLDs for a module name and version to KLD filename + mapping. The new + kldxref(8) utility is + used to generate these files.

+ +

+ lomac(4), a + Low-Watermark Mandatory Access Control security facility, + has been added as a kernel module. It provides a drop-in + security mechanism in addition to the traditional + UID-based security facilities, requiring no additional + configuration from the administrator. Work on this + feature was sponsored by DARPA and NAI Labs.

+ +

FreeBSD now supports an extensible Mandatory Access + Control framework, the TrustedBSD MAC Framework. It + permits loadable kernel modules to link to the kernel at + compile-time, boot-time, or run-time, and augment the + system security policy. The framework permits modules to + express interest in a variety of events, and also + provides common security policy services such as label + storage. A variety of sample policy modules are shipped + in this release, including implementations of fixed and + floating label Biba integrity models, Multi-Level + Security (MLS) with compartments, and a number of + augmented UNIX security models including a file system + firewall. This feature will permit easier development and + maintenance of local and vendor security extensions. The + extensibility service is enabled by adding options MAC to the kernel + configuration.

+ +

+

+
Note: The MAC framework is considered an + experimental feature in this release, and is not + enabled by default
+

+

+
+
+ +

+ mutex(9) profiling code + has been added, enabled by the MUTEX_PROFILING kernel configuration + option. It enables the debug.mutex.prof.* hierarchy of sysctl + variables.

+ +

The P1003_1B kernel option is + no longer used and has been removed.

+ +

PECOFF (Win32 Execution file format) support has been + added.

+ +

The + random(4) device has + been rewritten to use the Yarrow 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 + random(4) device is now + periodically saved to files in /var/db/entropy, as well as at shutdown + time. The semantics of /dev/random have changed; it never blocks + waiting for entropy bits but generates a stream of + pseudo-random data and now behaves exactly as /dev/urandom.

+ +

A new kernel option, options + REGRESSION, enables interfaces and functionality + intended for use during correctness and regression + testing.

+ +

RLIMIT_VMEM support has been + added. This feature defines a new resource limit that + covers a process's entire virtual memory space, including + + mmap(2) space. This + limit can be configured in + login.conf(5) via the + new vmemoryuse variable. + [MERGED]

+ +

A bug in the + sendfile(2) system + call, in which headers counted against the size of the + file to be sent, has been fixed. [MERGED]

+ +

The + syscons(4) driver now + supports keyboard-controlled pasting, by default bound to + Shift-Insert.

+ +

The uaudio driver, for USB audio devices, has been + added. [MERGED]

+ +

The ubsa driver has been added to support the Belkin + F5U103 (and compatible) USB-to-serial adaptors.

+ +

The + ucom(4) device driver + has been added, to support USB modems, serial devices, + and other programs that need to look like a tty. The + related + uplcom(4) and + uvscom(4) drivers + provide specific support for the Prolific PL-2303 serial + adapter and the SUNTAC Slipper U VS-10U, respectively. + [MERGED]

+ +

To increase security, the UCONSOLE kernel configuration option has + been removed.

+ +

The UserConfig boot-time kernel configuration feature, + usually used to enable, disable, or configure ISA + devices, has been removed. Its functionality has been + replaced by the kernel hints file in /boot/device.hints.

+ +

The USER_LDT kernel option is + now activated by default.

+ +

The + uvisor(4) driver for + connecting Handspring Visors via USB has been added. + [MERGED]

+ +

A VESA S3 linear framebuffer driver has been + added.

+ +

The kernel crashdump infrastructure has been revised, + to support new platforms and in general clean up the + logic in the code. One implication of this change is that + the on-disk format for kernel dumps has changed, and is + now byte-order-agnostic.

+ +

Extremely large swap areas (>67 GB) no longer panic + the system.

+ +

Linker sets are now self-contained; gensetdefs(8) is + unnecessary and has been removed.

+ +

It is now possible to hardwire kernel environment + variables (such as tuneables) at compile-time using + config(8)'s ENV directive.

+ +

Idle zeroing of pages can be enabled with the vm.idlezero_enable sysctl + variable.

+ +

The FreeBSD kernel scheduler now supports + Kernel-Scheduled Entities (KSEs), which provides support + for multiple threads of execution per process similar to + Scheduler Activations. At this point, the kernel has most + of the changes needed to support threading. The kernel + scheduler can schedule multiple threads per process, but + only on a single CPU at a time. More information can be + found in + kse(2).

+ +

+

+
Note: KSE is a work in progress.
+

+

+
+
+ +

The kernel now has support for multiple low-level + console devices. The new + conscontrol(8) utility + helps to manage the different consoles.

+ +

The kernel memory allocator is now a slab memory + allocator, similar to that used in Solaris. This is a + SMP-safe memory allocator that has near-linear + performance as the number of CPUs increases. It also + allows for reduced memory fragmentation.

+ +

+

+ +

2.1.1 + Processor/Motherboard Support

+ +

SMP support has been largely reworked, incorporating + code from BSD/OS 5.0. One of the main features of SMPng + (``SMP Next Generation'') 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.

+ +

Support for the 80386 processor has been removed + from the GENERIC kernel, as + this code seriously pessimizes performance on other + IA32 processors. The I386_CPU + 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. 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 I386_CPU.

+ +

On some systems, the BIOS does not activate the I/O + ports and memory of PC devices, thus making them + unusable. The hw.pci.enable_io_modes sysctl/boot + loader variable (which defaults to 1, for ``enabled'') forces FreeBSD to + enable these devices so that they can be used.

+ +

Support for the AMD Élan SC520 has been + added; this requires the CPU_ELAN option in the kernel + configuration file. [MERGED]

+ +

The CPU_DISABLE_CMPXCHG + kernel configuration option has been added. Enabling + this option has been shown to dramatically improve + performance on VMWare client OS installs.

+ +

+

+
Note: This option is not compatible with + SMP kernels.
+

+

+
+
+

+ +

+

+ +

2.1.2 Bootloader + Changes

+ +

The kernel and modules have been moved to the + directory /boot/kernel, so + they can be easily manipulated together. The boot + loader has been updated to make this change as seamless + as possible.

+

+ +

+

+ +

2.1.3 Network + Interface Support

+ +

The + dc(4) driver now + supports NICs based on the Xircom 3201 and Conexant + LANfinity RS7112 chips.

+ +

The + el(4) driver can now + be loaded as a module.

+ +

The + rp(4) driver has been + updated to version 3.02 and can now be built as a + module. [MERGED]

+ +

The + stf(4) device is now + clonable.

+ +

The + tx(4) driver now + supports true multicast filtering.

+ +

Network devices now automatically appear as special + files in /dev/net. Interface + hardware ioctls (not protocol or routing) can be + performed on these devices. The SIOCGIFCONF ioctl may be performed on + the special /dev/network + node.

+ +

``Zero copy'' support has been added to the + networking stack. This feature can eliminate a copy of + network data between the kernel and userland, which is + one of the more significant bottlenecks in network + throughput. The send-side code should work with almost + any network adapter, while the receive-side code + requires a network adapter with an MTU of at least one + memory page size (for example, jumbo frames on Gigabit + Ethernet). For more information, see + zero_copy(9).

+

+ +

+

+ +

2.1.4 Network + Protocols

+ +

A FAST_IPSEC kernel option + now allows the IPsec implementation to use the kernel + crypo framework, along with its support for hardware + cryptographic acceleration.

+ +

+

+
Note: The FAST_IPSEC and IPSEC options are mutually + exclusive.
+

+

+ +

+

+
Note: The FAST_IPSEC option is, at the moment, + not compatible with IPv6 or the INET6 option.
+

+

+
+
+ +

A + gre(4) driver, which + can encapsulate IP packets using GRE (RFC 1701) or + minimal IP encapsulation for Mobile IP (RFC 2004), has + been added.

+ +

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.

+ +

IP multicast now works on VLAN devices. Several + other bugs in the VLAN code have also been fixed.

+ +

+ ipfw(4) has been + re-implemented (the new version is commonly referred to + as ``IPFW2''). It now uses variable-sized + representation of rules in the kernel, similar to + bpf(4) instructions. + Most of the externally-visible behavior (i.e. through + + ipfw(8)) should be + unchanged., although + ipfw(8) now supports + or connectives between match + fields. [MERGED]

+ +

A new + ng_device(4) netgraph + node type has been added, which creates a device entry + in /dev, to be used as the + entry point to a networking graph.

+ +

The + ng_gif(4) and + ng_gif_demux(4) + netgraph nodes, for operating on + gif(4) devices, have + been added.

+ +

The + ng_ip_input(4) + netgraph node, for queueing IP packets into the main IP + input processing code, has been added.

+ +

A new + ng_l2tp(4) netgraph + node type, which implements the encapsulation layer of + the L2TP protocol as described in RFC 2661, has been + added. [MERGED]

+ +

A new ng_split node type has been added for + splitting a bidirectional packet flow into two + unidirectional flows.

+ +

The ephemeral port range used for TCP and UDP has + been changed to 49152-65535 (the old default was + 1024-5000). This increases the number of concurrent + outgoing connections/streams.

+ +

The + tcp(4) protocol's + retransmission timer can now be manipulated with two + sysctl variables, net.inet.tcp.rexmit_min and net.inet.tcp.rexmit_slop. The default + has been reduced from one second to 200ms (similar to + the Linux default) in order to better handle hicups + over interactive connections and improve recovery over + lossy fast connections such as wireless links.

+ +

The + tcp(4) protocol now + has the ability to dynamically limit the send-side + window to maximize bandwidth and minimize round trip + times. The feature can be enabled via the net.inet.tcp.inflight_enable sysctl. + [MERGED]

+

+ +

+

+ +

2.1.5 Disks and + Storage

+ +

The + ahd(4) driver, which + supports the Adaptec AIC7901, AIC7901A, and AIC7902 + Ultra320 PCI-X SCSI Controller chips, has been added. + [MERGED]

+ +

The + ata(4) driver (along + with + burncd(8)) now + supports writing to media in DVD+RW drives.

+ +

The + ata(4) driver now + supports accessing ATA devices as SCSI devices via the + CAM layer and drivers ( + cd(4), + da(4), + st(4), and + pass(4)). This + feature requires device + atapicam in the kernel configuration. More + information can be found in + atapicam(4). + [MERGED]

+ +

The + ata(4) driver now has + support for the Sil 0680 and VIA 8233/8235 controllers. + [MERGED]

+ +

The + cd(4) driver now + supports the same CDRIOCREADSPEED and CDRIOCWRITESPEED ioctls that the + acd(4) driver uses + for setting the speed of CDROM access.

+ +

The + fdc(4) floppy disk + has undergone a number of enhancements. Density + selection for common settings is now automatic; the + driver is also much more flexible in setting the + densities of various subdevices.

+ +

The + geom(4) disk I/O + request transformation framework has been added; this + extensible framework is designed to support a wide + variety of operations on I/O requests on their way from + the upper kernel to the device drivers.

+ +

+

+
Note: GEOM-enabled kernels no longer + support ``compatability slices''. This feature + (supported on the i386 and pc98 only) allowed a + user to refer to a disk partition without + specifying an MBR slice (e.g. /dev/ad0a); the kernel would + automatically find the first applicable FreeBSD + slice and use it. On GEOM kernels, only the full + partition names (e.g. /dev/ad0s1a) are allowed when + referring to partitions within MBR slices. This + change should affect very few users.
+

+

+
+
+ +

A GEOM Based Disk Encryption module has been added. + It provides denial of access to ``cold disks'', with + four different cryptographic barriers and up to four + changeable pass-phrases. Much more information can be + found in the + gbde(4) manual page. + The + gbde(8) userland + utility provides an operation and management interface + to this module. This feature is not enabled by default; + it requires options GEOM_BDE + to be added to a kernel configuration file.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

The + isp(4) driver is now + proactive about discovering Fibre Channel topology + changes.

+ +

The + isp(4) driver now + supports target mode for Qlogic SCSI cards, including + Ultra2 and Ultra3 and dual bus cards.

+ +

The + matcd(4) driver has + been removed due to breakage and licensing issues. + [MERGED]

+ +

+ md(4), the memory + disk device, has had the functionality of + vn(4) incorporated + into it. + md(4) devices can now + be configured by + mdconfig(8). + vn(4) has been + removed. The Memory Filesystem (MFS) has also been + removed.

+ +

The mpt driver, for supporting the LSI Logic + Fusion/MP architecture Fiber Channel controllers, has + been added. [MERGED]

+ +

The + pst(4) driver, for + supporting Promise SuperTrak ATA RAID controllers, has + been added. [MERGED]

+ +

The RAIDframe disk driver has been imported from + NetBSD. This driver provides software-based RAID 0, 1, + 4, and 5 capabilities, as well as other functionality. + More information can be found in the + raid(4) driver manual + page. The + raidctl(8) utility is + used to configure and unconfigure disk arrays. This + feature is not enabled by default, and requires device raidframe to be configured + into a kernel.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

Some problems in + sa(4) error handling + have been fixed, including the ``tape drive spinning + indefinitely upon + mt(1) stat'' problem.

+ +

The SCSI_DELAY + configuration parameter can now be set at boot time and + runtime via the kern.cam.scsi_delay tunable/sysctl.

+ +

The trm driver has been added to support SCSI + adapters using the Tekram TRM-S1040 SCSI chipset.

+

+ +

+

+ +

2.1.6 + Filesystems

+ +

Support for named extended attributes was added to + the FreeBSD 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 /usr/src/sys/ufs/ufs/README.extattr for + details).

+ +

A filesystem snapshot capability has been added to + FFS. Details can be found in /usr/src/sys/ufs/ffs/README.snapshot.

+ +

Softupdates for FFS have received some bug fixes and + enhancements.

+ +

When running with softupdates, + statfs(2) and + df(1) will track the + number of blocks and files that are committed to being + freed.

+ +

+ kernfs(5) is obsolete + and has been retired.

+ +

Client-side NFS locks have been implemented.

+ +

The client-side and server-side of the NFS code in + the kernel used to be intertwined in various complex + ways. They have been split apart for ease of + maintenance and further development.

+ +

Support for filesystem 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 /usr/src/sys/ufs/ufs/README.acls.

+ +

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. Compatibility ``glue'' has + been added to + mount(8) so that msdos filesystem entries in + fstab(5) will work + without changes.

+ +

pseudofs, a pseudo-filesystem framework, has been + added. + linprocfs(5) and + procfs(5) have been + modified to use pseudofs.

+ +

Network filesystems (such as NFS and smbfs + filesystems) listed in /etc/fstab can now be properly mounted + during startup initialization; their mounts are + deferred until after the network is initialized.

+ +

Read-only support for the Universal Disk Format + (UDF) has been added. This format is used on + packet-written CD-RWs and most commercial DVD-Video + disks. The + mount_udf(8) command + can be used to mount these disks.

+ +

Basic support has been added for the UFS2 + filesystem. Among its features:

+ +

+
The inode has been expanded to 256 bytes to make + space for 64-bit block pointers.
+
+
A file-creation time field has been added.
+
+
A native extended attributes implementation has + been added, permitting total attribute size stored + on an inode to be up to twice the filesystem block + size. This storage is used for Access Control Lists + and MAC labels, but may also be used by other + system extensions and user applications.
+

+
+
+

+ +

+

+ +

2.1.7 PCCARD + Support

+ +

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.

+ +

NEWCARD is now the default pccard/cardbus system in + the GENERIC kernel.

+

+ +

+

+ +

2.1.8 Multimedia + Support

+ +

The VT8233 audio controller now has its own driver + to facilitate supporting all known revisions of the + hardware. It is loadable at boot time by adding device pcm to the kernel + configuration or by adding snd_via8233="YES" to /boot/loader.conf. Documentation to + support this work was provided by VIA. [MERGED]

+ +

A new API has been added for sound cards with + hardware volume control.

+ +

The ich sound driver now provides rudimentary + support for ich4 audio support. [MERGED]

+ +

Drivers have been added to support the Direct + Rendering Infrastructure, which can used to provide 3D + acceleration within XFree86. + Video cards supported include the 3Dlabs Oxygen GMX + 2000 (gammadrm), AGP Matrox G200/G400/G450/G550 + (mgadrm), 3dfx Voodoo 3/4/5/Banshee (tdfxdrm), AGI ATI + Rage 128 (r128drm), and AGP ATI Radeon (radeondrm).

+

+ +

+

+ +

2.1.9 Contributed + Software

+ +

The Forth Inspired Command Language (FICL) used in the boot loader has + been updated to 3.02.

+ +

Support for Advanced Configuration and Power + Interface (ACPI), a multi-vendor standard for + configuration and power management, has been added. + This functionality has been provided by the Intel ACPI Component Architecture + project, as of the ACPI CA 20020815 snapshot. Some + backward compatability for applications using the older + APM standard has been provided.

+ +

+

+ +

2.1.9.1 + IPFilter

+ +

IPFilter has been + updated to 3.4.29. [MERGED]

+

+ +

+

+ +

2.1.9.2 + isdn4bsd

+ +

isdn4bsd has been + updated to version 1.0.2.

+ +

isdn4bsd now supports + Q.931 subaddressing.

+

+ +

+

+ +

2.1.9.3 + KAME

+

+ +

+

+ +

2.2 Security-Related + Changes

+ +

A bug in which malformed ELF executable images can + hang the system has been fixed (see security advisory + FreeBSD-SA-00:41). [MERGED]

+ +

A security hole in Linux emulation was fixed (see + security advisory FreeBSD-SA-00:42). [MERGED]

+ +

TCP now uses stronger randomness in choosing its + initial sequence numbers (see security advisory + FreeBSD-SA-00:52). [MERGED]

+ +

Several buffer overflows in + tcpdump(1) were + corrected (see security advisory FreeBSD-SA-00:61). + [MERGED]

+ +

A security hole in + top(1) was corrected + (see security advisory FreeBSD-SA-00:62). [MERGED]

+ +

A potential security hole caused by an + off-by-one-error in + gethostbyname(3) has + been fixed (see security advisory FreeBSD-SA-00:63). + [MERGED]

+ +

A potential buffer overflow in the + ncurses(3) library, + which could cause arbitrary code to be run from within + systat(1), has been + corrected (see security advisory FreeBSD-SA-00:68). + [MERGED]

+ +

A vulnerability in + telnetd(8) that could + cause it to consume large amounts of server resources has + been fixed (see security advisory FreeBSD-SA-00:69). + [MERGED]

+ +

The nat deny_incoming command + in + ppp(8) now works + correctly (see security advisory FreeBSD-SA-00:70). + [MERGED]

+ +

A vulnerability in + csh(1)/ + tcsh(1) temporary files + that could allow overwriting of arbitrary user-writable + files has been closed (see security advisory + FreeBSD-SA-00:76). [MERGED]

+ +

Several vulnerabilities in + procfs(5) were fixed + (see security advisory FreeBSD-SA-00:77). [MERGED]

+ +

A bug in OpenSSH in which a + server was unable to disable + ssh-agent(1) or X11Forwarding was fixed (see + security advisory FreeBSD-SA-01:01). [MERGED]

+ +

A bug in + ipfw(8) and + ip6fw(8) in which + inbound TCP segments could incorrectly be treated as + being part of an established + connection has been fixed (see security advisory + FreeBSD-SA-01:08). [MERGED]

+ +

A bug in + crontab(1) that could + allow users to read any file on the system in valid + crontab(5) syntax has + been fixed (see security advisory FreeBSD-SA-01:09). + [MERGED]

+ +

A vulnerability in + inetd(8) that could + allow read-access to the initial 16 bytes of wheel-accessible files has been fixed + (see security advisory FreeBSD-SA-01:11). [MERGED]

+ +

A bug in + periodic(8) that used + insecure temporary files has been corrected (see security + advisory FreeBSD-SA-01:12). [MERGED]

+ +

OpenSSH 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]

+ +

A bug in + timed(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:28). + [MERGED]

+ +

A bug in + rwhod(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:29). + [MERGED]

+ +

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]

+ +

A remotely-exploitable vulnerability in + ntpd(8) has been closed + (see security advisory FreeBSD-SA-01:31). [MERGED]

+ +

A security hole in IPFilter's fragment cache has been + closed (see security advisory FreeBSD-SA-01:32). + [MERGED]

+ +

Buffer overflows in + 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, + glob(3) allows + specification of a limit on the number of pathname + matches it will return. + ftpd(8) now uses this + feature (see security advisory FreeBSD-SA-01:33). + [MERGED]

+ +

Initial sequence numbers in TCP are more thoroughly + randomized (see security advisory FreeBSD-SA-01:39). Due + to some possible compatibility issues, the behavior of + this security fix can be enabled or disabled via the net.inet.tcp.tcp_seq_genscheme + sysctl variable.[MERGED]

+ +

A vulnerability in the + 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]

+ +

A flaw allowed some signal handlers to remain in + effect in a child process after being exec-ed from its + parent. This allowed an attacker to execute arbitrary + code in the context of a setuid binary. This flaw has + been corrected (see security advisory FreeBSD-SA-01:42). + [MERGED]

+ +

A remote buffer overflow in + tcpdump(1) has been + fixed (see security advisory FreeBSD-SA-01:48). + [MERGED]

+ +

A remote buffer overflow in + telnetd(8) has been + fixed (see security advisory FreeBSD-SA-01:49). + [MERGED]

+ +

The new net.inet.ip.maxfragpackets and net.inet.ip6.maxfragpackets sysctl + variables limit the amount of memory that can be consumed + by IPv4 and IPv6 packet fragments, which defends against + some denial of service attacks (see security advisory + FreeBSD-SA-01:52). [MERGED]

+ +

A flaw in the implementation of the + ipfw(8) me rules on point-to-point links has been + corrected. Formerly, me filter + rules would match the remote IP address of a + point-to-point interface in addition to the intended + local IP address (see security advisory + FreeBSD-SA-01:53). [MERGED]

+ +

A vulnerability in + procfs(5), which could + allow a process to read sensitive information from + another process's memory space, has been closed (see + security advisory FreeBSD-SA-01:55). [MERGED]

+ +

The PARANOID hostname + checking in tcp_wrappers now + works as advertised (see security advisory + FreeBSD-SA-01:56). [MERGED]

+ +

A local root exploit in + sendmail(8) has been + closed (see security advisory FreeBSD-SA-01:57). + [MERGED]

+ +

A remote root vulnerability in + lpd(8) has been closed + (see security advisory FreeBSD-SA-01:58). [MERGED]

+ +

A race condition in + rmuser(8) that briefly + exposed a world-readable /etc/master.passwd has been fixed (see + security advisory FreeBSD-SA-01:59). [MERGED]

+ +

A vulnerability in UUCP has + been closed (see security advisory FreeBSD-SA-01:62). All + non-root-owned binaries in + standard system paths now have the schg flag set to prevent exploit vectors + when run by + cron(8), by root, or by a user other then the one + owning the binary. In addition, + uustat(1) is now run + via /etc/periodic/daily/410.status-uucp as + uucp, not root. In FreeBSD -CURRENT, UUCP has since been moved to the Ports + Collection and no longer a part of the base system. + [MERGED]

+ +

A security hole in OpenSSH, + which could allow users to execute code with arbitrary + privileges if UseLogin yes was + set, has been closed. Note that the default value of this + setting is UseLogin no. (See + security advisory FreeBSD-SA-01:63.) [MERGED]

+ +

The use of an insecure temporary directory by + pkg_add(1) could permit + a local attacker to modify the contents of binary + packages while they were being installed. This hole has + been closed. (See security advisory FreeBSD-SA-02:01.) + [MERGED]

+ +

A race condition in + pw(8), which could + expose the contents of /etc/master.passwd, has been eliminated. + (See security advisory FreeBSD-SA-02:02.) [MERGED]

+ +

A bug in + k5su(8) could have + allowed a process that had given up superuser privileges + to regain them. This bug has been fixed. (See security + advisory FreeBSD-SA-02:07.) [MERGED]

+ +

An ``off-by-one'' bug has been fixed in OpenSSH's multiplexing code. This bug + could have allowed an authenticated remote user to cause + + sshd(8) to execute + arbitrary code with superuser privileges, or allowed a + malicious SSH server to execute arbitrary code on the + client system with the privileges of the client user. + (See security advisory FreeBSD-SA-02:13.) [MERGED]

+ +

A programming error in zlib + could result in attempts to free memory multiple times. + The + malloc(3)/ + free(3) routines used + in FreeBSD are not vulnerable to this error, but + applications receiving specially-crafted blocks of + invalid compressed data could be made to function + incorrectly or abort. This zlib bug has been fixed. For a + workaround and solutions, see security advisory FreeBSD-SA-02:18. [MERGED]

+ +

Bugs in the TCP SYN cache (``syncache'') and SYN + cookie (``syncookie'') implementations, which could cause + legitimate TCP/IP traffic to crash a machine, have been + fixed. For a workaround and patches, see security + advisory FreeBSD-SA-02:20. [MERGED]

+ +

A routing table memory leak, which could allow a + remote attacker to exhaust the memory of a target + machine, has been fixed. A workaround and patches can be + found in security advisory FreeBSD-SA-02:21. [MERGED]

+ +

A bug with memory-mapped I/O, which could cause a + system crash, has been fixed. For more information about + a solution, see security advisory FreeBSD-SA-02:22. [MERGED]

+ +

A security hole, in which SUID programs could be made + to read from or write to inappropriate files through + manipulation of their standard I/O file descriptors, has + been fixed. Information regarding a solution can be found + in security advisory FreeBSD-SA-02:23. [MERGED]

+ +

Some unexpected behavior could be allowed with + k5su(8) because it does + not require that an invoking user be a member of the wheel group when attempting to + become the superuser (this is the case with + su(1)). To avoid this + situation, + k5su(8) is now + installed non-SUID by default (effectively disabling it). + More information can be found in security advisory FreeBSD-SA-02:24. [MERGED]

+ +

Multiple vulnerabilities were found in the + bzip2(1) utility, which + could allow files to be overwritten without warning or + allow local users unintended access to files. These + problems have been corrected with a new import of bzip2. For more information, see + security advisory FreeBSD-SA-02:25. [MERGED]

+ +

A bug has been fixed in the implementation of the TCP + SYN cache (``syncache''), which could allow a remote + attacker to deny access to a service when accept filters + (see + accept_filter(9)) were + in use. This bug has been fixed; for more information, + see security advisory FreeBSD-SA-02:26. [MERGED]

+ +

Due to a bug in + rc(8)'s use of shell + globbing, users may be able to remove the contents of + arbitrary files if /tmp/.X11-unix does not exist and the + system can be made to reboot. This bug has been corrected + (see security advisory FreeBSD-SA-02:27). [MERGED]

+ +

A buffer overflow in the resolver, which could be + exploited by a malicious domain name server or an + attacker forging DNS messages, has been fixed. See + security advisory FreeBSD-SA-02:28 for more details. + [MERGED]

+ +

A buffer overflow in + tcpdump(1), which could + be triggered by badly-formed NFS packets, has been fixed. + See security advisory FreeBSD-SA-02:29 for more details. + [MERGED]

+ +

+ ktrace(1) can no longer + trace the operation of formerly privileged processes; + this prevents the leakage of sensitive information that + the process could have obtained before abandoning its + privileges. For a discussion of this issue, see security + advisory FreeBSD-SA-02:30 for more details. + [MERGED]

+ +

A race condition in + pppd(8), which could be + used to change the permissions of an arbitrary file, has + been corrected. For more information, see security + advisory FreeBSD-SA-02:32. [MERGED]

+ +

Multiple buffer overflows in OpenSSL have been corrected, by way of + an upgrade to the base system version of OpenSSL. More details can be found in + security advisory FreeBSD-SA-02:33. [MERGED]

+ +

A heap buffer overflow in the XDR decoder has been + fixed. For more details, see security advisory FreeBSD-SA-02:34. [MERGED]

+ +

A bug that could allow local users to read and write + arbitrary blocks on an FFS filesystem has been corrected. + More details can be found in security advisory FreeBSD-SA-02:35. [MERGED]

+ +

A bug in the NFS server code, which could allow a + remote denial of service attack, has been fixed. Security + advisory FreeBSD-SA-02:36 has more details. + [MERGED]

+ +

A bug that could allow local users to panic a system + using the + kqueue(2) mechanism has + been fixed. More information is contained in security + advisory FreeBSD-SA-02:37. [MERGED]

+ +

Several bounds-checking bugs in system calls, which + could result in some system calls returning a large + portion of kernel memory, have been fixed. More + information can be found in security advisory FreeBSD-SA-02:38. [MERGED]

+ +

A bug that could allow applications using libkvm to leak sensitive file descriptors + has been corrected. (See security advisory FreeBSD-SA-02:39 for more details.) + [MERGED]

+ +

Buffer overflows in kadmind(8) and k5admin have been + corrected. More details can be found in security advisory + FreeBSD-SA-02:40. [MERGED]

+ +

Errors in + smrsh(8), which could + allow users to circumvent restrictions on what programs + can be executed, have been fixed. See FreeBSD-SA-02:41 for details. + [MERGED]

+ +

Buffer overflows in the DNS + resolver(3), which + could cause some applications to fail, have been + corrected. More details are in FreeBSD-SA-02:42. [MERGED]

+ +

Multiple vulnerabilities in BIND have been fixed, as described in + FreeBSD-SA-02:43. [MERGED]

+

+ +

+

+ +

2.3 Userland + Changes

+ +

Support for + a.out(5) format + executables in the compiler toolchain has been largely + removed.

+ +

+

+
Note: This is a work in progress. + Eventually, + a.out(5) support + will resurface in a series of ports/packages.
+

+

+
+
+ +

+ arp(8) now prints [fddi] or [atm] tags for addresses on interfaces of + those types.

+ +

The + asa(1) utility, to + interpret FORTRAN carriage-control characters, has been + added.

+ +

+ at(1) now supports the + -r command-line option to remove + jobs and the -t option to specify + times in POSIX time format.

+ +

The system + awk(1) now refers to BWK awk.

+ +

+ basename(1) now accept + -a and -s + flags, which allow it to perform the + basename(3) function on + multiple files.

+ +

+ biff(1) now accepts a + b argument to enable ``bell + notification'' of new mail (which does not disturb the + terminal contents as biff y + would). [MERGED]

+ +

+ biff(1) now uses the + first terminal associated with the standard input, + standard output or standard error file descriptor, in + that order. Thus, it is possible to use the redirection + facilities of a shell (biff n < + /dev/ttyp1) to toggle the notification for other + terminals.

+ +

+ burncd(8) now supports + Disk At Once (DAO) mode, selectable via the -d flag. [MERGED]

+ +

+ burncd(8) now has the + ability to write VCDs/SVCDs. [MERGED]

+ +

+ burncd(8) now accepts a + value of max for its -s option to set the drive's maximum write + speed.

+ +

+ bzgrep(1), + bzegrep(1), and + bzfgrep(1) have been + added to perform + grep(1)-type operations + on + bzip2(1)-compressed + files.

+ +

+ calendar(1) now takes a + -W option, which operates similar + to -A but without special + treatment at weekends, and a -Foption to change the notion of + ``Friday''.

+ +

+ catman(1) is now a C + program, instead of a Perl script.

+ +

+ cdcontrol(1) now + supports a speed command to set + the maximum speed to be used by the drive (the maximum + possible speed can be selected setting the speed to max).

+ +

A + check_utility_compat(3) + library function has been added to libc, to determine whether certain + FreeBSD base system utilities should behave in FreeBSD + 4-compatible mode or in a ``standard'' mode (default + standard). The configuration is done + malloc(3)-style, with + either an environment variable or a symbolic link.

+ +

+ chflags(1) has moved + from /usr/bin to /bin.

+ +

+ chmod(1) now supports a + -h for changing the mode of a + symbolic link.

+ +

+ chmod(1) now also, when + the mode is modified, prints the old and new modes if the + -v option is specified more than + once.

+ +

+ chown(8) no longer + takes . as a user/group + delimeter. This change was made to support usernames + containing a ..

+ +

Use of the CSMG_* macros no + longer require inclusion of <sys/param.h>

+ +

A compat4x distribution has + been added for compatibility with FreeBSD 4-STABLE.

+ +

+ cp(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A new + csplit(1) utility, + which splits files based on context, has been added.

+ +

+ ctags(1) now creates + tags for typedefs, structs, unions, and enums by default + (implying the -t option). The new + -T reverts to the old + behavior.

+ +

The + daemon(8) program, a + command-line interface to + daemon(3), has been + added. It detaches itself from its controlling terminal + and executes a program specified on the command line. + This allows the user to run an arbitrary program as if it + were written to be a daemon. [MERGED]

+ +

The + devd(8) utility, a + userland daemon that can run arbitrary commands when + devices come and go in the device tree, has been added. + This program is a generalization of some of the + functionality of + pccardd(8).

+ +

+

+
Note: + devd(8) is + work-in-progress.
+

+

+
+
+ +

+ devinfo(8), a simple + tool to print the device tree and resource usage by + devices, has been added.

+ +

diskpart(8) has been declared obsolete, and has been + removed.

+ +

+ dump(8) now supports a + new -S flag to allow it to just + print out the dump size estimates and exit. [MERGED]

+ +

+ expr(1) is now + compliant with POSIX.2-1992 (and thus also with + POSIX.1-2001). Some program depend on the old, historic + behavior and do not properly protect their arguments to + keep them from being misinterpreted as command-line + options. (the + devel/libtool port/package, + used by many GNU programs, is a notable example). The old + behavior can be requested by enabling compatibility mode + for + expr(1) as described in + + check_utility_compat(3).

+ +

+ fbtab(5) now accepts + glob matching patterns for target devices, not just + individual devices and directories.

+ +

+ fdisk(8) no longer + attempts to search for a device if none has been + specified on the command line, but instead tries to + figure out the default device name from the root + device.

+ +

+ fdread(1), a program to + read data from floppy disks, has been added. It is a + counterpart to + 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 + dd(1).

+ +

+ finger(1) now has + support for a .pubkey file. + [MERGED]

+ +

+ finger(1) now supports + a -g flag to restrict the + printing of GECOS information to the user's full name + only. [MERGED]

+ +

+ finger(1) now supports + the -4 and -6 flags to specify an address family for + remote queries. [MERGED]

+ +

+ fold(1) now supports a + -b flag to break at byte + positions and a -s flag to break + at word boundaries. [MERGED]

+ +

+ fsck(8) wrappers have + been imported; this feature provides infrastructure for + + fsck(8) to work on + different types of filesystems (analogous to + mount(8)).

+ +

The behavior of + fsck(8) when dealing + with various passes (a la /etc/fstab) has been modified to + accommodate multiple-disk filesystems.

+ +

+ fsck(8) now has support + for foreground (-F) and + background (-B) checks. + Traditionally, + fsck(8) is invoked + before the filesystems are mounted and all checks are + done to completion at that time. If background checking + is available, + fsck(8) is invoked + twice. It is first invoked at the traditional time, + before the filesystems are mounted, with the -F 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 -B 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 background_fsck option in + rc.conf(5).

+ +

+ fsck_ffs(8) now + supports background filesystem checks to mounted FFS + filesystems with the -B option + (softupdates must be enabled on these filesystems). The + -F flag now determines whether a + specified filesystem needs foreground checking.

+ +

+ ftpd(8) now supports + the -m option to permit guest + users to modify existing files if allowed by filesystem + permissions. In particular, this enables guest users to + resume uploads. [MERGED]

+ +

+ ftpd(8) now supports + the -M option to prevent guest + users from creating directories. [MERGED]

+ +

+ ftpd(8) now supports + -o and -O + options to disable the RETR + command; the former for everybody, and the latter only + for guest users. Coupled with -A + and appropriate file permissions, these can be used to + create a relatively safe anonymous FTP drop box for + others to upload to. [MERGED]

+ +

+ ftpd(8) now supports + the -W option to disable logging + FTP sessions to + wtmp(5). [MERGED]

+ +

The + getconf(1) utility has + been added. It prints the values of POSIX or X/Open path + or system configuration variables. [MERGED]

+ +

gifconfig(8) is obsolete and has been removed. Its + functionality is now handled by the tunnel and deletetunnel commands of + ifconfig(8).

+ +

+ gprof(1) now has a -K option to enable dynamic symbol + resolution from the currently-running kernel. With this + change, properly-compiled KLD modules are now able to be + profiled.

+ +

The ibcs(8), linux(8), osf1(8), and 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.

+ +

+ ifconfig(8) now has the + ability to set promiscuous mode on an interface, via the + new promisc flag. [MERGED]

+ +

+ ifconfig(8) now + supports a monitor interface + flag, which blocks transmission of packets on that + interface. This feature is useful for monitoring network + traffic without interacting with the network in + question.

+ +

By default, + inetd(8) is no longer + run by + rc(8) at boot-time, + although + sysinstall(8) gives the + option of enabling it during binary installations. + inetd(8) can also be + enabled by adding the following line to /etc/rc.conf:

+

+    inetd_enable="YES"
+

+ +

+ inetd(8) now has the + capability for limiting the maximum number of + simultaneous invocations of each service from a single IP + address. [MERGED]

+ +

+ ipfw(8) filter rules + can now match on the value of the IPv4 precedence + field.

+ +

+ kbdmap(1) and + vidfont(1) have been + converted from Perl to C.

+ +

+ kenv(1) now has the + ability to set or delete kernel environment + variables.

+ +

The kget(8) utility has been removed (it was only + useful for UserConfig, which is not present in FreeBSD + 5.0-DP2).

+ +

+ killall(1) no longer + tries to kill zombie processes unless the -z flag is specified.

+ +

+ ktrdump(8), a utility + to dump the ktr trace buffer from userland, has been + added.

+ +

+ ldd(1) now supports a + -a flag to list all the objects + that are needed by each loaded object.

+ +

libc is now thread-safe by + default; libc_r contains only + thread functions.

+ +

libstand now has support for + overwriting the contents of a file on a UFS filesystem + (it cannot expand or truncate files because the + filesystem may be dirty or inconsistent).

+ +

libgmp has been superceded + by libmp.

+ +

The functions from libposix1e have been integrated into libc.

+ +

+ lock(1) now accepts a + -v to disable switching VTYs + while the current terminal is locked. This permits + locking the entire console from a single terminal. + [MERGED]

+ +

+ lpc(8) has been + improved; lpc clean is now + somewhat safer, and a new lpc + tclean command has been added to check to see what + files would be removed by lpc + clean. lpc topq has been + reimplemented, and now allows for a much more flexible + specification of which jobs should be moved (such as a + range of job numbers, or a hostname). An lpc bottomq command has been added to move + jobs to the bottom of a print queue, and a new lpc setstatus command can be used to set a + printer's status message. [MERGED]

+ +

The + ls(1) program now + supports a -m flag to list files + across a page, a -p flag to force + printing of a / after + directories, and a -x flag to + sort filenames across a page. [MERGED]

+ +

+ makewhatis(1) is now a + C program, instead of a Perl script.

+ +

+ man(1) is no longer + installed SUID man, in order to + reduce vulnerabilities associated with generating + ``catpages'' (preformatted manual pages cached for + repeated viewing). As a result, + man(1) can no longer + create system catpages on a regular user's behalf. It is + still able to do so if the user has write permissions to + the directory holding catpages (e.g. a user's own + manpages) or if the running user is root.

+ +

The + mdmfs(8) command has + been added; it is a wrapper around + mdconfig(8), + disklabel(8), + newfs(8), and + mount(8) that mimics + the command line option set of the deprecated + mount_mfs(8).

+ +

+ mesg(1) now conforms to + SUSv3. Among other things, it now uses the first terminal + associated with the standard input, standard output or + standard error file descriptor, in that order. Thus, it + is possible to use the redirection facilities of a shell + (mesg n < /dev/ttyp1) to + control write access for other terminals.

+ +

+ mountd(8) and + nfsd(8) have moved from + /sbin to /usr/sbin.

+ +

+ mv(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A number of archaic features of + newfs(8) have been + removed; these implement tuning features that are + essentially useless on modern hard disks. These features + were controlled by the -O, -d, -k, -l, -n, -p, -r, -t, and -x + flags.

+ +

+ newfs(8) now supports a + -O flag to select the creation of + UFS1 or UFS2 filesystems.

+ +

The + newgrp(1) utility to + change to a new group has been added.

+ +

+ newsyslog(8) now + compresses log files using + bzip2(1) by default. + (The former behavior of using + gzip(1) can be + specified in /etc/newsyslog.conf.)

+ +

The + nextboot(8) utility has + been added to specify an alternate kernel and/or boot + flags to be used the next time the machine is booted. A + previous incarnation of this feature first appeared in + FreeBSD 2.2.

+ +

NFS now works over + IPv6.

+ +

+ nice(1) now uses the + -n option to specify the + ``niceness'' of the utility being run. [MERGED]

+ +

nsswitch support has been + merged from NetBSD. By creating an + nsswitch.conf(5) file, + FreeBSD can be configured so that various databases such + as + passwd(5) and + group(5) can be looked + up using flat files, NIS, or Hesiod. If /etc/nsswitch.conf does not exist, it + will be automatically generated from an existing /etc/hosts.conf at system startup + time. The /etc/hosts.conf file + may be used by old executables; it will be automatically + generated from an existing /etc/nsswitch.conf during system startup + if it exists.

+ +

+ od(1) now supports the + -A option to specify the input + address base, the -N option to + specify the number of bytes to dump, the -j option to specify the number of bytes to + skip, the -s option to output + signed decimal shorts, and the -t + option to specify output type. [MERGED]

+ +

PAM support has been added + for account management and sessions.

+ +

PAM configuration is now + specified by files in /etc/pam.d/, rather than a single /etc/pam.conf file. /etc/pam.d/README has more details.

+ +

A + pam_echo(8) echo + service module has been added.

+ +

A + pam_exec(8) program + execution service module has been added.

+ +

A + pam_ftp(8) module has + been added to allow authentication of anonymous FTP + users.

+ +

A + pam_ftpusers(8) module + has been added to perform checks against the + ftpusers(5) file.

+ +

A + pam_ksu(8) module has + been added to do Kerberos 5 authentication and $HOME/.k5login authorization for + su(1).

+ +

A + pam_lastlog(8) module + has been added to record sessions in the + utmp(5), + wtmp(5), and + lastlog(5) + databases.

+ +

A + pam_login_access(8) + module has been added, to allow checking against /etc/login.access.

+ +

The + pam_nologin(8) module, + which can disallow logins using + nologin(5), has been + added.

+ +

The + pam_opie(8) and + pam_opieaccess(8) + modules have been added to control authentication via + opie(4). [MERGED]

+ +

A + pam_passwdqc(8) module + has been added, to check the quality of passwords + submitted during password changes.

+ +

A + pam_rhosts(8) module + has been added to support + rhosts(5) + authentication.

+ +

The + pam_rootok(8) module, + which can be used to authenticate only the superuser, has + been added.

+ +

A + pam_securetty(8) module + has been added to check the ``security'' of a TTY, as + listed in + ttys(5).

+ +

A + pam_self(8) module, + which allows self-authentication of a user, has been + added.

+ +

A + pam_wheel(8) module has + been added to permit authentication to members of a + group, which defaults to wheel.

+ +

The + pathchk(1) utility, + which checks pathnames for validity or portability + between POSIX systems, has been added. [MERGED]

+ +

+ ping(8) now supports a + -o flag to exit after receiving a + reply.

+ +

prefix(8) is obsolete and has been removed. Its + functionality is provided by the eui64 command to + ifconfig(8).

+ +

The + pselect(3) library + function (introduced by POSIX.1 as a slightly stronger + version of + select(2)) has been + added.

+ +

+ pwd(1) now supports the + -L flag to print the logical + current working directory. [MERGED]

+ +

+ quota(1) now takes a + -l flag to suppress quote checks + on NFS filesystems.

+ +

The pseudo-random number generator implemented by + rand(3) has been + improved to provide less biased results.

+ +

+ rcmd(3) now supports + the use of the RSH environment + variable to specify a program to use other than + rsh(1) for remote + execution. As a result, programs such as + dump(8), can use + ssh(1) for remote + transport.

+ +

+ rdist(1) has been + retired from the base system, but is still available from + FreeBSD Ports Collection as + net/44bsd-rdist.

+ +

The + renice(8) command + implements a -n option, which + specifies an increment to be applied to the priority of a + process. [MERGED]

+ +

+ rpcbind(8) has replaced + + portmap(8).

+ +

+ rpcgen(1) now uses /usr/bin/cpp (as on NetBSD), not + /usr/libexec/cpp.

+ +

+ rpc.lockd(8) has been + imported from NetBSD. This daemon provides support for + servicing client NFS locks.

+ +

+ rtld(1) will now print + the names of all objects that cause each object to be + loaded, if the LD_TRACE_LOADED_OBJECTS_ALL environment + variable is defined.

+ +

+ sed(1) now takes a -i option to enable in-place editing + of files. [MERGED]

+ +

The + setfacl(1) and + getfacl(1) commands + have been added to manage filesystem Access Control + Lists.

+ +

+ sh(1) no longer + implements printf as a built-in + command because it was considered less valuable compared + to the other built-in commands (this functionality is, of + course, still available through the + printf(1) + executable).

+ +

+ sh(1) now supports a + -C option to prevent existing + regular files from being overwritten by output + redirection, and a -u to give an + error if an unset variable is expanded. [MERGED]

+ +

The + sh(1) built-in cd command now supports -L and -P flags to + invoke logical or physical modes of operation, + respectively. Logical mode is the default, but the + default can be changed with the physical + sh(1) option. + [MERGED]

+ +

The + sh(1) built-in jobs command now supports a -s flag to output PIDs only and a -l flag to add PIDs to the output. + [MERGED]

+ +

+ sh(1) now supports a + bind built-in command, which + allows the key bindings for the shell's line editor to be + changed.

+ +

The + sh(1) built-in export and readonly commands now support a -p flag to print their output in + ``portable'' format. [MERGED]

+ +

+ sh(1) no longer accepts + invalid constructs as command & && command, && command, or || command. [MERGED]

+ +

+ spkrtest(8) is now a + sh(1) script, rather + than a Perl script.

+ +

+ split(1) now supports a + -a option to specify the number + of letters to use for the suffix of split files. + [MERGED]

+ +

In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, struct selinfo and related functions + have been moved to <sys/selinfo.h>.

+ +

+ su(1) now uses PAM for authentication.

+ +

+ sysctl(8) now accepts a + -d flag to print the descriptions + of variables.

+ +

The default root partition in + sysinstall(8) is now + 100MB on the i386 and pc98, 120MB on the Alpha.

+ +

+ sysinstall(8) now lives + in /usr/sbin, which simplifies + the installation process. The + sysinstall(8) manpage + is also installed in a more consistent fashion now.

+ +

+ sysinstall(8) no longer + mounts the + procfs(5) filesystem by + default on new installs.

+ +

+ tabs(1), a utility to + set terminal tab stops, has been added.

+ +

The + termcap(5) database now + uses the xterm terminal type + from XFree86. As a result, + xterm(1) now supports + color by default and the common workaround of setting TERM to xterm-color is no longer necessary. Use of + the xterm-color terminal type + may result in (benign) warnings from applications.

+ +

+ tftpd(8) now supports + RFC 2349 (TFTP Timeout Interval and Transfer Size + Options); this feature is required by some firmware like + EFI boot managers (at least on HP i2000 Itanium servers) + in order to boot an image using TFTP.

+ +

A version of Transport Independent RPC (TI-RPC) has been imported.

+ +

+ tip(1) has been updated + from OpenBSD, and has the + ability to act as a + cu(1) substitute.

+ +

+ top(1) will now use the + full width of its tty.

+ +

+ touch(1) now takes a + -h option to operate on a + symbolic link, rather than what the link points to.

+ +

+ tr(1) now has basic + support for equivalence classes for locales that support + them. [MERGED]

+ +

+ tr(1) now supports a + -C flag to complement the set of + characters specified by the first string argument.

+ +

+ tunefs(8) now supports + the -a and -l flags to enable and disable the FS_ACLS and FS_MULTILABEL administrative flags on UFS + file system.

+ +

A + ugidfw(8) utility has + been added to manage the rulesets provided by the mac_bsdextended Mandatory Access + Control policy, similar to + ipfw(8).

+ +

UUCP has been removed from + the base system. It can be found in the Ports Collection, + in + net/freebsd-uucp.

+ +

+ unexpand(1) now + supports a -t to specify tabstops + analogous to + expand(1). [MERGED]

+ +

+ usbdevs(8) now supports + a -d flag to show the device + driver associated with each device.

+ +

The base64 capabilities of + uuencode(1) and + uudecode(1) can now be + automatically enabled by invoking these utilities as + b64encode(1) and + b64decode(1) + respectively. [MERGED]

+ +

Functions to implement and manipulate OSF/DCE + 1.1-compliant UUIDs have been added to libc. More information can be found in + uuid(3).

+ +

The + uuidgen(1) utility has + been added. It uses the new + uuidgen(2) system call + to generate one or more Universally Unique Identifiers + compatible with OSF/DCE 1.1 version 1 UUIDs.

+ +

+ vidcontrol(1) now + accepts a -S to allow the user to + disable VTY switching. [MERGED]

+ +

The default stripe size in + vinum(8) has been + changed from 256KB to 279KB, to spread out superblocks + more evenly between stripes.

+ +

+ wc(1) now supports a + -m flag to count characters, + rather than bytes.

+ +

+ whereis(1), formerly a + Perl script, has been rewritten in C. It now supports a + -x flag to suppress the run of + locate(1), and a -q flag suppresses the leading name + of the query.

+ +

+ whereis(1) now supports + a -a flag to report all matches + instead of only the first of each requested type.

+ +

+ which(1) is now a C + program, rather than a Perl script.

+ +

+ who(1) now has a number + of new options: -H shows column + headings; -T shows + mesg(1) state; -m is an equivalent to am i; -u shows idle + time; -q to list names in + columns. [MERGED]

+ +

+ wicontrol(8) now + supports a -l to list the + stations associated in hostap + mode and a -L to list available + access points.

+ +

+ xargs(1) now supports a + -I replstr option that allows the + user to tell + xargs(1) to insert the + data read from standard input at specific points in the + command line arguments rather than at the end. (A + FreeBSD-specific -J option is + similar.) [MERGED]

+ +

+ xargs(1) now supports a + -L option to force its utility + argument to be called after some number of lines. + [MERGED]

+ +

Various routines in the C library now have support for + ``wide'' characters. Among these are character class + functions such as + wctype(3), wide + character I/O functions such as + getwc(3), formatted I/O + functions such as + wprintf(3) and + wscanf(3). Conversion + functions to + multibyte(3) characters + are also supported.

+ +

A number of utilities and libraries were enhanced to + improve their conformance with the Single UNIX + Specification (SUSv3) and IEEE Std 1003.1-2001 + (``POSIX.1''). Specific features added have been listed + in the release notes for each utility. The standards + conformance of each utility or library function is + generally listed in its manual page.

+ +

A number of games have been removed from the base + system. These include: adventure(6), arithmetic(6), + atc(6), backgammon(6), battlestar(6), bs(6), canfield(6), + cribbage(6), fish(6), hack(6), hangman(6), larn(6), + mille(6), phantasia(6), piano(6), pig(6), quiz(6), + rain(6), robots(6), rogue(6), sail(6), snake(6), trek(6), + wargames(6), worm(6), worms(6), wump(6). dm(8), which was + used to control access to games, is no longer necessary, + and has also been removed. The ``utility-like'' games, as + well as + fortune(6), remain.

+ +

+

+
Note: The affected programs will reappear + as a port in the Ports Collection. This note will + contain a pointer to that port, once it has been + committed.
+

+

+
+
+ +

+

+ +

2.3.1 Contributed + Software

+ +

am-utils has been updated + to 6.0.7.

+ +

A 10 February 2002 snapshot of awk from Bell Labs (variously known + as ``BWK awk'' or ``The One True AWK'') has been + imported. It is available as awk or nawk.

+ +

BIND has been updated to + 8.3.3. [MERGED]

+ +

Binutils has been updated + to a pre-release snapshot of 2.13.1 from 11 October + 2002.

+ +

file has been updated to + 3.39.

+ +

gcc has been updated to a + pre-release snapshot of gcc + 3.2.1, from 9 October 2002.

+ +

+

+
Warning: The C++ ABI from gcc 3.2.X is not compatible with + previous versions.
+

+

+
+
+ +

gdb has been updated to + version 5.2.1.

+ +

gperf has been updated to + 2.7.2.

+ +

groff and its related + utilities have been updated to FSF version 1.18.1.

+ +

Heimdal Kerberos has been + updated to a pre-0.5 snapshot from 16 September + 2002.

+ +

The ISC DHCP client has + been updated to 3.0.1RC9.

+ +

The + more(1) command has + been replaced by + less(1), although it + can still be run as more. + [MERGED] Version 371 of less + has been imported.

+ +

An XML processing library, named libbsdxml, has been added for the + benefit of XML-using utilities in the base system. It + is based almost entirely on an import of expat 1.95.5, but is installed under + a different name to avoid conflicts with any versions + of expat installed from the + Ports Collection.

+ +

libpcap has been updated + to 0.7.1. [MERGED]

+ +

libreadline has been + updated to 4.2.

+ +

libz has been updated to + 1.1.4.

+ +

lint has been updated to + snapshot of NetBSD + lint(1) as of 19 July + 2002.

+ +

lukemftp 1.6 beta 2 (the + FTP client from NetBSD) has replaced the FreeBSD + ftp(1) program. Among + its new features are more automation methods, better + standards compliance, transfer rate throttling, and a + customizable command-line prompt. Some environment + variables and command-line arguments have changed.

+ +

The FTP daemon from NetBSD, otherwise known as lukemftpd 1.2 beta 1, has been + imported and is available as + lukemftpd(8). + [MERGED]

+ +

+ m4(1) has been + imported from OpenBSD, as of 26 April 2002. + [MERGED]

+ +

ncurses has been updated + to 5.2-20020615.

+ +

The NTP suite of programs + has been updated to 4.1.1b.

+ +

OpenPAM (``Citronella'' + release) has been imported, replacing Linux-PAM.

+ +

The OPIE + one-time-password suite has been updated to 2.4. It has + completely replaced the functionality of S/Key. [MERGED]

+ +

Perl has been removed + from the FreeBSD base system. It can still be installed + from the FreeBSD Ports Collection or as a binary + package; moving it out of the base system will make + future upgrades and maintenence easier. To reduce the + dependence of the base system on Perl, many utilities + have been rewritten as shell scripts or C programs + (specific notes are made for each affected utility). + /usr/bin/perl is now a + ``wrapper'' program, so that programs expecting to find + a Perl interpreter there will be able to function + correctly.

+ +

+

+
Warning: The Perl removal and package + integration work is ongoing.
+

+

+
+
+ +

GNU ptx has been removed + from the base system. It is not used anywhere in the + base system, and has not been recently updated or + maintained. Users requiring its functionality can + install this utility as a part of the + textproc/textutils + port.

+ +

The rc.d framework from + NetBSD has been imported. It breaks down the system + startup functionality into a number of small, + ``task-oriented'' scripts in /etc/rc.d, with dynamic-determined + ordering of startup scripts performed at boot-time.

+ +

Version 1.4.5 of the smbfs userland utilities has been + imported. [MERGED]

+ +

GNU sort has been updated + to the version from GNU + textutils 2.0.21.

+ +

+ stat(1) from NetBSD, as of 5 June 2002 has, + been imported.

+ +

GNU tar has been updated + to 1.13.25. [MERGED]

+ +

tcpdump has been updated + to 3.7.1. [MERGED]

+ +

The + csh(1) shell has been + replaced by + tcsh(1), although it + can still be run as csh. tcsh has been updated to + version 6.12. [MERGED]

+ +

The contributed version of tcp_wrappers now includes the + tcpd(8) helper + daemon. While not strictly necessary in a standard + FreeBSD installation (because + inetd(8) already + incorporates this functionality), this may be useful + for + inetd(8) replacements + such as xinetd. [MERGED]

+ +

texinfo has been updated + to 4.2. [MERGED]

+ +

top has been updated to + version 3.5b12. [MERGED]

+ +

traceroute has been + updated to LBL version 1.4a12.

+ +

The timezone database has been updated to the tzdata2002d release. [MERGED]

+ +

+

+ +

2.3.1.1 + CVS

+ +

cvs has been updated to + 1.11.2. [MERGED]

+

+ +

+

+ +

2.3.1.2 + CVSup

+

+ +

+

+ +

2.3.1.3 + KAME

+

+ +

+

+ +

2.3.1.4 + OpenSSH

+ +

OpenSSH has been + updated to version 3.1. [MERGED] Among the + changes:

+ +

+
The *2 files are + obsolete (for example, ~/.ssh/known_hosts can hold the + contents of ~/.ssh/known_hosts2).
+
+
+ ssh-keygen(1) + can import and export keys using the SECSH Public + Key File Format, for key exchange with several + commercial SSH implementations.
+
+
+ ssh-add(1) now + adds all three default keys.
+
+
+ ssh-keygen(1) + no longer defaults to a specific key type; one + must be specified with the -t option.
+

+
+
+ +

OpenSSH has been + updated to 3.4p1. [MERGED] The main changes are:

+ +

+
A ``privilege separation'' feature, which uses + unprivileged processes to contain and restrict + the effects of future compromises or programming + errors.
+
+
Several bugfixes, including closure of a + security hole that could lead to an integer + overflow and undesired privilege escalation.
+

+
+
+

+ +

+

+ +

2.3.1.5 + OpenSSL

+ +

OpenSSL has been + updated to 0.9.6g. [MERGED]

+

+ +

+

+ +

2.3.1.6 + sendmail

+ +

sendmail has been + updated from version 8.9.3 to version 8.12.6. + Important changes include: + sendmail(8) is no + longer installed as a set-user-ID root binary (now set-group-ID smmsp); new default file + locations (see /usr/src/contrib/sendmail/cf/README); + + newaliases(1) is + limited to root and trusted + users; STARTTLS encryption; and the MSA port (587) is + turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES + for more information. [MERGED]

+ +

By default, + rc(8) no longer + enables sendmail for + inbound SMTP connections. Note that + sysinstall(8) may + override this default for a binary installation, + based on what security profile is selected. This + functionality can also be manually enabled by adding + the following line to /etc/rc.conf:

+

+    sendmail_enable="YES"
+

+ +

The permissions for sendmail alias and map databases + built via /etc/mail/Makefile now default to + mode 0640 to protect against a file locking local + denial of service. It can be changed by setting the + new SENDMAIL_MAP_PERMS make.conf option. [MERGED]

+ +

The permissions for the sendmail statistics file, /var/log/sendmail.st, have been + changed from mode 0644 to mode 0640 to protect + against a file locking local denial of service. + [MERGED]

+

+ +

+

+ +

2.3.2 + Ports/Packages Collection Infrastructure

+ +

BSDPAN, a collection of + modules that provides tighter integration of Perl into the FreeBSD Ports + Collection, has been added.

+ +

For some time, FreeBSD 5.0-CURRENT (as well as some + 4.X releases) included a pkg_update(1) utility to + update installed packages, as well as their + dependencies. This utility has been removed; a superset + of its functionality can be found in the + sysutils/portupgrade + port.

+ +

+ pkg_version(1), + formerly a Perl script, has been rewritten in C.

+ +

The Ports Collection infrastructure now uses XFree86 4.2.1 as the default + version of the X Window System for the purposes of + satisfying dependencies. To return to using XFree86 3.3.6, add the following line + to /etc/make.conf: + [MERGED]

+

+    XFREE86_VERSION=3
+

+ +

The libraries installed by the + emulators/linux_base port + (required for Linux emulation) have been updated; they + now correspond to those included with Red Hat Linux 7.1. [MERGED]

+ +

By default, packages generated by the Ports + Collection (as well as the packages on the FTP sites) + are now compressed using + bzip2(1), rather than + + gzip(1). (Thus, they + now have a .tbz extension, + rather than a .tgz + extension.) The package tools have been updated to + handle the new format.

+

+ +

+

+ +

2.4 Release + Engineering and Integration

+ +

The bin distribution has + been renamed base, in order to + make creation of combined install/recovery disks + easier.

+ +

ISO images and CDROMs now use the cdboot boot loader by default. This + eliminates the need for an emulated floppy disk image on + a bootable CDROM and allows for a full GENERIC kernel to be used for CDROM + installations, at the expense of compatability with some + old BIOSs.

+ +

It is now possible to make releases of FreeBSD + 5-CURRENT on a FreeBSD 4-STABLE host and vice versa. + Cross-architecture (building a release for a target + architecture on a host of a different architecture) + releases are also possible. See + release(7) for details. + [MERGED]

+ +

A third drivers.flp floppy + has been added to floppy releases. It holds loadable + modules containing drivers that do not fit in the kernel + on the kern.flp disk or in the + mfsroot.flp image.

+

+ +

+

+ +

2.5 + Documentation

+ +

A number of formerly-encumbered documents from the 4.4 + BSD Programmer's Supplementary Documents have been + restored to /usr/share/doc/psd. + These include:

+ +

+
The + UNIX Time-Sharing System (01.cacm)
+
+
UNIX + Implementation (02.implement)
+
+
The + UNIX I/O System (03.iosys)
+
+
UNIX + Programming -- Second Edition (04.uprog)
+
+
The C + Programming Language -- Reference Manual + (06.Clang)
+
+
Yacc: + Yet Another Compiler-Compiler (15.yacc)
+
+
Lex -- + A Lexical Analyzer Generator (16.lex)
+
+
The M4 + Macro Processor (17.m4)
+

+ +

Several formerly-encumbered documents from the 4.4 BSD + User's Supplementary Documents have been restored to /usr/share/doc/usd. They + include:

+ +

+
NROFF/TROFF User's Manual (21.troff)
+
+
A TROFF + Tutorial (22.trofftut)
+

+

+ +

+

+ +

3 Upgrading from + previous releases of FreeBSD

+ +

Users with existing FreeBSD systems are highly encouraged + to read the ``Early Adopter's Guide to FreeBSD 5.0''. This + document generally has the filename EARLY.TXT on the distribution media, or any + other place that the release notes can be found. It offers + some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.X versus + running FreeBSD 4.X.

+ +

+

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

+

FreeBSD/ia64 5.0-DP2 + Release Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.452 2002/11/14 17:59:11 bmah Exp $
+

+ +

+

+ + +

The release notes for FreeBSD 5.0-DP2 contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. Both + changes for kernel and userland are listed, as well as + applicable security advisories that were issued since + the last release. Some brief remarks on upgrading are + also presented.

+

+ +

+

Table of Contents

+

+

2.1.1 Processor/Motherboard + Support
2.1.2 Bootloader + Changes
2.1.3 Network Interface + Support
2.1.4 Network + Protocols
2.1.5 Disks and + Storage
2.1.6 Filesystems
2.1.7 PCCARD + Support
2.1.8 Multimedia + Support
2.1.9 Contributed + Software

+

+

2.3.1 Contributed + Software
2.3.2 Ports/Packages + Collection Infrastructure

+

3 Upgrading from previous releases + of FreeBSD

+

+

+ +

+

+ +

1 Introduction

+ +

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

+ +

The snapshot distribution to which these release notes + apply represents a point along the 5-CURRENT development + branch between 4.0-RELEASE and the future 5.0-RELEASE. Some + pre-built, binary snapshot distributions along this branch + can be found at http://snapshots.jp.FreeBSD.org/.

+

+ +

+

+ +

2 What's New

+ +

This section describes many of the user-visible new or + changed features in FreeBSD since 4.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 4.6-RELEASE). The later items are + marked as [MERGED].

+ +

Typical release note items document new drivers or + hardware support, new commands or options, major bugfixes, + or contributed software upgrades. Applicable security + advisories issued after 4.0-RELEASE are also listed.

+ +

Many additional changes were made to FreeBSD 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.

+ +

+

+ +

2.1 Kernel + Changes

+ +

+ acct(2) has been + changed to open the accounting file in append mode, so + that + accton(8) can be used + to enable accounting to an append-only file. [MERGED]

+ +

A new in-kernel cryptographic framework (see + crypto(4) and + crypto(9)) has been + imported from OpenBSD. It provides a consistent interface + to hardware and software implementations of cryptographic + algorithms for use by the kernel and access to + cryptographic hardware for user-mode applications. + Hardware device drivers are provided to support + hifn-based cards ( + hifn(4)) and + Broadcom-based cards ( + ubsec(4)).

+ +

A new + ddb(4) command show pcpu lists some of the per-CPU + data.

+ +

A devctl device has been + added to allow userland programs to learn when devices + come and go in the device tree (different from the XXX). + This facility is primariliy used by the + devd(8) utility.

+ +

+ devfs(5), which allows + entries in the /dev directory + to be built automatically and supports more flexible + attachment of devices, has been largely reworked. + devfs(5) is now enabled + by default and can be disabled by the NODEVFS kernel option.

+ +

The + devfs(5) ``rule'' + subsystem has been introduced. DEVFS rules permit the + administrator to define certain properties of new device + nodes before they become visible to the userland. Both + static (e.g. /dev/speaker) and + dynamic (e.g. /dev/bpf*, some + removable devices) nodes are supported. Each + devfs(5) mount may have + a different ruleset assigned to it, permitting different + policies to be implemented for things like jails. Rules + and rulesets are manipulated with the + devfs(8) utility.

+ +

The dgm driver has been removed in favor of the digi + driver.

+ +

A new digi driver has been added to support PCI + Xr-based and ISA Xem Digiboard cards. A new + digictl(8) program is + (mainly) used to re-initialize cards that have external + port modules attached such as the PC/Xem.

+ +

An + eaccess(2) system call + has been added, similar to + access(2) except that + the former uses effective credentials rather than real + credentials.

+ +

Each + jail(2) environment can + now run under its own securelevel.

+ +

The tunable sysctl variables for + jail(2) have moved from + jail.* to the security.* hierarchy. Other + security-related sysctl variables have moved from kern.security.* to security.*.

+ +

The kernel environment is now dynamic, and can be + changed via the new + kenv(2) system + call.

+ +

The labpc(4) driver has been removed due to + ``bitrot''.

+ +

The loader and kernel linker now look for files named + linker.hints in each directory + with KLDs for a module name and version to KLD filename + mapping. The new + kldxref(8) utility is + used to generate these files.

+ +

+ lomac(4), a + Low-Watermark Mandatory Access Control security facility, + has been added as a kernel module. It provides a drop-in + security mechanism in addition to the traditional + UID-based security facilities, requiring no additional + configuration from the administrator. Work on this + feature was sponsored by DARPA and NAI Labs.

+ +

FreeBSD now supports an extensible Mandatory Access + Control framework, the TrustedBSD MAC Framework. It + permits loadable kernel modules to link to the kernel at + compile-time, boot-time, or run-time, and augment the + system security policy. The framework permits modules to + express interest in a variety of events, and also + provides common security policy services such as label + storage. A variety of sample policy modules are shipped + in this release, including implementations of fixed and + floating label Biba integrity models, Multi-Level + Security (MLS) with compartments, and a number of + augmented UNIX security models including a file system + firewall. This feature will permit easier development and + maintenance of local and vendor security extensions. The + extensibility service is enabled by adding options MAC to the kernel + configuration.

+ +

+

+
Note: The MAC framework is considered an + experimental feature in this release, and is not + enabled by default
+

+

+
+
+ +

Machine Check Architecture (MCA) records are now + collected at boot time and made available through the hw.mca.* sysctl variables.

+ +

+ mutex(9) profiling code + has been added, enabled by the MUTEX_PROFILING kernel configuration + option. It enables the debug.mutex.prof.* hierarchy of sysctl + variables.

+ +

The P1003_1B kernel option is + no longer used and has been removed.

+ +

The + random(4) device has + been rewritten to use the Yarrow 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 + random(4) device is now + periodically saved to files in /var/db/entropy, as well as at shutdown + time. The semantics of /dev/random have changed; it never blocks + waiting for entropy bits but generates a stream of + pseudo-random data and now behaves exactly as /dev/urandom.

+ +

A new kernel option, options + REGRESSION, enables interfaces and functionality + intended for use during correctness and regression + testing.

+ +

RLIMIT_VMEM support has been + added. This feature defines a new resource limit that + covers a process's entire virtual memory space, including + + mmap(2) space. This + limit can be configured in + login.conf(5) via the + new vmemoryuse variable. + [MERGED]

+ +

A bug in the + sendfile(2) system + call, in which headers counted against the size of the + file to be sent, has been fixed. [MERGED]

+ +

The + syscons(4) driver now + supports keyboard-controlled pasting, by default bound to + Shift-Insert.

+ +

The uaudio driver, for USB audio devices, has been + added. [MERGED]

+ +

The + ucom(4) device driver + has been added, to support USB modems, serial devices, + and other programs that need to look like a tty. The + related + uplcom(4) and + uvscom(4) drivers + provide specific support for the Prolific PL-2303 serial + adapter and the SUNTAC Slipper U VS-10U, respectively. + [MERGED]

+ +

To increase security, the UCONSOLE kernel configuration option has + been removed.

+ +

The USER_LDT kernel option is + now activated by default.

+ +

The + uvisor(4) driver for + connecting Handspring Visors via USB has been added. + [MERGED]

+ +

A VESA S3 linear framebuffer driver has been + added.

+ +

The kernel crashdump infrastructure has been revised, + to support new platforms and in general clean up the + logic in the code. One implication of this change is that + the on-disk format for kernel dumps has changed, and is + now byte-order-agnostic.

+ +

Extremely large swap areas (>67 GB) no longer panic + the system.

+ +

Linker sets are now self-contained; gensetdefs(8) is + unnecessary and has been removed.

+ +

It is now possible to hardwire kernel environment + variables (such as tuneables) at compile-time using + config(8)'s ENV directive.

+ +

Idle zeroing of pages can be enabled with the vm.idlezero_enable sysctl + variable.

+ +

The FreeBSD kernel scheduler now supports + Kernel-Scheduled Entities (KSEs), which provides support + for multiple threads of execution per process similar to + Scheduler Activations. At this point, the kernel has most + of the changes needed to support threading. The kernel + scheduler can schedule multiple threads per process, but + only on a single CPU at a time. More information can be + found in + kse(2).

+ +

+

+
Note: KSE is a work in progress.
+

+

+
+
+ +

The kernel now has support for multiple low-level + console devices. The new + conscontrol(8) utility + helps to manage the different consoles.

+ +

The kernel memory allocator is now a slab memory + allocator, similar to that used in Solaris. This is a + SMP-safe memory allocator that has near-linear + performance as the number of CPUs increases. It also + allows for reduced memory fragmentation.

+ +

+

+ +

2.1.1 + Processor/Motherboard Support

+ +

SMP support has been largely reworked, incorporating + code from BSD/OS 5.0. One of the main features of SMPng + (``SMP Next Generation'') 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.

+

+ +

+

+ +

2.1.2 Bootloader + Changes

+ +

The kernel and modules have been moved to the + directory /boot/kernel, so + they can be easily manipulated together. The boot + loader has been updated to make this change as seamless + as possible.

+

+ +

+

+ +

2.1.3 Network + Interface Support

+ +

The + dc(4) driver now + supports NICs based on the Xircom 3201 and Conexant + LANfinity RS7112 chips.

+ +

The + stf(4) device is now + clonable.

+ +

The + tx(4) driver now + supports true multicast filtering.

+ +

Network devices now automatically appear as special + files in /dev/net. Interface + hardware ioctls (not protocol or routing) can be + performed on these devices. The SIOCGIFCONF ioctl may be performed on + the special /dev/network + node.

+ +

``Zero copy'' support has been added to the + networking stack. This feature can eliminate a copy of + network data between the kernel and userland, which is + one of the more significant bottlenecks in network + throughput. The send-side code should work with almost + any network adapter, while the receive-side code + requires a network adapter with an MTU of at least one + memory page size (for example, jumbo frames on Gigabit + Ethernet). For more information, see + zero_copy(9).

+

+ +

+

+ +

2.1.4 Network + Protocols

+ +

A FAST_IPSEC kernel option + now allows the IPsec implementation to use the kernel + crypo framework, along with its support for hardware + cryptographic acceleration.

+ +

+

+
Note: The FAST_IPSEC and IPSEC options are mutually + exclusive.
+

+

+ +

+

+
Note: The FAST_IPSEC option is, at the moment, + not compatible with IPv6 or the INET6 option.
+

+

+
+
+ +

A + gre(4) driver, which + can encapsulate IP packets using GRE (RFC 1701) or + minimal IP encapsulation for Mobile IP (RFC 2004), has + been added.

+ +

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.

+ +

IP multicast now works on VLAN devices. Several + other bugs in the VLAN code have also been fixed.

+ +

+ ipfw(4) has been + re-implemented (the new version is commonly referred to + as ``IPFW2''). It now uses variable-sized + representation of rules in the kernel, similar to + bpf(4) instructions. + Most of the externally-visible behavior (i.e. through + + ipfw(8)) should be + unchanged., although + ipfw(8) now supports + or connectives between match + fields. [MERGED]

+ +

A new + ng_device(4) netgraph + node type has been added, which creates a device entry + in /dev, to be used as the + entry point to a networking graph.

+ +

The + ng_gif(4) and + ng_gif_demux(4) + netgraph nodes, for operating on + gif(4) devices, have + been added.

+ +

The + ng_ip_input(4) + netgraph node, for queueing IP packets into the main IP + input processing code, has been added.

+ +

A new + ng_l2tp(4) netgraph + node type, which implements the encapsulation layer of + the L2TP protocol as described in RFC 2661, has been + added. [MERGED]

+ +

A new ng_split node type has been added for + splitting a bidirectional packet flow into two + unidirectional flows.

+ +

The ephemeral port range used for TCP and UDP has + been changed to 49152-65535 (the old default was + 1024-5000). This increases the number of concurrent + outgoing connections/streams.

+ +

The + tcp(4) protocol's + retransmission timer can now be manipulated with two + sysctl variables, net.inet.tcp.rexmit_min and net.inet.tcp.rexmit_slop. The default + has been reduced from one second to 200ms (similar to + the Linux default) in order to better handle hicups + over interactive connections and improve recovery over + lossy fast connections such as wireless links.

+ +

The + tcp(4) protocol now + has the ability to dynamically limit the send-side + window to maximize bandwidth and minimize round trip + times. The feature can be enabled via the net.inet.tcp.inflight_enable sysctl. + [MERGED]

+

+ +

+

+ +

2.1.5 Disks and + Storage

+ +

The + ata(4) driver (along + with + burncd(8)) now + supports writing to media in DVD+RW drives.

+ +

The + ata(4) driver now + supports accessing ATA devices as SCSI devices via the + CAM layer and drivers ( + cd(4), + da(4), + st(4), and + pass(4)). This + feature requires device + atapicam in the kernel configuration. More + information can be found in + atapicam(4). + [MERGED]

+ +

The + ata(4) driver now has + support for the Sil 0680 and VIA 8233/8235 controllers. + [MERGED]

+ +

The + cd(4) driver now + supports the same CDRIOCREADSPEED and CDRIOCWRITESPEED ioctls that the + acd(4) driver uses + for setting the speed of CDROM access.

+ +

The + fdc(4) floppy disk + has undergone a number of enhancements. Density + selection for common settings is now automatic; the + driver is also much more flexible in setting the + densities of various subdevices.

+ +

The + geom(4) disk I/O + request transformation framework has been added; this + extensible framework is designed to support a wide + variety of operations on I/O requests on their way from + the upper kernel to the device drivers.

+ +

+

+
Note: GEOM-enabled kernels no longer + support ``compatability slices''. This feature + (supported on the i386 and pc98 only) allowed a + user to refer to a disk partition without + specifying an MBR slice (e.g. /dev/ad0a); the kernel would + automatically find the first applicable FreeBSD + slice and use it. On GEOM kernels, only the full + partition names (e.g. /dev/ad0s1a) are allowed when + referring to partitions within MBR slices. This + change should affect very few users.
+

+

+
+
+ +

A GEOM Based Disk Encryption module has been added. + It provides denial of access to ``cold disks'', with + four different cryptographic barriers and up to four + changeable pass-phrases. Much more information can be + found in the + gbde(4) manual page. + The + gbde(8) userland + utility provides an operation and management interface + to this module. This feature is not enabled by default; + it requires options GEOM_BDE + to be added to a kernel configuration file.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

The + isp(4) driver is now + proactive about discovering Fibre Channel topology + changes.

+ +

The + isp(4) driver now + supports target mode for Qlogic SCSI cards, including + Ultra2 and Ultra3 and dual bus cards.

+ +

+ md(4), the memory + disk device, has had the functionality of + vn(4) incorporated + into it. + md(4) devices can now + be configured by + mdconfig(8). + vn(4) has been + removed. The Memory Filesystem (MFS) has also been + removed.

+ +

The RAIDframe disk driver has been imported from + NetBSD. This driver provides software-based RAID 0, 1, + 4, and 5 capabilities, as well as other functionality. + More information can be found in the + raid(4) driver manual + page. The + raidctl(8) utility is + used to configure and unconfigure disk arrays. This + feature is not enabled by default, and requires device raidframe to be configured + into a kernel.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

Some problems in + sa(4) error handling + have been fixed, including the ``tape drive spinning + indefinitely upon + mt(1) stat'' problem.

+ +

The SCSI_DELAY + configuration parameter can now be set at boot time and + runtime via the kern.cam.scsi_delay tunable/sysctl.

+ +

The trm driver has been added to support SCSI + adapters using the Tekram TRM-S1040 SCSI chipset.

+

+ +

+

+ +

2.1.6 + Filesystems

+ +

Support for named extended attributes was added to + the FreeBSD 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 /usr/src/sys/ufs/ufs/README.extattr for + details).

+ +

A filesystem snapshot capability has been added to + FFS. Details can be found in /usr/src/sys/ufs/ffs/README.snapshot.

+ +

Softupdates for FFS have received some bug fixes and + enhancements.

+ +

When running with softupdates, + statfs(2) and + df(1) will track the + number of blocks and files that are committed to being + freed.

+ +

+ kernfs(5) is obsolete + and has been retired.

+ +

Client-side NFS locks have been implemented.

+ +

The client-side and server-side of the NFS code in + the kernel used to be intertwined in various complex + ways. They have been split apart for ease of + maintenance and further development.

+ +

Support for filesystem 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 /usr/src/sys/ufs/ufs/README.acls.

+ +

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. Compatibility ``glue'' has + been added to + mount(8) so that msdos filesystem entries in + fstab(5) will work + without changes.

+ +

pseudofs, a pseudo-filesystem framework, has been + added. + linprocfs(5) and + procfs(5) have been + modified to use pseudofs.

+ +

Network filesystems (such as NFS and smbfs + filesystems) listed in /etc/fstab can now be properly mounted + during startup initialization; their mounts are + deferred until after the network is initialized.

+ +

Read-only support for the Universal Disk Format + (UDF) has been added. This format is used on + packet-written CD-RWs and most commercial DVD-Video + disks. The + mount_udf(8) command + can be used to mount these disks.

+ +

Basic support has been added for the UFS2 + filesystem. Among its features:

+ +

+
The inode has been expanded to 256 bytes to make + space for 64-bit block pointers.
+
+
A file-creation time field has been added.
+
+
A native extended attributes implementation has + been added, permitting total attribute size stored + on an inode to be up to twice the filesystem block + size. This storage is used for Access Control Lists + and MAC labels, but may also be used by other + system extensions and user applications.
+

+
+
+

+ +

+

+ +

2.1.7 PCCARD + Support

+ +

+

+ +

+

+ +

2.1.8 Multimedia + Support

+ +

A new API has been added for sound cards with + hardware volume control.

+

+ +

+

+ +

2.1.9 Contributed + Software

+ +

The Forth Inspired Command Language (FICL) used in the boot loader has + been updated to 3.02.

+ +

Support for Advanced Configuration and Power + Interface (ACPI), a multi-vendor standard for + configuration and power management, has been added. + This functionality has been provided by the Intel ACPI Component Architecture + project, as of the ACPI CA 20020815 snapshot. Some + backward compatability for applications using the older + APM standard has been provided.

+ +

+

+ +

2.1.9.1 + IPFilter

+ +

IPFilter has been + updated to 3.4.29. [MERGED]

+

+ +

+

+ +

2.1.9.3 + KAME

+

+ +

+

+ +

2.2 Security-Related + Changes

+ +

A bug in which malformed ELF executable images can + hang the system has been fixed (see security advisory + FreeBSD-SA-00:41). [MERGED]

+ +

A security hole in Linux emulation was fixed (see + security advisory FreeBSD-SA-00:42). [MERGED]

+ +

TCP now uses stronger randomness in choosing its + initial sequence numbers (see security advisory + FreeBSD-SA-00:52). [MERGED]

+ +

Several buffer overflows in + tcpdump(1) were + corrected (see security advisory FreeBSD-SA-00:61). + [MERGED]

+ +

A security hole in + top(1) was corrected + (see security advisory FreeBSD-SA-00:62). [MERGED]

+ +

A potential security hole caused by an + off-by-one-error in + gethostbyname(3) has + been fixed (see security advisory FreeBSD-SA-00:63). + [MERGED]

+ +

A potential buffer overflow in the + ncurses(3) library, + which could cause arbitrary code to be run from within + systat(1), has been + corrected (see security advisory FreeBSD-SA-00:68). + [MERGED]

+ +

A vulnerability in + telnetd(8) that could + cause it to consume large amounts of server resources has + been fixed (see security advisory FreeBSD-SA-00:69). + [MERGED]

+ +

The nat deny_incoming command + in + ppp(8) now works + correctly (see security advisory FreeBSD-SA-00:70). + [MERGED]

+ +

A vulnerability in + csh(1)/ + tcsh(1) temporary files + that could allow overwriting of arbitrary user-writable + files has been closed (see security advisory + FreeBSD-SA-00:76). [MERGED]

+ +

Several vulnerabilities in + procfs(5) were fixed + (see security advisory FreeBSD-SA-00:77). [MERGED]

+ +

A bug in OpenSSH in which a + server was unable to disable + ssh-agent(1) or X11Forwarding was fixed (see + security advisory FreeBSD-SA-01:01). [MERGED]

+ +

A bug in + ipfw(8) and + ip6fw(8) in which + inbound TCP segments could incorrectly be treated as + being part of an established + connection has been fixed (see security advisory + FreeBSD-SA-01:08). [MERGED]

+ +

A bug in + crontab(1) that could + allow users to read any file on the system in valid + crontab(5) syntax has + been fixed (see security advisory FreeBSD-SA-01:09). + [MERGED]

+ +

A vulnerability in + inetd(8) that could + allow read-access to the initial 16 bytes of wheel-accessible files has been fixed + (see security advisory FreeBSD-SA-01:11). [MERGED]

+ +

A bug in + periodic(8) that used + insecure temporary files has been corrected (see security + advisory FreeBSD-SA-01:12). [MERGED]

+ +

OpenSSH 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]

+ +

A bug in + timed(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:28). + [MERGED]

+ +

A bug in + rwhod(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:29). + [MERGED]

+ +

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]

+ +

A remotely-exploitable vulnerability in + ntpd(8) has been closed + (see security advisory FreeBSD-SA-01:31). [MERGED]

+ +

A security hole in IPFilter's fragment cache has been + closed (see security advisory FreeBSD-SA-01:32). + [MERGED]

+ +

Buffer overflows in + 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, + glob(3) allows + specification of a limit on the number of pathname + matches it will return. + ftpd(8) now uses this + feature (see security advisory FreeBSD-SA-01:33). + [MERGED]

+ +

Initial sequence numbers in TCP are more thoroughly + randomized (see security advisory FreeBSD-SA-01:39). Due + to some possible compatibility issues, the behavior of + this security fix can be enabled or disabled via the net.inet.tcp.tcp_seq_genscheme + sysctl variable.[MERGED]

+ +

A vulnerability in the + 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]

+ +

A flaw allowed some signal handlers to remain in + effect in a child process after being exec-ed from its + parent. This allowed an attacker to execute arbitrary + code in the context of a setuid binary. This flaw has + been corrected (see security advisory FreeBSD-SA-01:42). + [MERGED]

+ +

A remote buffer overflow in + tcpdump(1) has been + fixed (see security advisory FreeBSD-SA-01:48). + [MERGED]

+ +

A remote buffer overflow in + telnetd(8) has been + fixed (see security advisory FreeBSD-SA-01:49). + [MERGED]

+ +

The new net.inet.ip.maxfragpackets and net.inet.ip6.maxfragpackets sysctl + variables limit the amount of memory that can be consumed + by IPv4 and IPv6 packet fragments, which defends against + some denial of service attacks (see security advisory + FreeBSD-SA-01:52). [MERGED]

+ +

A flaw in the implementation of the + ipfw(8) me rules on point-to-point links has been + corrected. Formerly, me filter + rules would match the remote IP address of a + point-to-point interface in addition to the intended + local IP address (see security advisory + FreeBSD-SA-01:53). [MERGED]

+ +

A vulnerability in + procfs(5), which could + allow a process to read sensitive information from + another process's memory space, has been closed (see + security advisory FreeBSD-SA-01:55). [MERGED]

+ +

The PARANOID hostname + checking in tcp_wrappers now + works as advertised (see security advisory + FreeBSD-SA-01:56). [MERGED]

+ +

A local root exploit in + sendmail(8) has been + closed (see security advisory FreeBSD-SA-01:57). + [MERGED]

+ +

A remote root vulnerability in + lpd(8) has been closed + (see security advisory FreeBSD-SA-01:58). [MERGED]

+ +

A race condition in + rmuser(8) that briefly + exposed a world-readable /etc/master.passwd has been fixed (see + security advisory FreeBSD-SA-01:59). [MERGED]

+ +

A vulnerability in UUCP has + been closed (see security advisory FreeBSD-SA-01:62). All + non-root-owned binaries in + standard system paths now have the schg flag set to prevent exploit vectors + when run by + cron(8), by root, or by a user other then the one + owning the binary. In addition, + uustat(1) is now run + via /etc/periodic/daily/410.status-uucp as + uucp, not root. In FreeBSD -CURRENT, UUCP has since been moved to the Ports + Collection and no longer a part of the base system. + [MERGED]

+ +

A security hole in OpenSSH, + which could allow users to execute code with arbitrary + privileges if UseLogin yes was + set, has been closed. Note that the default value of this + setting is UseLogin no. (See + security advisory FreeBSD-SA-01:63.) [MERGED]

+ +

The use of an insecure temporary directory by + pkg_add(1) could permit + a local attacker to modify the contents of binary + packages while they were being installed. This hole has + been closed. (See security advisory FreeBSD-SA-02:01.) + [MERGED]

+ +

A race condition in + pw(8), which could + expose the contents of /etc/master.passwd, has been eliminated. + (See security advisory FreeBSD-SA-02:02.) [MERGED]

+ +

A bug in + k5su(8) could have + allowed a process that had given up superuser privileges + to regain them. This bug has been fixed. (See security + advisory FreeBSD-SA-02:07.) [MERGED]

+ +

An ``off-by-one'' bug has been fixed in OpenSSH's multiplexing code. This bug + could have allowed an authenticated remote user to cause + + sshd(8) to execute + arbitrary code with superuser privileges, or allowed a + malicious SSH server to execute arbitrary code on the + client system with the privileges of the client user. + (See security advisory FreeBSD-SA-02:13.) [MERGED]

+ +

A programming error in zlib + could result in attempts to free memory multiple times. + The + malloc(3)/ + free(3) routines used + in FreeBSD are not vulnerable to this error, but + applications receiving specially-crafted blocks of + invalid compressed data could be made to function + incorrectly or abort. This zlib bug has been fixed. For a + workaround and solutions, see security advisory FreeBSD-SA-02:18. [MERGED]

+ +

Bugs in the TCP SYN cache (``syncache'') and SYN + cookie (``syncookie'') implementations, which could cause + legitimate TCP/IP traffic to crash a machine, have been + fixed. For a workaround and patches, see security + advisory FreeBSD-SA-02:20. [MERGED]

+ +

A routing table memory leak, which could allow a + remote attacker to exhaust the memory of a target + machine, has been fixed. A workaround and patches can be + found in security advisory FreeBSD-SA-02:21. [MERGED]

+ +

A bug with memory-mapped I/O, which could cause a + system crash, has been fixed. For more information about + a solution, see security advisory FreeBSD-SA-02:22. [MERGED]

+ +

A security hole, in which SUID programs could be made + to read from or write to inappropriate files through + manipulation of their standard I/O file descriptors, has + been fixed. Information regarding a solution can be found + in security advisory FreeBSD-SA-02:23. [MERGED]

+ +

Some unexpected behavior could be allowed with + k5su(8) because it does + not require that an invoking user be a member of the wheel group when attempting to + become the superuser (this is the case with + su(1)). To avoid this + situation, + k5su(8) is now + installed non-SUID by default (effectively disabling it). + More information can be found in security advisory FreeBSD-SA-02:24. [MERGED]

+ +

Multiple vulnerabilities were found in the + bzip2(1) utility, which + could allow files to be overwritten without warning or + allow local users unintended access to files. These + problems have been corrected with a new import of bzip2. For more information, see + security advisory FreeBSD-SA-02:25. [MERGED]

+ +

A bug has been fixed in the implementation of the TCP + SYN cache (``syncache''), which could allow a remote + attacker to deny access to a service when accept filters + (see + accept_filter(9)) were + in use. This bug has been fixed; for more information, + see security advisory FreeBSD-SA-02:26. [MERGED]

+ +

Due to a bug in + rc(8)'s use of shell + globbing, users may be able to remove the contents of + arbitrary files if /tmp/.X11-unix does not exist and the + system can be made to reboot. This bug has been corrected + (see security advisory FreeBSD-SA-02:27). [MERGED]

+ +

A buffer overflow in the resolver, which could be + exploited by a malicious domain name server or an + attacker forging DNS messages, has been fixed. See + security advisory FreeBSD-SA-02:28 for more details. + [MERGED]

+ +

A buffer overflow in + tcpdump(1), which could + be triggered by badly-formed NFS packets, has been fixed. + See security advisory FreeBSD-SA-02:29 for more details. + [MERGED]

+ +

+ ktrace(1) can no longer + trace the operation of formerly privileged processes; + this prevents the leakage of sensitive information that + the process could have obtained before abandoning its + privileges. For a discussion of this issue, see security + advisory FreeBSD-SA-02:30 for more details. + [MERGED]

+ +

A race condition in + pppd(8), which could be + used to change the permissions of an arbitrary file, has + been corrected. For more information, see security + advisory FreeBSD-SA-02:32. [MERGED]

+ +

Multiple buffer overflows in OpenSSL have been corrected, by way of + an upgrade to the base system version of OpenSSL. More details can be found in + security advisory FreeBSD-SA-02:33. [MERGED]

+ +

A heap buffer overflow in the XDR decoder has been + fixed. For more details, see security advisory FreeBSD-SA-02:34. [MERGED]

+ +

A bug that could allow local users to read and write + arbitrary blocks on an FFS filesystem has been corrected. + More details can be found in security advisory FreeBSD-SA-02:35. [MERGED]

+ +

A bug in the NFS server code, which could allow a + remote denial of service attack, has been fixed. Security + advisory FreeBSD-SA-02:36 has more details. + [MERGED]

+ +

A bug that could allow local users to panic a system + using the + kqueue(2) mechanism has + been fixed. More information is contained in security + advisory FreeBSD-SA-02:37. [MERGED]

+ +

Several bounds-checking bugs in system calls, which + could result in some system calls returning a large + portion of kernel memory, have been fixed. More + information can be found in security advisory FreeBSD-SA-02:38. [MERGED]

+ +

A bug that could allow applications using libkvm to leak sensitive file descriptors + has been corrected. (See security advisory FreeBSD-SA-02:39 for more details.) + [MERGED]

+ +

Buffer overflows in kadmind(8) and k5admin have been + corrected. More details can be found in security advisory + FreeBSD-SA-02:40. [MERGED]

+ +

Errors in + smrsh(8), which could + allow users to circumvent restrictions on what programs + can be executed, have been fixed. See FreeBSD-SA-02:41 for details. + [MERGED]

+ +

Buffer overflows in the DNS + resolver(3), which + could cause some applications to fail, have been + corrected. More details are in FreeBSD-SA-02:42. [MERGED]

+ +

Multiple vulnerabilities in BIND have been fixed, as described in + FreeBSD-SA-02:43. [MERGED]

+

+ +

+

+ +

2.3 Userland + Changes

+ +

Support for + a.out(5) format + executables in the compiler toolchain has been largely + removed.

+ +

+

+
Note: This is a work in progress. + Eventually, + a.out(5) support + will resurface in a series of ports/packages.
+

+

+
+
+ +

+ arp(8) now prints [fddi] or [atm] tags for addresses on interfaces of + those types.

+ +

The + asa(1) utility, to + interpret FORTRAN carriage-control characters, has been + added.

+ +

+ at(1) now supports the + -r command-line option to remove + jobs and the -t option to specify + times in POSIX time format.

+ +

The system + awk(1) now refers to BWK awk.

+ +

+ basename(1) now accept + -a and -s + flags, which allow it to perform the + basename(3) function on + multiple files.

+ +

+ biff(1) now accepts a + b argument to enable ``bell + notification'' of new mail (which does not disturb the + terminal contents as biff y + would). [MERGED]

+ +

+ biff(1) now uses the + first terminal associated with the standard input, + standard output or standard error file descriptor, in + that order. Thus, it is possible to use the redirection + facilities of a shell (biff n < + /dev/ttyp1) to toggle the notification for other + terminals.

+ +

+ burncd(8) now supports + Disk At Once (DAO) mode, selectable via the -d flag. [MERGED]

+ +

+ burncd(8) now has the + ability to write VCDs/SVCDs. [MERGED]

+ +

+ burncd(8) now accepts a + value of max for its -s option to set the drive's maximum write + speed.

+ +

+ bzgrep(1), + bzegrep(1), and + bzfgrep(1) have been + added to perform + grep(1)-type operations + on + bzip2(1)-compressed + files.

+ +

+ calendar(1) now takes a + -W option, which operates similar + to -A but without special + treatment at weekends, and a -Foption to change the notion of + ``Friday''.

+ +

+ catman(1) is now a C + program, instead of a Perl script.

+ +

+ cdcontrol(1) now + supports a speed command to set + the maximum speed to be used by the drive (the maximum + possible speed can be selected setting the speed to max).

+ +

A + check_utility_compat(3) + library function has been added to libc, to determine whether certain + FreeBSD base system utilities should behave in FreeBSD + 4-compatible mode or in a ``standard'' mode (default + standard). The configuration is done + malloc(3)-style, with + either an environment variable or a symbolic link.

+ +

+ chflags(1) has moved + from /usr/bin to /bin.

+ +

+ chmod(1) now supports a + -h for changing the mode of a + symbolic link.

+ +

+ chmod(1) now also, when + the mode is modified, prints the old and new modes if the + -v option is specified more than + once.

+ +

+ chown(8) no longer + takes . as a user/group + delimeter. This change was made to support usernames + containing a ..

+ +

Use of the CSMG_* macros no + longer require inclusion of <sys/param.h>

+ +

A compat4x distribution has + been added for compatibility with FreeBSD 4-STABLE.

+ +

+ cp(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A new + csplit(1) utility, + which splits files based on context, has been added.

+ +

+ ctags(1) now creates + tags for typedefs, structs, unions, and enums by default + (implying the -t option). The new + -T reverts to the old + behavior.

+ +

The + daemon(8) program, a + command-line interface to + daemon(3), has been + added. It detaches itself from its controlling terminal + and executes a program specified on the command line. + This allows the user to run an arbitrary program as if it + were written to be a daemon. [MERGED]

+ +

The + devd(8) utility, a + userland daemon that can run arbitrary commands when + devices come and go in the device tree, has been added. + This program is a generalization of some of the + functionality of + pccardd(8).

+ +

+

+
Note: + devd(8) is + work-in-progress.
+

+

+
+
+ +

+ devinfo(8), a simple + tool to print the device tree and resource usage by + devices, has been added.

+ +

diskpart(8) has been declared obsolete, and has been + removed.

+ +

+ dump(8) now supports a + new -S flag to allow it to just + print out the dump size estimates and exit. [MERGED]

+ +

+ expr(1) is now + compliant with POSIX.2-1992 (and thus also with + POSIX.1-2001). Some program depend on the old, historic + behavior and do not properly protect their arguments to + keep them from being misinterpreted as command-line + options. (the + devel/libtool port/package, + used by many GNU programs, is a notable example). The old + behavior can be requested by enabling compatibility mode + for + expr(1) as described in + + check_utility_compat(3).

+ +

+ fbtab(5) now accepts + glob matching patterns for target devices, not just + individual devices and directories.

+ +

+ fdread(1), a program to + read data from floppy disks, has been added. It is a + counterpart to + 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 + dd(1).

+ +

+ finger(1) now has + support for a .pubkey file. + [MERGED]

+ +

+ finger(1) now supports + a -g flag to restrict the + printing of GECOS information to the user's full name + only. [MERGED]

+ +

+ finger(1) now supports + the -4 and -6 flags to specify an address family for + remote queries. [MERGED]

+ +

+ fold(1) now supports a + -b flag to break at byte + positions and a -s flag to break + at word boundaries. [MERGED]

+ +

+ fsck(8) wrappers have + been imported; this feature provides infrastructure for + + fsck(8) to work on + different types of filesystems (analogous to + mount(8)).

+ +

The behavior of + fsck(8) when dealing + with various passes (a la /etc/fstab) has been modified to + accommodate multiple-disk filesystems.

+ +

+ fsck(8) now has support + for foreground (-F) and + background (-B) checks. + Traditionally, + fsck(8) is invoked + before the filesystems are mounted and all checks are + done to completion at that time. If background checking + is available, + fsck(8) is invoked + twice. It is first invoked at the traditional time, + before the filesystems are mounted, with the -F 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 -B 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 background_fsck option in + rc.conf(5).

+ +

+ fsck_ffs(8) now + supports background filesystem checks to mounted FFS + filesystems with the -B option + (softupdates must be enabled on these filesystems). The + -F flag now determines whether a + specified filesystem needs foreground checking.

+ +

+ ftpd(8) now supports + the -m option to permit guest + users to modify existing files if allowed by filesystem + permissions. In particular, this enables guest users to + resume uploads. [MERGED]

+ +

+ ftpd(8) now supports + the -M option to prevent guest + users from creating directories. [MERGED]

+ +

+ ftpd(8) now supports + -o and -O + options to disable the RETR + command; the former for everybody, and the latter only + for guest users. Coupled with -A + and appropriate file permissions, these can be used to + create a relatively safe anonymous FTP drop box for + others to upload to. [MERGED]

+ +

+ ftpd(8) now supports + the -W option to disable logging + FTP sessions to + wtmp(5). [MERGED]

+ +

The + getconf(1) utility has + been added. It prints the values of POSIX or X/Open path + or system configuration variables. [MERGED]

+ +

gifconfig(8) is obsolete and has been removed. Its + functionality is now handled by the tunnel and deletetunnel commands of + ifconfig(8).

+ +

+ gprof(1) now has a -K option to enable dynamic symbol + resolution from the currently-running kernel. With this + change, properly-compiled KLD modules are now able to be + profiled.

+ +

The gpt tool for manipulating EFI GPT partitions has + been added.

+ +

The ibcs(8), linux(8), osf1(8), and 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.

+ +

+ ifconfig(8) now has the + ability to set promiscuous mode on an interface, via the + new promisc flag. [MERGED]

+ +

+ ifconfig(8) now + supports a monitor interface + flag, which blocks transmission of packets on that + interface. This feature is useful for monitoring network + traffic without interacting with the network in + question.

+ +

By default, + inetd(8) is no longer + run by + rc(8) at boot-time, + although + sysinstall(8) gives the + option of enabling it during binary installations. + inetd(8) can also be + enabled by adding the following line to /etc/rc.conf:

+

+    inetd_enable="YES"
+

+ +

+ inetd(8) now has the + capability for limiting the maximum number of + simultaneous invocations of each service from a single IP + address. [MERGED]

+ +

+ ipfw(8) filter rules + can now match on the value of the IPv4 precedence + field.

+ +

+ kbdmap(1) and + vidfont(1) have been + converted from Perl to C.

+ +

+ kenv(1) now has the + ability to set or delete kernel environment + variables.

+ +

The kget(8) utility has been removed (it was only + useful for UserConfig, which is not present in FreeBSD + 5.0-DP2).

+ +

+ killall(1) no longer + tries to kill zombie processes unless the -z flag is specified.

+ +

+ ktrdump(8), a utility + to dump the ktr trace buffer from userland, has been + added.

+ +

+ ldd(1) now supports a + -a flag to list all the objects + that are needed by each loaded object.

+ +

libc is now thread-safe by + default; libc_r contains only + thread functions.

+ +

libstand now has support for + overwriting the contents of a file on a UFS filesystem + (it cannot expand or truncate files because the + filesystem may be dirty or inconsistent).

+ +

libgmp has been superceded + by libmp.

+ +

The functions from libposix1e have been integrated into libc.

+ +

+ lock(1) now accepts a + -v to disable switching VTYs + while the current terminal is locked. This permits + locking the entire console from a single terminal. + [MERGED]

+ +

+ lpc(8) has been + improved; lpc clean is now + somewhat safer, and a new lpc + tclean command has been added to check to see what + files would be removed by lpc + clean. lpc topq has been + reimplemented, and now allows for a much more flexible + specification of which jobs should be moved (such as a + range of job numbers, or a hostname). An lpc bottomq command has been added to move + jobs to the bottom of a print queue, and a new lpc setstatus command can be used to set a + printer's status message. [MERGED]

+ +

The + ls(1) program now + supports a -m flag to list files + across a page, a -p flag to force + printing of a / after + directories, and a -x flag to + sort filenames across a page. [MERGED]

+ +

+ makewhatis(1) is now a + C program, instead of a Perl script.

+ +

+ man(1) is no longer + installed SUID man, in order to + reduce vulnerabilities associated with generating + ``catpages'' (preformatted manual pages cached for + repeated viewing). As a result, + man(1) can no longer + create system catpages on a regular user's behalf. It is + still able to do so if the user has write permissions to + the directory holding catpages (e.g. a user's own + manpages) or if the running user is root.

+ +

The mca utility, for decoding machine check records, + has been added.

+ +

The + mdmfs(8) command has + been added; it is a wrapper around + mdconfig(8), + disklabel(8), + newfs(8), and + mount(8) that mimics + the command line option set of the deprecated + mount_mfs(8).

+ +

+ mesg(1) now conforms to + SUSv3. Among other things, it now uses the first terminal + associated with the standard input, standard output or + standard error file descriptor, in that order. Thus, it + is possible to use the redirection facilities of a shell + (mesg n < /dev/ttyp1) to + control write access for other terminals.

+ +

+ mountd(8) and + nfsd(8) have moved from + /sbin to /usr/sbin.

+ +

+ mv(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A number of archaic features of + newfs(8) have been + removed; these implement tuning features that are + essentially useless on modern hard disks. These features + were controlled by the -O, -d, -k, -l, -n, -p, -r, -t, and -x + flags.

+ +

+ newfs(8) now supports a + -O flag to select the creation of + UFS1 or UFS2 filesystems.

+ +

The + newgrp(1) utility to + change to a new group has been added.

+ +

+ newsyslog(8) now + compresses log files using + bzip2(1) by default. + (The former behavior of using + gzip(1) can be + specified in /etc/newsyslog.conf.)

+ +

The + nextboot(8) utility has + been added to specify an alternate kernel and/or boot + flags to be used the next time the machine is booted. A + previous incarnation of this feature first appeared in + FreeBSD 2.2.

+ +

NFS now works over + IPv6.

+ +

+ nice(1) now uses the + -n option to specify the + ``niceness'' of the utility being run. [MERGED]

+ +

nsswitch support has been + merged from NetBSD. By creating an + nsswitch.conf(5) file, + FreeBSD can be configured so that various databases such + as + passwd(5) and + group(5) can be looked + up using flat files, NIS, or Hesiod. If /etc/nsswitch.conf does not exist, it + will be automatically generated from an existing /etc/hosts.conf at system startup + time. The /etc/hosts.conf file + may be used by old executables; it will be automatically + generated from an existing /etc/nsswitch.conf during system startup + if it exists.

+ +

+ od(1) now supports the + -A option to specify the input + address base, the -N option to + specify the number of bytes to dump, the -j option to specify the number of bytes to + skip, the -s option to output + signed decimal shorts, and the -t + option to specify output type. [MERGED]

+ +

PAM support has been added + for account management and sessions.

+ +

PAM configuration is now + specified by files in /etc/pam.d/, rather than a single /etc/pam.conf file. /etc/pam.d/README has more details.

+ +

A + pam_echo(8) echo + service module has been added.

+ +

A + pam_exec(8) program + execution service module has been added.

+ +

A + pam_ftp(8) module has + been added to allow authentication of anonymous FTP + users.

+ +

A + pam_ftpusers(8) module + has been added to perform checks against the + ftpusers(5) file.

+ +

A + pam_ksu(8) module has + been added to do Kerberos 5 authentication and $HOME/.k5login authorization for + su(1).

+ +

A + pam_lastlog(8) module + has been added to record sessions in the + utmp(5), + wtmp(5), and + lastlog(5) + databases.

+ +

A + pam_login_access(8) + module has been added, to allow checking against /etc/login.access.

+ +

The + pam_nologin(8) module, + which can disallow logins using + nologin(5), has been + added.

+ +

The + pam_opie(8) and + pam_opieaccess(8) + modules have been added to control authentication via + opie(4). [MERGED]

+ +

A + pam_passwdqc(8) module + has been added, to check the quality of passwords + submitted during password changes.

+ +

A + pam_rhosts(8) module + has been added to support + rhosts(5) + authentication.

+ +

The + pam_rootok(8) module, + which can be used to authenticate only the superuser, has + been added.

+ +

A + pam_securetty(8) module + has been added to check the ``security'' of a TTY, as + listed in + ttys(5).

+ +

A + pam_self(8) module, + which allows self-authentication of a user, has been + added.

+ +

A + pam_wheel(8) module has + been added to permit authentication to members of a + group, which defaults to wheel.

+ +

The + pathchk(1) utility, + which checks pathnames for validity or portability + between POSIX systems, has been added. [MERGED]

+ +

+ ping(8) now supports a + -o flag to exit after receiving a + reply.

+ +

prefix(8) is obsolete and has been removed. Its + functionality is provided by the eui64 command to + ifconfig(8).

+ +

The + pselect(3) library + function (introduced by POSIX.1 as a slightly stronger + version of + select(2)) has been + added.

+ +

+ pwd(1) now supports the + -L flag to print the logical + current working directory. [MERGED]

+ +

+ quota(1) now takes a + -l flag to suppress quote checks + on NFS filesystems.

+ +

The pseudo-random number generator implemented by + rand(3) has been + improved to provide less biased results.

+ +

+ rcmd(3) now supports + the use of the RSH environment + variable to specify a program to use other than + rsh(1) for remote + execution. As a result, programs such as + dump(8), can use + ssh(1) for remote + transport.

+ +

+ rdist(1) has been + retired from the base system, but is still available from + FreeBSD Ports Collection as + net/44bsd-rdist.

+ +

The + renice(8) command + implements a -n option, which + specifies an increment to be applied to the priority of a + process. [MERGED]

+ +

+ rpcbind(8) has replaced + + portmap(8).

+ +

+ rpcgen(1) now uses /usr/bin/cpp (as on NetBSD), not + /usr/libexec/cpp.

+ +

+ rpc.lockd(8) has been + imported from NetBSD. This daemon provides support for + servicing client NFS locks.

+ +

+ rtld(1) will now print + the names of all objects that cause each object to be + loaded, if the LD_TRACE_LOADED_OBJECTS_ALL environment + variable is defined.

+ +

+ sed(1) now takes a -i option to enable in-place editing + of files. [MERGED]

+ +

The + setfacl(1) and + getfacl(1) commands + have been added to manage filesystem Access Control + Lists.

+ +

+ sh(1) no longer + implements printf as a built-in + command because it was considered less valuable compared + to the other built-in commands (this functionality is, of + course, still available through the + printf(1) + executable).

+ +

+ sh(1) now supports a + -C option to prevent existing + regular files from being overwritten by output + redirection, and a -u to give an + error if an unset variable is expanded. [MERGED]

+ +

The + sh(1) built-in cd command now supports -L and -P flags to + invoke logical or physical modes of operation, + respectively. Logical mode is the default, but the + default can be changed with the physical + sh(1) option. + [MERGED]

+ +

The + sh(1) built-in jobs command now supports a -s flag to output PIDs only and a -l flag to add PIDs to the output. + [MERGED]

+ +

+ sh(1) now supports a + bind built-in command, which + allows the key bindings for the shell's line editor to be + changed.

+ +

The + sh(1) built-in export and readonly commands now support a -p flag to print their output in + ``portable'' format. [MERGED]

+ +

+ sh(1) no longer accepts + invalid constructs as command & && command, && command, or || command. [MERGED]

+ +

+ spkrtest(8) is now a + sh(1) script, rather + than a Perl script.

+ +

+ split(1) now supports a + -a option to specify the number + of letters to use for the suffix of split files. + [MERGED]

+ +

In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, struct selinfo and related functions + have been moved to <sys/selinfo.h>.

+ +

+ su(1) now uses PAM for authentication.

+ +

+ sysctl(8) now accepts a + -d flag to print the descriptions + of variables.

+ +

The default root partition in + sysinstall(8) is now + 100MB on the i386 and pc98, 120MB on the Alpha.

+ +

+ sysinstall(8) now lives + in /usr/sbin, which simplifies + the installation process. The + sysinstall(8) manpage + is also installed in a more consistent fashion now.

+ +

+ sysinstall(8) no longer + mounts the + procfs(5) filesystem by + default on new installs.

+ +

+ tabs(1), a utility to + set terminal tab stops, has been added.

+ +

The + termcap(5) database now + uses the xterm terminal type + from XFree86. As a result, + xterm(1) now supports + color by default and the common workaround of setting TERM to xterm-color is no longer necessary. Use of + the xterm-color terminal type + may result in (benign) warnings from applications.

+ +

+ tftpd(8) now supports + RFC 2349 (TFTP Timeout Interval and Transfer Size + Options); this feature is required by some firmware like + EFI boot managers (at least on HP i2000 Itanium servers) + in order to boot an image using TFTP.

+ +

A version of Transport Independent RPC (TI-RPC) has been imported.

+ +

+ tip(1) has been updated + from OpenBSD, and has the + ability to act as a + cu(1) substitute.

+ +

+ top(1) will now use the + full width of its tty.

+ +

+ touch(1) now takes a + -h option to operate on a + symbolic link, rather than what the link points to.

+ +

+ tr(1) now has basic + support for equivalence classes for locales that support + them. [MERGED]

+ +

+ tr(1) now supports a + -C flag to complement the set of + characters specified by the first string argument.

+ +

+ tunefs(8) now supports + the -a and -l flags to enable and disable the FS_ACLS and FS_MULTILABEL administrative flags on UFS + file system.

+ +

A + ugidfw(8) utility has + been added to manage the rulesets provided by the mac_bsdextended Mandatory Access + Control policy, similar to + ipfw(8).

+ +

UUCP has been removed from + the base system. It can be found in the Ports Collection, + in + net/freebsd-uucp.

+ +

+ unexpand(1) now + supports a -t to specify tabstops + analogous to + expand(1). [MERGED]

+ +

+ usbdevs(8) now supports + a -d flag to show the device + driver associated with each device.

+ +

The base64 capabilities of + uuencode(1) and + uudecode(1) can now be + automatically enabled by invoking these utilities as + b64encode(1) and + b64decode(1) + respectively. [MERGED]

+ +

Functions to implement and manipulate OSF/DCE + 1.1-compliant UUIDs have been added to libc. More information can be found in + uuid(3).

+ +

The + uuidgen(1) utility has + been added. It uses the new + uuidgen(2) system call + to generate one or more Universally Unique Identifiers + compatible with OSF/DCE 1.1 version 1 UUIDs.

+ +

+ vidcontrol(1) now + accepts a -S to allow the user to + disable VTY switching. [MERGED]

+ +

The default stripe size in + vinum(8) has been + changed from 256KB to 279KB, to spread out superblocks + more evenly between stripes.

+ +

+ wc(1) now supports a + -m flag to count characters, + rather than bytes.

+ +

+ whereis(1), formerly a + Perl script, has been rewritten in C. It now supports a + -x flag to suppress the run of + locate(1), and a -q flag suppresses the leading name + of the query.

+ +

+ whereis(1) now supports + a -a flag to report all matches + instead of only the first of each requested type.

+ +

+ which(1) is now a C + program, rather than a Perl script.

+ +

+ who(1) now has a number + of new options: -H shows column + headings; -T shows + mesg(1) state; -m is an equivalent to am i; -u shows idle + time; -q to list names in + columns. [MERGED]

+ +

+ wicontrol(8) now + supports a -l to list the + stations associated in hostap + mode and a -L to list available + access points.

+ +

+ xargs(1) now supports a + -I replstr option that allows the + user to tell + xargs(1) to insert the + data read from standard input at specific points in the + command line arguments rather than at the end. (A + FreeBSD-specific -J option is + similar.) [MERGED]

+ +

+ xargs(1) now supports a + -L option to force its utility + argument to be called after some number of lines. + [MERGED]

+ +

Various routines in the C library now have support for + ``wide'' characters. Among these are character class + functions such as + wctype(3), wide + character I/O functions such as + getwc(3), formatted I/O + functions such as + wprintf(3) and + wscanf(3). Conversion + functions to + multibyte(3) characters + are also supported.

+ +

A number of utilities and libraries were enhanced to + improve their conformance with the Single UNIX + Specification (SUSv3) and IEEE Std 1003.1-2001 + (``POSIX.1''). Specific features added have been listed + in the release notes for each utility. The standards + conformance of each utility or library function is + generally listed in its manual page.

+ +

A number of games have been removed from the base + system. These include: adventure(6), arithmetic(6), + atc(6), backgammon(6), battlestar(6), bs(6), canfield(6), + cribbage(6), fish(6), hack(6), hangman(6), larn(6), + mille(6), phantasia(6), piano(6), pig(6), quiz(6), + rain(6), robots(6), rogue(6), sail(6), snake(6), trek(6), + wargames(6), worm(6), worms(6), wump(6). dm(8), which was + used to control access to games, is no longer necessary, + and has also been removed. The ``utility-like'' games, as + well as + fortune(6), remain.

+ +

+

+
Note: The affected programs will reappear + as a port in the Ports Collection. This note will + contain a pointer to that port, once it has been + committed.
+

+

+
+
+ +

+

+ +

2.3.1 Contributed + Software

+ +

am-utils has been updated + to 6.0.7.

+ +

A 10 February 2002 snapshot of awk from Bell Labs (variously known + as ``BWK awk'' or ``The One True AWK'') has been + imported. It is available as awk or nawk.

+ +

BIND has been updated to + 8.3.3. [MERGED]

+ +

Binutils has been updated + to a pre-release snapshot of 2.13.1 from 11 October + 2002.

+ +

file has been updated to + 3.39.

+ +

gcc has been updated to a + pre-release snapshot of gcc + 3.2.1, from 9 October 2002.

+ +

+

+
Warning: The C++ ABI from gcc 3.2.X is not compatible with + previous versions.
+

+

+
+
+ +

gdb has been updated to + version 5.2.1.

+ +

gperf has been updated to + 2.7.2.

+ +

groff and its related + utilities have been updated to FSF version 1.18.1.

+ +

Heimdal Kerberos has been + updated to a pre-0.5 snapshot from 16 September + 2002.

+ +

The ISC DHCP client has + been updated to 3.0.1RC9.

+ +

The + more(1) command has + been replaced by + less(1), although it + can still be run as more. + [MERGED] Version 371 of less + has been imported.

+ +

An XML processing library, named libbsdxml, has been added for the + benefit of XML-using utilities in the base system. It + is based almost entirely on an import of expat 1.95.5, but is installed under + a different name to avoid conflicts with any versions + of expat installed from the + Ports Collection.

+ +

libpcap has been updated + to 0.7.1. [MERGED]

+ +

libreadline has been + updated to 4.2.

+ +

libz has been updated to + 1.1.4.

+ +

lint has been updated to + snapshot of NetBSD + lint(1) as of 19 July + 2002.

+ +

lukemftp 1.6 beta 2 (the + FTP client from NetBSD) has replaced the FreeBSD + ftp(1) program. Among + its new features are more automation methods, better + standards compliance, transfer rate throttling, and a + customizable command-line prompt. Some environment + variables and command-line arguments have changed.

+ +

The FTP daemon from NetBSD, otherwise known as lukemftpd 1.2 beta 1, has been + imported and is available as + lukemftpd(8). + [MERGED]

+ +

+ m4(1) has been + imported from OpenBSD, as of 26 April 2002. + [MERGED]

+ +

ncurses has been updated + to 5.2-20020615.

+ +

The NTP suite of programs + has been updated to 4.1.1b.

+ +

OpenPAM (``Citronella'' + release) has been imported, replacing Linux-PAM.

+ +

The OPIE + one-time-password suite has been updated to 2.4. It has + completely replaced the functionality of S/Key. [MERGED]

+ +

Perl has been removed + from the FreeBSD base system. It can still be installed + from the FreeBSD Ports Collection or as a binary + package; moving it out of the base system will make + future upgrades and maintenence easier. To reduce the + dependence of the base system on Perl, many utilities + have been rewritten as shell scripts or C programs + (specific notes are made for each affected utility). + /usr/bin/perl is now a + ``wrapper'' program, so that programs expecting to find + a Perl interpreter there will be able to function + correctly.

+ +

+

+
Warning: The Perl removal and package + integration work is ongoing.
+

+

+
+
+ +

GNU ptx has been removed + from the base system. It is not used anywhere in the + base system, and has not been recently updated or + maintained. Users requiring its functionality can + install this utility as a part of the + textproc/textutils + port.

+ +

The rc.d framework from + NetBSD has been imported. It breaks down the system + startup functionality into a number of small, + ``task-oriented'' scripts in /etc/rc.d, with dynamic-determined + ordering of startup scripts performed at boot-time.

+ +

GNU sort has been updated + to the version from GNU + textutils 2.0.21.

+ +

+ stat(1) from NetBSD, as of 5 June 2002 has, + been imported.

+ +

GNU tar has been updated + to 1.13.25. [MERGED]

+ +

tcpdump has been updated + to 3.7.1. [MERGED]

+ +

The + csh(1) shell has been + replaced by + tcsh(1), although it + can still be run as csh. tcsh has been updated to + version 6.12. [MERGED]

+ +

The contributed version of tcp_wrappers now includes the + tcpd(8) helper + daemon. While not strictly necessary in a standard + FreeBSD installation (because + inetd(8) already + incorporates this functionality), this may be useful + for + inetd(8) replacements + such as xinetd. [MERGED]

+ +

texinfo has been updated + to 4.2. [MERGED]

+ +

top has been updated to + version 3.5b12. [MERGED]

+ +

traceroute has been + updated to LBL version 1.4a12.

+ +

The timezone database has been updated to the tzdata2002d release. [MERGED]

+ +

+

+ +

2.3.1.1 + CVS

+ +

cvs has been updated to + 1.11.2. [MERGED]

+

+ +

+

+ +

2.3.1.2 + CVSup

+

+ +

+

+ +

2.3.1.3 + KAME

+

+ +

+

+ +

2.3.1.4 + OpenSSH

+ +

OpenSSH has been + updated to version 3.1. [MERGED] Among the + changes:

+ +

+
The *2 files are + obsolete (for example, ~/.ssh/known_hosts can hold the + contents of ~/.ssh/known_hosts2).
+
+
+ ssh-keygen(1) + can import and export keys using the SECSH Public + Key File Format, for key exchange with several + commercial SSH implementations.
+
+
+ ssh-add(1) now + adds all three default keys.
+
+
+ ssh-keygen(1) + no longer defaults to a specific key type; one + must be specified with the -t option.
+

+
+
+ +

OpenSSH has been + updated to 3.4p1. [MERGED] The main changes are:

+ +

+
A ``privilege separation'' feature, which uses + unprivileged processes to contain and restrict + the effects of future compromises or programming + errors.
+
+
Several bugfixes, including closure of a + security hole that could lead to an integer + overflow and undesired privilege escalation.
+

+
+
+

+ +

+

+ +

2.3.1.5 + OpenSSL

+ +

OpenSSL has been + updated to 0.9.6g. [MERGED]

+

+ +

+

+ +

2.3.1.6 + sendmail

+ +

sendmail has been + updated from version 8.9.3 to version 8.12.6. + Important changes include: + sendmail(8) is no + longer installed as a set-user-ID root binary (now set-group-ID smmsp); new default file + locations (see /usr/src/contrib/sendmail/cf/README); + + newaliases(1) is + limited to root and trusted + users; STARTTLS encryption; and the MSA port (587) is + turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES + for more information. [MERGED]

+ +

By default, + rc(8) no longer + enables sendmail for + inbound SMTP connections. Note that + sysinstall(8) may + override this default for a binary installation, + based on what security profile is selected. This + functionality can also be manually enabled by adding + the following line to /etc/rc.conf:

+

+    sendmail_enable="YES"
+

+ +

The permissions for sendmail alias and map databases + built via /etc/mail/Makefile now default to + mode 0640 to protect against a file locking local + denial of service. It can be changed by setting the + new SENDMAIL_MAP_PERMS make.conf option. [MERGED]

+ +

The permissions for the sendmail statistics file, /var/log/sendmail.st, have been + changed from mode 0644 to mode 0640 to protect + against a file locking local denial of service. + [MERGED]

+

+ +

+

+ +

2.3.2 + Ports/Packages Collection Infrastructure

+ +

BSDPAN, a collection of + modules that provides tighter integration of Perl into the FreeBSD Ports + Collection, has been added.

+ +

For some time, FreeBSD 5.0-CURRENT (as well as some + 4.X releases) included a pkg_update(1) utility to + update installed packages, as well as their + dependencies. This utility has been removed; a superset + of its functionality can be found in the + sysutils/portupgrade + port.

+ +

+ pkg_version(1), + formerly a Perl script, has been rewritten in C.

+ +

The Ports Collection infrastructure now uses XFree86 4.2.1 as the default + version of the X Window System for the purposes of + satisfying dependencies. To return to using XFree86 3.3.6, add the following line + to /etc/make.conf: + [MERGED]

+

+    XFREE86_VERSION=3
+

+ +

The libraries installed by the + emulators/linux_base port + (required for Linux emulation) have been updated; they + now correspond to those included with Red Hat Linux 7.1. [MERGED]

+ +

By default, packages generated by the Ports + Collection (as well as the packages on the FTP sites) + are now compressed using + bzip2(1), rather than + + gzip(1). (Thus, they + now have a .tbz extension, + rather than a .tgz + extension.) The package tools have been updated to + handle the new format.

+

+ +

+

+ +

2.4 Release + Engineering and Integration

+ +

The bin distribution has + been renamed base, in order to + make creation of combined install/recovery disks + easier.

+ +

It is now possible to make releases of FreeBSD + 5-CURRENT on a FreeBSD 4-STABLE host and vice versa. + Cross-architecture (building a release for a target + architecture on a host of a different architecture) + releases are also possible. See + release(7) for details. + [MERGED]

+ +

A third drivers.flp floppy + has been added to floppy releases. It holds loadable + modules containing drivers that do not fit in the kernel + on the kern.flp disk or in the + mfsroot.flp image.

+

+ +

+

+ +

2.5 + Documentation

+ +

A number of formerly-encumbered documents from the 4.4 + BSD Programmer's Supplementary Documents have been + restored to /usr/share/doc/psd. + These include:

+ +

+
The + UNIX Time-Sharing System (01.cacm)
+
+
UNIX + Implementation (02.implement)
+
+
The + UNIX I/O System (03.iosys)
+
+
UNIX + Programming -- Second Edition (04.uprog)
+
+
The C + Programming Language -- Reference Manual + (06.Clang)
+
+
Yacc: + Yet Another Compiler-Compiler (15.yacc)
+
+
Lex -- + A Lexical Analyzer Generator (16.lex)
+
+
The M4 + Macro Processor (17.m4)
+

+ +

Several formerly-encumbered documents from the 4.4 BSD + User's Supplementary Documents have been restored to /usr/share/doc/usd. They + include:

+ +

+
NROFF/TROFF User's Manual (21.troff)
+
+
A TROFF + Tutorial (22.trofftut)
+

+

+ +

+

+ +

3 Upgrading from + previous releases of FreeBSD

+ +

Users with existing FreeBSD systems are highly encouraged + to read the ``Early Adopter's Guide to FreeBSD 5.0''. This + document generally has the filename EARLY.TXT on the distribution media, or any + other place that the release notes can be found. It offers + some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.X versus + running FreeBSD 4.X.

+ +

+

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

+

FreeBSD/pc98 5.0-DP2 + Release Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.452 2002/11/14 17:59:11 bmah Exp $
+

+ +

+

+ + +

The release notes for FreeBSD 5.0-DP2 contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. Both + changes for kernel and userland are listed, as well as + applicable security advisories that were issued since + the last release. Some brief remarks on upgrading are + also presented.

+

+ +

+

Table of Contents

+

+

2.1.1 Processor/Motherboard + Support
2.1.2 Bootloader + Changes
2.1.3 Network Interface + Support
2.1.4 Network + Protocols
2.1.5 Disks and + Storage
2.1.6 Filesystems
2.1.7 PCCARD + Support
2.1.8 Multimedia + Support
2.1.9 Contributed + Software

+

+

2.3.1 Contributed + Software
2.3.2 Ports/Packages + Collection Infrastructure

+

3 Upgrading from previous releases + of FreeBSD

+

+

+ +

+

+ +

1 Introduction

+ +

This document contains the release notes for FreeBSD + 5.0-DP2 on the NEC PC-98x1 hardware platform. It describes + recently added, changed, or deleted features of FreeBSD. It + also provides some notes on upgrading from previous + versions of FreeBSD.

+ +

The snapshot distribution to which these release notes + apply represents a point along the 5-CURRENT development + branch between 4.0-RELEASE and the future 5.0-RELEASE. Some + pre-built, binary snapshot distributions along this branch + can be found at http://snapshots.jp.FreeBSD.org/.

+

+ +

+

+ +

2 What's New

+ +

This section describes many of the user-visible new or + changed features in FreeBSD since 4.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 4.6-RELEASE). The later items are + marked as [MERGED].

+ +

Typical release note items document new drivers or + hardware support, new commands or options, major bugfixes, + or contributed software upgrades. Applicable security + advisories issued after 4.0-RELEASE are also listed.

+ +

Many additional changes were made to FreeBSD 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.

+ +

+

+ +

2.1 Kernel + Changes

+ +

Execution of + a.out(5) format + executables now requires the COMPAT_AOUT option in the kernel + configuration or the loading of the aout.ko kernel module.

+ +

+ acct(2) has been + changed to open the accounting file in append mode, so + that + accton(8) can be used + to enable accounting to an append-only file. [MERGED]

+ +

A new in-kernel cryptographic framework (see + crypto(4) and + crypto(9)) has been + imported from OpenBSD. It provides a consistent interface + to hardware and software implementations of cryptographic + algorithms for use by the kernel and access to + cryptographic hardware for user-mode applications. + Hardware device drivers are provided to support + hifn-based cards ( + hifn(4)) and + Broadcom-based cards ( + ubsec(4)).

+ +

A new + ddb(4) command show pcpu lists some of the per-CPU + data.

+ +

A devctl device has been + added to allow userland programs to learn when devices + come and go in the device tree (different from the XXX). + This facility is primariliy used by the + devd(8) utility.

+ +

+ devfs(5), which allows + entries in the /dev directory + to be built automatically and supports more flexible + attachment of devices, has been largely reworked. + devfs(5) is now enabled + by default and can be disabled by the NODEVFS kernel option.

+ +

The + devfs(5) ``rule'' + subsystem has been introduced. DEVFS rules permit the + administrator to define certain properties of new device + nodes before they become visible to the userland. Both + static (e.g. /dev/speaker) and + dynamic (e.g. /dev/bpf*, some + removable devices) nodes are supported. Each + devfs(5) mount may have + a different ruleset assigned to it, permitting different + policies to be implemented for things like jails. Rules + and rulesets are manipulated with the + devfs(8) utility.

+ +

The dgm driver has been removed in favor of the digi + driver.

+ +

A new digi driver has been added to support PCI + Xr-based and ISA Xem Digiboard cards. A new + digictl(8) program is + (mainly) used to re-initialize cards that have external + port modules attached such as the PC/Xem.

+ +

An + eaccess(2) system call + has been added, similar to + access(2) except that + the former uses effective credentials rather than real + credentials.

+ +

Initial support has been added for Firewire devices + (see + firewire(4)). + [MERGED]

+ +

Each + jail(2) environment can + now run under its own securelevel.

+ +

The tunable sysctl variables for + jail(2) have moved from + jail.* to the security.* hierarchy. Other + security-related sysctl variables have moved from kern.security.* to security.*.

+ +

The kernel environment is now dynamic, and can be + changed via the new + kenv(2) system + call.

+ +

The labpc(4) driver has been removed due to + ``bitrot''.

+ +

The loader and kernel linker now look for files named + linker.hints in each directory + with KLDs for a module name and version to KLD filename + mapping. The new + kldxref(8) utility is + used to generate these files.

+ +

+ lomac(4), a + Low-Watermark Mandatory Access Control security facility, + has been added as a kernel module. It provides a drop-in + security mechanism in addition to the traditional + UID-based security facilities, requiring no additional + configuration from the administrator. Work on this + feature was sponsored by DARPA and NAI Labs.

+ +

FreeBSD now supports an extensible Mandatory Access + Control framework, the TrustedBSD MAC Framework. It + permits loadable kernel modules to link to the kernel at + compile-time, boot-time, or run-time, and augment the + system security policy. The framework permits modules to + express interest in a variety of events, and also + provides common security policy services such as label + storage. A variety of sample policy modules are shipped + in this release, including implementations of fixed and + floating label Biba integrity models, Multi-Level + Security (MLS) with compartments, and a number of + augmented UNIX security models including a file system + firewall. This feature will permit easier development and + maintenance of local and vendor security extensions. The + extensibility service is enabled by adding options MAC to the kernel + configuration.

+ +

+

+
Note: The MAC framework is considered an + experimental feature in this release, and is not + enabled by default
+

+

+
+
+ +

+ mutex(9) profiling code + has been added, enabled by the MUTEX_PROFILING kernel configuration + option. It enables the debug.mutex.prof.* hierarchy of sysctl + variables.

+ +

The P1003_1B kernel option is + no longer used and has been removed.

+ +

PECOFF (Win32 Execution file format) support has been + added.

+ +

The + random(4) device has + been rewritten to use the Yarrow 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 + random(4) device is now + periodically saved to files in /var/db/entropy, as well as at shutdown + time. The semantics of /dev/random have changed; it never blocks + waiting for entropy bits but generates a stream of + pseudo-random data and now behaves exactly as /dev/urandom.

+ +

A new kernel option, options + REGRESSION, enables interfaces and functionality + intended for use during correctness and regression + testing.

+ +

RLIMIT_VMEM support has been + added. This feature defines a new resource limit that + covers a process's entire virtual memory space, including + + mmap(2) space. This + limit can be configured in + login.conf(5) via the + new vmemoryuse variable. + [MERGED]

+ +

A bug in the + sendfile(2) system + call, in which headers counted against the size of the + file to be sent, has been fixed. [MERGED]

+ +

The + syscons(4) driver now + supports keyboard-controlled pasting, by default bound to + Shift-Insert.

+ +

The uaudio driver, for USB audio devices, has been + added. [MERGED]

+ +

The ubsa driver has been added to support the Belkin + F5U103 (and compatible) USB-to-serial adaptors.

+ +

The + ucom(4) device driver + has been added, to support USB modems, serial devices, + and other programs that need to look like a tty. The + related + uplcom(4) and + uvscom(4) drivers + provide specific support for the Prolific PL-2303 serial + adapter and the SUNTAC Slipper U VS-10U, respectively. + [MERGED]

+ +

To increase security, the UCONSOLE kernel configuration option has + been removed.

+ +

The UserConfig boot-time kernel configuration feature, + usually used to enable, disable, or configure ISA + devices, has been removed. Its functionality has been + replaced by the kernel hints file in /boot/device.hints.

+ +

The USER_LDT kernel option is + now activated by default.

+ +

The + uvisor(4) driver for + connecting Handspring Visors via USB has been added. + [MERGED]

+ +

A VESA S3 linear framebuffer driver has been + added.

+ +

The kernel crashdump infrastructure has been revised, + to support new platforms and in general clean up the + logic in the code. One implication of this change is that + the on-disk format for kernel dumps has changed, and is + now byte-order-agnostic.

+ +

Extremely large swap areas (>67 GB) no longer panic + the system.

+ +

Linker sets are now self-contained; gensetdefs(8) is + unnecessary and has been removed.

+ +

It is now possible to hardwire kernel environment + variables (such as tuneables) at compile-time using + config(8)'s ENV directive.

+ +

Idle zeroing of pages can be enabled with the vm.idlezero_enable sysctl + variable.

+ +

The FreeBSD kernel scheduler now supports + Kernel-Scheduled Entities (KSEs), which provides support + for multiple threads of execution per process similar to + Scheduler Activations. At this point, the kernel has most + of the changes needed to support threading. The kernel + scheduler can schedule multiple threads per process, but + only on a single CPU at a time. More information can be + found in + kse(2).

+ +

+

+
Note: KSE is a work in progress.
+

+

+
+
+ +

The kernel now has support for multiple low-level + console devices. The new + conscontrol(8) utility + helps to manage the different consoles.

+ +

The kernel memory allocator is now a slab memory + allocator, similar to that used in Solaris. This is a + SMP-safe memory allocator that has near-linear + performance as the number of CPUs increases. It also + allows for reduced memory fragmentation.

+ +

+

+ +

2.1.1 + Processor/Motherboard Support

+ +

SMP support has been largely reworked, incorporating + code from BSD/OS 5.0. One of the main features of SMPng + (``SMP Next Generation'') 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.

+ +

Support for the 80386 processor has been removed + from the GENERIC kernel, as + this code seriously pessimizes performance on other + IA32 processors. The I386_CPU + 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. 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 I386_CPU.

+ +

The CPU_DISABLE_CMPXCHG + kernel configuration option has been added. Enabling + this option has been shown to dramatically improve + performance on VMWare client OS installs.

+ +

+

+
Note: This option is not compatible with + SMP kernels.
+

+

+
+
+

+ +

+

+ +

2.1.2 Bootloader + Changes

+ +

The kernel and modules have been moved to the + directory /boot/kernel, so + they can be easily manipulated together. The boot + loader has been updated to make this change as seamless + as possible.

+

+ +

+

+ +

2.1.3 Network + Interface Support

+ +

The + dc(4) driver now + supports NICs based on the Xircom 3201 and Conexant + LANfinity RS7112 chips.

+ +

The + rp(4) driver has been + updated to version 3.02 and can now be built as a + module. [MERGED]

+ +

The + stf(4) device is now + clonable.

+ +

The + tx(4) driver now + supports true multicast filtering.

+ +

Network devices now automatically appear as special + files in /dev/net. Interface + hardware ioctls (not protocol or routing) can be + performed on these devices. The SIOCGIFCONF ioctl may be performed on + the special /dev/network + node.

+ +

``Zero copy'' support has been added to the + networking stack. This feature can eliminate a copy of + network data between the kernel and userland, which is + one of the more significant bottlenecks in network + throughput. The send-side code should work with almost + any network adapter, while the receive-side code + requires a network adapter with an MTU of at least one + memory page size (for example, jumbo frames on Gigabit + Ethernet). For more information, see + zero_copy(9).

+

+ +

+

+ +

2.1.4 Network + Protocols

+ +

A FAST_IPSEC kernel option + now allows the IPsec implementation to use the kernel + crypo framework, along with its support for hardware + cryptographic acceleration.

+ +

+

+
Note: The FAST_IPSEC and IPSEC options are mutually + exclusive.
+

+

+ +

+

+
Note: The FAST_IPSEC option is, at the moment, + not compatible with IPv6 or the INET6 option.
+

+

+
+
+ +

A + gre(4) driver, which + can encapsulate IP packets using GRE (RFC 1701) or + minimal IP encapsulation for Mobile IP (RFC 2004), has + been added.

+ +

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.

+ +

IP multicast now works on VLAN devices. Several + other bugs in the VLAN code have also been fixed.

+ +

+ ipfw(4) has been + re-implemented (the new version is commonly referred to + as ``IPFW2''). It now uses variable-sized + representation of rules in the kernel, similar to + bpf(4) instructions. + Most of the externally-visible behavior (i.e. through + + ipfw(8)) should be + unchanged., although + ipfw(8) now supports + or connectives between match + fields. [MERGED]

+ +

A new + ng_device(4) netgraph + node type has been added, which creates a device entry + in /dev, to be used as the + entry point to a networking graph.

+ +

The + ng_gif(4) and + ng_gif_demux(4) + netgraph nodes, for operating on + gif(4) devices, have + been added.

+ +

The + ng_ip_input(4) + netgraph node, for queueing IP packets into the main IP + input processing code, has been added.

+ +

A new + ng_l2tp(4) netgraph + node type, which implements the encapsulation layer of + the L2TP protocol as described in RFC 2661, has been + added. [MERGED]

+ +

A new ng_split node type has been added for + splitting a bidirectional packet flow into two + unidirectional flows.

+ +

The ephemeral port range used for TCP and UDP has + been changed to 49152-65535 (the old default was + 1024-5000). This increases the number of concurrent + outgoing connections/streams.

+ +

The + tcp(4) protocol's + retransmission timer can now be manipulated with two + sysctl variables, net.inet.tcp.rexmit_min and net.inet.tcp.rexmit_slop. The default + has been reduced from one second to 200ms (similar to + the Linux default) in order to better handle hicups + over interactive connections and improve recovery over + lossy fast connections such as wireless links.

+ +

The + tcp(4) protocol now + has the ability to dynamically limit the send-side + window to maximize bandwidth and minimize round trip + times. The feature can be enabled via the net.inet.tcp.inflight_enable sysctl. + [MERGED]

+

+ +

+

+ +

2.1.5 Disks and + Storage

+ +

The + ata(4) driver (along + with + burncd(8)) now + supports writing to media in DVD+RW drives.

+ +

The + ata(4) driver now + supports accessing ATA devices as SCSI devices via the + CAM layer and drivers ( + cd(4), + da(4), + st(4), and + pass(4)). This + feature requires device + atapicam in the kernel configuration. More + information can be found in + atapicam(4). + [MERGED]

+ +

The + ata(4) driver now has + support for the Sil 0680 and VIA 8233/8235 controllers. + [MERGED]

+ +

The + cd(4) driver now + supports the same CDRIOCREADSPEED and CDRIOCWRITESPEED ioctls that the + acd(4) driver uses + for setting the speed of CDROM access.

+ +

The + fdc(4) floppy disk + has undergone a number of enhancements. Density + selection for common settings is now automatic; the + driver is also much more flexible in setting the + densities of various subdevices.

+ +

The + geom(4) disk I/O + request transformation framework has been added; this + extensible framework is designed to support a wide + variety of operations on I/O requests on their way from + the upper kernel to the device drivers.

+ +

+

+
Note: GEOM-enabled kernels no longer + support ``compatability slices''. This feature + (supported on the i386 and pc98 only) allowed a + user to refer to a disk partition without + specifying an MBR slice (e.g. /dev/ad0a); the kernel would + automatically find the first applicable FreeBSD + slice and use it. On GEOM kernels, only the full + partition names (e.g. /dev/ad0s1a) are allowed when + referring to partitions within MBR slices. This + change should affect very few users.
+

+

+
+
+ +

A GEOM Based Disk Encryption module has been added. + It provides denial of access to ``cold disks'', with + four different cryptographic barriers and up to four + changeable pass-phrases. Much more information can be + found in the + gbde(4) manual page. + The + gbde(8) userland + utility provides an operation and management interface + to this module. This feature is not enabled by default; + it requires options GEOM_BDE + to be added to a kernel configuration file.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

The + isp(4) driver is now + proactive about discovering Fibre Channel topology + changes.

+ +

The + isp(4) driver now + supports target mode for Qlogic SCSI cards, including + Ultra2 and Ultra3 and dual bus cards.

+ +

The + matcd(4) driver has + been removed due to breakage and licensing issues. + [MERGED]

+ +

+ md(4), the memory + disk device, has had the functionality of + vn(4) incorporated + into it. + md(4) devices can now + be configured by + mdconfig(8). + vn(4) has been + removed. The Memory Filesystem (MFS) has also been + removed.

+ +

The mpt driver, for supporting the LSI Logic + Fusion/MP architecture Fiber Channel controllers, has + been added. [MERGED]

+ +

The RAIDframe disk driver has been imported from + NetBSD. This driver provides software-based RAID 0, 1, + 4, and 5 capabilities, as well as other functionality. + More information can be found in the + raid(4) driver manual + page. The + raidctl(8) utility is + used to configure and unconfigure disk arrays. This + feature is not enabled by default, and requires device raidframe to be configured + into a kernel.

+ +

+

+
Note: This feature should be considered + experimental.
+

+

+
+
+ +

Some problems in + sa(4) error handling + have been fixed, including the ``tape drive spinning + indefinitely upon + mt(1) stat'' problem.

+ +

The SCSI_DELAY + configuration parameter can now be set at boot time and + runtime via the kern.cam.scsi_delay tunable/sysctl.

+ +

The trm driver has been added to support SCSI + adapters using the Tekram TRM-S1040 SCSI chipset.

+

+ +

+

+ +

2.1.6 + Filesystems

+ +

Support for named extended attributes was added to + the FreeBSD 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 /usr/src/sys/ufs/ufs/README.extattr for + details).

+ +

A filesystem snapshot capability has been added to + FFS. Details can be found in /usr/src/sys/ufs/ffs/README.snapshot.

+ +

Softupdates for FFS have received some bug fixes and + enhancements.

+ +

When running with softupdates, + statfs(2) and + df(1) will track the + number of blocks and files that are committed to being + freed.

+ +

+ kernfs(5) is obsolete + and has been retired.

+ +

Client-side NFS locks have been implemented.

+ +

The client-side and server-side of the NFS code in + the kernel used to be intertwined in various complex + ways. They have been split apart for ease of + maintenance and further development.

+ +

Support for filesystem 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 /usr/src/sys/ufs/ufs/README.acls.

+ +

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. Compatibility ``glue'' has + been added to + mount(8) so that msdos filesystem entries in + fstab(5) will work + without changes.

+ +

pseudofs, a pseudo-filesystem framework, has been + added. + linprocfs(5) and + procfs(5) have been + modified to use pseudofs.

+ +

Network filesystems (such as NFS and smbfs + filesystems) listed in /etc/fstab can now be properly mounted + during startup initialization; their mounts are + deferred until after the network is initialized.

+ +

Read-only support for the Universal Disk Format + (UDF) has been added. This format is used on + packet-written CD-RWs and most commercial DVD-Video + disks. The + mount_udf(8) command + can be used to mount these disks.

+ +

Basic support has been added for the UFS2 + filesystem. Among its features:

+ +

+
The inode has been expanded to 256 bytes to make + space for 64-bit block pointers.
+
+
A file-creation time field has been added.
+
+
A native extended attributes implementation has + been added, permitting total attribute size stored + on an inode to be up to twice the filesystem block + size. This storage is used for Access Control Lists + and MAC labels, but may also be used by other + system extensions and user applications.
+

+
+
+

+ +

+

+ +

2.1.7 PCCARD + Support

+ +

+

+ +

+

+ +

2.1.8 Multimedia + Support

+ +

A new API has been added for sound cards with + hardware volume control.

+

+ +

+

+ +

2.1.9 Contributed + Software

+ +

The Forth Inspired Command Language (FICL) used in the boot loader has + been updated to 3.02.

+ +

Support for Advanced Configuration and Power + Interface (ACPI), a multi-vendor standard for + configuration and power management, has been added. + This functionality has been provided by the Intel ACPI Component Architecture + project, as of the ACPI CA 20020815 snapshot. Some + backward compatability for applications using the older + APM standard has been provided.

+ +

+

+ +

2.1.9.1 + IPFilter

+ +

IPFilter has been + updated to 3.4.29. [MERGED]

+

+ +

+

+ +

2.1.9.3 + KAME

+

+ +

+

+ +

2.2 Security-Related + Changes

+ +

A bug in which malformed ELF executable images can + hang the system has been fixed (see security advisory + FreeBSD-SA-00:41). [MERGED]

+ +

A security hole in Linux emulation was fixed (see + security advisory FreeBSD-SA-00:42). [MERGED]

+ +

TCP now uses stronger randomness in choosing its + initial sequence numbers (see security advisory + FreeBSD-SA-00:52). [MERGED]

+ +

Several buffer overflows in + tcpdump(1) were + corrected (see security advisory FreeBSD-SA-00:61). + [MERGED]

+ +

A security hole in + top(1) was corrected + (see security advisory FreeBSD-SA-00:62). [MERGED]

+ +

A potential security hole caused by an + off-by-one-error in + gethostbyname(3) has + been fixed (see security advisory FreeBSD-SA-00:63). + [MERGED]

+ +

A potential buffer overflow in the + ncurses(3) library, + which could cause arbitrary code to be run from within + systat(1), has been + corrected (see security advisory FreeBSD-SA-00:68). + [MERGED]

+ +

A vulnerability in + telnetd(8) that could + cause it to consume large amounts of server resources has + been fixed (see security advisory FreeBSD-SA-00:69). + [MERGED]

+ +

The nat deny_incoming command + in + ppp(8) now works + correctly (see security advisory FreeBSD-SA-00:70). + [MERGED]

+ +

A vulnerability in + csh(1)/ + tcsh(1) temporary files + that could allow overwriting of arbitrary user-writable + files has been closed (see security advisory + FreeBSD-SA-00:76). [MERGED]

+ +

Several vulnerabilities in + procfs(5) were fixed + (see security advisory FreeBSD-SA-00:77). [MERGED]

+ +

A bug in OpenSSH in which a + server was unable to disable + ssh-agent(1) or X11Forwarding was fixed (see + security advisory FreeBSD-SA-01:01). [MERGED]

+ +

A bug in + ipfw(8) and + ip6fw(8) in which + inbound TCP segments could incorrectly be treated as + being part of an established + connection has been fixed (see security advisory + FreeBSD-SA-01:08). [MERGED]

+ +

A bug in + crontab(1) that could + allow users to read any file on the system in valid + crontab(5) syntax has + been fixed (see security advisory FreeBSD-SA-01:09). + [MERGED]

+ +

A vulnerability in + inetd(8) that could + allow read-access to the initial 16 bytes of wheel-accessible files has been fixed + (see security advisory FreeBSD-SA-01:11). [MERGED]

+ +

A bug in + periodic(8) that used + insecure temporary files has been corrected (see security + advisory FreeBSD-SA-01:12). [MERGED]

+ +

OpenSSH 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]

+ +

A bug in + timed(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:28). + [MERGED]

+ +

A bug in + rwhod(8), which caused + it to crash if send certain malformed packets, has been + corrected (see security advisory FreeBSD-SA-01:29). + [MERGED]

+ +

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]

+ +

A remotely-exploitable vulnerability in + ntpd(8) has been closed + (see security advisory FreeBSD-SA-01:31). [MERGED]

+ +

A security hole in IPFilter's fragment cache has been + closed (see security advisory FreeBSD-SA-01:32). + [MERGED]

+ +

Buffer overflows in + 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, + glob(3) allows + specification of a limit on the number of pathname + matches it will return. + ftpd(8) now uses this + feature (see security advisory FreeBSD-SA-01:33). + [MERGED]

+ +

Initial sequence numbers in TCP are more thoroughly + randomized (see security advisory FreeBSD-SA-01:39). Due + to some possible compatibility issues, the behavior of + this security fix can be enabled or disabled via the net.inet.tcp.tcp_seq_genscheme + sysctl variable.[MERGED]

+ +

A vulnerability in the + 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]

+ +

A flaw allowed some signal handlers to remain in + effect in a child process after being exec-ed from its + parent. This allowed an attacker to execute arbitrary + code in the context of a setuid binary. This flaw has + been corrected (see security advisory FreeBSD-SA-01:42). + [MERGED]

+ +

A remote buffer overflow in + tcpdump(1) has been + fixed (see security advisory FreeBSD-SA-01:48). + [MERGED]

+ +

A remote buffer overflow in + telnetd(8) has been + fixed (see security advisory FreeBSD-SA-01:49). + [MERGED]

+ +

The new net.inet.ip.maxfragpackets and net.inet.ip6.maxfragpackets sysctl + variables limit the amount of memory that can be consumed + by IPv4 and IPv6 packet fragments, which defends against + some denial of service attacks (see security advisory + FreeBSD-SA-01:52). [MERGED]

+ +

A flaw in the implementation of the + ipfw(8) me rules on point-to-point links has been + corrected. Formerly, me filter + rules would match the remote IP address of a + point-to-point interface in addition to the intended + local IP address (see security advisory + FreeBSD-SA-01:53). [MERGED]

+ +

A vulnerability in + procfs(5), which could + allow a process to read sensitive information from + another process's memory space, has been closed (see + security advisory FreeBSD-SA-01:55). [MERGED]

+ +

The PARANOID hostname + checking in tcp_wrappers now + works as advertised (see security advisory + FreeBSD-SA-01:56). [MERGED]

+ +

A local root exploit in + sendmail(8) has been + closed (see security advisory FreeBSD-SA-01:57). + [MERGED]

+ +

A remote root vulnerability in + lpd(8) has been closed + (see security advisory FreeBSD-SA-01:58). [MERGED]

+ +

A race condition in + rmuser(8) that briefly + exposed a world-readable /etc/master.passwd has been fixed (see + security advisory FreeBSD-SA-01:59). [MERGED]

+ +

A vulnerability in UUCP has + been closed (see security advisory FreeBSD-SA-01:62). All + non-root-owned binaries in + standard system paths now have the schg flag set to prevent exploit vectors + when run by + cron(8), by root, or by a user other then the one + owning the binary. In addition, + uustat(1) is now run + via /etc/periodic/daily/410.status-uucp as + uucp, not root. In FreeBSD -CURRENT, UUCP has since been moved to the Ports + Collection and no longer a part of the base system. + [MERGED]

+ +

A security hole in OpenSSH, + which could allow users to execute code with arbitrary + privileges if UseLogin yes was + set, has been closed. Note that the default value of this + setting is UseLogin no. (See + security advisory FreeBSD-SA-01:63.) [MERGED]

+ +

The use of an insecure temporary directory by + pkg_add(1) could permit + a local attacker to modify the contents of binary + packages while they were being installed. This hole has + been closed. (See security advisory FreeBSD-SA-02:01.) + [MERGED]

+ +

A race condition in + pw(8), which could + expose the contents of /etc/master.passwd, has been eliminated. + (See security advisory FreeBSD-SA-02:02.) [MERGED]

+ +

A bug in + k5su(8) could have + allowed a process that had given up superuser privileges + to regain them. This bug has been fixed. (See security + advisory FreeBSD-SA-02:07.) [MERGED]

+ +

An ``off-by-one'' bug has been fixed in OpenSSH's multiplexing code. This bug + could have allowed an authenticated remote user to cause + + sshd(8) to execute + arbitrary code with superuser privileges, or allowed a + malicious SSH server to execute arbitrary code on the + client system with the privileges of the client user. + (See security advisory FreeBSD-SA-02:13.) [MERGED]

+ +

A programming error in zlib + could result in attempts to free memory multiple times. + The + malloc(3)/ + free(3) routines used + in FreeBSD are not vulnerable to this error, but + applications receiving specially-crafted blocks of + invalid compressed data could be made to function + incorrectly or abort. This zlib bug has been fixed. For a + workaround and solutions, see security advisory FreeBSD-SA-02:18. [MERGED]

+ +

Bugs in the TCP SYN cache (``syncache'') and SYN + cookie (``syncookie'') implementations, which could cause + legitimate TCP/IP traffic to crash a machine, have been + fixed. For a workaround and patches, see security + advisory FreeBSD-SA-02:20. [MERGED]

+ +

A routing table memory leak, which could allow a + remote attacker to exhaust the memory of a target + machine, has been fixed. A workaround and patches can be + found in security advisory FreeBSD-SA-02:21. [MERGED]

+ +

A bug with memory-mapped I/O, which could cause a + system crash, has been fixed. For more information about + a solution, see security advisory FreeBSD-SA-02:22. [MERGED]

+ +

A security hole, in which SUID programs could be made + to read from or write to inappropriate files through + manipulation of their standard I/O file descriptors, has + been fixed. Information regarding a solution can be found + in security advisory FreeBSD-SA-02:23. [MERGED]

+ +

Some unexpected behavior could be allowed with + k5su(8) because it does + not require that an invoking user be a member of the wheel group when attempting to + become the superuser (this is the case with + su(1)). To avoid this + situation, + k5su(8) is now + installed non-SUID by default (effectively disabling it). + More information can be found in security advisory FreeBSD-SA-02:24. [MERGED]

+ +

Multiple vulnerabilities were found in the + bzip2(1) utility, which + could allow files to be overwritten without warning or + allow local users unintended access to files. These + problems have been corrected with a new import of bzip2. For more information, see + security advisory FreeBSD-SA-02:25. [MERGED]

+ +

A bug has been fixed in the implementation of the TCP + SYN cache (``syncache''), which could allow a remote + attacker to deny access to a service when accept filters + (see + accept_filter(9)) were + in use. This bug has been fixed; for more information, + see security advisory FreeBSD-SA-02:26. [MERGED]

+ +

Due to a bug in + rc(8)'s use of shell + globbing, users may be able to remove the contents of + arbitrary files if /tmp/.X11-unix does not exist and the + system can be made to reboot. This bug has been corrected + (see security advisory FreeBSD-SA-02:27). [MERGED]

+ +

A buffer overflow in the resolver, which could be + exploited by a malicious domain name server or an + attacker forging DNS messages, has been fixed. See + security advisory FreeBSD-SA-02:28 for more details. + [MERGED]

+ +

A buffer overflow in + tcpdump(1), which could + be triggered by badly-formed NFS packets, has been fixed. + See security advisory FreeBSD-SA-02:29 for more details. + [MERGED]

+ +

+ ktrace(1) can no longer + trace the operation of formerly privileged processes; + this prevents the leakage of sensitive information that + the process could have obtained before abandoning its + privileges. For a discussion of this issue, see security + advisory FreeBSD-SA-02:30 for more details. + [MERGED]

+ +

A race condition in + pppd(8), which could be + used to change the permissions of an arbitrary file, has + been corrected. For more information, see security + advisory FreeBSD-SA-02:32. [MERGED]

+ +

Multiple buffer overflows in OpenSSL have been corrected, by way of + an upgrade to the base system version of OpenSSL. More details can be found in + security advisory FreeBSD-SA-02:33. [MERGED]

+ +

A heap buffer overflow in the XDR decoder has been + fixed. For more details, see security advisory FreeBSD-SA-02:34. [MERGED]

+ +

A bug that could allow local users to read and write + arbitrary blocks on an FFS filesystem has been corrected. + More details can be found in security advisory FreeBSD-SA-02:35. [MERGED]

+ +

A bug in the NFS server code, which could allow a + remote denial of service attack, has been fixed. Security + advisory FreeBSD-SA-02:36 has more details. + [MERGED]

+ +

A bug that could allow local users to panic a system + using the + kqueue(2) mechanism has + been fixed. More information is contained in security + advisory FreeBSD-SA-02:37. [MERGED]

+ +

Several bounds-checking bugs in system calls, which + could result in some system calls returning a large + portion of kernel memory, have been fixed. More + information can be found in security advisory FreeBSD-SA-02:38. [MERGED]

+ +

A bug that could allow applications using libkvm to leak sensitive file descriptors + has been corrected. (See security advisory FreeBSD-SA-02:39 for more details.) + [MERGED]

+ +

Buffer overflows in kadmind(8) and k5admin have been + corrected. More details can be found in security advisory + FreeBSD-SA-02:40. [MERGED]

+ +

Errors in + smrsh(8), which could + allow users to circumvent restrictions on what programs + can be executed, have been fixed. See FreeBSD-SA-02:41 for details. + [MERGED]

+ +

Buffer overflows in the DNS + resolver(3), which + could cause some applications to fail, have been + corrected. More details are in FreeBSD-SA-02:42. [MERGED]

+ +

Multiple vulnerabilities in BIND have been fixed, as described in + FreeBSD-SA-02:43. [MERGED]

+

+ +

+

+ +

2.3 Userland + Changes

+ +

Support for + a.out(5) format + executables in the compiler toolchain has been largely + removed.

+ +

+

+
Note: This is a work in progress. + Eventually, + a.out(5) support + will resurface in a series of ports/packages.
+

+

+
+
+ +

+ arp(8) now prints [fddi] or [atm] tags for addresses on interfaces of + those types.

+ +

The + asa(1) utility, to + interpret FORTRAN carriage-control characters, has been + added.

+ +

+ at(1) now supports the + -r command-line option to remove + jobs and the -t option to specify + times in POSIX time format.

+ +

The system + awk(1) now refers to BWK awk.

+ +

+ basename(1) now accept + -a and -s + flags, which allow it to perform the + basename(3) function on + multiple files.

+ +

+ biff(1) now accepts a + b argument to enable ``bell + notification'' of new mail (which does not disturb the + terminal contents as biff y + would). [MERGED]

+ +

+ biff(1) now uses the + first terminal associated with the standard input, + standard output or standard error file descriptor, in + that order. Thus, it is possible to use the redirection + facilities of a shell (biff n < + /dev/ttyp1) to toggle the notification for other + terminals.

+ +

+ burncd(8) now supports + Disk At Once (DAO) mode, selectable via the -d flag. [MERGED]

+ +

+ burncd(8) now has the + ability to write VCDs/SVCDs. [MERGED]

+ +

+ burncd(8) now accepts a + value of max for its -s option to set the drive's maximum write + speed.

+ +

+ bzgrep(1), + bzegrep(1), and + bzfgrep(1) have been + added to perform + grep(1)-type operations + on + bzip2(1)-compressed + files.

+ +

+ calendar(1) now takes a + -W option, which operates similar + to -A but without special + treatment at weekends, and a -Foption to change the notion of + ``Friday''.

+ +

+ catman(1) is now a C + program, instead of a Perl script.

+ +

+ cdcontrol(1) now + supports a speed command to set + the maximum speed to be used by the drive (the maximum + possible speed can be selected setting the speed to max).

+ +

A + check_utility_compat(3) + library function has been added to libc, to determine whether certain + FreeBSD base system utilities should behave in FreeBSD + 4-compatible mode or in a ``standard'' mode (default + standard). The configuration is done + malloc(3)-style, with + either an environment variable or a symbolic link.

+ +

+ chflags(1) has moved + from /usr/bin to /bin.

+ +

+ chmod(1) now supports a + -h for changing the mode of a + symbolic link.

+ +

+ chmod(1) now also, when + the mode is modified, prints the old and new modes if the + -v option is specified more than + once.

+ +

+ chown(8) no longer + takes . as a user/group + delimeter. This change was made to support usernames + containing a ..

+ +

Use of the CSMG_* macros no + longer require inclusion of <sys/param.h>

+ +

A compat4x distribution has + been added for compatibility with FreeBSD 4-STABLE.

+ +

+ cp(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A new + csplit(1) utility, + which splits files based on context, has been added.

+ +

+ ctags(1) now creates + tags for typedefs, structs, unions, and enums by default + (implying the -t option). The new + -T reverts to the old + behavior.

+ +

The + daemon(8) program, a + command-line interface to + daemon(3), has been + added. It detaches itself from its controlling terminal + and executes a program specified on the command line. + This allows the user to run an arbitrary program as if it + were written to be a daemon. [MERGED]

+ +

The + devd(8) utility, a + userland daemon that can run arbitrary commands when + devices come and go in the device tree, has been added. + This program is a generalization of some of the + functionality of + pccardd(8).

+ +

+

+
Note: + devd(8) is + work-in-progress.
+

+

+
+
+ +

+ devinfo(8), a simple + tool to print the device tree and resource usage by + devices, has been added.

+ +

diskpart(8) has been declared obsolete, and has been + removed.

+ +

+ dump(8) now supports a + new -S flag to allow it to just + print out the dump size estimates and exit. [MERGED]

+ +

+ expr(1) is now + compliant with POSIX.2-1992 (and thus also with + POSIX.1-2001). Some program depend on the old, historic + behavior and do not properly protect their arguments to + keep them from being misinterpreted as command-line + options. (the + devel/libtool port/package, + used by many GNU programs, is a notable example). The old + behavior can be requested by enabling compatibility mode + for + expr(1) as described in + + check_utility_compat(3).

+ +

+ fbtab(5) now accepts + glob matching patterns for target devices, not just + individual devices and directories.

+ +

+ fdisk(8) no longer + attempts to search for a device if none has been + specified on the command line, but instead tries to + figure out the default device name from the root + device.

+ +

+ fdread(1), a program to + read data from floppy disks, has been added. It is a + counterpart to + 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 + dd(1).

+ +

+ finger(1) now has + support for a .pubkey file. + [MERGED]

+ +

+ finger(1) now supports + a -g flag to restrict the + printing of GECOS information to the user's full name + only. [MERGED]

+ +

+ finger(1) now supports + the -4 and -6 flags to specify an address family for + remote queries. [MERGED]

+ +

+ fold(1) now supports a + -b flag to break at byte + positions and a -s flag to break + at word boundaries. [MERGED]

+ +

+ fsck(8) wrappers have + been imported; this feature provides infrastructure for + + fsck(8) to work on + different types of filesystems (analogous to + mount(8)).

+ +

The behavior of + fsck(8) when dealing + with various passes (a la /etc/fstab) has been modified to + accommodate multiple-disk filesystems.

+ +

+ fsck(8) now has support + for foreground (-F) and + background (-B) checks. + Traditionally, + fsck(8) is invoked + before the filesystems are mounted and all checks are + done to completion at that time. If background checking + is available, + fsck(8) is invoked + twice. It is first invoked at the traditional time, + before the filesystems are mounted, with the -F 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 -B 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 background_fsck option in + rc.conf(5).

+ +

+ fsck_ffs(8) now + supports background filesystem checks to mounted FFS + filesystems with the -B option + (softupdates must be enabled on these filesystems). The + -F flag now determines whether a + specified filesystem needs foreground checking.

+ +

+ ftpd(8) now supports + the -m option to permit guest + users to modify existing files if allowed by filesystem + permissions. In particular, this enables guest users to + resume uploads. [MERGED]

+ +

+ ftpd(8) now supports + the -M option to prevent guest + users from creating directories. [MERGED]

+ +

+ ftpd(8) now supports + -o and -O + options to disable the RETR + command; the former for everybody, and the latter only + for guest users. Coupled with -A + and appropriate file permissions, these can be used to + create a relatively safe anonymous FTP drop box for + others to upload to. [MERGED]

+ +

+ ftpd(8) now supports + the -W option to disable logging + FTP sessions to + wtmp(5). [MERGED]

+ +

The + getconf(1) utility has + been added. It prints the values of POSIX or X/Open path + or system configuration variables. [MERGED]

+ +

gifconfig(8) is obsolete and has been removed. Its + functionality is now handled by the tunnel and deletetunnel commands of + ifconfig(8).

+ +

+ gprof(1) now has a -K option to enable dynamic symbol + resolution from the currently-running kernel. With this + change, properly-compiled KLD modules are now able to be + profiled.

+ +

The ibcs(8), linux(8), osf1(8), and 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.

+ +

+ ifconfig(8) now has the + ability to set promiscuous mode on an interface, via the + new promisc flag. [MERGED]

+ +

+ ifconfig(8) now + supports a monitor interface + flag, which blocks transmission of packets on that + interface. This feature is useful for monitoring network + traffic without interacting with the network in + question.

+ +

By default, + inetd(8) is no longer + run by + rc(8) at boot-time, + although + sysinstall(8) gives the + option of enabling it during binary installations. + inetd(8) can also be + enabled by adding the following line to /etc/rc.conf:

+

+    inetd_enable="YES"
+

+ +

+ inetd(8) now has the + capability for limiting the maximum number of + simultaneous invocations of each service from a single IP + address. [MERGED]

+ +

+ ipfw(8) filter rules + can now match on the value of the IPv4 precedence + field.

+ +

+ kbdmap(1) and + vidfont(1) have been + converted from Perl to C.

+ +

+ kenv(1) now has the + ability to set or delete kernel environment + variables.

+ +

The kget(8) utility has been removed (it was only + useful for UserConfig, which is not present in FreeBSD + 5.0-DP2).

+ +

+ killall(1) no longer + tries to kill zombie processes unless the -z flag is specified.

+ +

+ ktrdump(8), a utility + to dump the ktr trace buffer from userland, has been + added.

+ +

+ ldd(1) now supports a + -a flag to list all the objects + that are needed by each loaded object.

+ +

libc is now thread-safe by + default; libc_r contains only + thread functions.

+ +

libstand now has support for + overwriting the contents of a file on a UFS filesystem + (it cannot expand or truncate files because the + filesystem may be dirty or inconsistent).

+ +

libgmp has been superceded + by libmp.

+ +

The functions from libposix1e have been integrated into libc.

+ +

+ lock(1) now accepts a + -v to disable switching VTYs + while the current terminal is locked. This permits + locking the entire console from a single terminal. + [MERGED]

+ +

+ lpc(8) has been + improved; lpc clean is now + somewhat safer, and a new lpc + tclean command has been added to check to see what + files would be removed by lpc + clean. lpc topq has been + reimplemented, and now allows for a much more flexible + specification of which jobs should be moved (such as a + range of job numbers, or a hostname). An lpc bottomq command has been added to move + jobs to the bottom of a print queue, and a new lpc setstatus command can be used to set a + printer's status message. [MERGED]

+ +

The + ls(1) program now + supports a -m flag to list files + across a page, a -p flag to force + printing of a / after + directories, and a -x flag to + sort filenames across a page. [MERGED]

+ +

+ makewhatis(1) is now a + C program, instead of a Perl script.

+ +

+ man(1) is no longer + installed SUID man, in order to + reduce vulnerabilities associated with generating + ``catpages'' (preformatted manual pages cached for + repeated viewing). As a result, + man(1) can no longer + create system catpages on a regular user's behalf. It is + still able to do so if the user has write permissions to + the directory holding catpages (e.g. a user's own + manpages) or if the running user is root.

+ +

The + mdmfs(8) command has + been added; it is a wrapper around + mdconfig(8), + disklabel(8), + newfs(8), and + mount(8) that mimics + the command line option set of the deprecated + mount_mfs(8).

+ +

+ mesg(1) now conforms to + SUSv3. Among other things, it now uses the first terminal + associated with the standard input, standard output or + standard error file descriptor, in that order. Thus, it + is possible to use the redirection facilities of a shell + (mesg n < /dev/ttyp1) to + control write access for other terminals.

+ +

+ mountd(8) and + nfsd(8) have moved from + /sbin to /usr/sbin.

+ +

+ mv(1) now takes a + (nonstandard) -n option to + automatically answer ``no'' when it would ask to + overwrite a file. [MERGED]

+ +

A number of archaic features of + newfs(8) have been + removed; these implement tuning features that are + essentially useless on modern hard disks. These features + were controlled by the -O, -d, -k, -l, -n, -p, -r, -t, and -x + flags.

+ +

+ newfs(8) now supports a + -O flag to select the creation of + UFS1 or UFS2 filesystems.

+ +

The + newgrp(1) utility to + change to a new group has been added.

+ +

+ newsyslog(8) now + compresses log files using + bzip2(1) by default. + (The former behavior of using + gzip(1) can be + specified in /etc/newsyslog.conf.)

+ +

The + nextboot(8) utility has + been added to specify an alternate kernel and/or boot + flags to be used the next time the machine is booted. A + previous incarnation of this feature first appeared in + FreeBSD 2.2.

+ +

NFS now works over + IPv6.

+ +

+ nice(1) now uses the + -n option to specify the + ``niceness'' of the utility being run. [MERGED]

+ +

nsswitch support has been + merged from NetBSD. By creating an + nsswitch.conf(5) file, + FreeBSD can be configured so that various databases such + as + passwd(5) and + group(5) can be looked + up using flat files, NIS, or Hesiod. If /etc/nsswitch.conf does not exist, it + will be automatically generated from an existing /etc/hosts.conf at system startup + time. The /etc/hosts.conf file + may be used by old executables; it will be automatically + generated from an existing /etc/nsswitch.conf during system startup + if it exists.

+ +

+ od(1) now supports the + -A option to specify the input + address base, the -N option to + specify the number of bytes to dump, the -j option to specify the number of bytes to + skip, the -s option to output + signed decimal shorts, and the -t + option to specify output type. [MERGED]

+ +

PAM support has been added + for account management and sessions.

+ +

PAM configuration is now + specified by files in /etc/pam.d/, rather than a single /etc/pam.conf file. /etc/pam.d/README has more details.

+ +

A + pam_echo(8) echo + service module has been added.

+ +

A + pam_exec(8) program + execution service module has been added.

+ +

A + pam_ftp(8) module has + been added to allow authentication of anonymous FTP + users.

+ +

A + pam_ftpusers(8) module + has been added to perform checks against the + ftpusers(5) file.

+ +

A + pam_ksu(8) module has + been added to do Kerberos 5 authentication and $HOME/.k5login authorization for + su(1).

+ +

A + pam_lastlog(8) module + has been added to record sessions in the + utmp(5), + wtmp(5), and + lastlog(5) + databases.

+ +

A + pam_login_access(8) + module has been added, to allow checking against /etc/login.access.

+ +

The + pam_nologin(8) module, + which can disallow logins using + nologin(5), has been + added.

+ +

The + pam_opie(8) and + pam_opieaccess(8) + modules have been added to control authentication via + opie(4). [MERGED]

+ +

A + pam_passwdqc(8) module + has been added, to check the quality of passwords + submitted during password changes.

+ +

A + pam_rhosts(8) module + has been added to support + rhosts(5) + authentication.

+ +

The + pam_rootok(8) module, + which can be used to authenticate only the superuser, has + been added.

+ +

A + pam_securetty(8) module + has been added to check the ``security'' of a TTY, as + listed in + ttys(5).

+ +

A + pam_self(8) module, + which allows self-authentication of a user, has been + added.

+ +

A + pam_wheel(8) module has + been added to permit authentication to members of a + group, which defaults to wheel.

+ +

The + pathchk(1) utility, + which checks pathnames for validity or portability + between POSIX systems, has been added. [MERGED]

+ +

+ ping(8) now supports a + -o flag to exit after receiving a + reply.

+ +

prefix(8) is obsolete and has been removed. Its + functionality is provided by the eui64 command to + ifconfig(8).

+ +

The + pselect(3) library + function (introduced by POSIX.1 as a slightly stronger + version of + select(2)) has been + added.

+ +

+ pwd(1) now supports the + -L flag to print the logical + current working directory. [MERGED]

+ +

+ quota(1) now takes a + -l flag to suppress quote checks + on NFS filesystems.

+ +

The pseudo-random number generator implemented by + rand(3) has been + improved to provide less biased results.

+ +

+ rcmd(3) now supports + the use of the RSH environment + variable to specify a program to use other than + rsh(1) for remote + execution. As a result, programs such as + dump(8), can use + ssh(1) for remote + transport.

+ +

+ rdist(1) has been + retired from the base system, but is still available from + FreeBSD Ports Collection as + net/44bsd-rdist.

+ +

The + renice(8) command + implements a -n option, which + specifies an increment to be applied to the priority of a + process. [MERGED]

+ +

+ rpcbind(8) has replaced + + portmap(8).

+ +

+ rpcgen(1) now uses /usr/bin/cpp (as on NetBSD), not + /usr/libexec/cpp.

+ +

+ rpc.lockd(8) has been + imported from NetBSD. This daemon provides support for + servicing client NFS locks.

+ +

+ rtld(1) will now print + the names of all objects that cause each object to be + loaded, if the LD_TRACE_LOADED_OBJECTS_ALL environment + variable is defined.

+ +

+ sed(1) now takes a -i option to enable in-place editing + of files. [MERGED]

+ +

The + setfacl(1) and + getfacl(1) commands + have been added to manage filesystem Access Control + Lists.

+ +

+ sh(1) no longer + implements printf as a built-in + command because it was considered less valuable compared + to the other built-in commands (this functionality is, of + course, still available through the + printf(1) + executable).

+ +

+ sh(1) now supports a + -C option to prevent existing + regular files from being overwritten by output + redirection, and a -u to give an + error if an unset variable is expanded. [MERGED]

+ +

The + sh(1) built-in cd command now supports -L and -P flags to + invoke logical or physical modes of operation, + respectively. Logical mode is the default, but the + default can be changed with the physical + sh(1) option. + [MERGED]

+ +

The + sh(1) built-in jobs command now supports a -s flag to output PIDs only and a -l flag to add PIDs to the output. + [MERGED]

+ +

+ sh(1) now supports a + bind built-in command, which + allows the key bindings for the shell's line editor to be + changed.

+ +

The + sh(1) built-in export and readonly commands now support a -p flag to print their output in + ``portable'' format. [MERGED]

+ +

+ sh(1) no longer accepts + invalid constructs as command & && command, && command, or || command. [MERGED]

+ +

+ spkrtest(8) is now a + sh(1) script, rather + than a Perl script.

+ +

+ split(1) now supports a + -a option to specify the number + of letters to use for the suffix of split files. + [MERGED]

+ +

In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, struct selinfo and related functions + have been moved to <sys/selinfo.h>.

+ +

+ su(1) now uses PAM for authentication.

+ +

+ sysctl(8) now accepts a + -d flag to print the descriptions + of variables.

+ +

The default root partition in + sysinstall(8) is now + 100MB on the i386 and pc98, 120MB on the Alpha.

+ +

+ sysinstall(8) now lives + in /usr/sbin, which simplifies + the installation process. The + sysinstall(8) manpage + is also installed in a more consistent fashion now.

+ +

+ sysinstall(8) no longer + mounts the + procfs(5) filesystem by + default on new installs.

+ +

+ tabs(1), a utility to + set terminal tab stops, has been added.

+ +

The + termcap(5) database now + uses the xterm terminal type + from XFree86. As a result, + xterm(1) now supports + color by default and the common workaround of setting TERM to xterm-color is no longer necessary. Use of + the xterm-color terminal type + may result in (benign) warnings from applications.

+ +

+ tftpd(8) now supports + RFC 2349 (TFTP Timeout Interval and Transfer Size + Options); this feature is required by some firmware like + EFI boot managers (at least on HP i2000 Itanium servers) + in order to boot an image using TFTP.

+ +

A version of Transport Independent RPC (TI-RPC) has been imported.

+ +

+ tip(1) has been updated + from OpenBSD, and has the + ability to act as a + cu(1) substitute.

+ +

+ top(1) will now use the + full width of its tty.

+ +

+ touch(1) now takes a + -h option to operate on a + symbolic link, rather than what the link points to.

+ +

+ tr(1) now has basic + support for equivalence classes for locales that support + them. [MERGED]

+ +

+ tr(1) now supports a + -C flag to complement the set of + characters specified by the first string argument.

+ +

+ tunefs(8) now supports + the -a and -l flags to enable and disable the FS_ACLS and FS_MULTILABEL administrative flags on UFS + file system.

+ +

A + ugidfw(8) utility has + been added to manage the rulesets provided by the mac_bsdextended Mandatory Access + Control policy, similar to + ipfw(8).

+ +

UUCP has been removed from + the base system. It can be found in the Ports Collection, + in + net/freebsd-uucp.

+ +

+ unexpand(1) now + supports a -t to specify tabstops + analogous to + expand(1). [MERGED]

+ +

+ usbdevs(8) now supports + a -d flag to show the device + driver associated with each device.

+ +

The base64 capabilities of + uuencode(1) and + uudecode(1) can now be + automatically enabled by invoking these utilities as + b64encode(1) and + b64decode(1) + respectively. [MERGED]

+ +

Functions to implement and manipulate OSF/DCE + 1.1-compliant UUIDs have been added to libc. More information can be found in + uuid(3).

+ +

The + uuidgen(1) utility has + been added. It uses the new + uuidgen(2) system call + to generate one or more Universally Unique Identifiers + compatible with OSF/DCE 1.1 version 1 UUIDs.

+ +

+ vidcontrol(1) now + accepts a -S to allow the user to + disable VTY switching. [MERGED]

+ +

The default stripe size in + vinum(8) has been + changed from 256KB to 279KB, to spread out superblocks + more evenly between stripes.

+ +

+ wc(1) now supports a + -m flag to count characters, + rather than bytes.

+ +

+ whereis(1), formerly a + Perl script, has been rewritten in C. It now supports a + -x flag to suppress the run of + locate(1), and a -q flag suppresses the leading name + of the query.

+ +

+ whereis(1) now supports + a -a flag to report all matches + instead of only the first of each requested type.

+ +

+ which(1) is now a C + program, rather than a Perl script.

+ +

+ who(1) now has a number + of new options: -H shows column + headings; -T shows + mesg(1) state; -m is an equivalent to am i; -u shows idle + time; -q to list names in + columns. [MERGED]

+ +

+ wicontrol(8) now + supports a -l to list the + stations associated in hostap + mode and a -L to list available + access points.

+ +

+ xargs(1) now supports a + -I replstr option that allows the + user to tell + xargs(1) to insert the + data read from standard input at specific points in the + command line arguments rather than at the end. (A + FreeBSD-specific -J option is + similar.) [MERGED]

+ +

+ xargs(1) now supports a + -L option to force its utility + argument to be called after some number of lines. + [MERGED]

+ +

Various routines in the C library now have support for + ``wide'' characters. Among these are character class + functions such as + wctype(3), wide + character I/O functions such as + getwc(3), formatted I/O + functions such as + wprintf(3) and + wscanf(3). Conversion + functions to + multibyte(3) characters + are also supported.

+ +

A number of utilities and libraries were enhanced to + improve their conformance with the Single UNIX + Specification (SUSv3) and IEEE Std 1003.1-2001 + (``POSIX.1''). Specific features added have been listed + in the release notes for each utility. The standards + conformance of each utility or library function is + generally listed in its manual page.

+ +

A number of games have been removed from the base + system. These include: adventure(6), arithmetic(6), + atc(6), backgammon(6), battlestar(6), bs(6), canfield(6), + cribbage(6), fish(6), hack(6), hangman(6), larn(6), + mille(6), phantasia(6), piano(6), pig(6), quiz(6), + rain(6), robots(6), rogue(6), sail(6), snake(6), trek(6), + wargames(6), worm(6), worms(6), wump(6). dm(8), which was + used to control access to games, is no longer necessary, + and has also been removed. The ``utility-like'' games, as + well as + fortune(6), remain.

+ +

+

+
Note: The affected programs will reappear + as a port in the Ports Collection. This note will + contain a pointer to that port, once it has been + committed.
+

+

+
+
+ +

+

+ +

2.3.1 Contributed + Software

+ +

am-utils has been updated + to 6.0.7.

+ +

A 10 February 2002 snapshot of awk from Bell Labs (variously known + as ``BWK awk'' or ``The One True AWK'') has been + imported. It is available as awk or nawk.

+ +

BIND has been updated to + 8.3.3. [MERGED]

+ +

Binutils has been updated + to a pre-release snapshot of 2.13.1 from 11 October + 2002.

+ +

file has been updated to + 3.39.

+ +

gcc has been updated to a + pre-release snapshot of gcc + 3.2.1, from 9 October 2002.

+ +

+

+
Warning: The C++ ABI from gcc 3.2.X is not compatible with + previous versions.
+

+

+
+
+ +

gdb has been updated to + version 5.2.1.

+ +

gperf has been updated to + 2.7.2.

+ +

groff and its related + utilities have been updated to FSF version 1.18.1.

+ +

Heimdal Kerberos has been + updated to a pre-0.5 snapshot from 16 September + 2002.

+ +

The ISC DHCP client has + been updated to 3.0.1RC9.

+ +

The + more(1) command has + been replaced by + less(1), although it + can still be run as more. + [MERGED] Version 371 of less + has been imported.

+ +

An XML processing library, named libbsdxml, has been added for the + benefit of XML-using utilities in the base system. It + is based almost entirely on an import of expat 1.95.5, but is installed under + a different name to avoid conflicts with any versions + of expat installed from the + Ports Collection.

+ +

libpcap has been updated + to 0.7.1. [MERGED]

+ +

libreadline has been + updated to 4.2.

+ +

libz has been updated to + 1.1.4.

+ +

lint has been updated to + snapshot of NetBSD + lint(1) as of 19 July + 2002.

+ +

lukemftp 1.6 beta 2 (the + FTP client from NetBSD) has replaced the FreeBSD + ftp(1) program. Among + its new features are more automation methods, better + standards compliance, transfer rate throttling, and a + customizable command-line prompt. Some environment + variables and command-line arguments have changed.

+ +

The FTP daemon from NetBSD, otherwise known as lukemftpd 1.2 beta 1, has been + imported and is available as + lukemftpd(8). + [MERGED]

+ +

+ m4(1) has been + imported from OpenBSD, as of 26 April 2002. + [MERGED]

+ +

ncurses has been updated + to 5.2-20020615.

+ +

The NTP suite of programs + has been updated to 4.1.1b.

+ +

OpenPAM (``Citronella'' + release) has been imported, replacing Linux-PAM.

+ +

The OPIE + one-time-password suite has been updated to 2.4. It has + completely replaced the functionality of S/Key. [MERGED]

+ +

Perl has been removed + from the FreeBSD base system. It can still be installed + from the FreeBSD Ports Collection or as a binary + package; moving it out of the base system will make + future upgrades and maintenence easier. To reduce the + dependence of the base system on Perl, many utilities + have been rewritten as shell scripts or C programs + (specific notes are made for each affected utility). + /usr/bin/perl is now a + ``wrapper'' program, so that programs expecting to find + a Perl interpreter there will be able to function + correctly.

+ +

+

+
Warning: The Perl removal and package + integration work is ongoing.
+

+

+
+
+ +

GNU ptx has been removed + from the base system. It is not used anywhere in the + base system, and has not been recently updated or + maintained. Users requiring its functionality can + install this utility as a part of the + textproc/textutils + port.

+ +

The rc.d framework from + NetBSD has been imported. It breaks down the system + startup functionality into a number of small, + ``task-oriented'' scripts in /etc/rc.d, with dynamic-determined + ordering of startup scripts performed at boot-time.

+ +

Version 1.4.5 of the smbfs userland utilities has been + imported. [MERGED]

+ +

GNU sort has been updated + to the version from GNU + textutils 2.0.21.

+ +

+ stat(1) from NetBSD, as of 5 June 2002 has, + been imported.

+ +

GNU tar has been updated + to 1.13.25. [MERGED]

+ +

tcpdump has been updated + to 3.7.1. [MERGED]

+ +

The + csh(1) shell has been + replaced by + tcsh(1), although it + can still be run as csh. tcsh has been updated to + version 6.12. [MERGED]

+ +

The contributed version of tcp_wrappers now includes the + tcpd(8) helper + daemon. While not strictly necessary in a standard + FreeBSD installation (because + inetd(8) already + incorporates this functionality), this may be useful + for + inetd(8) replacements + such as xinetd. [MERGED]

+ +

texinfo has been updated + to 4.2. [MERGED]

+ +

top has been updated to + version 3.5b12. [MERGED]

+ +

traceroute has been + updated to LBL version 1.4a12.

+ +

The timezone database has been updated to the tzdata2002d release. [MERGED]

+ +

+

+ +

2.3.1.1 + CVS

+ +

cvs has been updated to + 1.11.2. [MERGED]

+

+ +

+

+ +

2.3.1.2 + CVSup

+

+ +

+

+ +

2.3.1.3 + KAME

+

+ +

+

+ +

2.3.1.4 + OpenSSH

+ +

OpenSSH has been + updated to version 3.1. [MERGED] Among the + changes:

+ +

+
The *2 files are + obsolete (for example, ~/.ssh/known_hosts can hold the + contents of ~/.ssh/known_hosts2).
+
+
+ ssh-keygen(1) + can import and export keys using the SECSH Public + Key File Format, for key exchange with several + commercial SSH implementations.
+
+
+ ssh-add(1) now + adds all three default keys.
+
+
+ ssh-keygen(1) + no longer defaults to a specific key type; one + must be specified with the -t option.
+

+
+
+ +

OpenSSH has been + updated to 3.4p1. [MERGED] The main changes are:

+ +

+
A ``privilege separation'' feature, which uses + unprivileged processes to contain and restrict + the effects of future compromises or programming + errors.
+
+
Several bugfixes, including closure of a + security hole that could lead to an integer + overflow and undesired privilege escalation.
+

+
+
+

+ +

+

+ +

2.3.1.5 + OpenSSL

+ +

OpenSSL has been + updated to 0.9.6g. [MERGED]

+

+ +

+

+ +

2.3.1.6 + sendmail

+ +

sendmail has been + updated from version 8.9.3 to version 8.12.6. + Important changes include: + sendmail(8) is no + longer installed as a set-user-ID root binary (now set-group-ID smmsp); new default file + locations (see /usr/src/contrib/sendmail/cf/README); + + newaliases(1) is + limited to root and trusted + users; STARTTLS encryption; and the MSA port (587) is + turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES + for more information. [MERGED]

+ +

By default, + rc(8) no longer + enables sendmail for + inbound SMTP connections. Note that + sysinstall(8) may + override this default for a binary installation, + based on what security profile is selected. This + functionality can also be manually enabled by adding + the following line to /etc/rc.conf:

+

+    sendmail_enable="YES"
+

+ +

The permissions for sendmail alias and map databases + built via /etc/mail/Makefile now default to + mode 0640 to protect against a file locking local + denial of service. It can be changed by setting the + new SENDMAIL_MAP_PERMS make.conf option. [MERGED]

+ +

The permissions for the sendmail statistics file, /var/log/sendmail.st, have been + changed from mode 0644 to mode 0640 to protect + against a file locking local denial of service. + [MERGED]

+

+ +

+

+ +

2.3.2 + Ports/Packages Collection Infrastructure

+ +

BSDPAN, a collection of + modules that provides tighter integration of Perl into the FreeBSD Ports + Collection, has been added.

+ +

For some time, FreeBSD 5.0-CURRENT (as well as some + 4.X releases) included a pkg_update(1) utility to + update installed packages, as well as their + dependencies. This utility has been removed; a superset + of its functionality can be found in the + sysutils/portupgrade + port.

+ +

+ pkg_version(1), + formerly a Perl script, has been rewritten in C.

+ +

The Ports Collection infrastructure now uses XFree86 4.2.1 as the default + version of the X Window System for the purposes of + satisfying dependencies. To return to using XFree86 3.3.6, add the following line + to /etc/make.conf: + [MERGED]

+

+    XFREE86_VERSION=3
+

+ +

The libraries installed by the + emulators/linux_base port + (required for Linux emulation) have been updated; they + now correspond to those included with Red Hat Linux 7.1. [MERGED]

+ +

By default, packages generated by the Ports + Collection (as well as the packages on the FTP sites) + are now compressed using + bzip2(1), rather than + + gzip(1). (Thus, they + now have a .tbz extension, + rather than a .tgz + extension.) The package tools have been updated to + handle the new format.

+

+ +

+

+ +

2.4 Release + Engineering and Integration

+ +

The bin distribution has + been renamed base, in order to + make creation of combined install/recovery disks + easier.

+ +

It is now possible to make releases of FreeBSD + 5-CURRENT on a FreeBSD 4-STABLE host and vice versa. + Cross-architecture (building a release for a target + architecture on a host of a different architecture) + releases are also possible. See + release(7) for details. + [MERGED]

+ +

A third drivers.flp floppy + has been added to floppy releases. It holds loadable + modules containing drivers that do not fit in the kernel + on the kern.flp disk or in the + mfsroot.flp image.

+

+ +

+

+ +

2.5 + Documentation

+ +

A number of formerly-encumbered documents from the 4.4 + BSD Programmer's Supplementary Documents have been + restored to /usr/share/doc/psd. + These include:

+ +

+
The + UNIX Time-Sharing System (01.cacm)
+
+
UNIX + Implementation (02.implement)
+
+
The + UNIX I/O System (03.iosys)
+
+
UNIX + Programming -- Second Edition (04.uprog)
+
+
The C + Programming Language -- Reference Manual + (06.Clang)
+
+
Yacc: + Yet Another Compiler-Compiler (15.yacc)
+
+
Lex -- + A Lexical Analyzer Generator (16.lex)
+
+
The M4 + Macro Processor (17.m4)
+

+ +

Several formerly-encumbered documents from the 4.4 BSD + User's Supplementary Documents have been restored to /usr/share/doc/usd. They + include:

+ +

+
NROFF/TROFF User's Manual (21.troff)
+
+
A TROFF + Tutorial (22.trofftut)
+

+

+ +

+

+ +

3 Upgrading from + previous releases of FreeBSD

+ +

Users with existing FreeBSD systems are highly encouraged + to read the ``Early Adopter's Guide to FreeBSD 5.0''. This + document generally has the filename EARLY.TXT on the distribution media, or any + other place that the release notes can be found. It offers + some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.X versus + running FreeBSD 4.X.

+ +

+

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

+

FreeBSD/sparc64 5.0-DP2 + Release Notes

+ +

The FreeBSD Project

+ +

$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.452 2002/11/14 17:59:11 bmah Exp $
+

+ +

+

+ + +

The release notes for FreeBSD 5.0-DP2 contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. Both + changes for kernel and userland are listed, as well as + applicable security advisories that were issued since + the last release. Some brief remarks on upgrading are + also presented.

+

+ +

+

Table of Contents

+

+

2.1.1 Processor/Motherboard + Support
2.1.2 Bootloader + Changes
2.1.3 Network Interface + Support
2.1.4 Network + Protocols
2.1.5 Disks and + Storage
2.1.6 Filesystems
2.1.7 PCCARD + Support
2.1.8 Multimedia + Support
2.1.9 Contributed + Software

+

+

2.3.1 Contributed + Software
2.3.2 Ports/Packages + Collection Infrastructure

+