xref: /freebsd/UPDATING (revision e623dcb7016d1b6d188cfd8be357790a7889a2e7)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
49698f2c0SWarner Losh<imp@village.org>.  See end of file for further details.  For commonly
59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file.
6e72fd46aSWarner Losh
7f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
8f59d5f7aSPoul-Henning Kamp	FreeBSD 5.x has many debugging features turned on, in
969f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1069f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1169f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1269f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1369f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1469f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1569f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1669f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1769f7bcf3SWarner Losh	developers choose to disable these features on build machines
18a19f8ddaSDavid E. O'Brien	to maximize performance.
19c1f61aa9SDavid E. O'Brien
20e623dcb7SMarcel Moolenaar20040710:
21e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
22e623dcb7SMarcel Moolenaar
23e623dcb7SMarcel Moolenaar20040710:
24e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
25e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
26e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
27e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
28e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
29e623dcb7SMarcel Moolenaar	of this.
30e623dcb7SMarcel Moolenaar
31e623dcb7SMarcel Moolenaar20040710:
32e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
33e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
34e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
35e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
36e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
37e623dcb7SMarcel Moolenaar	   option for this.
38e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
39e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
40e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
41e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
42e623dcb7SMarcel Moolenaar	   to be enabled seperately now. Use the GDB option for this.
43e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
44e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
45e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
46e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
47e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
48e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
49e623dcb7SMarcel Moolenaar
506421d1dbSMaksim Yevmenkin20040708:
516421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
526421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
536421d1dbSMaksim Yevmenkin
5458af3216SWarner Losh20040702:
5558af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
5658af3216SWarner Losh	There is some report that ULE scheduler was broken in some
5758af3216SWarner Losh	machines and we encourage users using ULE schedluer either
5858af3216SWarner Losh	stick with an known good kernel, or temporary switch to 4BSD
5958af3216SWarner Losh	scheduler as a workaround.
6058af3216SWarner Losh
61c2dba668SNate Lawson20040630:
628ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
638ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
64a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
65a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
66a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
67a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
68a6c26e1cSBruce M Simpson	example of such changes.
698ed370fdSJulian Elischer
7058af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
7158af3216SWarner Losh	over.
7258af3216SWarner Losh
738ed370fdSJulian Elischer20040630:
74c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
75c2dba668SNate Lawson	will be printed on console indicating that ACPI has been disabled
76c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
77c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
78c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
79c2dba668SNate Lawson	loader prompt.
80c2dba668SNate Lawson
818ee2ac9eSMax Laier20040623:
828ee2ac9eSMax Laier	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is priviledge
838ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
848ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
858ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
868ee2ac9eSMax Laier
873db5687dSBrooks Davis20040622:
883db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
893db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
903db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
913db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
923db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
933db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
943db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
953db5687dSBrooks Davis
96e0ae81f3SDag-Erling Smørgrav20040621:
97e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
98e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
99e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
100e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
101e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
102e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
103e0ae81f3SDag-Erling Smørgrav	during the next reboot.
104e0ae81f3SDag-Erling Smørgrav
1054717d22aSJohn Polstra20040614:
1064717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1074717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1084717d22aSJohn Polstra	the ips module and any third-party modules which call
1094717d22aSJohn Polstra	sema_timedwait.
1104717d22aSJohn Polstra
1116cb7a382SMax Laier20040613:
1126cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1136cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
114df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
115df843493SMax Laier	please recompile and reinstall world.
1166cb7a382SMax Laier
1172454685eSJulian Elischer20040607:
1182454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1192454685eSJulian Elischer	requires that you re-run config after updating your tree.
1202454685eSJulian Elischer
12164fef830SSeigo Tanimura20040601:
12264fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
12364fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
12464fef830SSeigo Tanimura	kernel configuration.
12564fef830SSeigo Tanimura
126bb4f06e7SAndre Oppermann20040423:
127bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
128bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
129bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
130bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
131bb4f06e7SAndre Oppermann
13205641e82SColin Percival20040420:
13305641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
13405641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
13505641e82SColin Percival	20040406.
13605641e82SColin Percival
137d0dc9183SWarner Losh20040414:
138d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
139d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
140d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
141d0dc9183SWarner Losh
142d0dc9183SWarner Losh20040412:
143d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
144d0dc9183SWarner Losh	drive is still broken.
145d0dc9183SWarner Losh
146d0dc9183SWarner Losh20040410:
147d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
148d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
149d0dc9183SWarner Losh	the unanticipated problems have been resolved.
150d0dc9183SWarner Losh
1518633bbeaSBrooks Davis20040409:
1528633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1538633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1548633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1558633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
15676c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1578633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1588633bbeaSBrooks Davis
159d40d033aSRobert Watson20040322:
160d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
161d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
162d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
163d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
164d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
165d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
166d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
167d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
168d40d033aSRobert Watson	locking is merged to permit this to take place.
169d40d033aSRobert Watson
170ec9b318eSGarance A Drosehn20040310:
171ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
172ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
173ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
174ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
175ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
176ec9b318eSGarance A Drosehn
177fc28f1ffSMax Laier20040308:
178fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
179fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
1804c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
1814c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
182fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
183fc28f1ffSMax Laier	pf system consists of the following three devices:
184fc28f1ffSMax Laier	device		pf		# required
185fc28f1ffSMax Laier	device		pflog		# optional
186fc28f1ffSMax Laier	device		pfsync		# optional
187fc28f1ffSMax Laier
1883aff5d06SDag-Erling Smørgrav20040303:
1893aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
1903aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
1913aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
1923aff5d06SDag-Erling Smørgrav
1933aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
1943aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
1953aff5d06SDag-Erling Smørgrav
1963aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
1973aff5d06SDag-Erling Smørgrav	to use libpthread instead.
1983aff5d06SDag-Erling Smørgrav
199fd63c5b3SDag-Erling Smørgrav20040226:
2009d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
201fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
202fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
203fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
204fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
205fd63c5b3SDag-Erling Smørgrav
206714ae42aSBruce M Simpson20040225:
207e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
208e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
209e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
210e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
211e07a40f3SBrian Feldman	should remain unaffected.
212e07a40f3SBrian Feldman
213e07a40f3SBrian Feldman20040225:
214714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
215714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
216714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
217714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
218714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
219714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
220714ae42aSBruce M Simpson
221fbd2e692SAndre Oppermann20040224:
222fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
223fbd2e692SAndre Oppermann	and related userland network utilities neccessary.
224fbd2e692SAndre Oppermann
225158b90daSWarner Losh20040222:
226158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
227158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
228158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
229158b90daSWarner Losh	Drivers outside the tree will need to be updated.
230158b90daSWarner Losh
231b7b1e150SMike Makonnen20040207:
232b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
233b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
234b7b1e150SMike Makonnen
235aca89ee6SDaniel Eischen20040130:
236aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
237aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
238aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
239aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
240aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
241aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
242aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
243aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
244aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
245aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
246aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
247aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
248aca89ee6SDaniel Eischen	do not work with libpthread.
249aca89ee6SDaniel Eischen
25068b7b3a9SAlex Dupre20040125:
25168b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
25268b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
25368b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
25468b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
25568b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
25668b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
25768b7b3a9SAlex Dupre
258ff46e0deSWarner Losh20040125:
259ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
260ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
261ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
262ff46e0deSWarner Losh
263ce41f4bfSRobert Watson20031213:
264ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
265ce41f4bfSRobert Watson	if the login process is unable to successfully set the
266ce41f4bfSRobert Watson	process credentials to include all groups defined for the
267ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
268ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
269ce41f4bfSRobert Watson	defined, or they will be unable to log in.
270ce41f4bfSRobert Watson
271c124fa05SJohn Baldwin20031203:
272c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
273c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
274c124fa05SJohn Baldwin
2758ad1f5e4SHartmut Brandt20031112:
27630093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
27730093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
27897209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
27997209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
28097209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
28197209ca3SRobert Watson	not know about the new system calls that support the new statfs
2823f631d52SMarcel Moolenaar	structure.
2833f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
2843f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
2853f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
2863f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
2873f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
2883f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
2893f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
2903f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
2913f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
2923f631d52SMarcel Moolenaar	these changes are installed.
29330093b05SWarner Losh
29430093b05SWarner Losh	****************************DANGER*******************************
29530093b05SWarner Losh
29630093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
29730093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
29830093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
29930093b05SWarner Losh	kernel.
30064a18d6fSKirk McKusick
30164a18d6fSKirk McKusick20031112:
3028ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3038ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3048ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3058ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3068ad1f5e4SHartmut Brandt	sync before rebooting.
3078ad1f5e4SHartmut Brandt
308c53a5d8fSJohn Baldwin20031111:
309c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
310c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
311c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
312c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
313c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
314c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
315c53a5d8fSJohn Baldwin
3168bf455a5SJohn Baldwin20031103:
3178bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3188bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3192a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3208bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3218bf455a5SJohn Baldwin
3229bf40edeSBrooks Davis20031031:
3239bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
3249bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
3259bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
3269bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
3279bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
3289bf40edeSBrooks Davis	reflect this change.
3299bf40edeSBrooks Davis
33047a42c7aSPoul-Henning Kamp20030928:
33147a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
33247a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
33347a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
33447a42c7aSPoul-Henning Kamp
33507105342SMax Khon20030926:
33607105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
33707105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
33807105342SMax Khon
33917dcd026SSam Leffler20030925:
34017dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
34117dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
34217dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
34317dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
34417dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
34517dcd026SSam Leffler
346fedf1d01SBruce M Simpson20030923:
347fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
348fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
349fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
350fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
351fedf1d01SBruce M Simpson
352db38f9cbSJacques Vidrine20030915:
353db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
354db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
355db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
356db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
357db38f9cbSJacques Vidrine
358c09d2c2bSMike Makonnen20030829:
359c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
360c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
361c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
362c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
363c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
364c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
365c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
366c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
367c09d2c2bSMike Makonnen	may or may not exist on your system.
368c09d2c2bSMike Makonnen
36917c159dcSSøren Schmidt20030824:
37017c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
37117c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
372f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
373f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
37417c159dcSSøren Schmidt
375c1f61aa9SDavid E. O'Brien20030819:
376c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
377c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
378c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
379c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
38069f7bcf3SWarner Losh
38138c962e7SNate Lawson20030728:
38238c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
38338c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
38438c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
38538c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
38638c962e7SNate Lawson	so the quirk can be re-enabled.
38738c962e7SNate Lawson
38874111097SWarner Losh20030724:
38974111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
39074111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
39174111097SWarner Losh
392178cf4e9SWarner Losh20030722:
393178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
394178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
395178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
396178cf4e9SWarner Losh	FPU hardware.
397178cf4e9SWarner Losh
398178cf4e9SWarner Losh20030714:
399178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
400178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
401178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
402178cf4e9SWarner Losh	People should report those issues to current@.
403178cf4e9SWarner Losh
404157c629aSWarner Losh20030711:
405157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4068b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
40705538fa9SWarner Losh	/usr/obj.
408157c629aSWarner Losh
40974111097SWarner Losh20030610:
41074111097SWarner Losh	Remove deprecated locale names and transition period code
41174111097SWarner Losh	for them, finishing switching to the new scheme. Check your
41274111097SWarner Losh	LANG environment variable.
41374111097SWarner Losh
41474111097SWarner Losh20030609:
41574111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
41674111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
41774111097SWarner Losh	important to remember beforehand if your source tree is on
41874111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
41974111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
42074111097SWarner Losh	kernel.
42174111097SWarner Losh
42274111097SWarner Losh20030605:
4236cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
4246cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
4256cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
4266cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
4276cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
4286cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
4296cc6353fSMarcel Moolenaar
4306cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
4316cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
4326cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
4336cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
4346cc6353fSMarcel Moolenaar		:
4356cc6353fSMarcel Moolenaar
4366cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
4376cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
4386cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
4396cc6353fSMarcel Moolenaar
44052b47445SMark Murray20030505:
44152b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
44252b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
44352b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
44452b47445SMark Murray
445a26df538SWarner Losh20030502:
446a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
447a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
448a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
449a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
450a26df538SWarner Losh
4514b065e2cSDoug Barton20030501:
4524b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4534b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4544b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4554b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4564b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4574b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4584b065e2cSDoug Barton
45981cda3d9SWarner Losh20030423:
46081cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
46181cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
46281cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
46381cda3d9SWarner Losh	have until then to upgrade your kernel before updating
46481cda3d9SWarner Losh	userland.  In general, you should have a userland and
46581cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
46681cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
46781cda3d9SWarner Losh	allowances are made.
46881cda3d9SWarner Losh
46947a657d1SRuslan Ermilov20030329:
47047a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
47147a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
47247a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
47347a657d1SRuslan Ermilov
47447a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
47547a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
47647a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
47747a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
47847a657d1SRuslan Ermilov
47947a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
48047a657d1SRuslan Ermilov	    make cleandir && make obj && \
48147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
48247a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
48347a657d1SRuslan Ermilov
4845d2af00cSGregory Neil Shapiro20030208:
4855d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
4865d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
4875d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
4885d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
4895d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
4905d2af00cSGregory Neil Shapiro
4915d2af00cSGregory Neil Shapiro20030128:
4929db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
493ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
4949db58771SPoul-Henning Kamp	be removed when convenient.
4959db58771SPoul-Henning Kamp
4968d9b3f57SJake Burkholder20030126:
4978d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
4988d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
4998d9b3f57SJake Burkholder
5001c5efda5SJeff Roberson20030125:
5011c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5021c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
503ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5041c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5051c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5061c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5071c5efda5SJeff Roberson
5089d1d64f5SWarner Losh20030115:
5099d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5109d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5119d1d64f5SWarner Losh	properly.
5129d1d64f5SWarner Losh
513c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
514c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
515c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
516c9fdb80aSWarner Losh	with NetBSD.
517c9fdb80aSWarner Losh
518161dc364SAlexander Kabaev20021222:
519161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
520161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
521161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
522161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
523161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
524161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
52584cc83efSAlexander Kabaev	rebuilt.
526161dc364SAlexander Kabaev
527fb4c8061SMartin Blapp20021216:
528fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
52989056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
530fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
5319d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
532fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
533fb4c8061SMartin Blapp
53417d47eb3SGiorgos Keramidas20021202:
53517d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
53617d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
53717d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
53817d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
53917d47eb3SGiorgos Keramidas
540a4459294SBill Fenner20021029:
541a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
542a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
543a4459294SBill Fenner	consumers in sync.
544a4459294SBill Fenner
545fc8c157fSWarner Losh20021024:
546c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
547c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
548c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
549c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
550c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
551c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
552c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
553c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
55469f7bcf3SWarner Losh
555fd9e8bdaSAndrew Gallatin20021023:
556fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
557fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
558fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
559fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
560fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
561fd9e8bdaSAndrew Gallatin
562fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
563fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
564fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
565fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
566fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
567fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
568fd9e8bdaSAndrew Gallatin
569f8a4c901SWarner Losh20020831:
570f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
571f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
572f8a4c901SWarner Losh	programs and libraries need to be recompiled.
573f8a4c901SWarner Losh
574f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
575f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
576f8a4c901SWarner Losh
577c2248fa2SJens Schweikhardt20020827:
578c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
579c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
580c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
581c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
582c2248fa2SJens Schweikhardt
5830d533e43SRuslan Ermilov20020815:
5840d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
5850d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
5860d533e43SRuslan Ermilov	again.
5870d533e43SRuslan Ermilov
58833c1de7dSRuslan Ermilov20020729:
58933c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
59033c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
59133c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
59233c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
59333c1de7dSRuslan Ermilov
5942b877facSJulian Elischer20020702:
5952b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
5962b877facSJulian Elischer	There are still some minor problems with some signals but the
5972b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
5982b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
5992b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6002b877facSJulian Elischer
60106596d37SWarner Losh20020701:
60206596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
60306596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
60406596d37SWarner Losh	GNOME.
60506596d37SWarner Losh
60695ba4330SJacques Vidrine20020511:
60795ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
60895ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
60995ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
61095ba4330SJacques Vidrine	with the set-user-ID bit set.
61195ba4330SJacques Vidrine
612a81da3c9SDavid E. O'Brien20020510:
613f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
614f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6154b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
616f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
617f50caf6fSDavid E. O'Brien
618f50caf6fSDavid E. O'Brien20020510:
619a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
620a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
621a81da3c9SDavid E. O'Brien	and then do a cvs update.
622a81da3c9SDavid E. O'Brien
623528a0ef5SJacques Vidrine20020421:
624528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
625528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
626528a0ef5SJacques Vidrine
62785aa5a2eSGregory Neil Shapiro20020404:
62885aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
62985aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
63085aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
63185aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
63285aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
63385aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
63485aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
63585aa5a2eSGregory Neil Shapiro
6368f1e4358SRuslan Ermilov20020403:
6378f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
6388f1e4358SRuslan Ermilov
6392292c02eSWarner Losh20020315:
6402292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
6412292c02eSWarner Losh
64269f7bcf3SWarner Losh20020225:
64369f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
64469f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
64569f7bcf3SWarner Losh
6468f35c493SWarner Losh20020217:
6478f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6488f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6498f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6508f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6518f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6528f35c493SWarner Losh
653835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
654835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
655835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
656835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
657835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
658835284beSWarner Losh	and group must be merged from src/etc/group and
659835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
660835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
661835284beSWarner Losh	mergemaster before this will work if you are updating from a
662835284beSWarner Losh	very old version of current.  The updating recipe has changed
663835284beSWarner Losh	as of this date.
664835284beSWarner Losh
665fa9401c1SWarner Losh20020112:
666fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
667fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
668fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
669fa9401c1SWarner Losh	you have local modifications, you can use
670fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
671fa9401c1SWarner Losh	/etc/pam.d.
672fa9401c1SWarner Losh
673fa9401c1SWarner Losh	Please see the following url for more details:
674fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
67547d0d01fSWarner Losh20011229:
67647d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
67747d0d01fSWarner Losh	networkfs_types, please note that it has changed
67847d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
67947d0d01fSWarner Losh
680514318a8SWarner Losh20011220:
681514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
682514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
683514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
684514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
685514318a8SWarner Losh	version have now been merged back into the base system's
686514318a8SWarner Losh	version now.  The only user-visible change resulting from this
687514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
688514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
689514318a8SWarner Losh	as well.  (There has never been rc file support for
690514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
691514318a8SWarner Losh	reverted by the time the changes are MFCed.)
692514318a8SWarner Losh
693514318a8SWarner Losh20011215:
694514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
695514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
696514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
697514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
698514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
699514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
700514318a8SWarner Losh	will need to be customized then for `odd' densities using
701514318a8SWarner Losh	fdcontrol(8).
702514318a8SWarner Losh
7032d22e2bfSWarner Losh20011209:
7042d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7052d22e2bfSWarner Losh	and truss(1) now works again.
7062d22e2bfSWarner Losh
7079e0428e2SWarner Losh20011207:
7089e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7099e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7109e0428e2SWarner Losh	see
7119e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7129e0428e2SWarner Losh	for details.
7139e0428e2SWarner Losh
7149bab8c59SWarner Losh20011204:
7159bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7169bab8c59SWarner Losh	kernel and burncd to be in sync.
7179bab8c59SWarner Losh
718e57d8b01SWarner Losh20011203:
719e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
720e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
721e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
722e57d8b01SWarner Losh	not there already.
723e57d8b01SWarner Losh
724e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
725e57d8b01SWarner Losh	until the issue has been resolved.
726e57d8b01SWarner Losh
727b001d36fSJacques Vidrine20011202:
728b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
729b001d36fSJacques Vidrine	patched.
730b001d36fSJacques Vidrine
7314b676ec1SWarner Losh20011126:
7324b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
7335ebbf43eSWarner Losh	after this date.  You need to do this only once.
7344b676ec1SWarner Losh
735d961e462SWarner Losh20011103:
736d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
737d961e462SWarner Losh	edges may be left, but for the most part things should be
7384b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
739d961e462SWarner Losh
740d961e462SWarner Losh20011030:
741d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
742d961e462SWarner Losh	choppy waves in the upgrade process.
743d961e462SWarner Losh
7441fe003b6SWarner Losh20011030:
745a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7461fe003b6SWarner Losh
7471fe003b6SWarner Losh20011027:
7481fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7491fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7501fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7511fe003b6SWarner Losh	try to use from this date forward.
7521fe003b6SWarner Losh
7531fe003b6SWarner Losh20011025:
7541fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7551fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7561fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7571fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7581fe003b6SWarner Losh	TARGET_ARCH=i386.
7591fe003b6SWarner Losh
760d05f9643SWarner Losh20011001:
761d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
762d05f9643SWarner Losh	You must recompile both the kernel and userland applications
763d05f9643SWarner Losh	at the same time.
764d05f9643SWarner Losh
76558970f85SWarner Losh20010929:
76658970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
76758970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
76858970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
76958970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
7709d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
77158970f85SWarner Losh
77258970f85SWarner Losh20010927:
77358970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
77458970f85SWarner Losh	To disable ACPI you can add
77566ff0e67SMax Khon		hint.acpi.0.disabled="1"
77658970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
77758970f85SWarner Losh	loader "ok" prompt).
77858970f85SWarner Losh
77958970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
78058970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
78158970f85SWarner Losh	file and not list acpi in that list.
782378f4486SAlfred Perlstein
7835119d237SWarner Losh20010924:
7845119d237SWarner Losh	The buildworld has been fixed.  You may need to install
7855119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
7868b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
7878b039fffSWarner Losh	get them installed on every installworld, or execute the
7888b039fffSWarner Losh	following to get them installed only once:
7898b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
79058970f85SWarner Losh		make all install
7918b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
7925119d237SWarner Losh
7933c293725SWarner Losh20010919:
7943c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
7953c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
7963c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
797772730c7SWarner Losh	workaround is to add
7983c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
7993c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8003c293725SWarner Losh	can be removed afterwards.
8013c293725SWarner Losh
8023c293725SWarner Losh	A proper fix to the buildworld target is needed.
8033c293725SWarner Losh
8043c293725SWarner Losh20010918:
8053c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8063c293725SWarner Losh	NFS may be unstable after this date.
8073c293725SWarner Losh
8083c293725SWarner Losh20010912:
8093c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8103c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8113c293725SWarner Losh	initial commit, most of the major ones have been found and
8123c293725SWarner Losh	corrected.
8133c293725SWarner Losh
8143c293725SWarner Losh20010901:
8153c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8163c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8173c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8183c293725SWarner Losh	have been rectified around this date.
8193c293725SWarner Losh
82098b17b95SWarner Losh20010823:
82198b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
82298b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
82398b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
82498b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
82598b17b95SWarner Losh 	sure that user or group bind has read (and not write)
82698b17b95SWarner Losh 	permission for your name server configuration and that it
82798b17b95SWarner Losh 	has read and write permission for your slave zone files and
82898b17b95SWarner Losh 	directory.
82998b17b95SWarner Losh
83098b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
83198b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
83298b17b95SWarner Losh
83398b17b95SWarner Losh 		named_flags=
83498b17b95SWarner Losh
8357b9786edSMark Murray20010709:
8367b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
8377b9786edSMark Murray	the ability of the shared library major number to handle.
8387b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
8397b9786edSMark Murray	solution is to rebuild those ports.
8407b9786edSMark Murray
8411d28950eSWarner Losh20010628:
8421d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
8431d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8441d28950eSWarner Losh
845e72fd46aSWarner Losh20010625:
84698b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
84798b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
84898b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
84998b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
85098b17b95SWarner Losh	IRQ configuration needs more safety belts.
85116de1a07SWarner Losh
8520d415dffSWarner Losh20010617:
853e72fd46aSWarner Losh	Softupdates problems have been corrected.
8540d415dffSWarner Losh
8550d415dffSWarner Losh20010614:
8560d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8570d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8580d415dffSWarner Losh	kernel building methods.
8590d415dffSWarner Losh
8608b9959adSWarner Losh20010613:
8618b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
8628b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
863e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
864e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
8658b9959adSWarner Losh
866e72fd46aSWarner Losh20010613:
8678b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
868e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
869e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
8708b9959adSWarner Losh
8710d415dffSWarner Losh20010612:
8720d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
8730d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
8740d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
8750d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
8760d415dffSWarner Losh	until this bug is fixed.
8770d415dffSWarner Losh
878e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
879e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
880ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
881e72fd46aSWarner Losh
8820d415dffSWarner Losh20010610:
8830d415dffSWarner Losh	Locale names have changed to match other systems better.
8840d415dffSWarner Losh
8856ccdb5e4SWarner Losh20010604:
8866ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
8876ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
8886ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
8893590182eSWarner Losh	Interrupt storms look a lot like a hang.
8903590182eSWarner Losh
8913590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
8923590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
8933590182eSWarner Losh	it is).
8943590182eSWarner Losh
8953590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
8963590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
8973590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
8983590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
8996ccdb5e4SWarner Losh
9000bc62786SWarner Losh20010530:
9010bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9020bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9030bc62786SWarner Losh	a limited time.  If you see
9040bc62786SWarner Losh
9050bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9060bc62786SWarner Losh
9070bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9080bc62786SWarner Losh	COPY=-C.
9090bc62786SWarner Losh
91068a38c6cSWarner Losh20010525:
911b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
912c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
913c4f4a728SWarner Losh	definitely is in bad shape.
91468a38c6cSWarner Losh
915ed0f29caSWarner Losh20010521:
916ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
917ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
918ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
919ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
920ed0f29caSWarner Losh	is
921ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
922ed0f29caSWarner Losh
92380c16af9SWarner Losh20010520:
92468a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
92580c16af9SWarner Losh
92680c16af9SWarner Losh20010519:
92780c16af9SWarner Losh	pccard has had much reorganizational work done to it over
92880c16af9SWarner Losh	the past few days.  Everything should still work, but if
92980c16af9SWarner Losh	not, please contact imp@freebsd.org.
93080c16af9SWarner Losh
931a45f2d05SWarner Losh20010517:
932a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
933a45f2d05SWarner Losh	userland at the same time.
934a45f2d05SWarner Losh
935a45f2d05SWarner Losh20010517:
936a45f2d05SWarner Losh	New ncurses imported.
937a45f2d05SWarner Losh
9382988afcaSWarner Losh20010512:
9392988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
9402988afcaSWarner Losh	will be the only way to go starting July 1.
9412988afcaSWarner Losh
9421a33dba7SWarner Losh20010504:
9431a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9441a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9451a33dba7SWarner Losh
94609946a51SWarner Losh20010502:
94709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
94809946a51SWarner Losh
94909946a51SWarner Losh20010501:
95009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
95109946a51SWarner Losh
95209946a51SWarner Losh20010430:
953a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
95409946a51SWarner Losh	go back in the water.
95509946a51SWarner Losh
95609946a51SWarner Losh20010429:
95709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
95809946a51SWarner Losh	this date, but before the correction date.
95909946a51SWarner Losh
96091dd3b53SWarner Losh20010423:
96191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
96291dd3b53SWarner Losh
96391dd3b53SWarner Losh20010411:
96491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
96591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
96691dd3b53SWarner Losh	Update only if you understand that you must not use the old
96791dd3b53SWarner Losh	fsck with the new kernel ever.
96891dd3b53SWarner Losh
969933b3269SWarner Losh20010330:
970933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
971c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
972933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
973933b3269SWarner Losh
974933b3269SWarner Losh20010319:
975933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
976933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
977933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
978f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
97909946a51SWarner Losh
98009946a51SWarner Losh20010315:
98109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
982ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
98309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
984933b3269SWarner Losh
985933b3269SWarner Losh20010312:
986933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
987933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
988933b3269SWarner Losh
989933b3269SWarner Losh20010312:
990933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
991933b3269SWarner Losh	instead of ad-hoc.
992933b3269SWarner Losh
993933b3269SWarner Losh20010310:
994f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
995933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
996933b3269SWarner Losh	ssh might not work if you don't.
997933b3269SWarner Losh
99862353691SWarner Losh20010303:
99962353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
100062353691SWarner Losh	which means that you must include the miibus in your kernel if
100162353691SWarner Losh	you use the ed driver.
100262353691SWarner Losh
1003d325cf65SWarner Losh20010220:
1004d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1005d325cf65SWarner Losh	safe to go back into the water.
1006d325cf65SWarner Losh
1007024daae6SWarner Losh20010211:
1008024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1009024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1010024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1011024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1012024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1013024daae6SWarner Losh
1014024daae6SWarner Losh	To get to the new system, you'll need to use the following
1015024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1016024daae6SWarner Losh	don't have to move this to the updating section.
1017024daae6SWarner Losh
1018024daae6SWarner Losh	To get around the installworld problem, do:
1019024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1020024daae6SWarner Losh		# make install
1021024daae6SWarner Losh		# cd /usr/src
1022024daae6SWarner Losh		# make installworld
1023024daae6SWarner Losh	If that doesn't work, then try:
1024024daae6SWarner Losh		# make -k installworld
1025024daae6SWarner Losh		# make installworld
1026024daae6SWarner Losh
1027024daae6SWarner Losh20010207:
1028024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1029024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1030024daae6SWarner Losh
1031024daae6SWarner Losh20010205:
10327595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1033024daae6SWarner Losh	Remove them from your config.
1034024daae6SWarner Losh
10351e159248SWarner Losh20010122:
10361e159248SWarner Losh	****************************** WARNING ******************************
10371e159248SWarner Losh			buildkernel has been changed slightly
10381e159248SWarner Losh	****************************** WARNING ******************************
10391e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
10401e159248SWarner Losh	should update your scripts and make.conf accordingly.
10411e159248SWarner Losh
10421e159248SWarner Losh20010119:
10431e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10441e159248SWarner Losh	This requires a new config to build correctly.
10451e159248SWarner Losh
1046aac7dfeaSWarner Losh20010116:
1047ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1048aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1049aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1050aac7dfeaSWarner Losh
1051aac7dfeaSWarner Losh20010110:
1052aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1053aac7dfeaSWarner Losh
1054aac7dfeaSWarner Losh20010102:
1055aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1056aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1057aac7dfeaSWarner Losh
105863c90c9eSWarner Losh20010101:
105963c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
106063c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
10615fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
106263c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
106363c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
106463c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
106563c90c9eSWarner Losh	might have been ignored by the -k option.
106663c90c9eSWarner Losh
10675fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
10685fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
10695fd2a895SWarner Losh	of this working.
10705fd2a895SWarner Losh
1071aac7dfeaSWarner Losh20001228:
1072aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1073ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1074aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1075aac7dfeaSWarner Losh
1076de2bcc63SWarner Losh20001218:
1077de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1078de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1079de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1080de2bcc63SWarner Losh	cards will not be recognized without it.
1081de2bcc63SWarner Losh
1082960773f7SWarner Losh20001205:
1083960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1084960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1085960773f7SWarner Losh	adding the following in pam.conf:
1086960773f7SWarner Losh
1087960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1088960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1089960773f7SWarner Losh	sshd    session required        pam_permit.so
1090960773f7SWarner Losh
10910acc635eSWarner Losh20001031:
10920acc635eSWarner Losh	cvs updated to 1.11.
10930acc635eSWarner Losh
10940acc635eSWarner Losh20001020:
10950acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
10960acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
10970acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
10980acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
10990acc635eSWarner Losh	workaround.
11000acc635eSWarner Losh
11010acc635eSWarner Losh20001010:
11020acc635eSWarner Losh	****************************** WARNING ******************************
11030acc635eSWarner Losh				Sendmail has been updated.
11040acc635eSWarner Losh	****************************** WARNING ******************************
11050acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11060acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11070acc635eSWarner Losh	  is set.
11080acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11090acc635eSWarner Losh	  commands.
11100acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11110acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11120acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11130acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11140acc635eSWarner Losh
11150acc635eSWarner Losh	More details can be found at
11160acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11170acc635eSWarner Losh
11186e98a146SWarner Losh20001009:
11196e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11206e98a146SWarner Losh	your entire ports tree, or you will have problems.
11216e98a146SWarner Losh
11226e98a146SWarner Losh20001006:
1123685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
11246e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
11256e98a146SWarner Losh	/usr/bin/miniperl.
11266e98a146SWarner Losh
1127073113a4SWarner Losh20001005:
1128073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1129685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1130073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1131073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1132073113a4SWarner Losh	tree for anything to work.
1133073113a4SWarner Losh
11340acc635eSWarner Losh20000928:
11350acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
11360acc635eSWarner Losh
1137be3885b3SWarner Losh20000916:
1138be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1139be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1140be3885b3SWarner Losh	same time as your kernel.
1141be3885b3SWarner Losh
114276ec9675SWarner Losh20000914:
114376ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
114476ec9675SWarner Losh	include the device will cause suspended laptops losing time
114576ec9675SWarner Losh	when they resume.  Include
114676ec9675SWarner Losh		device		pmtimer
114776ec9675SWarner Losh	in your config file and
114801b9a434SWarner Losh		hint.pmtimer.0.at="isa"
114976ec9675SWarner Losh	to your /boot/device.hints file.
115076ec9675SWarner Losh
1151f4865386SMark Murray20000911:
1152f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1153f4865386SMark Murray	rather than an option. The supplied kernel config files have
1154f4865386SMark Murray	been updated. You will need to do something similar in your
1155f4865386SMark Murray	own kernel config file.
1156f4865386SMark Murray	Remove:
1157f4865386SMark Murray		options		RANDOMDEV
1158f4865386SMark Murray	Add:
1159f4865386SMark Murray		device		random
1160f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1161f4865386SMark Murray	nothing.
1162f4865386SMark Murray
1163d594498fSWarner Losh20000909:
1164d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1165d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1166d594498fSWarner Losh	reflect this if you load this module at boot time.
1167d594498fSWarner Losh	The line should read:
1168d594498fSWarner Losh		random_load="YES"
1169d594498fSWarner Losh
11700deb7ddcSWarner Losh20000907:
11710deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
117216eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
117316eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
117416eb772dSWarner Losh	sure you don't have model loading problems which might at
117516eb772dSWarner Losh	first blush appear related to SMP.
117652bf24e7SWarner Losh
11775a01880bSWarner Losh20000906:
11785a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
11795a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
11805a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
11815a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
11825a01880bSWarner Losh	don't have one, and you have host.conf.
11835a01880bSWarner Losh
11842b41163cSWarner Losh20000905:
118538d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
118638d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
118738d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
118838d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
118938d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
119038d6ecd2SWarner Losh
119138d6ecd2SWarner Losh20000905:
11928aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
11938aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
11948aab4bc7SWarner Losh	is /boot/kernel.
11958aab4bc7SWarner Losh
11968aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
119738d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
119838d6ecd2SWarner Losh	installkernel/installworld dance.
11992b41163cSWarner Losh
1200d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1201d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1202d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1203d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1204d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1205d594498fSWarner Losh
1206d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1207d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1208d594498fSWarner Losh		chflags noschg /kernel.old
1209d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1210d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1211d594498fSWarner Losh	fi
1212d594498fSWarner Losh
1213c22a309cSWarner Losh20000904:
1214c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1215c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1216c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1217c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1218c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1219c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1220c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1221c22a309cSWarner Losh	is not likely to be generated.
1222c22a309cSWarner Losh
1223fdb9f54dSWarner Losh20000825:
1224fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
12259c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
12269c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
12279c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
12289c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
12299c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
12309c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
12319c1a7444SWarner Losh	kernel.
12329c1a7444SWarner Losh
12339c1a7444SWarner Losh20000821:
12349c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
12359c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
12369c1a7444SWarner Losh	/boot/loader.conf.
1237fdb9f54dSWarner Losh
12388f250aa7SWarner Losh20000812:
12395da0d091SWarner Losh	suidperl is now always built and installed on the system, but
12405da0d091SWarner Losh	with permissions of 511.  If you have applications that use
12415da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
12425da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
12435da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12445da0d091SWarner Losh	will fix this until the next build.
12455da0d091SWarner Losh
12465da0d091SWarner Losh20000812:
12478f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12488f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12498f250aa7SWarner Losh	include:
12508f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12518f250aa7SWarner Losh	- newaliases limited to root and trusted users
12528f250aa7SWarner Losh	- MSA port (587) turned on by default
12538f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12548f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12558f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12568f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12578f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12588f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12598f250aa7SWarner Losh
126071c38472SWarner Losh20000810:
126171c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
126271c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
126371c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
126471c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
126571c38472SWarner Losh	specific use for it.
126671c38472SWarner Losh
126771c38472SWarner Losh20000729:
126871c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
126971c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
127071c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
127171c38472SWarner Losh	afterwards (unless the variables already are set, of course):
127271c38472SWarner Losh		# Enable network daemons for user convenience.
127371c38472SWarner Losh		inetd_enable="YES"
127471c38472SWarner Losh		portmap_enable="YES"
127571c38472SWarner Losh		sendmail_enable="YES"
127671c38472SWarner Losh
127771c38472SWarner Losh20000728:
127871c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
127971c38472SWarner Losh	will need to change that to nullfs_load="YES".
128071c38472SWarner Losh
12811dece4a9SWarner Losh20000728:
12821dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
12831dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
12841dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
12851dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
12861dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
12871dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
12881dece4a9SWarner Losh	to /MYKERNEL.
12891dece4a9SWarner Losh
1290409e887cSWarner Losh20000711:
1291409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1292409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1293409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1294409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1295409e887cSWarner Losh	for details on potential problems that you might have and how
1296409e887cSWarner Losh	to get around them.
1297409e887cSWarner Losh
1298409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1299409e887cSWarner Losh	clauses above, you needn't worry.
1300409e887cSWarner Losh
1301409e887cSWarner Losh20000711:
1302409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1303409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1304409e887cSWarner Losh	in the number of changed programs the first time when you run
1305409e887cSWarner Losh	mergemaster to get a new /etc/security.
1306409e887cSWarner Losh
1307673d13f2SWarner Losh20000710:
1308673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1309673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1310673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1311673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1312673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1313673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1314673d13f2SWarner Losh	errors. (see below, 20000624).
1315673d13f2SWarner Losh
1316bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13171dece4a9SWarner Losh
1318673d13f2SWarner Losh20000709:
1319c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1320c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1321c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1322673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1323673d13f2SWarner Losh
1324e98e26cdSWarner Losh20000706:
1325e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1326e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1327e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1328f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1329e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
13302c021c6cSMark Ovens	interim if needed.
1331e98e26cdSWarner Losh
1332e98e26cdSWarner Losh20000705:
1333e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1334e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1335e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1336e98e26cdSWarner Losh	details.
1337e98e26cdSWarner Losh
1338c373950eSWarner Losh20000704:
13392f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
13402f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
13412f961bc8SWarner Losh
13422f961bc8SWarner Losh20000704:
1343c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1344c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1345c373950eSWarner Losh	rc.d scripts that haven't been updated.
1346c373950eSWarner Losh
134727dc3a2bSWarner Losh20000630:
134827dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
134927dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
135027dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
135127dc3a2bSWarner Losh
1352b8c215acSWarner Losh20000625:
1353b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
135427dc3a2bSWarner Losh	system installed in order to build the system and kernel.
135527dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
135627dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
135727dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
135827dc3a2bSWarner Losh	were required.  You should check with the latest collections
135927dc3a2bSWarner Losh	to make sure that these haven't changed.
1360b8c215acSWarner Losh
13617b990719SWarner Losh20000624:
13627b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
13637b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
13647b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
13651a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
13667b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
13677b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
13687b990719SWarner Losh	date to the completion of the work.
13697b990719SWarner Losh
137027dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
137127dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
137227dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
137327dc3a2bSWarner Losh	recreate the random and urandom devices.
137427dc3a2bSWarner Losh
137581e54c50SWarner Losh20000622:
137681e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
137781e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
137881e54c50SWarner Losh	that used to be required when updating.
137981e54c50SWarner Losh
138039943833SWarner Losh20000621:
13812c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
13822a2f33fbSDaniel Baker	the config file update procedure.
13832a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1384c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
138559df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
138659df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
138739943833SWarner Losh
1388290f9ad8SWarner Losh20000620:
1389290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1390290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1391290f9ad8SWarner Losh	that workaround will no longer be required.
1392290f9ad8SWarner Losh
139390fb6346SWarner Losh20000615:
139490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
139590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
139690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
139790fb6346SWarner Losh	devices.
139890fb6346SWarner Losh
1399f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1400f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1401f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1402f75f65bbSWarner Losh	may work).
1403f75f65bbSWarner Losh
1404ba26da8eSWarner Losh20000612:
1405ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1406290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1407c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1408290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1409f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1410f54a3542SWarner Losh	NEWCARD for examples of the new format.
1411290f9ad8SWarner Losh
14129698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14139698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14149698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14159698f2c0SWarner Losh	in it.
1416bbcc5149SWarner Losh
1417d65850ebSWarner Losh20000522:
1418ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1419d65850ebSWarner Losh	building a kernel after this point is advised that they need
1420d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1421d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1422d65850ebSWarner Losh
1423d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1424d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1425d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1426d9583a00SWarner Losh	is resolved.
1427d9583a00SWarner Losh
14288039cedeSWarner Losh20000513:
14298039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
14308039cedeSWarner Losh
1431d65850ebSWarner Losh20000510:
14328039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
14338039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
14348039cedeSWarner Losh	is requires for the boot blocks to build properly.
14358039cedeSWarner Losh
14368039cedeSWarner Losh20000503:
14378039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
14388039cedeSWarner Losh	is now available.
14398039cedeSWarner Losh
1440d65850ebSWarner Losh20000502:
1441d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1442d65850ebSWarner Losh	connected to the kernel building instead.
1443d65850ebSWarner Losh
1444be149406SNik Clayton20000427:
14458039cedeSWarner Losh	You may need to build gperf
14468039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14478039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14488039cedeSWarner Losh	an option only in -current.
14498039cedeSWarner Losh
14502b8dd5f4SWarner Losh20000417:
14512b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1452f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14532b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14542b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14552c021c6cSMark Ovens	before you reboot, you'll need to issue:
14562b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14572b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14582b8dd5f4SWarner Losh
14598d9f1945SWarner Losh20000320:
14602b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
14612b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
14622b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1463ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
14642b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
14658d9f1945SWarner Losh
1466f8ab1dd6SWarner Losh20000319:
1467f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1468f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1469f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1470f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1471f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1472f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1473f8ab1dd6SWarner Losh
147419cada77SWarner Losh20000318:
1475f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
147619cada77SWarner Losh	Large kernel changes are being committed and are in the
147719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
147819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
147919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
148019cada77SWarner Losh	that you are loading are up to date.
1481ba228352SWarner Losh
148219cada77SWarner Losh20000315:
14836d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
14846d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
14856d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
14866d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
14876d23c382SWarner Losh	boot.
14886d23c382SWarner Losh
14896d23c382SWarner Losh20000315:
149019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
149119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
149257199806SWarner Losh
1493dc0dbf5cSWarner LoshCOMMON ITEMS:
1494dc0dbf5cSWarner Losh
1495a24eff53SWarner Losh	General Notes
1496a24eff53SWarner Losh	-------------
1497a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1498a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1499a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1500a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1501a24eff53SWarner Losh	or several minor releases, or when several months have passed
1502a24eff53SWarner Losh	on the -current branch).
1503a24eff53SWarner Losh
15045780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15055780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15065780f3baSWarner Losh	environment when searching for values for global variables.
15075780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15085780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15095780f3baSWarner Losh	page for more details.
15105780f3baSWarner Losh
1511dc0dbf5cSWarner Losh	To build a kernel
1512dc0dbf5cSWarner Losh	-----------------
1513ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1514f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1515ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1516282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1517282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1518dc0dbf5cSWarner Losh
1519ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1520ba01eb20SWarner Losh	--------------------------------------------------------------
15210fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15220fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
15230fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
15240fbd2da9SKen Smith
15250fbd2da9SKen Smith	cd src/sys/${arch}/conf
152647d0d01fSWarner Losh	config KERNEL_NAME_HERE
15270fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1528ba01eb20SWarner Losh	make depend
1529ba01eb20SWarner Losh	make
1530ba01eb20SWarner Losh	make install
1531ba01eb20SWarner Losh
1532ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1533ba01eb20SWarner Losh
1534ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1535ba01eb20SWarner Losh	-----------------------------------------------------------
153663cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
153763cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
153863cb445eSWarner Losh
1539f643de42SWarner Losh	<make sure you have good level 0 dumps>
154063cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
154163cb445eSWarner Losh	make buildworld
154263cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
154363cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
154463cb445eSWarner Losh							[1]
154563cb445eSWarner Losh	<reboot in single user>				[3]
15468633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
154763cb445eSWarner Losh	mergemaster -p					[5]
154863cb445eSWarner Losh	make installworld
154963cb445eSWarner Losh	mergemaster					[4]
155063cb445eSWarner Losh	<reboot>
155163cb445eSWarner Losh
1552759f0aefSWarner Losh
1553f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1554f27b1fceSJoseph Koshy	--------------------------------------------------
1555f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1556f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1557f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1558f27b1fceSJoseph Koshy	# size.
1559f27b1fceSJoseph Koshy
1560f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1561f27b1fceSJoseph Koshy	<boot into -stable>
1562f27b1fceSJoseph Koshy	make buildworld
1563f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1564f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1565f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1566f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1567f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1568f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1569f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1570f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1571f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1572f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1573f27b1fceSJoseph Koshy	<reboot into current>
1574f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1575f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1576f27b1fceSJoseph Koshy 	<reboot>
1577f27b1fceSJoseph Koshy
1578f27b1fceSJoseph Koshy
1579f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1580f27b1fceSJoseph Koshy	----------------------------------------------
15815c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
15825c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
15835c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
15845c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1585ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1586f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1587f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1588f643de42SWarner Losh	# space on /.
1589f643de42SWarner Losh
1590f643de42SWarner Losh	<make sure you have good level 0 dumps>
1591fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
159221c075eaSWarner Losh	make buildworld					[9]
1593c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1594802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1595be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1596802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1597fc8c157fSWarner Losh							[1]
1598fc8c157fSWarner Losh	<reboot in single user>				[3]
1599802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1600835284beSWarner Losh	mergemaster -p					[5]
1601f8a4c901SWarner Losh	rm -rf /usr/include/g++
1602ba26da8eSWarner Losh	make installworld
1603802fc49dSBrian Feldman	mergemaster -i					[4]
1604ba26da8eSWarner Losh	<reboot>
1605ba26da8eSWarner Losh
1606fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1607fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1608fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1609fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1610fdb9f54dSWarner Losh	the UPDATING entries.
1611ba26da8eSWarner Losh
16121dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16131dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16141dece4a9SWarner Losh	your sources that you have read and understood all the recent
16151dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16161dece4a9SWarner Losh	much fewer pitfalls.
16171dece4a9SWarner Losh
1618134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1619134d2e86SWarner Losh	should disable them at this point so they don't crash your
1620134d2e86SWarner Losh	system on reboot.
1621134d2e86SWarner Losh
16229c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
16239c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
16249c1a7444SWarner Losh	configuration.
16259c1a7444SWarner Losh
1626ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1627ee6e1fc3SWarner Losh		fsck -p
1628ee6e1fc3SWarner Losh		mount -u /
1629ee6e1fc3SWarner Losh		mount -a
1630ee6e1fc3SWarner Losh		cd /usr/src
163147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1632f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1633f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1634b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1635b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1636b705ae10SWarner Losh	be ignored while you proceed to the next step.
1637ee6e1fc3SWarner Losh
1638a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1639a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1640a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1641a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1642a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1643a6cd4f9dSWarner Losh	for potential gotchas.
1644a6cd4f9dSWarner Losh
1645835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1646835284beSWarner Losh	you may need to do this if you get unknown user in the following
1647835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1648835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1649835284beSWarner Losh	install) after the buildworld before this step if you last updated
1650835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1651835284beSWarner Losh
1652bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1653bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1654bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1655bd79cf40SWarner Losh		ok unload
1656bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1657bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1658bd79cf40SWarner Losh	described here.
1659fc8c157fSWarner Losh
1660fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1661fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1662fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1663fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1664fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1665fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1666fc8c157fSWarner Losh
1667c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1668c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1669c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1670c74fe6afSWarner Losh	that is hard to boot to recover.
1671c74fe6afSWarner Losh
167221c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1673802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1674802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1675802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1676802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1677802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1678802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1679802fc49dSBrian Feldman	using your existing software for a while.
16808633bbeaSBrooks Davis
16818633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
16828633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
16838633bbeaSBrooks Davis	takes care of this.
1684dc0dbf5cSWarner LoshFORMAT:
1685dc0dbf5cSWarner Losh
1686f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
16871fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1688f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1689f8ab1dd6SWarner Loshprevious releases if your system is older than this.
16901fc1a0dcSWarner Losh
1691e72fd46aSWarner LoshCopyright information:
1692e72fd46aSWarner Losh
16939698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1694e72fd46aSWarner Losh
1695772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1696772730c7SWarner Loshmodification, in full or in part, in any form or format of this
16979698f2c0SWarner Loshdocument are permitted without further permission from the author.
1698e72fd46aSWarner Losh
1699e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1700e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1701e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1702e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1703e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1704e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1705e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1706e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1707e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1708e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1709e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1710e72fd46aSWarner Losh
1711e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1712e72fd46aSWarner Loshauthor a beer.
1713e72fd46aSWarner Losh
171422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1715772730c7SWarner Loshthis document.
1716772730c7SWarner Losh
171797d92980SPeter Wemm$FreeBSD$
1718