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