xref: /freebsd/UPDATING (revision a81da3c933cc1886b64d5bbc27ba5de471306e4d)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
49698f2c0SWarner Losh<imp@village.org>.  See end of file for further details.  For commonly
59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file.
6e72fd46aSWarner Losh
769f7bcf3SWarner LoshNOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
869f7bcf3SWarner Losh	FreeBSD 5.0-CURRENT has many debugging features turned on, in
969f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1069f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1169f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1269f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1369f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1469f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1569f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1669f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1769f7bcf3SWarner Losh	developers choose to disable these features on build machines
1869f7bcf3SWarner Losh	to maximize performance.
1969f7bcf3SWarner Losh
2069f7bcf3SWarner Losh	In addition, IDE write caching is currently disabled by default
2169f7bcf3SWarner Losh	due to on-going concerns about disk write order and file system
2269f7bcf3SWarner Losh	integrity.  Re-enabling write caching can substantially improve
2369f7bcf3SWarner Losh	performance.
2469f7bcf3SWarner Losh
25a81da3c9SDavid E. O'Brien20020510:
26a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
27a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
28a81da3c9SDavid E. O'Brien	and then do a cvs update.
29a81da3c9SDavid E. O'Brien
30528a0ef5SJacques Vidrine20020421:
31528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
32528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
33528a0ef5SJacques Vidrine
3485aa5a2eSGregory Neil Shapiro20020404:
3585aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
3685aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
3785aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
3885aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
3985aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
4085aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
4185aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
4285aa5a2eSGregory Neil Shapiro
438f1e4358SRuslan Ermilov20020403:
448f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
458f1e4358SRuslan Ermilov
462292c02eSWarner Losh20020315:
472292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
482292c02eSWarner Losh
4969f7bcf3SWarner Losh20020225:
5069f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
5169f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
5269f7bcf3SWarner Losh
538f35c493SWarner Losh20020217:
548f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
558f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
568f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
578f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
588f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
598f35c493SWarner Losh
60835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
61835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
62835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
63835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
64835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
65835284beSWarner Losh	and group must be merged from src/etc/group and
66835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
67835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
68835284beSWarner Losh	mergemaster before this will work if you are updating from a
69835284beSWarner Losh	very old version of current.  The updating recipe has changed
70835284beSWarner Losh	as of this date.
71835284beSWarner Losh
72fa9401c1SWarner Losh20020112:
73fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
74fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
75fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
76fa9401c1SWarner Losh	you have local modifications, you can use
77fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
78fa9401c1SWarner Losh	/etc/pam.d.
79fa9401c1SWarner Losh
80fa9401c1SWarner Losh	Please see the following url for more details:
81fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
8247d0d01fSWarner Losh20011229:
8347d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
8447d0d01fSWarner Losh	networkfs_types, please note that it has changed
8547d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
8647d0d01fSWarner Losh
87514318a8SWarner Losh20011220:
88514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
89514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
90514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
91514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
92514318a8SWarner Losh	version have now been merged back into the base system's
93514318a8SWarner Losh	version now.  The only user-visible change resulting from this
94514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
95514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
96514318a8SWarner Losh	as well.  (There has never been rc file support for
97514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
98514318a8SWarner Losh	reverted by the time the changes are MFCed.)
99514318a8SWarner Losh
100514318a8SWarner Losh20011215:
101514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
102514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
103514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
104514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
105514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
106514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
107514318a8SWarner Losh	will need to be customized then for `odd' densities using
108514318a8SWarner Losh	fdcontrol(8).
109514318a8SWarner Losh
1102d22e2bfSWarner Losh20011209:
1112d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
1122d22e2bfSWarner Losh	and truss(1) now works again.
1132d22e2bfSWarner Losh
1149e0428e2SWarner Losh20011207:
1159e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
1169e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
1179e0428e2SWarner Losh	see
1189e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
1199e0428e2SWarner Losh	for details.
1209e0428e2SWarner Losh
1219bab8c59SWarner Losh20011204:
1229bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
1239bab8c59SWarner Losh	kernel and burncd to be in sync.
1249bab8c59SWarner Losh
125e57d8b01SWarner Losh20011203:
126e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
127e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
128e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
129e57d8b01SWarner Losh	not there already.
130e57d8b01SWarner Losh
131e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
132e57d8b01SWarner Losh	until the issue has been resolved.
133e57d8b01SWarner Losh
134b001d36fSJacques Vidrine20011202:
135b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
136b001d36fSJacques Vidrine	patched.
137b001d36fSJacques Vidrine
1384b676ec1SWarner Losh20011126:
1394b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
1405ebbf43eSWarner Losh	after this date.  You need to do this only once.
1414b676ec1SWarner Losh
142d961e462SWarner Losh20011103:
143d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
144d961e462SWarner Losh	edges may be left, but for the most part things should be
1454b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
146d961e462SWarner Losh
147d961e462SWarner Losh20011030:
148d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
149d961e462SWarner Losh	choppy waves in the upgrade process.
150d961e462SWarner Losh
1511fe003b6SWarner Losh20011030:
152a4b6fda0SWarner Losh	The asr driver problem has been resolved.
1531fe003b6SWarner Losh
1541fe003b6SWarner Losh20011027:
1551fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
1561fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
1571fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
1581fe003b6SWarner Losh	try to use from this date forward.
1591fe003b6SWarner Losh
1601fe003b6SWarner Losh20011025:
1611fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
1621fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1631fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1641fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
1651fe003b6SWarner Losh	TARGET_ARCH=i386.
1661fe003b6SWarner Losh
167d05f9643SWarner Losh20011001:
168d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
169d05f9643SWarner Losh	You must recompile both the kernel and userland applications
170d05f9643SWarner Losh	at the same time.
171d05f9643SWarner Losh
17258970f85SWarner Losh20010929:
17358970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
17458970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
17558970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
17658970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
17758970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
17858970f85SWarner Losh
17958970f85SWarner Losh20010927:
18058970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
18158970f85SWarner Losh	To disable ACPI you can add
182378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
18358970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
18458970f85SWarner Losh	loader "ok" prompt).
18558970f85SWarner Losh
18658970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
18758970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
18858970f85SWarner Losh	file and not list acpi in that list.
189378f4486SAlfred Perlstein
1905119d237SWarner Losh20010924:
1915119d237SWarner Losh	The buildworld has been fixed.  You may need to install
1925119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
1938b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
1948b039fffSWarner Losh	get them installed on every installworld, or execute the
1958b039fffSWarner Losh	following to get them installed only once:
1968b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
19758970f85SWarner Losh		make all install
1988b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
1995119d237SWarner Losh
2003c293725SWarner Losh20010919:
2013c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
2023c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
2033c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
204772730c7SWarner Losh	workaround is to add
2053c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
2063c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
2073c293725SWarner Losh	can be removed afterwards.
2083c293725SWarner Losh
2093c293725SWarner Losh	A proper fix to the buildworld target is needed.
2103c293725SWarner Losh
2113c293725SWarner Losh20010918:
2123c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
2133c293725SWarner Losh	NFS may be unstable after this date.
2143c293725SWarner Losh
2153c293725SWarner Losh20010912:
2163c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
2173c293725SWarner Losh	the kernel.  While a few problems were introduced in the
2183c293725SWarner Losh	initial commit, most of the major ones have been found and
2193c293725SWarner Losh	corrected.
2203c293725SWarner Losh
2213c293725SWarner Losh20010901:
2223c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
2233c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
2243c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
2253c293725SWarner Losh	have been rectified around this date.
2263c293725SWarner Losh
22798b17b95SWarner Losh20010823:
22898b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
22998b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
23098b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
23198b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
23298b17b95SWarner Losh 	sure that user or group bind has read (and not write)
23398b17b95SWarner Losh 	permission for your name server configuration and that it
23498b17b95SWarner Losh 	has read and write permission for your slave zone files and
23598b17b95SWarner Losh 	directory.
23698b17b95SWarner Losh
23798b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
23898b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
23998b17b95SWarner Losh
24098b17b95SWarner Losh 		named_flags=
24198b17b95SWarner Losh
2427b9786edSMark Murray20010709:
2437b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
2447b9786edSMark Murray	the ability of the shared library major number to handle.
2457b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
2467b9786edSMark Murray	solution is to rebuild those ports.
2477b9786edSMark Murray
2481d28950eSWarner Losh20010628:
2491d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
2501d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
2511d28950eSWarner Losh
252e72fd46aSWarner Losh20010625:
25398b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
25498b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
25598b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
25698b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
25798b17b95SWarner Losh	IRQ configuration needs more safety belts.
25816de1a07SWarner Losh
2590d415dffSWarner Losh20010617:
260e72fd46aSWarner Losh	Softupdates problems have been corrected.
2610d415dffSWarner Losh
2620d415dffSWarner Losh20010614:
2630d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2640d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
2650d415dffSWarner Losh	kernel building methods.
2660d415dffSWarner Losh
2678b9959adSWarner Losh20010613:
2688b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
2698b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
270e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
271e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
2728b9959adSWarner Losh
273e72fd46aSWarner Losh20010613:
2748b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
275e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
276e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
2778b9959adSWarner Losh
2780d415dffSWarner Losh20010612:
2790d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
2800d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
2810d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
2820d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
2830d415dffSWarner Losh	until this bug is fixed.
2840d415dffSWarner Losh
285e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
286e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
287e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
288e72fd46aSWarner Losh
2890d415dffSWarner Losh20010610:
2900d415dffSWarner Losh	Locale names have changed to match other systems better.
2910d415dffSWarner Losh
2926ccdb5e4SWarner Losh20010604:
2936ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
2946ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
2956ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
2963590182eSWarner Losh	Interrupt storms look a lot like a hang.
2973590182eSWarner Losh
2983590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
2993590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
3003590182eSWarner Losh	it is).
3013590182eSWarner Losh
3023590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
3033590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
3043590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
3053590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
3066ccdb5e4SWarner Losh
3070bc62786SWarner Losh20010530:
3080bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
3090bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
3100bc62786SWarner Losh	a limited time.  If you see
3110bc62786SWarner Losh
3120bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
3130bc62786SWarner Losh
3140bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
3150bc62786SWarner Losh	COPY=-C.
3160bc62786SWarner Losh
31768a38c6cSWarner Losh20010525:
318b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
319c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
320c4f4a728SWarner Losh	definitely is in bad shape.
32168a38c6cSWarner Losh
322ed0f29caSWarner Losh20010521:
323f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
324ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
325ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
326ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
327ed0f29caSWarner Losh	is
328ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
329ed0f29caSWarner Losh
33080c16af9SWarner Losh20010520:
33168a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
33280c16af9SWarner Losh
33380c16af9SWarner Losh20010519:
33480c16af9SWarner Losh	pccard has had much reorganizational work done to it over
33580c16af9SWarner Losh	the past few days.  Everything should still work, but if
33680c16af9SWarner Losh	not, please contact imp@freebsd.org.
33780c16af9SWarner Losh
338a45f2d05SWarner Losh20010517:
339a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
340a45f2d05SWarner Losh	userland at the same time.
341a45f2d05SWarner Losh
342a45f2d05SWarner Losh20010517:
343a45f2d05SWarner Losh	New ncurses imported.
344a45f2d05SWarner Losh
3452988afcaSWarner Losh20010512:
3462988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
3472988afcaSWarner Losh	will be the only way to go starting July 1.
3482988afcaSWarner Losh
3491a33dba7SWarner Losh20010504:
3501a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
3511a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
3521a33dba7SWarner Losh
35309946a51SWarner Losh20010502:
35409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
35509946a51SWarner Losh
35609946a51SWarner Losh20010501:
35709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
35809946a51SWarner Losh
35909946a51SWarner Losh20010430:
360a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
36109946a51SWarner Losh	go back in the water.
36209946a51SWarner Losh
36309946a51SWarner Losh20010429:
36409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
36509946a51SWarner Losh	this date, but before the correction date.
36609946a51SWarner Losh
36791dd3b53SWarner Losh20010423:
36891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
36991dd3b53SWarner Losh
37091dd3b53SWarner Losh20010411:
37191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
37291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
37391dd3b53SWarner Losh	Update only if you understand that you must not use the old
37491dd3b53SWarner Losh	fsck with the new kernel ever.
37591dd3b53SWarner Losh
376933b3269SWarner Losh20010330:
377933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
378c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
379933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
380933b3269SWarner Losh
381933b3269SWarner Losh20010319:
382933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
383933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
384933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
385f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
38609946a51SWarner Losh
38709946a51SWarner Losh20010315:
38809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
38909946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
39009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
391933b3269SWarner Losh
392933b3269SWarner Losh20010312:
393933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
394933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
395933b3269SWarner Losh
396933b3269SWarner Losh20010312:
397933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
398933b3269SWarner Losh	instead of ad-hoc.
399933b3269SWarner Losh
400933b3269SWarner Losh20010310:
401f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
402933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
403933b3269SWarner Losh	ssh might not work if you don't.
404933b3269SWarner Losh
40562353691SWarner Losh20010303:
40662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
40762353691SWarner Losh	which means that you must include the miibus in your kernel if
40862353691SWarner Losh	you use the ed driver.
40962353691SWarner Losh
410d325cf65SWarner Losh20010220:
411d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
412d325cf65SWarner Losh	safe to go back into the water.
413d325cf65SWarner Losh
414024daae6SWarner Losh20010211:
415024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
416024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
417024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
418024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
419024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
420024daae6SWarner Losh
421024daae6SWarner Losh	To get to the new system, you'll need to use the following
422024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
423024daae6SWarner Losh	don't have to move this to the updating section.
424024daae6SWarner Losh
425024daae6SWarner Losh	To get around the installworld problem, do:
426024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
427024daae6SWarner Losh		# make install
428024daae6SWarner Losh		# cd /usr/src
429024daae6SWarner Losh		# make installworld
430024daae6SWarner Losh	If that doesn't work, then try:
431024daae6SWarner Losh		# make -k installworld
432024daae6SWarner Losh		# make installworld
433024daae6SWarner Losh
434024daae6SWarner Losh20010207:
435024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
436024daae6SWarner Losh	do not include devfs in your kernel as problems result.
437024daae6SWarner Losh
438024daae6SWarner Losh20010205:
4397595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
440024daae6SWarner Losh	Remove them from your config.
441024daae6SWarner Losh
4421e159248SWarner Losh20010122:
4431e159248SWarner Losh	****************************** WARNING ******************************
4441e159248SWarner Losh			buildkernel has been changed slightly
4451e159248SWarner Losh	****************************** WARNING ******************************
4461e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
4471e159248SWarner Losh	should update your scripts and make.conf accordingly.
4481e159248SWarner Losh
4491e159248SWarner Losh20010119:
4501e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
4511e159248SWarner Losh	This requires a new config to build correctly.
4521e159248SWarner Losh
453aac7dfeaSWarner Losh20010116:
454aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
455aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
456aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
457aac7dfeaSWarner Losh
458aac7dfeaSWarner Losh20010110:
459aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
460aac7dfeaSWarner Losh
461aac7dfeaSWarner Losh20010102:
462aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
463aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
464aac7dfeaSWarner Losh
46563c90c9eSWarner Losh20010101:
46663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
46763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
4685fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
46963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
47063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
47163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
47263c90c9eSWarner Losh	might have been ignored by the -k option.
47363c90c9eSWarner Losh
4745fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
4755fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
4765fd2a895SWarner Losh	of this working.
4775fd2a895SWarner Losh
478aac7dfeaSWarner Losh20001228:
479aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
480aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
481aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
482aac7dfeaSWarner Losh
483de2bcc63SWarner Losh20001218:
484de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
485de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
486de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
487de2bcc63SWarner Losh	cards will not be recognized without it.
488de2bcc63SWarner Losh
489960773f7SWarner Losh20001205:
490960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
491960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
492960773f7SWarner Losh	adding the following in pam.conf:
493960773f7SWarner Losh
494960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
495960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
496960773f7SWarner Losh	sshd    session required        pam_permit.so
497960773f7SWarner Losh
4980acc635eSWarner Losh20001031:
4990acc635eSWarner Losh	cvs updated to 1.11.
5000acc635eSWarner Losh
5010acc635eSWarner Losh20001020:
5020acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
5030acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
5040acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
5050acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
5060acc635eSWarner Losh	workaround.
5070acc635eSWarner Losh
5080acc635eSWarner Losh20001010:
5090acc635eSWarner Losh	****************************** WARNING ******************************
5100acc635eSWarner Losh				Sendmail has been updated.
5110acc635eSWarner Losh	****************************** WARNING ******************************
5120acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
5130acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
5140acc635eSWarner Losh	  is set.
5150acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
5160acc635eSWarner Losh	  commands.
5170acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
5180acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
5190acc635eSWarner Losh	  in /usr/share/sendmail/cf.
5200acc635eSWarner Losh	o sendmail.cw changed to local-host-names
5210acc635eSWarner Losh
5220acc635eSWarner Losh	More details can be found at
5230acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
5240acc635eSWarner Losh
5256e98a146SWarner Losh20001009:
5266e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
5276e98a146SWarner Losh	your entire ports tree, or you will have problems.
5286e98a146SWarner Losh
5296e98a146SWarner Losh20001006:
530685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
5316e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
5326e98a146SWarner Losh	/usr/bin/miniperl.
5336e98a146SWarner Losh
534073113a4SWarner Losh20001005:
535073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
536685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
537073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
538073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
539073113a4SWarner Losh	tree for anything to work.
540073113a4SWarner Losh
5410acc635eSWarner Losh20000928:
5420acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
5430acc635eSWarner Losh
544be3885b3SWarner Losh20000916:
545be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
546be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
547be3885b3SWarner Losh	same time as your kernel.
548be3885b3SWarner Losh
54976ec9675SWarner Losh20000914:
55076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
55176ec9675SWarner Losh	include the device will cause suspended laptops losing time
55276ec9675SWarner Losh	when they resume.  Include
55376ec9675SWarner Losh		device		pmtimer
55476ec9675SWarner Losh	in your config file and
55501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
55676ec9675SWarner Losh	to your /boot/device.hints file.
55776ec9675SWarner Losh
558f4865386SMark Murray20000911:
559f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
560f4865386SMark Murray	rather than an option. The supplied kernel config files have
561f4865386SMark Murray	been updated. You will need to do something similar in your
562f4865386SMark Murray	own kernel config file.
563f4865386SMark Murray	Remove:
564f4865386SMark Murray		options		RANDOMDEV
565f4865386SMark Murray	Add:
566f4865386SMark Murray		device		random
567f4865386SMark Murray	If you prefer to load the loadable module, you need to do
568f4865386SMark Murray	nothing.
569f4865386SMark Murray
570d594498fSWarner Losh20000909:
571d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
572d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
573d594498fSWarner Losh	reflect this if you load this module at boot time.
574d594498fSWarner Losh	The line should read:
575d594498fSWarner Losh		random_load="YES"
576d594498fSWarner Losh
5770deb7ddcSWarner Losh20000907:
5780deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
57916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
58016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
58116eb772dSWarner Losh	sure you don't have model loading problems which might at
58216eb772dSWarner Losh	first blush appear related to SMP.
58352bf24e7SWarner Losh
5845a01880bSWarner Losh20000906:
5855a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
5865a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
5875a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
5885a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
5895a01880bSWarner Losh	don't have one, and you have host.conf.
5905a01880bSWarner Losh
5912b41163cSWarner Losh20000905:
59238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
59338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
59438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
59538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
59638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
59738d6ecd2SWarner Losh
59838d6ecd2SWarner Losh20000905:
5998aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
6008aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
6018aab4bc7SWarner Losh	is /boot/kernel.
6028aab4bc7SWarner Losh
6038aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
60438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
60538d6ecd2SWarner Losh	installkernel/installworld dance.
6062b41163cSWarner Losh
607d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
608d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
609d594498fSWarner Losh	modules in that directory instead of finding them in the correct
610d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
611d594498fSWarner Losh	is that the linux module crashes your machine after the update.
612d594498fSWarner Losh
613d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
614d594498fSWarner Losh		mv /modules.old /boot/kernel.old
615d594498fSWarner Losh		chflags noschg /kernel.old
616d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
617d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
618d594498fSWarner Losh	fi
619d594498fSWarner Losh
620c22a309cSWarner Losh20000904:
621c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
622c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
623c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
624c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
625c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
626c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
627c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
628c22a309cSWarner Losh	is not likely to be generated.
629c22a309cSWarner Losh
630fdb9f54dSWarner Losh20000825:
631fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
6329c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
6339c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
6349c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
6359c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
6369c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
6379c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
6389c1a7444SWarner Losh	kernel.
6399c1a7444SWarner Losh
6409c1a7444SWarner Losh20000821:
6419c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
6429c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
6439c1a7444SWarner Losh	/boot/loader.conf.
644fdb9f54dSWarner Losh
6458f250aa7SWarner Losh20000812:
6465da0d091SWarner Losh	suidperl is now always built and installed on the system, but
6475da0d091SWarner Losh	with permissions of 511.  If you have applications that use
6485da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
6495da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
6505da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
6515da0d091SWarner Losh	will fix this until the next build.
6525da0d091SWarner Losh
6535da0d091SWarner Losh20000812:
6548f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
6558f250aa7SWarner Losh	visible changes that may immediately affect your configuration
6568f250aa7SWarner Losh	include:
6578f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
6588f250aa7SWarner Losh	- newaliases limited to root and trusted users
6598f250aa7SWarner Losh	- MSA port (587) turned on by default
6608f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
6618f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
6628f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6638f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6648f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
6658f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
6668f250aa7SWarner Losh
66771c38472SWarner Losh20000810:
66871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
66971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
67071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
67171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
67271c38472SWarner Losh	specific use for it.
67371c38472SWarner Losh
67471c38472SWarner Losh20000729:
67571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
67671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
67771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
67871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
67971c38472SWarner Losh		# Enable network daemons for user convenience.
68071c38472SWarner Losh		inetd_enable="YES"
68171c38472SWarner Losh		portmap_enable="YES"
68271c38472SWarner Losh		sendmail_enable="YES"
68371c38472SWarner Losh
68471c38472SWarner Losh20000728:
68571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
68671c38472SWarner Losh	will need to change that to nullfs_load="YES".
68771c38472SWarner Losh
6881dece4a9SWarner Losh20000728:
6891dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
6901dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
6911dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
6921dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
6931dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
6941dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
6951dece4a9SWarner Losh	to /MYKERNEL.
6961dece4a9SWarner Losh
697409e887cSWarner Losh20000711:
698409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
699409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
700409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
701409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
702409e887cSWarner Losh	for details on potential problems that you might have and how
703409e887cSWarner Losh	to get around them.
704409e887cSWarner Losh
705409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
706409e887cSWarner Losh	clauses above, you needn't worry.
707409e887cSWarner Losh
708409e887cSWarner Losh20000711:
709409e887cSWarner Losh	/etc/security has been updated to print the inode number of
710409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
711409e887cSWarner Losh	in the number of changed programs the first time when you run
712409e887cSWarner Losh	mergemaster to get a new /etc/security.
713409e887cSWarner Losh
714673d13f2SWarner Losh20000710:
715673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
716673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
717673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
718673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
719673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
720673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
721673d13f2SWarner Losh	errors. (see below, 20000624).
722673d13f2SWarner Losh
723bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
7241dece4a9SWarner Losh
725673d13f2SWarner Losh20000709:
726c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
727c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
728c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
729673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
730673d13f2SWarner Losh
731e98e26cdSWarner Losh20000706:
732e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
733e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
734e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
735f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
736e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
7372c021c6cSMark Ovens	interim if needed.
738e98e26cdSWarner Losh
739e98e26cdSWarner Losh20000705:
740e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
741e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
742e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
743e98e26cdSWarner Losh	details.
744e98e26cdSWarner Losh
745c373950eSWarner Losh20000704:
7462f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
7472f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
7482f961bc8SWarner Losh
7492f961bc8SWarner Losh20000704:
750c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
751c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
752c373950eSWarner Losh	rc.d scripts that haven't been updated.
753c373950eSWarner Losh
75427dc3a2bSWarner Losh20000630:
75527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
75627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
75727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
75827dc3a2bSWarner Losh
759b8c215acSWarner Losh20000625:
760b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
76127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
76227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
76327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
76427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
76527dc3a2bSWarner Losh	were required.  You should check with the latest collections
76627dc3a2bSWarner Losh	to make sure that these haven't changed.
767b8c215acSWarner Losh
7687b990719SWarner Losh20000624:
7697b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
7707b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
7717b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
7721a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
7737b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
7747b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
7757b990719SWarner Losh	date to the completion of the work.
7767b990719SWarner Losh
77727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
77827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
77927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
78027dc3a2bSWarner Losh	recreate the random and urandom devices.
78127dc3a2bSWarner Losh
78281e54c50SWarner Losh20000622:
78381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
78481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
78581e54c50SWarner Losh	that used to be required when updating.
78681e54c50SWarner Losh
78739943833SWarner Losh20000621:
7882c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
7892a2f33fbSDaniel Baker	the config file update procedure.
7902a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
791c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
792a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
79339943833SWarner Losh
794290f9ad8SWarner Losh20000620:
795290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
796290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
797290f9ad8SWarner Losh	that workaround will no longer be required.
798290f9ad8SWarner Losh
79990fb6346SWarner Losh20000615:
80090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
80190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
80290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
80390fb6346SWarner Losh	devices.
80490fb6346SWarner Losh
805f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
806f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
807f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
808f75f65bbSWarner Losh	may work).
809f75f65bbSWarner Losh
810ba26da8eSWarner Losh20000612:
811ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
812290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
813c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
814290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
815f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
816f54a3542SWarner Losh	NEWCARD for examples of the new format.
817290f9ad8SWarner Losh
8189698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
8199698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
8209698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
8219698f2c0SWarner Losh	in it.
822bbcc5149SWarner Losh
823d65850ebSWarner Losh20000522:
824ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
825d65850ebSWarner Losh	building a kernel after this point is advised that they need
826d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
827d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
828d65850ebSWarner Losh
829d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
830d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
831d9583a00SWarner Losh	is recommended that you don't set this option until the problem
832d9583a00SWarner Losh	is resolved.
833d9583a00SWarner Losh
8348039cedeSWarner Losh20000513:
8358039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
8368039cedeSWarner Losh
837d65850ebSWarner Losh20000510:
8388039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
8398039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
8408039cedeSWarner Losh	is requires for the boot blocks to build properly.
8418039cedeSWarner Losh
8428039cedeSWarner Losh20000503:
8438039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
8448039cedeSWarner Losh	is now available.
8458039cedeSWarner Losh
846d65850ebSWarner Losh20000502:
847d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
848d65850ebSWarner Losh	connected to the kernel building instead.
849d65850ebSWarner Losh
850be149406SNik Clayton20000427:
8518039cedeSWarner Losh	You may need to build gperf
8528039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
8538039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
8548039cedeSWarner Losh	an option only in -current.
8558039cedeSWarner Losh
8562b8dd5f4SWarner Losh20000417:
8572b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
858f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
8592b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
8602b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
8612c021c6cSMark Ovens	before you reboot, you'll need to issue:
8622b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
8632b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
8642b8dd5f4SWarner Losh
8658d9f1945SWarner Losh20000320:
8662b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
8672b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
8682b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
869ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
8702b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
8718d9f1945SWarner Losh
872f8ab1dd6SWarner Losh20000319:
873f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
874f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
875f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
876f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
877f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
878f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
879f8ab1dd6SWarner Losh
88019cada77SWarner Losh20000318:
881f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
88219cada77SWarner Losh	Large kernel changes are being committed and are in the
88319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
88419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
88519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
88619cada77SWarner Losh	that you are loading are up to date.
887ba228352SWarner Losh
88819cada77SWarner Losh20000315:
8896d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
8906d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
8916d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
8926d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
8936d23c382SWarner Losh	boot.
8946d23c382SWarner Losh
8956d23c382SWarner Losh20000315:
89619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
89719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
89857199806SWarner Losh
899dc0dbf5cSWarner LoshCOMMON ITEMS:
900dc0dbf5cSWarner Losh
901a24eff53SWarner Losh	General Notes
902a24eff53SWarner Losh	-------------
903a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
904a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
905a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
906a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
907a24eff53SWarner Losh	or several minor releases, or when several months have passed
908a24eff53SWarner Losh	on the -current branch).
909a24eff53SWarner Losh
9105780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
9115780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
9125780f3baSWarner Losh	environment when searching for values for global variables.
9135780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
9145780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
9155780f3baSWarner Losh	page for more details.
9165780f3baSWarner Losh
917dc0dbf5cSWarner Losh	To build a kernel
918dc0dbf5cSWarner Losh	-----------------
919ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
920f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
921ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
9221e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9231e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
924dc0dbf5cSWarner Losh
925ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
926ba01eb20SWarner Losh	--------------------------------------------------------------
927ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
92847d0d01fSWarner Losh	config KERNEL_NAME_HERE
929ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
930ba01eb20SWarner Losh	make depend
931ba01eb20SWarner Losh	make
932ba01eb20SWarner Losh	make install
933ba01eb20SWarner Losh
934ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
935ba01eb20SWarner Losh
936ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
937ba01eb20SWarner Losh	-----------------------------------------------------------
938759f0aefSWarner Losh	make world
939fdb9f54dSWarner Losh	Build a new kernel, see above.
940759f0aefSWarner Losh
9411dece4a9SWarner Losh	To upgrade from 4.x-stable to current
942ba26da8eSWarner Losh	-------------------------------------
943ba26da8eSWarner Losh	make buildworld
9441e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9457595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
946f6a0ef01SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE [6]
947ee6e1fc3SWarner Losh	reboot in single user [3]
948835284beSWarner Losh	mergemaster -p		[5]
949ba26da8eSWarner Losh	make installworld
950a6cd4f9dSWarner Losh	mergemaster		[4]
951134d2e86SWarner Losh	[1]
952ba26da8eSWarner Losh	<reboot>
953ba26da8eSWarner Losh
954fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
955fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
956fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
957fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
958fdb9f54dSWarner Losh	the UPDATING entries.
959ba26da8eSWarner Losh
9601dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
9611dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
9621dece4a9SWarner Losh	your sources that you have read and understood all the recent
9631dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
9641dece4a9SWarner Losh	much fewer pitfalls.
9651dece4a9SWarner Losh
966134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
967134d2e86SWarner Losh	should disable them at this point so they don't crash your
968134d2e86SWarner Losh	system on reboot.
969134d2e86SWarner Losh
9709c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
9719c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
9729c1a7444SWarner Losh	configuration.
9739c1a7444SWarner Losh
974ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
975ee6e1fc3SWarner Losh		fsck -p
976ee6e1fc3SWarner Losh		mount -u /
977ee6e1fc3SWarner Losh		mount -a
978ee6e1fc3SWarner Losh		cd /usr/src
97947d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
980f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
981f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
982ee6e1fc3SWarner Losh
983a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
984a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
985a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
986a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
987a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
988a6cd4f9dSWarner Losh	for potential gotchas.
989a6cd4f9dSWarner Losh
990835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
991835284beSWarner Losh	you may need to do this if you get unknown user in the following
992835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
993835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
994835284beSWarner Losh	install) after the buildworld before this step if you last updated
995835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
996835284beSWarner Losh
997f6a0ef01SWarner Losh	[6] You may get a warning from kldxref.  Ignore it.  It doesn't
998f6a0ef01SWarner Losh	matter.
999f6a0ef01SWarner Losh
1000dc0dbf5cSWarner LoshFORMAT:
1001dc0dbf5cSWarner Losh
1002f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
10031fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1004f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1005f8ab1dd6SWarner Loshprevious releases if your system is older than this.
10061fc1a0dcSWarner Losh
1007e72fd46aSWarner LoshCopyright information:
1008e72fd46aSWarner Losh
10099698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1010e72fd46aSWarner Losh
1011772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1012772730c7SWarner Loshmodification, in full or in part, in any form or format of this
10139698f2c0SWarner Loshdocument are permitted without further permission from the author.
1014e72fd46aSWarner Losh
1015e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1016e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1017e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1018e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1019e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1020e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1021e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1022e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1023e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1024e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1025e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1026e72fd46aSWarner Losh
1027e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1028e72fd46aSWarner Loshauthor a beer.
1029e72fd46aSWarner Losh
103022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1031772730c7SWarner Loshthis document.
1032772730c7SWarner Losh
103397d92980SPeter Wemm$FreeBSD$
1034