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