UPDATING revision 109389
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
2020030115:
21	A new version of the wi driver has been imported into the tree.
22	One now must have device wlan in the config file for it to operate
23	properly.
24
2520021222:
26 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
27 	used an incompatible form of ABI for returning structures and unions
28 	which FreeBSD's GCC maintainers were not aware of relative to previous
29 	versions of FreeBSD.  We have gone back to the ABI for now, and any
30 	code compiled which is required to interoperate with other code (not
31 	built at the same time) returning structs or unions should be 
32	rebuilt.
33
3420021216:
35	A name change in /etc/netconfig has been reverted to stay
36	compatible with with suns TIRPC and also with NetBSD. You need
37	to run mergemaster after make world. A new libc does still work
38	with an outdated /etc/netconfig for some time, but you'll get
39	a warning. This warning will be removed in 20030301.
40
4120021202:
42	The recent binutils upgrade marks a kernel flag day on
43	sparc64: modules built with the old binutils will not work
44	with new kernels and vice versa. Mismatches will result in
45	panics.  Make sure your kernel and modules are in sync.
46
4720021029:
48	The value of IPPROTO_DIVERT has changed.  Make sure to keep
49	your kernel, netstat, natd and any third-party DIVERT
50	consumers in sync.
51
5220021024:
53	Old, compatibility slices have been removed in GEOM kernels.  This
54	means that you will have to update your /etc/fstab to not use
55	disk devices of the form /dev/ad0a.  Instead, you now must
56	specify /dev/ad0s1a, or whatever slice your FreeBSD partition
57	really is on.  The old device names have gone away, so if you
58	use them anywhere else, you must also adjust those uses.
59
6020021023:
61	Alphas with kernels from between 20020830 and 20021023 and/or
62	rtld (ld-elf.so.1) older than 20021023 may experience problems
63	with groff while doing a buildworld (kernel: "out of memory",
64	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
65	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
66
67	So, to successfully upgrade your Alpha, you must either
68	upgrade your kernel and rtld first (which might be a bit
69	tricky), or avoid running the bootstrapped groff during the
70	"transitional" buildworld.  To avoid running groff during the
71	transitional upgrade run make buildworld with -DNOMAN,
72	-DNO_SHAREDOCS, and -DNO_LPR.
73
7420020831:
75	gcc has been upgraded to 3.2.  It is not all binary compatible
76	with earlier versions of gcc for c++ programs.  All c++
77	programs and libraries need to be recompiled.
78
79	Also, if you encounter g++ issues, rm /usr/include/g++/* before
80	doing an installworld to make sure that stale files are removed.
81
8220020827:
83	Our /etc/termcap now has all the entries from the XFree86 xterm
84	almost unchanged. This means xterm now supports color by default.
85	If you used TERM=xterm-color in the past you now should use
86	TERM=xterm. (xterm-color will lead to benign warnings).
87
8820020815:
89	A "bug" in gcc(1) that was hiding warning in system headers was
90	fixed.  It's probably time to add -DNO_WERROR to your make line
91	again.
92
9320020729:
94	COPY is being deprecated.  The 20010530 change was reverted, as
95	it causes far more pain than was expected, and to always compare
96	before installing, please use INSTALL="install -C" again.  The
97	-C option is now silently ignored when used with the -d option.
98
9920020702:
100	Problems with libc_r clients like KDE and GNOME have been resolved.
101	There are still some minor problems with some signals but the 
102	system is stable enough for general use again. SMP is less so than UP
103	but each can successfully complete multiple buildworlds.
104	Libkvm needs to be recompiled due to KSE.
105
10620020701:
107	Now would be a bad time to upgrade.  Something in or near the
108	KSE commit totally broke programs using libc_r like KDE and
109	GNOME.
110
11120020511:
112	The k5su utility installed as part of Kerberos 5 is no longer
113	installed with the set-user-ID bit set by default.  Add
114	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
115	with the set-user-ID bit set.
116
11720020510:
118	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
119	Unfortunately our native GDB (at version 4.18) does not understand
120	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
121	generated debugging information for our native GDB.
122
12320020510:
124	Due to the way CVS works, it may not properly update src/contrib/gcc
125	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
126	and then do a cvs update.
127
12820020421:
129	When exec'ing set[ug]id executables, the kernel now ensures that the
130	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
131
13220020404:
133	New sendmail startup scripts have been installed to make it
134	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
135	variable sendmail_enable to "NO" no longer prevents any sendmail
136	daemons from starting.  Instead, either set sendmail_enable to
137	"NONE" or change mta_start_script to a script for starting
138	an alternative MTA.  Setting mta_start_script to "" will
139	also prevent any MTA from being started at boot.
140
14120020403:
142	UCONSOLE is no longer a valid kernel option.
143
14420020315:
145	FreeBSD 5.0 DP-1 was basically branched today.
146
14720020225:
148	Warnings are now errors in the kernel.  Unless you are a developer,
149	you should add -DNO_WERROR to your make line.
150
15120020217:
152	sendmail 8.12.2 has been imported.  The sendmail binary is no
153	longer a set-user-ID root binary and the infrastructure to support
154	command line mail submission has changed.  Be sure to run
155	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
156	and /etc/mail) and read /etc/mail/README for more details.
157
158	Due to the import of sendmail 8.12.2, a new user and group are
159	required in order for sendmail to run as a set-group-ID
160	binary.  A 'make installworld' will use the new user and group
161	to set the owner and group of /var/spool/clientmqueue and will
162	fail if the new user and group do not exist.  The 'smmsp' user
163	and group must be merged from src/etc/group and
164	src/etc/master.passwd before using 'make installworld'.
165	'mergemaster -p' will do this.  You may need to install
166	mergemaster before this will work if you are updating from a
167	very old version of current.  The updating recipe has changed
168	as of this date.
169
17020020112:
171	The preferred configuration method for PAM is now /etc/pam.d/
172	rather than /etc/pam.conf.  If you have an unmodified
173	pam.conf, just delete it after your next mergemaster run.  If
174	you have local modifications, you can use
175	/usr/src/etc/pam.d/convert.pl to incorporate them into your
176	/etc/pam.d.
177
178	Please see the following url for more details:
179http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
18020011229:
181	If anyone here is already using the new rc.conf(5) variable
182	networkfs_types, please note that it has changed
183http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
184
18520011220:
186	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
187	started out its life in the ISDN4BSD project as an offspring
188	from sys/net/if_spppsubr.c, which eventually got a life of its
189	own.  All the accumulated features and bugfixes of the i4b
190	version have now been merged back into the base system's
191	version now.  The only user-visible change resulting from this
192	is that i4b's sppp(4) interfaces are to be managed with
193	spppcontrol(8) again, since ispppcontrol(8) has been retired
194	as well.  (There has never been rc file support for
195	ispppcontrol in -current, but only in -stable.  That will be
196	reverted by the time the changes are MFCed.)
197
19820011215:
199	The fdc(4) driver has been updated and now automatically
200	recognizes media in `standard' formats (like 1440 KB and
201	720 KB for a 3.5" high-density drive) when accessing the
202	default device node (e. g. /dev/fd0).  The old variety of
203	floppy device nodes /dev/fd*.* is no longer present by
204	default, devices can be created (in DEVFS) on demand.  They
205	will need to be customized then for `odd' densities using
206	fdcontrol(8).
207
20820011209:
209	The bugs in procfs' debugging support code have been fixed,
210	and truss(1) now works again.
211
21220011207:
213	Daily security checks have been split out to use the periodic(8)
214	scripts.  Some change in configuration may be necessary.  Please
215	see 
216http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
217	for details.
218
21920011204:
220	sos added VCD/SVCD support to ata driver and that needs the
221	kernel and burncd to be in sync.
222
22320011203:
224	The procfs pseudo-filesystem has now been converted to use the
225	pseudofs framework.  If you have 'options PROCFS' in your
226	kernel config, you'll need to add 'options PSEUDOFS' if it's
227	not there already.
228
229	This change temporarily breaks truss(1); use ktrace(1) instead
230	until the issue has been resolved.
231
23220011202:
233	A security hole in OpenSSH involving `UseLogin yes' has been
234	patched.
235
23620011126:
237	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
238	after this date.  You need to do this only once.
239
24020011103:
241	Most of the awk issues have been resolved.  Some rough
242	edges may be left, but for the most part things should be
243	back to "normal." For CURRENT's usual definition of "normal."
244
24520011030:
246	Awk has been upgraded to the one true awk from bell labs.  Expect
247	choppy waves in the upgrade process.
248
24920011030:
250	The asr driver problem has been resolved.
251
25220011027:
253	Due to changes in other parts of the system, the asr driver
254	now causes the system to panic on boot.  Do not use it pending
255	correction.  Comment it out of any kernel config file that you
256	try to use from this date forward.
257
25820011025:
259	When crossbuilding, use TARGET=xxx where you used to use
260	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
261	unless you are changing both of them.  To cross build pc98 on
262	an alpha, for example, you need to set TARGET=pc98 and
263	TARGET_ARCH=i386.
264
26520011001:
266	The kernel interface that burncd depends on has changed.
267	You must recompile both the kernel and userland applications
268	at the same time.
269
27020010929:
271	When crossbuilding, please set TARGET_ARCH rather than
272	MACHINE_ARCH to indicate the target.  In the future, one will
273	set TARGET_MACHINE where you set MACHINE now.  At the moment,
274	setting MACHINE alone for same MACHINE_ARCH machines works
275	(eg, you can build pc98 on an i386 machine and vice versa).
276
27720010927:
278	Some weird problems result from using ACPI on some machines.
279	To disable ACPI you can add
280		hint.acpi.0.disable="1"
281	to /boot/loader.conf (or by putting set X=Y at the boot
282	loader "ok" prompt).
283
284	Alternatively, you can remove it from /boot/kernel/acpi.ko
285	or use the MODULES_OVERRIDE function in your kernel config
286	file and not list acpi in that list.
287
28820010924:
289	The buildworld has been fixed.  You may need to install
290	the 4.x compatibility libraries for some old binaries
291	to work.  Add COMPAT4X=true to your /etc/make.conf to
292	get them installed on every installworld, or execute the
293	following to get them installed only once:
294		cd src/lib/compat/compat4x.<arch>
295		make all install
296	You will see ``__stdoutp undefined'' until you do this.
297
29820010919:
299	There's a bug in the world build process.  The cross-tools
300	are build with the NEW headers, but the OLD libc.a.  This
301	leads to all kinds of problems with the new libc.  A temporary
302	workaround is to add
303		CFLAGS="-O -pipe -D_OLD_STDIO"
304	before building world when upgrading from 4.x to current.  This
305	can be removed afterwards.
306
307	A proper fix to the buildworld target is needed.
308
30920010918:
310	Peter has committed his new kthread nfs client/server code.
311	NFS may be unstable after this date.
312
31320010912:
314	KSE has hit the tree.  Lots of things are now different in
315	the kernel.  While a few problems were introduced in the
316	initial commit, most of the major ones have been found and
317	corrected.
318
31920010901:
320	In OLDCARD, CardBus bridges appear to be stable.  The work
321	arounds described in the 20010604 entry are now no longer
322	necessary and will be ignored.  Most insert/remove problems
323	have been rectified around this date.
324
32520010823:
326 	named now runs as user bind and group bind rather than as 
327 	root.  If named_enable is set to YES in /etc/rc.conf, ensure 
328 	that user bind is available in /etc/passwd (using vipw(8)) 
329 	and that group bind is available in /etc/group.  Also make 
330 	sure that user or group bind has read (and not write) 
331 	permission for your name server configuration and that it 
332 	has read and write permission for your slave zone files and 
333 	directory.
334 
335 	If you wish to continue to run named as root (a less secure 
336 	alternative), add a line to /etc/rc.conf saying
337 
338 		named_flags=
339
34020010709:
341	The PAM libraries have had an API upgrade that is beyond
342	the ability of the shared library major number to handle.
343	It is manifested by PAM-using ports dumping core. The
344	solution is to rebuild those ports.
345
34620010628:
347	The kernel compile module has moved from src/sys/compile/FOO
348	to src/sys/${MACHINE}/compile/FOO.
349
35020010625:
351	The pccard modem issue from 20010613 has been corrected.
352	OLDCARD support is still a little weak in -current.  slot 1 is
353	known not to work on some TI based cardbus bridges.  Some
354	cardbus bridges do not properly detect insert/removal events.
355	IRQ configuration needs more safety belts.
356
35720010617:
358	Softupdates problems have been corrected.
359
36020010614:
361	Peter ripped out the linkerset support.  You must, as always,
362	rerun config after you cvsup if you are using the traditional
363	kernel building methods.
364
36520010613:
366	pccard modems may not work with current after 20010604 date.  Some
367	do, others result in panics.  *MAKE*SURE* that you update your
368	config and /etc/rc.conf ala the 20010604 entry, or you will have
369	problems (this issue will be fixed, it just hasn't been yet).
370
37120010613:
372	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
373	use them in current.  You can disable softupdates on all mounted
374	partitions, or remove SOFTUPDATES the kernel config file.
375
37620010612:
377	After Peter's commits to the hints code, people have been noticing
378	that certain devices are attached (or try to) twice.  This is due
379	to having both static hints as well as a /boot/device.hints.  To
380	work around this issue, please use only one or the other mechanism
381	until this bug is fixed.
382
383	Please note that a feature of config is that if you have config
384	file FOO and FOO.hints, it automatically adds FOO.hints to the
385	hints.c file, wheather you want it to or not.
386
38720010610:
388	Locale names have changed to match other systems better.
389
39020010604:
391	pccard support for pci cards has been committed.  You must change
392	your /etc/pccard.conf irq lines.  It must match the irq used by
393	pcic device.  Interrupt storms may result if you fail to do this.
394	Interrupt storms look a lot like a hang.
395
396	You must also install a new pccardd, otherwise you will get an
397	interrupt storm at card reset time (just after it tells you what
398	it is).
399
400	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
401	not to ask the kernel if the interrupt is really free or not before
402	using it.  You can either change the /etc/pccard.conf irq lines to
403	match pcic, or add "-i X" to the pccardd_flags.
404
40520010530:
406	INSTALL=install -C is being deprecated.  If you want to do this,
407	use COPY=-C instead.  The former method will be supported for only
408	a limited time.  If you see
409
410install: warning: the -d and -C options may not be specified together
411
412	in your makeworld, then you need to migrate towards using
413	COPY=-C.
414
41520010525:
416	It appears that vm is now stable enough to use again.  However,
417	there may be other problems, so caution is still urged.  alpha
418	definitely is in bad shape.
419
42020010521:
421	Minor repo damange has happened.  This may cause problems
422	with cvsup of ports.  If you get errors, please see
423	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
424	at the bottom for details on a workaround.  The error message
425	is
426Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
427
42820010520:
429	Vm and/or swapping are busted on -current.  Please be patient.
430
43120010519:
432	pccard has had much reorganizational work done to it over
433	the past few days.  Everything should still work, but if
434	not, please contact imp@freebsd.org.
435
43620010517:
437	ata ioctl changed.  Make sure to recompile both kernel and
438	userland at the same time.
439
44020010517:
441	New ncurses imported.
442
44320010512:
444	DEVFS is now opt out, not opt in.  Barring major problems, this
445	will be the only way to go starting July 1.
446
44720010504:
448	OpenSSH has been updated to 2.9.  Some defaults are different,
449	including RhostsRSAAuthentication, which changes from yes to no.
450
45120010502:
452	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
453
45420010501:
455	Building perl was broken at 02:25:25 PDT.
456
45720010430:
458	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
459	go back in the water.
460
46120010429:
462	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
463	this date, but before the correction date.
464
46520010423:
466	old fsck and new kernel interactions appear to have been fixed.
467
46820010411:
469	fsck and the kernel were changed to handle some optimizations
470	to directory layout.  This breaks backward compatibility.
471	Update only if you understand that you must not use the old
472	fsck with the new kernel ever.
473
47420010330:
475	fsck has changed the meaning of the pass column in /etc/fstab.
476	Please see the cvs commit to fsck.8 or the fsck.8 man page for
477	details.  It is unclear if changes to /etc/fstab are necessary.
478
47920010319:
480	portmap had changed name to rpcbind for maximum POLA in your
481	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
482	other rpc based programs that rely on portmapper will not work
483	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
484
48520010315:
486	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
487	and ATA_ENABEL_TAGS are no longer kernel options.  They have
488	been replaced by tunables.  See ata.4 for details.
489
49020010312:
491	The fxp driver was converted to use miibus.  If you compile
492	fxp into your kernel statically, you will need to add miibus.
493
49420010312:
495	The wi device now defaults to BSS (infrastructure) mode
496	instead of ad-hoc.
497
49820010310:
499	/dev/urandom should be a symbolic link to /dev/random now.
500	Users of current not using DEVFS need to run MAKEDEV std.
501	ssh might not work if you don't.
502
50320010303:
504	The ed driver has been updated.  It now allows mii attachments,
505	which means that you must include the miibus in your kernel if
506	you use the ed driver.
507
50820010220:
509	The problems with libc have been corrected.  It is now mostly
510	safe to go back into the water.
511
51220010211:
513	The size of FILE was changed.  This breaks upgrading.  If
514	you must upgrade, be prepared for pain.  It also breaks almost
515	all binaries that you've compiled on -current.  You are warned
516	that before upgrading would be a good time to do a level 0
517	dump of your system.  No, really, I mean it this time.
518
519	To get to the new system, you'll need to use the following
520	workaround.  Hopefully this can be sorted out so that we
521	don't have to move this to the updating section.
522
523	To get around the installworld problem, do:
524		# cd /usr/src/usr.bin/sed
525		# make install
526		# cd /usr/src
527		# make installworld
528	If that doesn't work, then try:
529		# make -k installworld
530		# make installworld
531
53220010207:
533	DEVFS is now the default.  If you use vinum, make sure that you
534	do not include devfs in your kernel as problems result.
535
53620010205:
537	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
538	Remove them from your config.
539
54020010122:
541	****************************** WARNING ******************************
542			buildkernel has been changed slightly
543	****************************** WARNING ******************************
544	KERNCONF replaces the variable KERNEL for buildkernel.  You
545	should update your scripts and make.conf accordingly.
546
54720010119:
548	config has changed to allow DEV_FOO as a replacement for NFOO.
549	This requires a new config to build correctly.
550
55120010116:
552	The kerrnel option I386_CPU is now mutually exclusive with the
553	other cpu types. If you have an i386 system, be sure that it
554	only had this line.  Remove it for all other configurations.
555
55620010110:
557	Changes to the kernel require it and burncd be in sync.
558
55920010102:
560	Everyone who has hw.sndunit set to something in
561	/etc/sysctl.conf, it is now hw.snd.unit.
562
56320010101:
564	ex and vi were broken by some changes to sys/queue.h.  If you
565	have a bad vi, you will see make buildworld fail with a core
566	dump while building termcap.  You can work around this problem
567	by adding -k to your make buildworld.  This will cause the
568	build to complete and install a new vi.  Once that's done, you
569	can rebuild again without the -k to pick up anything that
570	might have been ignored by the -k option.
571
572	Others have suggested that you can just rebuild libc if your
573	vi/ex is dynamically linked, but I've not received any reports
574	of this working.
575
57620001228:
577	There have been some changes to libcrypt in -current.  The
578	libscrypt/libdescrypt symlink sillyness is gone and the installed
579	libcrypt is fully functional.  Be aware of this.
580
58120001218:
582	Linksys Fast Ethernet PCCARD cards supported by the ed driver
583	now require the addition of flag 0x80000 to their config line
584	in pccard.conf(5).  This flag is not optional.  These Linksys
585	cards will not be recognized without it.
586
58720001205:
588	Important new FreeBSD-version stuff: PAM support has been worked
589	in, partially from the "Unix" OpenSSH version.  This requires
590	adding the following in pam.conf:
591  
592	sshd    auth    sufficient      pam_skey.so
593	sshd    auth    required        pam_unix.so         try_first_pass
594	sshd    session required        pam_permit.so
595
59620001031:
597	cvs updated to 1.11.
598
59920001020:
600	The random device needs more entropy, so you need to make sure
601	that you've run mergemaster to get a /etc/rc which will seed
602	/dev/random.  If you don't and the system hangs after ldconfig,
603	then banging on the keyboard randomly until it unhangs is one
604	workaround.
605
60620001010:
607	****************************** WARNING ******************************
608				Sendmail has been updated.
609	****************************** WARNING ******************************
610	o mail.local(8) is no longer installed as a set-user-id binary.
611	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
612	  is set.
613	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
614	  commands.
615	o Now using sendmail's version of vacation(1).
616	o The sendmail cf building tools (contrib/sendmail/cf) are installed
617	  in /usr/share/sendmail/cf.
618	o sendmail.cw changed to local-host-names
619
620	More details can be found at
621		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
622
62320001009:
624	The ports tree's new layout is in place.  Be sure to update
625	your entire ports tree, or you will have problems.
626
62720001006:
628	The perl build procedure no longer installs miniperl, nor uses
629	the installed miniperl.  It is recommended that you delete
630	/usr/bin/miniperl.
631
63220001005:
633	This weekend the ports tree will be updated to a new layout.
634	It will be in an inconsistent state until noted in the UPDATING
635	file, or with asami-san's message to the relevant mailing
636	lists.  With this new layout, you'll need to update the whole
637	tree for anything to work.
638
63920000928:
640	There was a change in the passwd format.  Need more information.
641
64220000916:
643	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
644	place.  Please update boot loader (not the boot blocks) at the
645	same time as your kernel.
646
64720000914:
648	The new pmtimer device is necessary for laptops.  Failure to
649	include the device will cause suspended laptops losing time
650	when they resume.  Include
651		device		pmtimer
652	in your config file and
653		hint.pmtimer.0.at="isa"
654	to your /boot/device.hints file.
655
65620000911:
657	The random device has been turned into a (pseudo-)device,
658	rather than an option. The supplied kernel config files have
659	been updated. You will need to do something similar in your
660	own kernel config file.
661	Remove:
662		options		RANDOMDEV
663	Add:
664		device		random
665	If you prefer to load the loadable module, you need to do
666	nothing.
667
66820000909:
669	The random device module has been renamed from randomdev.ko to
670	random.ko. You will need to edit your /boot/loader.conf to
671	reflect this if you load this module at boot time.
672	The line should read:
673		random_load="YES"
674
67520000907:
676	The SMPNG commit has happened.  It should work, but if it
677	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
678	to be a variety of minor issues.  Please see 20000905 to make
679	sure you don't have model loading problems which might at
680	first blush appear related to SMP.
681
68220000906:
683	nsswitch has been imported from NetBSD.  Among other things,
684	this means that /etc/host.conf is no longer used.  See
685	nsswitch.conf(5) instead.  Note that at boot time rc.network
686	will attempt to produce a new nsswitch.conf file for you if you
687	don't have one, and you have host.conf.
688
68920000905:
690	The ucred structure changed size.  This breaks the interface
691	that mountd uses.  Trying to use an older mountd with a newer
692	kernel guarantees a panic.  This means that you need to use
693	kernels newer than today only with matching mountd, but you
694	needed to do that anyway with the boot loader changes.
695
69620000905:
697	The boot loader has been updated.  The new default kernel is
698	now /boot/kernel/kernel.ko.  The new default module location
699	is /boot/kernel.
700
701	You *MUST* upgrade your boot loader and kernel at the same time.
702	The easiest way to do this is to do the buildworld/buildkernel/
703	installkernel/installworld dance.
704
705	Furthermore, you are urged to delete your old /modules directory
706	before booting the new kernel, since kldload will find stale
707	modules in that directory instead of finding them in the correct
708	path, /boot/kernel.  The most common complaint that this cures
709	is that the linux module crashes your machine after the update.
710
711	if [ ! -d /boot/kernel.old ]; then
712		mv /modules.old /boot/kernel.old
713		chflags noschg /kernel.old
714		mv /kernel.old /boot/kernel.old/kernel.ko
715		chflags schg /boot/kernel.old/kernel.ko
716	fi
717
71820000904:
719	A new issue with the sendmail upgrade has come to light.
720	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
721	incorrectly install the default aliases in /etc/mail rather than
722	move the old one from /etc.  So you'll need to manually move the
723	file, create a symbolic link, remove the old /etc/aliases.db and
724	run newaliases.  For safety sake, you should stop sendmail
725	while doing this and run the upgrade when locally sourced email
726	is not likely to be generated.
727
72820000825:
729	/boot/device.hints is now required for installkernel to
730	succeed.  You should copy GENERIC.hints for your architecture
731	into /boot/device.hints.  If and only if you compile hints
732	into your kernel, then this file may be empty.  Please note,
733	if you have an empty or missing /boot/device.hints file and
734	you neglected to compile hints into your kernel, no boot
735	messages will appear after the boot loader tries to start the
736	kernel.
737
73820000821:
739	If you do NOT have ``options RANDOMDEV'' in your kernel and
740	you DO want the random device then add randomdev_load="YES" to
741	/boot/loader.conf.
742
74320000812:
744	suidperl is now always built and installed on the system, but
745	with permissions of 511.  If you have applications that use
746	this program, you are now required to add ENABLE_SUIDPERL=true
747	to /etc/make.conf.  If you forget to do this,
748		chmod 4511 /usr/bin/suidperl
749	will fix this until the next build.
750
75120000812:
752	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
753	visible changes that may immediately affect your configuration
754	include:
755	- New default file locations from src/contrib/sendmail/cf/README
756	- newaliases limited to root and trusted users
757	- MSA port (587) turned on by default
758	- New queue file naming system so can't go from 8.11 -> 8.9
759	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
760	- FEATURE(`nullclient') is more full featured
761	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
762	- mail.local FreeBSD-only -b option changed to -B
763	- See src/contrib/sendmail/RELEASE_NOTES for more info
764
76520000810:
766	suidperl (aka sperl) is no longer build by default.  You must
767	specifically define BUILD_SUIDPERL to "true" for it to be build.
768	Furthermore, we recommend that you remove /usr/bin/sperl* and
769	/usr/bin/suidperl files from your system unless you have a
770	specific use for it.
771
77220000729:
773	Networking defaults have been tightened.  Anybody upgrading
774	/etc/defaults/rc.conf needs to add the following lines to
775	/etc/rc.conf if they want to have the same setup
776	afterwards (unless the variables already are set, of course):
777		# Enable network daemons for user convenience.
778		inetd_enable="YES"
779		portmap_enable="YES"
780		sendmail_enable="YES"
781
78220000728:
783	If you have null_load="YES" in your /boot/loader.conf, you
784	will need to change that to nullfs_load="YES".
785
78620000728:
787	The "installkernel" target has changed slightly. Now even if
788	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
789	it will install the MYKERNEL file (built with the buildkernel
790	target) as /kernel rather than /MYKERNEL. Those who have
791	updated their /boot/loader.conf files to point to /MYKERNEL
792	should remove that entry or perform manual rename of /kernel
793	to /MYKERNEL.
794
79520000711:
796	If you use CVSUP or CTM to get CVS trees, AND you used to get 
797	the old crypto files from internat.freebsd.org AND you check
798	out files from the CVS tree with the cvs command, please read
799		http://people.freebsd.org/~imp/internat.txt
800	for details on potential problems that you might have and how
801	to get around them.
802
803	If you are merely a mirror, or don't answer yes to each of the
804	clauses above, you needn't worry.
805
80620000711:
807	/etc/security has been updated to print the inode number of
808	setuid programs that have changed.  You will see a large spike
809	in the number of changed programs the first time when you run
810	mergemaster to get a new /etc/security.
811
81220000710:
813	/dev/random now has good entropy collection (from the keyboard
814	and sysmouse drivers). Please ensure that either `options
815	RANDOMDEV' is present in your kernel config file or that
816	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
817	not have the /dev/random driver, OpenSSL (and consequently
818	lots of crypto tools (like SSH)) will fail with strange
819	errors. (see below, 20000624).
820
821	FreeBSD-current is safe again to run Crypto.
822
82320000709:
824	phk made the malloc default options AJ.  This may slow things
825	down and uncover other latent bugs in the code.  If you need to
826	run at full speed, you can disable this by doing the following:
827		ln -s aj /etc/malloc.conf
828
82920000706:
830	libftpio's version was accidentally bumped a few days ago.  This
831	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
832	before doing your next buildworld/installworld pair.  It certainly
833	won't hurt to remove it before the update procedure.  It will
834	break fetch until a new one is built, but ftp can be used in the
835	interim if needed.
836
83720000705:
838	The crypto packages have changed for the cvsup.  This has been done
839	in a backward compatible way, but the old packages will go away at
840	some point in the future.  Look at /usr/share/examples/cvsup for
841	details.
842
84320000704:
844	With the new sys/modules/sound/drivers/*, you will need to
845	set SYSDIR until you do an installworld after July 7th.
846
84720000704:
848	rc.shutdown and rc will now call the rc.d scripts with start
849	or stop.  This may cause some harmless warnings from older
850	rc.d scripts that haven't been updated.
851
85220000630:
853	The libfetch based version of fetch has gone into the tree.
854	Minor problems may result on some of the less popular sites,
855	which should be reported to des@freebsd.org.
856
85720000625:
858	From approximately this date forward, one must have the crypto
859	system installed in order to build the system and kernel.
860	While not technically strictly true, one should treat it as
861	required and grab the crypto bits.  If you are grabbing CVS
862	trees, src-all and cvs-crypto should be treated as if they
863	were required.  You should check with the latest collections
864	to make sure that these haven't changed.
865
86620000624:
867	Mark Murray just committed the first parts of a cleanup of
868	/dev/zero, et al.  This is also cleaning up /dev/random.
869	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
870	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
871	until Mark can merge in the fixes to this work in progress.
872	openssh and openssl should not be used to generate keys from this
873	date to the completion of the work.
874
875	If you must operate at this reduced level of security, add '
876	options RANDOMDEV' to your kernel or modload the randomdev
877	module.  You may also need to copy a new MAKEDEV to /dev and
878	recreate the random and urandom devices.
879
88020000622:
881	The license on the softupdates is now a standard 2 clause
882	BSD license.  You may need to remove your symbolic links
883	that used to be required when updating.
884
88520000621:
886	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
887	the config file update procedure.
888		http://people.freebsd.org/~imp/config-upd.html
889	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
890	isn't buildable.  However, you can generate a LINT file.
891
89220000620:
893	Binutils 2.10 have hit the tree, or will shortly.  As soon
894	as they do, the problem noted in 20000522 will be resolved and
895	that workaround will no longer be required.
896
89720000615:
898	phk removed the compatibility creation of wd devices in the
899	ad driver.  If you haven't done so already, you must update
900	your fstab, etc to use the ad devices instead of the wd
901	devices.
902
903	In addition, you'll need to update your boot blocks to a
904	more modern version, if you haven't already done so.  Modern
905	here means 4.0 release or newer (although older releases
906	may work).
907
90820000612:
909	Peter took an axe to config(8).  Be sure that you read his mail
910	on the topic before even thinking about updating.  You will
911	need to create a /boot/device.hints or add a hints directive
912	to your config file to compile them in statically.  The format
913	of the config file has changed as well.  Please see GENERIC or
914	NEWCARD for examples of the new format.
915
916	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
917	says that it has been fixed, assume that must use the hints mechanism
918	in the loader if you need to use a machine with very old ISA cards
919	in it.
920
92120000522:
922	A new set of binutils went into the tree today.  Anybody
923	building a kernel after this point is advised that they need
924	to rebuild their binutils (or better yet do a
925	buildworld/installworld) before building a new kernel.
926
927	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
928	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
929	is recommended that you don't set this option until the problem
930	is resolved.
931
93220000513:
933	The ethernet drivers were all updated to clean up the BPF handling.
934
93520000510:
936	The problems with boot blocks on the alphas have been corrected.
937	This will require some care in updating alphas.  A new libstand
938	is requires for the boot blocks to build properly.
939
94020000503:
941	Recompile all kld modules.  Proper version dependency info
942	is now available.
943
94420000502:
945	Modules have been disconnected from the buildworld tree and 
946	connected to the kernel building instead.
947
94820000427:
949	You may need to build gperf
950		cd /usr/src/gnu/usr.bin/gperf && make depend all install
951	when upgrading from 4.0 -> current.  The build system now uses
952	an option only in -current.
953
95420000417:
955	The method that we brand ELF binaries has changed to be more
956	acceptable to the binutils maintainers.  You will need to
957	rebrand your ELF binaries that aren't native.  One problem
958	binary is the Linux ldconfig.  After your make world, but
959	before you reboot, you'll need to issue:
960		brandelf -t Linux /compat/linux/sbin/ldconfig
961	if you have Linux compatibility enabled on your machine.
962
96320000320:
964	If you have really bad/marginal IDE drives, you may find they
965	don't work well.  Use pio mode instead.  The easiest way to
966	cope if you have a problem combination is to add:
967		/sbin/sysctl hw.ata.ata_dma=0
968	to the start of /etc/rc.conf.
969
97020000319:
971	The ISA and PCI compatibility shims have been connected to the
972	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
973	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
974	include the appropriate option in your kernel config.  Drivers
975	using the shims should be updated or they won't ship with
976	5.0-RELEASE, targeted for 2001.
977
97820000318:
979	We've entered the traditional post release dumping party.
980	Large kernel changes are being committed and are in the
981	works.  It is important to keep the systems' klds and kernel
982	in sync as kernel interfaces and structures are changing.
983	Before reporting kernel panics, make sure that all modules
984	that you are loading are up to date.
985
98620000315:
987	If you are upgrading from an older version of FreeBSD, you
988	need to update your boot blocks as well.  'disklabel -B ad0'
989	will do the trick.  This isn't critical until you remove your
990	wd device entries in /dev, at which point your system will not
991	boot.
992
99320000315:
994	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
995	to upgrade to 4.0 from 3.x.
996
997COMMON ITEMS:
998
999	General Notes
1000	-------------
1001	Avoid using make -j when upgrading.  From time to time in the
1002	past there have been problems using -j with buildworld and/or
1003	installworld.  This is especially true when upgrading between
1004	"distant" versions (eg one that cross a major release boundary
1005	or several minor releases, or when several months have passed
1006	on the -current branch).
1007
1008	Sometimes, obscure build problems are the result of environment
1009	poisoning.  This can happen because the make utility reads its
1010	environment when searching for values for global variables.
1011	To run your build attempts in an "environmental clean room",
1012	prefix all make commands with 'env -i '.  See the env(1) manual
1013	page for more details.
1014
1015	To build a kernel
1016	-----------------
1017	If you are updating from a prior version of FreeBSD (even one just
1018	a few days old), you should follow this procedure. With a
1019	/usr/obj tree with a fresh buildworld,
1020	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1021	make installkernel KERNCONF=YOUR_KERNEL_HERE
1022
1023	To just build a kernel when you know that it won't mess you up
1024	--------------------------------------------------------------
1025	cd src/sys/{i386,alpha}/conf
1026	config KERNEL_NAME_HERE
1027	cd ../../compile/KERNEL_NAME_HERE
1028	make depend
1029	make
1030	make install	
1031
1032	If this fails, go to the "To build a kernel" section.
1033
1034	To rebuild everything and install it on the current system.
1035	-----------------------------------------------------------
1036	# Note: sometimes if you are running current you gotta do more than
1037	# is listed here if you are upgrading from a really old current.
1038
1039	<make sure you have good level 0 dumps>
1040	<maybe fix /etc/fstab>				[7]
1041	make buildworld
1042	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1043	make installkernel KERNCONF=YOUR_KERNEL_HERE
1044							[1]
1045	<reboot in single user>				[3]
1046	mergemaster -p					[5]
1047	make installworld
1048	mergemaster					[4]
1049	<reboot>
1050
1051
1052	To upgrade from 4.x-stable to current
1053	-------------------------------------
1054	# 5.x uses more space than 4.x.  Also, the location of kernel
1055	# modules has changed.  If you are installing 5.0 onto a 4.x
1056	# system, you'll need about 30MB of free disk space on your /
1057	# partition.  If you have less than this, you may encounter difficult
1058	# to back out of problems with this proceedure.  If /tmp is on
1059	# the / partition, you may want to completely remove all its content
1060	# before upgrading, as this can be a common source of shortage of
1061	# space on /.
1062	
1063	<make sure you have good level 0 dumps>
1064	<maybe fix /etc/fstab>				[7]
1065	make buildworld					[9]
1066	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1067	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1068	make installkernel KERNCONF=YOUR_KERNEL_HERE
1069	cd src/sys/boot ; make install			[6]
1070							[1]
1071	<reboot in single user>				[3]
1072	mergemaster -p					[5]
1073	rm -rf /usr/include/g++
1074	make installworld
1075	mergemaster					[4]
1076	<reboot>
1077
1078	Make sure that you've read the UPDATING file to understand the
1079	tweaks to various things you need.  At this point in the life
1080	cycle of current, things change often and you are on your own
1081	to cope.  The defaults can also change, so please read ALL of
1082	the UPDATING entries.
1083
1084	Also, if you are tracking -current, you must be subscribed to
1085	freebsd-current@freebsd.org.  Make sure that before you update
1086	your sources that you have read and understood all the recent
1087	messages there.  If in doubt, please track -stable which has
1088	much fewer pitfalls.
1089
1090	[1] If you have third party modules, such as vmware, you
1091	should disable them at this point so they don't crash your
1092	system on reboot.
1093
1094	[2] If you have legacy ISA devices, you may need to create
1095	your own device.hints to reflect your unique hardware
1096	configuration.
1097
1098	[3] From the bootblocks, boot -s, and then do
1099		fsck -p
1100		mount -u /
1101		mount -a
1102		cd /usr/src
1103		adjkerntz -i		# if CMOS is wall time
1104	Also, when doing a major release upgrade, it is required that
1105	you boot into single user mode to do the installworld.
1106	For the 4.x -> 5.0 upgrade, you will also see many messages about
1107	needing to recompile your userland.  These are harmless and can
1108	be ignored while you proceed to the next step.
1109
1110	[4] Note: This step is non-optional.  Failure to do this step
1111	can result in a significant reduction in the functionality of the
1112	system.  Attempting to do it by hand is not recommended and those
1113	that pursue this avenue should read this file carefully, as well
1114	as the archives of freebsd-current and freebsd-hackers mailing lists
1115	for potential gotchas.
1116
1117	[5] Usually this step is a noop.  However, from time to time
1118	you may need to do this if you get unknown user in the following
1119	step.  It never hurts to do it all the time.  You may need to
1120	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1121	install) after the buildworld before this step if you last updated
1122	from current before 20020224 or from -stable before 20020408.
1123
1124	[6] 4.x boot loader can be used to boot a 5.x system, however
1125	it is difficult to do that at best.  If you wish to try, then
1126	you should interrupt the boot and at the ok prompt type:
1127		ok unload
1128		ok boot /boot/kernel/kernel
1129	If this fails to work, you must install a new boot loader as
1130	described here.
1131
1132	[7] Before you upgrade, please make sure that you are not using
1133	compatibility slices.  These are device names of the form, on i386
1134	and other architectures that use MBR slicing, /dev/ad0a without the
1135	actual slice name.  Chances are excellent that these will break.
1136	You generally must update these entries to use the post FreeBSD
1137	2.x form of /dev/ad0s1a.
1138
1139	[8] In order to have a kernel that can run the 4.x binaries
1140	needed to do an installworld, you must include the COMPAT_FREEBSD4
1141	option in your kernel.  Failure to do so may leave you with a system
1142	that is hard to boot to recover.
1143
1144	[9] When checking out sources, you must include the -P flag to have
1145	cvs prune empty directories.
1146FORMAT:
1147
1148This file contains a list, in reverse chronological order, of major
1149breakages in tracking -current.  Not all things will be listed here,
1150and it only starts on March 15, 2000.  Updating files can found in
1151previous releases if your system is older than this.
1152
1153Copyright information:
1154
1155Copyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1156
1157Redistribution, publication, translation and use, with or without
1158modification, in full or in part, in any form or format of this
1159document are permitted without further permission from the author.
1160
1161THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1162IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1163WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1164DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1165INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1166(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1167SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1168HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1169STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1170IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1171POSSIBILITY OF SUCH DAMAGE.
1172
1173If you find this document useful, and you want to, you may buy the
1174author a beer.
1175
1176Contact Warner Losh if you have any questions about your use of
1177this document.
1178
1179$FreeBSD: head/UPDATING 109389 2003-01-16 16:56:58Z imp $
1180