Copyright © 2002, 2003 The FreeBSD Release Engineering Team
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/early-adopter/article.sgml,v
+1.17 2003/12/02 05:54:35 bmah Exp $
+
FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to +change soon.
+ +Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.
+ +Microsoft, FrontPage, MS-DOS, Outlook, Windows, Windows Media, and Windows NT are +either registered trademarks or trademarks of Microsoft Corporation in the United States +and/or other countries.
+ +Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the ``™'' or the ``®'' symbol.
+This article describes the status of FreeBSD 5.2-RELEASE, from the standpoint of users +who may be new to the 5.X series of releases or to FreeBSD +in general. It presents some background information on release engineering, some +highlights of new features, and some possible drawbacks that might be faced by early +adopters. It also contains some of the future release engineering plans for the 4-STABLE +development branch and some tips on upgrading existing systems.
+FreeBSD 5.X marks the first new major version of +FreeBSD in over two years. Besides a number of new features, it also contains a number of +major developments in the underlying system architecture. Along with these advances, +however, comes a system that incorporates a tremendous amount of new and +not-widely-tested code. Compared to the existing line of 4.X releases, the first few 5.X +releases may have regressions in areas of stability, performance, and occasionally +functionality.
+ +For these reasons, the Release Engineering Team <re@FreeBSD.org> specifically discourages
+users from updating from older FreeBSD releases to 5.2-RELEASE unless they are aware of
+(and prepared to deal with) possible regressions in the newer releases. Specifically, for
+more conservative users, we recommend running 4.X releases
+(such as 4.9-RELEASE) for the near-term future. We feel that such users are probably best
+served by upgrading to 5.X only after a 5-STABLE
+development branch has been created; this may be around the time of 5.3-RELEASE.
(FreeBSD 5.X suffers from what has been described as a +``chicken and egg'' problem. The entire project has a goal of producing releases that are +as stable and reliable as possible. This stability and reliability requires widespread +testing, particularly of the system's newer features. However, getting a large number of +users to test the system, in a practical sense, means building and distributing a release +first!)
+ +This article describes some of the issues involved in installing and running FreeBSD +5.2-RELEASE. We begin with a brief overview of the FreeBSD release process. We then +present some of the more noteworthy new features in FreeBSD 5.2-RELEASE, along with some +areas that may prove troublesome for unwary users. For those users choosing to remain +with 4-STABLE-based releases, we give some of the short- to medium-term plans for this +development branch. Finally, we present some notes on upgrading existing 4.X systems to 5.2-RELEASE.
+FreeBSD employs a model of development that relies on multiple development branches +within the source code repository. The main branch is called ``CURRENT'', and is referred +to in the CVS repository with the HEAD tag. New features are +committed first to this branch; although this means that CURRENT is the first to see new +functionality, it also means that it occasionally suffers from breakages as new features +are added and debugged.
+ +Most FreeBSD releases are made from one of several ``STABLE'' branches. Features are +only added to these branches after some amount of testing in CURRENT. At the moment, only +one STABLE branch is under active development; this branch is referred to as +``4-STABLE'', and all of the FreeBSD 4.X releases were +based on it. This branch has the tag RELENG_4 in the CVS +repository.
+ +FreeBSD 5.0, 5.1, and 5.2 are based on the CURRENT branch. The first of these releases +was made after over two years of development (prior to these, the last release from HEAD +was FreeBSD 4.0, in March 2000).
+ +At some point after the release of FreeBSD 5.0, a ``5-STABLE'' branch will be created +in the FreeBSD CVS repository with the branch tag RELENG_5. +The past two stable branches (3-STABLE and 4-STABLE) were created immediately after their +respective ``dot-oh'' releases (3.0 and 4.0, respectively). In hindsight, this practice +did not give sufficient time for either CURRENT to stabilize before the new branches were +created. This in turn resulted in wasted effort porting bug fixes between branches, as +well as some architectural changes that could not be ported between branches at all.
+ +Therefore, the release engineering team will only create the 5-STABLE branch in the +CVS repository after we have found a relatively stable state to use as its basis. It is +likely that there will be multiple releases in the 5.X +series before this happens; we estimate that the 5-STABLE branch will be created around +the time of 5.3-RELEASE.
+ +More information on FreeBSD release engineering processes can be found on the Release Engineering Web +pages and in the ``FreeBSD Release Engineering'' article. Specific issues for the +upcoming 5-STABLE development branch can be found in ``The Roadmap for 5-STABLE''.
+A large attraction of FreeBSD 5.X is a number of new +features. These new features and functionality generally involve large architectural +changes that were not feasible to port back to the FreeBSD 4-STABLE development branch. +(By contrast, many self-contained enhancements, such as new device drivers or userland +utilities, have already been ported.) A brief, but not exhaustive list includes:
+ +SMPng: The ``next generation'' support for SMP machines (work in progress). Ongoing +work aims to perform fine-grained locking of various kernel subsystems to increase the +number of threads of execution that can be running in the kernel. More information can be +found on the FreeBSD SMP Project +page.
+KSE: Kernel Scheduled Entities allow a single process to have multiple kernel-level +threads, similar to Scheduler Activations. The libkse and libthr threading libraries make this feature available to +multi-threaded userland programs, using the +pthread(3) +API.
+New architectures: Support for the sparc64, ia64, and amd64 architectures, in addition +to the i386, pc98, and alpha.
+GCC: The compiler toolchain is now based on GCC 3.3.X, +rather than GCC 2.95.X.
+MAC: Support for extensible, loadable Mandatory Access Control policies.
+GEOM: A flexible framework for transformations of disk I/O requests. The GBDE +experimental disk encryption facility has been developed based on GEOM.
+FFS: The FFS filesystem now supports background +fsck(8) +operations (for faster crash recovery) and filesystem snapshots.
+UFS2: A new UFS2 on-disk format has been added, which supports extended per-file +attributes and larger file sizes. UFS2 is now the default format for +newfs(8). On all +platforms except for pc98, filesystems created from within +sysinstall(8) +will use UFS2 by default.
+Cardbus: Support for Cardbus devices.
+Bluetooth: Support for Bluetooth devices.
+A more comprehensive list of new features can be found in the release notes for the +various FreeBSD 5.X releases.
+Along with the new features of FreeBSD 5.X come some +areas that can cause problems, or at least can lead to unexpected behavior. Generally, +these come from the fact that a number of features are works-in-progress. A partial list +of these areas of difficulty includes:
+ +A number of features are not yet finished. Examples from the feature list above +include SMPng and KSE. While suitable for testing and experimentation, these features may +not be ready for production use.
+Because of changes in kernel data structures and ABIs/APIs, third-party binary device +drivers will require modifications to work correctly under FreeBSD 5.0. There is a +possibility of more minor ABI/API changes before the 5-STABLE branch is created, +particularly on newer machine architectures. In some (hopefully rare) cases, user-visible +structures may change, requiring recompiling of applications or reinstallation of +ports/packages.
+Several parts of FreeBSD's base system functionality have been moved to the Ports +Collection. Notable examples include Perl, UUCP, and most (but not all) games. While these programs are +still supported, their removal from the base system may cause some confusion.
+Some parts of the FreeBSD base system have fallen into a state of disrepair due to a +lack of users and maintainers. These have been removed. Specific examples include the +generation of a.out-style executables, XNS networking support, and the X-10 controller +driver.
+A number of ports and packages do not build or do not run correctly under FreeBSD +5.X, whereas they did under FreeBSD 4-STABLE. Generally +these problems are caused by compiler toolchain changes or cleanups of header files. In +some cases they are caused by changes in kernel or device support.
+Many FreeBSD 5.X features are seeing wide exposure for +the first time. Many of these features (such as SMPng) have broad impacts on the kernel, +and it may be difficult to gauge their effects on stability and performance.
+A certain amount of debugging and diagnostic code is still in place to help track down +problems in FreeBSD 5.X's new features. This may cause +FreeBSD 5.X to perform more slowly than 4-STABLE.
+Features are only added to the 4-STABLE development branch after a ``settling time'' +in -CURRENT. FreeBSD 5.X does not have the stabilizing +influence of a -STABLE branch. (It is likely that the 5-STABLE development branch will be +created sometime after 5.3-RELEASE.)
+Documentation (such as the FreeBSD Handbook and FAQ) may not reflect changes recently made to FreeBSD 5.X.
+Because a number of these drawbacks affect system stability, the release engineering +team recommends that more conservative sites and users stick to releases based on the +4-STABLE branch until the 5.X series is more polished. +While we believe that many initial problems with stability have been fixed, some issues +with performance are still being addressed by works-in-progress. We also note that best +common practices in system administration call for trying operating system upgrades in a +test environment before upgrading one's production, or ``mission-critical'' systems.
+It is important to note that even though releases are being made in the 5.X series, support for 4.X +releases will continue for some time. Indeed, FreeBSD 4.8 was released two months after +5.0, in April 2003, followed by 4.9, in October 2003. Future releases from the 4-STABLE +branch (if any) will depend on several factors. The most important of these is the +existence and stability of the 5-STABLE branch. If CURRENT is not sufficiently stable to +allow the creation of a 5-STABLE branch, this may require and permit more releases from +the 4-STABLE branch. Until the last declared release on the 4-STABLE branch, new features +may be merged from HEAD at the discretion of developers, +subject to existing release engineering policies.
+ +To some extent, the release engineering team (as well as the developer community as a +whole) will take into account user demand for future 4-STABLE releases. This demand, +however, will need to be balanced with release engineering resources (particularly +developers' time, computing resources, and mirror archive space). We note that in +general, the FreeBSD community (both users and developers) has shown a preference for +moving forward with new features in the 5.X branch and +beyond, due to the difficulty involved in backporting (and maintaining) new functionality +in 4.X.
+ +The Security Officer Team <security-officer@FreeBSD.org>
+will continue to support releases made from the 4-STABLE branch in accordance with their
+published policies, which can be found on the Security page on the
+FreeBSD web site. Generally, the two most recent releases from any branch will be
+supported with respect to security advisories and security fixes. At its discretion, the
+team may support other releases for specific issues.
At this point, the release engineering team has no specific plans for future releases +from the 4-STABLE development branch. It seems likely that any future releases (if any) +from this branch will be lightweight, ``point'' releases. These will probably carry +4.9.X version numbers, to indicate that they are not +intended to provide large amount of new functionality compared to 4.9-RELEASE. In +general, these releases will emphasize security fixes, bug fixes, and device driver +updates (particularly to accommodate new hardware easily supported by existing drivers). +Major new features (especially those requiring infrastructure support added in 5.X) will probably not be added in these releases.
+For those users with existing FreeBSD systems, this section offers a few notes on +upgrading a FreeBSD 4.X system to 5.X. As with any FreeBSD upgrade, it is crucial to read the +release notes and the errata for the version in question, as well as src/UPDATING in the case of source upgrades.
+ +Probably the most straightforward approach is that of ``backup everything, reformat, +reinstall, and restore everything''. This eliminates problems of incompatible or obsolete +executables or configuration files polluting the new system. It allows new filesystems to +be created to take advantage of new functionality (most notably, the UFS2 defaults).
+ +As of this time, the binary upgrade option in +sysinstall(8) +has not been well-tested for cross-major-version upgrades. Using this feature is not +recommended. In particular, a binary upgrade will leave behind a number of files that are +present in FreeBSD 4.X but not in 5.X. These obsolete files may create some problems. Examples of +these files include old C++ headers, programs moved to the Ports Collection, or shared +libraries that have moved to support dynamically-linked root filesystem executables.
+ +On the i386™ and pc98 platforms, a UserConfig +utility exists on 4-STABLE to allow boot-time configuration of ISA devices when booting +from installation media. Under FreeBSD 5.X, this +functionality has been replaced in part by the +device.hints(5) +mechanism (it allows specifying the same parameters, but with a very different +interface).
+ +Floppy-based binary installations may require downloading a third, new floppy image +holding additional device drivers in kernel modules. This drivers.flp floppy image will generally be found in the same +location as the usual kern.flp and mfsroot.flp floppy images.
+ +CDROM-based installations on the i386 architecture now +use a ``no-emulation'' boot loader. This allows, among other things, the use of a GENERIC kernel, rather than the stripped-down kernel on the floppy +images. In theory, any system capable of booting the Microsoft® Windows NT® 4 installation CDROMs should be able to +cope with the FreeBSD 5.X CDROMs.
+Reading src/UPDATING is absolutely essential. The section +entitled ``To upgrade from 4.x-stable to current'' contains a step-by-step update +procedure. This procedure must be followed exactly, without making use of the +``shortcuts'' that some users occasionally employ.
+Perl has been removed from the base system, and should be +installed either from a pre-built package or from the Ports Collection. Building Perl as +a part of the base system created a number of difficulties which made updates +problematic. The base system utilities that used Perl have either been rewritten (if +still applicable) or discarded (if obsolete). +sysinstall(8) +will now install the Perl package as a part of most distribution sets, so most users will +not notice this change.
+ +It is generally possible to run old 4.X executables +under 5.X, but this requires the compat4x distribution to be installed. Using old ports may be +possible in some cases, although there are a number of known cases of backward +incompatibility. As an example, the devel/gnomevfs2, mail/postfix, and security/cfs ports need to be recompiled due to changes in the +statfs structure.
+ +When installing or upgrading over the top of an existing 4-STABLE-based system, it is +extremely important to clear out old header files in /usr/include. Renaming or moving this directory before a binary +installation or an installworld is generally sufficient. If +this step is not taken, confusion may result (especially with C++ programs) as the +compiler may wind up using a mixture of obsolete and current header files.
+ +MAKEDEV is no longer available, nor is it required. FreeBSD +5.X uses a device filesystem, which automatically creates +device nodes on demand. For more information, please see +devfs(5).
+ +UFS2 is the default on-disk format for file systems created using +newfs(8). For +all platforms except pc98, it is also the default for file systems created using the disk +labeling screen within +sysinstall(8). +Because FreeBSD 4.X only understands UFS1 (not UFS2), disk +partitions that need to be accessed by both 5.X and 4.X must be created with UFS1. This can be specified using the +-O1 option to +newfs(8), or on +the disk labeling screen in +sysinstall(8). +This situation most often arises with a a single machine that dual-boots FreeBSD 4.X and FreeBSD 5.X. Note that +there is no way to convert file systems between the two on-disk formats (other than +backing up, re-creating the file system, and restoring).
+While FreeBSD 5.2-RELEASE contains a number of new and exciting features, it may not +be suitable for all users at this time. In this document, we presented some background on +release engineering, some of the more notable new features of the 5.X series, and some drawbacks to early adoption. We also +presented some future plans for the 4-STABLE development branch and some tips on +upgrading for early adopters.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +Alpha/AXP hardware platform (also referred to as FreeBSD/alpha 5.2-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.
+ +++Note: This document includes information specific to the Alpha/AXP hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
Additions, corrections and constructive criticism are invited. In particular, +information on system quirks is more than welcome.
+ +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. To be completely politically correct given +that Hewlett Packard in turn has acquired Compaq I probably should be using HP +everywhere. 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.
+
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.
+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.
+ +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 ++
++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.
+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
+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. Graphics performance using a 64 bit slot is generally substantially +better.
+ +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 ++
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. Enabling it +requires the following line in the kernel configuration file:
+ ++device ata ++ +
The ATA interface uses irq 14.
+ +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 ++
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]
+21171 (Alcor) chip set [EB164]
+ +21172 (Alcor2) chip set [PC164]
+ +21174 (Pyxis) chip [164LX, 164SX]
+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 ++
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 10 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 ++
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 (Alcor) or 21172 (Alcor2) 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 Fast Page Mode 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. Note that the DIMMs are not SDRAM 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 ++
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 ++
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)
+ +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. KZPEA aka Adaptec 39160 +gives you dual channel LVD U160 SCSI which is bootable from SRM.
+ +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.
+
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.
+
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. You can use a KZPEA aka Adaptec 39160 for +dual channel LVD U160 SCSI, which is bootable from SRM.
+ +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.
+
UP2000 was built by Alpha Processor Inc.
+ +Features:
+ +21264 EV6 CPU at 670 or 750 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'')
+2 embedded Adaptec AIC7890/91 Wide Ultra2 SCSI chips
+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 SCSI HBAs are bootable on UP2000.
+ +Busmaster DMA is supported on the first IDE interface only. The system can boot from +it's IDE hard drives and cdrom drives.
+ +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.
+
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 1M x36 bit (4 Mbyte), 2M x36bit (8 Mbyte) and 4M 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 ++
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. +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, 333 MHz or 21164A EV56 CPUs at 400, 466, 533, 600 Mhz
+cache: 4 Mbytes per CPU. EV5 300 MHz was also available cache-less. 8 Mbytes for EV56 +600Mhz
+memory bus: 128 bit with ECC
+embedded floppy controller
+2 serial ports
+1 parallel port
+PS/2 style keyboard & mouse port
+Rawhide can be equipped with a variety of CPU modules. CPU modules exist in versions +with and without external cache. In all cases the CPU modules installed always must be of +the same speed. A mix of NT-only and full-blown Tru64/VMS CPUs works fine. It will +however result in the system reporting itself to the operating system as a Digital Server +730x (so the NT-only variant). FreeBSD does not care, but such a system will not allow +Tru64 or VMS to run.
+ +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 AS4100 has 4 pairs of memory modules. The AS4000 model is limited to 2 +pairs of memory modules. Given the choice use SDRAM for best performance. The highest +capacity memory boards must be in the memory slots marked MEM0L and MEM0H. A mix of +memory board sizes is allowed. A mix of EDO and SDRAM works as well (assuming you don't +try to mix EDO and SDRAM in a single 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 a +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 as a console. In case you use +EISA options in your machine you must run the EISA Configuration Utility (ECU) from +floppy. Do yourself a favor and use the Tru64/OpenVMS ECU, and not the WindowsNT ECU.
+
Rawhide employs an I2C based power controller system. If you want to be sure all power +is removed from the system remove all mains cables from the system.
+ +Rawhide comes with RCM functionality, which means you can power it on/off remotely, +reset it etc. See also the description for the RMC in the DS10 section of this document. +RCM versus RMC is not a typo, the various documentation I consulted used both acronyms +interchangably. Note that if you want remote power on/off to function you need to connect +a small DC adapter to the machine in order to have the RCM logic powered. You need to +supply 9-12V DC to the small inlet located next to the keyboard connector.
+ +The kernel config file must contain:
+ ++options DEC_KN300 +cpu EV5 ++
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 a 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 ++
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.
+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 ++
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.
+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.
+The ES40 is a SMP system that can have 1 - 4 21264 Alpha CPUs. With the maximum +configuration of 32GB of memory these systems are often deployed as heavy database +servers and are also found in HPTC compute farm environments.
+ +Features:
+ +21264 Alpha CPU at 500 (EV6), 667 (EV67) or 833 MHz (EV68) (max. 4 CPUs)
+memory bus: 256-bit wide
+21272 Core Logic chipset
+PS/2 mouse & keyboard port
+memory: 200-pin JEDEC standard SDRAM DIMMS, max 32 GBytes of memory
+2 16550A serial port
+1 ECP/EPP parallel port
+ALI M1543C Ultra DMA66 IDE interface
+expansion: 2 64 bit PCI buses
+SRM console code comes standard with the ES40.
+ +ES40 comes with an ATA CDROM drive, but uses SCSI harddisks. The usual Symbios & +Qlogic adapters are bootable, as is the KZPEA aka Adaptec 39160 dual channel LVD U160 +adapter.
+ +Memory is divided in 4 memory arrays which each contain a set of 4 SDRAM DIMMs. Each +DIMM is 72 bit wide and of the 100MHz speed variant. An array can contain 2 sets, so 8 +DIMMs max per array. The DIMMs live on Memory Mother Boards (MMBs). There are 2 MMB +models, with 4 and 8 DIMM sockets respectively. Each MMB provides half of the 256 bit +memory bus width to the CPUs. Given the myriad options for the memory configuration it is +advisable to check the system documentation for the optimum memory configuration.
+ +Dependent on the model variation the ES40 has 6 or 10 64 bit PCI slots. This is +basically just means the same backplane with less connectors mounted.
+ +ES40 has the same RMC remote power control as DS10 and DS20. See the description of +the RMC in the DS10 section of this document. Most variations of ES40 have multiple power +supplies, allowing for N+1 redundancy. When installing CPU cards you must unplug all +power cords, the CPU cards receive standby power from the power supplies. Maximum memory +configurations need more than the default number of powersupplies.
+ +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.
+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. Those of you interested in U160 SCSI might want to take a look +at an Adaptec 39160 dual channel LVD U160 adapter. Compaq calls this a KZPEA adapter. +Recent Alpha models have SRM versions that can boot from them. In general be aware of the +machine-specific boot-ability issues for the various adapter models. Where known they are +listed in the individual machine descriptions.
+ +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.
+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
+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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host +adapters ( +ahc(4) +driver)
+ +AMI MegaRAID Express and Enterprise family RAID controllers ( +amr(4) +driver)
+ +++Booting from these controllers is not supported due to SRM limitations.
+
Mylex DAC-family RAID controllers with 2.x, 3.x, 4.x and 5.x firmware ( +mlx(4) +driver)
+ +++Booting from these controllers is not supported due to SRM limitations. DAC960 +controllers sold by Digital/Compaq for Alpha systems as part of the StorageWorks family, +e.g. KZPSC or KZPAC are bootable from SRM. Note that these cards used 2.x firmware. SRM +bootability of newer firmware is unknown.
+
LSI/Symbios (formerly NCR) 53C8XX and 53C10XX PCI SCSI controllers, either embedded on motherboard or on +add-on boards ( +ncr(4) and +sym(4) +drivers)
+ +Qlogic controllers and variants ( +isp(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+ATAPI IDE interface ( +acd(4))
+Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast +Ethernet controller chip ( +sf(4) +driver)
+ +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)
+ +Winbond W89C840F Fast Ethernet NICs ( +wb(4) +driver)
+ +VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M +``Rhine III'' Fast Ethernet NICs ( +vr(4) +driver)
+ +Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83815 Fast Ethernet NICs ( +sis(4) +driver)
+ +Sundance Technologies ST201 PCI Fast Ethernet NICs ( +ste(4) +driver)
+ +SysKonnect SK-984x PCI Gigabit Ethernet cards ( +sk(4) +driver)
+ +Texas Instruments ThunderLAN PCI NICs ( +tl(4) +driver)
+ +DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus ( +dc(4) +driver)
+ +DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs ( +de(4) +driver)
+ +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
+3Com Etherlink XL-based NICs ( +xl(4) +driver)
+ +Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990) +chipset ( +txp(4) +driver)
+ +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)
+ +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based PCI Fast Ethernet and Gigabit +Ethernet controllers ( +re(4) +driver)
+``PC standard'' 8250, 16450, and 16550-based serial ports ( +sio(4) +driver)
+ +AST 4 port serial card using shared IRQ
+ +Comtrol Rocketport card ( +rp(4) +driver)
+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
+A range of USB peripherals are supported; devices known to work are listed in this +section. Owing to the generic nature of most USB devices, with some exceptions any device +of a given class will be supported, even if not explicitly listed here.
+ +++Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.
+
++Note: USB Bluetooth adapters can be found in Bluetooth +section.
+
OHCI 1.0-compliant host controllers ( +ohci(4) +driver)
+ +UHCI 1.1-compliant host controllers ( +uhci(4) +driver)
+ +Hubs
+ +Keyboards ( +ukbd(4) +driver)
+ +Mice ( +ums(4) +driver)
+ +Printers and parallel printer conversion cables ( +ulpt(4) +driver)
+ +ATen parallel printer adapter
+Belkin F5U002 parallel printer adapter
+Canon BJ F850, S600
+Canon LBP-1310, 350
+Entrega USB-to-parallel printer adapter
+Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)
+Oki Data MICROLINE ML660PS
+Seiko Epson PM-900C, 880C, 820C, 730C
+Storage ( +umass(4) +driver)
+ +ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M
+Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20
+FujiFilm Zip USB Drive ZDR100 USB A
+GREEN HOUSE USB Flash Memory ``PicoDrive'' GH-UFD32M, 64M, 128M
+IBM 32MB USB Memory Key (P/N 22P5296)
+IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)
+I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)
+I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)
+Iomega Zip750 USB2.0 Drive
+Keian USB1.1/2.0 3.5-inch HDD Case KU350A
+Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0
+Logitec USB1.1/2.0 HDD Unit SHD-E60U2
+Logitec Mobile USB Memory LMC-256UD
+Logitec USB Double-Speed Floppy Drive LFD-31U2
+Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)
+Matshita CF-VFDU03 floppy drive
+MELCO USB2.0 MO Drive MO-CH640U2
+I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI
+MELCO USB Flash Disk ``PetitDrive'', RUF-32M, -64M, -128M, -256M
+MELCO USB2.0 Flash Disk ``PetitDrive2'', RUF-256M/U2, -512M/U2
+MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, -C64M, -C128M, -C256M, -C512M
+Microtech USB-SCSI-HD 50 USB to SCSI cable
+NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U
+Panasonic floppy drive
+Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)
+RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B
+Sony Portable CD-R/RW Drive CRX10U (CDROM only)
+TEAC Portable USB CD-ROM Unit CD-110PU/210PU
+Y-E Data floppy drive (720/1.44/2.88Mb)
+Floppy drives ( +fdc(4) +driver)
+ +VGA-compatible video cards ( +vga(4) +driver)
+ +++Note: Information regarding specific video cards and compatibility with XFree86 can be found at http://www.xfree86.org/.
+
Keyboards including:
+ +AT-style keyboards ( +atkbd(4) +driver)
+PS/2 keyboards ( +atkbd(4) +driver)
+USB keyboards ( +ukbd(4) +driver)
+Pointing devices including:
+ +PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)
+Serial mice and compatible devices
+USB mice ( +ums(4) +driver)
+++Note: +moused(8) has +more information on using pointing devices with FreeBSD. Information on using pointing +devices with XFree86 can be found at http://www.xfree86.org/.
+
``PC standard'' parallel ports ( +ppc(4) +driver)
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +AMD64 hardware platform (also referred to as FreeBSD/amd64 5.2-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.
+ +++Note: This document includes information specific to the AMD64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
FreeBSD/amd64 has supported the AMD64 (``Hammer'') architecture since mid-2003. It +made its first debut as an experimental release based on FreeBSD 5.1-RELEASE.
+ +As of this writing, this port supports the Athlon64 (``Clawhammer'') and Opteron +(``Sledgehammer'') machines. The largest tested memory configuration to date is 8GB. SMP +support has been recently completed and is reasonably robust.
+ +In many respects, FreeBSD/amd64 is similar to FreeBSD/i386, in terms of drivers +supported. There may be some issues with 64-bit cleanliness in some (particularly older) +drivers. Generally, drivers that already function correctly on other 64-bit platforms +should work.
+ +FreeBSD/amd64 is a very young platform on FreeBSD. While the core FreeBSD kernel and +base system components are generally fairly robust, there are likely to still be rough +edges, particularly with third party packages.
+This section describes the devices currently known to be supported by with FreeBSD on +the AMD64 platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.
+ +Where possible, the drivers applicable to each device or class of devices is listed. +If the driver in question has a manual page in the FreeBSD base distribution (most +should), it is referenced here. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+Adaptec AIC-6260 and AIC-6360 based boards ( +aic(4) +driver)
+ +Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host +adapters ( +ahc(4) +driver)
+ +Ultra-320 SCSI controllers based on the Adaptec AIC7901, AIC7901A, and AIC7902 +Ultra320 controller chips ( +ahd(4) +driver)
+ +Adaptec FSA family RAID controllers ( +aac(4) +driver)
+ +AdvanSys SCSI controllers (all models, +adv(4) and +adw(4) +drivers)
+ +BusLogic MultiMaster ``W'', ``C'', ``S'', and ``A'' Series Host Adapters ( +bt(4) +driver)
+ +DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV +SCSI/RAID controllers ( +dpt(4) +driver)
+ +Adaptec 21x0S/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)
+ +DPT SmartRAID V and VI SCSI RAID controllers ( +asr(4) +driver)
+ +AMI MegaRAID Express and Enterprise family RAID controllers ( +amr(4) +driver)
+ +++Note: Booting from these controllers is supported. EISA adapters are not +supported.
+
Mylex DAC-family RAID controllers with 2.x, 3.x, 4.x and 5.x firmware ( +mlx(4) +driver)
+ +++Note: Booting from these controllers is supported. EISA adapters are not +supported.
+
Mylex AcceleRAID/eXtremeRAID family PCI to SCSI RAID controllers with 6.x firmware ( +mly(4) +driver)
+ +LSI/Symbios (formerly NCR) 53C8XX and 53C10XX PCI SCSI controllers, either embedded on motherboard or on +add-on boards ( +ncr(4) and +sym(4) +drivers)
+ +Qlogic controllers and variants ( +isp(4) +driver)
+ +DTC 3290 EISA SCSI controller in 1542 emulation mode.
+ +Tekram DC390 and DC390T controllers, maybe other cards based on the AMD 53c974 as well +( +amd(4) +driver)
+ +SCSI adapters utilizing the Command Interface for SCSI-3 Support ( +ciss(4) +driver)
+ +Intel Integrated RAID Controllers ( +iir(4) +driver)
+ +IBM / Adaptec ServeRAID series ( +ips(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +PCI SCSI host adapters using the Tekram TRM-S1040 SCSI chipset ( +trm(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+ATAPI IDE interface ( +acd(4))
+Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast +Ethernet controller chip ( +sf(4) +driver)
+ +Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets +( +ti(4) +driver)
+ +AMD PCnet NICs ( +lnc(4) and +pcn(4) +drivers)
+ +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)
+ +RealTek 8129/8139 Fast Ethernet NICs ( +rl(4) +driver)
+ +Winbond W89C840F Fast Ethernet NICs ( +wb(4) +driver)
+ +VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M +``Rhine III'' Fast Ethernet NICs ( +vr(4) +driver)
+ +Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83815 Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs ( +nge(4) +driver)
+ +Sundance Technologies ST201 PCI Fast Ethernet NICs ( +ste(4) +driver)
+ +SysKonnect SK-984x PCI Gigabit Ethernet cards ( +sk(4) +driver)
+ +Texas Instruments ThunderLAN PCI NICs ( +tl(4) +driver)
+ +DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus ( +dc(4) +driver)
+ +ADMtek Inc. AN986-based USB Ethernet NICs ( +aue(4) +driver)
+ +CATC USB-EL1210A-based USB Ethernet NICs ( +cue(4) +driver)
+ +Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs ( +kue(4) +driver)
+ +ASIX Electronics AX88172-based USB Ethernet NICs ( +axe(4) +driver)
+ +RealTek RTL8150-based USB Ethernet NICs ( +rue(4) +driver)
+ +DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs ( +de(4) +driver)
+ +Fujitsu MB86960A/MB86965A based Fast Ethernet NICs ( +fe(4) +driver)
+ +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)
+ +3Com 3C5x9 Etherlink III NICs ( +ep(4) +driver)
+ +3Com Etherlink XL-based NICs ( +xl(4) +driver)
+ +3Com 3C59X series NICs ( +vx(4) +driver)
+ +Crystal Semiconductor CS89x0-based NICs ( +cs(4) +driver)
+ +Megahertz X-Jack Ethernet PC-Card CC-10BT ( +sn(4) +driver)
+ +Xircom CreditCard adapters (16 bit) and workalikes ( +xe(4) +driver)
+ +Gigabit Ethernet cards based on the Level 1 LXT1001 NetCellerator controller ( +lge(4) +driver)
+ +Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990) +chipset ( +txp(4) +driver)
+ +Gigabit Ethernet NICs based on the Broadcom BCM570x ( +bge(4) +driver)
+ +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)
+ +Broadcom BCM4401 based Fast Ethernet adapters ( +bfe(4) +driver)
+ +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based PCI Fast Ethernet and Gigabit +Ethernet controllers ( +re(4) +driver)
+Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets ( +wi(4) +driver)
+ +Cisco/Aironet 802.11b wireless adapters ( +an(4) +driver)
+ +AMD Am79C930 and Harris (Intersil) based 802.11b cards ( +awi(4) +driver)
+``PC standard'' 8250, 16450, and 16550-based serial ports ( +sio(4) +driver)
+ +AST 4 port serial card using shared IRQ
+ +PCI-Based multi-port serial boards ( +puc(4) +driver)
+ +Actiontech 56K PCI
+Avlab Technology, PCI IO 2S and PCI IO 4S
+Comtrol RocketPort 550
+Decision Computers PCCOM 4-port serial and dual port RS232/422/485
+Dolphin Peripherals 4025/4035/4036
+IC Book Labs Dreadnought 16x Lite and Pro
+Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550
+Middle Digital, Weasle serial port
+Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI
+NEC PK-UG-X001 and PK-UG-X008
+Netmos NM9835 PCI-2S-550
+Oxford Semiconductor OX16PCI954 PCI UART
+Syba Tech SD-LAB PCI-4S2P-550-ECP
+SIIG Cyber I/O PCI 16C550/16C650/16C850
+SIIG Cyber 2P1S PCI 16C550/16C650/16C850
+SIIG Cyber 2S1P PCI 16C550/16C650/16C850
+SIIG Cyber 4S PCI 16C550/16C650/16C850
+SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850
+Syba Tech Ltd. PCI-4S2P-550-ECP
+Titan PCI-200H and PCI-800H
+US Robotics (3Com) 3CP5609 modem
+VScom PCI-400 and PCI-800
+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)
+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
+Creative Technologies Sound Blaster Live! series (emu10k1 driver)
+ +Trident 4DWave DX/NX ( +pcm(4) +driver)
+ +VIA Technologies VT82C686A
+ +Yamaha
+ +DS1
+DS1e
+A range of USB peripherals are supported; devices known to work are listed in this +section. Owing to the generic nature of most USB devices, with some exceptions any device +of a given class will be supported, even if not explicitly listed here.
+ +++Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.
+
++Note: USB Bluetooth adapters can be found in Bluetooth +section.
+
OHCI 1.0-compliant host controllers ( +ohci(4) +driver)
+ +UHCI 1.1-compliant host controllers ( +uhci(4) +driver)
+ +USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)
+ +Hubs
+ +Keyboards ( +ukbd(4) +driver)
+ +Miscellaneous
+ +Assist Computer Systems PC Camera C-M1
+ActiveWire I/O Board
+Creative Technology Video Blaster WebCam Plus
+Diamond Rio 500, 600, and 800 MP3 players ( +urio(4) +driver)
+D-Link DSB-R100 USB Radio ( +ufm(4) +driver)
+Mirunet AlphaCam Plus
+Modems ( +umodem(4) +driver)
+ +3Com 5605
+Metricom Ricochet GS USB wireless modem
+Yamaha Broadband Wireless Router RTW65b
+Mice ( +ums(4) +driver)
+ +Printers and parallel printer conversion cables ( +ulpt(4) +driver)
+ +ATen parallel printer adapter
+Belkin F5U002 parallel printer adapter
+Canon BJ F850, S600
+Canon LBP-1310, 350
+Entrega USB-to-parallel printer adapter
+Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)
+Oki Data MICROLINE ML660PS
+Seiko Epson PM-900C, 880C, 820C, 730C
+Serial devices ( +ubsa(4), +uftdi(4) and +uplcom(4) +drivers)
+ +Scanners (through SANE) ( +uscanner(4) +driver)
+ +Storage ( +umass(4) +driver)
+ +ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M
+Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20
+FujiFilm Zip USB Drive ZDR100 USB A
+GREEN HOUSE USB Flash Memory ``PicoDrive'' GH-UFD32M, 64M, 128M
+IBM 32MB USB Memory Key (P/N 22P5296)
+IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)
+I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)
+I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)
+Iomega Zip750 USB2.0 Drive
+Keian USB1.1/2.0 3.5-inch HDD Case KU350A
+Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0
+Logitec USB1.1/2.0 HDD Unit SHD-E60U2
+Logitec Mobile USB Memory LMC-256UD
+Logitec USB Double-Speed Floppy Drive LFD-31U2
+Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)
+Matshita CF-VFDU03 floppy drive
+MELCO USB2.0 MO Drive MO-CH640U2
+I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI
+MELCO USB Flash Disk ``PetitDrive'', RUF-32M, -64M, -128M, -256M
+MELCO USB2.0 Flash Disk ``PetitDrive2'', RUF-256M/U2, -512M/U2
+MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, -C64M, -C128M, -C256M, -C512M
+Microtech USB-SCSI-HD 50 USB to SCSI cable
+NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U
+Panasonic floppy drive
+Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)
+RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B
+Sony Portable CD-R/RW Drive CRX10U (CDROM only)
+TEAC Portable USB CD-ROM Unit CD-110PU/210PU
+Y-E Data floppy drive (720/1.44/2.88Mb)
+Audio Devices ( +uaudio(4) +driver)
+ +Handspring Visor and other PalmOS devices ( +uvisor(4) +driver)
+ +Handspring Visor
+Palm M125, M500, M505
+Sony Clie 4.0 and 4.1
+Host Controllers ( +fwohci(4) +driver)
+ +Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)
+PCCARD Host Controllers ( +ng_bt3c(4) +driver)
+ +3Com/HP 3CRWB6096-A PCCARD adapter
+USB Host Controllers ( +ng_ubt(4) +driver)
+ +3Com 3CREB96
+EPoX BT-DG02
+Mitsumi USB Bluetooth adapter
+MSI MS-6967
+TDK Bluetooth USB adapter
+Accelerators based on the Hifn 7751, 7811, or 7951 chipsets ( +hifn(4) +driver)
+ +Accelerators based on the SafeNet 1141 or 1741 cryptographic accelerator chipsets ( +safe(4) +driver)
+ +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)
+FAX-Modem/PCCARD
+ +MELCO IGM-PCM56K/IGM-PCM56KH
+Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)
+Floppy drives ( +fdc(4) +driver)
+ +VGA-compatible video cards ( +vga(4) +driver)
+ +++Note: Information regarding specific video cards and compatibility with XFree86 can be found at http://www.xfree86.org/.
+
Keyboards including:
+ + + +Pointing devices including:
+ +Bus mice and compatible devices ( +mse(4) +driver)
+PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)
+Serial mice and compatible devices
+USB mice ( +ums(4) +driver)
+++Note: +moused(8) has +more information on using pointing devices with FreeBSD. Information on using pointing +devices with XFree86 can be found at http://www.xfree86.org/.
+
``PC standard'' parallel ports ( +ppc(4) +driver)
+ +PC-compatible joysticks ( +joy(4) +driver)
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +i386 hardware platform (also referred to as FreeBSD/i386 5.2-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.
+ +++Note: This document includes information specific to the i386 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
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. (However, FreeBSD 5.2-RELEASE and later no longer support the 80386SX +processor.) 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 may yield some +clues.
+ +FreeBSD will take advantage of HyperThreading (HTT) support on Intel CPUs that support +this feature. A kernel with the options SMP feature +enabled will automatically detect the additional logical processors. The default FreeBSD +scheduler treats the logical processors the same as additional physical processors; in +other words, no attempt is made to optimize scheduling decisions given the shared +resources between logical processors within the same CPU. Because this naive scheduling +can result in suboptimal performance, under certain circumstances it may be useful to +disable the logical processors with the the machdep.hlt_logical_cpus sysctl variable. It is also possible to +halt any CPU in the idle loop with the machdep.hlt_cpus sysctl +variable. The +smp(4) manual +page has more details.
+ +FreeBSD will take advantage of Physical Address Extensions (PAE) support on CPUs that +support this feature. A kernel with the PAE feature enabled +will detect memory above 4 gigabytes and allow it to be used by the system. This feature +places constraints on the device drivers and other features of FreeBSD which may be used; +consult the +pae(4) manpage +for more details.
+ +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 may be useful.
+ +Most modern laptops (as well as many desktops) use the Advanced Configuration and +Power Management (ACPI) standard. FreeBSD supports ACPI via the ACPI Component +Architecture reference implementation from Intel, as described in the +acpi(4) manual +page. The use of ACPI causes instabilities on some machines and it may be necessary to +disable the ACPI driver, which is normally loaded via a kernel module. This may be +accomplished by adding the following line to /boot/device.hints:
+ ++hint.acpi.0.disabled="1" ++ +
Users debugging ACPI-related problems may find it useful to disable portions of the +ACPI functionality. The +acpi(4) manual +page has more information on how to do this via loader tunables.
+ +ACPI depends on a Differentiated System Descriptor Table (DSDT) provided by each +machine's BIOS. Some machines have bad or incomplete DSDTs, which prevents ACPI from +functioning correctly. Replacement DSDTs for some machines can be found at the DSDT section of the +ACPI4Linux project Web site. +FreeBSD can use these DSDTs to override the DSDT provided by the BIOS; see the +acpi(4) manual +page for more information.
+This section describes the devices currently known to be supported by with FreeBSD on +the i386 platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.
+ +Where possible, the drivers applicable to each device or class of devices is listed. +If the driver in question has a manual page in the FreeBSD base distribution (most +should), it is referenced here. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+Adaptec AIC-6260 and AIC-6360 based boards ( +aic(4) +driver)
+ +Adaptec AHA-154X ISA and AHA-1640 MCA SCSI controllers and compatibles ( +aha(4) +driver)
+ +Adaptec AHA_174x series EISA SCSI controller in enhanced mode ( +ahb(4) +driver)
+ +Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host +adapters ( +ahc(4) +driver)
+ +Ultra-320 SCSI controllers based on the Adaptec AIC7901, AIC7901A, and AIC7902 +Ultra320 controller chips ( +ahd(4) +driver)
+ +Adaptec FSA family RAID controllers ( +aac(4) +driver)
+ +AdvanSys SCSI controllers (all models, +adv(4) and +adw(4) +drivers)
+ +BusLogic MultiMaster ``W'', ``C'', ``S'', and ``A'' Series Host Adapters ( +bt(4) +driver)
+ +++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)
+ +Adaptec 21x0S/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)
+ +DPT SmartRAID V and VI SCSI RAID controllers ( +asr(4) +driver)
+ +AMI MegaRAID Express and Enterprise family RAID controllers ( +amr(4) +driver)
+ +++Note: Booting from these controllers is supported. EISA adapters are not +supported.
+
Mylex DAC-family RAID controllers with 2.x, 3.x, 4.x and 5.x firmware ( +mlx(4) +driver)
+ +++Note: Booting from these controllers is supported. EISA adapters are not +supported.
+
Mylex AcceleRAID/eXtremeRAID family PCI to SCSI RAID controllers with 6.x firmware ( +mly(4) +driver)
+ +3ware Escalade ATA RAID controllers ( +twe(4) +driver)
+ +LSI/Symbios (formerly NCR) 53C8XX and 53C10XX PCI SCSI controllers, either embedded on motherboard or on +add-on boards ( +ncr(4) and +sym(4) +drivers)
+ +NCR 53C500 based PC-Card SCSI host adapters ( +ncv(4) +driver)
+ +TMC 18C30, 18C50 and 36C70 (AIC-6820) based ISA/PC-Card SCSI host adapters ( +stg(4) +driver)
+ +Qlogic controllers and variants ( +isp(4) +driver)
+ +DTC 3290 EISA SCSI controller in 1542 emulation mode.
+ +Tekram DC390 and DC390T controllers, maybe other cards based on the AMD 53c974 as well +( +amd(4) +driver)
+ +Workbit Ninja SCSI-3 based PC-Card SCSI host adapters ( +nsp(4) +driver)
+ +Adaptec AIC-7110 Parallel to SCSI interfaces ( +vpo(4) +driver)
+ +Compaq Intelligent Drive Array Controllers ( +ida(4) +driver)
+ +SCSI adapters utilizing the Command Interface for SCSI-3 Support ( +ciss(4) +driver)
+ +Intel Integrated RAID Controllers ( +iir(4) +driver)
+ +Promise SuperTrak ATA RAID controllers ( +pst(4) +driver)
+ +IBM / Adaptec ServeRAID series ( +ips(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +PCI SCSI host adapters using the Tekram TRM-S1040 SCSI chipset ( +trm(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+Matsushita CR-562, CR-563, and compatibles ( +matcd(4) +driver)
+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 +cam(4) 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))
+Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast +Ethernet controller chip ( +sf(4) +driver)
+ +Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets +( +ti(4) +driver)
+ +AMD PCnet NICs ( +lnc(4) and +pcn(4) +drivers)
+ +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)
+ +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)
+ +Winbond W89C840F Fast Ethernet NICs ( +wb(4) +driver)
+ +VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M +``Rhine III'' Fast Ethernet NICs ( +vr(4) +driver)
+ +Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83815 Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs ( +nge(4) +driver)
+ +Sundance Technologies ST201 PCI Fast Ethernet NICs ( +ste(4) +driver)
+ +SysKonnect SK-984x PCI Gigabit Ethernet cards ( +sk(4) +driver)
+ +Texas Instruments ThunderLAN PCI NICs ( +tl(4) +driver)
+ +DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus ( +dc(4) +driver)
+ +ADMtek Inc. AN986-based USB Ethernet NICs ( +aue(4) +driver)
+ +CATC USB-EL1210A-based USB Ethernet NICs ( +cue(4) +driver)
+ +Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs ( +kue(4) +driver)
+ +ASIX Electronics AX88172-based USB Ethernet NICs ( +axe(4) +driver)
+ +RealTek RTL8150-based USB Ethernet NICs ( +rue(4) +driver)
+ +DEC EtherWORKS II and III NICs ( +le(4) +driver)
+ +DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs ( +de(4) +driver)
+ +Fujitsu MB86960A/MB86965A based Fast Ethernet NICs ( +fe(4) +driver)
+ +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 82586-based Ethernet NICs ( +ie(4) +driver)
+ +3Com 3C5x9 Etherlink III NICs ( +ep(4) +driver)
+ +3Com 3C501 8-bit ISA Ethernet NIC ( +el(4) +driver)
+ +3Com Etherlink XL-based NICs ( +xl(4) +driver)
+ +3Com 3C59X series NICs ( +vx(4) +driver)
+ +Crystal Semiconductor CS89x0-based NICs ( +cs(4) +driver)
+ +Megahertz X-Jack Ethernet PC-Card CC-10BT ( +sn(4) +driver)
+ +Xircom CreditCard adapters (16 bit) and workalikes ( +xe(4) +driver)
+ +Gigabit Ethernet cards based on the Level 1 LXT1001 NetCellerator controller ( +lge(4) +driver)
+ +Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990) +chipset ( +txp(4) +driver)
+ +Gigabit Ethernet NICs based on the Broadcom BCM570x ( +bge(4) +driver)
+ +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)
+ +Myson Ethernet NICs ( +my(4) +driver)
+ +Broadcom BCM4401 based Fast Ethernet adapters ( +bfe(4) +driver)
+ +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based PCI Fast Ethernet and Gigabit +Ethernet controllers ( +re(4) +driver)
+Efficient Networks, Inc. ENI-155p ATM PCI Adapters (hea driver)
+ +FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)
+ +IDT NICStAR 77201/211-based ATM Adapters ( +idt(4) +driver)
+ +FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)
+ +IDT77252-based ATM cards ( +patm(4) +driver)
+NCR / AT&T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards ( +wl(4) +driver)
+ +Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets ( +wi(4) +driver)
+ +Cisco/Aironet 802.11b wireless adapters ( +an(4) +driver)
+ +Raytheon Raylink 2.4GHz wireless adapters ( +ray(4) +driver)
+ +AMD Am79C930 and Harris (Intersil) based 802.11b cards ( +awi(4) +driver)
+ +Atheros AR5210, AR5211, and AR5212-based 802.11a/b/g network interfaces ( +ath(4) +driver)
+Cronyx-Sigma synchronous / asynchronous serial adapters ( +cx(4) +driver)
+ +Granch SBNI12 point-to-point communications adapters ( +sbni(4) +driver)
+ +Granch SBNI16 SHDSL modems ( +sbsh(4) +driver)
+ +SMC COM90cx6 ARCNET network adapters (cm driver)
+ +SMC 90c26, 90c56, and 90c66 in 90c56 compatability mode
+LAN Media Corp WAN adapters based on the DEC ``Tulip'' Fast Ethernet controller ( +lmc(4) +driver)
+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
+``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)
+ +PCI-Based multi-port serial boards ( +puc(4) +driver)
+ +Actiontech 56K PCI
+Avlab Technology, PCI IO 2S and PCI IO 4S
+Comtrol RocketPort 550
+Decision Computers PCCOM 4-port serial and dual port RS232/422/485
+Dolphin Peripherals 4025/4035/4036
+IC Book Labs Dreadnought 16x Lite and Pro
+Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550
+Middle Digital, Weasle serial port
+Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI
+NEC PK-UG-X001 and PK-UG-X008
+Netmos NM9835 PCI-2S-550
+Oxford Semiconductor OX16PCI954 PCI UART
+Syba Tech SD-LAB PCI-4S2P-550-ECP
+SIIG Cyber I/O PCI 16C550/16C650/16C850
+SIIG Cyber 2P1S PCI 16C550/16C650/16C850
+SIIG Cyber 2S1P PCI 16C550/16C650/16C850
+SIIG Cyber 4S PCI 16C550/16C650/16C850
+SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850
+Syba Tech Ltd. PCI-4S2P-550-ECP
+Titan PCI-200H and PCI-800H
+US Robotics (3Com) 3CP5609 modem
+VScom PCI-400 and PCI-800
+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 ( +stl(4) and +stli(4) +drivers)
+ +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)
+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
+Creative Technologies Sound Blaster Live! series (emu10k1 driver)
+ +Trident 4DWave DX/NX ( +pcm(4) +driver)
+ +VIA Technologies VT82C686A
+ +Yamaha
+ +DS1
+DS1e
+Brooktree Bt848/849/878/879-based frame grabbers ( +bktr(4) +driver)
+ +Connectix QuickCam
+ +Cortex1 frame grabber (ctx driver)
+ +Creative Labs Video Spigot frame grabber (spigot driver)
+ +Matrox Meteor Video frame grabber ( +meteor(4) +driver)
+A range of USB peripherals are supported; devices known to work are listed in this +section. Owing to the generic nature of most USB devices, with some exceptions any device +of a given class will be supported, even if not explicitly listed here.
+ +++Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.
+
++Note: USB Bluetooth adapters can be found in Bluetooth +section.
+
OHCI 1.0-compliant host controllers ( +ohci(4) +driver)
+ +UHCI 1.1-compliant host controllers ( +uhci(4) +driver)
+ +USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)
+ +Hubs
+ +Keyboards ( +ukbd(4) +driver)
+ +Miscellaneous
+ +Assist Computer Systems PC Camera C-M1
+ActiveWire I/O Board
+Creative Technology Video Blaster WebCam Plus
+Diamond Rio 500, 600, and 800 MP3 players ( +urio(4) +driver)
+D-Link DSB-R100 USB Radio ( +ufm(4) +driver)
+Mirunet AlphaCam Plus
+Modems ( +umodem(4) +driver)
+ +3Com 5605
+Metricom Ricochet GS USB wireless modem
+Yamaha Broadband Wireless Router RTW65b
+Mice ( +ums(4) +driver)
+ +Printers and parallel printer conversion cables ( +ulpt(4) +driver)
+ +ATen parallel printer adapter
+Belkin F5U002 parallel printer adapter
+Canon BJ F850, S600
+Canon LBP-1310, 350
+Entrega USB-to-parallel printer adapter
+Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)
+Oki Data MICROLINE ML660PS
+Seiko Epson PM-900C, 880C, 820C, 730C
+Serial devices ( +ubsa(4), +uftdi(4) and +uplcom(4) +drivers)
+ +Scanners (through SANE) ( +uscanner(4) +driver)
+ +Storage ( +umass(4) +driver)
+ +ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M
+Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20
+FujiFilm Zip USB Drive ZDR100 USB A
+GREEN HOUSE USB Flash Memory ``PicoDrive'' GH-UFD32M, 64M, 128M
+IBM 32MB USB Memory Key (P/N 22P5296)
+IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)
+I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)
+I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)
+Iomega USB Zip 100Mb (primitive support still)
+Iomega Zip750 USB2.0 Drive
+Keian USB1.1/2.0 3.5-inch HDD Case KU350A
+Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0
+Logitec USB1.1/2.0 HDD Unit SHD-E60U2
+Logitec Mobile USB Memory LMC-256UD
+Logitec USB Double-Speed Floppy Drive LFD-31U2
+Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)
+Matshita CF-VFDU03 floppy drive
+MELCO USB2.0 MO Drive MO-CH640U2
+I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI
+MELCO USB Flash Disk ``PetitDrive'', RUF-32M, -64M, -128M, -256M
+MELCO USB2.0 Flash Disk ``PetitDrive2'', RUF-256M/U2, -512M/U2
+MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, -C64M, -C128M, -C256M, -C512M
+Microtech USB-SCSI-HD 50 USB to SCSI cable
+NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U
+Panasonic floppy drive
+Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)
+RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B
+Sony Portable CD-R/RW Drive CRX10U (CDROM only)
+TEAC Portable USB CD-ROM Unit CD-110PU/210PU
+Y-E Data floppy drive (720/1.44/2.88Mb)
+Audio Devices ( +uaudio(4) +driver)
+ +Handspring Visor and other PalmOS devices ( +uvisor(4) +driver)
+ +Handspring Visor
+Palm M125, M500, M505
+Sony Clie 4.0 and 4.1
+Host Controllers ( +fwohci(4) +driver)
+ +Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)
+PCCARD Host Controllers ( +ng_bt3c(4) +driver)
+ +3Com/HP 3CRWB6096-A PCCARD adapter
+USB Host Controllers ( +ng_ubt(4) +driver)
+ +3Com 3CREB96
+EPoX BT-DG02
+Mitsumi USB Bluetooth adapter
+MSI MS-6967
+TDK Bluetooth USB adapter
+Accelerators based on the Hifn 7751, 7811, or 7951 chipsets ( +hifn(4) +driver)
+ +Accelerators based on the SafeNet 1141 or 1741 cryptographic accelerator chipsets ( +safe(4) +driver)
+ +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)
+FAX-Modem/PCCARD
+ +MELCO IGM-PCM56K/IGM-PCM56KH
+Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)
+Floppy drives ( +fdc(4) +driver)
+ +Genius and Mustek hand scanners
+ +GPB and Transputer drivers
+ +VGA-compatible video cards ( +vga(4) +driver)
+ +++Note: Information regarding specific video cards and compatibility with XFree86 can be found at http://www.xfree86.org/.
+
Keyboards including:
+ +AT-style keyboards ( +atkbd(4) +driver)
+PS/2 keyboards ( +atkbd(4) +driver)
+USB keyboards ( +ukbd(4) +driver)
+Loran-C receiver (Dave Mills experimental hardware, loran driver).
+ +Pointing devices including:
+ +Bus mice and compatible devices ( +mse(4) +driver)
+PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)
+Serial mice and compatible devices
+USB mice ( +ums(4) +driver)
+++Note: +moused(8) has +more information on using pointing devices with FreeBSD. Information on using pointing +devices with XFree86 can be found at http://www.xfree86.org/.
+
``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
+Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (xrpu driver).
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +++ +++This is a preliminary document. It is incomplete, and in need of additional content. +Please send additional information on IA-64 processors, motherboards, and various devices +working on FreeBSD to the FreeBSD IA64 +porting mailing list.
+
This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +IA-64 hardware platform (also referred to as FreeBSD/ia64 5.2-RELEASE). It lists devices +known to work on this platform, as well as some notes on boot-time kernel customization +that may be useful when attempting to configure support for new devices.
+ +++Note: This document includes information specific to the IA-64 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
More information on FreeBSD/ia64 is contained on the FreeBSD/ia64 +Project page.
+Currently supported processors are the Itanium +and the Itanium +2.
+ +Supported chipsets include:
+ +HP zx1 (only on development branch, see the Perforce repository)
+HP i2000
+Intel 460GX
+Intel E8870
+Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are under +active development. At this time, SMP-enabled systems are considered less stable. The +current priorities are UP fixes to improve stability.
+ +This section contains additional information about what devices may or may not be +supported by FreeBSD/ia64.
+ +Except for the PC chipset embedded +ata(4) +controllers, most should work out of the box. Eventually, all ia64-compatible ATA +controllers are expected to be fully supported. Refer to the following sections for +various disk controllers and their current status.
+ +In general, ``PC standard'' serial ports supported by the +sio(4) driver +are expected to work on Intel legacy machines, but not PA legacy machines. The reason is +that all devices on HP machines are memory-mapped and there is no ISA device support other than the PCI dictated VGA +legacy.
+ +In addition to +sio(4) devices, +the following devices fail on non-Intel legacy machines (but should work on boxes with an +Intel legacy) because their drivers make ISA-specific assumptions that do not hold:
+ +| +sio(4) | +No support for memory-mapped I/O | +
| +syscons(4) | +Expect BIOS, VGA probes, etc. | +
| +pcm(4) | +Probes MSS ISA ports ad +nauseum | +
| +atkbd(4), +psm(4) | +Fixed ISA port locations | +
This section describes the devices currently known to be supported by with FreeBSD on +the IA-64 platform. Other configurations may also work, but simply have not been tested +yet. Feedback, updates, and corrections to this list are encouraged.
+ +Where possible, the drivers applicable to each device or class of devices is listed. +If the driver in question has a manual page in the FreeBSD base distribution (most +should), it is referenced here. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+Qlogic controllers and variants ( +isp(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+ATAPI IDE interface ( +acd(4))
+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 Broadcom BCM570x ( +bge(4) +driver)
+ +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)
+``PC standard'' 8250, 16450, and 16550-based serial ports ( +sio(4) +driver)
+ +PCI-Based multi-port serial boards ( +puc(4) +driver)
+ +Diva Serial (GSP) Multiport UART (development branch only)
+OHCI 1.0-compliant host controllers ( +ohci(4) +driver)
+ +UHCI 1.1-compliant host controllers ( +uhci(4) +driver)
+ +USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)
+VGA-compatible video cards ( +vga(4) +driver)
+ +++Note: Information regarding specific video cards and compatibility with XFree86 can be found at http://www.xfree86.org/.
+
Keyboards including:
+ +PS/2 keyboards ( +atkbd(4) +driver)
+Pointing devices including:
+ +PS/2 mice and compatible devices, including many laptop pointing devices ( +psm(4) +driver)
+Serial mice and compatible devices
+++Note: +moused(8) has +more information on using pointing devices with FreeBSD. Information on using pointing +devices with XFree86 can be found at http://www.xfree86.org/.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +NEC PC-98x1 hardware platform (also referred to as FreeBSD/pc98 5.2-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.
+ +++Note: This document includes information specific to the NEC PC-98x1 hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
NEC PC-9801/9821 series with almost all i386-compatible processors, including 80386, +80486, Pentium, Pentium Pro, Pentium II, and variants. All i386-compatible processors by +AMD, Cyrix, IBM, and IDT are also supported.
+ +NEC FC-9801/9821 series, and NEC SV-98 series (both of them are compatible with +PC-9801/9821 series) should be supported.
+ +EPSON PC-386/486/586 series, which are compatible with NEC PC-9801 series are +supported.
+ +High-resolution mode is not supported. NEC PC-98XA/XL/RL/XL^2, and NEC PC-H98 series +are supported in normal (PC-9801 compatible) mode only.
+ +Although there are some multi-processor systems (such as Rs20/B20), SMP-related +features of FreeBSD are not supported yet.
+ +PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE expansion bus (110pin), and PCI +bus are supported. New Extend Standard Architecture (NESA) bus (used in PC-H98, SV-H98, +and FC-H98 series) is not supported.
+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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+IDE/ATA controllers (wdc driver)
+ +On-board IDE controller
+Adaptec AIC-6260 and AIC-6360 based boards ( +aic(4) +driver)
+ +Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host +adapters ( +ahc(4) +driver)
+ +NEC PC-9801-55, 92 and their compatible C-Bus SCSI interfaces (ct 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.
+
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) 53C8XX and 53C10XX PCI SCSI controllers, either embedded on motherboard or on +add-on boards ( +ncr(4) and +sym(4) +drivers)
+ +NCR 53C500 based PC-Card SCSI host adapters ( +ncv(4) +driver)
+ +TMC 18C30, 18C50 and 36C70 (AIC-6820) based ISA/PC-Card SCSI host adapters ( +stg(4) +driver)
+ +Qlogic controllers and variants ( +isp(4) +driver)
+ +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(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+ATAPI IDE interface ( +acd(4))
+Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast +Ethernet controller chip ( +sf(4) +driver)
+ +Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets +( +ti(4) +driver)
+ +AMD PCnet NICs ( +lnc(4) and +pcn(4) +drivers)
+ +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)
+ +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)
+ +Winbond W89C840F Fast Ethernet NICs ( +wb(4) +driver)
+ +VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine II'', and VT6105/VT6105M +``Rhine III'' Fast Ethernet NICs ( +vr(4) +driver)
+ +Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83815 Fast Ethernet NICs ( +sis(4) +driver)
+ +National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs ( +nge(4) +driver)
+ +Sundance Technologies ST201 PCI Fast Ethernet NICs ( +ste(4) +driver)
+ +SysKonnect SK-984x PCI Gigabit Ethernet cards ( +sk(4) +driver)
+ +Texas Instruments ThunderLAN PCI NICs ( +tl(4) +driver)
+ +DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus ( +dc(4) +driver)
+ +ADMtek Inc. AN986-based USB Ethernet NICs ( +aue(4) +driver)
+ +CATC USB-EL1210A-based USB Ethernet NICs ( +cue(4) +driver)
+ +Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs ( +kue(4) +driver)
+ +ASIX Electronics AX88172-based USB Ethernet NICs ( +axe(4) +driver)
+ +RealTek RTL8150-based USB Ethernet NICs ( +rue(4) +driver)
+ +DEC DC21040, DC21041, DC21140, DC21141, DC21142, and DC21143 based NICs ( +de(4) +driver)
+ +Fujitsu MB86960A/MB86965A based Fast Ethernet NICs ( +fe(4) +driver)
+ +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
+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 Etherlink XL-based NICs ( +xl(4) +driver)
+ +3Com 3C59X series NICs ( +vx(4) +driver)
+ +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)
+ +Ethernet and Fast Ethernet NICs based on the 3Com 3XP Typhoon/Sidewinder (3CR990) +chipset ( +txp(4) +driver)
+ +Gigabit Ethernet NICs based on the Broadcom BCM570x ( +bge(4) +driver)
+ +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)
+ +Myson Ethernet NICs ( +my(4) +driver)
+ +RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based PCI Fast Ethernet and Gigabit +Ethernet controllers ( +re(4) +driver)
+Efficient Networks, Inc. ENI-155p ATM PCI Adapters (hea driver)
+ +FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)
+ +IDT NICStAR 77201/211-based ATM Adapters ( +idt(4) +driver)
+ +FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)
+ +IDT77252-based ATM cards ( +patm(4) +driver)
+Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes +using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and +Symbol Spectrum24 chipsets ( +wi(4) +driver)
+ +Cisco/Aironet 802.11b wireless adapters ( +an(4) +driver)
+ +Raytheon Raylink 2.4GHz wireless adapters ( +ray(4) +driver)
+ +AMD Am79C930 and Harris (Intersil) based 802.11b cards ( +awi(4) +driver)
+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.
+
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)
+ +MPU-401 and compatible interfaces (mpu driver)
+ +Q-Vision WaveStar
+Brooktree Bt848/849/878/879-based frame grabbers ( +bktr(4) +driver)
+A range of USB peripherals are supported; devices known to work are listed in this +section. Owing to the generic nature of most USB devices, with some exceptions any device +of a given class will be supported, even if not explicitly listed here.
+ +++Note: USB Ethernet adapters can be found in the section listing Ethernet interfaces.
+
++Note: USB Bluetooth adapters can be found in Bluetooth +section.
+
OHCI 1.0-compliant host controllers ( +ohci(4) +driver)
+ +UHCI 1.1-compliant host controllers ( +uhci(4) +driver)
+ +USB 2.0 controllers using the EHCI interface ( +ehci(4) +driver)
+ +Hubs
+ +Keyboards ( +ukbd(4) +driver)
+ +Miscellaneous
+ +Assist Computer Systems PC Camera C-M1
+ActiveWire I/O Board
+Creative Technology Video Blaster WebCam Plus
+Diamond Rio 500, 600, and 800 MP3 players ( +urio(4) +driver)
+D-Link DSB-R100 USB Radio ( +ufm(4) +driver)
+Mirunet AlphaCam Plus
+Modems ( +umodem(4) +driver)
+ +3Com 5605
+Metricom Ricochet GS USB wireless modem
+Yamaha Broadband Wireless Router RTW65b
+Mice ( +ums(4) +driver)
+ +Printers and parallel printer conversion cables ( +ulpt(4) +driver)
+ +ATen parallel printer adapter
+Belkin F5U002 parallel printer adapter
+Canon BJ F850, S600
+Canon LBP-1310, 350
+Entrega USB-to-parallel printer adapter
+Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)
+Oki Data MICROLINE ML660PS
+Seiko Epson PM-900C, 880C, 820C, 730C
+Serial devices ( +ubsa(4), +uftdi(4) and +uplcom(4) +drivers)
+ +Scanners (through SANE) ( +uscanner(4) +driver)
+ +Storage ( +umass(4) +driver)
+ +ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M
+Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20
+FujiFilm Zip USB Drive ZDR100 USB A
+GREEN HOUSE USB Flash Memory ``PicoDrive'' GH-UFD32M, 64M, 128M
+IBM 32MB USB Memory Key (P/N 22P5296)
+IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)
+I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)
+I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM +only)
+Iomega USB Zip 100Mb (primitive support still)
+Iomega Zip750 USB2.0 Drive
+Keian USB1.1/2.0 3.5-inch HDD Case KU350A
+Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0
+Logitec USB1.1/2.0 HDD Unit SHD-E60U2
+Logitec Mobile USB Memory LMC-256UD
+Logitec USB Double-Speed Floppy Drive LFD-31U2
+Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)
+Matshita CF-VFDU03 floppy drive
+MELCO USB2.0 MO Drive MO-CH640U2
+I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI
+MELCO USB Flash Disk ``PetitDrive'', RUF-32M, -64M, -128M, -256M
+MELCO USB2.0 Flash Disk ``PetitDrive2'', RUF-256M/U2, -512M/U2
+MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, -C64M, -C128M, -C256M, -C512M
+Microtech USB-SCSI-HD 50 USB to SCSI cable
+NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U
+Panasonic floppy drive
+Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)
+RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B
+Sony Portable CD-R/RW Drive CRX10U (CDROM only)
+TEAC Portable USB CD-ROM Unit CD-110PU/210PU
+Y-E Data floppy drive (720/1.44/2.88Mb)
+Audio Devices ( +uaudio(4) +driver)
+ +Handspring Visor and other PalmOS devices ( +uvisor(4) +driver)
+ +Handspring Visor
+Palm M125, M500, M505
+Sony Clie 4.0 and 4.1
+PCCARD Host Controllers ( +ng_bt3c(4) +driver)
+ +3Com/HP 3CRWB6096-A PCCARD adapter
+USB Host Controllers ( +ng_ubt(4) +driver)
+ +3Com 3CREB96
+EPoX BT-DG02
+Mitsumi USB Bluetooth adapter
+MSI MS-6967
+TDK Bluetooth USB adapter
+Accelerators based on the Hifn 7751, 7811, or 7951 chipsets ( +hifn(4) +driver)
+ +Accelerators based on the SafeNet 1141 or 1741 cryptographic accelerator chipsets ( +safe(4) +driver)
+ +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)
+FAX-Modem/PCCARD
+ +MELCO IGM-PCM56K/IGM-PCM56KH
+Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)
+Floppy drives ( +fdc(4) +driver)
+ +Keyboards including:
+ +Standard keyboards
+USB keyboards ( +ukbd(4) +driver)
+Pointing devices including:
+ +Bus mice and compatible devices ( +mse(4) +driver)
+Serial mice and compatible devices
+USB mice ( +ums(4) +driver)
+++Note: +moused(8) has +more information on using pointing devices with FreeBSD. Information on using pointing +devices with XFree86 can be found at http://www.xfree86.org/.
+
``PC-9821 standard'' parallel ports ( +ppc(4) +driver)
+ +Joystick port of SoundBlaster(98) ( +joy(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)
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the +UltraSPARC hardware platform (also referred to as FreeBSD/sparc64 5.2-RELEASE). It lists +devices known to work on this platform, as well as some notes on boot-time kernel +customization that may be useful when attempting to configure support for new +devices.
+ +++Note: This document includes information specific to the UltraSPARC hardware +platform. Versions of the hardware compatibility notes for other architectures will +differ in some details.
+
This section describes the systems currently known to be supported by FreeBSD on the +UltraSPARC platform. For background information on the various hardware designs see the +Sun System +Handbook.
+ +SMP is supported on all systems with more than 1 processor.
+ +If you have a system that is not listed here, it may not have been tested with FreeBSD +5.2-RELEASE. We encourage you to try it and send a note to the FreeBSD +SPARC porting mailing list with your results, including which devices work and which +do not.
+ +The following systems are fully supported by FreeBSD.
+ +Blade 100
+Blade 150
+Enterprise 220R
+Enterprise 250
+Enterprise 420R
+Enterprise 450
+Fire V100
+Fire V120
+Netra t1 105
+Netra T1 AC200/DC200
+Netra t 1100
+Netra t 1120
+Netra t 1125
+Netra t 1400/1405
+Netra 120
+Netra X1
+SPARCEngine Ultra AXi
+SPARCEngine Ultra AXmp
+Ultra 5
+Ultra 10
+Ultra 30
+Ultra 60
+Ultra 80
+The following systems are partially supported by FreeBSD. In particular the onboard +scsi controller in sbus systems is not supported.
+ +Enterprise 3500
+Enterprise 4500
+Ultra 1 Enterprise (1E for short)
+Ultra 2
+The following systems are not supported by FreeBSD. This may be due to lack of +processor support (UltraSPARC III), due to a quirk in the system design that makes +FreeBSD unstable, or due to lack of support for sufficient onboard devices to make +FreeBSD generally useful.
+ +All systems containing UltraSPARC III processor(s).
+Ultra 1
+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. Information on specific models of supported devices, +controllers, etc. can be found in the manual pages.
+ +++Note: Lists of specific, supported devices are gradually being removed from +this document in order to reduce the amount of duplicated (and potentially out-of-date) +information contained within. When this process is complete, the manual page for each +driver should be consulted for the authoritative list of devices supported that +particular driver.
+
IDE/ATA controllers ( +ata(4) +driver)
+ +Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6
+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, nForce2 ATA133
+Promise ATA100 OEM chip (pdc20265)
+Promise ATA133 OEM chip (pdc20269)
+Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 TX2/TX2000
+Promise SATA150 TX2/TX4 Serial ATA/150
+Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000
+ServerWorks ROSB4 ATA33
+ServerWorks CSB5 and CSB6 ATA66/ATA100
+Sil 0680 UDMA6
+SiS 530, 540, 550, 620
+SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735, +740, 745, 746, 748, 750, 751, 752, 755
+SiS 5591 ATA100
+VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, 82C686b ATA100
+VIA 8233, 8235 ATA133
+Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host +adapters ( +ahc(4) +driver)
+ +Ultra-320 SCSI controllers based on the Adaptec AIC7901, AIC7901A, and AIC7902 +Ultra320 controller chips ( +ahd(4) +driver)
+ +LSI/Symbios (formerly NCR) 53C8XX and 53C10XX PCI SCSI controllers, either embedded on motherboard or on +add-on boards ( +ncr(4) and +sym(4) +drivers)
+ +Qlogic controllers and variants ( +isp(4) +driver)
+ +LSI Logic Fusion/MP architecture Fiber Channel controllers ( +mpt(4) +driver)
+ +With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and +SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, +8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM +drives. WORM devices that support CD-ROM commands are supported for read-only access by +the CD-ROM drivers (such as +cd(4)). +WORM/CD-R/CD-RW writing support is provided by +cdrecord(1), +which is a part of the sysutils/cdrtools port in the Ports Collection.
+ +The following CD-ROM type systems are supported at this time:
+ +SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) ( +cd(4))
+ATAPI IDE interface ( +acd(4))
+RealTek 8129/8139 Fast Ethernet NICs ( +rl(4) +driver)
+ +DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus ( +dc(4) +driver)
+ +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
+3Com Etherlink XL-based NICs ( +xl(4) +driver)
+ +Sun HME and QFE Ethernet NICs ( +hme(4) +driver)
+ +Sun GEM (Gigabit Ethernet) and ERI (Fast Ethernet) NICs ( +gem(4) +driver)
+FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and +fatm(4) +drivers)
+ +FORE Systems, Inc. HE155 and HE622 ATM interfaces ( +hatm(4) +driver)
+Serial ports based on the SAB82532 serial chip, console only ( +sab(4) +driver)
+ +Serial ports based on the Zilog 8530 dual uart, console only (zs driver)
+Host Controllers ( +fwohci(4) +driver)
+ +Serial Bus Protocol 2 (SBP-2) storage devices ( +sbp(4) +driver)
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
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.
+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 most CDROM or network installations, all you need to copy onto actual floppies +from the floppies/ directory are the kern.flp and mfsroot.flp images (for +1.44MB floppies). Depending on your hardware, you may also need to make the third drivers.flp image to provide necessary device drivers.
+ +Getting these images over the network is easy. Simply fetch the release/floppies/kern.flp, release/floppies/mfsroot.flp, and +release/floppies/drivers.flp +files from ftp://ftp.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.
+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.
+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 ++ +
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.
+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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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.
+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.
+No. FreeBSD, like Compaq Tru64 and VMS, will only boot from the SRM +console.
+Unfortunately, yes.
+FreeBSD can run Tru64 applications very well using the emulators/osf1_base port/package.
+FreeBSD can run AlphaLinux binaries with the assistance of the emulators/linux_base port/package.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
FreeBSD for the AMD64 requires an Athlon64, Athlon64-FX, Opteron or better processor +to run.
+ +If you have an machine based on an nVidia nForce3 Pro-150, you MUST use the BIOS setup +to disable the IO APIC. If you do not have an option to do this, you will likely have to +disable ACPI instead. There are bugs in the Pro-150 chipset that we have not found a +workaround for yet.
+ +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.
+Floppy disk based install is not supported on FreeBSD/amd64.
+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.
+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.
+ +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.
+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.
+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:\BASE C:\FREEBSD\BASE ++ +
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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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/amd64/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.
+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.
+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.
+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.
+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 ++
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 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.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
FreeBSD for the i386 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.
+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 most CDROM or network installations, all you need to copy onto actual floppies +from the floppies/ directory are the kern.flp and mfsroot.flp images (for +1.44MB floppies). Depending on your hardware, you may also need to make the third drivers.flp image to provide necessary device drivers.
+ +Getting these images over the network is easy. Simply fetch the release/floppies/kern.flp, release/floppies/mfsroot.flp, and +release/floppies/drivers.flp +files from ftp://ftp.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).
+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.
+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.
+ +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.
+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.
+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:\BASE C:\FREEBSD\BASE ++ +
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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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.
+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.
+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.
+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.
+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 ++
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 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.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.1. My system hangs while probing +hardware during boot, or it behaves strangely during install, or the floppy drive isn't +probed.
+FreeBSD 5.0 and above makes extensive use of the system ACPI service on the +i386 platform to aid in system configuration if it's detected during boot. Unfortunately, +some bugs still exist in both the ACPI driver and within system motherboards and BIOS. +The use of ACPI can be disabled by setting the ``hint.acpi.0.disabled'' hint in the third +stage boot loader:
+ ++set hint.acpi.0.disabled="1" ++ +
This is reset each time the system is booted, so it is necessary to add hint.acpi.0.disabled="1" to the file /boot/loader.conf. More information about the boot loader can be +found in the FreeBSD Handbook.
+4.2.2. My legacy ISA device used to be +recognized in previous versions of FreeBSD, but now it's not. What happened?
+Some device drivers, like matcd, were removed over time due to lack of +maintainership or other reasons. Others still exist but are disabled because of their +intrusive hardware probe routines. The following ISA device drivers fall into this +category and can re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed, cs, +sn, ie, fe, le, and lnc. To do this, stop the loader during it's 10 second countdown and +enter the following at the prompt:
+ ++unset hint.foo.0.disabled ++ +
where foo is the name of the driver to re-enable. This +can be set permanently by editing the file /boot/device.hints +and removing the appropriate ``disabled'' entry.
+4.2.3. 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.4. 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.5. 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.
+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.7. 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'.)
+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.9. 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.10. 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.
+FreeBSD does not support this controller.
+4.2.12. 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.13. When installing on a 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.14. 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.15. 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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
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.
+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.
+ +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.
+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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
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.
+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, release/floppies/mfsroot.flp, and +release/floppies/drivers.flp +files from ftp://ftp.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).
+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.
+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.
+ +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.
+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.
+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:\BASE A:\FREEBSD\BASE ++ +
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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ ++ ++ +
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.2-RELEASE +distribution and to beginning the installation procedure. The ``Installing FreeBSD'' chapter of the FreeBSD +Handbook provides more in-depth information about the installation program itself, +including a guided walkthrough with screenshots.
+ +If you are upgrading from a previous release of FreeBSD, please see Section 3 for instructions on upgrading.
+ +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.
+
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.
+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) ++ +
At this point, place the CDROM into your drive, and from the PROM prompt, type boot cdrom.
+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.
+ +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.
+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.
+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.
+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.
+ +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.
+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.
+
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.
+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.
+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.
+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 ++
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.2-RELEASE from FreeBSD 4-STABLE are not +supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence +can be disruptive, but are not removed by a binary upgrade. One notable example is that +an old /usr/include/g++ directory will cause C++ programs to +compile incorrectly (or not at all).
+ + + +These upgrade instructions are provided for the use of users upgrading from relatively +recent FreeBSD 5-CURRENT snapshots.
+
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.
+ +Upgrading of a distribution is performed by extracting the new version of the +component over the top of the previous version. Files belonging to the old distribution +are not deleted.
+ +System configuration is preserved by retaining and restoring the previous version of +the following files:
+ +Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, motd, namedb, networks, newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp
+ +The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new +versions and merge components as desired. Note that many of these files are +interdependent, and the best merge procedure is to copy all site-specific data from the +current files into the new.
+ +During the upgrade procedure, the administrator is prompted for a location into which +all files from /etc/ are saved. In the event that local +modifications have been made to other files, they may be subsequently retrieved from this +location.
+This section details the upgrade procedure. Particular attention is given to items +which substantially differ from a normal installation.
+ +User data and system configuration should be backed up before upgrading. While the +upgrade procedure does its best to prevent accidental mistakes, it is possible to +partially or completely destroy data and configuration information.
+The disklabel editor is entered with the nominated disk's filesystem devices listed. +Prior to commencing the upgrade, the administrator should make a note of the device names +and corresponding mountpoints. These mountpoints should be entered here. Do not set the ``newfs flag'' for any +filesystems, as this will cause data loss.
+When selecting distributions, there are no constraints on which must be selected. As a +general rule, the base distribution should be selected for an +update, and the man distribution if manpages are already +installed. Other distributions may be selected beyond those originally installed if the +administrator wishes to add additional functionality.
+Once the installation procedure has completed, the administrator is prompted to +examine the new configuration files. At this point, checks should be made to ensure that +the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should +be checked.
+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.
+ + +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.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.27
+2003/09/08 14:53:02 simon Exp $
+
FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to +change soon.
+ +Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.
+ +Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group +are trademarks of The Open Group in the United States and other countries.
+ +Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc +in the United States and other countries. Products bearing SPARC trademarks are based +upon architecture developed by Sun Microsystems, Inc.
+ +Many of the designations used by manufacturers and sellers to distinguish their +products are claimed as trademarks. Where those designations appear in this document, and +the FreeBSD Project was aware of the trademark claim, the designations have been followed +by the ``™'' or the ``®'' symbol.
++ ++ +
This distribution is a release of FreeBSD 5.2-RELEASE, the latest point along the +5-CURRENT branch.
+ +FreeBSD is an operating system based on 4.4 BSD Lite for Intel, AMD, Cyrix or NexGen +``x86'' based PC hardware (i386™), NEC PC-9801/9821 +series PCs and compatibles (pc98), DEC/Compaq/HP Alpha computers (alpha), and UltraSPARC® machines (Sparc64®). Versions for the IA64 (ia64), PowerPC® (PowerPC), and AMD +``Hammer'' (amd64) architectures are currently under development as well. FreeBSD works +with a wide variety of peripherals and configurations and can be used for everything from +software development to games to Internet Service Provision.
+ +This release of FreeBSD contains everything you need to run such a system, including +full source code for the kernel and all utilities in the base distribution. With the +source distribution installed, you can literally recompile the entire system from scratch +with one command, making it ideal for students, researchers, or users who simply want to +see how it all works.
+ +A large collection of third-party ported software (the ``Ports Collection'') is also +provided to make it easy to obtain and install all your favorite traditional UNIX® utilities for FreeBSD. Each ``port'' consists of a set +of scripts to retrieve, configure, build, and install a piece of software, with a single +command. Over 10,000 ports, from editors to programming languages to graphical +applications, make FreeBSD a powerful and comprehensive operating environment that +extends far beyond what's provided by many commercial versions of UNIX. Most ports are also available as pre-compiled +``packages'', which can be quickly installed from the installation program.
+This release of FreeBSD is suitable for all users. It has undergone a period of +testing and quality assurance checking to ensure the highest reliability and +dependability.
+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.
+ +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.
+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.
+For any questions or general technical support issues, please send mail to the FreeBSD +general questions mailing list.
+ +If you're tracking the 5-CURRENT development efforts, you must join the FreeBSD-CURRENT mailing list, 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.
+ +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.
+ +All of the mailing lists can be freely joined by anyone wishing to do so. Visit the FreeBSD Mailman Info +Page. 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 from the Mailman pages or the +mailing lists +section of the FreeBSD Web site.
+ +++Important: Do not send +email to the lists asking to be subscribed. Use the Mailman interface instead.
+
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. ``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.
+ +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.
+There are many sources of information about FreeBSD; some are included with this +distribution, while others are available on-line or in print versions.
+ +A number of other files provide more specific information about this release +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.2-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.2-RELEASE compared to the previous release (FreeBSD +5.1-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 alpha, i386, ia64, pc98, and Sparc64), 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).
+
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 give 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).
+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.
+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 +release. 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 release simply would not have been possible.
+This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE 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.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +The +puc(4) PCI +Universal Communications driver now supports connecting parallel ports to the +ppc(4) +driver.
+ +The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ + + + + +The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +A number of utilities available in /bin and /sbin are now available as a statically-linked ``crunched'' binary +that lives in /rescue. This functionality is similar to the /stand directory installed by +sysinstall(8), +but /rescue includes more functionality and is updated as part +of buildworld/installworld +operations. More details can be found in +rescue(8).
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+Floppy disk installation images are no longer built for the alpha, amd64, and ia64 +architectures.
+ +The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE on the AMD64 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The +acpi(4) driver's +CPU component now supports idle states C1-C3 for both single and SMP systems, providing +power/heat savings when the processor is idle, according to ACPI 2.0. Additionally, the +throttling support has been updated to ACPI 2.0.
+ +The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +The +puc(4) PCI +Universal Communications driver now supports connecting parallel ports to the +ppc(4) +driver.
+ +The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ + + + + +The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +A number of utilities available in /bin and /sbin are now available as a statically-linked ``crunched'' binary +that lives in /rescue. This functionality is similar to the /stand directory installed by +sysinstall(8), +but /rescue includes more functionality and is updated as part +of buildworld/installworld +operations. More details can be found in +rescue(8).
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+Floppy disk installation images are no longer built for the alpha, amd64, and ia64 +architectures.
+ +The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE on the i386 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The +acpi(4) driver's +CPU component now supports idle states C1-C3 for both single and SMP systems, providing +power/heat savings when the processor is idle, according to ACPI 2.0. Additionally, the +throttling support has been updated to ACPI 2.0.
+ +A bug that caused +atkbd(4) to +register an AT keyboard during console initialization, even when no AT keyboard was +connected, has been fixed. kbdcontrol -k /dev/kbd1 is no longer +needed when only a USB keyboard is connected. [MERGED]
+ +The +cx(4) driver for +Cronyx-Sigma serial interfaces has been overhauled. As a part of this update, the +cxconfig userland configuration utility has been replaced by a newer +sconfig(8) +utility.
+ +The DRM kernel modules have been updated from DRI CVS as of 12 November 2003. Among +other changes, this change includes a newly-ported SiS 300/305/540/630/730 driver and +mostly-complete SMPng locking.
+ +The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +The +hifn(4) driver +now supports symmetric crypto for the 7955 and 7956 chipsets. [MERGED]
+ +The +puc(4) PCI +Universal Communications driver now supports connecting parallel ports to the +ppc(4) +driver.
+ +The +safe(4) driver +has been added to support SafeNet 1141- and 1741-based crypto accelerators. [MERGED]
+ +++Warning: This driver should be considered experimental and and should be used +with some caution.
+
++Note: The public key support is not implemented.
+
The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ +Large changes have been made to the i386 machine-dependent code to improve interrupt +routing and handling, as well as SMP support. Two major user-visible changes are that SMP +kernels can run on UP systems and that SMP functionality is now enabled by default in the +GENERIC kernel. Also, the options +APIC_IO kernel option has been replaced by device +apic.
+ +An integer overflow that could cause kernel panics on PAE machines of certain large +memory sizes has been corrected.
+ +Floating point emulation in the kernel has been removed.
+ +Problems with some Pentium 4 CPUs and some older Pentium Pro and Pentium II CPUs have +been worked around. Typically these manifested themselves as memory corruption or +unexplained crashes.
+ +Logical CPUs (with HyperThreading) are now enabled according to BIOS settings +(previously, they were disabled by default and had to be enabled explicitly).
+The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +harp(4) driver +has been added. This is a pseudo physical interface driver for HARP, which attaches to +all NetGraph ATM interfaces in the system and presents a physical interface to the HARP +stack for each of these interfaces.
+ +The +hatm(4) driver +has been added to support Fore/Marconi HE155 and HE622 ATM cards.
+ +The hfa driver has been updated to firmware version 4.1.12 and now supports a limited +number of CBR channels.
+ +The +patm(4) driver +has been added to support IDT77252 based ATM interfaces.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +matcd(4) driver, +which supports the Matsushita CR-562 and CR-563 CD drives, has returned.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
+The last bits of the i386-only, a.out compiler toolchain have been removed.
+ ++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +asf(8) utility, +which helps load the symbol files from KLDs into a +gdb(1) debugging +environment, has been added.
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +The libthr 1:1 threading library is now built by +default.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +A number of utilities available in /bin and /sbin are now available as a statically-linked ``crunched'' binary +that lives in /rescue. This functionality is similar to the /stand directory installed by +sysinstall(8), +but /rescue includes more functionality and is updated as part +of buildworld/installworld +operations. More details can be found in +rescue(8).
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE on the IA-64 hardware +platform. It describes recently added, changed, or deleted features of FreeBSD. It also +provides some notes on upgrading from previous versions of FreeBSD.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The +acpi(4) driver's +CPU component now supports idle states C1-C3 for both single and SMP systems, providing +power/heat savings when the processor is idle, according to ACPI 2.0. Additionally, the +throttling support has been updated to ACPI 2.0.
+ +The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +The +puc(4) PCI +Universal Communications driver now supports connecting parallel ports to the +ppc(4) +driver.
+ +The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ + + + + +The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +libkse is now the default threading library on +FreeBSD/ia64.
+ +The libthr 1:1 threading library is now built by +default.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+Floppy disk installation images are no longer built for the alpha, amd64, and ia64 +architectures.
+ +The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE 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.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The DRM kernel modules have been updated from DRI CVS as of 12 November 2003. Among +other changes, this change includes a newly-ported SiS 300/305/540/630/730 driver and +mostly-complete SMPng locking.
+ +The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +The +hifn(4) driver +now supports symmetric crypto for the 7955 and 7956 chipsets. [MERGED]
+ +The +puc(4) PCI +Universal Communications driver now supports connecting parallel ports to the +ppc(4) +driver.
+ +The +safe(4) driver +has been added to support SafeNet 1141- and 1741-based crypto accelerators. [MERGED]
+ +++Warning: This driver should be considered experimental and and should be used +with some caution.
+
++Note: The public key support is not implemented.
+
The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ +Large changes have been made to the i386 machine-dependent code to improve interrupt +routing and handling.
+ +Floating point emulation in the kernel has been removed.
+ +Problems with some Pentium 4 CPUs and some older Pentium Pro and Pentium II CPUs have +been worked around. Typically these manifested themselves as memory corruption or +unexplained crashes.
+The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +harp(4) driver +has been added. This is a pseudo physical interface driver for HARP, which attaches to +all NetGraph ATM interfaces in the system and presents a physical interface to the HARP +stack for each of these interfaces.
+ +The +hatm(4) driver +has been added to support Fore/Marconi HE155 and HE622 ATM cards.
+ +The +patm(4) driver +has been added to support IDT77252 based ATM interfaces.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
+The last bits of the i386-only, a.out compiler toolchain have been removed.
+ ++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +asf(8) utility, +which helps load the symbol files from KLDs into a +gdb(1) debugging +environment, has been added.
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +A number of utilities available in /bin and /sbin are now available as a statically-linked ``crunched'' binary +that lives in /rescue. This functionality is similar to the /stand directory installed by +sysinstall(8), +but /rescue includes more functionality and is updated as part +of buildworld/installworld +operations. More details can be found in +rescue(8).
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project
+ +$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
+1.663.2.3 2003/12/20 17:58:57 bmah Exp $
+
The release notes for FreeBSD 5.2-RELEASE contain a summary of recent changes made to +the FreeBSD base system on the 5-CURRENT development branch. This document lists +applicable security advisories that were issued since the last release, as well as +significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading +are also presented.
+This document contains the release notes for FreeBSD 5.2-RELEASE on the UltraSPARC +hardware platform. It describes recently added, changed, or deleted features of FreeBSD. +It also provides some notes on upgrading from previous versions of FreeBSD.
+ +This distribution of FreeBSD 5.2-RELEASE is a release distribution. It can be found at +ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/ or any of its +mirrors. More information on obtaining this (or other) release distributions of FreeBSD +can be found in the ``Obtaining FreeBSD'' appendix to the FreeBSD +Handbook.
+ +Users who are new to the 5-CURRENT series of FreeBSD releases should also read the +``Early Adopters Guide to FreeBSD 5.2-RELEASE''. This document can generally be found in +the same location as the release notes (either as a part of a FreeBSD distribution or on +the FreeBSD Web site). It contains important information regarding the advantages and +disadvantages of using FreeBSD 5.2-RELEASE, as opposed to releases based on the FreeBSD +4-STABLE development branch.
+ +All users are encouraged to consult the release errata before installing FreeBSD. The +errata document is updated with ``late-breaking'' information discovered late in the +release cycle or after the release. Typically, it contains information on known bugs, +security advisories, and corrections to documentation. An up-to-date copy of the errata +for FreeBSD 5.2-RELEASE can be found on the FreeBSD Web site.
+This section describes many of the user-visible new or changed features in FreeBSD +since 5.1-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 +5.1-RELEASE). The latter items are marked as [MERGED].
+ +Typical release note items document recent security advisories issued after +5.1-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, +or contributed software upgrades. They may also list changes to major ports/packages or +release engineering practices. Clearly the release notes cannot list every single change +made to FreeBSD between releases; this document focuses primarily on security advisories, +user-visible changes, and major architectural improvements.
+ +A single-byte buffer overflow in +realpath(3) was +fixed. Although the fix was committed prior to FreeBSD 5.1-RELEASE (and thus 5.1-RELEASE +was not affected), it was not noted in the release documentation. See security advisory +FreeBSD-SA-03:08. [MERGED]
+ +A bug that could allow the kernel to attempt delivery of invalid signals has been +fixed. The bug could have led to a kernel panic or, under some circumstances, +unauthorized modification of kernel memory. For more information, see security advisory +FreeBSD-SA-03:09. [MERGED]
+ +A bug in the iBCS2 emulation module, which could result in disclosing the contents of +kernel memory, has been fixed. This module is not enabled in FreeBSD by default. For more +information, see security advisory FreeBSD-SA-03:10. [MERGED]
+ +A buffer management bug in OpenSSH, which could potentially +cause a crash, has been fixed. More information can be found in security advisory FreeBSD-SA-03:12. [MERGED]
+ +A buffer overflow in sendmail has been fixed. More +information can be found in security advisory FreeBSD-SA-03:13. [MERGED]
+ +A bug that could allow the kernel to cause resource starvation which eventually +results in a system panic in the ARP cache code has been fixed. More information can be +found in security advisory FreeBSD-SA-03:14. [MERGED]
+ +Several errors in the OpenSSH PAM challenge/response +authentication subsystem have been fixed. The impacts of these bugs vary; details can be +found in security advisory FreeBSD-SA-03:15. [MERGED]
+ +A bug in +procfs(5) and +linprocfs(5), +which could result in disclosing the contents of kernel memory, has been fixed. More +information can be found in security advisory FreeBSD-SA-03:17. [MERGED]
+ +Four separate security flaws in OpenSSL, which could allow +a remote attacker to crash an OpenSSL-using application or to +execute arbitrary code with the privileges of the application, have been fixed. More +information can be found in security advisory FreeBSD-SA-03:18. [MERGED]
+ +A potential denial of service in BIND has been fixed. For +more information, see security advisory FreeBSD-SA-03:19. [MERGED]
+The +dcons(4) ``dumb +console'' driver has been added to provide a local and remote console. It can be accessed +over FireWire using the +dcons_crom(4) +driver. A +dconschat(8) +utility provides user access to +dcons(4) +devices.
+ +A multi-byte character set conversion method is now supported by the LIBICONV kernel option.
+ +A new OFW PCI framework, conditional on the OFW_NEWPCI +kernel configuration option, has been added. This addition improves the handling of PCI +busses. One user-visible change is that the enumeration of devices is closer to Solaris™ (as a result of this change, the numbering of +devices may change if more than one unit of a device type is present). The OFW_NEWPCI kernel configuration is enabled by default in the GENERIC kernel.
+ +The +syscons(4) +driver now has support for FreeBSD/sparc64. Installation on the system console should now +be supported, and systems with Creator3D graphics cards (e.g. Ultra 30) can now run XFree86.
+ +The +uart(4) driver +has been added to support various classes of UART (Universal Asynchronous +Receiver/Transmitter) devices. It is an analog of the +sio(4) driver +but supports a wider range of devices. This driver is necessary to support serial ports +on certain architectures, such as ia64 and sparc64.
+ +A kernel software watchdog facility has been implemented. For more information, see +watchdog(4) and + +watchdogd(8).
+ +The swap pager has been revamped. Among user-visible changes are a change in the +layout policy (from fixed-width striping to a round-robin across devices) for better I/O +throughput, the elimination of compile-time limits on the number of swap devices, and a +reduction in memory overheads.
+ + + + + +The new +ath(4) and +ath_hal(4) +drivers provide support for 802.11a/b/g devices based on the AR5210, AR5211, and AR5212 +chips.
+ +The +bfe(4) driver +has been added to support Broadcom BCM4401 based Fast Ethernet adapters.
+ ++bge(4) now +supports Broadcom 5705 based Gigabit Ethernet NICs. [MERGED]
+ +A bug in the +bge(4) driver +that prevented it from working correctly at 10 Mbps has been fixed.
+ +The +em(4) driver now +has support for tuning the interrupt delays using sysctl tunables without recompiling the +driver.
+ +The +fatm(4) driver +has been added. This is a driver for NATM and NgATM that supports Fore/Marconi PCA200 ATM +cards.
+ +The +harp(4) driver +has been added. This is a pseudo physical interface driver for HARP, which attaches to +all NetGraph ATM interfaces in the system and presents a physical interface to the HARP +stack for each of these interfaces.
+ +The +hatm(4) driver +has been added to support Fore/Marconi HE155 and HE622 ATM cards.
+ +The +patm(4) driver +has been added to support IDT77252 based ATM interfaces.
+ +The +re(4) driver has +been added. It provides support for the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S +PCI Fast Ethernet and Gigabit Ethernet controllers.
+ ++sk(4) now +supports SK-9521 V2.0 and 3COM 3C940 based Gigabit Ethernet NICs. [MERGED]
+ +A new +utopia(4) driver +supports 25MBit/sec, 155MBit/sec and 622MBit/sec ATM physical layer configuration, status +and statistics reporting for the most commonly used ATM-PHY chips.
+ +The suspend/resume support for the +wi(4) driver now +works correctly when the device is configured down. [MERGED]
+ +The +wi(4) driver +should once again work correctly with Lucent 802.11b interfaces.
+ +The 802.11 support layer has been rewritten to allow for future growth and new +features.
+ +The +xe(4) driver now +supports CE2, CEM28, and CEM33 cards, and +multicast(4) +datagrams. Also several bugs in the driver have been fixed.
+ +A number of network drivers have had their interrupt handlers marked as MPSAFE, +meaning they can run without the Giant lock. Among the drivers so converted are: +ath(4), +em(4), +ep(4), +fxp(4), +sn(4), +wi(4), and +sis(4).
+The ip_flow feature in the IPv4 protocol implementation has +been replaced by the ip_fastforward feature. ip_fastforward attempts to speed up simple cases of packet +forwarding, processing a forwarded packet to an outgoing interface without queues or +netisrs. If it cannot handle a particular packet, it passes that packet to the normal +ip_input routines for processing. This feature can be enabled +by setting the net.inet.ip.fastforwarding sysctl variable to +1.
+ +The IP_ONESBCAST option has been added to enable undirected + +ip(4) broadcasts +to be sent to specific network interfaces.
+ +Enabling the options IPFILTER feature also requires +enabling options PFIL_HOOKS.
+ +A bug in +ipfw(4) limit +rule processing that could cause various panics has been fixed. [MERGED]
+ ++ipfw(4) rules +now support comma-separated address lists (such as 1.2.3.4, +5.6.7.8/30, 9.10.11.12/22), and allow spaces after commas to make lists of +addresses more readable. [MERGED]
+ ++ipfw(4) rules +now support C++-style comments. Each comment is stored together with its rule and appears +using the +ipfw(8) show command. [MERGED]
+ ++ipfw(8) can now +modify +ipfw(4) rules in +set 31, which was read-only and used for the default rules. They can be deleted by ipfw delete set 31 command but are not deleted by the ipfw flush command. This implements a flexible form of ``persistent +rules''. More details can be found in +ipfw(8). +[MERGED]
+ +The +ng_atmpif(4) +NetGraph node type has been added. It emulates a HARP physical interface, and allows one +to run the HARP ATM stack without real hardware.
+ +Kernel support has been added for Protocol Independent Multicast routing ( +pim(4)). +[MERGED]
+ +To reduce information leakage, IPv4 packets no longer have an ip_id field set unless fragmentation is being done.
+ +The FreeBSD Bluetooth protocol stack has been updated:
+ +libsdp has been re-implemented under a BSD style license. +This is because the Linux BlueZ code is distributed under the GPL.
+The +hccontrol(8) +utility now supports four new commands: Read/Write_Page_Scan_Mode and +Read/Write_Page_Scan_Period_Mode.
+The +hcsecd(8) daemon +now stores link keys on a disk. It is no longer required to pair devices every time.
+A NetGraph timeout problem in the +ng_hci(4) and +ng_l2cap(4) +kernel modules, which could cause access to a data structure that was already freed, has +been fixed.
+The +ng_ubt(4) +module, which cannot be built on FreeBSD 5.1-RELEASE, has been fixed.
++rfcomm_sppd(1) +and +rfcomm_pppd(8) +now support to query the RFCOMM channel via SDP from the server. Specifying the RFCOMM +channel manually, this behavior can be disabled and these utilities will not use SDP +query.
+The +sdpcontrol(8) +utility, which is analogous to the sdptool utility in the Linux BlueZ SDP package, has +been added.
+A number of fixes and updates to the IPv6 and IPSec code have been imported from the +KAME Project.
+ +Support for the IPv6 Advanced Sockets API now conforms to RFC 3542 (also known as RFC +2292bis), rather than RFC 2292. Applications using this API have been updated +accordingly.
+ +Support for the source address selection part of RFC 3484 has been added. The +ip6addrctl(8) +utility can be used to configure the address selection policy.
+ +The tcp_hostcache feature has been added to the TCP +implementation. It caches measured parameters of past TCP sessions to provide better +initial start values for following connections from or to the same source or destination. +Similar information that used to be stored in the routing table has been removed.
+The +amr(4) driver +now has system crashdump support. [MERGED]
+ +A major rework of the +ata(4) driver +has been committed. One of the more notable changes is that the +ata(4) driver is +now out from under the Giant kernel lock. Note that ATA software RAID systems must now +include device ataraid in their kernel configuration files, as +it is no longer automatically implied by device atadisk.
+ ++ccd(4) can now +operate on raw disks and other +geom(4) +providers.
+ +The +da(4) driver no +longer tries to send 6-byte commands to USB and FireWire devices. The quirks for these +devices (which hopefully are now unnecessary) have been disabled; to restore the old +behavior, add options DA_OLD_QUIRKS to the kernel +configuration. [MERGED]
+ +Various +geom(4) modules +can now be loaded as kernel modules, namely: geom_apple, geom_bde, geom_bsd, geom_gpt, geom_mbr, geom_pc98, geom_sunlabel, geom_vol_ffs.
+ +A GEOM_FOX module has been added to detect and select +between multiple redundant paths to the same device.
+ +The +twe(4) driver +now supports the 3ware generic API. [MERGED]
+Multi-byte character conversion with the cd9660, msdosfs, ntfs, and udf filesystems is +now supported by including the CD9660_ICONV, MSDOSFS_ICONV, NTFS_ICONV, and UDF_ICONV kernel options, respectively.
+ +Some off-by-one errors in the smbfs that prevented it from working correctly with +15-character NetBIOS names have been fixed.
+ +The sizes of some members of the statfs structure have +changed from 32 bits to 64 bits in order to better support multi-terabyte +filesystems.
+ +Users performing source upgrades across this change must ensure that their kernel and +userland bits are in sync, by following the documented source upgrade procedures.
+A backward compatibility version of the +statfs(2) system +call exists but only if the COMPAT_FREEBSD4 kernel option is +defined. Including this option in the kernel is strongly encouraged.
+Programs that use the +statfs(2) will +need to be recompiled. Among the known examples are the devel/gnomevfs2, mail/postfix, and security/cfg ports.
+Support for NFSv4 has been added with the import of the University of Michigan's Citi +NFSv4 client implementation. More information can be found in the +mount_nfs4(8) +and +idmapd(8) manual +pages.
++acpiconf(8) now +supports a -i option to print battery information.
+ ++acpidb(8), an +ACPI DSDT debugger, has been added.
+ ++arp(8) now +supports a -i option to limit the scope of the current +operation to the ARP entries on a particular interface. This option applies to the +display operations only. It should be useful on routers with numerous network interfaces. +[MERGED]
+ +The +atmconfig(8) +program has been added for configuration of the ATM drivers and IP-over-ATM +functionality.
+ ++chroot(8) now +allows the optional setting of a user, primary group, or group list to use inside the +chroot environment via the -u, -g, +and -G options respectively. [MERGED]
+ +The compat4x.i386 libraries have been updated to correspond +to those available in FreeBSD 4.9-RELEASE.
+ +The dev_mkdb utility is unnecessary due to the mandatory presence of devfs, and has +been removed.
+ ++dhclient(8) now +polls the state of network interfaces and only sends DHCP requests on interfaces that are +up. The polling interval can be controlled with the -i +option.
+ +The default mode for the lost+found directory of +fsck(8) is now +0700 instead of 01777. [MERGED]
+ ++fsck_ffs(8) and + +newfs(8) now +create a .snap directory in the root directory of each +filesystem, with group operator. +fsck_ffs(8), +mksnap_ffs(8), +and +dump(8) will +write their filesystem snapshots to this directory. This change avoids locking access to +the root directory of a filesystem during snapshot creation and also helps non-root users create snapshots.
+ +The +ffsinfo(8) +utility has been updated to understand UFS2 filesystems and has been re-enabled.
+ +The +iasl(8) utility, +a compiler/decompiler for ACPI Source Language (ASL) and ACPI Machine language (AML), has +been added.
+ ++ifconfig(8) now +supports a staticarp option for an interface, which disables +the sending of ARP requests for that interface.
+ +A fix in the +initgroups(3) +library function now causes logins to fail if the login process is unable to successfully +set the process credentials to include all groups defined for a user. The current kernel limit is 16 +groups; administrators may wish to check that users do not have more than 16 groups +defined, or they will be unable to log in.
+ +The +ipfw(8) list and show commands now support +ranges of rule numbers. [MERGED]
+ ++ipfw(8) now +supports a -n flag to test the syntax of commands without +actually changing anything. [MERGED]
+ ++kdump(1) now +supports a -p option to display only the trace events +corresponding to a specific process, as well as a new -E flag +to display timestamps relative to the start of the dump.
+ ++last(1) now +supports a -n flag to limit the number of lines in its output +report.
+ +The libalias library, +natd(8), and +ppp(8) now +support Cisco Skinny Station protocol, which is the protocol used by Cisco IP phones to +talk to Cisco Call Managers. Note that currently having the Call Manager behind the NAT +gateway is not supported. [MERGED]
+ +The libcipher DES cryptography library has been removed. All +of its functionality is provided by the libcrypto library, and +all base systems programs that used libcipher have been +converted to use libcrypto instead.
+ +The libkiconv library has been added to support working with +loadable character set conversion tables in the kernel.
+ +libwrap and +tcpdchk(8) are +now configured to support the extended tcp_wrappers syntax by +default.
+ +The +locale(1) +utility has been re-implemented and is now POSIX-compliant. A new -m option shows all available codesets.
+ +The +mount(8) utility +now supports to display the filesystem ID for each file system in addition to the normal +information when a -v flag is specified, and the +umount(8) +utility now accepts the filesystem ID as well as the usual device and path names. This +allows to unambiguously specify which file system is to be unmounted even when two or +more file systems share the same device and mount point names.
+ +The +mount_cd9660(8), + +mount_ntfs(8), +and +mount_udf(8) +utilities now support a -C option to specify local character +sets to convert Unicode filenames. It is possible to specify multi-byte character sets +using this option.
+ +The +mount_msdosfs(8) +utility now supports a -M option to specify the maximum file +permissions for directories in the file system. [MERGED]
+ +The +mount_msdosfs(8) +utility now supports a -D option to specify MS-DOS codepages +and a -L option to specify local character sets. They are used +to convert character sets of filenames. The /usr/libdata/msdosfs tables have been retired.
+ +The +mount_nwfs(8), + +mount_portalfs(8), and +mount_smbfs(8) +utilities have been moved from /sbin to /usr/sbin.
+ +The +nologin(8) +program has been reimplemented in C (it was formerly a shell script).
+ +The +rc.conf(5) +variable ntpd_flags for +ntpd(8) now +includes -f /var/db/ntpd.drift by default.
+ +The +pam_guest(8) PAM +module has been added to allow guest logins. It replaces the pam_ftp(8) module.
+ ++ps(1) and +top(1) now +support a -H flag to display all kernel-visible threads in each +process.
+ +A bug that +rarpd(8) does +not recognize removable Ethernet NICs has been fixed.
+ ++repquota(8) now +supports a -n flag to display users and groups numerically.
+ ++rtld(1) now +includes ``libmap'' functionality by default; the WITH_LIBMAP +compile knob is unnecessary and has been retired. More information can be found in +libmap.conf(5).
+ ++savecore(8) now +supports a -C flag that merely indicates the existence or +absence of a coredump file.
+ +The symorder utility has been removed. It is unnecessary now that all kernels use ELF +format and there is no a.out format toolchain.
+ ++sysinstall(8) +now gives the ability to select an alternate MTA during installation. Currently, exim and Postfix are supported.
+ ++sysinstall(8) no +longer supports system ``security profiles''; this feature has been replaced by +individual tuning knobs to enable and disable +sshd(8) and set +the system securelevels.
+ ++systat(1) now +includes displays for IPv6 and ICMPv6 traffic. [MERGED]
+ ++uname(1) now +supports a -i flag to return the kernel identification. This +name is also available via the kern.ident sysctl variable.
+ +A number of utilities available in /bin and /sbin are now available as a statically-linked ``crunched'' binary +that lives in /rescue. This functionality is similar to the /stand directory installed by +sysinstall(8), +but /rescue includes more functionality and is updated as part +of buildworld/installworld +operations. More details can be found in +rescue(8).
+ +Many executables in /bin and /sbin +are now built using dynamic, rather than static linking. This feature brings support for +loadable PAM and NSS modules to base system utilities located in those directories. It +also reduces the storage requirements for the root filesystem due to the use of shared +libraries. This feature can be disabled in a buildworld by +defining the Makefile variable NO_DYNAMICROOT. Note that +statically-linked, crunched executables are available in the /rescue directory for use during system repair and recovery +operations.
+The ACPI-CA code has been updated from the 20030228 +snapshot to the 20030619 snapshot.
+ +amd has been updated from 6.0.7 to 6.0.9.
+ +awk from Bell Labs has been updated from a 14 March 2003 +snapshot to a 29 July 2003 snapshot.
+ +BIND has been updated from 8.3.4 to 8.3.7. [MERGED]
+ +GCC has been updated from 3.2.2 to a 3.3.3 post-release +snapshot from 6 November 2003.
+ +++Note: Previous versions of GCC generated incorrect +code when -march=pentium4 optimization was enabled. This +problem is believed to have been fixed with this upgrade, and the earlier workaround for +the case of CPUTYPE=p4 has been removed.
+
GNU Readline has been updated from 4.2 to 4.3.
+ +GNU Sort has been updated from the version in textutils +2.0.21 to the version in textutils 2.1.
+ +Heimdal Kerberos has been updated from 0.5.1 to 0.6.
+ +The ISC DHCP client has been updated from 3.0.1rc11 to +3.0.1rc12.
+ +lukemftp has been updated from 1.6beta2 to a 11 November +2003 snapshot from NetBSD.
+ +OpenPAM has been updated from the ``Dianthus'' release to +the ``Dogwood'' release.
+ +OpenSSL has been updated from 0.9.7a to 0.9.7c. +[MERGED]
+ +sendmail has been updated from version 8.12.9 to version +8.12.10. [MERGED]
+ +texinfo has been updated from 4.5 to 4.6. [MERGED]
+ +The timezone database has been updated from the tzdata2003a +release to the tzdata2003d release. [MERGED]
+If GNU_CONFIGURE is defined, all instances of config.guess and config.sub found under +WRKDIR are replaced with the master +versions from PORTSDIR/Template. This +allows old ports (which contain old versions of these scripts) to build on newer +architectures like ia64 and amd64.
+The supported release of GNOME has been updated from 2.2.1 +to 2.4. [MERGED]
+ +The supported release of KDE has been updated from 3.1.2 to +3.1.4. [MERGED]
+ +The versions of GNOME and KDE +included on release disc 1 (and installable from the +sysinstall(8) +``X Desktops'' menu) are now ``Lite Edition'', packages, rather than the more +full-featured meta-packages. These packages are streamlined to provide users with the +core essentials for each desktop, while still fitting within the space constraints of +release disc 1.
+To reduce duplication of information (and subsequent difficulty in maintaining +consistency), many instances of specific devices supported in the Hardware Notes have +been moved to system manual pages. This project is ongoing as of this release.
+ +A Turkish (tr_TR.ISO8859-9) translation project has been started.
+Users with existing FreeBSD systems are highly encouraged to read the ``Early Adopter's Guide to +FreeBSD 5.2-RELEASE''. 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.
+
This file, and other release-related documents, can be +downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/.
+ +For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
+ +For questions about this documentation, e-mail <doc@FreeBSD.org>.
+ +