xref: /freebsd/UPDATING (revision 9d1d64f5a6217fb29d90ec8442c5b9f62e1fb85d)
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
209d1d64f5SWarner Losh20030115:
219d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
229d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
239d1d64f5SWarner Losh	properly.
249d1d64f5SWarner Losh
25161dc364SAlexander Kabaev20021222:
26161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
27161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
28161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
29161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
30161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
31161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
3284cc83efSAlexander Kabaev	rebuilt.
33161dc364SAlexander Kabaev
34fb4c8061SMartin Blapp20021216:
35fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
36fb4c8061SMartin Blapp	compatible with with suns TIRPC and also with NetBSD. You need
37fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
389d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
39fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
40fb4c8061SMartin Blapp
4117d47eb3SGiorgos Keramidas20021202:
4217d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
4317d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
4417d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
4517d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
4617d47eb3SGiorgos Keramidas
47a4459294SBill Fenner20021029:
48a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
49a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
50a4459294SBill Fenner	consumers in sync.
51a4459294SBill Fenner
52fc8c157fSWarner Losh20021024:
53fc8c157fSWarner Losh	Old, compatibility slices have been removed in GEOM kernels.  This
54fc8c157fSWarner Losh	means that you will have to update your /etc/fstab to not use
55fc8c157fSWarner Losh	disk devices of the form /dev/ad0a.  Instead, you now must
56fc8c157fSWarner Losh	specify /dev/ad0s1a, or whatever slice your FreeBSD partition
57fc8c157fSWarner Losh	really is on.  The old device names have gone away, so if you
58fc8c157fSWarner Losh	use them anywhere else, you must also adjust those uses.
5969f7bcf3SWarner Losh
60fd9e8bdaSAndrew Gallatin20021023:
61fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
62fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
63fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
64fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
65fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
66fd9e8bdaSAndrew Gallatin
67fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
68fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
69fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
70fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
71fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
72fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
73fd9e8bdaSAndrew Gallatin
74f8a4c901SWarner Losh20020831:
75f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
76f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
77f8a4c901SWarner Losh	programs and libraries need to be recompiled.
78f8a4c901SWarner Losh
79f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
80f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
81f8a4c901SWarner Losh
82c2248fa2SJens Schweikhardt20020827:
83c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
84c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
85c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
86c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
87c2248fa2SJens Schweikhardt
880d533e43SRuslan Ermilov20020815:
890d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
900d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
910d533e43SRuslan Ermilov	again.
920d533e43SRuslan Ermilov
9333c1de7dSRuslan Ermilov20020729:
9433c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
9533c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
9633c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
9733c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
9833c1de7dSRuslan Ermilov
992b877facSJulian Elischer20020702:
1002b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
1012b877facSJulian Elischer	There are still some minor problems with some signals but the
1022b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
1032b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
1042b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
1052b877facSJulian Elischer
10606596d37SWarner Losh20020701:
10706596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
10806596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
10906596d37SWarner Losh	GNOME.
11006596d37SWarner Losh
11195ba4330SJacques Vidrine20020511:
11295ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
11395ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
11495ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
11595ba4330SJacques Vidrine	with the set-user-ID bit set.
11695ba4330SJacques Vidrine
117a81da3c9SDavid E. O'Brien20020510:
118f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
119f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
1204b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
121f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
122f50caf6fSDavid E. O'Brien
123f50caf6fSDavid E. O'Brien20020510:
124a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
125a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
126a81da3c9SDavid E. O'Brien	and then do a cvs update.
127a81da3c9SDavid E. O'Brien
128528a0ef5SJacques Vidrine20020421:
129528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
130528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
131528a0ef5SJacques Vidrine
13285aa5a2eSGregory Neil Shapiro20020404:
13385aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
13485aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
13585aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
13685aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
13785aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
13885aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
13985aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
14085aa5a2eSGregory Neil Shapiro
1418f1e4358SRuslan Ermilov20020403:
1428f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
1438f1e4358SRuslan Ermilov
1442292c02eSWarner Losh20020315:
1452292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
1462292c02eSWarner Losh
14769f7bcf3SWarner Losh20020225:
14869f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
14969f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
15069f7bcf3SWarner Losh
1518f35c493SWarner Losh20020217:
1528f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
1538f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
1548f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
1558f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
1568f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
1578f35c493SWarner Losh
158835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
159835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
160835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
161835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
162835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
163835284beSWarner Losh	and group must be merged from src/etc/group and
164835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
165835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
166835284beSWarner Losh	mergemaster before this will work if you are updating from a
167835284beSWarner Losh	very old version of current.  The updating recipe has changed
168835284beSWarner Losh	as of this date.
169835284beSWarner Losh
170fa9401c1SWarner Losh20020112:
171fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
172fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
173fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
174fa9401c1SWarner Losh	you have local modifications, you can use
175fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
176fa9401c1SWarner Losh	/etc/pam.d.
177fa9401c1SWarner Losh
178fa9401c1SWarner Losh	Please see the following url for more details:
179fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
18047d0d01fSWarner Losh20011229:
18147d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
18247d0d01fSWarner Losh	networkfs_types, please note that it has changed
18347d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
18447d0d01fSWarner Losh
185514318a8SWarner Losh20011220:
186514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
187514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
188514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
189514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
190514318a8SWarner Losh	version have now been merged back into the base system's
191514318a8SWarner Losh	version now.  The only user-visible change resulting from this
192514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
193514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
194514318a8SWarner Losh	as well.  (There has never been rc file support for
195514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
196514318a8SWarner Losh	reverted by the time the changes are MFCed.)
197514318a8SWarner Losh
198514318a8SWarner Losh20011215:
199514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
200514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
201514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
202514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
203514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
204514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
205514318a8SWarner Losh	will need to be customized then for `odd' densities using
206514318a8SWarner Losh	fdcontrol(8).
207514318a8SWarner Losh
2082d22e2bfSWarner Losh20011209:
2092d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
2102d22e2bfSWarner Losh	and truss(1) now works again.
2112d22e2bfSWarner Losh
2129e0428e2SWarner Losh20011207:
2139e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
2149e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
2159e0428e2SWarner Losh	see
2169e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
2179e0428e2SWarner Losh	for details.
2189e0428e2SWarner Losh
2199bab8c59SWarner Losh20011204:
2209bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
2219bab8c59SWarner Losh	kernel and burncd to be in sync.
2229bab8c59SWarner Losh
223e57d8b01SWarner Losh20011203:
224e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
225e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
226e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
227e57d8b01SWarner Losh	not there already.
228e57d8b01SWarner Losh
229e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
230e57d8b01SWarner Losh	until the issue has been resolved.
231e57d8b01SWarner Losh
232b001d36fSJacques Vidrine20011202:
233b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
234b001d36fSJacques Vidrine	patched.
235b001d36fSJacques Vidrine
2364b676ec1SWarner Losh20011126:
2374b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
2385ebbf43eSWarner Losh	after this date.  You need to do this only once.
2394b676ec1SWarner Losh
240d961e462SWarner Losh20011103:
241d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
242d961e462SWarner Losh	edges may be left, but for the most part things should be
2434b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
244d961e462SWarner Losh
245d961e462SWarner Losh20011030:
246d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
247d961e462SWarner Losh	choppy waves in the upgrade process.
248d961e462SWarner Losh
2491fe003b6SWarner Losh20011030:
250a4b6fda0SWarner Losh	The asr driver problem has been resolved.
2511fe003b6SWarner Losh
2521fe003b6SWarner Losh20011027:
2531fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
2541fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
2551fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
2561fe003b6SWarner Losh	try to use from this date forward.
2571fe003b6SWarner Losh
2581fe003b6SWarner Losh20011025:
2591fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
2601fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
2611fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
2621fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
2631fe003b6SWarner Losh	TARGET_ARCH=i386.
2641fe003b6SWarner Losh
265d05f9643SWarner Losh20011001:
266d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
267d05f9643SWarner Losh	You must recompile both the kernel and userland applications
268d05f9643SWarner Losh	at the same time.
269d05f9643SWarner Losh
27058970f85SWarner Losh20010929:
27158970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
27258970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
27358970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
27458970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
2759d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
27658970f85SWarner Losh
27758970f85SWarner Losh20010927:
27858970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
27958970f85SWarner Losh	To disable ACPI you can add
280378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
28158970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
28258970f85SWarner Losh	loader "ok" prompt).
28358970f85SWarner Losh
28458970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
28558970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
28658970f85SWarner Losh	file and not list acpi in that list.
287378f4486SAlfred Perlstein
2885119d237SWarner Losh20010924:
2895119d237SWarner Losh	The buildworld has been fixed.  You may need to install
2905119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
2918b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
2928b039fffSWarner Losh	get them installed on every installworld, or execute the
2938b039fffSWarner Losh	following to get them installed only once:
2948b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
29558970f85SWarner Losh		make all install
2968b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
2975119d237SWarner Losh
2983c293725SWarner Losh20010919:
2993c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
3003c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
3013c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
302772730c7SWarner Losh	workaround is to add
3033c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
3043c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
3053c293725SWarner Losh	can be removed afterwards.
3063c293725SWarner Losh
3073c293725SWarner Losh	A proper fix to the buildworld target is needed.
3083c293725SWarner Losh
3093c293725SWarner Losh20010918:
3103c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
3113c293725SWarner Losh	NFS may be unstable after this date.
3123c293725SWarner Losh
3133c293725SWarner Losh20010912:
3143c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
3153c293725SWarner Losh	the kernel.  While a few problems were introduced in the
3163c293725SWarner Losh	initial commit, most of the major ones have been found and
3173c293725SWarner Losh	corrected.
3183c293725SWarner Losh
3193c293725SWarner Losh20010901:
3203c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
3213c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
3223c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
3233c293725SWarner Losh	have been rectified around this date.
3243c293725SWarner Losh
32598b17b95SWarner Losh20010823:
32698b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
32798b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
32898b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
32998b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
33098b17b95SWarner Losh 	sure that user or group bind has read (and not write)
33198b17b95SWarner Losh 	permission for your name server configuration and that it
33298b17b95SWarner Losh 	has read and write permission for your slave zone files and
33398b17b95SWarner Losh 	directory.
33498b17b95SWarner Losh
33598b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
33698b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
33798b17b95SWarner Losh
33898b17b95SWarner Losh 		named_flags=
33998b17b95SWarner Losh
3407b9786edSMark Murray20010709:
3417b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
3427b9786edSMark Murray	the ability of the shared library major number to handle.
3437b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
3447b9786edSMark Murray	solution is to rebuild those ports.
3457b9786edSMark Murray
3461d28950eSWarner Losh20010628:
3471d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
3481d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
3491d28950eSWarner Losh
350e72fd46aSWarner Losh20010625:
35198b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
35298b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
35398b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
35498b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
35598b17b95SWarner Losh	IRQ configuration needs more safety belts.
35616de1a07SWarner Losh
3570d415dffSWarner Losh20010617:
358e72fd46aSWarner Losh	Softupdates problems have been corrected.
3590d415dffSWarner Losh
3600d415dffSWarner Losh20010614:
3610d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
3620d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
3630d415dffSWarner Losh	kernel building methods.
3640d415dffSWarner Losh
3658b9959adSWarner Losh20010613:
3668b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
3678b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
368e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
369e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
3708b9959adSWarner Losh
371e72fd46aSWarner Losh20010613:
3728b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
373e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
374e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
3758b9959adSWarner Losh
3760d415dffSWarner Losh20010612:
3770d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
3780d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
3790d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
3800d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
3810d415dffSWarner Losh	until this bug is fixed.
3820d415dffSWarner Losh
383e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
384e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
385e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
386e72fd46aSWarner Losh
3870d415dffSWarner Losh20010610:
3880d415dffSWarner Losh	Locale names have changed to match other systems better.
3890d415dffSWarner Losh
3906ccdb5e4SWarner Losh20010604:
3916ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
3926ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
3936ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
3943590182eSWarner Losh	Interrupt storms look a lot like a hang.
3953590182eSWarner Losh
3963590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
3973590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
3983590182eSWarner Losh	it is).
3993590182eSWarner Losh
4003590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
4013590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
4023590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
4033590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
4046ccdb5e4SWarner Losh
4050bc62786SWarner Losh20010530:
4060bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
4070bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
4080bc62786SWarner Losh	a limited time.  If you see
4090bc62786SWarner Losh
4100bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
4110bc62786SWarner Losh
4120bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
4130bc62786SWarner Losh	COPY=-C.
4140bc62786SWarner Losh
41568a38c6cSWarner Losh20010525:
416b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
417c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
418c4f4a728SWarner Losh	definitely is in bad shape.
41968a38c6cSWarner Losh
420ed0f29caSWarner Losh20010521:
421f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
422ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
423ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
424ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
425ed0f29caSWarner Losh	is
426ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
427ed0f29caSWarner Losh
42880c16af9SWarner Losh20010520:
42968a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
43080c16af9SWarner Losh
43180c16af9SWarner Losh20010519:
43280c16af9SWarner Losh	pccard has had much reorganizational work done to it over
43380c16af9SWarner Losh	the past few days.  Everything should still work, but if
43480c16af9SWarner Losh	not, please contact imp@freebsd.org.
43580c16af9SWarner Losh
436a45f2d05SWarner Losh20010517:
437a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
438a45f2d05SWarner Losh	userland at the same time.
439a45f2d05SWarner Losh
440a45f2d05SWarner Losh20010517:
441a45f2d05SWarner Losh	New ncurses imported.
442a45f2d05SWarner Losh
4432988afcaSWarner Losh20010512:
4442988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
4452988afcaSWarner Losh	will be the only way to go starting July 1.
4462988afcaSWarner Losh
4471a33dba7SWarner Losh20010504:
4481a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
4491a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
4501a33dba7SWarner Losh
45109946a51SWarner Losh20010502:
45209946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
45309946a51SWarner Losh
45409946a51SWarner Losh20010501:
45509946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
45609946a51SWarner Losh
45709946a51SWarner Losh20010430:
458a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
45909946a51SWarner Losh	go back in the water.
46009946a51SWarner Losh
46109946a51SWarner Losh20010429:
46209946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
46309946a51SWarner Losh	this date, but before the correction date.
46409946a51SWarner Losh
46591dd3b53SWarner Losh20010423:
46691dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
46791dd3b53SWarner Losh
46891dd3b53SWarner Losh20010411:
46991dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
47091dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
47191dd3b53SWarner Losh	Update only if you understand that you must not use the old
47291dd3b53SWarner Losh	fsck with the new kernel ever.
47391dd3b53SWarner Losh
474933b3269SWarner Losh20010330:
475933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
476c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
477933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
478933b3269SWarner Losh
479933b3269SWarner Losh20010319:
480933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
481933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
482933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
483f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
48409946a51SWarner Losh
48509946a51SWarner Losh20010315:
48609946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
48709946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
48809946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
489933b3269SWarner Losh
490933b3269SWarner Losh20010312:
491933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
492933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
493933b3269SWarner Losh
494933b3269SWarner Losh20010312:
495933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
496933b3269SWarner Losh	instead of ad-hoc.
497933b3269SWarner Losh
498933b3269SWarner Losh20010310:
499f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
500933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
501933b3269SWarner Losh	ssh might not work if you don't.
502933b3269SWarner Losh
50362353691SWarner Losh20010303:
50462353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
50562353691SWarner Losh	which means that you must include the miibus in your kernel if
50662353691SWarner Losh	you use the ed driver.
50762353691SWarner Losh
508d325cf65SWarner Losh20010220:
509d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
510d325cf65SWarner Losh	safe to go back into the water.
511d325cf65SWarner Losh
512024daae6SWarner Losh20010211:
513024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
514024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
515024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
516024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
517024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
518024daae6SWarner Losh
519024daae6SWarner Losh	To get to the new system, you'll need to use the following
520024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
521024daae6SWarner Losh	don't have to move this to the updating section.
522024daae6SWarner Losh
523024daae6SWarner Losh	To get around the installworld problem, do:
524024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
525024daae6SWarner Losh		# make install
526024daae6SWarner Losh		# cd /usr/src
527024daae6SWarner Losh		# make installworld
528024daae6SWarner Losh	If that doesn't work, then try:
529024daae6SWarner Losh		# make -k installworld
530024daae6SWarner Losh		# make installworld
531024daae6SWarner Losh
532024daae6SWarner Losh20010207:
533024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
534024daae6SWarner Losh	do not include devfs in your kernel as problems result.
535024daae6SWarner Losh
536024daae6SWarner Losh20010205:
5377595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
538024daae6SWarner Losh	Remove them from your config.
539024daae6SWarner Losh
5401e159248SWarner Losh20010122:
5411e159248SWarner Losh	****************************** WARNING ******************************
5421e159248SWarner Losh			buildkernel has been changed slightly
5431e159248SWarner Losh	****************************** WARNING ******************************
5441e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
5451e159248SWarner Losh	should update your scripts and make.conf accordingly.
5461e159248SWarner Losh
5471e159248SWarner Losh20010119:
5481e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
5491e159248SWarner Losh	This requires a new config to build correctly.
5501e159248SWarner Losh
551aac7dfeaSWarner Losh20010116:
552aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
553aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
554aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
555aac7dfeaSWarner Losh
556aac7dfeaSWarner Losh20010110:
557aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
558aac7dfeaSWarner Losh
559aac7dfeaSWarner Losh20010102:
560aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
561aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
562aac7dfeaSWarner Losh
56363c90c9eSWarner Losh20010101:
56463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
56563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
5665fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
56763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
56863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
56963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
57063c90c9eSWarner Losh	might have been ignored by the -k option.
57163c90c9eSWarner Losh
5725fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
5735fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
5745fd2a895SWarner Losh	of this working.
5755fd2a895SWarner Losh
576aac7dfeaSWarner Losh20001228:
577aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
578aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
579aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
580aac7dfeaSWarner Losh
581de2bcc63SWarner Losh20001218:
582de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
583de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
584de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
585de2bcc63SWarner Losh	cards will not be recognized without it.
586de2bcc63SWarner Losh
587960773f7SWarner Losh20001205:
588960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
589960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
590960773f7SWarner Losh	adding the following in pam.conf:
591960773f7SWarner Losh
592960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
593960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
594960773f7SWarner Losh	sshd    session required        pam_permit.so
595960773f7SWarner Losh
5960acc635eSWarner Losh20001031:
5970acc635eSWarner Losh	cvs updated to 1.11.
5980acc635eSWarner Losh
5990acc635eSWarner Losh20001020:
6000acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
6010acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
6020acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
6030acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
6040acc635eSWarner Losh	workaround.
6050acc635eSWarner Losh
6060acc635eSWarner Losh20001010:
6070acc635eSWarner Losh	****************************** WARNING ******************************
6080acc635eSWarner Losh				Sendmail has been updated.
6090acc635eSWarner Losh	****************************** WARNING ******************************
6100acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
6110acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
6120acc635eSWarner Losh	  is set.
6130acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
6140acc635eSWarner Losh	  commands.
6150acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
6160acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
6170acc635eSWarner Losh	  in /usr/share/sendmail/cf.
6180acc635eSWarner Losh	o sendmail.cw changed to local-host-names
6190acc635eSWarner Losh
6200acc635eSWarner Losh	More details can be found at
6210acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
6220acc635eSWarner Losh
6236e98a146SWarner Losh20001009:
6246e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
6256e98a146SWarner Losh	your entire ports tree, or you will have problems.
6266e98a146SWarner Losh
6276e98a146SWarner Losh20001006:
628685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
6296e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
6306e98a146SWarner Losh	/usr/bin/miniperl.
6316e98a146SWarner Losh
632073113a4SWarner Losh20001005:
633073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
634685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
635073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
636073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
637073113a4SWarner Losh	tree for anything to work.
638073113a4SWarner Losh
6390acc635eSWarner Losh20000928:
6400acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
6410acc635eSWarner Losh
642be3885b3SWarner Losh20000916:
643be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
644be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
645be3885b3SWarner Losh	same time as your kernel.
646be3885b3SWarner Losh
64776ec9675SWarner Losh20000914:
64876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
64976ec9675SWarner Losh	include the device will cause suspended laptops losing time
65076ec9675SWarner Losh	when they resume.  Include
65176ec9675SWarner Losh		device		pmtimer
65276ec9675SWarner Losh	in your config file and
65301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
65476ec9675SWarner Losh	to your /boot/device.hints file.
65576ec9675SWarner Losh
656f4865386SMark Murray20000911:
657f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
658f4865386SMark Murray	rather than an option. The supplied kernel config files have
659f4865386SMark Murray	been updated. You will need to do something similar in your
660f4865386SMark Murray	own kernel config file.
661f4865386SMark Murray	Remove:
662f4865386SMark Murray		options		RANDOMDEV
663f4865386SMark Murray	Add:
664f4865386SMark Murray		device		random
665f4865386SMark Murray	If you prefer to load the loadable module, you need to do
666f4865386SMark Murray	nothing.
667f4865386SMark Murray
668d594498fSWarner Losh20000909:
669d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
670d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
671d594498fSWarner Losh	reflect this if you load this module at boot time.
672d594498fSWarner Losh	The line should read:
673d594498fSWarner Losh		random_load="YES"
674d594498fSWarner Losh
6750deb7ddcSWarner Losh20000907:
6760deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
67716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
67816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
67916eb772dSWarner Losh	sure you don't have model loading problems which might at
68016eb772dSWarner Losh	first blush appear related to SMP.
68152bf24e7SWarner Losh
6825a01880bSWarner Losh20000906:
6835a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
6845a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
6855a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
6865a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
6875a01880bSWarner Losh	don't have one, and you have host.conf.
6885a01880bSWarner Losh
6892b41163cSWarner Losh20000905:
69038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
69138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
69238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
69338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
69438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
69538d6ecd2SWarner Losh
69638d6ecd2SWarner Losh20000905:
6978aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
6988aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
6998aab4bc7SWarner Losh	is /boot/kernel.
7008aab4bc7SWarner Losh
7018aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
70238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
70338d6ecd2SWarner Losh	installkernel/installworld dance.
7042b41163cSWarner Losh
705d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
706d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
707d594498fSWarner Losh	modules in that directory instead of finding them in the correct
708d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
709d594498fSWarner Losh	is that the linux module crashes your machine after the update.
710d594498fSWarner Losh
711d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
712d594498fSWarner Losh		mv /modules.old /boot/kernel.old
713d594498fSWarner Losh		chflags noschg /kernel.old
714d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
715d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
716d594498fSWarner Losh	fi
717d594498fSWarner Losh
718c22a309cSWarner Losh20000904:
719c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
720c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
721c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
722c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
723c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
724c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
725c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
726c22a309cSWarner Losh	is not likely to be generated.
727c22a309cSWarner Losh
728fdb9f54dSWarner Losh20000825:
729fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
7309c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
7319c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
7329c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
7339c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
7349c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
7359c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
7369c1a7444SWarner Losh	kernel.
7379c1a7444SWarner Losh
7389c1a7444SWarner Losh20000821:
7399c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
7409c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
7419c1a7444SWarner Losh	/boot/loader.conf.
742fdb9f54dSWarner Losh
7438f250aa7SWarner Losh20000812:
7445da0d091SWarner Losh	suidperl is now always built and installed on the system, but
7455da0d091SWarner Losh	with permissions of 511.  If you have applications that use
7465da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
7475da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
7485da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
7495da0d091SWarner Losh	will fix this until the next build.
7505da0d091SWarner Losh
7515da0d091SWarner Losh20000812:
7528f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
7538f250aa7SWarner Losh	visible changes that may immediately affect your configuration
7548f250aa7SWarner Losh	include:
7558f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
7568f250aa7SWarner Losh	- newaliases limited to root and trusted users
7578f250aa7SWarner Losh	- MSA port (587) turned on by default
7588f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
7598f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
7608f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
7618f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
7628f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
7638f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
7648f250aa7SWarner Losh
76571c38472SWarner Losh20000810:
76671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
76771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
76871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
76971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
77071c38472SWarner Losh	specific use for it.
77171c38472SWarner Losh
77271c38472SWarner Losh20000729:
77371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
77471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
77571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
77671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
77771c38472SWarner Losh		# Enable network daemons for user convenience.
77871c38472SWarner Losh		inetd_enable="YES"
77971c38472SWarner Losh		portmap_enable="YES"
78071c38472SWarner Losh		sendmail_enable="YES"
78171c38472SWarner Losh
78271c38472SWarner Losh20000728:
78371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
78471c38472SWarner Losh	will need to change that to nullfs_load="YES".
78571c38472SWarner Losh
7861dece4a9SWarner Losh20000728:
7871dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
7881dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
7891dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
7901dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
7911dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
7921dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
7931dece4a9SWarner Losh	to /MYKERNEL.
7941dece4a9SWarner Losh
795409e887cSWarner Losh20000711:
796409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
797409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
798409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
799409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
800409e887cSWarner Losh	for details on potential problems that you might have and how
801409e887cSWarner Losh	to get around them.
802409e887cSWarner Losh
803409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
804409e887cSWarner Losh	clauses above, you needn't worry.
805409e887cSWarner Losh
806409e887cSWarner Losh20000711:
807409e887cSWarner Losh	/etc/security has been updated to print the inode number of
808409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
809409e887cSWarner Losh	in the number of changed programs the first time when you run
810409e887cSWarner Losh	mergemaster to get a new /etc/security.
811409e887cSWarner Losh
812673d13f2SWarner Losh20000710:
813673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
814673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
815673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
816673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
817673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
818673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
819673d13f2SWarner Losh	errors. (see below, 20000624).
820673d13f2SWarner Losh
821bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
8221dece4a9SWarner Losh
823673d13f2SWarner Losh20000709:
824c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
825c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
826c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
827673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
828673d13f2SWarner Losh
829e98e26cdSWarner Losh20000706:
830e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
831e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
832e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
833f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
834e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
8352c021c6cSMark Ovens	interim if needed.
836e98e26cdSWarner Losh
837e98e26cdSWarner Losh20000705:
838e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
839e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
840e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
841e98e26cdSWarner Losh	details.
842e98e26cdSWarner Losh
843c373950eSWarner Losh20000704:
8442f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
8452f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
8462f961bc8SWarner Losh
8472f961bc8SWarner Losh20000704:
848c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
849c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
850c373950eSWarner Losh	rc.d scripts that haven't been updated.
851c373950eSWarner Losh
85227dc3a2bSWarner Losh20000630:
85327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
85427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
85527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
85627dc3a2bSWarner Losh
857b8c215acSWarner Losh20000625:
858b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
85927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
86027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
86127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
86227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
86327dc3a2bSWarner Losh	were required.  You should check with the latest collections
86427dc3a2bSWarner Losh	to make sure that these haven't changed.
865b8c215acSWarner Losh
8667b990719SWarner Losh20000624:
8677b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
8687b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
8697b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
8701a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
8717b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
8727b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
8737b990719SWarner Losh	date to the completion of the work.
8747b990719SWarner Losh
87527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
87627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
87727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
87827dc3a2bSWarner Losh	recreate the random and urandom devices.
87927dc3a2bSWarner Losh
88081e54c50SWarner Losh20000622:
88181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
88281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
88381e54c50SWarner Losh	that used to be required when updating.
88481e54c50SWarner Losh
88539943833SWarner Losh20000621:
8862c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
8872a2f33fbSDaniel Baker	the config file update procedure.
8882a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
889c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
890a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
89139943833SWarner Losh
892290f9ad8SWarner Losh20000620:
893290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
894290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
895290f9ad8SWarner Losh	that workaround will no longer be required.
896290f9ad8SWarner Losh
89790fb6346SWarner Losh20000615:
89890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
89990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
90090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
90190fb6346SWarner Losh	devices.
90290fb6346SWarner Losh
903f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
904f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
905f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
906f75f65bbSWarner Losh	may work).
907f75f65bbSWarner Losh
908ba26da8eSWarner Losh20000612:
909ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
910290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
911c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
912290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
913f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
914f54a3542SWarner Losh	NEWCARD for examples of the new format.
915290f9ad8SWarner Losh
9169698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
9179698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
9189698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
9199698f2c0SWarner Losh	in it.
920bbcc5149SWarner Losh
921d65850ebSWarner Losh20000522:
922ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
923d65850ebSWarner Losh	building a kernel after this point is advised that they need
924d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
925d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
926d65850ebSWarner Losh
927d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
928d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
929d9583a00SWarner Losh	is recommended that you don't set this option until the problem
930d9583a00SWarner Losh	is resolved.
931d9583a00SWarner Losh
9328039cedeSWarner Losh20000513:
9338039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
9348039cedeSWarner Losh
935d65850ebSWarner Losh20000510:
9368039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
9378039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
9388039cedeSWarner Losh	is requires for the boot blocks to build properly.
9398039cedeSWarner Losh
9408039cedeSWarner Losh20000503:
9418039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
9428039cedeSWarner Losh	is now available.
9438039cedeSWarner Losh
944d65850ebSWarner Losh20000502:
945d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
946d65850ebSWarner Losh	connected to the kernel building instead.
947d65850ebSWarner Losh
948be149406SNik Clayton20000427:
9498039cedeSWarner Losh	You may need to build gperf
9508039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
9518039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
9528039cedeSWarner Losh	an option only in -current.
9538039cedeSWarner Losh
9542b8dd5f4SWarner Losh20000417:
9552b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
956f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
9572b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
9582b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
9592c021c6cSMark Ovens	before you reboot, you'll need to issue:
9602b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
9612b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
9622b8dd5f4SWarner Losh
9638d9f1945SWarner Losh20000320:
9642b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
9652b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
9662b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
967ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
9682b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
9698d9f1945SWarner Losh
970f8ab1dd6SWarner Losh20000319:
971f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
972f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
973f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
974f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
975f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
976f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
977f8ab1dd6SWarner Losh
97819cada77SWarner Losh20000318:
979f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
98019cada77SWarner Losh	Large kernel changes are being committed and are in the
98119cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
98219cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
98319cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
98419cada77SWarner Losh	that you are loading are up to date.
985ba228352SWarner Losh
98619cada77SWarner Losh20000315:
9876d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
9886d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
9896d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
9906d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
9916d23c382SWarner Losh	boot.
9926d23c382SWarner Losh
9936d23c382SWarner Losh20000315:
99419cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
99519cada77SWarner Losh	to upgrade to 4.0 from 3.x.
99657199806SWarner Losh
997dc0dbf5cSWarner LoshCOMMON ITEMS:
998dc0dbf5cSWarner Losh
999a24eff53SWarner Losh	General Notes
1000a24eff53SWarner Losh	-------------
1001a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1002a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1003a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1004a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1005a24eff53SWarner Losh	or several minor releases, or when several months have passed
1006a24eff53SWarner Losh	on the -current branch).
1007a24eff53SWarner Losh
10085780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
10095780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
10105780f3baSWarner Losh	environment when searching for values for global variables.
10115780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
10125780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
10135780f3baSWarner Losh	page for more details.
10145780f3baSWarner Losh
1015dc0dbf5cSWarner Losh	To build a kernel
1016dc0dbf5cSWarner Losh	-----------------
1017ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1018f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1019ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
10201e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
10211e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
1022dc0dbf5cSWarner Losh
1023ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1024ba01eb20SWarner Losh	--------------------------------------------------------------
1025ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
102647d0d01fSWarner Losh	config KERNEL_NAME_HERE
1027ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1028ba01eb20SWarner Losh	make depend
1029ba01eb20SWarner Losh	make
1030ba01eb20SWarner Losh	make install
1031ba01eb20SWarner Losh
1032ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1033ba01eb20SWarner Losh
1034ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1035ba01eb20SWarner Losh	-----------------------------------------------------------
103663cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
103763cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
103863cb445eSWarner Losh
1039f643de42SWarner Losh	<make sure you have good level 0 dumps>
104063cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
104163cb445eSWarner Losh	make buildworld
104263cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
104363cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
104463cb445eSWarner Losh							[1]
104563cb445eSWarner Losh	<reboot in single user>				[3]
104663cb445eSWarner Losh	mergemaster -p					[5]
104763cb445eSWarner Losh	make installworld
104863cb445eSWarner Losh	mergemaster					[4]
104963cb445eSWarner Losh	<reboot>
105063cb445eSWarner Losh
1051759f0aefSWarner Losh
10521dece4a9SWarner Losh	To upgrade from 4.x-stable to current
1053ba26da8eSWarner Losh	-------------------------------------
10545c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
10555c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
10565c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
10575c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1058f643de42SWarner Losh	# to back out of problems with this proceedure.  If /tmp is on
1059f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1060f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1061f643de42SWarner Losh	# space on /.
1062f643de42SWarner Losh
1063f643de42SWarner Losh	<make sure you have good level 0 dumps>
1064fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
106521c075eaSWarner Losh	make buildworld					[9]
1066c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1067d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1068be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1069fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1070fc8c157fSWarner Losh							[1]
1071fc8c157fSWarner Losh	<reboot in single user>				[3]
1072835284beSWarner Losh	mergemaster -p					[5]
1073f8a4c901SWarner Losh	rm -rf /usr/include/g++
1074ba26da8eSWarner Losh	make installworld
1075a6cd4f9dSWarner Losh	mergemaster					[4]
1076ba26da8eSWarner Losh	<reboot>
1077ba26da8eSWarner Losh
1078fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1079fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1080fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1081fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1082fdb9f54dSWarner Losh	the UPDATING entries.
1083ba26da8eSWarner Losh
10841dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
10851dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
10861dece4a9SWarner Losh	your sources that you have read and understood all the recent
10871dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
10881dece4a9SWarner Losh	much fewer pitfalls.
10891dece4a9SWarner Losh
1090134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1091134d2e86SWarner Losh	should disable them at this point so they don't crash your
1092134d2e86SWarner Losh	system on reboot.
1093134d2e86SWarner Losh
10949c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
10959c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
10969c1a7444SWarner Losh	configuration.
10979c1a7444SWarner Losh
1098ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1099ee6e1fc3SWarner Losh		fsck -p
1100ee6e1fc3SWarner Losh		mount -u /
1101ee6e1fc3SWarner Losh		mount -a
1102ee6e1fc3SWarner Losh		cd /usr/src
110347d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1104f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1105f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1106b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1107b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1108b705ae10SWarner Losh	be ignored while you proceed to the next step.
1109ee6e1fc3SWarner Losh
1110a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1111a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1112a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1113a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1114a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1115a6cd4f9dSWarner Losh	for potential gotchas.
1116a6cd4f9dSWarner Losh
1117835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1118835284beSWarner Losh	you may need to do this if you get unknown user in the following
1119835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1120835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1121835284beSWarner Losh	install) after the buildworld before this step if you last updated
1122835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1123835284beSWarner Losh
1124bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1125bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1126bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1127bd79cf40SWarner Losh		ok unload
1128bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1129bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1130bd79cf40SWarner Losh	described here.
1131fc8c157fSWarner Losh
1132fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1133fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1134fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1135fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1136fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1137fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1138fc8c157fSWarner Losh
1139c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1140c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1141c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1142c74fe6afSWarner Losh	that is hard to boot to recover.
1143c74fe6afSWarner Losh
114421c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
114521c075eaSWarner Losh	cvs prune empty directories.
1146dc0dbf5cSWarner LoshFORMAT:
1147dc0dbf5cSWarner Losh
1148f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
11491fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1150f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1151f8ab1dd6SWarner Loshprevious releases if your system is older than this.
11521fc1a0dcSWarner Losh
1153e72fd46aSWarner LoshCopyright information:
1154e72fd46aSWarner Losh
11559698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1156e72fd46aSWarner Losh
1157772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1158772730c7SWarner Loshmodification, in full or in part, in any form or format of this
11599698f2c0SWarner Loshdocument are permitted without further permission from the author.
1160e72fd46aSWarner Losh
1161e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1162e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1163e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1164e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1165e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1166e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1167e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1168e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1169e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1170e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1171e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1172e72fd46aSWarner Losh
1173e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1174e72fd46aSWarner Loshauthor a beer.
1175e72fd46aSWarner Losh
117622306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1177772730c7SWarner Loshthis document.
1178772730c7SWarner Losh
117997d92980SPeter Wemm$FreeBSD$
1180