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