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