UPDATING revision 119413
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
2020030824:
21	ATAng has been committed. You need to build world as sys/ata.h 
22	has changed, and userland atacontrol depends on it.
23	If you use ATA SW raids you need "device ataraid" in your
24	kernel config file, as it is no longer pulled in automatically.
25
2620030819:
27	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
28	Among other things, this changes the device enumeration to be
29	closer to Solaris.  Be aware that, this can even cause the machine
30	to not boot without manual intervention before the fstab is adjusted.
31
3220030728:
33	All current USB and Firewire quirks in da(4) have been deprecated
34	and will be removed for 5.2.  If this causes failure for your
35	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
36	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
37	so the quirk can be re-enabled.
38
3920030722:
40	FPU-less support has been removed from FreeBSD.  Chances are you won't
41	notice.  386+387 support should still work after this change, but
42	it is now a minimum requirement for the i386 port that you have real
43	FPU hardware.
44
4520030714:
46	Some people are having problems with changes related to /rescue.
47	If you are building -j N, you will need to define NO_RESCUE.  Others
48	will need to define it if /rescue has issues with their environment.
49	People should report those issues to current@.
50
5120030711:
52	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
53	across this point.  Further, it might be a good idea to remove
54	/usr/obj.
55
5620030613: [retrospective]
57	There was a small window in which sed(1) was broken.  If you
58	happen to have sed(1) installed during that window, which is
59	evidenced by an inability to build world with the failure
60	given below, you need to manually build and install sed(1)
61	(and only sed(1)) before doing anything else. This is a one-
62	time snafu. Typical failure mode:
63
64	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
65	targmatch.h:7:1: null character(s) ignored
66	targmatch.h:12:1: null character(s) ignored
67	targmatch.h:16:1: null character(s) ignored
68		:
69
70	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
71	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
72	usr.bin/sed/process.c).
73
7420030610:
75	Remove deprecated locale names and transition period code
76	for them, finishing switching to the new scheme. Check your
77	LANG environment variable.
78
7920030609:
80	CCD has been changed to be a fully GEOMified class.  Kernel
81	and ccdconfig(8) needs to be in sync, this is particularly
82	important to remember beforehand if your source tree is on
83	a ccd device.  Consider making a copy of the old ccdconfig
84	into /boot/kernel.good or wherever you keep your backup
85	kernel.
86
8720030505:
88	Kerberos 5 (Heimdal) is now built by default. Setting
89	MAKE_KERBEROS5 no longer has any effect. If you do NOT
90	want the "base" Kerberos 5, you need to set NO_KERBEROS.
91
9220030502:
93	groff has been updated.  If you try to do a buildworld and
94	get an infinite loop in troff, update to May 4th or newer.  If you
95	have a newer kernel than userland, you may need to set the OSRELDATE
96	to 500110 in your environment before starting a buildworld.
97
9820030501:
99	The old rc system has been removed.  Please report any problems
100	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
101	Your personal versions of these files will not be removed, so you can
102	continue to use them. However, you should take great care when updating,
103	especially when using mergemaster, since the compatibility code that
104	utilizes these old scripts has also been removed.
105
10620030423:
107	A bug has been fixed in /dev/devctl which would cause devd
108	to hang on boot, were it not for a workaround in devd.  The
109	work around in devd will be removed around 20030507.  You
110	have until then to upgrade your kernel before updating
111	userland.  In general, you should have a userland and
112	kernel that's in sync with each other.  However, given the
113	effects of this bug (hang on boot when starting devd), some
114	allowances are made.
115
11620030329:
117	Alphas with libc from between 20030312 and 20030329 exhibit
118	floating point exceptions (FPEs), most notably in awk(1)
119	while upgrading the system through a buildworld.
120
121	So, to successfully upgrade your Alpha, you must either
122	downgrade your libc.so to a pre-20030312 version, or update
123	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
124	to CFLAGS, then forcibly rebuild and install libc:
125
126	cd /usr/src/lib/libc && \
127	    make cleandir && make obj && \
128	    make -DNOMAN -DNOPROFILE all && \
129	    make -DNOMAN -DNOPROFILE install
130
13120030208:
132	sendmail 8.12.7 has been imported.  It has one important
133	change for IPv6 users.  The default submit.mc now uses
134	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
135	used to connect to the MTA.  Users on IPv6-only machines
136	will need to edit /etc/mail/submit.mc appropriately.
137
13820030128:
139	NODEVFS option has been removed and DEVFS thereby made standard.
140	This makes all references to MAKEDEV obsolete, and they should
141	be removed when convenient.
142
14320030126:
144	The name of the device for the ofw console has changed, sparc64 users
145	must run mergemaster to update their installed /etc/ttys.
146
14720030125:
148	The scheduler framework has grown a second scheduler and consequently
149	you must specify one and only one scheduler in your kernel config.
150	The cvs config files have been updated to use the old scheduler
151	which may be selected via 'options SCHED_4BSD'.  If you would like
152	to try the new, much more experimental, scheduler please try
153	'options SCHED_ULE' and contribute to the arch@ discussion.
154
15520030115:
156	A new version of the wi driver has been imported into the tree.
157	One now must have device wlan in the config file for it to operate
158	properly.
159
160	In addition, there have been some changes to how wi devices are
161	configured for point to point links to bring it more in line
162	with the former way of doing things, as well as compatibility
163	with NetBSD.
164
16520021222:
166 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
167 	used an incompatible form of ABI for returning structures and unions
168 	which FreeBSD's GCC maintainers were not aware of relative to previous
169 	versions of FreeBSD.  We have gone back to the ABI for now, and any
170 	code compiled which is required to interoperate with other code (not
171 	built at the same time) returning structs or unions should be 
172	rebuilt.
173
17420021216:
175	A name change in /etc/netconfig has been reverted to stay
176	compatible with suns TIRPC and also with NetBSD. You need
177	to run mergemaster after make world. A new libc does still work
178	with an outdated /etc/netconfig for some time, but you'll get
179	a warning. This warning will be removed in 20030301.
180
18120021202:
182	The recent binutils upgrade marks a kernel flag day on
183	sparc64: modules built with the old binutils will not work
184	with new kernels and vice versa. Mismatches will result in
185	panics.  Make sure your kernel and modules are in sync.
186
18720021029:
188	The value of IPPROTO_DIVERT has changed.  Make sure to keep
189	your kernel, netstat, natd and any third-party DIVERT
190	consumers in sync.
191
19220021024:
193	Old, compatibility slices have been removed in GEOM kernels.
194	This means that you will have to update your /etc/fstab to
195	not use disk devices of the form /dev/ad0a.  Instead, you
196	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
197	partition really is on.  The old device names have gone
198	away, so if you use them anywhere else, you must also adjust
199	those uses.  (This doesn't affect the disks formatted in
200	the ``dangerously-dedicated'' mode.)
201
20220021023:
203	Alphas with kernels from between 20020830 and 20021023 and/or
204	rtld (ld-elf.so.1) older than 20021023 may experience problems
205	with groff while doing a buildworld (kernel: "out of memory",
206	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
207	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
208
209	So, to successfully upgrade your Alpha, you must either
210	upgrade your kernel and rtld first (which might be a bit
211	tricky), or avoid running the bootstrapped groff during the
212	"transitional" buildworld.  To avoid running groff during the
213	transitional upgrade run make buildworld with -DNOMAN,
214	-DNO_SHAREDOCS, and -DNO_LPR.
215
21620020831:
217	gcc has been upgraded to 3.2.  It is not all binary compatible
218	with earlier versions of gcc for c++ programs.  All c++
219	programs and libraries need to be recompiled.
220
221	Also, if you encounter g++ issues, rm /usr/include/g++/* before
222	doing an installworld to make sure that stale files are removed.
223
22420020827:
225	Our /etc/termcap now has all the entries from the XFree86 xterm
226	almost unchanged. This means xterm now supports color by default.
227	If you used TERM=xterm-color in the past you now should use
228	TERM=xterm. (xterm-color will lead to benign warnings).
229
23020020815:
231	A "bug" in gcc(1) that was hiding warning in system headers was
232	fixed.  It's probably time to add -DNO_WERROR to your make line
233	again.
234
23520020729:
236	COPY is being deprecated.  The 20010530 change was reverted, as
237	it causes far more pain than was expected, and to always compare
238	before installing, please use INSTALL="install -C" again.  The
239	-C option is now silently ignored when used with the -d option.
240
24120020702:
242	Problems with libc_r clients like KDE and GNOME have been resolved.
243	There are still some minor problems with some signals but the 
244	system is stable enough for general use again. SMP is less so than UP
245	but each can successfully complete multiple buildworlds.
246	Libkvm needs to be recompiled due to KSE.
247
24820020701:
249	Now would be a bad time to upgrade.  Something in or near the
250	KSE commit totally broke programs using libc_r like KDE and
251	GNOME.
252
25320020511:
254	The k5su utility installed as part of Kerberos 5 is no longer
255	installed with the set-user-ID bit set by default.  Add
256	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
257	with the set-user-ID bit set.
258
25920020510:
260	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
261	Unfortunately our native GDB (at version 4.18) does not understand
262	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
263	generated debugging information for our native GDB.
264
26520020510:
266	Due to the way CVS works, it may not properly update src/contrib/gcc
267	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
268	and then do a cvs update.
269
27020020421:
271	When exec'ing set[ug]id executables, the kernel now ensures that the
272	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
273
27420020404:
275	New sendmail startup scripts have been installed to make it
276	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
277	variable sendmail_enable to "NO" no longer prevents any sendmail
278	daemons from starting.  Instead, either set sendmail_enable to
279	"NONE" or change mta_start_script to a script for starting
280	an alternative MTA.  Setting mta_start_script to "" will
281	also prevent any MTA from being started at boot.
282
28320020403:
284	UCONSOLE is no longer a valid kernel option.
285
28620020315:
287	FreeBSD 5.0 DP-1 was basically branched today.
288
28920020225:
290	Warnings are now errors in the kernel.  Unless you are a developer,
291	you should add -DNO_WERROR to your make line.
292
29320020217:
294	sendmail 8.12.2 has been imported.  The sendmail binary is no
295	longer a set-user-ID root binary and the infrastructure to support
296	command line mail submission has changed.  Be sure to run
297	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
298	and /etc/mail) and read /etc/mail/README for more details.
299
300	Due to the import of sendmail 8.12.2, a new user and group are
301	required in order for sendmail to run as a set-group-ID
302	binary.  A 'make installworld' will use the new user and group
303	to set the owner and group of /var/spool/clientmqueue and will
304	fail if the new user and group do not exist.  The 'smmsp' user
305	and group must be merged from src/etc/group and
306	src/etc/master.passwd before using 'make installworld'.
307	'mergemaster -p' will do this.  You may need to install
308	mergemaster before this will work if you are updating from a
309	very old version of current.  The updating recipe has changed
310	as of this date.
311
31220020112:
313	The preferred configuration method for PAM is now /etc/pam.d/
314	rather than /etc/pam.conf.  If you have an unmodified
315	pam.conf, just delete it after your next mergemaster run.  If
316	you have local modifications, you can use
317	/usr/src/etc/pam.d/convert.pl to incorporate them into your
318	/etc/pam.d.
319
320	Please see the following url for more details:
321http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
32220011229:
323	If anyone here is already using the new rc.conf(5) variable
324	networkfs_types, please note that it has changed
325http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
326
32720011220:
328	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
329	started out its life in the ISDN4BSD project as an offspring
330	from sys/net/if_spppsubr.c, which eventually got a life of its
331	own.  All the accumulated features and bugfixes of the i4b
332	version have now been merged back into the base system's
333	version now.  The only user-visible change resulting from this
334	is that i4b's sppp(4) interfaces are to be managed with
335	spppcontrol(8) again, since ispppcontrol(8) has been retired
336	as well.  (There has never been rc file support for
337	ispppcontrol in -current, but only in -stable.  That will be
338	reverted by the time the changes are MFCed.)
339
34020011215:
341	The fdc(4) driver has been updated and now automatically
342	recognizes media in `standard' formats (like 1440 KB and
343	720 KB for a 3.5" high-density drive) when accessing the
344	default device node (e. g. /dev/fd0).  The old variety of
345	floppy device nodes /dev/fd*.* is no longer present by
346	default, devices can be created (in DEVFS) on demand.  They
347	will need to be customized then for `odd' densities using
348	fdcontrol(8).
349
35020011209:
351	The bugs in procfs' debugging support code have been fixed,
352	and truss(1) now works again.
353
35420011207:
355	Daily security checks have been split out to use the periodic(8)
356	scripts.  Some change in configuration may be necessary.  Please
357	see 
358http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
359	for details.
360
36120011204:
362	sos added VCD/SVCD support to ata driver and that needs the
363	kernel and burncd to be in sync.
364
36520011203:
366	The procfs pseudo-filesystem has now been converted to use the
367	pseudofs framework.  If you have 'options PROCFS' in your
368	kernel config, you'll need to add 'options PSEUDOFS' if it's
369	not there already.
370
371	This change temporarily breaks truss(1); use ktrace(1) instead
372	until the issue has been resolved.
373
37420011202:
375	A security hole in OpenSSH involving `UseLogin yes' has been
376	patched.
377
37820011126:
379	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
380	after this date.  You need to do this only once.
381
38220011103:
383	Most of the awk issues have been resolved.  Some rough
384	edges may be left, but for the most part things should be
385	back to "normal." For CURRENT's usual definition of "normal."
386
38720011030:
388	Awk has been upgraded to the one true awk from bell labs.  Expect
389	choppy waves in the upgrade process.
390
39120011030:
392	The asr driver problem has been resolved.
393
39420011027:
395	Due to changes in other parts of the system, the asr driver
396	now causes the system to panic on boot.  Do not use it pending
397	correction.  Comment it out of any kernel config file that you
398	try to use from this date forward.
399
40020011025:
401	When crossbuilding, use TARGET=xxx where you used to use
402	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
403	unless you are changing both of them.  To cross build pc98 on
404	an alpha, for example, you need to set TARGET=pc98 and
405	TARGET_ARCH=i386.
406
40720011001:
408	The kernel interface that burncd depends on has changed.
409	You must recompile both the kernel and userland applications
410	at the same time.
411
41220010929:
413	When crossbuilding, please set TARGET_ARCH rather than
414	MACHINE_ARCH to indicate the target.  In the future, one will
415	set TARGET_MACHINE where you set MACHINE now.  At the moment,
416	setting MACHINE alone for same MACHINE_ARCH machines works
417	(eg, you can build pc98 on an i386 machine and vice versa).
418
41920010927:
420	Some weird problems result from using ACPI on some machines.
421	To disable ACPI you can add
422		hint.acpi.0.disabled="1"
423	to /boot/loader.conf (or by putting set X=Y at the boot
424	loader "ok" prompt).
425
426	Alternatively, you can remove it from /boot/kernel/acpi.ko
427	or use the MODULES_OVERRIDE function in your kernel config
428	file and not list acpi in that list.
429
43020010924:
431	The buildworld has been fixed.  You may need to install
432	the 4.x compatibility libraries for some old binaries
433	to work.  Add COMPAT4X=true to your /etc/make.conf to
434	get them installed on every installworld, or execute the
435	following to get them installed only once:
436		cd src/lib/compat/compat4x.<arch>
437		make all install
438	You will see ``__stdoutp undefined'' until you do this.
439
44020010919:
441	There's a bug in the world build process.  The cross-tools
442	are build with the NEW headers, but the OLD libc.a.  This
443	leads to all kinds of problems with the new libc.  A temporary
444	workaround is to add
445		CFLAGS="-O -pipe -D_OLD_STDIO"
446	before building world when upgrading from 4.x to current.  This
447	can be removed afterwards.
448
449	A proper fix to the buildworld target is needed.
450
45120010918:
452	Peter has committed his new kthread nfs client/server code.
453	NFS may be unstable after this date.
454
45520010912:
456	KSE has hit the tree.  Lots of things are now different in
457	the kernel.  While a few problems were introduced in the
458	initial commit, most of the major ones have been found and
459	corrected.
460
46120010901:
462	In OLDCARD, CardBus bridges appear to be stable.  The work
463	arounds described in the 20010604 entry are now no longer
464	necessary and will be ignored.  Most insert/remove problems
465	have been rectified around this date.
466
46720010823:
468 	named now runs as user bind and group bind rather than as 
469 	root.  If named_enable is set to YES in /etc/rc.conf, ensure 
470 	that user bind is available in /etc/passwd (using vipw(8)) 
471 	and that group bind is available in /etc/group.  Also make 
472 	sure that user or group bind has read (and not write) 
473 	permission for your name server configuration and that it 
474 	has read and write permission for your slave zone files and 
475 	directory.
476 
477 	If you wish to continue to run named as root (a less secure 
478 	alternative), add a line to /etc/rc.conf saying
479 
480 		named_flags=
481
48220010709:
483	The PAM libraries have had an API upgrade that is beyond
484	the ability of the shared library major number to handle.
485	It is manifested by PAM-using ports dumping core. The
486	solution is to rebuild those ports.
487
48820010628:
489	The kernel compile module has moved from src/sys/compile/FOO
490	to src/sys/${MACHINE}/compile/FOO.
491
49220010625:
493	The pccard modem issue from 20010613 has been corrected.
494	OLDCARD support is still a little weak in -current.  slot 1 is
495	known not to work on some TI based cardbus bridges.  Some
496	cardbus bridges do not properly detect insert/removal events.
497	IRQ configuration needs more safety belts.
498
49920010617:
500	Softupdates problems have been corrected.
501
50220010614:
503	Peter ripped out the linkerset support.  You must, as always,
504	rerun config after you cvsup if you are using the traditional
505	kernel building methods.
506
50720010613:
508	pccard modems may not work with current after 20010604 date.  Some
509	do, others result in panics.  *MAKE*SURE* that you update your
510	config and /etc/rc.conf ala the 20010604 entry, or you will have
511	problems (this issue will be fixed, it just hasn't been yet).
512
51320010613:
514	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
515	use them in current.  You can disable softupdates on all mounted
516	partitions, or remove SOFTUPDATES the kernel config file.
517
51820010612:
519	After Peter's commits to the hints code, people have been noticing
520	that certain devices are attached (or try to) twice.  This is due
521	to having both static hints as well as a /boot/device.hints.  To
522	work around this issue, please use only one or the other mechanism
523	until this bug is fixed.
524
525	Please note that a feature of config is that if you have config
526	file FOO and FOO.hints, it automatically adds FOO.hints to the
527	hints.c file, whether you want it to or not.
528
52920010610:
530	Locale names have changed to match other systems better.
531
53220010604:
533	pccard support for pci cards has been committed.  You must change
534	your /etc/pccard.conf irq lines.  It must match the irq used by
535	pcic device.  Interrupt storms may result if you fail to do this.
536	Interrupt storms look a lot like a hang.
537
538	You must also install a new pccardd, otherwise you will get an
539	interrupt storm at card reset time (just after it tells you what
540	it is).
541
542	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
543	not to ask the kernel if the interrupt is really free or not before
544	using it.  You can either change the /etc/pccard.conf irq lines to
545	match pcic, or add "-i X" to the pccardd_flags.
546
54720010530:
548	INSTALL=install -C is being deprecated.  If you want to do this,
549	use COPY=-C instead.  The former method will be supported for only
550	a limited time.  If you see
551
552install: warning: the -d and -C options may not be specified together
553
554	in your makeworld, then you need to migrate towards using
555	COPY=-C.
556
55720010525:
558	It appears that vm is now stable enough to use again.  However,
559	there may be other problems, so caution is still urged.  alpha
560	definitely is in bad shape.
561
56220010521:
563	Minor repo damage has happened.  This may cause problems
564	with cvsup of ports.  If you get errors, please see
565	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
566	at the bottom for details on a workaround.  The error message
567	is
568Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
569
57020010520:
571	Vm and/or swapping are busted on -current.  Please be patient.
572
57320010519:
574	pccard has had much reorganizational work done to it over
575	the past few days.  Everything should still work, but if
576	not, please contact imp@freebsd.org.
577
57820010517:
579	ata ioctl changed.  Make sure to recompile both kernel and
580	userland at the same time.
581
58220010517:
583	New ncurses imported.
584
58520010512:
586	DEVFS is now opt out, not opt in.  Barring major problems, this
587	will be the only way to go starting July 1.
588
58920010504:
590	OpenSSH has been updated to 2.9.  Some defaults are different,
591	including RhostsRSAAuthentication, which changes from yes to no.
592
59320010502:
594	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
595
59620010501:
597	Building perl was broken at 02:25:25 PDT.
598
59920010430:
600	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
601	go back in the water.
602
60320010429:
604	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
605	this date, but before the correction date.
606
60720010423:
608	old fsck and new kernel interactions appear to have been fixed.
609
61020010411:
611	fsck and the kernel were changed to handle some optimizations
612	to directory layout.  This breaks backward compatibility.
613	Update only if you understand that you must not use the old
614	fsck with the new kernel ever.
615
61620010330:
617	fsck has changed the meaning of the pass column in /etc/fstab.
618	Please see the cvs commit to fsck.8 or the fsck.8 man page for
619	details.  It is unclear if changes to /etc/fstab are necessary.
620
62120010319:
622	portmap had changed name to rpcbind for maximum POLA in your
623	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
624	other rpc based programs that rely on portmapper will not work
625	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
626
62720010315:
628	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
629	and ATA_ENABLE_TAGS are no longer kernel options.  They have
630	been replaced by tunables.  See ata.4 for details.
631
63220010312:
633	The fxp driver was converted to use miibus.  If you compile
634	fxp into your kernel statically, you will need to add miibus.
635
63620010312:
637	The wi device now defaults to BSS (infrastructure) mode
638	instead of ad-hoc.
639
64020010310:
641	/dev/urandom should be a symbolic link to /dev/random now.
642	Users of current not using DEVFS need to run MAKEDEV std.
643	ssh might not work if you don't.
644
64520010303:
646	The ed driver has been updated.  It now allows mii attachments,
647	which means that you must include the miibus in your kernel if
648	you use the ed driver.
649
65020010220:
651	The problems with libc have been corrected.  It is now mostly
652	safe to go back into the water.
653
65420010211:
655	The size of FILE was changed.  This breaks upgrading.  If
656	you must upgrade, be prepared for pain.  It also breaks almost
657	all binaries that you've compiled on -current.  You are warned
658	that before upgrading would be a good time to do a level 0
659	dump of your system.  No, really, I mean it this time.
660
661	To get to the new system, you'll need to use the following
662	workaround.  Hopefully this can be sorted out so that we
663	don't have to move this to the updating section.
664
665	To get around the installworld problem, do:
666		# cd /usr/src/usr.bin/sed
667		# make install
668		# cd /usr/src
669		# make installworld
670	If that doesn't work, then try:
671		# make -k installworld
672		# make installworld
673
67420010207:
675	DEVFS is now the default.  If you use vinum, make sure that you
676	do not include devfs in your kernel as problems result.
677
67820010205:
679	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
680	Remove them from your config.
681
68220010122:
683	****************************** WARNING ******************************
684			buildkernel has been changed slightly
685	****************************** WARNING ******************************
686	KERNCONF replaces the variable KERNEL for buildkernel.  You
687	should update your scripts and make.conf accordingly.
688
68920010119:
690	config has changed to allow DEV_FOO as a replacement for NFOO.
691	This requires a new config to build correctly.
692
69320010116:
694	The kernel option I386_CPU is now mutually exclusive with the
695	other cpu types. If you have an i386 system, be sure that it
696	only had this line.  Remove it for all other configurations.
697
69820010110:
699	Changes to the kernel require it and burncd be in sync.
700
70120010102:
702	Everyone who has hw.sndunit set to something in
703	/etc/sysctl.conf, it is now hw.snd.unit.
704
70520010101:
706	ex and vi were broken by some changes to sys/queue.h.  If you
707	have a bad vi, you will see make buildworld fail with a core
708	dump while building termcap.  You can work around this problem
709	by adding -k to your make buildworld.  This will cause the
710	build to complete and install a new vi.  Once that's done, you
711	can rebuild again without the -k to pick up anything that
712	might have been ignored by the -k option.
713
714	Others have suggested that you can just rebuild libc if your
715	vi/ex is dynamically linked, but I've not received any reports
716	of this working.
717
71820001228:
719	There have been some changes to libcrypt in -current.  The
720	libscrypt/libdescrypt symlink silliness is gone and the installed
721	libcrypt is fully functional.  Be aware of this.
722
72320001218:
724	Linksys Fast Ethernet PCCARD cards supported by the ed driver
725	now require the addition of flag 0x80000 to their config line
726	in pccard.conf(5).  This flag is not optional.  These Linksys
727	cards will not be recognized without it.
728
72920001205:
730	Important new FreeBSD-version stuff: PAM support has been worked
731	in, partially from the "Unix" OpenSSH version.  This requires
732	adding the following in pam.conf:
733  
734	sshd    auth    sufficient      pam_skey.so
735	sshd    auth    required        pam_unix.so         try_first_pass
736	sshd    session required        pam_permit.so
737
73820001031:
739	cvs updated to 1.11.
740
74120001020:
742	The random device needs more entropy, so you need to make sure
743	that you've run mergemaster to get a /etc/rc which will seed
744	/dev/random.  If you don't and the system hangs after ldconfig,
745	then banging on the keyboard randomly until it unhangs is one
746	workaround.
747
74820001010:
749	****************************** WARNING ******************************
750				Sendmail has been updated.
751	****************************** WARNING ******************************
752	o mail.local(8) is no longer installed as a set-user-id binary.
753	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
754	  is set.
755	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
756	  commands.
757	o Now using sendmail's version of vacation(1).
758	o The sendmail cf building tools (contrib/sendmail/cf) are installed
759	  in /usr/share/sendmail/cf.
760	o sendmail.cw changed to local-host-names
761
762	More details can be found at
763		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
764
76520001009:
766	The ports tree's new layout is in place.  Be sure to update
767	your entire ports tree, or you will have problems.
768
76920001006:
770	The perl build procedure no longer installs miniperl, nor uses
771	the installed miniperl.  It is recommended that you delete
772	/usr/bin/miniperl.
773
77420001005:
775	This weekend the ports tree will be updated to a new layout.
776	It will be in an inconsistent state until noted in the UPDATING
777	file, or with asami-san's message to the relevant mailing
778	lists.  With this new layout, you'll need to update the whole
779	tree for anything to work.
780
78120000928:
782	There was a change in the passwd format.  Need more information.
783
78420000916:
785	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
786	place.  Please update boot loader (not the boot blocks) at the
787	same time as your kernel.
788
78920000914:
790	The new pmtimer device is necessary for laptops.  Failure to
791	include the device will cause suspended laptops losing time
792	when they resume.  Include
793		device		pmtimer
794	in your config file and
795		hint.pmtimer.0.at="isa"
796	to your /boot/device.hints file.
797
79820000911:
799	The random device has been turned into a (pseudo-)device,
800	rather than an option. The supplied kernel config files have
801	been updated. You will need to do something similar in your
802	own kernel config file.
803	Remove:
804		options		RANDOMDEV
805	Add:
806		device		random
807	If you prefer to load the loadable module, you need to do
808	nothing.
809
81020000909:
811	The random device module has been renamed from randomdev.ko to
812	random.ko. You will need to edit your /boot/loader.conf to
813	reflect this if you load this module at boot time.
814	The line should read:
815		random_load="YES"
816
81720000907:
818	The SMPNG commit has happened.  It should work, but if it
819	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
820	to be a variety of minor issues.  Please see 20000905 to make
821	sure you don't have model loading problems which might at
822	first blush appear related to SMP.
823
82420000906:
825	nsswitch has been imported from NetBSD.  Among other things,
826	this means that /etc/host.conf is no longer used.  See
827	nsswitch.conf(5) instead.  Note that at boot time rc.network
828	will attempt to produce a new nsswitch.conf file for you if you
829	don't have one, and you have host.conf.
830
83120000905:
832	The ucred structure changed size.  This breaks the interface
833	that mountd uses.  Trying to use an older mountd with a newer
834	kernel guarantees a panic.  This means that you need to use
835	kernels newer than today only with matching mountd, but you
836	needed to do that anyway with the boot loader changes.
837
83820000905:
839	The boot loader has been updated.  The new default kernel is
840	now /boot/kernel/kernel.ko.  The new default module location
841	is /boot/kernel.
842
843	You *MUST* upgrade your boot loader and kernel at the same time.
844	The easiest way to do this is to do the buildworld/buildkernel/
845	installkernel/installworld dance.
846
847	Furthermore, you are urged to delete your old /modules directory
848	before booting the new kernel, since kldload will find stale
849	modules in that directory instead of finding them in the correct
850	path, /boot/kernel.  The most common complaint that this cures
851	is that the linux module crashes your machine after the update.
852
853	if [ ! -d /boot/kernel.old ]; then
854		mv /modules.old /boot/kernel.old
855		chflags noschg /kernel.old
856		mv /kernel.old /boot/kernel.old/kernel.ko
857		chflags schg /boot/kernel.old/kernel.ko
858	fi
859
86020000904:
861	A new issue with the sendmail upgrade has come to light.
862	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
863	incorrectly install the default aliases in /etc/mail rather than
864	move the old one from /etc.  So you'll need to manually move the
865	file, create a symbolic link, remove the old /etc/aliases.db and
866	run newaliases.  For safety sake, you should stop sendmail
867	while doing this and run the upgrade when locally sourced email
868	is not likely to be generated.
869
87020000825:
871	/boot/device.hints is now required for installkernel to
872	succeed.  You should copy GENERIC.hints for your architecture
873	into /boot/device.hints.  If and only if you compile hints
874	into your kernel, then this file may be empty.  Please note,
875	if you have an empty or missing /boot/device.hints file and
876	you neglected to compile hints into your kernel, no boot
877	messages will appear after the boot loader tries to start the
878	kernel.
879
88020000821:
881	If you do NOT have ``options RANDOMDEV'' in your kernel and
882	you DO want the random device then add randomdev_load="YES" to
883	/boot/loader.conf.
884
88520000812:
886	suidperl is now always built and installed on the system, but
887	with permissions of 511.  If you have applications that use
888	this program, you are now required to add ENABLE_SUIDPERL=true
889	to /etc/make.conf.  If you forget to do this,
890		chmod 4511 /usr/bin/suidperl
891	will fix this until the next build.
892
89320000812:
894	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
895	visible changes that may immediately affect your configuration
896	include:
897	- New default file locations from src/contrib/sendmail/cf/README
898	- newaliases limited to root and trusted users
899	- MSA port (587) turned on by default
900	- New queue file naming system so can't go from 8.11 -> 8.9
901	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
902	- FEATURE(`nullclient') is more full featured
903	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
904	- mail.local FreeBSD-only -b option changed to -B
905	- See src/contrib/sendmail/RELEASE_NOTES for more info
906
90720000810:
908	suidperl (aka sperl) is no longer build by default.  You must
909	specifically define BUILD_SUIDPERL to "true" for it to be build.
910	Furthermore, we recommend that you remove /usr/bin/sperl* and
911	/usr/bin/suidperl files from your system unless you have a
912	specific use for it.
913
91420000729:
915	Networking defaults have been tightened.  Anybody upgrading
916	/etc/defaults/rc.conf needs to add the following lines to
917	/etc/rc.conf if they want to have the same setup
918	afterwards (unless the variables already are set, of course):
919		# Enable network daemons for user convenience.
920		inetd_enable="YES"
921		portmap_enable="YES"
922		sendmail_enable="YES"
923
92420000728:
925	If you have null_load="YES" in your /boot/loader.conf, you
926	will need to change that to nullfs_load="YES".
927
92820000728:
929	The "installkernel" target has changed slightly. Now even if
930	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
931	it will install the MYKERNEL file (built with the buildkernel
932	target) as /kernel rather than /MYKERNEL. Those who have
933	updated their /boot/loader.conf files to point to /MYKERNEL
934	should remove that entry or perform manual rename of /kernel
935	to /MYKERNEL.
936
93720000711:
938	If you use CVSUP or CTM to get CVS trees, AND you used to get 
939	the old crypto files from internat.freebsd.org AND you check
940	out files from the CVS tree with the cvs command, please read
941		http://people.freebsd.org/~imp/internat.txt
942	for details on potential problems that you might have and how
943	to get around them.
944
945	If you are merely a mirror, or don't answer yes to each of the
946	clauses above, you needn't worry.
947
94820000711:
949	/etc/security has been updated to print the inode number of
950	setuid programs that have changed.  You will see a large spike
951	in the number of changed programs the first time when you run
952	mergemaster to get a new /etc/security.
953
95420000710:
955	/dev/random now has good entropy collection (from the keyboard
956	and sysmouse drivers). Please ensure that either `options
957	RANDOMDEV' is present in your kernel config file or that
958	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
959	not have the /dev/random driver, OpenSSL (and consequently
960	lots of crypto tools (like SSH)) will fail with strange
961	errors. (see below, 20000624).
962
963	FreeBSD-current is safe again to run Crypto.
964
96520000709:
966	phk made the malloc default options AJ.  This may slow things
967	down and uncover other latent bugs in the code.  If you need to
968	run at full speed, you can disable this by doing the following:
969		ln -s aj /etc/malloc.conf
970
97120000706:
972	libftpio's version was accidentally bumped a few days ago.  This
973	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
974	before doing your next buildworld/installworld pair.  It certainly
975	won't hurt to remove it before the update procedure.  It will
976	break fetch until a new one is built, but ftp can be used in the
977	interim if needed.
978
97920000705:
980	The crypto packages have changed for the cvsup.  This has been done
981	in a backward compatible way, but the old packages will go away at
982	some point in the future.  Look at /usr/share/examples/cvsup for
983	details.
984
98520000704:
986	With the new sys/modules/sound/drivers/*, you will need to
987	set SYSDIR until you do an installworld after July 7th.
988
98920000704:
990	rc.shutdown and rc will now call the rc.d scripts with start
991	or stop.  This may cause some harmless warnings from older
992	rc.d scripts that haven't been updated.
993
99420000630:
995	The libfetch based version of fetch has gone into the tree.
996	Minor problems may result on some of the less popular sites,
997	which should be reported to des@freebsd.org.
998
99920000625:
1000	From approximately this date forward, one must have the crypto
1001	system installed in order to build the system and kernel.
1002	While not technically strictly true, one should treat it as
1003	required and grab the crypto bits.  If you are grabbing CVS
1004	trees, src-all and cvs-crypto should be treated as if they
1005	were required.  You should check with the latest collections
1006	to make sure that these haven't changed.
1007
100820000624:
1009	Mark Murray just committed the first parts of a cleanup of
1010	/dev/zero, et al.  This is also cleaning up /dev/random.
1011	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1012	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
1013	until Mark can merge in the fixes to this work in progress.
1014	openssh and openssl should not be used to generate keys from this
1015	date to the completion of the work.
1016
1017	If you must operate at this reduced level of security, add '
1018	options RANDOMDEV' to your kernel or modload the randomdev
1019	module.  You may also need to copy a new MAKEDEV to /dev and
1020	recreate the random and urandom devices.
1021
102220000622:
1023	The license on the softupdates is now a standard 2 clause
1024	BSD license.  You may need to remove your symbolic links
1025	that used to be required when updating.
1026
102720000621:
1028	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1029	the config file update procedure.
1030		http://people.freebsd.org/~imp/config-upd.html
1031	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
1032	isn't buildable.  However, you can generate a LINT file:
1033		cd /sys/<ARCH>/conf && make LINT
1034
103520000620:
1036	Binutils 2.10 have hit the tree, or will shortly.  As soon
1037	as they do, the problem noted in 20000522 will be resolved and
1038	that workaround will no longer be required.
1039
104020000615:
1041	phk removed the compatibility creation of wd devices in the
1042	ad driver.  If you haven't done so already, you must update
1043	your fstab, etc to use the ad devices instead of the wd
1044	devices.
1045
1046	In addition, you'll need to update your boot blocks to a
1047	more modern version, if you haven't already done so.  Modern
1048	here means 4.0 release or newer (although older releases
1049	may work).
1050
105120000612:
1052	Peter took an axe to config(8).  Be sure that you read his mail
1053	on the topic before even thinking about updating.  You will
1054	need to create a /boot/device.hints or add a hints directive
1055	to your config file to compile them in statically.  The format
1056	of the config file has changed as well.  Please see GENERIC or
1057	NEWCARD for examples of the new format.
1058
1059	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
1060	says that it has been fixed, assume that must use the hints mechanism
1061	in the loader if you need to use a machine with very old ISA cards
1062	in it.
1063
106420000522:
1065	A new set of binutils went into the tree today.  Anybody
1066	building a kernel after this point is advised that they need
1067	to rebuild their binutils (or better yet do a
1068	buildworld/installworld) before building a new kernel.
1069
1070	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1071	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1072	is recommended that you don't set this option until the problem
1073	is resolved.
1074
107520000513:
1076	The ethernet drivers were all updated to clean up the BPF handling.
1077
107820000510:
1079	The problems with boot blocks on the alphas have been corrected.
1080	This will require some care in updating alphas.  A new libstand
1081	is requires for the boot blocks to build properly.
1082
108320000503:
1084	Recompile all kld modules.  Proper version dependency info
1085	is now available.
1086
108720000502:
1088	Modules have been disconnected from the buildworld tree and 
1089	connected to the kernel building instead.
1090
109120000427:
1092	You may need to build gperf
1093		cd /usr/src/gnu/usr.bin/gperf && make depend all install
1094	when upgrading from 4.0 -> current.  The build system now uses
1095	an option only in -current.
1096
109720000417:
1098	The method that we brand ELF binaries has changed to be more
1099	acceptable to the binutils maintainers.  You will need to
1100	rebrand your ELF binaries that aren't native.  One problem
1101	binary is the Linux ldconfig.  After your make world, but
1102	before you reboot, you'll need to issue:
1103		brandelf -t Linux /compat/linux/sbin/ldconfig
1104	if you have Linux compatibility enabled on your machine.
1105
110620000320:
1107	If you have really bad/marginal IDE drives, you may find they
1108	don't work well.  Use pio mode instead.  The easiest way to
1109	cope if you have a problem combination is to add:
1110		/sbin/sysctl hw.ata.ata_dma=0
1111	to the start of /etc/rc.conf.
1112
111320000319:
1114	The ISA and PCI compatibility shims have been connected to the
1115	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1116	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1117	include the appropriate option in your kernel config.  Drivers
1118	using the shims should be updated or they won't ship with
1119	5.0-RELEASE, targeted for 2001.
1120
112120000318:
1122	We've entered the traditional post release dumping party.
1123	Large kernel changes are being committed and are in the
1124	works.  It is important to keep the systems' klds and kernel
1125	in sync as kernel interfaces and structures are changing.
1126	Before reporting kernel panics, make sure that all modules
1127	that you are loading are up to date.
1128
112920000315:
1130	If you are upgrading from an older version of FreeBSD, you
1131	need to update your boot blocks as well.  'disklabel -B ad0'
1132	will do the trick.  This isn't critical until you remove your
1133	wd device entries in /dev, at which point your system will not
1134	boot.
1135
113620000315:
1137	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
1138	to upgrade to 4.0 from 3.x.
1139
1140COMMON ITEMS:
1141
1142	General Notes
1143	-------------
1144	Avoid using make -j when upgrading.  From time to time in the
1145	past there have been problems using -j with buildworld and/or
1146	installworld.  This is especially true when upgrading between
1147	"distant" versions (eg one that cross a major release boundary
1148	or several minor releases, or when several months have passed
1149	on the -current branch).
1150
1151	Sometimes, obscure build problems are the result of environment
1152	poisoning.  This can happen because the make utility reads its
1153	environment when searching for values for global variables.
1154	To run your build attempts in an "environmental clean room",
1155	prefix all make commands with 'env -i '.  See the env(1) manual
1156	page for more details.
1157
1158	To build a kernel
1159	-----------------
1160	If you are updating from a prior version of FreeBSD (even one just
1161	a few days old), you should follow this procedure. With a
1162	/usr/obj tree with a fresh buildworld,
1163	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1164	make installkernel KERNCONF=YOUR_KERNEL_HERE
1165
1166	To just build a kernel when you know that it won't mess you up
1167	--------------------------------------------------------------
1168	cd src/sys/{i386,alpha}/conf
1169	config KERNEL_NAME_HERE
1170	cd ../../compile/KERNEL_NAME_HERE
1171	make depend
1172	make
1173	make install	
1174
1175	If this fails, go to the "To build a kernel" section.
1176
1177	To rebuild everything and install it on the current system.
1178	-----------------------------------------------------------
1179	# Note: sometimes if you are running current you gotta do more than
1180	# is listed here if you are upgrading from a really old current.
1181
1182	<make sure you have good level 0 dumps>
1183	<maybe fix /etc/fstab>				[7]
1184	make buildworld
1185	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1186	make installkernel KERNCONF=YOUR_KERNEL_HERE
1187							[1]
1188	<reboot in single user>				[3]
1189	mergemaster -p					[5]
1190	make installworld
1191	mergemaster					[4]
1192	<reboot>
1193
1194
1195	To cross-install current onto a separate partition
1196	--------------------------------------------------
1197	# In this approach we use a separate partition to hold
1198	# current's root, 'usr', and 'var' directories.   A partition
1199	# holding "/", "/usr" and "/var" should be about 2GB in
1200	# size.
1201
1202	<make sure you have good level 0 dumps>
1203	<boot into -stable>
1204	make buildworld
1205	<maybe newfs current's root partition>
1206	<mount current's root partition on directory ${CURRENT_ROOT}>
1207	make installworld DESTDIR=${CURRENT_ROOT}
1208	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1209	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1210		${CURRENT_ROOT}/boot/device.hints	# as needed
1211	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1212	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1213	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1214	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1215	<reboot into current>
1216	<do a "native" rebuild/install as described in the previous section>
1217	<maybe install compatibility libraries from /usr/src/lib/compat>
1218 	<reboot>	
1219
1220
1221	To upgrade in-place from 4.x-stable to current 
1222	----------------------------------------------
1223	# 5.x uses more space than 4.x.  Also, the location of kernel
1224	# modules has changed.  If you are installing 5.0 onto a 4.x
1225	# system, you'll need about 30MB of free disk space on your /
1226	# partition.  If you have less than this, you may encounter difficult
1227	# to back out of problems with this procedure.  If /tmp is on
1228	# the / partition, you may want to completely remove all its content
1229	# before upgrading, as this can be a common source of shortage of
1230	# space on /.
1231	
1232	<make sure you have good level 0 dumps>
1233	<maybe fix /etc/fstab>				[7]
1234	make buildworld					[9]
1235	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1236	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1237	make installkernel KERNCONF=YOUR_KERNEL_HERE
1238	cd src/sys/boot ; make install			[6]
1239							[1]
1240	<reboot in single user>				[3]
1241	mergemaster -p					[5]
1242	rm -rf /usr/include/g++
1243	make installworld
1244	mergemaster					[4]
1245	<reboot>
1246
1247	Make sure that you've read the UPDATING file to understand the
1248	tweaks to various things you need.  At this point in the life
1249	cycle of current, things change often and you are on your own
1250	to cope.  The defaults can also change, so please read ALL of
1251	the UPDATING entries.
1252
1253	Also, if you are tracking -current, you must be subscribed to
1254	freebsd-current@freebsd.org.  Make sure that before you update
1255	your sources that you have read and understood all the recent
1256	messages there.  If in doubt, please track -stable which has
1257	much fewer pitfalls.
1258
1259	[1] If you have third party modules, such as vmware, you
1260	should disable them at this point so they don't crash your
1261	system on reboot.
1262
1263	[2] If you have legacy ISA devices, you may need to create
1264	your own device.hints to reflect your unique hardware
1265	configuration.
1266
1267	[3] From the bootblocks, boot -s, and then do
1268		fsck -p
1269		mount -u /
1270		mount -a
1271		cd /usr/src
1272		adjkerntz -i		# if CMOS is wall time
1273	Also, when doing a major release upgrade, it is required that
1274	you boot into single user mode to do the installworld.
1275	For the 4.x -> 5.0 upgrade, you will also see many messages about
1276	needing to recompile your userland.  These are harmless and can
1277	be ignored while you proceed to the next step.
1278
1279	[4] Note: This step is non-optional.  Failure to do this step
1280	can result in a significant reduction in the functionality of the
1281	system.  Attempting to do it by hand is not recommended and those
1282	that pursue this avenue should read this file carefully, as well
1283	as the archives of freebsd-current and freebsd-hackers mailing lists
1284	for potential gotchas.
1285
1286	[5] Usually this step is a noop.  However, from time to time
1287	you may need to do this if you get unknown user in the following
1288	step.  It never hurts to do it all the time.  You may need to
1289	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1290	install) after the buildworld before this step if you last updated
1291	from current before 20020224 or from -stable before 20020408.
1292
1293	[6] 4.x boot loader can be used to boot a 5.x system, however
1294	it is difficult to do that at best.  If you wish to try, then
1295	you should interrupt the boot and at the ok prompt type:
1296		ok unload
1297		ok boot /boot/kernel/kernel
1298	If this fails to work, you must install a new boot loader as
1299	described here.
1300
1301	[7] Before you upgrade, please make sure that you are not using
1302	compatibility slices.  These are device names of the form, on i386
1303	and other architectures that use MBR slicing, /dev/ad0a without the
1304	actual slice name.  Chances are excellent that these will break.
1305	You generally must update these entries to use the post FreeBSD
1306	2.x form of /dev/ad0s1a.
1307
1308	[8] In order to have a kernel that can run the 4.x binaries
1309	needed to do an installworld, you must include the COMPAT_FREEBSD4
1310	option in your kernel.  Failure to do so may leave you with a system
1311	that is hard to boot to recover.
1312
1313	[9] When checking out sources, you must include the -P flag to have
1314	cvs prune empty directories.
1315FORMAT:
1316
1317This file contains a list, in reverse chronological order, of major
1318breakages in tracking -current.  Not all things will be listed here,
1319and it only starts on March 15, 2000.  Updating files can found in
1320previous releases if your system is older than this.
1321
1322Copyright information:
1323
1324Copyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1325
1326Redistribution, publication, translation and use, with or without
1327modification, in full or in part, in any form or format of this
1328document are permitted without further permission from the author.
1329
1330THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1331IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1332WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1333DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1334INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1335(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1336SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1337HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1338STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1339IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1340POSSIBILITY OF SUCH DAMAGE.
1341
1342If you find this document useful, and you want to, you may buy the
1343author a beer.
1344
1345Contact Warner Losh if you have any questions about your use of
1346this document.
1347
1348$FreeBSD: head/UPDATING 119413 2003-08-24 16:46:03Z sos $
1349