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