freebsd-dev/release/doc/en_US.ISO8859-1/relnotes/article.sgml
Bruce A. Mah e148fee838 New release notes: Background fsck(8) summary recomputation (+MFC),
newfs(8) snapshot warning (+MFC), newsyslog(8) -N, systat(1) -netstat
IPv6-ware (+MFC), merged install/fixit CDROMs (+MFC).

MFCs noted:  IPFIREWALL_FORWARD_EXTENDED, strftime(3) GNU extensions,
rc.conf(5) tmpmfs_flags and varmfs_flags.
2005-03-05 16:26:32 +00:00

894 lines
36 KiB
Plaintext

<articleinfo>
<title>&os;/&arch; &release.current; Release Notes</title>
<corpauthor>The &os; Project</corpauthor>
<pubdate>$FreeBSD$</pubdate>
<copyright>
<year>2000</year>
<year>2001</year>
<year>2002</year>
<year>2003</year>
<year>2004</year>
<year>2005</year>
<holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
</copyright>
<abstract>
<para>The release notes for &os; &release.current; contain a summary
of the changes made to the &os; base system since &release.branch; is created.
This document lists applicable security advisories that were issued since
the last release, as well as significant changes to the &os;
kernel and userland.
Some brief remarks on upgrading are also presented.</para>
</abstract>
</articleinfo>
<sect1 id="intro">
<title>Introduction</title>
<para>This document contains the release notes for &os;
&release.current; on the &arch.print; hardware platform. It
describes recently added, changed, or deleted features of &os;.
It also provides some notes on upgrading
from previous versions of &os;.</para>
<![ %release.type.current [
<para>The &release.type; distribution to which these release notes
apply represents the latest point along the &release.branch; development
branch since &release.branch; is created. Some pre-built, binary
&release.type; distributions along this branch
can be found at <ulink url="&release.url;"></ulink>.</para>
]]>
<![ %release.type.snapshot [
<para>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 <ulink url="&release.url;"></ulink>.</para>
]]>
<![ %release.type.release [
<para>This distribution of &os; &release.current; is a
&release.type; distribution. It can be found at <ulink
url="&release.url;"></ulink> or any of its mirrors. More
information on obtaining this (or other) &release.type;
distributions of &os; can be found in the <ulink
url="&url.books.handbook;/mirrors.html"><quote>Obtaining
&os;</quote> appendix</ulink> to the <ulink
url="&url.books.handbook;/">&os;
Handbook</ulink>.</para>
]]>
<para>All users are encouraged to consult the release errata before
installing &os;. The errata document is updated with
<quote>late-breaking</quote> 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 &os;
&release.current; can be found on the &os; Web site.</para>
</sect1>
<sect1 id="new">
<title>What's New</title>
<para>This section describes
the most user-visible new or changed features in &os;
since &release.prev;.
In general, changes described here are unique to the &release.branch;
branch unless specifically marked as &merged; features.
</para>
<para>Typical release note items
document recent security advisories issued after
&release.prev.historic;,
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 &os; between releases; this document focuses
primarily on security advisories, user-visible changes, and major
architectural improvements.</para>
<sect2 id="security">
<title>Security Advisories</title>
<para>A bug in the &man.fetch.1; utility, which allows
a malicious HTTP server to cause arbitrary portions of the client's
memory to be overwritten, has been fixed.
For more information, see security advisory
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:16.fetch.asc">FreeBSD-SA-04:16.fetch</ulink>.
&merged;</para>
<para>A bug in &man.procfs.5; and &man.linprocfs.5;
which could allow a malicious local user to read parts of kernel
memory or perform a local
denial of service attack by causing a system panic,
has been fixed.
For more information, see security advisory
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:17.procfs.asc">FreeBSD-SA-04:17.procfs</ulink>.
&merged;</para>
</sect2>
<sect2 id="kernel">
<title>Kernel Changes</title>
<para arch="i386">Support for 80386 processors (the
<literal>I386_CPU</literal> kernel configuration option) has
been removed. Users running this class of CPU should use &os;
5.<replaceable>X</replaceable> or earlier.</para>
<para arch="alpha,amd64,i386">The loader tunable <varname>debug.mpsafevm</varname>
has been enabled by default. &merged;</para>
<para>&man.memguard.9;, a kernel memory allocator designed to help detect
<quote>tamper-after-free</quote> scenarios, has been added.
This must be explicitly enabled via <literal>options
DEBUG_MEMGUARD</literal>, plus small kernel modifications. It
is generally intended for use by kernel developers.</para>
<para>A number of bugs have been fixed in the ULE
scheduler. &merged;</para>
<para>Fine-grained locking to allow much of the VFS stack to run
without the Giant lock has been added. This is enabled by default
on the alpha, amd64, and i386 architectures, and can be disabled
by setting the loader tunable (and sysctl variable)
<varname>debug.mpsafevfs</varname> to
<literal>0</literal>.</para>
<para arch="i386">A bug in Inter-Processor Interrupt (IPI)
handling, which could cause SMP systems to crash under heavy
load, has been fixed. More details are contained in errata note
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:03.ipi.asc">FreeBSD-EN-05:03.ipi</ulink>.
&merged;</para>
<para>System V IPC objects (message queues, semaphores, and shared
memory) now have support for Mandatory Access Control policies,
notably &man.mac.biba.4;, &man.mac.mls.4;, &man.mac.stub.4;, and
&man.mac.test.4;.</para>
<para arch="i386">Memory allocation for legacy PCI bridges has
been limited to the top 32MB of RAM. Many older, legacy bridges
only allow allocation from this range. This change only applies
to devices which do not have their memory assigned by the BIOS.
This change fixes the <quote>bad Vcc</quote> error of CardBus
bridges (&man.pccbb.4;). &merged;</para>
<para>The &man.sysctl.3; MIBs beginning with <quote>debug</quote>
now require the kernel option <literal>options SYSCTL_DEBUG</literal>.
This option is disabled by default.</para>
<para>The generic &man.tty.4; driver interface has been added
and many device drivers including
&man.cx.4; (<literal>{tty,cua}x</literal>),
&man.cy.4; (<literal>{tty,cua}c</literal>),
&man.digi.4; (<literal>{tty,cua}D</literal>),
&man.rc.4; (<literal>{tty,cua}m</literal>),
&man.rp.4; (<literal>{tty,cua}R</literal>),
&man.sab.4; (<literal>{tty,cua}z</literal>),
&man.si.4; (<literal>{tty,cua}A</literal>),
&man.sio.4; (<literal>{tty,cua}d</literal>),
sx (<literal>{tty,cua}G</literal>),
&man.uart.4; (<literal>{tty,cua}u</literal>),
&man.ubser.4; (<literal>{tty,cua}y</literal>),
&man.ucom.4; (<literal>{tty,cua}U</literal>), and
&man.ucycom.4; (<literal>{tty,cua}y</literal>)
have been rewritten to use it. Note that <filename>/etc/remote</filename>
and <filename>/etc/ttys</filename> have been updated as well.</para>
<para>The &man.vkbd.4; driver has been added. This driver
provides a software loopback mechanism that can implement
a virtual AT keyboard similar to what the &man.pty.4; driver
does for terminals.</para>
<!-- Above this line, sort kernel changes by manpage/keyword-->
<para arch="i386,amd64,ia64">The default <varname>HZ</varname>
parameter (which controls various kernel timers) has been
increased from <literal>100</literal> to <literal>1000</literal>
on the i386 and ia64. It has been reduced from
<literal>1024</literal> to <literal>1000</literal> on the amd64
to reduce synchronization effects with other system
clocks.</para>
<para>The maximum length of shell commands has changed from 128
bytes to <varname>PAGE_SIZE</varname>. By default, this value
is either 4KB (i386, pc98, amd64, and powerpc) or 8KB (sparc64
and ia64). As a result, compatibility modules need to be
rebuilt to stay synchronized with data structure changes in the
kernel.</para>
<sect3 id="boot">
<title>Boot Loader Changes</title>
<para arch="i386">A serial console-capable version of
<filename>boot0</filename> has been added. It can be written
to a disk using &man.boot0cfg.8; and specifying
<filename>/boot/boot0sio</filename> as the argument to the
<option>-b</option> option.</para>
<para arch="i386"><filename>cdboot</filename> now works around a
BIOS problem observed on some systems when booting from USB
CDROM drives.</para>
<para>The <command>autoboot</command> loader command
now supports the prompt parameter.</para>
<para>A loader menu option to set <varname>hint.atkbd.0.flags=0x1</varname>
has been added. This setting allows USB keyboards to work
if no PS/2 keyboard is attached.</para>
<!-- Above this line, order boot loader changes by keyword-->
</sect3>
<sect3 id="proc">
<title>Hardware Support</title>
<para arch="i386,amd64">The acpi_snc driver,
which supports the Sony Notebook Controller on various
Sony laptops has been added.</para>
<para arch="sparc64">The &man.auxio.4; driver has been to drive
some auxiliary I/O functions found on various SBus/EBus
&ultrasparc; models. &merged;</para>
<para>A framework for flexible processor speed control has been
added. It provides methods for various drivers to control CPU
power utilization by adjusting the processor speed. More
details can be found in the &man.cpufreq.4; manual page. &merged;
Currently supported drivers include acpi_perf (ACPI CPU
performance states), ichss (Intel SpeedStep for ICH), and
acpi_throttle (ACPI CPU throttling).</para>
<para arch="i386">Support for the OLDCARD subsystem has
been removed. The NEWCARD system is now used for all PCCARD
device support.</para>
<para>The pcii driver has been added to support GPIB-PCIIA IEEE-488
cards.</para>
<para arch="i386">The &man.pbio.4; driver,
which supports direct access to
the Intel 8255A programmable peripheral interface (PPI)
chip running in mode 0 (simple I/O) has been added.</para>
<para>The &man.psm.4; driver now has improved support for
Synaptics Touchpad users. It now has better tracking of
slow-speed movement and support for various extra
buttons and dials. These features can be tuned with the
<varname>hw.psm.synaptics.<replaceable>*</replaceable></varname>
hierarchy of sysctl variables.</para>
<para arch="sparc64">The rtc driver has been added to support
the MC146818-compatible clock found on some &ultrasparc; II
and III models. &merged;</para>
<para arch="sparc64">The &man.uart.4; driver is now enabled in
the <filename>GENERIC</filename> kernel, and is now the
default driver for serial ports. The ofw_console,
&man.sab.4;, and zs drivers are now disabled in the
<filename>GENERIC</filename> kernel. &merged;</para>
<para>The &man.uplcom.4; driver now supports handling of the
<literal>CTS</literal> signal.</para>
<para>The &man.ehci.4; driver has been improved.</para>
<sect4 id="mm">
<title>Multimedia Support</title>
<para arch="sparc64">The &man.snd.audiocs.4; driver has been
added to support the Crystal Semiconductor CS4231 audio
controller found on &ultrasparc;
workstations. &merged;</para>
<para>The &man.uaudio.4; driver now has some added
functionality, including volume control on more inputs and
recording capability on some devices.</para>
</sect4>
<sect4 id="net-if">
<title>Network Interface Support</title>
<para>The &man.ath.4; driver has been updated to split the
transmit rate control algorithm into a separate module.
Either <literal>device ath_rate_onoe</literal> or
<literal>device ath_rate_amrr</literal> must be included in
the kernel configuration when using the &man.ath.4;
driver.</para>
<para>The &man.bge.4; driver now supports the &man.altq.4;
framework.</para>
<para>The &man.cp.4; driver is now MPSAFE. &merged;</para>
<para>The &man.ctau.4; driver is now MPSAFE. &merged;</para>
<para>The &man.cx.4; driver is now MPSAFE. &merged;</para>
<para>The &man.dc.4; driver now supports the &man.altq.4; framework.</para>
<para>In the &man.em.4; driver, hardware support for VLAN
tagging is now disabled by default due to some interactions
between this feature and promiscuous mode. &merged;</para>
<para>Ethernet flow control is now disabled by default in the
&man.fxp.4; driver, to prevent problems with a system panics
or is left in the kernel debugger. &merged;</para>
<para>The gx(4) driver has been removed because
it is no longer maintained actively and
the &man.em.4; supports all of the supported hardware.</para>
<para>The &man.hme.4; driver is now MPSAFE. &merged;</para>
<para arch="amd64">The &man.ndis.4; device driver wrapper now
supports &windows;/x86-64 binaries on amd64
systems. &merged;</para>
<para>The &man.sf.4; driver now has support for device polling
and &man.altq.4;. &merged;</para>
<para>Several programming errors in the &man.sk.4; driver have
been corrected. These bugs were particular to SMP systems, and
could cause panics, page faults, aborted SSH connections, or
corrupted file transfers. More details can be found in
errata note
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:02.sk.asc">FreeBSD-EN-05:02.sk</ulink>.
&merged;</para>
<para>The &man.sk.4; driver now has support for &man.altq.4;.
This driver also now supports jumbo frames on Yukon-based
interfaces. &merged;</para>
<para>The &man.vge.4; driver now has support for device polling
(&man.polling.4;).</para>
<para>Support for 802.11 devices in the &man.wlan.4; framework has been
greatly overhauled. In addition to architectural changes,
it includes completed 802.11g, WPA, 802.11i, 802.1x,
WME/WMM, AP-side power-saving, and plugin frameworks for
cryptography modules, authenticators, and access control.
Note in particular that WEP now requires the
<filename>wlan_wep</filename> module to be loaded (or
compiled) into the kernel.</para>
</sect4>
</sect3>
<sect3 id="net-proto">
<title>Network Protocols</title>
<para>The MTU feedback in IPv6 has been disabled when the sender writes
data that must be fragmented. &merged;</para>
<para>The Common Address Redundancy Protocol (CARP) has
been implemented. CARP comes from OpenBSD and allows
multiple hosts to share an IP address, providing
high availability and load balancing.
For more information, see the &man.carp.4; manual page.</para>
<para>The &man.ipfw.4; <literal>IPDIVERT</literal> option is now
available as a kernel loadable module.
If this module is not loaded, &man.ipfw.4; will refuse to
install <literal>divert</literal> rules and &man.natd.8;
will return the error message <quote>protocol not supported</quote>.</para>
<para>&man.ipfw.8; now supports classification and tagging
of &man.altq.4; packets via a divert socket,
as well as the TCP data length.</para>
<para>The &man.ipfw.8; <literal>ipfw fwd</literal> rule now supports
the full packet destination manipulation when the kernel option
<literal>options IPFIREWALL_FORWARD_EXTENDED</literal> is specified
in addition to <literal>options IPFIRWALL_FORWARD</literal>.
This kernel option disables all restrictions to ensure proper
behavior for locally generated packets and allows redirection of
packets destined to locally configured IP addresses.
Note that &man.ipfw.8; rules have to be carefully crafted to
make sure that things like PMTU discovery do not break. &merged;</para>
<para>Ongoing work is reducing the use of the Giant lock by the
network protocol stack and improving the locking
strategies.</para>
<para>A new &man.ng.netflow.4; NetGraph node allows a router
running &os; to do NetFlow version 5 exports. &merged;</para>
<para>The &man.sppp.4; driver now includes Frame Relay
support. &merged;</para>
<para>A bug in TCP that sometimes caused RST packets to
be ignored if the receive window was zero bytes has been
fixed. &merged;</para>
<para>Several bugs in the TCP SACK implementation have been
fixed. &merged;</para>
<para>RFC 1644 T/TCP support has been removed. This is because
the design is based on a weak security model that can easily
permit denial-of-service attacks. This TCP
extension has been considered a defective one in
a recent Internet Draft.</para>
<para>Random ephemeral port number allocation has led to some
problems with port reuse at high connection rates. This
feature is now disabled during periods of high connection
rates; whenever new connections are created faster than
<varname>net.inet.ip.portrange.randomcps</varname> per second,
port number randomization is disabled for the next
<varname>net.inet.ip.portrange.randomtime</varname>
seconds. The default values for these two sysctl variables
are <literal>10</literal> and <literal>45</literal>,
respectively. &merged;</para>
<para>Fine-grained locking has been applied to many of the data
structures in the IPX/SPX protocol stack. While not fully
MPSAFE at this point, it is generally safe to use IPX/SPX
without the Giant lock (in other words, the
<varname>debug.mpsafenet</varname> sysctl variable may be set
to <literal>1</literal>).</para>
</sect3>
<sect3 id="disks">
<title>Disks and Storage</title>
<para>The &man.amr.4; driver is now safe for use on systems
using &man.pae.4;. &merged;</para>
<para>The SHSEC GEOM class has been added. It provides for the
sharing of a secret between multiple GEOM providers. All of
these providers must be present in order to reveal the
secret. This feature is controlled by the &man.gshsec.8;
utility. &merged;</para>
<para>The &man.hptmv.4; driver, which supports the HighPoint
RocketRAID 182x series, has been added. &merged;</para>
<para>The &man.matcd.4; driver has been removed. &merged;</para>
<para>The default SCSI boot-time probe delay in the
<filename>GENERIC</filename> kernel has been reduced from
fifteen seconds to five seconds.</para>
<para>The old vinum(4) subsystem has been removed
in favor of the new &man.geom.4;-based version.</para>
<para arch="pc98">The &man.wd.4; driver has been removed. The
&man.ata.4; driver has been found to work well enough on the
pc98 platform that there is no need for the older &man.wd.4;
driver.</para>
<para>Information about newly-mounted cd9660 file systems (such
as the presence of Rockridge extensions) is now only printed
if the kernel was booted in verbose mode. This change was
made to reduce the amount of (generally unnecessary) kernel
log messages. &merged;</para>
</sect3>
<sect3 id="fs">
<title>File Systems</title>
<para>The autofs(9) file system and the userland library
&man.libautofs.3; have been added.</para>
<para>Recomputing the summary information for
<quote>dirty</quote> UFS and UFS2 file systems is no longer
done at mount time, but is now done by background
&man.fsck.8;. This change improves the startup speed when
mounting large file systems after a crash. The prior behavior
can be restored by setting the
<varname>vfs.ffs.compute_summary_at_mount</varname> sysctl
variable to a non-zero value. &merged;</para>
<para>A kernel panic in the NFS server has been fixed. More
details can be found in errata note
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:01.nfs.asc">FreeBSD-EN-05:01.nfs</ulink>.
&merged;</para>
</sect3>
<sect3>
<title>Contributed Software</title>
<para><application>ACPI-CA</application> has been updated from
20040527 to 20041119. &merged;</para>
</sect3>
</sect2>
<sect2 id="userland">
<title>Userland Changes</title>
<para>The &man.burncd.8; utility now allows commands (such as
<command>eject</command>) to take place after fixating a
disk.</para>
<para>The <literal>create</literal> command of the &man.gpt.8;
utility now supports a <option>-f</option> command-line flag to
force creation of a GPT even when there is an MBR record on a
disk. &merged;</para>
<para>The &man.ifconfig.8; utility has been restructured. It is
now more modular and flexible with respect to supporting
interface-specific functionality. The 802.11 support has been
updated to support recent changes to the 802.11 subsystem and
drivers.</para>
<para>Support for abbreviated forms of a number of &man.ipfw.8;
options has been deprecated. Warnings are printed to stderr
indicating the correct full form when one of these abbreviations
is detected.</para>
<para>The on-disk format of <literal>LC_CTYPE</literal> files has
been changed to be machine-independent.</para>
<para>The <filename>libarchive</filename> library (as well as the
&man.tar.1; command that uses it) now has support for reading ISO
images (with optional RockRidge extensions) and ZIP archives
(with <literal>deflate</literal> and <literal>none</literal>
compression). &merged;</para>
<para>The <filename>libgpib</filename> library has been added to
give userland access to GPIB devices (using the the pcii driver)
via the
<function>ib<replaceable>foo</replaceable></function>
API.</para>
<para>The default stack sizes in <filename>libpthread</filename>
and <filename>libc_r</filename> have been increased. On 32-bit
platforms, the main thread receives a 2MB stack size by default,
with other threads receiving a 1MB stack size by default. On
64-bit platforms, the default stack sizes are 4MB and 2MB
respectively.</para>
<para>The <filename>libxpg4</filename> library has been removed
because all of its functionality was long ago merged into
<filename>libc</filename>.
All binaries linked with <filename>libxpg4</filename>
must be recompiled or use &man.libmap.conf.5;.
Note that the &os; base system has no such binaries.</para>
<para>A number of new functions have been implemented in the
&man.math.3; library. These include &man.ceill.3;,
&man.floorl.3;, &man.ilogbl.3;, &man.fma.3; and variants,
&man.lrint.3; and variants, and &man.lround.3; and
variants. &merged;</para>
<para>The &man.mknod.8; utility is now deprecated.
Device nodes have been managed by the &man.devfs.5; device file
system since &os; 5.0.</para>
<para arch="i386">The &man.mkuzip.8; utility, which
compresses file system images for use with
<literal>GEOM_UZIP</literal> &man.geom.4; module,
has been added. &merged;</para>
<para>The &man.moused.8; daemon now supports <quote>virtual
scrolling</quote>, in which mouse motions made while holding
down the middle mouse button are interpreted as scrolling. This
feature is enabled with the <option>-V</option>
flag. &merged;</para>
<para>A separate directory has been added for &man.named.8;
dynamic zones which is owned by the <username>bind</username> user
(for creation of the zone journal file).
For more detail, see an example dynamic zone in the sample
&man.named.conf.5;. &merged;</para>
<para>The &man.ncal.1; utility now supports a <option>-m</option>
flag to generate a calendar for a specified month in the current
year. &merged;</para>
<para>The &man.newfs.8; utility now supports a <option>-n</option>
flag to suppress the creation of a <filename>.snap</filename>
directory on new file systems. This feature is intended for use
on memory or vnode file systems that will not require snapshot
support. &merged;</para>
<para>The &man.newfs.8; utility now emits a warning when creating
a UFS or UFS2 file system that cannot support snapshots. This
situation can occur in the case of very large file systems with
small block sizes. &merged;</para>
<para>The &man.newsyslog.8; utility now supports
a <option>-d</option> option to specify an alternate root for log files
similar to <varname>DESTDIR</varname> in the BSD make process.
This only affects log file paths, not configuration file (<option>-f</option>)
or archive directory (<option>-a</option>) paths.</para>
<para>The &man.newsyslog.8; utility now supports a
<option>-N</option> that causes it not to rotate any files.</para>
<para>The <literal>NO_NIS</literal> compile-time knob for userland
has been added. As its name implies, enabling this
<filename>Makefile</filename> variable will cause NIS support to
be excluded from various programs and will cause the NIS
utilities to not be built. &merged;</para>
<para>For years, &os; has used <filename>Makefile</filename>
variables of the form
<varname>NO<replaceable>FOO</replaceable></varname> and
<varname>NO_<replaceable>FOO</replaceable></varname>. For
consistency, those variables using the former naming convention
have been converted to the
<varname>NO_<replaceable>FOO</replaceable></varname> form. The
file <filename>/usr/share/mk/bsd.compat.mk</filename> has a
complete list of these variables; it also implements some
temporary backward compatibility for the old names.</para>
<para>The &man.ppp.8; program now implements an
<option>echo</option> parameter, which allows LCP ECHOs to be
enabled independently of LQR reports. Older versions of
&man.ppp.8; would revert to LCP ECHO mode on negotiation
failure. It is now necessary to specify <command>enable
echo</command> to get this behavior. &merged;</para>
<para>The &man.rm.1; utility now supports an <option>-I</option>
option that asks for confirmation (once) if recursively
removing directories or if more than 3 files are listed in the
command line. &merged;</para>
<para>The &man.rm.1; utility now suppresses diagnostic messages
when it attempts to remove a non-existent directory
with the <option>-r</option> and <option>-f</option> options
specified. This behavior is required by
Version 3 of the Single UNIX Specification (SUSv3).</para>
<para>An &man.rpmatch.3; library function has been added to check
a string for being an affirmative or negative response in the
current locale.</para>
<para>The &man.rtld.1; dynamic linker now supports specifying
library replacements via the <varname>LD_LIBMAP</varname>
environment variable. This variable will override the entries
in &man.libmap.conf.5;. &merged;</para>
<para>The rune(3) non-standard multibyte and wide character support
interface has been removed.</para>
<para>The &man.strftime.3; function now supports some GNU extensions
such as <literal>-</literal> (no padding),
<literal>_</literal> (use space as padding),
and <literal>0</literal> (zero padding). &merged;</para>
<para>The &man.syslog.3; function is now thread-safe. &merged;</para>
<para>The &man.syslogd.8; utility now opens an additional domain
socket (<filename>/var/run/logpriv</filename> by default),
with <literal>0600</literal> permissions to be used
by privileged programs. This prevents privileged
programs from locking when the domain sockets
run out of buffer space due to a
local denial-of-service attack. &merged;</para>
<para>The &man.systat.1; <option>-netstat</option> display is now
IPv6-aware. &merged;<para>
<para>The <option>-f</option> option of &man.tail.1; utility
now supports more than one file at a time. &merged;</para>
<para>The &man.telnet.1; and &man.telnetd.8; programs now support
the <option>-S</option> option for specifying a numeric TOS
byte.</para>
<para>Prepending a <literal>+</literal> character to port numbers
passed to &man.telnet.1; program will now disable option
negotiation and allow the transfer of characters with the high
bit set. This feature is intended to support the fairly common
use of &man.telnet.1; as a protocol tester.</para>
<para>The &man.tcpdrop.8; command, which closes a selected TCP
connection, has been added. It was obtained from
OpenBSD.</para>
<para>&man.whois.1; now supports
a <option>-k</option> flag
for querying <hostid role="fqdn">whois.krnic.net</hostid>
(the National Internet Development Agency of Korea),
which holds details of IP address allocations within
Korea. &merged;</para>
<para>The <option>-I</option> option of the &man.xargs.1; command
has been changed to confirm IEEE Std 1003.1-2004.
The standard requires that the constructed
arguments cannot grow larger than 255 bytes.</para>
<sect3 id="rc-scripts">
<title><filename>/etc/rc.d</filename> Scripts</title>
<para>&man.rc.conf.5; now supports changes of network interface names
at boot time. For example:</para>
<programlisting>ifconfig_fxp0_name="net0"
ifconfig_net0="inet 10.0.0.1/16"</programlisting>
<para>The <filename>rc.d/moused</filename> script now
starts/stops/checks a specific device when
the device name is given as the second argument to the script:</para>
<screen>&prompt.root; /etc/rc.d/moused start ums0</screen>
<para>To use different &man.rc.conf.5; knobs with different
mice, use the device name as part of the knob.
For example, if the mouse device is <filename>/dev/ums0</filename>
the following lines can be used:</para>
<programlisting>moused_ums0_enable=yes
moused_ums0_flags="-z 4"
moused_ums0_port="/dev/ums0"</programlisting>
<para>&man.rc.conf.5; now supports the <varname>tmpmfs_flags</varname>
and <varname>varmfs_flags</varname> variables.
These can be used to pass extra options to the &man.mdmfs.8; utility,
to customize the finer details of the &man.md.4; file system creation,
such as to turn on/off softupdates, to specify a default owner
for the file system, and so on. &merged;</para>
</sect3>
</sect2>
<sect2 id="contrib">
<title>Contributed Software</title>
<para><application>FILE</application> has been updated from 4.10
to 4.12.</para>
<para><application>GNU readline</application> has been updated from
version 4.3 to version 5.0.</para>
<para><application>Heimdal</application> has been updated from
0.6.1 to 0.6.3. &merged;</para>
<para><application>lukemftp</application> has been updated from a
26 April 2004 snapshot from OpenBSD's sources to a snapshot as
of 19 February 2005.</para>
<para>A snapshot of <application>netcat</application> from OpenBSD
as of 4 February 2005 has been added. More information can be
found in the &man.nc.1; manual page. &merged;</para>
<para><application>OpenPAM</application> has been updated from the
Eelgrass release to the Feterita release.</para>
<para><application>OpenSSH</application> has been updated from 3.8p1
to 3.9p1.</para>
<para><application>OpenSSL</application> has been updated from
0.9.7d to 0.9.7e. &merged;</para>
<para><application>sendmail</application> has been updated from
version 8.13.1 to version 8.13.3. &merged;</para>
<para>The timezone database has been updated from the
<application>tzdata2004e</application> release to the
<application>tzdata2004g</application> release. &merged;</para>
</sect2>
<sect2 id="ports">
<title>Ports/Packages Collection Infrastructure</title>
<para>The &man.pkg.version.1; utility now supports a
<option>-q</option> flag to suppress the output of the port
version comparison characters <literal>&lt;</literal>,
<literal>=</literal>, and <literal>&gt;</literal>.</para>
<para>The
<filename>ports/INDEX<replaceable>*</replaceable></filename>
files, which kept an index of all of the entries in the ports
collection, have been removed from the CVS repository. &merged;
These files were generated only infrequently, and therefore were
usually out-of-date and inaccurate. Users requiring an index
file (such as for use by programs such as &man.portupgrade.1;)
have two alternatives for obtaining a copy:</para>
<itemizedlist>
<listitem>
<para>Build an index file based on the current ports tree by
running <command>make index</command> from the top of the
<filename>ports/</filename> tree.</para>
</listitem>
<listitem>
<para>Fetch an index file over the network by running
<command>make fetchindex</command> from the top of the
<filename>ports/</filename> tree. This index file will
(typically) be accurate to within a day.</para>
</listitem>
</itemizedlist>
</sect2>
<sect2 id="releng">
<title>Release Engineering and Integration</title>
<para>In prior &os; releases, the <filename>disc1</filename>
CD-ROM (or ISO image) was a bootable installation disk
containing the base system, ports tree, and common packages.
The <filename>disc2</filename> CD-ROM (or ISO image) was a
bootable <quote>fix it</quote> disk with a live filesystem, to
be used for making emergency repairs. This layout has now
changed. For all architectures except ia64, the
<filename>disc1</filename> image now contains the base system
distribution files, ports tree, and the live filesystem, making
it suitable for both an initial installation and repair
purposes. (On the ia64, the live filesystem is on a separate
disk due to its size.) Packages appear on separate
disks. &merged;</para>
<para>The supported version of the
<application>GNOME</application> desktop environment has been
updated from 2.6.2 to 2.8.3. &merged;
<note>
<para>Users of older versions of the
<application>GNOME</application> desktop
(<filename role="package">x11/gnome2</filename>)
must take particular care in upgrading. Simply upgrading it
from the &os; Ports Collection with &man.portupgrade.1;
(<filename role="package">sysutils/portupgrade</filename>)
will cause serious problems.
<application>GNOME</application> desktop users should read
the instructions carefully at
<ulink url="&url.base;/gnome/docs/faq28.html"></ulink>
and use the
<ulink url="&url.base;/gnome/gnome_upgrade.sh"><filename>gnome_upgrade.sh</filename></ulink>
script to properly upgrade to
<application>GNOME</application> 2.8.3.</para>
<para>For casual users of the various
<application>GNOME</application> libraries,
&man.portupgrade.1; should be sufficient.</para> </note>
</para>
<para>The supported version of the <application>KDE</application>
desktop environment has been updated from 3.3.0 to
3.3.2. &merged;</para>
<para>The supported version of <application>Xorg</application> has
been updated from 6.7.0 to 6.8.1. &merged;</para>
</sect2>
<sect2 id="doc">
<title>Documentation</title>
<para>Manual pages in the base system have received a number of
cleanups, both for content and presentation. Cross-references
are more correct and consistent, standard section headings are
now used throughout, and markup has been cleaned up.</para>
</sect2>
</sect1>
<sect1 id="upgrade">
<title>Upgrading from previous releases of &os;</title>
<para>Source upgrades to &os; &release.current; are only supported
from &os; 5.3-RELEASE or later. Users of older systems wanting to
upgrade &release.current; will need to update to &os; 5.3 or newer
first, then to &os; &release.current;.</para>
<important>
<para>Upgrading &os; should, of course, only be attempted after
backing up <emphasis>all</emphasis> data and configuration
files.</para>
</important>
</sect1>