UPDATING revision 114492
1Updating Information for FreeBSD current users
2
3This file is maintained and copyrighted by M. Warner Losh
4<imp@village.org>.  See end of file for further details.  For commonly
5done items, please see the COMMON ITEMS: section later in the file.
6
7NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
8	FreeBSD 5.0-CURRENT has many debugging features turned on, in
9	both the kernel and userland.  These features attempt to detect
10	incorrect use of system primitives, and encourage loud failure
11	through extra sanity checking and fail stop semantics.  They
12	also substantially impact system performance.  If you want to
13	do performance measurement, benchmarking, and optimization,
14	you'll want to turn them off.  This includes various WITNESS-
15	related kernel options, INVARIANTS, malloc debugging flags
16	in userland, and various verbose features in the kernel.  Many
17	developers choose to disable these features on build machines
18	to maximize performance.
19
2020030501:
21	The old rc system has been removed.  Please report any problems
22	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
23	Your personal versions of these files will not be removed, so you can
24	continue to use them. However, you should take great care when updating,
25	especially when using mergemaster, since the compatibility code that
26	utilizes these old scripts has also been removed.
27
28
2920030423:
30	A bug has been fixed in /dev/devctl which would cause devd
31	to hang on boot, were it not for a workaround in devd.  The
32	work around in devd will be removed around 20030507.  You
33	have until then to upgrade your kernel before updating
34	userland.  In general, you should have a userland and
35	kernel that's in sync with each other.  However, given the
36	effects of this bug (hang on boot when starting devd), some
37	allowances are made.
38
3920030329:
40	Alphas with libc from between 20030312 and 20030329 exhibit
41	floating point exceptions (FPEs), most notably in awk(1)
42	while upgrading the system through a buildworld.
43
44	So, to successfully upgrade your Alpha, you must either
45	downgrade your libc.so to a pre-20030312 version, or update
46	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
47	to CFLAGS, then forcibly rebuild and install libc:
48
49	cd /usr/src/lib/libc && \
50	    make cleandir && make obj && \
51	    make -DNOMAN -DNOPROFILE all && \
52	    make -DNOMAN -DNOPROFILE install
53
5420030208:
55	sendmail 8.12.7 has been imported.  It has one important
56	change for IPv6 users.  The default submit.mc now uses
57	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
58	used to connect to the MTA.  Users on IPv6-only machines
59	will need to edit /etc/mail/submit.mc appropriately.
60
6120030128:
62	NODEVFS option has been removed and DEVFS thereby made standard.
63	This makes all references to MAKEDEV obsolete, and they should
64	be removed when convenient.
65
6620030126:
67	The name of the device for the ofw console has changed, sparc64 users
68	must run mergemaster to update their installed /etc/ttys.
69
7020030125:
71	The scheduler framework has grown a second scheduler and consequently
72	you must specify one and only one scheduler in your kernel config.
73	The cvs config files have been updated to use the old scheduler
74	which may be selected via 'options SCHED_4BSD'.  If you would like
75	to try the new, much more experimental, scheduler please try
76	'options SCHED_ULE' and contribute to the arch@ discussion.
77
7820030115:
79	A new version of the wi driver has been imported into the tree.
80	One now must have device wlan in the config file for it to operate
81	properly.
82
83	In addition, there have been some changes to how wi devices are
84	configured for point to point links to bring it more in line
85	with the former way of doing things, as well as compatibility
86	with NetBSD.
87
8820021222:
89 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
90 	used an incompatible form of ABI for returning structures and unions
91 	which FreeBSD's GCC maintainers were not aware of relative to previous
92 	versions of FreeBSD.  We have gone back to the ABI for now, and any
93 	code compiled which is required to interoperate with other code (not
94 	built at the same time) returning structs or unions should be 
95	rebuilt.
96
9720021216:
98	A name change in /etc/netconfig has been reverted to stay
99	compatible with suns TIRPC and also with NetBSD. You need
100	to run mergemaster after make world. A new libc does still work
101	with an outdated /etc/netconfig for some time, but you'll get
102	a warning. This warning will be removed in 20030301.
103
10420021202:
105	The recent binutils upgrade marks a kernel flag day on
106	sparc64: modules built with the old binutils will not work
107	with new kernels and vice versa. Mismatches will result in
108	panics.  Make sure your kernel and modules are in sync.
109
11020021029:
111	The value of IPPROTO_DIVERT has changed.  Make sure to keep
112	your kernel, netstat, natd and any third-party DIVERT
113	consumers in sync.
114
11520021024:
116	Old, compatibility slices have been removed in GEOM kernels.
117	This means that you will have to update your /etc/fstab to
118	not use disk devices of the form /dev/ad0a.  Instead, you
119	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
120	partition really is on.  The old device names have gone
121	away, so if you use them anywhere else, you must also adjust
122	those uses.  (This doesn't affect the disks formatted in
123	the ``dangerously-dedicated'' mode.)
124
12520021023:
126	Alphas with kernels from between 20020830 and 20021023 and/or
127	rtld (ld-elf.so.1) older than 20021023 may experience problems
128	with groff while doing a buildworld (kernel: "out of memory",
129	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
130	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
131
132	So, to successfully upgrade your Alpha, you must either
133	upgrade your kernel and rtld first (which might be a bit
134	tricky), or avoid running the bootstrapped groff during the
135	"transitional" buildworld.  To avoid running groff during the
136	transitional upgrade run make buildworld with -DNOMAN,
137	-DNO_SHAREDOCS, and -DNO_LPR.
138
13920020831:
140	gcc has been upgraded to 3.2.  It is not all binary compatible
141	with earlier versions of gcc for c++ programs.  All c++
142	programs and libraries need to be recompiled.
143
144	Also, if you encounter g++ issues, rm /usr/include/g++/* before
145	doing an installworld to make sure that stale files are removed.
146
14720020827:
148	Our /etc/termcap now has all the entries from the XFree86 xterm
149	almost unchanged. This means xterm now supports color by default.
150	If you used TERM=xterm-color in the past you now should use
151	TERM=xterm. (xterm-color will lead to benign warnings).
152
15320020815:
154	A "bug" in gcc(1) that was hiding warning in system headers was
155	fixed.  It's probably time to add -DNO_WERROR to your make line
156	again.
157
15820020729:
159	COPY is being deprecated.  The 20010530 change was reverted, as
160	it causes far more pain than was expected, and to always compare
161	before installing, please use INSTALL="install -C" again.  The
162	-C option is now silently ignored when used with the -d option.
163
16420020702:
165	Problems with libc_r clients like KDE and GNOME have been resolved.
166	There are still some minor problems with some signals but the 
167	system is stable enough for general use again. SMP is less so than UP
168	but each can successfully complete multiple buildworlds.
169	Libkvm needs to be recompiled due to KSE.
170
17120020701:
172	Now would be a bad time to upgrade.  Something in or near the
173	KSE commit totally broke programs using libc_r like KDE and
174	GNOME.
175
17620020511:
177	The k5su utility installed as part of Kerberos 5 is no longer
178	installed with the set-user-ID bit set by default.  Add
179	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
180	with the set-user-ID bit set.
181
18220020510:
183	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
184	Unfortunately our native GDB (at version 4.18) does not understand
185	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
186	generated debugging information for our native GDB.
187
18820020510:
189	Due to the way CVS works, it may not properly update src/contrib/gcc
190	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
191	and then do a cvs update.
192
19320020421:
194	When exec'ing set[ug]id executables, the kernel now ensures that the
195	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
196
19720020404:
198	New sendmail startup scripts have been installed to make it
199	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
200	variable sendmail_enable to "NO" no longer prevents any sendmail
201	daemons from starting.  Instead, either set sendmail_enable to
202	"NONE" or change mta_start_script to a script for starting
203	an alternative MTA.  Setting mta_start_script to "" will
204	also prevent any MTA from being started at boot.
205
20620020403:
207	UCONSOLE is no longer a valid kernel option.
208
20920020315:
210	FreeBSD 5.0 DP-1 was basically branched today.
211
21220020225:
213	Warnings are now errors in the kernel.  Unless you are a developer,
214	you should add -DNO_WERROR to your make line.
215
21620020217:
217	sendmail 8.12.2 has been imported.  The sendmail binary is no
218	longer a set-user-ID root binary and the infrastructure to support
219	command line mail submission has changed.  Be sure to run
220	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
221	and /etc/mail) and read /etc/mail/README for more details.
222
223	Due to the import of sendmail 8.12.2, a new user and group are
224	required in order for sendmail to run as a set-group-ID
225	binary.  A 'make installworld' will use the new user and group
226	to set the owner and group of /var/spool/clientmqueue and will
227	fail if the new user and group do not exist.  The 'smmsp' user
228	and group must be merged from src/etc/group and
229	src/etc/master.passwd before using 'make installworld'.
230	'mergemaster -p' will do this.  You may need to install
231	mergemaster before this will work if you are updating from a
232	very old version of current.  The updating recipe has changed
233	as of this date.
234
23520020112:
236	The preferred configuration method for PAM is now /etc/pam.d/
237	rather than /etc/pam.conf.  If you have an unmodified
238	pam.conf, just delete it after your next mergemaster run.  If
239	you have local modifications, you can use
240	/usr/src/etc/pam.d/convert.pl to incorporate them into your
241	/etc/pam.d.
242
243	Please see the following url for more details:
244http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
24520011229:
246	If anyone here is already using the new rc.conf(5) variable
247	networkfs_types, please note that it has changed
248http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
249
25020011220:
251	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
252	started out its life in the ISDN4BSD project as an offspring
253	from sys/net/if_spppsubr.c, which eventually got a life of its
254	own.  All the accumulated features and bugfixes of the i4b
255	version have now been merged back into the base system's
256	version now.  The only user-visible change resulting from this
257	is that i4b's sppp(4) interfaces are to be managed with
258	spppcontrol(8) again, since ispppcontrol(8) has been retired
259	as well.  (There has never been rc file support for
260	ispppcontrol in -current, but only in -stable.  That will be
261	reverted by the time the changes are MFCed.)
262
26320011215:
264	The fdc(4) driver has been updated and now automatically
265	recognizes media in `standard' formats (like 1440 KB and
266	720 KB for a 3.5" high-density drive) when accessing the
267	default device node (e. g. /dev/fd0).  The old variety of
268	floppy device nodes /dev/fd*.* is no longer present by
269	default, devices can be created (in DEVFS) on demand.  They
270	will need to be customized then for `odd' densities using
271	fdcontrol(8).
272
27320011209:
274	The bugs in procfs' debugging support code have been fixed,
275	and truss(1) now works again.
276
27720011207:
278	Daily security checks have been split out to use the periodic(8)
279	scripts.  Some change in configuration may be necessary.  Please
280	see 
281http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
282	for details.
283
28420011204:
285	sos added VCD/SVCD support to ata driver and that needs the
286	kernel and burncd to be in sync.
287
28820011203:
289	The procfs pseudo-filesystem has now been converted to use the
290	pseudofs framework.  If you have 'options PROCFS' in your
291	kernel config, you'll need to add 'options PSEUDOFS' if it's
292	not there already.
293
294	This change temporarily breaks truss(1); use ktrace(1) instead
295	until the issue has been resolved.
296
29720011202:
298	A security hole in OpenSSH involving `UseLogin yes' has been
299	patched.
300
30120011126:
302	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
303	after this date.  You need to do this only once.
304
30520011103:
306	Most of the awk issues have been resolved.  Some rough
307	edges may be left, but for the most part things should be
308	back to "normal." For CURRENT's usual definition of "normal."
309
31020011030:
311	Awk has been upgraded to the one true awk from bell labs.  Expect
312	choppy waves in the upgrade process.
313
31420011030:
315	The asr driver problem has been resolved.
316
31720011027:
318	Due to changes in other parts of the system, the asr driver
319	now causes the system to panic on boot.  Do not use it pending
320	correction.  Comment it out of any kernel config file that you
321	try to use from this date forward.
322
32320011025:
324	When crossbuilding, use TARGET=xxx where you used to use
325	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
326	unless you are changing both of them.  To cross build pc98 on
327	an alpha, for example, you need to set TARGET=pc98 and
328	TARGET_ARCH=i386.
329
33020011001:
331	The kernel interface that burncd depends on has changed.
332	You must recompile both the kernel and userland applications
333	at the same time.
334
33520010929:
336	When crossbuilding, please set TARGET_ARCH rather than
337	MACHINE_ARCH to indicate the target.  In the future, one will
338	set TARGET_MACHINE where you set MACHINE now.  At the moment,
339	setting MACHINE alone for same MACHINE_ARCH machines works
340	(eg, you can build pc98 on an i386 machine and vice versa).
341
34220010927:
343	Some weird problems result from using ACPI on some machines.
344	To disable ACPI you can add
345		hint.acpi.0.disabled="1"
346	to /boot/loader.conf (or by putting set X=Y at the boot
347	loader "ok" prompt).
348
349	Alternatively, you can remove it from /boot/kernel/acpi.ko
350	or use the MODULES_OVERRIDE function in your kernel config
351	file and not list acpi in that list.
352
35320010924:
354	The buildworld has been fixed.  You may need to install
355	the 4.x compatibility libraries for some old binaries
356	to work.  Add COMPAT4X=true to your /etc/make.conf to
357	get them installed on every installworld, or execute the
358	following to get them installed only once:
359		cd src/lib/compat/compat4x.<arch>
360		make all install
361	You will see ``__stdoutp undefined'' until you do this.
362
36320010919:
364	There's a bug in the world build process.  The cross-tools
365	are build with the NEW headers, but the OLD libc.a.  This
366	leads to all kinds of problems with the new libc.  A temporary
367	workaround is to add
368		CFLAGS="-O -pipe -D_OLD_STDIO"
369	before building world when upgrading from 4.x to current.  This
370	can be removed afterwards.
371
372	A proper fix to the buildworld target is needed.
373
37420010918:
375	Peter has committed his new kthread nfs client/server code.
376	NFS may be unstable after this date.
377
37820010912:
379	KSE has hit the tree.  Lots of things are now different in
380	the kernel.  While a few problems were introduced in the
381	initial commit, most of the major ones have been found and
382	corrected.
383
38420010901:
385	In OLDCARD, CardBus bridges appear to be stable.  The work
386	arounds described in the 20010604 entry are now no longer
387	necessary and will be ignored.  Most insert/remove problems
388	have been rectified around this date.
389
39020010823:
391 	named now runs as user bind and group bind rather than as 
392 	root.  If named_enable is set to YES in /etc/rc.conf, ensure 
393 	that user bind is available in /etc/passwd (using vipw(8)) 
394 	and that group bind is available in /etc/group.  Also make 
395 	sure that user or group bind has read (and not write) 
396 	permission for your name server configuration and that it 
397 	has read and write permission for your slave zone files and 
398 	directory.
399 
400 	If you wish to continue to run named as root (a less secure 
401 	alternative), add a line to /etc/rc.conf saying
402 
403 		named_flags=
404
40520010709:
406	The PAM libraries have had an API upgrade that is beyond
407	the ability of the shared library major number to handle.
408	It is manifested by PAM-using ports dumping core. The
409	solution is to rebuild those ports.
410
41120010628:
412	The kernel compile module has moved from src/sys/compile/FOO
413	to src/sys/${MACHINE}/compile/FOO.
414
41520010625:
416	The pccard modem issue from 20010613 has been corrected.
417	OLDCARD support is still a little weak in -current.  slot 1 is
418	known not to work on some TI based cardbus bridges.  Some
419	cardbus bridges do not properly detect insert/removal events.
420	IRQ configuration needs more safety belts.
421
42220010617:
423	Softupdates problems have been corrected.
424
42520010614:
426	Peter ripped out the linkerset support.  You must, as always,
427	rerun config after you cvsup if you are using the traditional
428	kernel building methods.
429
43020010613:
431	pccard modems may not work with current after 20010604 date.  Some
432	do, others result in panics.  *MAKE*SURE* that you update your
433	config and /etc/rc.conf ala the 20010604 entry, or you will have
434	problems (this issue will be fixed, it just hasn't been yet).
435
43620010613:
437	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
438	use them in current.  You can disable softupdates on all mounted
439	partitions, or remove SOFTUPDATES the kernel config file.
440
44120010612:
442	After Peter's commits to the hints code, people have been noticing
443	that certain devices are attached (or try to) twice.  This is due
444	to having both static hints as well as a /boot/device.hints.  To
445	work around this issue, please use only one or the other mechanism
446	until this bug is fixed.
447
448	Please note that a feature of config is that if you have config
449	file FOO and FOO.hints, it automatically adds FOO.hints to the
450	hints.c file, whether you want it to or not.
451
45220010610:
453	Locale names have changed to match other systems better.
454
45520010604:
456	pccard support for pci cards has been committed.  You must change
457	your /etc/pccard.conf irq lines.  It must match the irq used by
458	pcic device.  Interrupt storms may result if you fail to do this.
459	Interrupt storms look a lot like a hang.
460
461	You must also install a new pccardd, otherwise you will get an
462	interrupt storm at card reset time (just after it tells you what
463	it is).
464
465	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
466	not to ask the kernel if the interrupt is really free or not before
467	using it.  You can either change the /etc/pccard.conf irq lines to
468	match pcic, or add "-i X" to the pccardd_flags.
469
47020010530:
471	INSTALL=install -C is being deprecated.  If you want to do this,
472	use COPY=-C instead.  The former method will be supported for only
473	a limited time.  If you see
474
475install: warning: the -d and -C options may not be specified together
476
477	in your makeworld, then you need to migrate towards using
478	COPY=-C.
479
48020010525:
481	It appears that vm is now stable enough to use again.  However,
482	there may be other problems, so caution is still urged.  alpha
483	definitely is in bad shape.
484
48520010521:
486	Minor repo damage has happened.  This may cause problems
487	with cvsup of ports.  If you get errors, please see
488	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
489	at the bottom for details on a workaround.  The error message
490	is
491Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
492
49320010520:
494	Vm and/or swapping are busted on -current.  Please be patient.
495
49620010519:
497	pccard has had much reorganizational work done to it over
498	the past few days.  Everything should still work, but if
499	not, please contact imp@freebsd.org.
500
50120010517:
502	ata ioctl changed.  Make sure to recompile both kernel and
503	userland at the same time.
504
50520010517:
506	New ncurses imported.
507
50820010512:
509	DEVFS is now opt out, not opt in.  Barring major problems, this
510	will be the only way to go starting July 1.
511
51220010504:
513	OpenSSH has been updated to 2.9.  Some defaults are different,
514	including RhostsRSAAuthentication, which changes from yes to no.
515
51620010502:
517	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
518
51920010501:
520	Building perl was broken at 02:25:25 PDT.
521
52220010430:
523	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
524	go back in the water.
525
52620010429:
527	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
528	this date, but before the correction date.
529
53020010423:
531	old fsck and new kernel interactions appear to have been fixed.
532
53320010411:
534	fsck and the kernel were changed to handle some optimizations
535	to directory layout.  This breaks backward compatibility.
536	Update only if you understand that you must not use the old
537	fsck with the new kernel ever.
538
53920010330:
540	fsck has changed the meaning of the pass column in /etc/fstab.
541	Please see the cvs commit to fsck.8 or the fsck.8 man page for
542	details.  It is unclear if changes to /etc/fstab are necessary.
543
54420010319:
545	portmap had changed name to rpcbind for maximum POLA in your
546	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
547	other rpc based programs that rely on portmapper will not work
548	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
549
55020010315:
551	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
552	and ATA_ENABLE_TAGS are no longer kernel options.  They have
553	been replaced by tunables.  See ata.4 for details.
554
55520010312:
556	The fxp driver was converted to use miibus.  If you compile
557	fxp into your kernel statically, you will need to add miibus.
558
55920010312:
560	The wi device now defaults to BSS (infrastructure) mode
561	instead of ad-hoc.
562
56320010310:
564	/dev/urandom should be a symbolic link to /dev/random now.
565	Users of current not using DEVFS need to run MAKEDEV std.
566	ssh might not work if you don't.
567
56820010303:
569	The ed driver has been updated.  It now allows mii attachments,
570	which means that you must include the miibus in your kernel if
571	you use the ed driver.
572
57320010220:
574	The problems with libc have been corrected.  It is now mostly
575	safe to go back into the water.
576
57720010211:
578	The size of FILE was changed.  This breaks upgrading.  If
579	you must upgrade, be prepared for pain.  It also breaks almost
580	all binaries that you've compiled on -current.  You are warned
581	that before upgrading would be a good time to do a level 0
582	dump of your system.  No, really, I mean it this time.
583
584	To get to the new system, you'll need to use the following
585	workaround.  Hopefully this can be sorted out so that we
586	don't have to move this to the updating section.
587
588	To get around the installworld problem, do:
589		# cd /usr/src/usr.bin/sed
590		# make install
591		# cd /usr/src
592		# make installworld
593	If that doesn't work, then try:
594		# make -k installworld
595		# make installworld
596
59720010207:
598	DEVFS is now the default.  If you use vinum, make sure that you
599	do not include devfs in your kernel as problems result.
600
60120010205:
602	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
603	Remove them from your config.
604
60520010122:
606	****************************** WARNING ******************************
607			buildkernel has been changed slightly
608	****************************** WARNING ******************************
609	KERNCONF replaces the variable KERNEL for buildkernel.  You
610	should update your scripts and make.conf accordingly.
611
61220010119:
613	config has changed to allow DEV_FOO as a replacement for NFOO.
614	This requires a new config to build correctly.
615
61620010116:
617	The kernel option I386_CPU is now mutually exclusive with the
618	other cpu types. If you have an i386 system, be sure that it
619	only had this line.  Remove it for all other configurations.
620
62120010110:
622	Changes to the kernel require it and burncd be in sync.
623
62420010102:
625	Everyone who has hw.sndunit set to something in
626	/etc/sysctl.conf, it is now hw.snd.unit.
627
62820010101:
629	ex and vi were broken by some changes to sys/queue.h.  If you
630	have a bad vi, you will see make buildworld fail with a core
631	dump while building termcap.  You can work around this problem
632	by adding -k to your make buildworld.  This will cause the
633	build to complete and install a new vi.  Once that's done, you
634	can rebuild again without the -k to pick up anything that
635	might have been ignored by the -k option.
636
637	Others have suggested that you can just rebuild libc if your
638	vi/ex is dynamically linked, but I've not received any reports
639	of this working.
640
64120001228:
642	There have been some changes to libcrypt in -current.  The
643	libscrypt/libdescrypt symlink silliness is gone and the installed
644	libcrypt is fully functional.  Be aware of this.
645
64620001218:
647	Linksys Fast Ethernet PCCARD cards supported by the ed driver
648	now require the addition of flag 0x80000 to their config line
649	in pccard.conf(5).  This flag is not optional.  These Linksys
650	cards will not be recognized without it.
651
65220001205:
653	Important new FreeBSD-version stuff: PAM support has been worked
654	in, partially from the "Unix" OpenSSH version.  This requires
655	adding the following in pam.conf:
656  
657	sshd    auth    sufficient      pam_skey.so
658	sshd    auth    required        pam_unix.so         try_first_pass
659	sshd    session required        pam_permit.so
660
66120001031:
662	cvs updated to 1.11.
663
66420001020:
665	The random device needs more entropy, so you need to make sure
666	that you've run mergemaster to get a /etc/rc which will seed
667	/dev/random.  If you don't and the system hangs after ldconfig,
668	then banging on the keyboard randomly until it unhangs is one
669	workaround.
670
67120001010:
672	****************************** WARNING ******************************
673				Sendmail has been updated.
674	****************************** WARNING ******************************
675	o mail.local(8) is no longer installed as a set-user-id binary.
676	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
677	  is set.
678	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
679	  commands.
680	o Now using sendmail's version of vacation(1).
681	o The sendmail cf building tools (contrib/sendmail/cf) are installed
682	  in /usr/share/sendmail/cf.
683	o sendmail.cw changed to local-host-names
684
685	More details can be found at
686		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
687
68820001009:
689	The ports tree's new layout is in place.  Be sure to update
690	your entire ports tree, or you will have problems.
691
69220001006:
693	The perl build procedure no longer installs miniperl, nor uses
694	the installed miniperl.  It is recommended that you delete
695	/usr/bin/miniperl.
696
69720001005:
698	This weekend the ports tree will be updated to a new layout.
699	It will be in an inconsistent state until noted in the UPDATING
700	file, or with asami-san's message to the relevant mailing
701	lists.  With this new layout, you'll need to update the whole
702	tree for anything to work.
703
70420000928:
705	There was a change in the passwd format.  Need more information.
706
70720000916:
708	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
709	place.  Please update boot loader (not the boot blocks) at the
710	same time as your kernel.
711
71220000914:
713	The new pmtimer device is necessary for laptops.  Failure to
714	include the device will cause suspended laptops losing time
715	when they resume.  Include
716		device		pmtimer
717	in your config file and
718		hint.pmtimer.0.at="isa"
719	to your /boot/device.hints file.
720
72120000911:
722	The random device has been turned into a (pseudo-)device,
723	rather than an option. The supplied kernel config files have
724	been updated. You will need to do something similar in your
725	own kernel config file.
726	Remove:
727		options		RANDOMDEV
728	Add:
729		device		random
730	If you prefer to load the loadable module, you need to do
731	nothing.
732
73320000909:
734	The random device module has been renamed from randomdev.ko to
735	random.ko. You will need to edit your /boot/loader.conf to
736	reflect this if you load this module at boot time.
737	The line should read:
738		random_load="YES"
739
74020000907:
741	The SMPNG commit has happened.  It should work, but if it
742	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
743	to be a variety of minor issues.  Please see 20000905 to make
744	sure you don't have model loading problems which might at
745	first blush appear related to SMP.
746
74720000906:
748	nsswitch has been imported from NetBSD.  Among other things,
749	this means that /etc/host.conf is no longer used.  See
750	nsswitch.conf(5) instead.  Note that at boot time rc.network
751	will attempt to produce a new nsswitch.conf file for you if you
752	don't have one, and you have host.conf.
753
75420000905:
755	The ucred structure changed size.  This breaks the interface
756	that mountd uses.  Trying to use an older mountd with a newer
757	kernel guarantees a panic.  This means that you need to use
758	kernels newer than today only with matching mountd, but you
759	needed to do that anyway with the boot loader changes.
760
76120000905:
762	The boot loader has been updated.  The new default kernel is
763	now /boot/kernel/kernel.ko.  The new default module location
764	is /boot/kernel.
765
766	You *MUST* upgrade your boot loader and kernel at the same time.
767	The easiest way to do this is to do the buildworld/buildkernel/
768	installkernel/installworld dance.
769
770	Furthermore, you are urged to delete your old /modules directory
771	before booting the new kernel, since kldload will find stale
772	modules in that directory instead of finding them in the correct
773	path, /boot/kernel.  The most common complaint that this cures
774	is that the linux module crashes your machine after the update.
775
776	if [ ! -d /boot/kernel.old ]; then
777		mv /modules.old /boot/kernel.old
778		chflags noschg /kernel.old
779		mv /kernel.old /boot/kernel.old/kernel.ko
780		chflags schg /boot/kernel.old/kernel.ko
781	fi
782
78320000904:
784	A new issue with the sendmail upgrade has come to light.
785	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
786	incorrectly install the default aliases in /etc/mail rather than
787	move the old one from /etc.  So you'll need to manually move the
788	file, create a symbolic link, remove the old /etc/aliases.db and
789	run newaliases.  For safety sake, you should stop sendmail
790	while doing this and run the upgrade when locally sourced email
791	is not likely to be generated.
792
79320000825:
794	/boot/device.hints is now required for installkernel to
795	succeed.  You should copy GENERIC.hints for your architecture
796	into /boot/device.hints.  If and only if you compile hints
797	into your kernel, then this file may be empty.  Please note,
798	if you have an empty or missing /boot/device.hints file and
799	you neglected to compile hints into your kernel, no boot
800	messages will appear after the boot loader tries to start the
801	kernel.
802
80320000821:
804	If you do NOT have ``options RANDOMDEV'' in your kernel and
805	you DO want the random device then add randomdev_load="YES" to
806	/boot/loader.conf.
807
80820000812:
809	suidperl is now always built and installed on the system, but
810	with permissions of 511.  If you have applications that use
811	this program, you are now required to add ENABLE_SUIDPERL=true
812	to /etc/make.conf.  If you forget to do this,
813		chmod 4511 /usr/bin/suidperl
814	will fix this until the next build.
815
81620000812:
817	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
818	visible changes that may immediately affect your configuration
819	include:
820	- New default file locations from src/contrib/sendmail/cf/README
821	- newaliases limited to root and trusted users
822	- MSA port (587) turned on by default
823	- New queue file naming system so can't go from 8.11 -> 8.9
824	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
825	- FEATURE(`nullclient') is more full featured
826	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
827	- mail.local FreeBSD-only -b option changed to -B
828	- See src/contrib/sendmail/RELEASE_NOTES for more info
829
83020000810:
831	suidperl (aka sperl) is no longer build by default.  You must
832	specifically define BUILD_SUIDPERL to "true" for it to be build.
833	Furthermore, we recommend that you remove /usr/bin/sperl* and
834	/usr/bin/suidperl files from your system unless you have a
835	specific use for it.
836
83720000729:
838	Networking defaults have been tightened.  Anybody upgrading
839	/etc/defaults/rc.conf needs to add the following lines to
840	/etc/rc.conf if they want to have the same setup
841	afterwards (unless the variables already are set, of course):
842		# Enable network daemons for user convenience.
843		inetd_enable="YES"
844		portmap_enable="YES"
845		sendmail_enable="YES"
846
84720000728:
848	If you have null_load="YES" in your /boot/loader.conf, you
849	will need to change that to nullfs_load="YES".
850
85120000728:
852	The "installkernel" target has changed slightly. Now even if
853	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
854	it will install the MYKERNEL file (built with the buildkernel
855	target) as /kernel rather than /MYKERNEL. Those who have
856	updated their /boot/loader.conf files to point to /MYKERNEL
857	should remove that entry or perform manual rename of /kernel
858	to /MYKERNEL.
859
86020000711:
861	If you use CVSUP or CTM to get CVS trees, AND you used to get 
862	the old crypto files from internat.freebsd.org AND you check
863	out files from the CVS tree with the cvs command, please read
864		http://people.freebsd.org/~imp/internat.txt
865	for details on potential problems that you might have and how
866	to get around them.
867
868	If you are merely a mirror, or don't answer yes to each of the
869	clauses above, you needn't worry.
870
87120000711:
872	/etc/security has been updated to print the inode number of
873	setuid programs that have changed.  You will see a large spike
874	in the number of changed programs the first time when you run
875	mergemaster to get a new /etc/security.
876
87720000710:
878	/dev/random now has good entropy collection (from the keyboard
879	and sysmouse drivers). Please ensure that either `options
880	RANDOMDEV' is present in your kernel config file or that
881	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
882	not have the /dev/random driver, OpenSSL (and consequently
883	lots of crypto tools (like SSH)) will fail with strange
884	errors. (see below, 20000624).
885
886	FreeBSD-current is safe again to run Crypto.
887
88820000709:
889	phk made the malloc default options AJ.  This may slow things
890	down and uncover other latent bugs in the code.  If you need to
891	run at full speed, you can disable this by doing the following:
892		ln -s aj /etc/malloc.conf
893
89420000706:
895	libftpio's version was accidentally bumped a few days ago.  This
896	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
897	before doing your next buildworld/installworld pair.  It certainly
898	won't hurt to remove it before the update procedure.  It will
899	break fetch until a new one is built, but ftp can be used in the
900	interim if needed.
901
90220000705:
903	The crypto packages have changed for the cvsup.  This has been done
904	in a backward compatible way, but the old packages will go away at
905	some point in the future.  Look at /usr/share/examples/cvsup for
906	details.
907
90820000704:
909	With the new sys/modules/sound/drivers/*, you will need to
910	set SYSDIR until you do an installworld after July 7th.
911
91220000704:
913	rc.shutdown and rc will now call the rc.d scripts with start
914	or stop.  This may cause some harmless warnings from older
915	rc.d scripts that haven't been updated.
916
91720000630:
918	The libfetch based version of fetch has gone into the tree.
919	Minor problems may result on some of the less popular sites,
920	which should be reported to des@freebsd.org.
921
92220000625:
923	From approximately this date forward, one must have the crypto
924	system installed in order to build the system and kernel.
925	While not technically strictly true, one should treat it as
926	required and grab the crypto bits.  If you are grabbing CVS
927	trees, src-all and cvs-crypto should be treated as if they
928	were required.  You should check with the latest collections
929	to make sure that these haven't changed.
930
93120000624:
932	Mark Murray just committed the first parts of a cleanup of
933	/dev/zero, et al.  This is also cleaning up /dev/random.
934	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
935	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
936	until Mark can merge in the fixes to this work in progress.
937	openssh and openssl should not be used to generate keys from this
938	date to the completion of the work.
939
940	If you must operate at this reduced level of security, add '
941	options RANDOMDEV' to your kernel or modload the randomdev
942	module.  You may also need to copy a new MAKEDEV to /dev and
943	recreate the random and urandom devices.
944
94520000622:
946	The license on the softupdates is now a standard 2 clause
947	BSD license.  You may need to remove your symbolic links
948	that used to be required when updating.
949
95020000621:
951	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
952	the config file update procedure.
953		http://people.freebsd.org/~imp/config-upd.html
954	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
955	isn't buildable.  However, you can generate a LINT file:
956		cd /sys/<ARCH>/conf && make LINT
957
95820000620:
959	Binutils 2.10 have hit the tree, or will shortly.  As soon
960	as they do, the problem noted in 20000522 will be resolved and
961	that workaround will no longer be required.
962
96320000615:
964	phk removed the compatibility creation of wd devices in the
965	ad driver.  If you haven't done so already, you must update
966	your fstab, etc to use the ad devices instead of the wd
967	devices.
968
969	In addition, you'll need to update your boot blocks to a
970	more modern version, if you haven't already done so.  Modern
971	here means 4.0 release or newer (although older releases
972	may work).
973
97420000612:
975	Peter took an axe to config(8).  Be sure that you read his mail
976	on the topic before even thinking about updating.  You will
977	need to create a /boot/device.hints or add a hints directive
978	to your config file to compile them in statically.  The format
979	of the config file has changed as well.  Please see GENERIC or
980	NEWCARD for examples of the new format.
981
982	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
983	says that it has been fixed, assume that must use the hints mechanism
984	in the loader if you need to use a machine with very old ISA cards
985	in it.
986
98720000522:
988	A new set of binutils went into the tree today.  Anybody
989	building a kernel after this point is advised that they need
990	to rebuild their binutils (or better yet do a
991	buildworld/installworld) before building a new kernel.
992
993	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
994	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
995	is recommended that you don't set this option until the problem
996	is resolved.
997
99820000513:
999	The ethernet drivers were all updated to clean up the BPF handling.
1000
100120000510:
1002	The problems with boot blocks on the alphas have been corrected.
1003	This will require some care in updating alphas.  A new libstand
1004	is requires for the boot blocks to build properly.
1005
100620000503:
1007	Recompile all kld modules.  Proper version dependency info
1008	is now available.
1009
101020000502:
1011	Modules have been disconnected from the buildworld tree and 
1012	connected to the kernel building instead.
1013
101420000427:
1015	You may need to build gperf
1016		cd /usr/src/gnu/usr.bin/gperf && make depend all install
1017	when upgrading from 4.0 -> current.  The build system now uses
1018	an option only in -current.
1019
102020000417:
1021	The method that we brand ELF binaries has changed to be more
1022	acceptable to the binutils maintainers.  You will need to
1023	rebrand your ELF binaries that aren't native.  One problem
1024	binary is the Linux ldconfig.  After your make world, but
1025	before you reboot, you'll need to issue:
1026		brandelf -t Linux /compat/linux/sbin/ldconfig
1027	if you have Linux compatibility enabled on your machine.
1028
102920000320:
1030	If you have really bad/marginal IDE drives, you may find they
1031	don't work well.  Use pio mode instead.  The easiest way to
1032	cope if you have a problem combination is to add:
1033		/sbin/sysctl hw.ata.ata_dma=0
1034	to the start of /etc/rc.conf.
1035
103620000319:
1037	The ISA and PCI compatibility shims have been connected to the
1038	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1039	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1040	include the appropriate option in your kernel config.  Drivers
1041	using the shims should be updated or they won't ship with
1042	5.0-RELEASE, targeted for 2001.
1043
104420000318:
1045	We've entered the traditional post release dumping party.
1046	Large kernel changes are being committed and are in the
1047	works.  It is important to keep the systems' klds and kernel
1048	in sync as kernel interfaces and structures are changing.
1049	Before reporting kernel panics, make sure that all modules
1050	that you are loading are up to date.
1051
105220000315:
1053	If you are upgrading from an older version of FreeBSD, you
1054	need to update your boot blocks as well.  'disklabel -B ad0'
1055	will do the trick.  This isn't critical until you remove your
1056	wd device entries in /dev, at which point your system will not
1057	boot.
1058
105920000315:
1060	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
1061	to upgrade to 4.0 from 3.x.
1062
1063COMMON ITEMS:
1064
1065	General Notes
1066	-------------
1067	Avoid using make -j when upgrading.  From time to time in the
1068	past there have been problems using -j with buildworld and/or
1069	installworld.  This is especially true when upgrading between
1070	"distant" versions (eg one that cross a major release boundary
1071	or several minor releases, or when several months have passed
1072	on the -current branch).
1073
1074	Sometimes, obscure build problems are the result of environment
1075	poisoning.  This can happen because the make utility reads its
1076	environment when searching for values for global variables.
1077	To run your build attempts in an "environmental clean room",
1078	prefix all make commands with 'env -i '.  See the env(1) manual
1079	page for more details.
1080
1081	To build a kernel
1082	-----------------
1083	If you are updating from a prior version of FreeBSD (even one just
1084	a few days old), you should follow this procedure. With a
1085	/usr/obj tree with a fresh buildworld,
1086	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1087	make installkernel KERNCONF=YOUR_KERNEL_HERE
1088
1089	To just build a kernel when you know that it won't mess you up
1090	--------------------------------------------------------------
1091	cd src/sys/{i386,alpha}/conf
1092	config KERNEL_NAME_HERE
1093	cd ../../compile/KERNEL_NAME_HERE
1094	make depend
1095	make
1096	make install	
1097
1098	If this fails, go to the "To build a kernel" section.
1099
1100	To rebuild everything and install it on the current system.
1101	-----------------------------------------------------------
1102	# Note: sometimes if you are running current you gotta do more than
1103	# is listed here if you are upgrading from a really old current.
1104
1105	<make sure you have good level 0 dumps>
1106	<maybe fix /etc/fstab>				[7]
1107	make buildworld
1108	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1109	make installkernel KERNCONF=YOUR_KERNEL_HERE
1110							[1]
1111	<reboot in single user>				[3]
1112	mergemaster -p					[5]
1113	make installworld
1114	mergemaster					[4]
1115	<reboot>
1116
1117
1118	To cross-install current onto a separate partition
1119	--------------------------------------------------
1120	# In this approach we use a separate partition to hold
1121	# current's root, 'usr', and 'var' directories.   A partition
1122	# holding "/", "/usr" and "/var" should be about 2GB in
1123	# size.
1124
1125	<make sure you have good level 0 dumps>
1126	<boot into -stable>
1127	make buildworld
1128	<maybe newfs current's root partition>
1129	<mount current's root partition on directory ${CURRENT_ROOT}>
1130	make installworld DESTDIR=${CURRENT_ROOT}
1131	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1132	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1133		${CURRENT_ROOT}/boot/device.hints	# as needed
1134	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1135	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1136	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1137	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1138	<reboot into current>
1139	<do a "native" rebuild/install as described in the previous section>
1140	<maybe install compatibility libraries from /usr/src/lib/compat>
1141 	<reboot>	
1142
1143
1144	To upgrade in-place from 4.x-stable to current 
1145	----------------------------------------------
1146	# 5.x uses more space than 4.x.  Also, the location of kernel
1147	# modules has changed.  If you are installing 5.0 onto a 4.x
1148	# system, you'll need about 30MB of free disk space on your /
1149	# partition.  If you have less than this, you may encounter difficult
1150	# to back out of problems with this procedure.  If /tmp is on
1151	# the / partition, you may want to completely remove all its content
1152	# before upgrading, as this can be a common source of shortage of
1153	# space on /.
1154	
1155	<make sure you have good level 0 dumps>
1156	<maybe fix /etc/fstab>				[7]
1157	make buildworld					[9]
1158	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1159	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1160	make installkernel KERNCONF=YOUR_KERNEL_HERE
1161	cd src/sys/boot ; make install			[6]
1162							[1]
1163	<reboot in single user>				[3]
1164	mergemaster -p					[5]
1165	rm -rf /usr/include/g++
1166	make installworld
1167	mergemaster					[4]
1168	<reboot>
1169
1170	Make sure that you've read the UPDATING file to understand the
1171	tweaks to various things you need.  At this point in the life
1172	cycle of current, things change often and you are on your own
1173	to cope.  The defaults can also change, so please read ALL of
1174	the UPDATING entries.
1175
1176	Also, if you are tracking -current, you must be subscribed to
1177	freebsd-current@freebsd.org.  Make sure that before you update
1178	your sources that you have read and understood all the recent
1179	messages there.  If in doubt, please track -stable which has
1180	much fewer pitfalls.
1181
1182	[1] If you have third party modules, such as vmware, you
1183	should disable them at this point so they don't crash your
1184	system on reboot.
1185
1186	[2] If you have legacy ISA devices, you may need to create
1187	your own device.hints to reflect your unique hardware
1188	configuration.
1189
1190	[3] From the bootblocks, boot -s, and then do
1191		fsck -p
1192		mount -u /
1193		mount -a
1194		cd /usr/src
1195		adjkerntz -i		# if CMOS is wall time
1196	Also, when doing a major release upgrade, it is required that
1197	you boot into single user mode to do the installworld.
1198	For the 4.x -> 5.0 upgrade, you will also see many messages about
1199	needing to recompile your userland.  These are harmless and can
1200	be ignored while you proceed to the next step.
1201
1202	[4] Note: This step is non-optional.  Failure to do this step
1203	can result in a significant reduction in the functionality of the
1204	system.  Attempting to do it by hand is not recommended and those
1205	that pursue this avenue should read this file carefully, as well
1206	as the archives of freebsd-current and freebsd-hackers mailing lists
1207	for potential gotchas.
1208
1209	[5] Usually this step is a noop.  However, from time to time
1210	you may need to do this if you get unknown user in the following
1211	step.  It never hurts to do it all the time.  You may need to
1212	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1213	install) after the buildworld before this step if you last updated
1214	from current before 20020224 or from -stable before 20020408.
1215
1216	[6] 4.x boot loader can be used to boot a 5.x system, however
1217	it is difficult to do that at best.  If you wish to try, then
1218	you should interrupt the boot and at the ok prompt type:
1219		ok unload
1220		ok boot /boot/kernel/kernel
1221	If this fails to work, you must install a new boot loader as
1222	described here.
1223
1224	[7] Before you upgrade, please make sure that you are not using
1225	compatibility slices.  These are device names of the form, on i386
1226	and other architectures that use MBR slicing, /dev/ad0a without the
1227	actual slice name.  Chances are excellent that these will break.
1228	You generally must update these entries to use the post FreeBSD
1229	2.x form of /dev/ad0s1a.
1230
1231	[8] In order to have a kernel that can run the 4.x binaries
1232	needed to do an installworld, you must include the COMPAT_FREEBSD4
1233	option in your kernel.  Failure to do so may leave you with a system
1234	that is hard to boot to recover.
1235
1236	[9] When checking out sources, you must include the -P flag to have
1237	cvs prune empty directories.
1238FORMAT:
1239
1240This file contains a list, in reverse chronological order, of major
1241breakages in tracking -current.  Not all things will be listed here,
1242and it only starts on March 15, 2000.  Updating files can found in
1243previous releases if your system is older than this.
1244
1245Copyright information:
1246
1247Copyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1248
1249Redistribution, publication, translation and use, with or without
1250modification, in full or in part, in any form or format of this
1251document are permitted without further permission from the author.
1252
1253THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1254IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1255WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1256DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1257INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1258(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1259SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1260HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1261STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1262IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1263POSSIBILITY OF SUCH DAMAGE.
1264
1265If you find this document useful, and you want to, you may buy the
1266author a beer.
1267
1268Contact Warner Losh if you have any questions about your use of
1269this document.
1270
1271$FreeBSD: head/UPDATING 114492 2003-05-02 05:27:35Z dougb $
1272