xref: /freebsd/UPDATING (revision 54bd52716a54ee27f22e0852fd53e069abdfe19a)
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
2054bd5271SAlexander Kabaev20030728:
2154bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
2254bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
2354bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
2454bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
2554bd5271SAlexander Kabaev	compiler. A new unit-at-a-time optimization mode, which is default
2654bd5271SAlexander Kabaev	in this compiler release, is more aggressive in removing unused
2754bd5271SAlexander Kabaev	static symbols. This is the likely cause of 'make buildworld'
2854bd5271SAlexander Kabaev	breakages with non-default CFLAGS where optimization level is set
2954bd5271SAlexander Kabaev	to -O2 or higher.
3054bd5271SAlexander Kabaev
3136ed21e6SRobert Watson20040727:
3236ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
3336ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
3436ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
3536ed21e6SRobert Watson	a result.
3636ed21e6SRobert Watson
376305ac24SSeigo Tanimura20040716:
386305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
396305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
406305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
416305ac24SSeigo Tanimura
42e623dcb7SMarcel Moolenaar20040710:
43e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
44e623dcb7SMarcel Moolenaar
45e623dcb7SMarcel Moolenaar20040710:
46e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
47e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
48e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
49e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
50e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
51e623dcb7SMarcel Moolenaar	of this.
52e623dcb7SMarcel Moolenaar
53e623dcb7SMarcel Moolenaar20040710:
54e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
55e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
56e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
57e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
58e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
59e623dcb7SMarcel Moolenaar	   option for this.
60e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
61e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
62e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
63e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
645bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
65e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
66e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
67e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
68e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
69e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
70e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
71e623dcb7SMarcel Moolenaar
726421d1dbSMaksim Yevmenkin20040708:
736421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
746421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
756421d1dbSMaksim Yevmenkin
7658af3216SWarner Losh20040702:
7758af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
785bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
795bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
805bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
8158af3216SWarner Losh	scheduler as a workaround.
8258af3216SWarner Losh
83c2dba668SNate Lawson20040630:
848ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
858ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
86a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
87a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
88a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
89a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
90a6c26e1cSBruce M Simpson	example of such changes.
918ed370fdSJulian Elischer
9258af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
9358af3216SWarner Losh	over.
9458af3216SWarner Losh
958ed370fdSJulian Elischer20040630:
96c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
975bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
98c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
99c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
100c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
101c2dba668SNate Lawson	loader prompt.
102c2dba668SNate Lawson
1038ee2ac9eSMax Laier20040623:
1045bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
1058ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
1068ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
1078ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
1088ee2ac9eSMax Laier
1093db5687dSBrooks Davis20040622:
1103db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
1113db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
1123db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
1133db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
1143db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
1153db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
1163db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
1173db5687dSBrooks Davis
118e0ae81f3SDag-Erling Smørgrav20040621:
119e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
120e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
121e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
122e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
123e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
124e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
125e0ae81f3SDag-Erling Smørgrav	during the next reboot.
126e0ae81f3SDag-Erling Smørgrav
1274717d22aSJohn Polstra20040614:
1284717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1294717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1304717d22aSJohn Polstra	the ips module and any third-party modules which call
1314717d22aSJohn Polstra	sema_timedwait.
1324717d22aSJohn Polstra
1336cb7a382SMax Laier20040613:
1346cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1356cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
136df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
137df843493SMax Laier	please recompile and reinstall world.
1386cb7a382SMax Laier
1392454685eSJulian Elischer20040607:
1402454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1412454685eSJulian Elischer	requires that you re-run config after updating your tree.
1422454685eSJulian Elischer
14364fef830SSeigo Tanimura20040601:
14464fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
14564fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
14664fef830SSeigo Tanimura	kernel configuration.
14764fef830SSeigo Tanimura
148bb4f06e7SAndre Oppermann20040423:
149bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
150bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
151bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
152bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
153bb4f06e7SAndre Oppermann
15405641e82SColin Percival20040420:
15505641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
15605641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
15705641e82SColin Percival	20040406.
15805641e82SColin Percival
159d0dc9183SWarner Losh20040414:
160d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
161d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
162d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
163d0dc9183SWarner Losh
164d0dc9183SWarner Losh20040412:
165d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
166d0dc9183SWarner Losh	drive is still broken.
167d0dc9183SWarner Losh
168d0dc9183SWarner Losh20040410:
169d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
170d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
171d0dc9183SWarner Losh	the unanticipated problems have been resolved.
172d0dc9183SWarner Losh
1738633bbeaSBrooks Davis20040409:
1748633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1758633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1768633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1778633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
17876c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1798633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1808633bbeaSBrooks Davis
181d40d033aSRobert Watson20040322:
182d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
183d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
184d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
185d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
186d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
187d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
188d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
189d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
190d40d033aSRobert Watson	locking is merged to permit this to take place.
191d40d033aSRobert Watson
192ec9b318eSGarance A Drosehn20040310:
193ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
194ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
195ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
196ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
197ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
198ec9b318eSGarance A Drosehn
199fc28f1ffSMax Laier20040308:
200fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
201fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
2024c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
2034c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
204fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
205fc28f1ffSMax Laier	pf system consists of the following three devices:
206fc28f1ffSMax Laier	device		pf		# required
207fc28f1ffSMax Laier	device		pflog		# optional
208fc28f1ffSMax Laier	device		pfsync		# optional
209fc28f1ffSMax Laier
2103aff5d06SDag-Erling Smørgrav20040303:
2113aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
2123aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
2133aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
2143aff5d06SDag-Erling Smørgrav
2153aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
2163aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
2173aff5d06SDag-Erling Smørgrav
2183aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
2193aff5d06SDag-Erling Smørgrav	to use libpthread instead.
2203aff5d06SDag-Erling Smørgrav
221fd63c5b3SDag-Erling Smørgrav20040226:
2229d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
223fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
224fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
225fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
226fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
227fd63c5b3SDag-Erling Smørgrav
228714ae42aSBruce M Simpson20040225:
229e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
230e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
231e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
232e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
233e07a40f3SBrian Feldman	should remain unaffected.
234e07a40f3SBrian Feldman
235e07a40f3SBrian Feldman20040225:
236714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
237714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
238714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
239714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
240714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
241714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
242714ae42aSBruce M Simpson
243fbd2e692SAndre Oppermann20040224:
244fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
2455bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
246fbd2e692SAndre Oppermann
247158b90daSWarner Losh20040222:
248158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
249158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
250158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
251158b90daSWarner Losh	Drivers outside the tree will need to be updated.
252158b90daSWarner Losh
253b7b1e150SMike Makonnen20040207:
254b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
255b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
256b7b1e150SMike Makonnen
257aca89ee6SDaniel Eischen20040130:
258aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
259aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
260aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
261aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
262aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
263aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
264aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
265aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
266aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
267aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
268aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
269aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
270aca89ee6SDaniel Eischen	do not work with libpthread.
271aca89ee6SDaniel Eischen
27268b7b3a9SAlex Dupre20040125:
27368b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
27468b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
27568b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
27668b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
27768b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
27868b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
27968b7b3a9SAlex Dupre
280ff46e0deSWarner Losh20040125:
281ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
282ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
283ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
284ff46e0deSWarner Losh
285ce41f4bfSRobert Watson20031213:
286ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
287ce41f4bfSRobert Watson	if the login process is unable to successfully set the
288ce41f4bfSRobert Watson	process credentials to include all groups defined for the
289ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
290ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
291ce41f4bfSRobert Watson	defined, or they will be unable to log in.
292ce41f4bfSRobert Watson
293c124fa05SJohn Baldwin20031203:
294c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
295c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
296c124fa05SJohn Baldwin
2978ad1f5e4SHartmut Brandt20031112:
29830093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
29930093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
30097209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
30197209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
30297209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
30397209ca3SRobert Watson	not know about the new system calls that support the new statfs
3043f631d52SMarcel Moolenaar	structure.
3053f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
3063f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
3073f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
3083f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
3093f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
3103f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
3113f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
3123f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
3133f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
3143f631d52SMarcel Moolenaar	these changes are installed.
31530093b05SWarner Losh
31630093b05SWarner Losh	****************************DANGER*******************************
31730093b05SWarner Losh
31830093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
31930093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
32030093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
32130093b05SWarner Losh	kernel.
32264a18d6fSKirk McKusick
32364a18d6fSKirk McKusick20031112:
3248ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3258ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3268ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3278ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3288ad1f5e4SHartmut Brandt	sync before rebooting.
3298ad1f5e4SHartmut Brandt
330c53a5d8fSJohn Baldwin20031111:
331c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
332c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
333c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
334c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
335c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
336c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
337c53a5d8fSJohn Baldwin
3388bf455a5SJohn Baldwin20031103:
3398bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3408bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3412a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3428bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3438bf455a5SJohn Baldwin
3449bf40edeSBrooks Davis20031031:
3459bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
3469bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
3479bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
3489bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
3499bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
3509bf40edeSBrooks Davis	reflect this change.
3519bf40edeSBrooks Davis
35247a42c7aSPoul-Henning Kamp20030928:
35347a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
35447a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
3555bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
35647a42c7aSPoul-Henning Kamp
35707105342SMax Khon20030926:
35807105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
35907105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
36007105342SMax Khon
36117dcd026SSam Leffler20030925:
36217dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
36317dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
36417dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
36517dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
36617dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
36717dcd026SSam Leffler
368fedf1d01SBruce M Simpson20030923:
369fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
370fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
371fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
372fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
373fedf1d01SBruce M Simpson
374db38f9cbSJacques Vidrine20030915:
375db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
376db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
377db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
378db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
379db38f9cbSJacques Vidrine
380c09d2c2bSMike Makonnen20030829:
381c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
382c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
383c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
384c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
385c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
386c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
387c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
388c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
389c09d2c2bSMike Makonnen	may or may not exist on your system.
390c09d2c2bSMike Makonnen
39117c159dcSSøren Schmidt20030824:
39217c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
39317c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
394f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
395f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
39617c159dcSSøren Schmidt
397c1f61aa9SDavid E. O'Brien20030819:
398c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
399c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
400c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
401c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
40269f7bcf3SWarner Losh
40338c962e7SNate Lawson20030728:
40438c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
40538c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
40638c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
40738c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
40838c962e7SNate Lawson	so the quirk can be re-enabled.
40938c962e7SNate Lawson
41074111097SWarner Losh20030724:
41174111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
41274111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
41374111097SWarner Losh
414178cf4e9SWarner Losh20030722:
415178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
416178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
417178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
418178cf4e9SWarner Losh	FPU hardware.
419178cf4e9SWarner Losh
420178cf4e9SWarner Losh20030714:
421178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
422178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
423178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
424178cf4e9SWarner Losh	People should report those issues to current@.
425178cf4e9SWarner Losh
426157c629aSWarner Losh20030711:
427157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4288b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
42905538fa9SWarner Losh	/usr/obj.
430157c629aSWarner Losh
43174111097SWarner Losh20030610:
43274111097SWarner Losh	Remove deprecated locale names and transition period code
43374111097SWarner Losh	for them, finishing switching to the new scheme. Check your
43474111097SWarner Losh	LANG environment variable.
43574111097SWarner Losh
43674111097SWarner Losh20030609:
43774111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
43874111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
43974111097SWarner Losh	important to remember beforehand if your source tree is on
44074111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
44174111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
44274111097SWarner Losh	kernel.
44374111097SWarner Losh
44474111097SWarner Losh20030605:
4456cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
4466cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
4476cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
4486cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
4496cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
4506cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
4516cc6353fSMarcel Moolenaar
4526cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
4536cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
4546cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
4556cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
4566cc6353fSMarcel Moolenaar		:
4576cc6353fSMarcel Moolenaar
4586cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
4596cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
4606cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
4616cc6353fSMarcel Moolenaar
46252b47445SMark Murray20030505:
46352b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
46452b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
46552b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
46652b47445SMark Murray
467a26df538SWarner Losh20030502:
468a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
469a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
470a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
471a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
472a26df538SWarner Losh
4734b065e2cSDoug Barton20030501:
4744b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4754b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4764b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4774b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4784b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4794b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4804b065e2cSDoug Barton
48181cda3d9SWarner Losh20030423:
48281cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
48381cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
48481cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
48581cda3d9SWarner Losh	have until then to upgrade your kernel before updating
48681cda3d9SWarner Losh	userland.  In general, you should have a userland and
48781cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
48881cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
48981cda3d9SWarner Losh	allowances are made.
49081cda3d9SWarner Losh
49147a657d1SRuslan Ermilov20030329:
49247a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
49347a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
49447a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
49547a657d1SRuslan Ermilov
49647a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
49747a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
49847a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
49947a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
50047a657d1SRuslan Ermilov
50147a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
50247a657d1SRuslan Ermilov	    make cleandir && make obj && \
50347a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
50447a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
50547a657d1SRuslan Ermilov
5065d2af00cSGregory Neil Shapiro20030208:
5075d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
5085d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
5095d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
5105d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
5115d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
5125d2af00cSGregory Neil Shapiro
5135d2af00cSGregory Neil Shapiro20030128:
5149db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
515ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
5169db58771SPoul-Henning Kamp	be removed when convenient.
5179db58771SPoul-Henning Kamp
5188d9b3f57SJake Burkholder20030126:
5198d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
5208d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
5218d9b3f57SJake Burkholder
5221c5efda5SJeff Roberson20030125:
5231c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5241c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
525ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5261c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5271c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5281c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5291c5efda5SJeff Roberson
5309d1d64f5SWarner Losh20030115:
5319d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5329d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5339d1d64f5SWarner Losh	properly.
5349d1d64f5SWarner Losh
535c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
536c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
537c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
538c9fdb80aSWarner Losh	with NetBSD.
539c9fdb80aSWarner Losh
540161dc364SAlexander Kabaev20021222:
541161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
542161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
543161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
544161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
545161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
546161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
54784cc83efSAlexander Kabaev	rebuilt.
548161dc364SAlexander Kabaev
549fb4c8061SMartin Blapp20021216:
550fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
55189056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
552fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
5539d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
554fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
555fb4c8061SMartin Blapp
55617d47eb3SGiorgos Keramidas20021202:
55717d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
55817d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
55917d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
56017d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
56117d47eb3SGiorgos Keramidas
562a4459294SBill Fenner20021029:
563a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
564a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
565a4459294SBill Fenner	consumers in sync.
566a4459294SBill Fenner
567fc8c157fSWarner Losh20021024:
568c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
569c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
570c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
571c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
572c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
573c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
574c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
575c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
57669f7bcf3SWarner Losh
577fd9e8bdaSAndrew Gallatin20021023:
578fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
579fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
580fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
581fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
582fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
583fd9e8bdaSAndrew Gallatin
584fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
585fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
586fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
587fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
588fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
589fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
590fd9e8bdaSAndrew Gallatin
591f8a4c901SWarner Losh20020831:
592f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
593f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
594f8a4c901SWarner Losh	programs and libraries need to be recompiled.
595f8a4c901SWarner Losh
596f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
597f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
598f8a4c901SWarner Losh
599c2248fa2SJens Schweikhardt20020827:
600c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
601c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
602c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
603c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
604c2248fa2SJens Schweikhardt
6050d533e43SRuslan Ermilov20020815:
6060d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
6070d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
6080d533e43SRuslan Ermilov	again.
6090d533e43SRuslan Ermilov
61033c1de7dSRuslan Ermilov20020729:
61133c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
61233c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
61333c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
61433c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
61533c1de7dSRuslan Ermilov
6162b877facSJulian Elischer20020702:
6172b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
6182b877facSJulian Elischer	There are still some minor problems with some signals but the
6192b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
6202b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
6212b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6222b877facSJulian Elischer
62306596d37SWarner Losh20020701:
62406596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
62506596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
62606596d37SWarner Losh	GNOME.
62706596d37SWarner Losh
62895ba4330SJacques Vidrine20020511:
62995ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
63095ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
63195ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
63295ba4330SJacques Vidrine	with the set-user-ID bit set.
63395ba4330SJacques Vidrine
634a81da3c9SDavid E. O'Brien20020510:
635f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
636f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6374b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
638f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
639f50caf6fSDavid E. O'Brien
640f50caf6fSDavid E. O'Brien20020510:
641a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
642a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
643a81da3c9SDavid E. O'Brien	and then do a cvs update.
644a81da3c9SDavid E. O'Brien
645528a0ef5SJacques Vidrine20020421:
646528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
647528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
648528a0ef5SJacques Vidrine
64985aa5a2eSGregory Neil Shapiro20020404:
65085aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
65185aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
65285aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
65385aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
65485aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
65585aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
65685aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
65785aa5a2eSGregory Neil Shapiro
6588f1e4358SRuslan Ermilov20020403:
6598f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
6608f1e4358SRuslan Ermilov
6612292c02eSWarner Losh20020315:
6622292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
6632292c02eSWarner Losh
66469f7bcf3SWarner Losh20020225:
66569f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
66669f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
66769f7bcf3SWarner Losh
6688f35c493SWarner Losh20020217:
6698f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6708f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6718f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6728f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6738f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6748f35c493SWarner Losh
675835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
676835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
677835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
678835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
679835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
680835284beSWarner Losh	and group must be merged from src/etc/group and
681835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
682835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
683835284beSWarner Losh	mergemaster before this will work if you are updating from a
684835284beSWarner Losh	very old version of current.  The updating recipe has changed
685835284beSWarner Losh	as of this date.
686835284beSWarner Losh
687fa9401c1SWarner Losh20020112:
688fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
689fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
690fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
691fa9401c1SWarner Losh	you have local modifications, you can use
692fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
693fa9401c1SWarner Losh	/etc/pam.d.
694fa9401c1SWarner Losh
695fa9401c1SWarner Losh	Please see the following url for more details:
696fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
69747d0d01fSWarner Losh20011229:
69847d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
69947d0d01fSWarner Losh	networkfs_types, please note that it has changed
70047d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
70147d0d01fSWarner Losh
702514318a8SWarner Losh20011220:
703514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
704514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
705514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
706514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
707514318a8SWarner Losh	version have now been merged back into the base system's
708514318a8SWarner Losh	version now.  The only user-visible change resulting from this
709514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
710514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
711514318a8SWarner Losh	as well.  (There has never been rc file support for
712514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
713514318a8SWarner Losh	reverted by the time the changes are MFCed.)
714514318a8SWarner Losh
715514318a8SWarner Losh20011215:
716514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
717514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
718514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
719514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
720514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
721514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
722514318a8SWarner Losh	will need to be customized then for `odd' densities using
723514318a8SWarner Losh	fdcontrol(8).
724514318a8SWarner Losh
7252d22e2bfSWarner Losh20011209:
7262d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7272d22e2bfSWarner Losh	and truss(1) now works again.
7282d22e2bfSWarner Losh
7299e0428e2SWarner Losh20011207:
7309e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7319e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7329e0428e2SWarner Losh	see
7339e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7349e0428e2SWarner Losh	for details.
7359e0428e2SWarner Losh
7369bab8c59SWarner Losh20011204:
7379bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7389bab8c59SWarner Losh	kernel and burncd to be in sync.
7399bab8c59SWarner Losh
740e57d8b01SWarner Losh20011203:
741e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
742e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
743e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
744e57d8b01SWarner Losh	not there already.
745e57d8b01SWarner Losh
746e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
747e57d8b01SWarner Losh	until the issue has been resolved.
748e57d8b01SWarner Losh
749b001d36fSJacques Vidrine20011202:
750b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
751b001d36fSJacques Vidrine	patched.
752b001d36fSJacques Vidrine
7534b676ec1SWarner Losh20011126:
7544b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
7555ebbf43eSWarner Losh	after this date.  You need to do this only once.
7564b676ec1SWarner Losh
757d961e462SWarner Losh20011103:
758d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
759d961e462SWarner Losh	edges may be left, but for the most part things should be
7604b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
761d961e462SWarner Losh
762d961e462SWarner Losh20011030:
763d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
764d961e462SWarner Losh	choppy waves in the upgrade process.
765d961e462SWarner Losh
7661fe003b6SWarner Losh20011030:
767a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7681fe003b6SWarner Losh
7691fe003b6SWarner Losh20011027:
7701fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7711fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7721fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7731fe003b6SWarner Losh	try to use from this date forward.
7741fe003b6SWarner Losh
7751fe003b6SWarner Losh20011025:
7761fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7771fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7781fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7791fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7801fe003b6SWarner Losh	TARGET_ARCH=i386.
7811fe003b6SWarner Losh
782d05f9643SWarner Losh20011001:
783d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
784d05f9643SWarner Losh	You must recompile both the kernel and userland applications
785d05f9643SWarner Losh	at the same time.
786d05f9643SWarner Losh
78758970f85SWarner Losh20010929:
78858970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
78958970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
79058970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
79158970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
7929d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
79358970f85SWarner Losh
79458970f85SWarner Losh20010927:
79558970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
79658970f85SWarner Losh	To disable ACPI you can add
79766ff0e67SMax Khon		hint.acpi.0.disabled="1"
79858970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
79958970f85SWarner Losh	loader "ok" prompt).
80058970f85SWarner Losh
80158970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
80258970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
80358970f85SWarner Losh	file and not list acpi in that list.
804378f4486SAlfred Perlstein
8055119d237SWarner Losh20010924:
8065119d237SWarner Losh	The buildworld has been fixed.  You may need to install
8075119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8088b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
8098b039fffSWarner Losh	get them installed on every installworld, or execute the
8108b039fffSWarner Losh	following to get them installed only once:
8118b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
81258970f85SWarner Losh		make all install
8138b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
8145119d237SWarner Losh
8153c293725SWarner Losh20010919:
8163c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
8173c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
8183c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
819772730c7SWarner Losh	workaround is to add
8203c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
8213c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8223c293725SWarner Losh	can be removed afterwards.
8233c293725SWarner Losh
8243c293725SWarner Losh	A proper fix to the buildworld target is needed.
8253c293725SWarner Losh
8263c293725SWarner Losh20010918:
8273c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8283c293725SWarner Losh	NFS may be unstable after this date.
8293c293725SWarner Losh
8303c293725SWarner Losh20010912:
8313c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8323c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8333c293725SWarner Losh	initial commit, most of the major ones have been found and
8343c293725SWarner Losh	corrected.
8353c293725SWarner Losh
8363c293725SWarner Losh20010901:
8373c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8383c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8393c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8403c293725SWarner Losh	have been rectified around this date.
8413c293725SWarner Losh
84298b17b95SWarner Losh20010823:
84398b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
84498b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
84598b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
84698b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
84798b17b95SWarner Losh 	sure that user or group bind has read (and not write)
84898b17b95SWarner Losh 	permission for your name server configuration and that it
84998b17b95SWarner Losh 	has read and write permission for your slave zone files and
85098b17b95SWarner Losh 	directory.
85198b17b95SWarner Losh
85298b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
85398b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
85498b17b95SWarner Losh
85598b17b95SWarner Losh 		named_flags=
85698b17b95SWarner Losh
8577b9786edSMark Murray20010709:
8587b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
8597b9786edSMark Murray	the ability of the shared library major number to handle.
8607b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
8617b9786edSMark Murray	solution is to rebuild those ports.
8627b9786edSMark Murray
8631d28950eSWarner Losh20010628:
8641d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
8651d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8661d28950eSWarner Losh
867e72fd46aSWarner Losh20010625:
86898b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
86998b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
87098b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
87198b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
87298b17b95SWarner Losh	IRQ configuration needs more safety belts.
87316de1a07SWarner Losh
8740d415dffSWarner Losh20010617:
875e72fd46aSWarner Losh	Softupdates problems have been corrected.
8760d415dffSWarner Losh
8770d415dffSWarner Losh20010614:
8780d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8790d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8800d415dffSWarner Losh	kernel building methods.
8810d415dffSWarner Losh
8828b9959adSWarner Losh20010613:
8838b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
8848b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
885e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
886e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
8878b9959adSWarner Losh
888e72fd46aSWarner Losh20010613:
8898b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
890e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
891e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
8928b9959adSWarner Losh
8930d415dffSWarner Losh20010612:
8940d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
8950d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
8960d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
8970d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
8980d415dffSWarner Losh	until this bug is fixed.
8990d415dffSWarner Losh
900e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
901e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
902ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
903e72fd46aSWarner Losh
9040d415dffSWarner Losh20010610:
9050d415dffSWarner Losh	Locale names have changed to match other systems better.
9060d415dffSWarner Losh
9076ccdb5e4SWarner Losh20010604:
9086ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
9096ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
9106ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
9113590182eSWarner Losh	Interrupt storms look a lot like a hang.
9123590182eSWarner Losh
9133590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
9143590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
9153590182eSWarner Losh	it is).
9163590182eSWarner Losh
9173590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
9183590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
9193590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
9203590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
9216ccdb5e4SWarner Losh
9220bc62786SWarner Losh20010530:
9230bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9240bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9250bc62786SWarner Losh	a limited time.  If you see
9260bc62786SWarner Losh
9270bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9280bc62786SWarner Losh
9290bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9300bc62786SWarner Losh	COPY=-C.
9310bc62786SWarner Losh
93268a38c6cSWarner Losh20010525:
933b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
934c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
935c4f4a728SWarner Losh	definitely is in bad shape.
93668a38c6cSWarner Losh
937ed0f29caSWarner Losh20010521:
938ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
939ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
940ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
941ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
942ed0f29caSWarner Losh	is
943ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
944ed0f29caSWarner Losh
94580c16af9SWarner Losh20010520:
94668a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
94780c16af9SWarner Losh
94880c16af9SWarner Losh20010519:
94980c16af9SWarner Losh	pccard has had much reorganizational work done to it over
95080c16af9SWarner Losh	the past few days.  Everything should still work, but if
95180c16af9SWarner Losh	not, please contact imp@freebsd.org.
95280c16af9SWarner Losh
953a45f2d05SWarner Losh20010517:
954a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
955a45f2d05SWarner Losh	userland at the same time.
956a45f2d05SWarner Losh
957a45f2d05SWarner Losh20010517:
958a45f2d05SWarner Losh	New ncurses imported.
959a45f2d05SWarner Losh
9602988afcaSWarner Losh20010512:
9612988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
9622988afcaSWarner Losh	will be the only way to go starting July 1.
9632988afcaSWarner Losh
9641a33dba7SWarner Losh20010504:
9651a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9661a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9671a33dba7SWarner Losh
96809946a51SWarner Losh20010502:
96909946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
97009946a51SWarner Losh
97109946a51SWarner Losh20010501:
97209946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
97309946a51SWarner Losh
97409946a51SWarner Losh20010430:
975a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
97609946a51SWarner Losh	go back in the water.
97709946a51SWarner Losh
97809946a51SWarner Losh20010429:
97909946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
98009946a51SWarner Losh	this date, but before the correction date.
98109946a51SWarner Losh
98291dd3b53SWarner Losh20010423:
98391dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
98491dd3b53SWarner Losh
98591dd3b53SWarner Losh20010411:
98691dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
98791dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
98891dd3b53SWarner Losh	Update only if you understand that you must not use the old
98991dd3b53SWarner Losh	fsck with the new kernel ever.
99091dd3b53SWarner Losh
991933b3269SWarner Losh20010330:
992933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
993c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
994933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
995933b3269SWarner Losh
996933b3269SWarner Losh20010319:
997933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
998933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
999933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1000f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
100109946a51SWarner Losh
100209946a51SWarner Losh20010315:
100309946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1004ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
100509946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1006933b3269SWarner Losh
1007933b3269SWarner Losh20010312:
1008933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1009933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1010933b3269SWarner Losh
1011933b3269SWarner Losh20010312:
1012933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1013933b3269SWarner Losh	instead of ad-hoc.
1014933b3269SWarner Losh
1015933b3269SWarner Losh20010310:
1016f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1017933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1018933b3269SWarner Losh	ssh might not work if you don't.
1019933b3269SWarner Losh
102062353691SWarner Losh20010303:
102162353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
102262353691SWarner Losh	which means that you must include the miibus in your kernel if
102362353691SWarner Losh	you use the ed driver.
102462353691SWarner Losh
1025d325cf65SWarner Losh20010220:
1026d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1027d325cf65SWarner Losh	safe to go back into the water.
1028d325cf65SWarner Losh
1029024daae6SWarner Losh20010211:
1030024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1031024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1032024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1033024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1034024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1035024daae6SWarner Losh
1036024daae6SWarner Losh	To get to the new system, you'll need to use the following
1037024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1038024daae6SWarner Losh	don't have to move this to the updating section.
1039024daae6SWarner Losh
1040024daae6SWarner Losh	To get around the installworld problem, do:
1041024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1042024daae6SWarner Losh		# make install
1043024daae6SWarner Losh		# cd /usr/src
1044024daae6SWarner Losh		# make installworld
1045024daae6SWarner Losh	If that doesn't work, then try:
1046024daae6SWarner Losh		# make -k installworld
1047024daae6SWarner Losh		# make installworld
1048024daae6SWarner Losh
1049024daae6SWarner Losh20010207:
1050024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1051024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1052024daae6SWarner Losh
1053024daae6SWarner Losh20010205:
10547595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1055024daae6SWarner Losh	Remove them from your config.
1056024daae6SWarner Losh
10571e159248SWarner Losh20010122:
10581e159248SWarner Losh	****************************** WARNING ******************************
10591e159248SWarner Losh			buildkernel has been changed slightly
10601e159248SWarner Losh	****************************** WARNING ******************************
10611e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
10621e159248SWarner Losh	should update your scripts and make.conf accordingly.
10631e159248SWarner Losh
10641e159248SWarner Losh20010119:
10651e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10661e159248SWarner Losh	This requires a new config to build correctly.
10671e159248SWarner Losh
1068aac7dfeaSWarner Losh20010116:
1069ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1070aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1071aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1072aac7dfeaSWarner Losh
1073aac7dfeaSWarner Losh20010110:
1074aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1075aac7dfeaSWarner Losh
1076aac7dfeaSWarner Losh20010102:
1077aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1078aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1079aac7dfeaSWarner Losh
108063c90c9eSWarner Losh20010101:
108163c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
108263c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
10835fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
108463c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
108563c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
108663c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
108763c90c9eSWarner Losh	might have been ignored by the -k option.
108863c90c9eSWarner Losh
10895fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
10905fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
10915fd2a895SWarner Losh	of this working.
10925fd2a895SWarner Losh
1093aac7dfeaSWarner Losh20001228:
1094aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1095ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1096aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1097aac7dfeaSWarner Losh
1098de2bcc63SWarner Losh20001218:
1099de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1100de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1101de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1102de2bcc63SWarner Losh	cards will not be recognized without it.
1103de2bcc63SWarner Losh
1104960773f7SWarner Losh20001205:
1105960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1106960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1107960773f7SWarner Losh	adding the following in pam.conf:
1108960773f7SWarner Losh
1109960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1110960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1111960773f7SWarner Losh	sshd    session required        pam_permit.so
1112960773f7SWarner Losh
11130acc635eSWarner Losh20001031:
11140acc635eSWarner Losh	cvs updated to 1.11.
11150acc635eSWarner Losh
11160acc635eSWarner Losh20001020:
11170acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
11180acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
11190acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
11200acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
11210acc635eSWarner Losh	workaround.
11220acc635eSWarner Losh
11230acc635eSWarner Losh20001010:
11240acc635eSWarner Losh	****************************** WARNING ******************************
11250acc635eSWarner Losh				Sendmail has been updated.
11260acc635eSWarner Losh	****************************** WARNING ******************************
11270acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11280acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11290acc635eSWarner Losh	  is set.
11300acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11310acc635eSWarner Losh	  commands.
11320acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11330acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11340acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11350acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11360acc635eSWarner Losh
11370acc635eSWarner Losh	More details can be found at
11380acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11390acc635eSWarner Losh
11406e98a146SWarner Losh20001009:
11416e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11426e98a146SWarner Losh	your entire ports tree, or you will have problems.
11436e98a146SWarner Losh
11446e98a146SWarner Losh20001006:
1145685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
11466e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
11476e98a146SWarner Losh	/usr/bin/miniperl.
11486e98a146SWarner Losh
1149073113a4SWarner Losh20001005:
1150073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1151685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1152073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1153073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1154073113a4SWarner Losh	tree for anything to work.
1155073113a4SWarner Losh
11560acc635eSWarner Losh20000928:
11570acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
11580acc635eSWarner Losh
1159be3885b3SWarner Losh20000916:
1160be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1161be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1162be3885b3SWarner Losh	same time as your kernel.
1163be3885b3SWarner Losh
116476ec9675SWarner Losh20000914:
116576ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
116676ec9675SWarner Losh	include the device will cause suspended laptops losing time
116776ec9675SWarner Losh	when they resume.  Include
116876ec9675SWarner Losh		device		pmtimer
116976ec9675SWarner Losh	in your config file and
117001b9a434SWarner Losh		hint.pmtimer.0.at="isa"
117176ec9675SWarner Losh	to your /boot/device.hints file.
117276ec9675SWarner Losh
1173f4865386SMark Murray20000911:
1174f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1175f4865386SMark Murray	rather than an option. The supplied kernel config files have
1176f4865386SMark Murray	been updated. You will need to do something similar in your
1177f4865386SMark Murray	own kernel config file.
1178f4865386SMark Murray	Remove:
1179f4865386SMark Murray		options		RANDOMDEV
1180f4865386SMark Murray	Add:
1181f4865386SMark Murray		device		random
1182f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1183f4865386SMark Murray	nothing.
1184f4865386SMark Murray
1185d594498fSWarner Losh20000909:
1186d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1187d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1188d594498fSWarner Losh	reflect this if you load this module at boot time.
1189d594498fSWarner Losh	The line should read:
1190d594498fSWarner Losh		random_load="YES"
1191d594498fSWarner Losh
11920deb7ddcSWarner Losh20000907:
11930deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
119416eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
119516eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
119616eb772dSWarner Losh	sure you don't have model loading problems which might at
119716eb772dSWarner Losh	first blush appear related to SMP.
119852bf24e7SWarner Losh
11995a01880bSWarner Losh20000906:
12005a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
12015a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
12025a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
12035a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
12045a01880bSWarner Losh	don't have one, and you have host.conf.
12055a01880bSWarner Losh
12062b41163cSWarner Losh20000905:
120738d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
120838d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
120938d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
121038d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
121138d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
121238d6ecd2SWarner Losh
121338d6ecd2SWarner Losh20000905:
12148aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
12158aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
12168aab4bc7SWarner Losh	is /boot/kernel.
12178aab4bc7SWarner Losh
12188aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
121938d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
122038d6ecd2SWarner Losh	installkernel/installworld dance.
12212b41163cSWarner Losh
1222d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1223d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1224d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1225d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1226d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1227d594498fSWarner Losh
1228d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1229d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1230d594498fSWarner Losh		chflags noschg /kernel.old
1231d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1232d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1233d594498fSWarner Losh	fi
1234d594498fSWarner Losh
1235c22a309cSWarner Losh20000904:
1236c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1237c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1238c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1239c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1240c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1241c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1242c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1243c22a309cSWarner Losh	is not likely to be generated.
1244c22a309cSWarner Losh
1245fdb9f54dSWarner Losh20000825:
1246fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
12479c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
12489c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
12499c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
12509c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
12519c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
12529c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
12539c1a7444SWarner Losh	kernel.
12549c1a7444SWarner Losh
12559c1a7444SWarner Losh20000821:
12569c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
12579c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
12589c1a7444SWarner Losh	/boot/loader.conf.
1259fdb9f54dSWarner Losh
12608f250aa7SWarner Losh20000812:
12615da0d091SWarner Losh	suidperl is now always built and installed on the system, but
12625da0d091SWarner Losh	with permissions of 511.  If you have applications that use
12635da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
12645da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
12655da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12665da0d091SWarner Losh	will fix this until the next build.
12675da0d091SWarner Losh
12685da0d091SWarner Losh20000812:
12698f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12708f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12718f250aa7SWarner Losh	include:
12728f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12738f250aa7SWarner Losh	- newaliases limited to root and trusted users
12748f250aa7SWarner Losh	- MSA port (587) turned on by default
12758f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12768f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12778f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12788f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12798f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12808f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12818f250aa7SWarner Losh
128271c38472SWarner Losh20000810:
128371c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
128471c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
128571c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
128671c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
128771c38472SWarner Losh	specific use for it.
128871c38472SWarner Losh
128971c38472SWarner Losh20000729:
129071c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
129171c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
129271c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
129371c38472SWarner Losh	afterwards (unless the variables already are set, of course):
129471c38472SWarner Losh		# Enable network daemons for user convenience.
129571c38472SWarner Losh		inetd_enable="YES"
129671c38472SWarner Losh		portmap_enable="YES"
129771c38472SWarner Losh		sendmail_enable="YES"
129871c38472SWarner Losh
129971c38472SWarner Losh20000728:
130071c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
130171c38472SWarner Losh	will need to change that to nullfs_load="YES".
130271c38472SWarner Losh
13031dece4a9SWarner Losh20000728:
13041dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
13051dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
13061dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
13071dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
13081dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
13091dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
13101dece4a9SWarner Losh	to /MYKERNEL.
13111dece4a9SWarner Losh
1312409e887cSWarner Losh20000711:
1313409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1314409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1315409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1316409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1317409e887cSWarner Losh	for details on potential problems that you might have and how
1318409e887cSWarner Losh	to get around them.
1319409e887cSWarner Losh
1320409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1321409e887cSWarner Losh	clauses above, you needn't worry.
1322409e887cSWarner Losh
1323409e887cSWarner Losh20000711:
1324409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1325409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1326409e887cSWarner Losh	in the number of changed programs the first time when you run
1327409e887cSWarner Losh	mergemaster to get a new /etc/security.
1328409e887cSWarner Losh
1329673d13f2SWarner Losh20000710:
1330673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1331673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1332673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1333673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1334673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1335673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1336673d13f2SWarner Losh	errors. (see below, 20000624).
1337673d13f2SWarner Losh
1338bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13391dece4a9SWarner Losh
1340673d13f2SWarner Losh20000709:
1341c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1342c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1343c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1344673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1345673d13f2SWarner Losh
1346e98e26cdSWarner Losh20000706:
1347e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1348e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1349e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1350f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1351e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
13522c021c6cSMark Ovens	interim if needed.
1353e98e26cdSWarner Losh
1354e98e26cdSWarner Losh20000705:
1355e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1356e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1357e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1358e98e26cdSWarner Losh	details.
1359e98e26cdSWarner Losh
1360c373950eSWarner Losh20000704:
13612f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
13622f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
13632f961bc8SWarner Losh
13642f961bc8SWarner Losh20000704:
1365c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1366c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1367c373950eSWarner Losh	rc.d scripts that haven't been updated.
1368c373950eSWarner Losh
136927dc3a2bSWarner Losh20000630:
137027dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
137127dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
137227dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
137327dc3a2bSWarner Losh
1374b8c215acSWarner Losh20000625:
1375b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
137627dc3a2bSWarner Losh	system installed in order to build the system and kernel.
137727dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
137827dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
137927dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
138027dc3a2bSWarner Losh	were required.  You should check with the latest collections
138127dc3a2bSWarner Losh	to make sure that these haven't changed.
1382b8c215acSWarner Losh
13837b990719SWarner Losh20000624:
13847b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
13857b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
13867b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
13871a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
13887b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
13897b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
13907b990719SWarner Losh	date to the completion of the work.
13917b990719SWarner Losh
139227dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
139327dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
139427dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
139527dc3a2bSWarner Losh	recreate the random and urandom devices.
139627dc3a2bSWarner Losh
139781e54c50SWarner Losh20000622:
139881e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
139981e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
140081e54c50SWarner Losh	that used to be required when updating.
140181e54c50SWarner Losh
140239943833SWarner Losh20000621:
14032c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
14042a2f33fbSDaniel Baker	the config file update procedure.
14052a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1406c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
140759df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
140859df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
140939943833SWarner Losh
1410290f9ad8SWarner Losh20000620:
1411290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1412290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1413290f9ad8SWarner Losh	that workaround will no longer be required.
1414290f9ad8SWarner Losh
141590fb6346SWarner Losh20000615:
141690fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
141790fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
141890fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
141990fb6346SWarner Losh	devices.
142090fb6346SWarner Losh
1421f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1422f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1423f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1424f75f65bbSWarner Losh	may work).
1425f75f65bbSWarner Losh
1426ba26da8eSWarner Losh20000612:
1427ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1428290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1429c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1430290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1431f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1432f54a3542SWarner Losh	NEWCARD for examples of the new format.
1433290f9ad8SWarner Losh
14349698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14359698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14369698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14379698f2c0SWarner Losh	in it.
1438bbcc5149SWarner Losh
1439d65850ebSWarner Losh20000522:
1440ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1441d65850ebSWarner Losh	building a kernel after this point is advised that they need
1442d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1443d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1444d65850ebSWarner Losh
1445d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1446d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1447d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1448d9583a00SWarner Losh	is resolved.
1449d9583a00SWarner Losh
14508039cedeSWarner Losh20000513:
14518039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
14528039cedeSWarner Losh
1453d65850ebSWarner Losh20000510:
14548039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
14558039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
14568039cedeSWarner Losh	is requires for the boot blocks to build properly.
14578039cedeSWarner Losh
14588039cedeSWarner Losh20000503:
14598039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
14608039cedeSWarner Losh	is now available.
14618039cedeSWarner Losh
1462d65850ebSWarner Losh20000502:
1463d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1464d65850ebSWarner Losh	connected to the kernel building instead.
1465d65850ebSWarner Losh
1466be149406SNik Clayton20000427:
14678039cedeSWarner Losh	You may need to build gperf
14688039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14698039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14708039cedeSWarner Losh	an option only in -current.
14718039cedeSWarner Losh
14722b8dd5f4SWarner Losh20000417:
14732b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1474f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14752b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14762b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14772c021c6cSMark Ovens	before you reboot, you'll need to issue:
14782b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14792b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14802b8dd5f4SWarner Losh
14818d9f1945SWarner Losh20000320:
14822b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
14832b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
14842b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1485ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
14862b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
14878d9f1945SWarner Losh
1488f8ab1dd6SWarner Losh20000319:
1489f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1490f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1491f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1492f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1493f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1494f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1495f8ab1dd6SWarner Losh
149619cada77SWarner Losh20000318:
1497f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
149819cada77SWarner Losh	Large kernel changes are being committed and are in the
149919cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
150019cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
150119cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
150219cada77SWarner Losh	that you are loading are up to date.
1503ba228352SWarner Losh
150419cada77SWarner Losh20000315:
15056d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
15066d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
15076d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
15086d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
15096d23c382SWarner Losh	boot.
15106d23c382SWarner Losh
15116d23c382SWarner Losh20000315:
151219cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
151319cada77SWarner Losh	to upgrade to 4.0 from 3.x.
151457199806SWarner Losh
1515dc0dbf5cSWarner LoshCOMMON ITEMS:
1516dc0dbf5cSWarner Losh
1517a24eff53SWarner Losh	General Notes
1518a24eff53SWarner Losh	-------------
1519a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1520a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1521a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1522a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1523a24eff53SWarner Losh	or several minor releases, or when several months have passed
1524a24eff53SWarner Losh	on the -current branch).
1525a24eff53SWarner Losh
15265780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15275780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15285780f3baSWarner Losh	environment when searching for values for global variables.
15295780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15305780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15315780f3baSWarner Losh	page for more details.
15325780f3baSWarner Losh
1533dc0dbf5cSWarner Losh	To build a kernel
1534dc0dbf5cSWarner Losh	-----------------
1535ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1536f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1537ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1538282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1539282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1540dc0dbf5cSWarner Losh
1541ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1542ba01eb20SWarner Losh	--------------------------------------------------------------
15430fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15440fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
15450fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
15460fbd2da9SKen Smith
15470fbd2da9SKen Smith	cd src/sys/${arch}/conf
154847d0d01fSWarner Losh	config KERNEL_NAME_HERE
15490fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1550ba01eb20SWarner Losh	make depend
1551ba01eb20SWarner Losh	make
1552ba01eb20SWarner Losh	make install
1553ba01eb20SWarner Losh
1554ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1555ba01eb20SWarner Losh
1556ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1557ba01eb20SWarner Losh	-----------------------------------------------------------
155863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
155963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
156063cb445eSWarner Losh
1561f643de42SWarner Losh	<make sure you have good level 0 dumps>
156263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
156363cb445eSWarner Losh	make buildworld
156463cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
156563cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
156663cb445eSWarner Losh							[1]
156763cb445eSWarner Losh	<reboot in single user>				[3]
15688633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
156963cb445eSWarner Losh	mergemaster -p					[5]
157063cb445eSWarner Losh	make installworld
157163cb445eSWarner Losh	mergemaster					[4]
157263cb445eSWarner Losh	<reboot>
157363cb445eSWarner Losh
1574759f0aefSWarner Losh
1575f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1576f27b1fceSJoseph Koshy	--------------------------------------------------
1577f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1578f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1579f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1580f27b1fceSJoseph Koshy	# size.
1581f27b1fceSJoseph Koshy
1582f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1583f27b1fceSJoseph Koshy	<boot into -stable>
1584f27b1fceSJoseph Koshy	make buildworld
1585f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1586f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1587f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1588f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1589f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1590f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1591f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1592f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1593f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1594f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1595f27b1fceSJoseph Koshy	<reboot into current>
1596f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1597f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1598f27b1fceSJoseph Koshy 	<reboot>
1599f27b1fceSJoseph Koshy
1600f27b1fceSJoseph Koshy
1601f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1602f27b1fceSJoseph Koshy	----------------------------------------------
16035c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
16045c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
16055c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
16065c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1607ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1608f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1609f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1610f643de42SWarner Losh	# space on /.
1611f643de42SWarner Losh
1612f643de42SWarner Losh	<make sure you have good level 0 dumps>
1613fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
161421c075eaSWarner Losh	make buildworld					[9]
1615c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1616802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1617be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1618802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1619fc8c157fSWarner Losh							[1]
1620fc8c157fSWarner Losh	<reboot in single user>				[3]
1621802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1622835284beSWarner Losh	mergemaster -p					[5]
1623f8a4c901SWarner Losh	rm -rf /usr/include/g++
1624ba26da8eSWarner Losh	make installworld
1625802fc49dSBrian Feldman	mergemaster -i					[4]
1626ba26da8eSWarner Losh	<reboot>
1627ba26da8eSWarner Losh
1628fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1629fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1630fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1631fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1632fdb9f54dSWarner Losh	the UPDATING entries.
1633ba26da8eSWarner Losh
16341dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16351dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16361dece4a9SWarner Losh	your sources that you have read and understood all the recent
16371dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16381dece4a9SWarner Losh	much fewer pitfalls.
16391dece4a9SWarner Losh
1640134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1641134d2e86SWarner Losh	should disable them at this point so they don't crash your
1642134d2e86SWarner Losh	system on reboot.
1643134d2e86SWarner Losh
16449c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
16459c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
16469c1a7444SWarner Losh	configuration.
16479c1a7444SWarner Losh
1648ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1649ee6e1fc3SWarner Losh		fsck -p
1650ee6e1fc3SWarner Losh		mount -u /
1651ee6e1fc3SWarner Losh		mount -a
1652ee6e1fc3SWarner Losh		cd /usr/src
165347d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1654f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1655f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1656b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1657b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1658b705ae10SWarner Losh	be ignored while you proceed to the next step.
1659ee6e1fc3SWarner Losh
1660a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1661a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1662a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1663a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1664a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1665a6cd4f9dSWarner Losh	for potential gotchas.
1666a6cd4f9dSWarner Losh
1667835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1668835284beSWarner Losh	you may need to do this if you get unknown user in the following
1669835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1670835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1671835284beSWarner Losh	install) after the buildworld before this step if you last updated
1672835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1673835284beSWarner Losh
1674bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1675bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1676bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1677bd79cf40SWarner Losh		ok unload
1678bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1679bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1680bd79cf40SWarner Losh	described here.
1681fc8c157fSWarner Losh
1682fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1683fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1684fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1685fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1686fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1687fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1688fc8c157fSWarner Losh
1689c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1690c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1691c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1692c74fe6afSWarner Losh	that is hard to boot to recover.
1693c74fe6afSWarner Losh
169421c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1695802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1696802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1697802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1698802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1699802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1700802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1701802fc49dSBrian Feldman	using your existing software for a while.
17028633bbeaSBrooks Davis
17038633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
17048633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
17058633bbeaSBrooks Davis	takes care of this.
1706dc0dbf5cSWarner LoshFORMAT:
1707dc0dbf5cSWarner Losh
1708f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
17091fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1710f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1711f8ab1dd6SWarner Loshprevious releases if your system is older than this.
17121fc1a0dcSWarner Losh
1713e72fd46aSWarner LoshCopyright information:
1714e72fd46aSWarner Losh
17159698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1716e72fd46aSWarner Losh
1717772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1718772730c7SWarner Loshmodification, in full or in part, in any form or format of this
17199698f2c0SWarner Loshdocument are permitted without further permission from the author.
1720e72fd46aSWarner Losh
1721e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1722e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1723e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1724e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1725e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1726e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1727e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1728e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1729e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1730e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1731e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1732e72fd46aSWarner Losh
1733e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1734e72fd46aSWarner Loshauthor a beer.
1735e72fd46aSWarner Losh
173622306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1737772730c7SWarner Loshthis document.
1738772730c7SWarner Losh
173997d92980SPeter Wemm$FreeBSD$
1740