UPDATING revision 79015
11590SrgrimesUpdating Information for FreeBSD current users
21590Srgrimes
31590SrgrimesThis file is maintained and copyrighted by M. Warner Losh
41590Srgrimes<imp@village.org>.  Please send new entries directly to him.  See end
51590Srgrimesof file for further details.  For commonly done items, please see the
61590SrgrimesCOMMON ITEMS: section later in the file.
71590Srgrimes
81590Srgrimes20010628:
91590Srgrimes	The kernel compile module has moved from src/sys/compile/FOO
101590Srgrimes	to src/sys/${MACHINE}/compile/FOO.
111590Srgrimes
121590Srgrimes20010625:
131590Srgrimes	The pccard modem issue has been corrected.  OLDCARD support is
141590Srgrimes	still a little weak in -current.  slot 1 is known not to work
151590Srgrimes	on some TI based cardbus bridges.  Some cardbus bridges do not
161590Srgrimes	properly detect insert/removal events.  IRQ configuration needs
171590Srgrimes	more safety belts.
181590Srgrimes
191590Srgrimes20010617:
201590Srgrimes	Softupdates problems have been corrected.
211590Srgrimes
221590Srgrimes20010614:
231590Srgrimes	Peter ripped out the linkerset support.  You must, as always,
241590Srgrimes	rerun config after you cvsup if you are using the traditional
251590Srgrimes	kernel building methods.
261590Srgrimes
271590Srgrimes20010613:
281590Srgrimes	pccard modems may not work with current after 20010604 date.  Some
291590Srgrimes	do, others result in panics.  *MAKE*SURE* that you update your
301590Srgrimes	config and /etc/rc.conf ala the 20010604 entry, or you will have
311590Srgrimes	problems (this issue will be fixed, it just hasn't been yet).
321590Srgrimes
331590Srgrimes20010613:
341590Srgrimes	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
351590Srgrimes	use them in current.  You can disable softupdates on all mounted
361590Srgrimes	partitions, or remove SOFTUPDATES the kernel config file.
371590Srgrimes
381590Srgrimes20010612:
391590Srgrimes	After Peter's commits to the hints code, people have been noticing
401590Srgrimes	that certain devices are attached (or try to) twice.  This is due
411590Srgrimes	to having both static hints as well as a /boot/device.hints.  To
421590Srgrimes	work around this issue, please use only one or the other mechanism
431590Srgrimes	until this bug is fixed.
441590Srgrimes
451590Srgrimes	Please note that a feature of config is that if you have config
461590Srgrimes	file FOO and FOO.hints, it automatically adds FOO.hints to the
471590Srgrimes	hints.c file, wheather you want it to or not.
481590Srgrimes
491590Srgrimes20010610:
501590Srgrimes	Locale names have changed to match other systems better.
511590Srgrimes
521590Srgrimes20010604:
531590Srgrimes	pccard support for pci cards has been committed.  You must change
541590Srgrimes	your /etc/pccard.conf irq lines.  It must match the irq used by
551590Srgrimes	pcic device.  Interrupt storms may result if you fail to do this.
561590Srgrimes	Interrupt storms look a lot like a hang.
571590Srgrimes
581590Srgrimes	You must also install a new pccardd, otherwise you will get an
591590Srgrimes	interrupt storm at card reset time (just after it tells you what
601590Srgrimes	it is).
611590Srgrimes
621590Srgrimes	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
631590Srgrimes	not to ask the kernel if the interrupt is really free or not before
641590Srgrimes	using it.  You can either change the /etc/pccard.conf irq lines to
651590Srgrimes	match pcic, or add "-i X" to the pccardd_flags.
661590Srgrimes
671590Srgrimes20010530:
681590Srgrimes	INSTALL=install -C is being deprecated.  If you want to do this,
691590Srgrimes	use COPY=-C instead.  The former method will be supported for only
701590Srgrimes	a limited time.  If you see
711590Srgrimes
721590Srgrimesinstall: warning: the -d and -C options may not be specified together
731590Srgrimes
741590Srgrimes	in your makeworld, then you need to migrate towards using
751590Srgrimes	COPY=-C.
761590Srgrimes
771590Srgrimes20010525:
781590Srgrimes	It appears that vm is now stable enough to use again.  However,
791590Srgrimes	there may be other problems, so caution is still urged.  alpha
801590Srgrimes	definitely is in bad shape.
811590Srgrimes
821590Srgrimes20010521:
831590Srgrimes	Minor repo damanged has happened.  This may cause problems
841590Srgrimes	with cvsup of ports.  If you get errors, please see
851590Srgrimes	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
861590Srgrimes	at the bottom for details on a workaround.  The error message
871590Srgrimes	is
881590SrgrimesUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
891590Srgrimes
901590Srgrimes20010520:
911590Srgrimes	Vm and/or swapping are busted on -current.  Please be patient.
921590Srgrimes
931590Srgrimes20010519:
941590Srgrimes	pccard has had much reorganizational work done to it over
951590Srgrimes	the past few days.  Everything should still work, but if
961590Srgrimes	not, please contact imp@freebsd.org.
971590Srgrimes
981590Srgrimes20010517:
991590Srgrimes	ata ioctl changed.  Make sure to recompile both kernel and
1001590Srgrimes	userland at the same time.
1011590Srgrimes
1021590Srgrimes20010517:
1031590Srgrimes	New ncurses imported.
1041590Srgrimes
1051590Srgrimes20010512:
1061590Srgrimes	DEVFS is now opt out, not opt in.  Barring major problems, this
1071590Srgrimes	will be the only way to go starting July 1.
1081590Srgrimes
1091590Srgrimes20010502:
1101590Srgrimes	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1111590Srgrimes
1121590Srgrimes20010501:
1131590Srgrimes	Building perl was broken at 02:25:25 PDT.
1141590Srgrimes
1151590Srgrimes20010430:
1161590Srgrimes	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
1171590Srgrimes	go back in the water.
1181590Srgrimes
1191590Srgrimes20010429:
1201590Srgrimes	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
1211590Srgrimes	this date, but before the correction date.
1221590Srgrimes
1231590Srgrimes20010423:
1241590Srgrimes	old fsck and new kernel interactions appear to have been fixed.
1251590Srgrimes
1261590Srgrimes20010411:
1271590Srgrimes	fsck and the kernel were changed to handle some optimizations
1281590Srgrimes	to directory layout.  This breaks backward compatibility.
1291590Srgrimes	Update only if you understand that you must not use the old
1301590Srgrimes	fsck with the new kernel ever.
1311590Srgrimes
1321590Srgrimes20010330:
1331590Srgrimes	fsck has changed the meaning of the pass column in /etc/fstab.
1341590Srgrimes	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1351590Srgrimes	details.  It is unclear if changes to /etc/fstab are necessary.
1361590Srgrimes
1371590Srgrimes20010319:
1381590Srgrimes	portmap had changed name to rpcbind for maximum POLA in your
1391590Srgrimes	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1401590Srgrimes	other rpc based programs that rely on portmapper will not work
1411590Srgrimes	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
1421590Srgrimes
1431590Srgrimes20010315:
1441590Srgrimes	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1451590Srgrimes	and ATA_ENABEL_TAGS are no longer kernel options.  They have
1461590Srgrimes	been replaced by tunables.  See ata.4 for details.
1471590Srgrimes
1481590Srgrimes20010312:
1491590Srgrimes	The fxp driver was converted to use miibus.  If you compile
1501590Srgrimes	fxp into your kernel statically, you will need to add miibus.
1511590Srgrimes
1521590Srgrimes20010312:
1531590Srgrimes	The wi device now defaults to BSS (infrastructure) mode
1541590Srgrimes	instead of ad-hoc.
1551590Srgrimes
1561590Srgrimes20010310:
1571590Srgrimes	/dev/urandom should be a symbolic link to /dev/random now.
1581590Srgrimes	Users of current not using DEVFS need to run MAKEDEV std.
1591590Srgrimes	ssh might not work if you don't.
1601590Srgrimes
1611590Srgrimes20010220:
1621590Srgrimes	The problems with libc have been corrected.  It is now mostly
1631590Srgrimes	safe to go back into the water.
1641590Srgrimes
1651590Srgrimes20010211:
1661590Srgrimes	The size of FILE was changed.  This breaks upgrading.  If
1671590Srgrimes	you must upgrade, be prepared for pain.  It also breaks almost
1681590Srgrimes	all binaries that you've compiled on -current.  You are warned
1691590Srgrimes	that before upgrading would be a good time to do a level 0
1701590Srgrimes	dump of your system.  No, really, I mean it this time.
1711590Srgrimes
1721590Srgrimes	To get to the new system, you'll need to use the following
1731590Srgrimes	workaround.  Hopefully this can be sorted out so that we
1741590Srgrimes	don't have to move this to the updating section.
1751590Srgrimes
1761590Srgrimes	To get around the installworld problem, do:
1771590Srgrimes		# cd /usr/src/usr.bin/sed
1781590Srgrimes		# make install
1791590Srgrimes		# cd /usr/src
1801590Srgrimes		# make installworld
1811590Srgrimes	If that doesn't work, then try:
1821590Srgrimes		# make -k installworld
1831590Srgrimes		# make installworld
1841590Srgrimes
1851590Srgrimes20010207:
1861590Srgrimes	DEVFS is now the default.  If you use vinum, make sure that you
1871590Srgrimes	do not include devfs in your kernel as problems result.
1881590Srgrimes
1891590Srgrimes20010205:
1901590Srgrimes	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1911590Srgrimes	Remove them from your config.
1921590Srgrimes
1931590Srgrimes20010122:
1941590Srgrimes	****************************** WARNING ******************************
1951590Srgrimes			buildkernel has been changed slightly
1961590Srgrimes	****************************** WARNING ******************************
1971590Srgrimes	KERNCONF replaces the variable KERNEL for buildkernel.  You
1981590Srgrimes	should update your scripts and make.conf accordingly.
1991590Srgrimes
2001590Srgrimes20010119:
2011590Srgrimes	config has changed to allow DEV_FOO as a replacement for NFOO.
2021590Srgrimes	This requires a new config to build correctly.
2031590Srgrimes
2041590Srgrimes20010116:
2051590Srgrimes	The kerrnel option I386_CPU is now mutually exclusive with the
2061590Srgrimes	other cpu types. If you have an i386 system, be sure that it
2071590Srgrimes	only had this line.  Remove it for all other configurations.
2081590Srgrimes
2091590Srgrimes20010110:
2101590Srgrimes	Changes to the kernel require it and burncd be in sync.
2111590Srgrimes
2121590Srgrimes20010102:
2131590Srgrimes	Everyone who has hw.sndunit set to something in
2141590Srgrimes	/etc/sysctl.conf, it is now hw.snd.unit.
2151590Srgrimes
2161590Srgrimes20010101:
2171590Srgrimes	ex and vi were broken by some changes to sys/queue.h.  If you
2181590Srgrimes	have a bad vi, you will see make buildworld fail with a core
2191590Srgrimes	dump while building termcap.  You can work around this problem
2201590Srgrimes	by adding -k to your make buildworld.  This will cause the
2211590Srgrimes	build to complete and install a new vi.  Once that's done, you
2221590Srgrimes	can rebuild again without the -k to pick up anything that
2231590Srgrimes	might have been ignored by the -k option.
2241590Srgrimes
2251590Srgrimes	Others have suggested that you can just rebuild libc if your
2261590Srgrimes	vi/ex is dynamically linked, but I've not received any reports
2271590Srgrimes	of this working.
2281590Srgrimes
2291590Srgrimes20001228:
2301590Srgrimes	There have been some changes to libcrypt in -current.  The
2311590Srgrimes	libscrypt/libdescrypt symlink sillyness is gone and the installed
2321590Srgrimes	libcrypt is fully functional.  Be aware of this.
2331590Srgrimes
23440188Sbde20001218:
2351590Srgrimes	Linksys Fast Ethernet PCCARD cards supported by the ed driver
2361590Srgrimes	now require the addition of flag 0x80000 to their config line
2371590Srgrimes	in pccard.conf(5).  This flag is not optional.  These Linksys
2381590Srgrimes	cards will not be recognized without it.
2391590Srgrimes
2401590Srgrimes20001205:
2411590Srgrimes	Important new FreeBSD-version stuff: PAM support has been worked
2421590Srgrimes	in, partially from the "Unix" OpenSSH version.  This requires
2431590Srgrimes	adding the following in pam.conf:
2441590Srgrimes  
2451590Srgrimes	sshd    auth    sufficient      pam_skey.so
2461590Srgrimes	sshd    auth    required        pam_unix.so         try_first_pass
2471590Srgrimes	sshd    session required        pam_permit.so
2481590Srgrimes
2491590Srgrimes20001031:
2501590Srgrimes	cvs updated to 1.11.
2511590Srgrimes
2521590Srgrimes20001020:
2531590Srgrimes	The random device needs more entropy, so you need to make sure
2541590Srgrimes	that you've run mergemaster to get a /etc/rc which will seed
2551590Srgrimes	/dev/random.  If you don't and the system hangs after ldconfig,
2561590Srgrimes	then banging on the keyboard randomly until it unhangs is one
2571590Srgrimes	workaround.
2581590Srgrimes
2591590Srgrimes20001010:
2601590Srgrimes	****************************** WARNING ******************************
2611590Srgrimes				Sendmail has been updated.
2621590Srgrimes	****************************** WARNING ******************************
2631590Srgrimes	o mail.local(8) is no longer installed as a set-user-id binary.
2641590Srgrimes	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
2651590Srgrimes	  is set.
2661590Srgrimes	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
2671590Srgrimes	  commands.
2681590Srgrimes	o Now using sendmail's version of vacation(1).
2691590Srgrimes	o The sendmail cf building tools (contrib/sendmail/cf) are installed
2701590Srgrimes	  in /usr/share/sendmail/cf.
2711590Srgrimes	o sendmail.cw changed to local-host-names
2721590Srgrimes
2731590Srgrimes	More details can be found at
2741590Srgrimes		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
2751590Srgrimes
2761590Srgrimes20001009:
2771590Srgrimes	The ports tree's new layout is in place.  Be sure to update
2781590Srgrimes	your entire ports tree, or you will have problems.
2791590Srgrimes
2801590Srgrimes20001006:
2811590Srgrimes	The perl build procedure no longer installs miniperl, nor uses
2821590Srgrimes	the installed miniperl.  It is recommended that you delete
2831590Srgrimes	/usr/bin/miniperl.
2841590Srgrimes
2851590Srgrimes20001005:
2861590Srgrimes	This weekend the ports tree will be updated to a new layout.
2871590Srgrimes	It will be in an inconsistent state until noted in the UPDATING
2881590Srgrimes	file, or with asami-san's message to the relevant mailing
2891590Srgrimes	lists.  With this new layout, you'll need to update the whole
2901590Srgrimes	tree for anything to work.
2911590Srgrimes
2921590Srgrimes20000928:
2931590Srgrimes	There was a change in the passwd format.  Need more information.
2941590Srgrimes
2951590Srgrimes20000916:
2961590Srgrimes	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
2971590Srgrimes	place.  Please update boot loader (not the boot blocks) at the
2981590Srgrimes	same time as your kernel.
2991590Srgrimes
3001590Srgrimes20000914:
3011590Srgrimes	The new pmtimer device is necessary for laptops.  Failure to
3021590Srgrimes	include the device will cause suspended laptops losing time
3031590Srgrimes	when they resume.  Include
3041590Srgrimes		device		pmtimer
3051590Srgrimes	in your config file and
3061590Srgrimes		hint.pmtimer.0.at="isa"
3071590Srgrimes	to your /boot/device.hints file.
3081590Srgrimes
3091590Srgrimes20000911:
3101590Srgrimes	The random device has been turned into a (pseudo-)device,
3111590Srgrimes	rather than an option. The supplied kernel config files have
3121590Srgrimes	been updated. You will need to do something similar in your
3131590Srgrimes	own kernel config file.
3141590Srgrimes	Remove:
3151590Srgrimes		options		RANDOMDEV
3161590Srgrimes	Add:
3171590Srgrimes		device		random
3181590Srgrimes	If you prefer to load the loadable module, you need to do
3191590Srgrimes	nothing.
3201590Srgrimes
3211590Srgrimes20000909:
3221590Srgrimes	The random device module has been renamed from randomdev.ko to
3231590Srgrimes	random.ko. You will need to edit your /boot/loader.conf to
3241590Srgrimes	reflect this if you load this module at boot time.
3251590Srgrimes	The line should read:
3261590Srgrimes		random_load="YES"
3271590Srgrimes
3281590Srgrimes20000907:
3291590Srgrimes	The SMPNG commit has happened.  It should work, but if it
3301590Srgrimes	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
3311590Srgrimes	to be a variety of minor issues.  Please see 20000905 to make
3321590Srgrimes	sure you don't have model loading problems which might at
3331590Srgrimes	first blush appear related to SMP.
3341590Srgrimes
3351590Srgrimes20000906:
3361590Srgrimes	nsswitch has been imported from NetBSD.  Among other things,
3371590Srgrimes	this means that /etc/host.conf is no longer used.  See
3381590Srgrimes	nsswitch.conf(5) instead.  Note that at boot time rc.network
3391590Srgrimes	will attempt to produce a new nsswitch.conf file for you if you
3401590Srgrimes	don't have one, and you have host.conf.
3411590Srgrimes
3421590Srgrimes20000905:
3431590Srgrimes	The ucred structure changed size.  This breaks the interface
3441590Srgrimes	that mountd uses.  Trying to use an older mountd with a newer
3451590Srgrimes	kernel guarantees a panic.  This means that you need to use
3461590Srgrimes	kernels newer than today only with matching mountd, but you
3471590Srgrimes	needed to do that anyway with the boot loader changes.
3481590Srgrimes
3491590Srgrimes20000905:
3501590Srgrimes	The boot loader has been updated.  The new default kernel is
3511590Srgrimes	now /boot/kernel/kernel.ko.  The new default module location
3521590Srgrimes	is /boot/kernel.
3531590Srgrimes
3541590Srgrimes	You *MUST* upgrade your boot loader and kernel at the same time.
3551590Srgrimes	The easiest way to do this is to do the buildworld/buildkernel/
3561590Srgrimes	installkernel/installworld dance.
3571590Srgrimes
3581590Srgrimes	Furthermore, you are urged to delete your old /modules directory
3591590Srgrimes	before booting the new kernel, since kldload will find stale
3601590Srgrimes	modules in that directory instead of finding them in the correct
3611590Srgrimes	path, /boot/kernel.  The most common complaint that this cures
3621590Srgrimes	is that the linux module crashes your machine after the update.
3631590Srgrimes
3641590Srgrimes	if [ ! -d /boot/kernel.old ]; then
3651590Srgrimes		mv /modules.old /boot/kernel.old
3661590Srgrimes		chflags noschg /kernel.old
3671590Srgrimes		mv /kernel.old /boot/kernel.old/kernel.ko
3681590Srgrimes		chflags schg /boot/kernel.old/kernel.ko
3691590Srgrimes	fi
3701590Srgrimes
3711590Srgrimes20000904:
3721590Srgrimes	A new issue with the sendmail upgrade has come to light.
3731590Srgrimes	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will 
374	incorrectly install the default aliases in /etc/mail rather than
375	move the old one from /etc.  So you'll need to manually move the
376	file, create a symbolic link, remove the old /etc/aliases.db and
377	run newaliases.  For safety sake, you should stop sendmail
378	while doing this and run the upgrade when locally sourced email
379	is not likely to be generated.
380
38120000825:
382	/boot/device.hints is now required for installkernel to
383	succeed.  You should copy GENERIC.hints for your architecture
384	into /boot/device.hints.  If and only if you compile hints
385	into your kernel, then this file may be empty.  Please note,
386	if you have an empty or missing /boot/device.hints file and
387	you neglected to compile hints into your kernel, no boot
388	messages will appear after the boot loader tries to start the
389	kernel.
390
39120000821:
392	If you do NOT have ``options RANDOMDEV'' in your kernel and
393	you DO want the random device then add randomdev_load="YES" to
394	/boot/loader.conf.
395
39620000812:
397	suidperl is now always built and installed on the system, but
398	with permissions of 511.  If you have applications that use
399	this program, you are now required to add ENABLE_SUIDPERL=true
400	to /etc/make.conf.  If you forget to do this,
401		chmod 4511 /usr/bin/suidperl
402	will fix this until the next build.
403
40420000812:
405	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
406	visible changes that may immediately affect your configuration
407	include:
408	- New default file locations from src/contrib/sendmail/cf/README
409	- newaliases limited to root and trusted users
410	- MSA port (587) turned on by default
411	- New queue file naming system so can't go from 8.11 -> 8.9
412	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
413	- FEATURE(`nullclient') is more full featured
414	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
415	- mail.local FreeBSD-only -b option changed to -B
416	- See src/contrib/sendmail/RELEASE_NOTES for more info
417
41820000810:
419	suidperl (aka sperl) is no longer build by default.  You must
420	specifically define BUILD_SUIDPERL to "true" for it to be build.
421	Furthermore, we recommend that you remove /usr/bin/sperl* and
422	/usr/bin/suidperl files from your system unless you have a
423	specific use for it.
424
42520000729:
426	Networking defaults have been tightened.  Anybody upgrading
427	/etc/defaults/rc.conf needs to add the following lines to
428	/etc/rc.conf if they want to have the same setup
429	afterwards (unless the variables already are set, of course):
430		# Enable network daemons for user convenience.
431		inetd_enable="YES"
432		portmap_enable="YES"
433		sendmail_enable="YES"
434
43520000728:
436	If you have null_load="YES" in your /boot/loader.conf, you
437	will need to change that to nullfs_load="YES".
438
43920000728:
440	The "installkernel" target has changed slightly. Now even if
441	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
442	it will install the MYKERNEL file (built with the buildkernel
443	target) as /kernel rather than /MYKERNEL. Those who have
444	updated their /boot/loader.conf files to point to /MYKERNEL
445	should remove that entry or perform manual rename of /kernel
446	to /MYKERNEL.
447
44820000711:
449	If you use CVSUP or CTM to get CVS trees, AND you used to get 
450	the old crypto files from internat.freebsd.org AND you check
451	out files from the CVS tree with the cvs command, please read
452		http://people.freebsd.org/~imp/internat.txt
453	for details on potential problems that you might have and how
454	to get around them.
455
456	If you are merely a mirror, or don't answer yes to each of the
457	clauses above, you needn't worry.
458
45920000711:
460	/etc/security has been updated to print the inode number of
461	setuid programs that have changed.  You will see a large spike
462	in the number of changed programs the first time when you run
463	mergemaster to get a new /etc/security.
464
46520000710:
466	/dev/random now has good entropy collection (from the keyboard
467	and sysmouse drivers). Please ensure that either `options
468	RANDOMDEV' is present in your kernel config file or that
469	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
470	not have the /dev/random driver, OpenSSL (and consequently
471	lots of crypto tools (like SSH)) will fail with strange
472	errors. (see below, 20000624).
473
474	FreeBSD-current is safe again to run Crypto.
475
47620000709:
477	phk made the malloc default options AJ.  This may slow things
478	down and uncover other latent bugs in the code.  If you need to
479	run at full speed, you can disable this by doing the following:
480		ln -s aj /etc/malloc.conf
481
48220000706:
483	libftpio's version was accidentally bumped a few days ago.  This
484	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
485	before doing your next buildworld/installworld pair.  It certainly
486	won't hurt to remove it before the update procedure.  It will
487	break fetch until a new one is built, but ftp can be used in the
488	interim if needed.
489
49020000705:
491	The crypto packages have changed for the cvsup.  This has been done
492	in a backward compatible way, but the old packages will go away at
493	some point in the future.  Look at /usr/share/examples/cvsup for
494	details.
495
49620000704:
497	With the new sys/modules/sound/drivers/*, you will need to
498	set SYSDIR until you do an installworld after July 7th.
499
50020000704:
501	rc.shutdown and rc will now call the rc.d scripts with start
502	or stop.  This may cause some harmless warnings from older
503	rc.d scripts that haven't been updated.
504
50520000630:
506	The libfetch based version of fetch has gone into the tree.
507	Minor problems may result on some of the less popular sites,
508	which should be reported to des@freebsd.org.
509
51020000625:
511	From approximately this date forward, one must have the crypto
512	system installed in order to build the system and kernel.
513	While not technically strictly true, one should treat it as
514	required and grab the crypto bits.  If you are grabbing CVS
515	trees, src-all and cvs-crypto should be treated as if they
516	were required.  You should check with the latest collections
517	to make sure that these haven't changed.
518
51920000624:
520	Mark Murray just committed the first parts of a cleanup of
521	/dev/zero, et al.  This is also cleaning up /dev/random.
522	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
523	-CURRENT FROM THIS POINT FORWARD for cryptographic services
524	until Mark can merge in the fixes to this work in progress.
525	openssh and openssl should not be used to generate keys from this
526	date to the completion of the work.
527
528	If you must operate at this reduced level of security, add '
529	options RANDOMDEV' to your kernel or modload the randomdev
530	module.  You may also need to copy a new MAKEDEV to /dev and
531	recreate the random and urandom devices.
532
53320000622:
534	The license on the softupdates is now a standard 2 clause
535	BSD license.  You may need to remove your symbolic links
536	that used to be required when updating.
537
53820000621:
539	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
540	the config file update procedure.
541		http://people.freebsd.org/~imp/config-upd.html
542	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
543	isn't buildable.  However, you can generate a LINT file.
544
54520000620:
546	Binutils 2.10 have hit the tree, or will shortly.  As soon
547	as they do, the problem noted in 20000522 will be resolved and
548	that workaround will no longer be required.
549
55020000615:
551	phk removed the compatibility creation of wd devices in the
552	ad driver.  If you haven't done so already, you must update
553	your fstab, etc to use the ad devices instead of the wd
554	devices.
555
556	In addition, you'll need to update your boot blocks to a
557	more modern version, if you haven't already done so.  Modern
558	here means 4.0 release or newer (although older releases
559	may work).
560
56120000612:
562	Peter took an axe to config(8).  Be sure that you read his mail
563	on the topic before even thinking about updating.  You will
564	need to create a /boot/device.hints or add a hints directive
565	to your config file to compile them in statically.  The format
566	of the config file has changed as well.  Please see GENERIC or
567	NEWCARD for examples of the new format.
568
56920000522:
570	A new set of binutils went into the tree today.  Anybody
571	building a kernel after this point is advised that they need
572	to rebuild their binutils (or better yet do a
573	buildworld/installworld) before building a new kernel.
574
575	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
576	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
577	is recommended that you don't set this option until the problem
578	is resolved.
579
58020000513:
581	The ethernet drivers were all updated to clean up the BPF handling.
582
58320000510:
584	The problems with boot blocks on the alphas have been corrected.
585	This will require some care in updating alphas.  A new libstand
586	is requires for the boot blocks to build properly.
587
58820000503:
589	Recompile all kld modules.  Proper version dependency info
590	is now available.
591
59220000502:
593	Modules have been disconnected from the buildworld tree and 
594	connected to the kernel building instead.
595
59620000427:
597	You may need to build gperf
598		cd /usr/src/gnu/usr.bin/gperf && make depend all install
599	when upgrading from 4.0 -> current.  The build system now uses
600	an option only in -current.
601
60220000417:
603	The method that we brand ELF binaries has changed to be more
604	acceptable to the binutils maintainers.  You will need to
605	rebrand your ELF binaries that aren't native.  One problem
606	binary is the Linux ldconfig.  After your make world, but
607	before you reboot, you'll need to issue:
608		brandelf -t Linux /compat/linux/sbin/ldconfig
609	if you have Linux compatibility enabled on your machine.
610
61120000320:
612	If you have really bad/marginal IDE drives, you may find they
613	don't work well.  Use pio mode instead.  The easiest way to
614	cope if you have a problem combination is to add:
615		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
616	to the start of /etc/rc.conf.
617
61820000319:
619	The ISA and PCI compatibility shims have been connected to the
620	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
621	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
622	include the appropriate option in your kernel config.  Drivers
623	using the shims should be updated or they won't ship with
624	5.0-RELEASE, targeted for 2001.
625
62620000318:
627	We've entered the traditional post release dumping party.
628	Large kernel changes are being committed and are in the
629	works.  It is important to keep the systems' klds and kernel
630	in sync as kernel interfaces and structures are changing.
631	Before reporting kernel panics, make sure that all modules
632	that you are loading are up to date.
633
63420000315:
635	If you are upgrading from an older version of FreeBSD, you
636	need to update your boot blocks as well.  'disklabel -B ad0'
637	will do the trick.  This isn't critical until you remove your
638	wd device entries in /dev, at which point your system will not
639	boot.
640
64120000315:
642	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
643	to upgrade to 4.0 from 3.x.
644
645COMMON ITEMS:
646
647	General Notes
648	-------------
649	Avoid using make -j when upgrading.  From time to time in the
650	past there have been problems using -j with buildworld and/or
651	installworld.  This is especially true when upgrading between
652	"distant" versions (eg one that cross a major release boundary
653	or several minor releases, or when several months have passed
654	on the -current branch).
655
656	To build a kernel
657	-----------------
658	If you are updating from a prior version of FreeBSD (even one just
659	a few days old), you should follow this procedure. With a
660	/usr/obj tree with a fresh buildworld,
661	make buildkernel KERNCONF=YOUR_KERNEL_HERE
662	make installkernel KERNCONF=YOUR_KERNEL_HERE
663
664	To just build a kernel when you know that it won't mess you up
665	--------------------------------------------------------------
666	cd src/sys/{i386,alpha}/conf
667	config KERNEL_NAME_HERE			[1]
668	cd ../../compile/KERNEL_NAME_HERE
669	make depend
670	make
671	make install	
672	
673	[1] If in doubt, -r might help here.
674
675	If this fails, go to the "To build a kernel" section.
676
677	To rebuild everything and install it on the current system.
678	-----------------------------------------------------------
679	make world
680	Build a new kernel, see above.
681
682	To upgrade from 4.x-stable to current
683	-------------------------------------
684	make buildworld
685	make buildkernel KERNCONF=YOUR_KERNEL_HERE
686	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
687	make installkernel KERNCONF=YOUR_KERNEL_HERE
688	reboot in single user [3]
689	make installworld
690	mergemaster
691	[1]
692	<reboot>
693
694	Make sure that you've read the UPDATING file to understand the
695	tweaks to various things you need.  At this point in the life
696	cycle of current, things change often and you are on your own
697	to cope.  The defaults can also change, so please read ALL of
698	the UPDATING entries.
699
700	Also, if you are tracking -current, you must be subscribed to
701	freebsd-current@freebsd.org.  Make sure that before you update
702	your sources that you have read and understood all the recent
703	messages there.  If in doubt, please track -stable which has
704	much fewer pitfalls.
705
706	[1] If you have third party modules, such as vmware, you
707	should disable them at this point so they don't crash your
708	system on reboot.
709
710	[2] If you have legacy ISA devices, you may need to create
711	your own device.hints to reflect your unique hardware
712	configuration.
713
714	[3] From the bootblocks, boot -s, and then do
715		fsck -p
716		mount -u /
717		mount -a
718		cd /usr/src
719		adjkerntz -i		# if COMS is wall time
720
721FORMAT:
722
723This file contains a list, in reverse chronological order, of major
724breakages in tracking -current.  Not all things will be listed here,
725and it only starts on March 15, 2000.  Updating files can found in
726previous releases if your system is older than this.
727
728Please filter your entries through Warner Losh (imp@village.org) so
729that the style, formatting, etc of this file can be maintained.
730
731Copyright information:
732
733Copyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
734
735Redistribution, translation and use, with or without modification, in
736full or in part, are permitted provided that the above copyright
737notice is retained.
738
739THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
740IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
741WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
742DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
743INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
744(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
745SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
746HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
747STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
748IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
749POSSIBILITY OF SUCH DAMAGE.
750
751If you find this document useful, and you want to, you may buy the
752author a beer.
753
754$FreeBSD: head/UPDATING 79015 2001-06-30 06:35:45Z imp $
755