UPDATING revision 89849
1Updating Information for FreeBSD current users
2
3This file is maintained and copyrighted by M. Warner Losh
4<imp@village.org>.  Please send new entries directly to him.  See end
5of file for further details.  For commonly done items, please see the
6COMMON ITEMS: section later in the file.
7
820020112:
9	The preferred configuration method for PAM is now /etc/pam.d/
10	rather than /etc/pam.conf.  If you have an unmodified
11	pam.conf, just delete it after your next mergemaster run.  If
12	you have local modifications, you can use
13	/usr/src/etc/pam.d/convert.pl to incorporate them into your
14	/etc/pam.d.
15
16	Please see the following url for more details:
17http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
18
1920011229:
20	If anyone here is already using the new rc.conf(5) variable
21	networkfs_types, please note that it has changed
22http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
23
2420011220:
25	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
26	started out its life in the ISDN4BSD project as an offspring
27	from sys/net/if_spppsubr.c, which eventually got a life of its
28	own.  All the accumulated features and bugfixes of the i4b
29	version have now been merged back into the base system's
30	version now.  The only user-visible change resulting from this
31	is that i4b's sppp(4) interfaces are to be managed with
32	spppcontrol(8) again, since ispppcontrol(8) has been retired
33	as well.  (There has never been rc file support for
34	ispppcontrol in -current, but only in -stable.  That will be
35	reverted by the time the changes are MFCed.)
36
3720011215:
38	The fdc(4) driver has been updated and now automatically
39	recognizes media in `standard' formats (like 1440 KB and
40	720 KB for a 3.5" high-density drive) when accessing the
41	default device node (e. g. /dev/fd0).  The old variety of
42	floppy device nodes /dev/fd*.* is no longer present by
43	default, devices can be created (in DEVFS) on demand.  They
44	will need to be customized then for `odd' densities using
45	fdcontrol(8).
46
4720011209:
48	The bugs in procfs' debugging support code have been fixed,
49	and truss(1) now works again.
50
5120011207:
52	Daily security checks have been split out to use the periodic(8)
53	scripts.  Some change in configuration may be necessary.  Please
54	see 
55http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
56	for details.
57
5820011204:
59	sos added VCD/SVCD support to ata driver and that needs the
60	kernel and burncd to be in sync.
61
6220011203:
63	The procfs pseudo-filesystem has now been converted to use the
64	pseudofs framework.  If you have 'options PROCFS' in your
65	kernel config, you'll need to add 'options PSEUDOFS' if it's
66	not there already.
67
68	This change temporarily breaks truss(1); use ktrace(1) instead
69	until the issue has been resolved.
70
7120011202:
72	A security hole in OpenSSH involving `UseLogin yes' has been
73	patched.
74
7520011126:
76	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
77	after this date.  You need to do this only once.
78
7920011103:
80	Most of the awk issues have been resolved.  Some rough
81	edges may be left, but for the most part things should be
82	back to "normal." For CURRENT's usual definition of "normal."
83
8420011030:
85	Awk has been upgraded to the one true awk from bell labs.  Expect
86	choppy waves in the upgrade process.
87
8820011030:
89	The asr driver problem has been resolved.
90
9120011027:
92	Due to changes in other parts of the system, the asr driver
93	now causes the system to panic on boot.  Do not use it pending
94	correction.  Comment it out of any kernel config file that you
95	try to use from this date forward.
96
9720011025:
98	When crossbuilding, use TARGET=xxx where you used to use
99	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
100	unless you are changing both of them.  To cross build pc98 on
101	an alpha, for example, you need to set TARGET=pc98 and
102	TARGET_ARCH=i386.
103
10420011001:
105	The kernel interface that burncd depends on has changed.
106	You must recompile both the kernel and userland applications
107	at the same time.
108
10920010929:
110	When crossbuilding, please set TARGET_ARCH rather than
111	MACHINE_ARCH to indicate the target.  In the future, one will
112	set TARGET_MACHINE where you set MACHINE now.  At the moment,
113	setting MACHINE alone for same MACHINE_ARCH machines works
114	(eg, you can build pc98 on a i386 machine and vice versa).
115
11620010927:
117	Some weird problems result from using ACPI on some machines.
118	To disable ACPI you can add
119		hint.acpi.0.disable="1"
120	to /boot/loader.conf (or by putting set X=Y at the boot
121	loader "ok" prompt).
122
123	Alternatively, you can remove it from /boot/kernel/acpi.ko
124	or use the MODULES_OVERRIDE function in your kernel config
125	file and not list acpi in that list.
126
12720010924:
128	The buildworld has been fixed.  You may need to install
129	the 4.x compatibility libraries for some old binaries
130	to work.  Add COMPAT4X=true to your /etc/make.conf to
131	get them installed on every installworld, or execute the
132	following to get them installed only once:
133		cd src/lib/compat/compat4x.<arch>
134		make all install
135	You will see ``__stdoutp undefined'' until you do this.
136
13720010919:
138	There's a bug in the world build process.  The cross-tools
139	are build with the NEW headers, but the OLD libc.a.  This
140	leads to all kinds of problems with the new libc.  A temporary
141	workaround is to add
142		CFLAGS="-O -pipe -D_OLD_STDIO"
143	before building world when upgrading from 4.x to current.  This
144	can be removed afterwards.
145
146	A proper fix to the buildworld target is needed.
147
14820010918:
149	Peter has committed his new kthread nfs client/server code.
150	NFS may be unstable after this date.
151
15220010912:
153	KSE has hit the tree.  Lots of things are now different in
154	the kernel.  While a few problems were introduced in the
155	initial commit, most of the major ones have been found and
156	corrected.
157
15820010901:
159	In OLDCARD, CardBus bridges appear to be stable.  The work
160	arounds described in the 20010604 entry are now no longer
161	necessary and will be ignored.  Most insert/remove problems
162	have been rectified around this date.
163
16420010823:
165 	named now runs as user bind and group bind rather than as 
166 	root.  If named_enable is set to YES in /etc/rc.conf, ensure 
167 	that user bind is available in /etc/passwd (using vipw(8)) 
168 	and that group bind is available in /etc/group.  Also make 
169 	sure that user or group bind has read (and not write) 
170 	permission for your name server configuration and that it 
171 	has read and write permission for your slave zone files and 
172 	directory.
173 
174 	If you wish to continue to run named as root (a less secure 
175 	alternative), add a line to /etc/rc.conf saying
176 
177 		named_flags=
178
17920010709:
180	The PAM libraries have had an API upgrade that is beyond
181	the ability of the shared library major number to handle.
182	It is manifested by PAM-using ports dumping core. The
183	solution is to rebuild those ports.
184
18520010628:
186	The kernel compile module has moved from src/sys/compile/FOO
187	to src/sys/${MACHINE}/compile/FOO.
188
18920010625:
190	The pccard modem issue from 20010613 has been corrected.
191	OLDCARD support is still a little weak in -current.  slot 1 is
192	known not to work on some TI based cardbus bridges.  Some
193	cardbus bridges do not properly detect insert/removal events.
194	IRQ configuration needs more safety belts.
195
19620010617:
197	Softupdates problems have been corrected.
198
19920010614:
200	Peter ripped out the linkerset support.  You must, as always,
201	rerun config after you cvsup if you are using the traditional
202	kernel building methods.
203
20420010613:
205	pccard modems may not work with current after 20010604 date.  Some
206	do, others result in panics.  *MAKE*SURE* that you update your
207	config and /etc/rc.conf ala the 20010604 entry, or you will have
208	problems (this issue will be fixed, it just hasn't been yet).
209
21020010613:
211	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
212	use them in current.  You can disable softupdates on all mounted
213	partitions, or remove SOFTUPDATES the kernel config file.
214
21520010612:
216	After Peter's commits to the hints code, people have been noticing
217	that certain devices are attached (or try to) twice.  This is due
218	to having both static hints as well as a /boot/device.hints.  To
219	work around this issue, please use only one or the other mechanism
220	until this bug is fixed.
221
222	Please note that a feature of config is that if you have config
223	file FOO and FOO.hints, it automatically adds FOO.hints to the
224	hints.c file, wheather you want it to or not.
225
22620010610:
227	Locale names have changed to match other systems better.
228
22920010604:
230	pccard support for pci cards has been committed.  You must change
231	your /etc/pccard.conf irq lines.  It must match the irq used by
232	pcic device.  Interrupt storms may result if you fail to do this.
233	Interrupt storms look a lot like a hang.
234
235	You must also install a new pccardd, otherwise you will get an
236	interrupt storm at card reset time (just after it tells you what
237	it is).
238
239	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
240	not to ask the kernel if the interrupt is really free or not before
241	using it.  You can either change the /etc/pccard.conf irq lines to
242	match pcic, or add "-i X" to the pccardd_flags.
243
24420010530:
245	INSTALL=install -C is being deprecated.  If you want to do this,
246	use COPY=-C instead.  The former method will be supported for only
247	a limited time.  If you see
248
249install: warning: the -d and -C options may not be specified together
250
251	in your makeworld, then you need to migrate towards using
252	COPY=-C.
253
25420010525:
255	It appears that vm is now stable enough to use again.  However,
256	there may be other problems, so caution is still urged.  alpha
257	definitely is in bad shape.
258
25920010521:
260	Minor repo damange has happened.  This may cause problems
261	with cvsup of ports.  If you get errors, please see
262	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
263	at the bottom for details on a workaround.  The error message
264	is
265Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
266
26720010520:
268	Vm and/or swapping are busted on -current.  Please be patient.
269
27020010519:
271	pccard has had much reorganizational work done to it over
272	the past few days.  Everything should still work, but if
273	not, please contact imp@freebsd.org.
274
27520010517:
276	ata ioctl changed.  Make sure to recompile both kernel and
277	userland at the same time.
278
27920010517:
280	New ncurses imported.
281
28220010512:
283	DEVFS is now opt out, not opt in.  Barring major problems, this
284	will be the only way to go starting July 1.
285
28620010504:
287	OpenSSH has been updated to 2.9.  Some defaults are different,
288	including RhostsRSAAuthentication, which changes from yes to no.
289
29020010502:
291	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
292
29320010501:
294	Building perl was broken at 02:25:25 PDT.
295
29620010430:
297	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
298	go back in the water.
299
30020010429:
301	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
302	this date, but before the correction date.
303
30420010423:
305	old fsck and new kernel interactions appear to have been fixed.
306
30720010411:
308	fsck and the kernel were changed to handle some optimizations
309	to directory layout.  This breaks backward compatibility.
310	Update only if you understand that you must not use the old
311	fsck with the new kernel ever.
312
31320010330:
314	fsck has changed the meaning of the pass column in /etc/fstab.
315	Please see the cvs commit to fsck.8 or the fsck.8 man page for
316	details.  It is unclear if changes to /etc/fstab are necessary.
317
31820010319:
319	portmap had changed name to rpcbind for maximum POLA in your
320	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
321	other rpc based programs that rely on portmapper will not work
322	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
323
32420010315:
325	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
326	and ATA_ENABEL_TAGS are no longer kernel options.  They have
327	been replaced by tunables.  See ata.4 for details.
328
32920010312:
330	The fxp driver was converted to use miibus.  If you compile
331	fxp into your kernel statically, you will need to add miibus.
332
33320010312:
334	The wi device now defaults to BSS (infrastructure) mode
335	instead of ad-hoc.
336
33720010310:
338	/dev/urandom should be a symbolic link to /dev/random now.
339	Users of current not using DEVFS need to run MAKEDEV std.
340	ssh might not work if you don't.
341
34220010303:
343	The ed driver has been updated.  It now allows mii attachments,
344	which means that you must include the miibus in your kernel if
345	you use the ed driver.
346
34720010220:
348	The problems with libc have been corrected.  It is now mostly
349	safe to go back into the water.
350
35120010211:
352	The size of FILE was changed.  This breaks upgrading.  If
353	you must upgrade, be prepared for pain.  It also breaks almost
354	all binaries that you've compiled on -current.  You are warned
355	that before upgrading would be a good time to do a level 0
356	dump of your system.  No, really, I mean it this time.
357
358	To get to the new system, you'll need to use the following
359	workaround.  Hopefully this can be sorted out so that we
360	don't have to move this to the updating section.
361
362	To get around the installworld problem, do:
363		# cd /usr/src/usr.bin/sed
364		# make install
365		# cd /usr/src
366		# make installworld
367	If that doesn't work, then try:
368		# make -k installworld
369		# make installworld
370
37120010207:
372	DEVFS is now the default.  If you use vinum, make sure that you
373	do not include devfs in your kernel as problems result.
374
37520010205:
376	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
377	Remove them from your config.
378
37920010122:
380	****************************** WARNING ******************************
381			buildkernel has been changed slightly
382	****************************** WARNING ******************************
383	KERNCONF replaces the variable KERNEL for buildkernel.  You
384	should update your scripts and make.conf accordingly.
385
38620010119:
387	config has changed to allow DEV_FOO as a replacement for NFOO.
388	This requires a new config to build correctly.
389
39020010116:
391	The kerrnel option I386_CPU is now mutually exclusive with the
392	other cpu types. If you have an i386 system, be sure that it
393	only had this line.  Remove it for all other configurations.
394
39520010110:
396	Changes to the kernel require it and burncd be in sync.
397
39820010102:
399	Everyone who has hw.sndunit set to something in
400	/etc/sysctl.conf, it is now hw.snd.unit.
401
40220010101:
403	ex and vi were broken by some changes to sys/queue.h.  If you
404	have a bad vi, you will see make buildworld fail with a core
405	dump while building termcap.  You can work around this problem
406	by adding -k to your make buildworld.  This will cause the
407	build to complete and install a new vi.  Once that's done, you
408	can rebuild again without the -k to pick up anything that
409	might have been ignored by the -k option.
410
411	Others have suggested that you can just rebuild libc if your
412	vi/ex is dynamically linked, but I've not received any reports
413	of this working.
414
41520001228:
416	There have been some changes to libcrypt in -current.  The
417	libscrypt/libdescrypt symlink sillyness is gone and the installed
418	libcrypt is fully functional.  Be aware of this.
419
42020001218:
421	Linksys Fast Ethernet PCCARD cards supported by the ed driver
422	now require the addition of flag 0x80000 to their config line
423	in pccard.conf(5).  This flag is not optional.  These Linksys
424	cards will not be recognized without it.
425
42620001205:
427	Important new FreeBSD-version stuff: PAM support has been worked
428	in, partially from the "Unix" OpenSSH version.  This requires
429	adding the following in pam.conf:
430  
431	sshd    auth    sufficient      pam_skey.so
432	sshd    auth    required        pam_unix.so         try_first_pass
433	sshd    session required        pam_permit.so
434
43520001031:
436	cvs updated to 1.11.
437
43820001020:
439	The random device needs more entropy, so you need to make sure
440	that you've run mergemaster to get a /etc/rc which will seed
441	/dev/random.  If you don't and the system hangs after ldconfig,
442	then banging on the keyboard randomly until it unhangs is one
443	workaround.
444
44520001010:
446	****************************** WARNING ******************************
447				Sendmail has been updated.
448	****************************** WARNING ******************************
449	o mail.local(8) is no longer installed as a set-user-id binary.
450	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
451	  is set.
452	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
453	  commands.
454	o Now using sendmail's version of vacation(1).
455	o The sendmail cf building tools (contrib/sendmail/cf) are installed
456	  in /usr/share/sendmail/cf.
457	o sendmail.cw changed to local-host-names
458
459	More details can be found at
460		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
461
46220001009:
463	The ports tree's new layout is in place.  Be sure to update
464	your entire ports tree, or you will have problems.
465
46620001006:
467	The perl build procedure no longer installs miniperl, nor uses
468	the installed miniperl.  It is recommended that you delete
469	/usr/bin/miniperl.
470
47120001005:
472	This weekend the ports tree will be updated to a new layout.
473	It will be in an inconsistent state until noted in the UPDATING
474	file, or with asami-san's message to the relevant mailing
475	lists.  With this new layout, you'll need to update the whole
476	tree for anything to work.
477
47820000928:
479	There was a change in the passwd format.  Need more information.
480
48120000916:
482	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
483	place.  Please update boot loader (not the boot blocks) at the
484	same time as your kernel.
485
48620000914:
487	The new pmtimer device is necessary for laptops.  Failure to
488	include the device will cause suspended laptops losing time
489	when they resume.  Include
490		device		pmtimer
491	in your config file and
492		hint.pmtimer.0.at="isa"
493	to your /boot/device.hints file.
494
49520000911:
496	The random device has been turned into a (pseudo-)device,
497	rather than an option. The supplied kernel config files have
498	been updated. You will need to do something similar in your
499	own kernel config file.
500	Remove:
501		options		RANDOMDEV
502	Add:
503		device		random
504	If you prefer to load the loadable module, you need to do
505	nothing.
506
50720000909:
508	The random device module has been renamed from randomdev.ko to
509	random.ko. You will need to edit your /boot/loader.conf to
510	reflect this if you load this module at boot time.
511	The line should read:
512		random_load="YES"
513
51420000907:
515	The SMPNG commit has happened.  It should work, but if it
516	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
517	to be a variety of minor issues.  Please see 20000905 to make
518	sure you don't have model loading problems which might at
519	first blush appear related to SMP.
520
52120000906:
522	nsswitch has been imported from NetBSD.  Among other things,
523	this means that /etc/host.conf is no longer used.  See
524	nsswitch.conf(5) instead.  Note that at boot time rc.network
525	will attempt to produce a new nsswitch.conf file for you if you
526	don't have one, and you have host.conf.
527
52820000905:
529	The ucred structure changed size.  This breaks the interface
530	that mountd uses.  Trying to use an older mountd with a newer
531	kernel guarantees a panic.  This means that you need to use
532	kernels newer than today only with matching mountd, but you
533	needed to do that anyway with the boot loader changes.
534
53520000905:
536	The boot loader has been updated.  The new default kernel is
537	now /boot/kernel/kernel.ko.  The new default module location
538	is /boot/kernel.
539
540	You *MUST* upgrade your boot loader and kernel at the same time.
541	The easiest way to do this is to do the buildworld/buildkernel/
542	installkernel/installworld dance.
543
544	Furthermore, you are urged to delete your old /modules directory
545	before booting the new kernel, since kldload will find stale
546	modules in that directory instead of finding them in the correct
547	path, /boot/kernel.  The most common complaint that this cures
548	is that the linux module crashes your machine after the update.
549
550	if [ ! -d /boot/kernel.old ]; then
551		mv /modules.old /boot/kernel.old
552		chflags noschg /kernel.old
553		mv /kernel.old /boot/kernel.old/kernel.ko
554		chflags schg /boot/kernel.old/kernel.ko
555	fi
556
55720000904:
558	A new issue with the sendmail upgrade has come to light.
559	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
560	incorrectly install the default aliases in /etc/mail rather than
561	move the old one from /etc.  So you'll need to manually move the
562	file, create a symbolic link, remove the old /etc/aliases.db and
563	run newaliases.  For safety sake, you should stop sendmail
564	while doing this and run the upgrade when locally sourced email
565	is not likely to be generated.
566
56720000825:
568	/boot/device.hints is now required for installkernel to
569	succeed.  You should copy GENERIC.hints for your architecture
570	into /boot/device.hints.  If and only if you compile hints
571	into your kernel, then this file may be empty.  Please note,
572	if you have an empty or missing /boot/device.hints file and
573	you neglected to compile hints into your kernel, no boot
574	messages will appear after the boot loader tries to start the
575	kernel.
576
57720000821:
578	If you do NOT have ``options RANDOMDEV'' in your kernel and
579	you DO want the random device then add randomdev_load="YES" to
580	/boot/loader.conf.
581
58220000812:
583	suidperl is now always built and installed on the system, but
584	with permissions of 511.  If you have applications that use
585	this program, you are now required to add ENABLE_SUIDPERL=true
586	to /etc/make.conf.  If you forget to do this,
587		chmod 4511 /usr/bin/suidperl
588	will fix this until the next build.
589
59020000812:
591	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
592	visible changes that may immediately affect your configuration
593	include:
594	- New default file locations from src/contrib/sendmail/cf/README
595	- newaliases limited to root and trusted users
596	- MSA port (587) turned on by default
597	- New queue file naming system so can't go from 8.11 -> 8.9
598	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
599	- FEATURE(`nullclient') is more full featured
600	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
601	- mail.local FreeBSD-only -b option changed to -B
602	- See src/contrib/sendmail/RELEASE_NOTES for more info
603
60420000810:
605	suidperl (aka sperl) is no longer build by default.  You must
606	specifically define BUILD_SUIDPERL to "true" for it to be build.
607	Furthermore, we recommend that you remove /usr/bin/sperl* and
608	/usr/bin/suidperl files from your system unless you have a
609	specific use for it.
610
61120000729:
612	Networking defaults have been tightened.  Anybody upgrading
613	/etc/defaults/rc.conf needs to add the following lines to
614	/etc/rc.conf if they want to have the same setup
615	afterwards (unless the variables already are set, of course):
616		# Enable network daemons for user convenience.
617		inetd_enable="YES"
618		portmap_enable="YES"
619		sendmail_enable="YES"
620
62120000728:
622	If you have null_load="YES" in your /boot/loader.conf, you
623	will need to change that to nullfs_load="YES".
624
62520000728:
626	The "installkernel" target has changed slightly. Now even if
627	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
628	it will install the MYKERNEL file (built with the buildkernel
629	target) as /kernel rather than /MYKERNEL. Those who have
630	updated their /boot/loader.conf files to point to /MYKERNEL
631	should remove that entry or perform manual rename of /kernel
632	to /MYKERNEL.
633
63420000711:
635	If you use CVSUP or CTM to get CVS trees, AND you used to get 
636	the old crypto files from internat.freebsd.org AND you check
637	out files from the CVS tree with the cvs command, please read
638		http://people.freebsd.org/~imp/internat.txt
639	for details on potential problems that you might have and how
640	to get around them.
641
642	If you are merely a mirror, or don't answer yes to each of the
643	clauses above, you needn't worry.
644
64520000711:
646	/etc/security has been updated to print the inode number of
647	setuid programs that have changed.  You will see a large spike
648	in the number of changed programs the first time when you run
649	mergemaster to get a new /etc/security.
650
65120000710:
652	/dev/random now has good entropy collection (from the keyboard
653	and sysmouse drivers). Please ensure that either `options
654	RANDOMDEV' is present in your kernel config file or that
655	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
656	not have the /dev/random driver, OpenSSL (and consequently
657	lots of crypto tools (like SSH)) will fail with strange
658	errors. (see below, 20000624).
659
660	FreeBSD-current is safe again to run Crypto.
661
66220000709:
663	phk made the malloc default options AJ.  This may slow things
664	down and uncover other latent bugs in the code.  If you need to
665	run at full speed, you can disable this by doing the following:
666		ln -s aj /etc/malloc.conf
667
66820000706:
669	libftpio's version was accidentally bumped a few days ago.  This
670	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
671	before doing your next buildworld/installworld pair.  It certainly
672	won't hurt to remove it before the update procedure.  It will
673	break fetch until a new one is built, but ftp can be used in the
674	interim if needed.
675
67620000705:
677	The crypto packages have changed for the cvsup.  This has been done
678	in a backward compatible way, but the old packages will go away at
679	some point in the future.  Look at /usr/share/examples/cvsup for
680	details.
681
68220000704:
683	With the new sys/modules/sound/drivers/*, you will need to
684	set SYSDIR until you do an installworld after July 7th.
685
68620000704:
687	rc.shutdown and rc will now call the rc.d scripts with start
688	or stop.  This may cause some harmless warnings from older
689	rc.d scripts that haven't been updated.
690
69120000630:
692	The libfetch based version of fetch has gone into the tree.
693	Minor problems may result on some of the less popular sites,
694	which should be reported to des@freebsd.org.
695
69620000625:
697	From approximately this date forward, one must have the crypto
698	system installed in order to build the system and kernel.
699	While not technically strictly true, one should treat it as
700	required and grab the crypto bits.  If you are grabbing CVS
701	trees, src-all and cvs-crypto should be treated as if they
702	were required.  You should check with the latest collections
703	to make sure that these haven't changed.
704
70520000624:
706	Mark Murray just committed the first parts of a cleanup of
707	/dev/zero, et al.  This is also cleaning up /dev/random.
708	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
709	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
710	until Mark can merge in the fixes to this work in progress.
711	openssh and openssl should not be used to generate keys from this
712	date to the completion of the work.
713
714	If you must operate at this reduced level of security, add '
715	options RANDOMDEV' to your kernel or modload the randomdev
716	module.  You may also need to copy a new MAKEDEV to /dev and
717	recreate the random and urandom devices.
718
71920000622:
720	The license on the softupdates is now a standard 2 clause
721	BSD license.  You may need to remove your symbolic links
722	that used to be required when updating.
723
72420000621:
725	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
726	the config file update procedure.
727		http://people.freebsd.org/~imp/config-upd.html
728	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
729	isn't buildable.  However, you can generate a LINT file.
730
73120000620:
732	Binutils 2.10 have hit the tree, or will shortly.  As soon
733	as they do, the problem noted in 20000522 will be resolved and
734	that workaround will no longer be required.
735
73620000615:
737	phk removed the compatibility creation of wd devices in the
738	ad driver.  If you haven't done so already, you must update
739	your fstab, etc to use the ad devices instead of the wd
740	devices.
741
742	In addition, you'll need to update your boot blocks to a
743	more modern version, if you haven't already done so.  Modern
744	here means 4.0 release or newer (although older releases
745	may work).
746
74720000612:
748	Peter took an axe to config(8).  Be sure that you read his mail
749	on the topic before even thinking about updating.  You will
750	need to create a /boot/device.hints or add a hints directive
751	to your config file to compile them in statically.  The format
752	of the config file has changed as well.  Please see GENERIC or
753	NEWCARD for examples of the new format.
754
75520000522:
756	A new set of binutils went into the tree today.  Anybody
757	building a kernel after this point is advised that they need
758	to rebuild their binutils (or better yet do a
759	buildworld/installworld) before building a new kernel.
760
761	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
762	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
763	is recommended that you don't set this option until the problem
764	is resolved.
765
76620000513:
767	The ethernet drivers were all updated to clean up the BPF handling.
768
76920000510:
770	The problems with boot blocks on the alphas have been corrected.
771	This will require some care in updating alphas.  A new libstand
772	is requires for the boot blocks to build properly.
773
77420000503:
775	Recompile all kld modules.  Proper version dependency info
776	is now available.
777
77820000502:
779	Modules have been disconnected from the buildworld tree and 
780	connected to the kernel building instead.
781
78220000427:
783	You may need to build gperf
784		cd /usr/src/gnu/usr.bin/gperf && make depend all install
785	when upgrading from 4.0 -> current.  The build system now uses
786	an option only in -current.
787
78820000417:
789	The method that we brand ELF binaries has changed to be more
790	acceptable to the binutils maintainers.  You will need to
791	rebrand your ELF binaries that aren't native.  One problem
792	binary is the Linux ldconfig.  After your make world, but
793	before you reboot, you'll need to issue:
794		brandelf -t Linux /compat/linux/sbin/ldconfig
795	if you have Linux compatibility enabled on your machine.
796
79720000320:
798	If you have really bad/marginal IDE drives, you may find they
799	don't work well.  Use pio mode instead.  The easiest way to
800	cope if you have a problem combination is to add:
801		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
802	to the start of /etc/rc.conf.
803
80420000319:
805	The ISA and PCI compatibility shims have been connected to the
806	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
807	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
808	include the appropriate option in your kernel config.  Drivers
809	using the shims should be updated or they won't ship with
810	5.0-RELEASE, targeted for 2001.
811
81220000318:
813	We've entered the traditional post release dumping party.
814	Large kernel changes are being committed and are in the
815	works.  It is important to keep the systems' klds and kernel
816	in sync as kernel interfaces and structures are changing.
817	Before reporting kernel panics, make sure that all modules
818	that you are loading are up to date.
819
82020000315:
821	If you are upgrading from an older version of FreeBSD, you
822	need to update your boot blocks as well.  'disklabel -B ad0'
823	will do the trick.  This isn't critical until you remove your
824	wd device entries in /dev, at which point your system will not
825	boot.
826
82720000315:
828	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
829	to upgrade to 4.0 from 3.x.
830
831COMMON ITEMS:
832
833	General Notes
834	-------------
835	Avoid using make -j when upgrading.  From time to time in the
836	past there have been problems using -j with buildworld and/or
837	installworld.  This is especially true when upgrading between
838	"distant" versions (eg one that cross a major release boundary
839	or several minor releases, or when several months have passed
840	on the -current branch).
841
842	Sometimes, obscure build problems are the result of environment
843	poisoning.  This can happen because the make utility reads its
844	environment when searching for values for global variables.
845	To run your build attempts in an "environmental clean room",
846	prefix all make commands with 'env -i '.  See the env(1) manual
847	page for more details.
848
849	To build a kernel
850	-----------------
851	If you are updating from a prior version of FreeBSD (even one just
852	a few days old), you should follow this procedure. With a
853	/usr/obj tree with a fresh buildworld,
854	make buildkernel KERNCONF=YOUR_KERNEL_HERE
855	make installkernel KERNCONF=YOUR_KERNEL_HERE
856
857	To just build a kernel when you know that it won't mess you up
858	--------------------------------------------------------------
859	cd src/sys/{i386,alpha}/conf
860	config KERNEL_NAME_HERE
861	cd ../../compile/KERNEL_NAME_HERE
862	make depend
863	make
864	make install	
865
866	If this fails, go to the "To build a kernel" section.
867
868	To rebuild everything and install it on the current system.
869	-----------------------------------------------------------
870	make world
871	Build a new kernel, see above.
872
873	To upgrade from 4.x-stable to current
874	-------------------------------------
875	make buildworld
876	make buildkernel KERNCONF=YOUR_KERNEL_HERE
877	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
878	make installkernel KERNCONF=YOUR_KERNEL_HERE
879	reboot in single user [3]
880	make installworld
881	mergemaster		[4]
882	[1]
883	<reboot>
884
885	Make sure that you've read the UPDATING file to understand the
886	tweaks to various things you need.  At this point in the life
887	cycle of current, things change often and you are on your own
888	to cope.  The defaults can also change, so please read ALL of
889	the UPDATING entries.
890
891	Also, if you are tracking -current, you must be subscribed to
892	freebsd-current@freebsd.org.  Make sure that before you update
893	your sources that you have read and understood all the recent
894	messages there.  If in doubt, please track -stable which has
895	much fewer pitfalls.
896
897	[1] If you have third party modules, such as vmware, you
898	should disable them at this point so they don't crash your
899	system on reboot.
900
901	[2] If you have legacy ISA devices, you may need to create
902	your own device.hints to reflect your unique hardware
903	configuration.
904
905	[3] From the bootblocks, boot -s, and then do
906		fsck -p
907		mount -u /
908		mount -a
909		cd /usr/src
910		adjkerntz -i		# if CMOS is wall time
911
912	[4] Note: This step is non-optional.  Failure to do this step
913	can result in a significant reduction in the functionality of the
914	system.  Attempting to do it by hand is not recommended and those
915	that pursue this avenue should read this file carefully, as well
916	as the archives of freebsd-current and freebsd-hackers mailing lists
917	for potential gotchas.
918
919FORMAT:
920
921This file contains a list, in reverse chronological order, of major
922breakages in tracking -current.  Not all things will be listed here,
923and it only starts on March 15, 2000.  Updating files can found in
924previous releases if your system is older than this.
925
926Please filter your entries through Warner Losh (imp@village.org) so
927that the style, formatting, etc of this file can be maintained.
928
929Copyright information:
930
931Copyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
932
933Redistribution, publication, translation and use, with or without
934modification, in full or in part, in any form or format of this
935document are permitted.
936
937THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
938IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
939WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
940DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
941INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
942(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
943SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
944HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
945STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
946IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
947POSSIBILITY OF SUCH DAMAGE.
948
949If you find this document useful, and you want to, you may buy the
950author a beer.
951
952Contact Warner Losh if you have any questions about your use of
953this document.
954
955$FreeBSD: head/UPDATING 89849 2002-01-27 07:00:25Z imp $
956