UPDATING revision 101911
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
20	In addition, IDE write caching is currently disabled by default
21	due to on-going concerns about disk write order and file system
22	integrity.  Re-enabling write caching can substantially improve
23	performance.
24
2520020815:
26	A "bug" in gcc(1) that was hiding warning in system headers was
27	fixed.  It's probably time to add -DNO_WERROR to your make line
28	again.
29
3020020729:
31	COPY is being deprecated.  The 20010530 change was reverted, as
32	it causes far more pain than was expected, and to always compare
33	before installing, please use INSTALL="install -C" again.  The
34	-C option is now silently ignored when used with the -d option.
35
3620020702:
37	Problems with libc_r clients like KDE and GNOME have been resolved.
38	There are still some minor problems with some signals but the 
39	system is stable enough for general use again. SMP is less so than UP
40	but each can successfully complete multiple buildworlds.
41	Libkvm needs to be recompiled due to KSE.
42
4320020701:
44	Now would be a bad time to upgrade.  Something in or near the
45	KSE commit totally broke programs using libc_r like KDE and
46	GNOME.
47
4820020511:
49	The k5su utility installed as part of Kerberos 5 is no longer
50	installed with the set-user-ID bit set by default.  Add
51	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
52	with the set-user-ID bit set.
53
5420020510:
55	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
56	Unfortunately our native GDB (at version 4.18) does not understand
57	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
58	generated debugging information for our native GDB.
59
6020020510:
61	Due to the way CVS works, it may not properly update src/contrib/gcc
62	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
63	and then do a cvs update.
64
6520020421:
66	When exec'ing set[ug]id executables, the kernel now ensures that the
67	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
68
6920020404:
70	New sendmail startup scripts have been installed to make it
71	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
72	variable sendmail_enable to "NO" no longer prevents any sendmail
73	daemons from starting.  Instead, either set sendmail_enable to
74	"NONE" or change mta_start_script to a script for starting
75	an alternative MTA.  Setting mta_start_script to "" will
76	also prevent any MTA from being started at boot.
77
7820020403:
79	UCONSOLE is no longer a valid kernel option.
80
8120020315:
82	FreeBSD 5.0 DP-1 was basically branched today.
83
8420020225:
85	Warnings are now errors in the kernel.  Unless you are a developer,
86	you should add -DNO_WERROR to your make line.
87
8820020217:
89	sendmail 8.12.2 has been imported.  The sendmail binary is no
90	longer a set-user-ID root binary and the infrastructure to support
91	command line mail submission has changed.  Be sure to run
92	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
93	and /etc/mail) and read /etc/mail/README for more details.
94
95	Due to the import of sendmail 8.12.2, a new user and group are
96	required in order for sendmail to run as a set-group-ID
97	binary.  A 'make installworld' will use the new user and group
98	to set the owner and group of /var/spool/clientmqueue and will
99	fail if the new user and group do not exist.  The 'smmsp' user
100	and group must be merged from src/etc/group and
101	src/etc/master.passwd before using 'make installworld'.
102	'mergemaster -p' will do this.  You may need to install
103	mergemaster before this will work if you are updating from a
104	very old version of current.  The updating recipe has changed
105	as of this date.
106
10720020112:
108	The preferred configuration method for PAM is now /etc/pam.d/
109	rather than /etc/pam.conf.  If you have an unmodified
110	pam.conf, just delete it after your next mergemaster run.  If
111	you have local modifications, you can use
112	/usr/src/etc/pam.d/convert.pl to incorporate them into your
113	/etc/pam.d.
114
115	Please see the following url for more details:
116http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
11720011229:
118	If anyone here is already using the new rc.conf(5) variable
119	networkfs_types, please note that it has changed
120http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
121
12220011220:
123	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
124	started out its life in the ISDN4BSD project as an offspring
125	from sys/net/if_spppsubr.c, which eventually got a life of its
126	own.  All the accumulated features and bugfixes of the i4b
127	version have now been merged back into the base system's
128	version now.  The only user-visible change resulting from this
129	is that i4b's sppp(4) interfaces are to be managed with
130	spppcontrol(8) again, since ispppcontrol(8) has been retired
131	as well.  (There has never been rc file support for
132	ispppcontrol in -current, but only in -stable.  That will be
133	reverted by the time the changes are MFCed.)
134
13520011215:
136	The fdc(4) driver has been updated and now automatically
137	recognizes media in `standard' formats (like 1440 KB and
138	720 KB for a 3.5" high-density drive) when accessing the
139	default device node (e. g. /dev/fd0).  The old variety of
140	floppy device nodes /dev/fd*.* is no longer present by
141	default, devices can be created (in DEVFS) on demand.  They
142	will need to be customized then for `odd' densities using
143	fdcontrol(8).
144
14520011209:
146	The bugs in procfs' debugging support code have been fixed,
147	and truss(1) now works again.
148
14920011207:
150	Daily security checks have been split out to use the periodic(8)
151	scripts.  Some change in configuration may be necessary.  Please
152	see 
153http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
154	for details.
155
15620011204:
157	sos added VCD/SVCD support to ata driver and that needs the
158	kernel and burncd to be in sync.
159
16020011203:
161	The procfs pseudo-filesystem has now been converted to use the
162	pseudofs framework.  If you have 'options PROCFS' in your
163	kernel config, you'll need to add 'options PSEUDOFS' if it's
164	not there already.
165
166	This change temporarily breaks truss(1); use ktrace(1) instead
167	until the issue has been resolved.
168
16920011202:
170	A security hole in OpenSSH involving `UseLogin yes' has been
171	patched.
172
17320011126:
174	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
175	after this date.  You need to do this only once.
176
17720011103:
178	Most of the awk issues have been resolved.  Some rough
179	edges may be left, but for the most part things should be
180	back to "normal." For CURRENT's usual definition of "normal."
181
18220011030:
183	Awk has been upgraded to the one true awk from bell labs.  Expect
184	choppy waves in the upgrade process.
185
18620011030:
187	The asr driver problem has been resolved.
188
18920011027:
190	Due to changes in other parts of the system, the asr driver
191	now causes the system to panic on boot.  Do not use it pending
192	correction.  Comment it out of any kernel config file that you
193	try to use from this date forward.
194
19520011025:
196	When crossbuilding, use TARGET=xxx where you used to use
197	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
198	unless you are changing both of them.  To cross build pc98 on
199	an alpha, for example, you need to set TARGET=pc98 and
200	TARGET_ARCH=i386.
201
20220011001:
203	The kernel interface that burncd depends on has changed.
204	You must recompile both the kernel and userland applications
205	at the same time.
206
20720010929:
208	When crossbuilding, please set TARGET_ARCH rather than
209	MACHINE_ARCH to indicate the target.  In the future, one will
210	set TARGET_MACHINE where you set MACHINE now.  At the moment,
211	setting MACHINE alone for same MACHINE_ARCH machines works
212	(eg, you can build pc98 on a i386 machine and vice versa).
213
21420010927:
215	Some weird problems result from using ACPI on some machines.
216	To disable ACPI you can add
217		hint.acpi.0.disable="1"
218	to /boot/loader.conf (or by putting set X=Y at the boot
219	loader "ok" prompt).
220
221	Alternatively, you can remove it from /boot/kernel/acpi.ko
222	or use the MODULES_OVERRIDE function in your kernel config
223	file and not list acpi in that list.
224
22520010924:
226	The buildworld has been fixed.  You may need to install
227	the 4.x compatibility libraries for some old binaries
228	to work.  Add COMPAT4X=true to your /etc/make.conf to
229	get them installed on every installworld, or execute the
230	following to get them installed only once:
231		cd src/lib/compat/compat4x.<arch>
232		make all install
233	You will see ``__stdoutp undefined'' until you do this.
234
23520010919:
236	There's a bug in the world build process.  The cross-tools
237	are build with the NEW headers, but the OLD libc.a.  This
238	leads to all kinds of problems with the new libc.  A temporary
239	workaround is to add
240		CFLAGS="-O -pipe -D_OLD_STDIO"
241	before building world when upgrading from 4.x to current.  This
242	can be removed afterwards.
243
244	A proper fix to the buildworld target is needed.
245
24620010918:
247	Peter has committed his new kthread nfs client/server code.
248	NFS may be unstable after this date.
249
25020010912:
251	KSE has hit the tree.  Lots of things are now different in
252	the kernel.  While a few problems were introduced in the
253	initial commit, most of the major ones have been found and
254	corrected.
255
25620010901:
257	In OLDCARD, CardBus bridges appear to be stable.  The work
258	arounds described in the 20010604 entry are now no longer
259	necessary and will be ignored.  Most insert/remove problems
260	have been rectified around this date.
261
26220010823:
263 	named now runs as user bind and group bind rather than as 
264 	root.  If named_enable is set to YES in /etc/rc.conf, ensure 
265 	that user bind is available in /etc/passwd (using vipw(8)) 
266 	and that group bind is available in /etc/group.  Also make 
267 	sure that user or group bind has read (and not write) 
268 	permission for your name server configuration and that it 
269 	has read and write permission for your slave zone files and 
270 	directory.
271 
272 	If you wish to continue to run named as root (a less secure 
273 	alternative), add a line to /etc/rc.conf saying
274 
275 		named_flags=
276
27720010709:
278	The PAM libraries have had an API upgrade that is beyond
279	the ability of the shared library major number to handle.
280	It is manifested by PAM-using ports dumping core. The
281	solution is to rebuild those ports.
282
28320010628:
284	The kernel compile module has moved from src/sys/compile/FOO
285	to src/sys/${MACHINE}/compile/FOO.
286
28720010625:
288	The pccard modem issue from 20010613 has been corrected.
289	OLDCARD support is still a little weak in -current.  slot 1 is
290	known not to work on some TI based cardbus bridges.  Some
291	cardbus bridges do not properly detect insert/removal events.
292	IRQ configuration needs more safety belts.
293
29420010617:
295	Softupdates problems have been corrected.
296
29720010614:
298	Peter ripped out the linkerset support.  You must, as always,
299	rerun config after you cvsup if you are using the traditional
300	kernel building methods.
301
30220010613:
303	pccard modems may not work with current after 20010604 date.  Some
304	do, others result in panics.  *MAKE*SURE* that you update your
305	config and /etc/rc.conf ala the 20010604 entry, or you will have
306	problems (this issue will be fixed, it just hasn't been yet).
307
30820010613:
309	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
310	use them in current.  You can disable softupdates on all mounted
311	partitions, or remove SOFTUPDATES the kernel config file.
312
31320010612:
314	After Peter's commits to the hints code, people have been noticing
315	that certain devices are attached (or try to) twice.  This is due
316	to having both static hints as well as a /boot/device.hints.  To
317	work around this issue, please use only one or the other mechanism
318	until this bug is fixed.
319
320	Please note that a feature of config is that if you have config
321	file FOO and FOO.hints, it automatically adds FOO.hints to the
322	hints.c file, wheather you want it to or not.
323
32420010610:
325	Locale names have changed to match other systems better.
326
32720010604:
328	pccard support for pci cards has been committed.  You must change
329	your /etc/pccard.conf irq lines.  It must match the irq used by
330	pcic device.  Interrupt storms may result if you fail to do this.
331	Interrupt storms look a lot like a hang.
332
333	You must also install a new pccardd, otherwise you will get an
334	interrupt storm at card reset time (just after it tells you what
335	it is).
336
337	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
338	not to ask the kernel if the interrupt is really free or not before
339	using it.  You can either change the /etc/pccard.conf irq lines to
340	match pcic, or add "-i X" to the pccardd_flags.
341
34220010530:
343	INSTALL=install -C is being deprecated.  If you want to do this,
344	use COPY=-C instead.  The former method will be supported for only
345	a limited time.  If you see
346
347install: warning: the -d and -C options may not be specified together
348
349	in your makeworld, then you need to migrate towards using
350	COPY=-C.
351
35220010525:
353	It appears that vm is now stable enough to use again.  However,
354	there may be other problems, so caution is still urged.  alpha
355	definitely is in bad shape.
356
35720010521:
358	Minor repo damange has happened.  This may cause problems
359	with cvsup of ports.  If you get errors, please see
360	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
361	at the bottom for details on a workaround.  The error message
362	is
363Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
364
36520010520:
366	Vm and/or swapping are busted on -current.  Please be patient.
367
36820010519:
369	pccard has had much reorganizational work done to it over
370	the past few days.  Everything should still work, but if
371	not, please contact imp@freebsd.org.
372
37320010517:
374	ata ioctl changed.  Make sure to recompile both kernel and
375	userland at the same time.
376
37720010517:
378	New ncurses imported.
379
38020010512:
381	DEVFS is now opt out, not opt in.  Barring major problems, this
382	will be the only way to go starting July 1.
383
38420010504:
385	OpenSSH has been updated to 2.9.  Some defaults are different,
386	including RhostsRSAAuthentication, which changes from yes to no.
387
38820010502:
389	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
390
39120010501:
392	Building perl was broken at 02:25:25 PDT.
393
39420010430:
395	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
396	go back in the water.
397
39820010429:
399	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
400	this date, but before the correction date.
401
40220010423:
403	old fsck and new kernel interactions appear to have been fixed.
404
40520010411:
406	fsck and the kernel were changed to handle some optimizations
407	to directory layout.  This breaks backward compatibility.
408	Update only if you understand that you must not use the old
409	fsck with the new kernel ever.
410
41120010330:
412	fsck has changed the meaning of the pass column in /etc/fstab.
413	Please see the cvs commit to fsck.8 or the fsck.8 man page for
414	details.  It is unclear if changes to /etc/fstab are necessary.
415
41620010319:
417	portmap had changed name to rpcbind for maximum POLA in your
418	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
419	other rpc based programs that rely on portmapper will not work
420	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
421
42220010315:
423	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
424	and ATA_ENABEL_TAGS are no longer kernel options.  They have
425	been replaced by tunables.  See ata.4 for details.
426
42720010312:
428	The fxp driver was converted to use miibus.  If you compile
429	fxp into your kernel statically, you will need to add miibus.
430
43120010312:
432	The wi device now defaults to BSS (infrastructure) mode
433	instead of ad-hoc.
434
43520010310:
436	/dev/urandom should be a symbolic link to /dev/random now.
437	Users of current not using DEVFS need to run MAKEDEV std.
438	ssh might not work if you don't.
439
44020010303:
441	The ed driver has been updated.  It now allows mii attachments,
442	which means that you must include the miibus in your kernel if
443	you use the ed driver.
444
44520010220:
446	The problems with libc have been corrected.  It is now mostly
447	safe to go back into the water.
448
44920010211:
450	The size of FILE was changed.  This breaks upgrading.  If
451	you must upgrade, be prepared for pain.  It also breaks almost
452	all binaries that you've compiled on -current.  You are warned
453	that before upgrading would be a good time to do a level 0
454	dump of your system.  No, really, I mean it this time.
455
456	To get to the new system, you'll need to use the following
457	workaround.  Hopefully this can be sorted out so that we
458	don't have to move this to the updating section.
459
460	To get around the installworld problem, do:
461		# cd /usr/src/usr.bin/sed
462		# make install
463		# cd /usr/src
464		# make installworld
465	If that doesn't work, then try:
466		# make -k installworld
467		# make installworld
468
46920010207:
470	DEVFS is now the default.  If you use vinum, make sure that you
471	do not include devfs in your kernel as problems result.
472
47320010205:
474	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
475	Remove them from your config.
476
47720010122:
478	****************************** WARNING ******************************
479			buildkernel has been changed slightly
480	****************************** WARNING ******************************
481	KERNCONF replaces the variable KERNEL for buildkernel.  You
482	should update your scripts and make.conf accordingly.
483
48420010119:
485	config has changed to allow DEV_FOO as a replacement for NFOO.
486	This requires a new config to build correctly.
487
48820010116:
489	The kerrnel option I386_CPU is now mutually exclusive with the
490	other cpu types. If you have an i386 system, be sure that it
491	only had this line.  Remove it for all other configurations.
492
49320010110:
494	Changes to the kernel require it and burncd be in sync.
495
49620010102:
497	Everyone who has hw.sndunit set to something in
498	/etc/sysctl.conf, it is now hw.snd.unit.
499
50020010101:
501	ex and vi were broken by some changes to sys/queue.h.  If you
502	have a bad vi, you will see make buildworld fail with a core
503	dump while building termcap.  You can work around this problem
504	by adding -k to your make buildworld.  This will cause the
505	build to complete and install a new vi.  Once that's done, you
506	can rebuild again without the -k to pick up anything that
507	might have been ignored by the -k option.
508
509	Others have suggested that you can just rebuild libc if your
510	vi/ex is dynamically linked, but I've not received any reports
511	of this working.
512
51320001228:
514	There have been some changes to libcrypt in -current.  The
515	libscrypt/libdescrypt symlink sillyness is gone and the installed
516	libcrypt is fully functional.  Be aware of this.
517
51820001218:
519	Linksys Fast Ethernet PCCARD cards supported by the ed driver
520	now require the addition of flag 0x80000 to their config line
521	in pccard.conf(5).  This flag is not optional.  These Linksys
522	cards will not be recognized without it.
523
52420001205:
525	Important new FreeBSD-version stuff: PAM support has been worked
526	in, partially from the "Unix" OpenSSH version.  This requires
527	adding the following in pam.conf:
528  
529	sshd    auth    sufficient      pam_skey.so
530	sshd    auth    required        pam_unix.so         try_first_pass
531	sshd    session required        pam_permit.so
532
53320001031:
534	cvs updated to 1.11.
535
53620001020:
537	The random device needs more entropy, so you need to make sure
538	that you've run mergemaster to get a /etc/rc which will seed
539	/dev/random.  If you don't and the system hangs after ldconfig,
540	then banging on the keyboard randomly until it unhangs is one
541	workaround.
542
54320001010:
544	****************************** WARNING ******************************
545				Sendmail has been updated.
546	****************************** WARNING ******************************
547	o mail.local(8) is no longer installed as a set-user-id binary.
548	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
549	  is set.
550	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
551	  commands.
552	o Now using sendmail's version of vacation(1).
553	o The sendmail cf building tools (contrib/sendmail/cf) are installed
554	  in /usr/share/sendmail/cf.
555	o sendmail.cw changed to local-host-names
556
557	More details can be found at
558		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
559
56020001009:
561	The ports tree's new layout is in place.  Be sure to update
562	your entire ports tree, or you will have problems.
563
56420001006:
565	The perl build procedure no longer installs miniperl, nor uses
566	the installed miniperl.  It is recommended that you delete
567	/usr/bin/miniperl.
568
56920001005:
570	This weekend the ports tree will be updated to a new layout.
571	It will be in an inconsistent state until noted in the UPDATING
572	file, or with asami-san's message to the relevant mailing
573	lists.  With this new layout, you'll need to update the whole
574	tree for anything to work.
575
57620000928:
577	There was a change in the passwd format.  Need more information.
578
57920000916:
580	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
581	place.  Please update boot loader (not the boot blocks) at the
582	same time as your kernel.
583
58420000914:
585	The new pmtimer device is necessary for laptops.  Failure to
586	include the device will cause suspended laptops losing time
587	when they resume.  Include
588		device		pmtimer
589	in your config file and
590		hint.pmtimer.0.at="isa"
591	to your /boot/device.hints file.
592
59320000911:
594	The random device has been turned into a (pseudo-)device,
595	rather than an option. The supplied kernel config files have
596	been updated. You will need to do something similar in your
597	own kernel config file.
598	Remove:
599		options		RANDOMDEV
600	Add:
601		device		random
602	If you prefer to load the loadable module, you need to do
603	nothing.
604
60520000909:
606	The random device module has been renamed from randomdev.ko to
607	random.ko. You will need to edit your /boot/loader.conf to
608	reflect this if you load this module at boot time.
609	The line should read:
610		random_load="YES"
611
61220000907:
613	The SMPNG commit has happened.  It should work, but if it
614	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
615	to be a variety of minor issues.  Please see 20000905 to make
616	sure you don't have model loading problems which might at
617	first blush appear related to SMP.
618
61920000906:
620	nsswitch has been imported from NetBSD.  Among other things,
621	this means that /etc/host.conf is no longer used.  See
622	nsswitch.conf(5) instead.  Note that at boot time rc.network
623	will attempt to produce a new nsswitch.conf file for you if you
624	don't have one, and you have host.conf.
625
62620000905:
627	The ucred structure changed size.  This breaks the interface
628	that mountd uses.  Trying to use an older mountd with a newer
629	kernel guarantees a panic.  This means that you need to use
630	kernels newer than today only with matching mountd, but you
631	needed to do that anyway with the boot loader changes.
632
63320000905:
634	The boot loader has been updated.  The new default kernel is
635	now /boot/kernel/kernel.ko.  The new default module location
636	is /boot/kernel.
637
638	You *MUST* upgrade your boot loader and kernel at the same time.
639	The easiest way to do this is to do the buildworld/buildkernel/
640	installkernel/installworld dance.
641
642	Furthermore, you are urged to delete your old /modules directory
643	before booting the new kernel, since kldload will find stale
644	modules in that directory instead of finding them in the correct
645	path, /boot/kernel.  The most common complaint that this cures
646	is that the linux module crashes your machine after the update.
647
648	if [ ! -d /boot/kernel.old ]; then
649		mv /modules.old /boot/kernel.old
650		chflags noschg /kernel.old
651		mv /kernel.old /boot/kernel.old/kernel.ko
652		chflags schg /boot/kernel.old/kernel.ko
653	fi
654
65520000904:
656	A new issue with the sendmail upgrade has come to light.
657	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
658	incorrectly install the default aliases in /etc/mail rather than
659	move the old one from /etc.  So you'll need to manually move the
660	file, create a symbolic link, remove the old /etc/aliases.db and
661	run newaliases.  For safety sake, you should stop sendmail
662	while doing this and run the upgrade when locally sourced email
663	is not likely to be generated.
664
66520000825:
666	/boot/device.hints is now required for installkernel to
667	succeed.  You should copy GENERIC.hints for your architecture
668	into /boot/device.hints.  If and only if you compile hints
669	into your kernel, then this file may be empty.  Please note,
670	if you have an empty or missing /boot/device.hints file and
671	you neglected to compile hints into your kernel, no boot
672	messages will appear after the boot loader tries to start the
673	kernel.
674
67520000821:
676	If you do NOT have ``options RANDOMDEV'' in your kernel and
677	you DO want the random device then add randomdev_load="YES" to
678	/boot/loader.conf.
679
68020000812:
681	suidperl is now always built and installed on the system, but
682	with permissions of 511.  If you have applications that use
683	this program, you are now required to add ENABLE_SUIDPERL=true
684	to /etc/make.conf.  If you forget to do this,
685		chmod 4511 /usr/bin/suidperl
686	will fix this until the next build.
687
68820000812:
689	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
690	visible changes that may immediately affect your configuration
691	include:
692	- New default file locations from src/contrib/sendmail/cf/README
693	- newaliases limited to root and trusted users
694	- MSA port (587) turned on by default
695	- New queue file naming system so can't go from 8.11 -> 8.9
696	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
697	- FEATURE(`nullclient') is more full featured
698	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
699	- mail.local FreeBSD-only -b option changed to -B
700	- See src/contrib/sendmail/RELEASE_NOTES for more info
701
70220000810:
703	suidperl (aka sperl) is no longer build by default.  You must
704	specifically define BUILD_SUIDPERL to "true" for it to be build.
705	Furthermore, we recommend that you remove /usr/bin/sperl* and
706	/usr/bin/suidperl files from your system unless you have a
707	specific use for it.
708
70920000729:
710	Networking defaults have been tightened.  Anybody upgrading
711	/etc/defaults/rc.conf needs to add the following lines to
712	/etc/rc.conf if they want to have the same setup
713	afterwards (unless the variables already are set, of course):
714		# Enable network daemons for user convenience.
715		inetd_enable="YES"
716		portmap_enable="YES"
717		sendmail_enable="YES"
718
71920000728:
720	If you have null_load="YES" in your /boot/loader.conf, you
721	will need to change that to nullfs_load="YES".
722
72320000728:
724	The "installkernel" target has changed slightly. Now even if
725	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
726	it will install the MYKERNEL file (built with the buildkernel
727	target) as /kernel rather than /MYKERNEL. Those who have
728	updated their /boot/loader.conf files to point to /MYKERNEL
729	should remove that entry or perform manual rename of /kernel
730	to /MYKERNEL.
731
73220000711:
733	If you use CVSUP or CTM to get CVS trees, AND you used to get 
734	the old crypto files from internat.freebsd.org AND you check
735	out files from the CVS tree with the cvs command, please read
736		http://people.freebsd.org/~imp/internat.txt
737	for details on potential problems that you might have and how
738	to get around them.
739
740	If you are merely a mirror, or don't answer yes to each of the
741	clauses above, you needn't worry.
742
74320000711:
744	/etc/security has been updated to print the inode number of
745	setuid programs that have changed.  You will see a large spike
746	in the number of changed programs the first time when you run
747	mergemaster to get a new /etc/security.
748
74920000710:
750	/dev/random now has good entropy collection (from the keyboard
751	and sysmouse drivers). Please ensure that either `options
752	RANDOMDEV' is present in your kernel config file or that
753	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
754	not have the /dev/random driver, OpenSSL (and consequently
755	lots of crypto tools (like SSH)) will fail with strange
756	errors. (see below, 20000624).
757
758	FreeBSD-current is safe again to run Crypto.
759
76020000709:
761	phk made the malloc default options AJ.  This may slow things
762	down and uncover other latent bugs in the code.  If you need to
763	run at full speed, you can disable this by doing the following:
764		ln -s aj /etc/malloc.conf
765
76620000706:
767	libftpio's version was accidentally bumped a few days ago.  This
768	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
769	before doing your next buildworld/installworld pair.  It certainly
770	won't hurt to remove it before the update procedure.  It will
771	break fetch until a new one is built, but ftp can be used in the
772	interim if needed.
773
77420000705:
775	The crypto packages have changed for the cvsup.  This has been done
776	in a backward compatible way, but the old packages will go away at
777	some point in the future.  Look at /usr/share/examples/cvsup for
778	details.
779
78020000704:
781	With the new sys/modules/sound/drivers/*, you will need to
782	set SYSDIR until you do an installworld after July 7th.
783
78420000704:
785	rc.shutdown and rc will now call the rc.d scripts with start
786	or stop.  This may cause some harmless warnings from older
787	rc.d scripts that haven't been updated.
788
78920000630:
790	The libfetch based version of fetch has gone into the tree.
791	Minor problems may result on some of the less popular sites,
792	which should be reported to des@freebsd.org.
793
79420000625:
795	From approximately this date forward, one must have the crypto
796	system installed in order to build the system and kernel.
797	While not technically strictly true, one should treat it as
798	required and grab the crypto bits.  If you are grabbing CVS
799	trees, src-all and cvs-crypto should be treated as if they
800	were required.  You should check with the latest collections
801	to make sure that these haven't changed.
802
80320000624:
804	Mark Murray just committed the first parts of a cleanup of
805	/dev/zero, et al.  This is also cleaning up /dev/random.
806	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
807	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
808	until Mark can merge in the fixes to this work in progress.
809	openssh and openssl should not be used to generate keys from this
810	date to the completion of the work.
811
812	If you must operate at this reduced level of security, add '
813	options RANDOMDEV' to your kernel or modload the randomdev
814	module.  You may also need to copy a new MAKEDEV to /dev and
815	recreate the random and urandom devices.
816
81720000622:
818	The license on the softupdates is now a standard 2 clause
819	BSD license.  You may need to remove your symbolic links
820	that used to be required when updating.
821
82220000621:
823	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
824	the config file update procedure.
825		http://people.freebsd.org/~imp/config-upd.html
826	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
827	isn't buildable.  However, you can generate a LINT file.
828
82920000620:
830	Binutils 2.10 have hit the tree, or will shortly.  As soon
831	as they do, the problem noted in 20000522 will be resolved and
832	that workaround will no longer be required.
833
83420000615:
835	phk removed the compatibility creation of wd devices in the
836	ad driver.  If you haven't done so already, you must update
837	your fstab, etc to use the ad devices instead of the wd
838	devices.
839
840	In addition, you'll need to update your boot blocks to a
841	more modern version, if you haven't already done so.  Modern
842	here means 4.0 release or newer (although older releases
843	may work).
844
84520000612:
846	Peter took an axe to config(8).  Be sure that you read his mail
847	on the topic before even thinking about updating.  You will
848	need to create a /boot/device.hints or add a hints directive
849	to your config file to compile them in statically.  The format
850	of the config file has changed as well.  Please see GENERIC or
851	NEWCARD for examples of the new format.
852
853	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
854	says that it has been fixed, assume that must use the hints mechanism
855	in the loader if you need to use a machine with very old ISA cards
856	in it.
857
85820000522:
859	A new set of binutils went into the tree today.  Anybody
860	building a kernel after this point is advised that they need
861	to rebuild their binutils (or better yet do a
862	buildworld/installworld) before building a new kernel.
863
864	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
865	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
866	is recommended that you don't set this option until the problem
867	is resolved.
868
86920000513:
870	The ethernet drivers were all updated to clean up the BPF handling.
871
87220000510:
873	The problems with boot blocks on the alphas have been corrected.
874	This will require some care in updating alphas.  A new libstand
875	is requires for the boot blocks to build properly.
876
87720000503:
878	Recompile all kld modules.  Proper version dependency info
879	is now available.
880
88120000502:
882	Modules have been disconnected from the buildworld tree and 
883	connected to the kernel building instead.
884
88520000427:
886	You may need to build gperf
887		cd /usr/src/gnu/usr.bin/gperf && make depend all install
888	when upgrading from 4.0 -> current.  The build system now uses
889	an option only in -current.
890
89120000417:
892	The method that we brand ELF binaries has changed to be more
893	acceptable to the binutils maintainers.  You will need to
894	rebrand your ELF binaries that aren't native.  One problem
895	binary is the Linux ldconfig.  After your make world, but
896	before you reboot, you'll need to issue:
897		brandelf -t Linux /compat/linux/sbin/ldconfig
898	if you have Linux compatibility enabled on your machine.
899
90020000320:
901	If you have really bad/marginal IDE drives, you may find they
902	don't work well.  Use pio mode instead.  The easiest way to
903	cope if you have a problem combination is to add:
904		/sbin/sysctl hw.ata.ata_dma=0
905	to the start of /etc/rc.conf.
906
90720000319:
908	The ISA and PCI compatibility shims have been connected to the
909	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
910	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
911	include the appropriate option in your kernel config.  Drivers
912	using the shims should be updated or they won't ship with
913	5.0-RELEASE, targeted for 2001.
914
91520000318:
916	We've entered the traditional post release dumping party.
917	Large kernel changes are being committed and are in the
918	works.  It is important to keep the systems' klds and kernel
919	in sync as kernel interfaces and structures are changing.
920	Before reporting kernel panics, make sure that all modules
921	that you are loading are up to date.
922
92320000315:
924	If you are upgrading from an older version of FreeBSD, you
925	need to update your boot blocks as well.  'disklabel -B ad0'
926	will do the trick.  This isn't critical until you remove your
927	wd device entries in /dev, at which point your system will not
928	boot.
929
93020000315:
931	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
932	to upgrade to 4.0 from 3.x.
933
934COMMON ITEMS:
935
936	General Notes
937	-------------
938	Avoid using make -j when upgrading.  From time to time in the
939	past there have been problems using -j with buildworld and/or
940	installworld.  This is especially true when upgrading between
941	"distant" versions (eg one that cross a major release boundary
942	or several minor releases, or when several months have passed
943	on the -current branch).
944
945	Sometimes, obscure build problems are the result of environment
946	poisoning.  This can happen because the make utility reads its
947	environment when searching for values for global variables.
948	To run your build attempts in an "environmental clean room",
949	prefix all make commands with 'env -i '.  See the env(1) manual
950	page for more details.
951
952	To build a kernel
953	-----------------
954	If you are updating from a prior version of FreeBSD (even one just
955	a few days old), you should follow this procedure. With a
956	/usr/obj tree with a fresh buildworld,
957	make buildkernel KERNCONF=YOUR_KERNEL_HERE
958	make installkernel KERNCONF=YOUR_KERNEL_HERE
959
960	To just build a kernel when you know that it won't mess you up
961	--------------------------------------------------------------
962	cd src/sys/{i386,alpha}/conf
963	config KERNEL_NAME_HERE
964	cd ../../compile/KERNEL_NAME_HERE
965	make depend
966	make
967	make install	
968
969	If this fails, go to the "To build a kernel" section.
970
971	To rebuild everything and install it on the current system.
972	-----------------------------------------------------------
973	make world
974	Build a new kernel, see above.
975
976	To upgrade from 4.x-stable to current
977	-------------------------------------
978	make buildworld
979	make buildkernel KERNCONF=YOUR_KERNEL_HERE
980	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
981	make installkernel KERNCONF=YOUR_KERNEL_HERE
982	reboot in single user [3]
983	mergemaster -p		[5]
984	make installworld
985	mergemaster		[4]
986	[1]
987	<reboot>
988
989	Make sure that you've read the UPDATING file to understand the
990	tweaks to various things you need.  At this point in the life
991	cycle of current, things change often and you are on your own
992	to cope.  The defaults can also change, so please read ALL of
993	the UPDATING entries.
994
995	Also, if you are tracking -current, you must be subscribed to
996	freebsd-current@freebsd.org.  Make sure that before you update
997	your sources that you have read and understood all the recent
998	messages there.  If in doubt, please track -stable which has
999	much fewer pitfalls.
1000
1001	[1] If you have third party modules, such as vmware, you
1002	should disable them at this point so they don't crash your
1003	system on reboot.
1004
1005	[2] If you have legacy ISA devices, you may need to create
1006	your own device.hints to reflect your unique hardware
1007	configuration.
1008
1009	[3] From the bootblocks, boot -s, and then do
1010		fsck -p
1011		mount -u /
1012		mount -a
1013		cd /usr/src
1014		adjkerntz -i		# if CMOS is wall time
1015	Also, when doing a major release upgrade, it is required that
1016	you boot into single user mode to do the installworld.
1017
1018	[4] Note: This step is non-optional.  Failure to do this step
1019	can result in a significant reduction in the functionality of the
1020	system.  Attempting to do it by hand is not recommended and those
1021	that pursue this avenue should read this file carefully, as well
1022	as the archives of freebsd-current and freebsd-hackers mailing lists
1023	for potential gotchas.
1024
1025	[5] Usually this step is a noop.  However, from time to time
1026	you may need to do this if you get unknown user in the following
1027	step.  It never hurts to do it all the time.  You may need to
1028	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1029	install) after the buildworld before this step if you last updated
1030	from current before 20020224 or from -stable before 20020408.
1031
1032FORMAT:
1033
1034This file contains a list, in reverse chronological order, of major
1035breakages in tracking -current.  Not all things will be listed here,
1036and it only starts on March 15, 2000.  Updating files can found in
1037previous releases if your system is older than this.
1038
1039Copyright information:
1040
1041Copyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1042
1043Redistribution, publication, translation and use, with or without
1044modification, in full or in part, in any form or format of this
1045document are permitted without further permission from the author.
1046
1047THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1048IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1049WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1050DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1051INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1052(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1053SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1054HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1055STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1056IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1057POSSIBILITY OF SUCH DAMAGE.
1058
1059If you find this document useful, and you want to, you may buy the
1060author a beer.
1061
1062Contact Warner Losh if you have any questions about your use of
1063this document.
1064
1065$FreeBSD: head/UPDATING 101911 2002-08-15 08:51:24Z ru $
1066