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