Index: stable/4/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml =================================================================== --- stable/4/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml (revision 93790) +++ stable/4/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml (revision 93791) @@ -1,375 +1,391 @@ &os;/&arch; &release.current; Release Notes $FreeBSD$ The FreeBSD Project 2000 2001 2002 The FreeBSD Documentation Project The release notes for &os; &release.current; contain a summary of the changes made in the &os; base system since &release.prev;. Both changes for kernel and userland are listed, as well as applicable security advisories for the base system that were issued since the last release. Some brief remarks on upgrading are also presented. Introduction This document contains the release notes for &os; &release.current; on the &arch.print; hardware platform. It describes new features of &os; that have been added (or changed) since &release.prev;. It also provides some notes on upgrading from previous versions of &os;. The &release.type; distribution to which these release notes apply represents a point along the &release.branch; development branch between &release.prev; and the future &release.next;. Some pre-built, binary &release.type; distributions along this branch can be found at . ]]> This distribution of &os; &release.current; is a &release.type; distribution. It can be found at or any of its mirrors. More information on obtaining this (or other) &release.type; distributions of &os; can be found in the Obtaining FreeBSD appendix in the FreeBSD Handbook. ]]> What's New This section describes the most user-visible new or changed features in &os; since &release.prev;. Typical release note items document new drivers or hardware support, new commands or options, major bugfixes, or contributed software upgrades. Security advisories for the base system that were issued after &release.prev; are also listed. Many additional changes were made to &os; that are not listed here for lack of space. For example, documentation was corrected and improved, minor bugs were fixed, insecure coding practices were audited and corrected, and source code was cleaned up. Kernel Changes The &man.puc.4; (PCI Universal Communications) driver has been added, to help connect PCI-based serial ports to the &man.sio.4; driver. The kernel dump device can now be set via the dumpdev loader tunable. As a result, it is now possible to obtain crash dumps from panics during the late stages of kernel initialization (before the system enters into single-user mode). The &man.snp.4; device is no longer static and can now be compiled as a module. Processor/Motherboard Support Boot Loaders Network Interface Support The &man.an.4; driver now supports Cisco LEAP, as well as the Home WEP key. The Linux Aironet utilities are now supported under emulation. Generic support for ARCNET token-based networks has been added. The cm driver has been added to support SMC COM90cx6 ARCNET network adapters. The &man.dc.4; driver now has support for VLANs. The &man.wi.4; driver now has support for Prism II and Prism 2.5-based NICs. 104/128-bit WEP now works on Prism cards. Selected network drivers now implement a semi-polling mode, which makes systems much more resilient to attacks and overloads. To enable polling, the following options are required in a kernel configuration file: options DEVICE_POLLING options HZ=1000 # not compulsory but strongly recommended The kern.polling.enable sysctl variable will then activate polling mode; with the kern.polling.user_frac sysctl indicating the percentage of CPU time to be reserved for userland. The devices initially supporting polling are &man.dc.4;, &man.fxp.4;, and &man.sis.4;. More details can be found in the &man.polling.4; manual page. Network Protocols &man.bridge.4; now has better support for multiple, fully-independent bridging clusters, and is much more stable in the presence of dynamic attachments and detatchments. Full support for VLANs is also supported. A bug in the IPSec processing for IPv4, which caused the inbound SPD checks to be ignored, has been fixed. The &man.tcp.4; syncache implementation had a bug that could cause kernel panics; this has been fixed. The TCP implementation now properly ignores packets addressed to IP-layer broadcast addresses. Disks and Storage The &man.ata.4; driver now has support for rebuilding failed drives in a RAID1 configuration, under control of &man.atacontrol.8;. Filesystems A bug was been fixed in soft updates that could cause occasional filesystem corruption if the system is shut down immediately after performing heavy filesystem activities, such as installing a new kernel or other software. PCCARD Support Multimedia Support The ufm driver, supporting the D-Link DSB-R100 USB Radio, has been added. The via82c686 sound driver now supports the VIA VT8233. The ich sound driver now support the SiS 7012 chipset. Contributed Software Security Advisories An off-by-one bug has been fixed in OpenSSH's multiplexing code. This bug could have allowed an authenticated remote user to cause &man.sshd.8; to execute arbitrary code with superuser privileges, or allowed a malicious SSH server to execute arbitrary code on the client system with the privileges of the client user. (See security advisory FreeBSD-SA-02:13.) A programming error in zlib could result in attempts to free memory multiple times. The &man.malloc.3;/&man.free.3; routines used in &os; are not vulnerable to this error, but applications receiving specially-crafted blocks of invalid compressed data could be made to function incorrectly or abort. This zlib bug has been fixed. For a workaround and solutions, see security advisory FreeBSD-SA-02:18. Userland Changes &man.atacontrol.8; has been added to control various aspects of the &man.ata.4; driver. &man.ctags.1; no longer creates a corrupt tags file if the source file used // (C++-style) comments. &man.dump.8; now supplies progress information in its process title, useful for monitoring automated backups. /etc/rc.firewall and /etc/rc.firewall6 will no longer add their own hardcoded rules in the cases of a rules file in the firewall_type variable or a non-existent firewall type. (The motivation for this change is to avoid acting on assumptions about a site's firewall policies.) In addition, the closed firewall type now works as documented in the &man.rc.firewall.8; manual page. The functionality of /etc/security has been been moved into a set of scripts under the &man.periodic.8; framework, to make local customization easier and more maintainable. These scripts now reside in /etc/periodic/security/. + The address family of + &man.ifconfig.8; has been changed to a more generic + family ( is still + accepted for backwards compatability). + &man.ldd.1; can now be used on shared libraries, in addition to executables. + libusb has been renamed as + libusbhid, following NetBSD's naming + conventions. + &man.ngctl.8; now supports a command to send a data packet down a given hook. + The &man.usbhidctl.1; utility has been added to manipulate + USB Human Interface Devices. + The option to &man.ps.1; (to extract information from a specified swap device) has been useless for some time; it has been removed. &man.watch.8; now takes a option to specify a &man.snp.4; device to use. Locales with names of the form *.EUC have been renamed to the form *.euc??. For example, ja_JP.euc has become ja_JP.eucJP. This improves locale name compatability with &os; CURRENT, X11R6, and a number of other UNIX versions. Contributed Software BIND has been updated to 8.3.1-REL. bzip2 has been updated to 1.0.2. sendmail has been updated to 8.12.2. &man.sendmail.8; is no longer installed as a set-user-ID root binary (now set-group-ID smmsp). See /usr/src/contrib/sendmail/RELEASE_NOTES and /etc/mail/README for more information. + + texinfo has been updated to + 4.1. + Ports/Packages Collection Upgrading from previous releases of &os; If you're upgrading from a previous release of &os;, you generally will have three options: Using the binary upgrade option of &man.sysinstall.8;. This option is perhaps the quickest, although it presumes that your installation of &os; uses no special compilation options. Performing a complete reinstall of &os;. Technically, this is not an upgrading method, and in any case is usually less convenient than a binary upgrade, in that it requires you to manually backup and restore the contents of /etc. However, it may be useful in cases where you want (or need) to change the partitioning of your disks. From source code in /usr/src. This route is more flexible, but requires more disk space, time, and more technical expertise. Upgrading from very old versions of &os; may be problematic; in cases like this, it is usually more effective to perform a binary upgrade or a complete reinstall. Please read the INSTALL.TXT file for more information, preferably before beginning an upgrade. If you are upgrading from source, please be sure to read /usr/src/UPDATING as well. Finally, if you want to use one of various means to track the -STABLE or -CURRENT branches of &os;, please be sure to consult the -CURRENT vs. -STABLE section of the FreeBSD Handbook. Upgrading &os; should, of course, only be attempted after backing up all data and configuration files.