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