xref: /freebsd/UPDATING (revision 9db58771e0f3803c5d063364ce555bfa1c3b02ac)
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
209db58771SPoul-Henning Kamp20030128
219db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
229db58771SPoul-Henning Kamp	This makes all references to MAKEDEV obsolete, and the should
239db58771SPoul-Henning Kamp	be removed when convenient.
249db58771SPoul-Henning Kamp
258d9b3f57SJake Burkholder20030126:
268d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
278d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
288d9b3f57SJake Burkholder
291c5efda5SJeff Roberson20030125:
301c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
311c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
321c5efda5SJeff Roberson	The in cvs config files have been updated to use the old scheduler
331c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
341c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
351c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
361c5efda5SJeff Roberson
379d1d64f5SWarner Losh20030115:
389d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
399d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
409d1d64f5SWarner Losh	properly.
419d1d64f5SWarner Losh
42c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
43c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
44c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
45c9fdb80aSWarner Losh	with NetBSD.
46c9fdb80aSWarner Losh
47161dc364SAlexander Kabaev20021222:
48161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
49161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
50161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
51161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
52161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
53161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
5484cc83efSAlexander Kabaev	rebuilt.
55161dc364SAlexander Kabaev
56fb4c8061SMartin Blapp20021216:
57fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
58fb4c8061SMartin Blapp	compatible with with suns TIRPC and also with NetBSD. You need
59fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
609d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
61fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
62fb4c8061SMartin Blapp
6317d47eb3SGiorgos Keramidas20021202:
6417d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
6517d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
6617d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
6717d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
6817d47eb3SGiorgos Keramidas
69a4459294SBill Fenner20021029:
70a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
71a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
72a4459294SBill Fenner	consumers in sync.
73a4459294SBill Fenner
74fc8c157fSWarner Losh20021024:
75fc8c157fSWarner Losh	Old, compatibility slices have been removed in GEOM kernels.  This
76fc8c157fSWarner Losh	means that you will have to update your /etc/fstab to not use
77fc8c157fSWarner Losh	disk devices of the form /dev/ad0a.  Instead, you now must
78fc8c157fSWarner Losh	specify /dev/ad0s1a, or whatever slice your FreeBSD partition
79fc8c157fSWarner Losh	really is on.  The old device names have gone away, so if you
80fc8c157fSWarner Losh	use them anywhere else, you must also adjust those uses.
8169f7bcf3SWarner Losh
82fd9e8bdaSAndrew Gallatin20021023:
83fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
84fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
85fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
86fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
87fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
88fd9e8bdaSAndrew Gallatin
89fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
90fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
91fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
92fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
93fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
94fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
95fd9e8bdaSAndrew Gallatin
96f8a4c901SWarner Losh20020831:
97f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
98f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
99f8a4c901SWarner Losh	programs and libraries need to be recompiled.
100f8a4c901SWarner Losh
101f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
102f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
103f8a4c901SWarner Losh
104c2248fa2SJens Schweikhardt20020827:
105c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
106c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
107c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
108c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
109c2248fa2SJens Schweikhardt
1100d533e43SRuslan Ermilov20020815:
1110d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
1120d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
1130d533e43SRuslan Ermilov	again.
1140d533e43SRuslan Ermilov
11533c1de7dSRuslan Ermilov20020729:
11633c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
11733c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
11833c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
11933c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
12033c1de7dSRuslan Ermilov
1212b877facSJulian Elischer20020702:
1222b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
1232b877facSJulian Elischer	There are still some minor problems with some signals but the
1242b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
1252b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
1262b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
1272b877facSJulian Elischer
12806596d37SWarner Losh20020701:
12906596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
13006596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
13106596d37SWarner Losh	GNOME.
13206596d37SWarner Losh
13395ba4330SJacques Vidrine20020511:
13495ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
13595ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
13695ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
13795ba4330SJacques Vidrine	with the set-user-ID bit set.
13895ba4330SJacques Vidrine
139a81da3c9SDavid E. O'Brien20020510:
140f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
141f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
1424b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
143f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
144f50caf6fSDavid E. O'Brien
145f50caf6fSDavid E. O'Brien20020510:
146a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
147a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
148a81da3c9SDavid E. O'Brien	and then do a cvs update.
149a81da3c9SDavid E. O'Brien
150528a0ef5SJacques Vidrine20020421:
151528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
152528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
153528a0ef5SJacques Vidrine
15485aa5a2eSGregory Neil Shapiro20020404:
15585aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
15685aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
15785aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
15885aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
15985aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
16085aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
16185aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
16285aa5a2eSGregory Neil Shapiro
1638f1e4358SRuslan Ermilov20020403:
1648f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
1658f1e4358SRuslan Ermilov
1662292c02eSWarner Losh20020315:
1672292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
1682292c02eSWarner Losh
16969f7bcf3SWarner Losh20020225:
17069f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
17169f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
17269f7bcf3SWarner Losh
1738f35c493SWarner Losh20020217:
1748f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
1758f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
1768f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
1778f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
1788f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
1798f35c493SWarner Losh
180835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
181835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
182835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
183835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
184835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
185835284beSWarner Losh	and group must be merged from src/etc/group and
186835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
187835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
188835284beSWarner Losh	mergemaster before this will work if you are updating from a
189835284beSWarner Losh	very old version of current.  The updating recipe has changed
190835284beSWarner Losh	as of this date.
191835284beSWarner Losh
192fa9401c1SWarner Losh20020112:
193fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
194fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
195fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
196fa9401c1SWarner Losh	you have local modifications, you can use
197fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
198fa9401c1SWarner Losh	/etc/pam.d.
199fa9401c1SWarner Losh
200fa9401c1SWarner Losh	Please see the following url for more details:
201fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
20247d0d01fSWarner Losh20011229:
20347d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
20447d0d01fSWarner Losh	networkfs_types, please note that it has changed
20547d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
20647d0d01fSWarner Losh
207514318a8SWarner Losh20011220:
208514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
209514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
210514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
211514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
212514318a8SWarner Losh	version have now been merged back into the base system's
213514318a8SWarner Losh	version now.  The only user-visible change resulting from this
214514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
215514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
216514318a8SWarner Losh	as well.  (There has never been rc file support for
217514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
218514318a8SWarner Losh	reverted by the time the changes are MFCed.)
219514318a8SWarner Losh
220514318a8SWarner Losh20011215:
221514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
222514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
223514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
224514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
225514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
226514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
227514318a8SWarner Losh	will need to be customized then for `odd' densities using
228514318a8SWarner Losh	fdcontrol(8).
229514318a8SWarner Losh
2302d22e2bfSWarner Losh20011209:
2312d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
2322d22e2bfSWarner Losh	and truss(1) now works again.
2332d22e2bfSWarner Losh
2349e0428e2SWarner Losh20011207:
2359e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
2369e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
2379e0428e2SWarner Losh	see
2389e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
2399e0428e2SWarner Losh	for details.
2409e0428e2SWarner Losh
2419bab8c59SWarner Losh20011204:
2429bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
2439bab8c59SWarner Losh	kernel and burncd to be in sync.
2449bab8c59SWarner Losh
245e57d8b01SWarner Losh20011203:
246e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
247e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
248e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
249e57d8b01SWarner Losh	not there already.
250e57d8b01SWarner Losh
251e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
252e57d8b01SWarner Losh	until the issue has been resolved.
253e57d8b01SWarner Losh
254b001d36fSJacques Vidrine20011202:
255b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
256b001d36fSJacques Vidrine	patched.
257b001d36fSJacques Vidrine
2584b676ec1SWarner Losh20011126:
2594b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
2605ebbf43eSWarner Losh	after this date.  You need to do this only once.
2614b676ec1SWarner Losh
262d961e462SWarner Losh20011103:
263d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
264d961e462SWarner Losh	edges may be left, but for the most part things should be
2654b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
266d961e462SWarner Losh
267d961e462SWarner Losh20011030:
268d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
269d961e462SWarner Losh	choppy waves in the upgrade process.
270d961e462SWarner Losh
2711fe003b6SWarner Losh20011030:
272a4b6fda0SWarner Losh	The asr driver problem has been resolved.
2731fe003b6SWarner Losh
2741fe003b6SWarner Losh20011027:
2751fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
2761fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
2771fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
2781fe003b6SWarner Losh	try to use from this date forward.
2791fe003b6SWarner Losh
2801fe003b6SWarner Losh20011025:
2811fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
2821fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
2831fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
2841fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
2851fe003b6SWarner Losh	TARGET_ARCH=i386.
2861fe003b6SWarner Losh
287d05f9643SWarner Losh20011001:
288d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
289d05f9643SWarner Losh	You must recompile both the kernel and userland applications
290d05f9643SWarner Losh	at the same time.
291d05f9643SWarner Losh
29258970f85SWarner Losh20010929:
29358970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
29458970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
29558970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
29658970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
2979d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
29858970f85SWarner Losh
29958970f85SWarner Losh20010927:
30058970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
30158970f85SWarner Losh	To disable ACPI you can add
30266ff0e67SMax Khon		hint.acpi.0.disabled="1"
30358970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
30458970f85SWarner Losh	loader "ok" prompt).
30558970f85SWarner Losh
30658970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
30758970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
30858970f85SWarner Losh	file and not list acpi in that list.
309378f4486SAlfred Perlstein
3105119d237SWarner Losh20010924:
3115119d237SWarner Losh	The buildworld has been fixed.  You may need to install
3125119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
3138b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
3148b039fffSWarner Losh	get them installed on every installworld, or execute the
3158b039fffSWarner Losh	following to get them installed only once:
3168b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
31758970f85SWarner Losh		make all install
3188b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
3195119d237SWarner Losh
3203c293725SWarner Losh20010919:
3213c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
3223c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
3233c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
324772730c7SWarner Losh	workaround is to add
3253c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
3263c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
3273c293725SWarner Losh	can be removed afterwards.
3283c293725SWarner Losh
3293c293725SWarner Losh	A proper fix to the buildworld target is needed.
3303c293725SWarner Losh
3313c293725SWarner Losh20010918:
3323c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
3333c293725SWarner Losh	NFS may be unstable after this date.
3343c293725SWarner Losh
3353c293725SWarner Losh20010912:
3363c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
3373c293725SWarner Losh	the kernel.  While a few problems were introduced in the
3383c293725SWarner Losh	initial commit, most of the major ones have been found and
3393c293725SWarner Losh	corrected.
3403c293725SWarner Losh
3413c293725SWarner Losh20010901:
3423c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
3433c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
3443c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
3453c293725SWarner Losh	have been rectified around this date.
3463c293725SWarner Losh
34798b17b95SWarner Losh20010823:
34898b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
34998b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
35098b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
35198b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
35298b17b95SWarner Losh 	sure that user or group bind has read (and not write)
35398b17b95SWarner Losh 	permission for your name server configuration and that it
35498b17b95SWarner Losh 	has read and write permission for your slave zone files and
35598b17b95SWarner Losh 	directory.
35698b17b95SWarner Losh
35798b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
35898b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
35998b17b95SWarner Losh
36098b17b95SWarner Losh 		named_flags=
36198b17b95SWarner Losh
3627b9786edSMark Murray20010709:
3637b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
3647b9786edSMark Murray	the ability of the shared library major number to handle.
3657b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
3667b9786edSMark Murray	solution is to rebuild those ports.
3677b9786edSMark Murray
3681d28950eSWarner Losh20010628:
3691d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
3701d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
3711d28950eSWarner Losh
372e72fd46aSWarner Losh20010625:
37398b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
37498b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
37598b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
37698b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
37798b17b95SWarner Losh	IRQ configuration needs more safety belts.
37816de1a07SWarner Losh
3790d415dffSWarner Losh20010617:
380e72fd46aSWarner Losh	Softupdates problems have been corrected.
3810d415dffSWarner Losh
3820d415dffSWarner Losh20010614:
3830d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
3840d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
3850d415dffSWarner Losh	kernel building methods.
3860d415dffSWarner Losh
3878b9959adSWarner Losh20010613:
3888b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
3898b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
390e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
391e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
3928b9959adSWarner Losh
393e72fd46aSWarner Losh20010613:
3948b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
395e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
396e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
3978b9959adSWarner Losh
3980d415dffSWarner Losh20010612:
3990d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
4000d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
4010d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
4020d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
4030d415dffSWarner Losh	until this bug is fixed.
4040d415dffSWarner Losh
405e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
406e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
407e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
408e72fd46aSWarner Losh
4090d415dffSWarner Losh20010610:
4100d415dffSWarner Losh	Locale names have changed to match other systems better.
4110d415dffSWarner Losh
4126ccdb5e4SWarner Losh20010604:
4136ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
4146ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
4156ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
4163590182eSWarner Losh	Interrupt storms look a lot like a hang.
4173590182eSWarner Losh
4183590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
4193590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
4203590182eSWarner Losh	it is).
4213590182eSWarner Losh
4223590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
4233590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
4243590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
4253590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
4266ccdb5e4SWarner Losh
4270bc62786SWarner Losh20010530:
4280bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
4290bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
4300bc62786SWarner Losh	a limited time.  If you see
4310bc62786SWarner Losh
4320bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
4330bc62786SWarner Losh
4340bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
4350bc62786SWarner Losh	COPY=-C.
4360bc62786SWarner Losh
43768a38c6cSWarner Losh20010525:
438b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
439c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
440c4f4a728SWarner Losh	definitely is in bad shape.
44168a38c6cSWarner Losh
442ed0f29caSWarner Losh20010521:
443f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
444ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
445ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
446ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
447ed0f29caSWarner Losh	is
448ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
449ed0f29caSWarner Losh
45080c16af9SWarner Losh20010520:
45168a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
45280c16af9SWarner Losh
45380c16af9SWarner Losh20010519:
45480c16af9SWarner Losh	pccard has had much reorganizational work done to it over
45580c16af9SWarner Losh	the past few days.  Everything should still work, but if
45680c16af9SWarner Losh	not, please contact imp@freebsd.org.
45780c16af9SWarner Losh
458a45f2d05SWarner Losh20010517:
459a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
460a45f2d05SWarner Losh	userland at the same time.
461a45f2d05SWarner Losh
462a45f2d05SWarner Losh20010517:
463a45f2d05SWarner Losh	New ncurses imported.
464a45f2d05SWarner Losh
4652988afcaSWarner Losh20010512:
4662988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
4672988afcaSWarner Losh	will be the only way to go starting July 1.
4682988afcaSWarner Losh
4691a33dba7SWarner Losh20010504:
4701a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
4711a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
4721a33dba7SWarner Losh
47309946a51SWarner Losh20010502:
47409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
47509946a51SWarner Losh
47609946a51SWarner Losh20010501:
47709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
47809946a51SWarner Losh
47909946a51SWarner Losh20010430:
480a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
48109946a51SWarner Losh	go back in the water.
48209946a51SWarner Losh
48309946a51SWarner Losh20010429:
48409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
48509946a51SWarner Losh	this date, but before the correction date.
48609946a51SWarner Losh
48791dd3b53SWarner Losh20010423:
48891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
48991dd3b53SWarner Losh
49091dd3b53SWarner Losh20010411:
49191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
49291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
49391dd3b53SWarner Losh	Update only if you understand that you must not use the old
49491dd3b53SWarner Losh	fsck with the new kernel ever.
49591dd3b53SWarner Losh
496933b3269SWarner Losh20010330:
497933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
498c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
499933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
500933b3269SWarner Losh
501933b3269SWarner Losh20010319:
502933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
503933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
504933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
505f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
50609946a51SWarner Losh
50709946a51SWarner Losh20010315:
50809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
50909946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
51009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
511933b3269SWarner Losh
512933b3269SWarner Losh20010312:
513933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
514933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
515933b3269SWarner Losh
516933b3269SWarner Losh20010312:
517933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
518933b3269SWarner Losh	instead of ad-hoc.
519933b3269SWarner Losh
520933b3269SWarner Losh20010310:
521f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
522933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
523933b3269SWarner Losh	ssh might not work if you don't.
524933b3269SWarner Losh
52562353691SWarner Losh20010303:
52662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
52762353691SWarner Losh	which means that you must include the miibus in your kernel if
52862353691SWarner Losh	you use the ed driver.
52962353691SWarner Losh
530d325cf65SWarner Losh20010220:
531d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
532d325cf65SWarner Losh	safe to go back into the water.
533d325cf65SWarner Losh
534024daae6SWarner Losh20010211:
535024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
536024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
537024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
538024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
539024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
540024daae6SWarner Losh
541024daae6SWarner Losh	To get to the new system, you'll need to use the following
542024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
543024daae6SWarner Losh	don't have to move this to the updating section.
544024daae6SWarner Losh
545024daae6SWarner Losh	To get around the installworld problem, do:
546024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
547024daae6SWarner Losh		# make install
548024daae6SWarner Losh		# cd /usr/src
549024daae6SWarner Losh		# make installworld
550024daae6SWarner Losh	If that doesn't work, then try:
551024daae6SWarner Losh		# make -k installworld
552024daae6SWarner Losh		# make installworld
553024daae6SWarner Losh
554024daae6SWarner Losh20010207:
555024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
556024daae6SWarner Losh	do not include devfs in your kernel as problems result.
557024daae6SWarner Losh
558024daae6SWarner Losh20010205:
5597595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
560024daae6SWarner Losh	Remove them from your config.
561024daae6SWarner Losh
5621e159248SWarner Losh20010122:
5631e159248SWarner Losh	****************************** WARNING ******************************
5641e159248SWarner Losh			buildkernel has been changed slightly
5651e159248SWarner Losh	****************************** WARNING ******************************
5661e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
5671e159248SWarner Losh	should update your scripts and make.conf accordingly.
5681e159248SWarner Losh
5691e159248SWarner Losh20010119:
5701e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
5711e159248SWarner Losh	This requires a new config to build correctly.
5721e159248SWarner Losh
573aac7dfeaSWarner Losh20010116:
574aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
575aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
576aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
577aac7dfeaSWarner Losh
578aac7dfeaSWarner Losh20010110:
579aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
580aac7dfeaSWarner Losh
581aac7dfeaSWarner Losh20010102:
582aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
583aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
584aac7dfeaSWarner Losh
58563c90c9eSWarner Losh20010101:
58663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
58763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
5885fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
58963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
59063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
59163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
59263c90c9eSWarner Losh	might have been ignored by the -k option.
59363c90c9eSWarner Losh
5945fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
5955fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
5965fd2a895SWarner Losh	of this working.
5975fd2a895SWarner Losh
598aac7dfeaSWarner Losh20001228:
599aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
600aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
601aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
602aac7dfeaSWarner Losh
603de2bcc63SWarner Losh20001218:
604de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
605de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
606de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
607de2bcc63SWarner Losh	cards will not be recognized without it.
608de2bcc63SWarner Losh
609960773f7SWarner Losh20001205:
610960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
611960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
612960773f7SWarner Losh	adding the following in pam.conf:
613960773f7SWarner Losh
614960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
615960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
616960773f7SWarner Losh	sshd    session required        pam_permit.so
617960773f7SWarner Losh
6180acc635eSWarner Losh20001031:
6190acc635eSWarner Losh	cvs updated to 1.11.
6200acc635eSWarner Losh
6210acc635eSWarner Losh20001020:
6220acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
6230acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
6240acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
6250acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
6260acc635eSWarner Losh	workaround.
6270acc635eSWarner Losh
6280acc635eSWarner Losh20001010:
6290acc635eSWarner Losh	****************************** WARNING ******************************
6300acc635eSWarner Losh				Sendmail has been updated.
6310acc635eSWarner Losh	****************************** WARNING ******************************
6320acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
6330acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
6340acc635eSWarner Losh	  is set.
6350acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
6360acc635eSWarner Losh	  commands.
6370acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
6380acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
6390acc635eSWarner Losh	  in /usr/share/sendmail/cf.
6400acc635eSWarner Losh	o sendmail.cw changed to local-host-names
6410acc635eSWarner Losh
6420acc635eSWarner Losh	More details can be found at
6430acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
6440acc635eSWarner Losh
6456e98a146SWarner Losh20001009:
6466e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
6476e98a146SWarner Losh	your entire ports tree, or you will have problems.
6486e98a146SWarner Losh
6496e98a146SWarner Losh20001006:
650685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
6516e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
6526e98a146SWarner Losh	/usr/bin/miniperl.
6536e98a146SWarner Losh
654073113a4SWarner Losh20001005:
655073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
656685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
657073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
658073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
659073113a4SWarner Losh	tree for anything to work.
660073113a4SWarner Losh
6610acc635eSWarner Losh20000928:
6620acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
6630acc635eSWarner Losh
664be3885b3SWarner Losh20000916:
665be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
666be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
667be3885b3SWarner Losh	same time as your kernel.
668be3885b3SWarner Losh
66976ec9675SWarner Losh20000914:
67076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
67176ec9675SWarner Losh	include the device will cause suspended laptops losing time
67276ec9675SWarner Losh	when they resume.  Include
67376ec9675SWarner Losh		device		pmtimer
67476ec9675SWarner Losh	in your config file and
67501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
67676ec9675SWarner Losh	to your /boot/device.hints file.
67776ec9675SWarner Losh
678f4865386SMark Murray20000911:
679f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
680f4865386SMark Murray	rather than an option. The supplied kernel config files have
681f4865386SMark Murray	been updated. You will need to do something similar in your
682f4865386SMark Murray	own kernel config file.
683f4865386SMark Murray	Remove:
684f4865386SMark Murray		options		RANDOMDEV
685f4865386SMark Murray	Add:
686f4865386SMark Murray		device		random
687f4865386SMark Murray	If you prefer to load the loadable module, you need to do
688f4865386SMark Murray	nothing.
689f4865386SMark Murray
690d594498fSWarner Losh20000909:
691d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
692d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
693d594498fSWarner Losh	reflect this if you load this module at boot time.
694d594498fSWarner Losh	The line should read:
695d594498fSWarner Losh		random_load="YES"
696d594498fSWarner Losh
6970deb7ddcSWarner Losh20000907:
6980deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
69916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
70016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
70116eb772dSWarner Losh	sure you don't have model loading problems which might at
70216eb772dSWarner Losh	first blush appear related to SMP.
70352bf24e7SWarner Losh
7045a01880bSWarner Losh20000906:
7055a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
7065a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
7075a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
7085a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
7095a01880bSWarner Losh	don't have one, and you have host.conf.
7105a01880bSWarner Losh
7112b41163cSWarner Losh20000905:
71238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
71338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
71438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
71538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
71638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
71738d6ecd2SWarner Losh
71838d6ecd2SWarner Losh20000905:
7198aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
7208aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
7218aab4bc7SWarner Losh	is /boot/kernel.
7228aab4bc7SWarner Losh
7238aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
72438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
72538d6ecd2SWarner Losh	installkernel/installworld dance.
7262b41163cSWarner Losh
727d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
728d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
729d594498fSWarner Losh	modules in that directory instead of finding them in the correct
730d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
731d594498fSWarner Losh	is that the linux module crashes your machine after the update.
732d594498fSWarner Losh
733d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
734d594498fSWarner Losh		mv /modules.old /boot/kernel.old
735d594498fSWarner Losh		chflags noschg /kernel.old
736d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
737d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
738d594498fSWarner Losh	fi
739d594498fSWarner Losh
740c22a309cSWarner Losh20000904:
741c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
742c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
743c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
744c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
745c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
746c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
747c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
748c22a309cSWarner Losh	is not likely to be generated.
749c22a309cSWarner Losh
750fdb9f54dSWarner Losh20000825:
751fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
7529c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
7539c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
7549c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
7559c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
7569c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
7579c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
7589c1a7444SWarner Losh	kernel.
7599c1a7444SWarner Losh
7609c1a7444SWarner Losh20000821:
7619c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
7629c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
7639c1a7444SWarner Losh	/boot/loader.conf.
764fdb9f54dSWarner Losh
7658f250aa7SWarner Losh20000812:
7665da0d091SWarner Losh	suidperl is now always built and installed on the system, but
7675da0d091SWarner Losh	with permissions of 511.  If you have applications that use
7685da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
7695da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
7705da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
7715da0d091SWarner Losh	will fix this until the next build.
7725da0d091SWarner Losh
7735da0d091SWarner Losh20000812:
7748f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
7758f250aa7SWarner Losh	visible changes that may immediately affect your configuration
7768f250aa7SWarner Losh	include:
7778f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
7788f250aa7SWarner Losh	- newaliases limited to root and trusted users
7798f250aa7SWarner Losh	- MSA port (587) turned on by default
7808f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
7818f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
7828f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
7838f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
7848f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
7858f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
7868f250aa7SWarner Losh
78771c38472SWarner Losh20000810:
78871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
78971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
79071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
79171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
79271c38472SWarner Losh	specific use for it.
79371c38472SWarner Losh
79471c38472SWarner Losh20000729:
79571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
79671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
79771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
79871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
79971c38472SWarner Losh		# Enable network daemons for user convenience.
80071c38472SWarner Losh		inetd_enable="YES"
80171c38472SWarner Losh		portmap_enable="YES"
80271c38472SWarner Losh		sendmail_enable="YES"
80371c38472SWarner Losh
80471c38472SWarner Losh20000728:
80571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
80671c38472SWarner Losh	will need to change that to nullfs_load="YES".
80771c38472SWarner Losh
8081dece4a9SWarner Losh20000728:
8091dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
8101dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
8111dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
8121dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
8131dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
8141dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
8151dece4a9SWarner Losh	to /MYKERNEL.
8161dece4a9SWarner Losh
817409e887cSWarner Losh20000711:
818409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
819409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
820409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
821409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
822409e887cSWarner Losh	for details on potential problems that you might have and how
823409e887cSWarner Losh	to get around them.
824409e887cSWarner Losh
825409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
826409e887cSWarner Losh	clauses above, you needn't worry.
827409e887cSWarner Losh
828409e887cSWarner Losh20000711:
829409e887cSWarner Losh	/etc/security has been updated to print the inode number of
830409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
831409e887cSWarner Losh	in the number of changed programs the first time when you run
832409e887cSWarner Losh	mergemaster to get a new /etc/security.
833409e887cSWarner Losh
834673d13f2SWarner Losh20000710:
835673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
836673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
837673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
838673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
839673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
840673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
841673d13f2SWarner Losh	errors. (see below, 20000624).
842673d13f2SWarner Losh
843bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
8441dece4a9SWarner Losh
845673d13f2SWarner Losh20000709:
846c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
847c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
848c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
849673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
850673d13f2SWarner Losh
851e98e26cdSWarner Losh20000706:
852e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
853e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
854e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
855f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
856e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
8572c021c6cSMark Ovens	interim if needed.
858e98e26cdSWarner Losh
859e98e26cdSWarner Losh20000705:
860e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
861e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
862e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
863e98e26cdSWarner Losh	details.
864e98e26cdSWarner Losh
865c373950eSWarner Losh20000704:
8662f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
8672f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
8682f961bc8SWarner Losh
8692f961bc8SWarner Losh20000704:
870c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
871c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
872c373950eSWarner Losh	rc.d scripts that haven't been updated.
873c373950eSWarner Losh
87427dc3a2bSWarner Losh20000630:
87527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
87627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
87727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
87827dc3a2bSWarner Losh
879b8c215acSWarner Losh20000625:
880b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
88127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
88227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
88327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
88427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
88527dc3a2bSWarner Losh	were required.  You should check with the latest collections
88627dc3a2bSWarner Losh	to make sure that these haven't changed.
887b8c215acSWarner Losh
8887b990719SWarner Losh20000624:
8897b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
8907b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
8917b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
8921a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
8937b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
8947b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
8957b990719SWarner Losh	date to the completion of the work.
8967b990719SWarner Losh
89727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
89827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
89927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
90027dc3a2bSWarner Losh	recreate the random and urandom devices.
90127dc3a2bSWarner Losh
90281e54c50SWarner Losh20000622:
90381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
90481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
90581e54c50SWarner Losh	that used to be required when updating.
90681e54c50SWarner Losh
90739943833SWarner Losh20000621:
9082c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
9092a2f33fbSDaniel Baker	the config file update procedure.
9102a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
911c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
912a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
91339943833SWarner Losh
914290f9ad8SWarner Losh20000620:
915290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
916290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
917290f9ad8SWarner Losh	that workaround will no longer be required.
918290f9ad8SWarner Losh
91990fb6346SWarner Losh20000615:
92090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
92190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
92290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
92390fb6346SWarner Losh	devices.
92490fb6346SWarner Losh
925f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
926f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
927f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
928f75f65bbSWarner Losh	may work).
929f75f65bbSWarner Losh
930ba26da8eSWarner Losh20000612:
931ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
932290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
933c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
934290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
935f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
936f54a3542SWarner Losh	NEWCARD for examples of the new format.
937290f9ad8SWarner Losh
9389698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
9399698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
9409698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
9419698f2c0SWarner Losh	in it.
942bbcc5149SWarner Losh
943d65850ebSWarner Losh20000522:
944ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
945d65850ebSWarner Losh	building a kernel after this point is advised that they need
946d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
947d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
948d65850ebSWarner Losh
949d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
950d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
951d9583a00SWarner Losh	is recommended that you don't set this option until the problem
952d9583a00SWarner Losh	is resolved.
953d9583a00SWarner Losh
9548039cedeSWarner Losh20000513:
9558039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
9568039cedeSWarner Losh
957d65850ebSWarner Losh20000510:
9588039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
9598039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
9608039cedeSWarner Losh	is requires for the boot blocks to build properly.
9618039cedeSWarner Losh
9628039cedeSWarner Losh20000503:
9638039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
9648039cedeSWarner Losh	is now available.
9658039cedeSWarner Losh
966d65850ebSWarner Losh20000502:
967d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
968d65850ebSWarner Losh	connected to the kernel building instead.
969d65850ebSWarner Losh
970be149406SNik Clayton20000427:
9718039cedeSWarner Losh	You may need to build gperf
9728039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
9738039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
9748039cedeSWarner Losh	an option only in -current.
9758039cedeSWarner Losh
9762b8dd5f4SWarner Losh20000417:
9772b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
978f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
9792b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
9802b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
9812c021c6cSMark Ovens	before you reboot, you'll need to issue:
9822b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
9832b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
9842b8dd5f4SWarner Losh
9858d9f1945SWarner Losh20000320:
9862b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
9872b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
9882b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
989ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
9902b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
9918d9f1945SWarner Losh
992f8ab1dd6SWarner Losh20000319:
993f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
994f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
995f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
996f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
997f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
998f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
999f8ab1dd6SWarner Losh
100019cada77SWarner Losh20000318:
1001f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
100219cada77SWarner Losh	Large kernel changes are being committed and are in the
100319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
100419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
100519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
100619cada77SWarner Losh	that you are loading are up to date.
1007ba228352SWarner Losh
100819cada77SWarner Losh20000315:
10096d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
10106d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
10116d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
10126d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
10136d23c382SWarner Losh	boot.
10146d23c382SWarner Losh
10156d23c382SWarner Losh20000315:
101619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
101719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
101857199806SWarner Losh
1019dc0dbf5cSWarner LoshCOMMON ITEMS:
1020dc0dbf5cSWarner Losh
1021a24eff53SWarner Losh	General Notes
1022a24eff53SWarner Losh	-------------
1023a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1024a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1025a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1026a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1027a24eff53SWarner Losh	or several minor releases, or when several months have passed
1028a24eff53SWarner Losh	on the -current branch).
1029a24eff53SWarner Losh
10305780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
10315780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
10325780f3baSWarner Losh	environment when searching for values for global variables.
10335780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
10345780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
10355780f3baSWarner Losh	page for more details.
10365780f3baSWarner Losh
1037dc0dbf5cSWarner Losh	To build a kernel
1038dc0dbf5cSWarner Losh	-----------------
1039ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1040f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1041ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
10421e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
10431e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
1044dc0dbf5cSWarner Losh
1045ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1046ba01eb20SWarner Losh	--------------------------------------------------------------
1047ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
104847d0d01fSWarner Losh	config KERNEL_NAME_HERE
1049ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1050ba01eb20SWarner Losh	make depend
1051ba01eb20SWarner Losh	make
1052ba01eb20SWarner Losh	make install
1053ba01eb20SWarner Losh
1054ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1055ba01eb20SWarner Losh
1056ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1057ba01eb20SWarner Losh	-----------------------------------------------------------
105863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
105963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
106063cb445eSWarner Losh
1061f643de42SWarner Losh	<make sure you have good level 0 dumps>
106263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
106363cb445eSWarner Losh	make buildworld
106463cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
106563cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
106663cb445eSWarner Losh							[1]
106763cb445eSWarner Losh	<reboot in single user>				[3]
106863cb445eSWarner Losh	mergemaster -p					[5]
106963cb445eSWarner Losh	make installworld
107063cb445eSWarner Losh	mergemaster					[4]
107163cb445eSWarner Losh	<reboot>
107263cb445eSWarner Losh
1073759f0aefSWarner Losh
10741dece4a9SWarner Losh	To upgrade from 4.x-stable to current
1075ba26da8eSWarner Losh	-------------------------------------
10765c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
10775c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
10785c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
10795c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1080f643de42SWarner Losh	# to back out of problems with this proceedure.  If /tmp is on
1081f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1082f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1083f643de42SWarner Losh	# space on /.
1084f643de42SWarner Losh
1085f643de42SWarner Losh	<make sure you have good level 0 dumps>
1086fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
108721c075eaSWarner Losh	make buildworld					[9]
1088c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1089d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1090be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1091fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1092fc8c157fSWarner Losh							[1]
1093fc8c157fSWarner Losh	<reboot in single user>				[3]
1094835284beSWarner Losh	mergemaster -p					[5]
1095f8a4c901SWarner Losh	rm -rf /usr/include/g++
1096ba26da8eSWarner Losh	make installworld
1097a6cd4f9dSWarner Losh	mergemaster					[4]
1098ba26da8eSWarner Losh	<reboot>
1099ba26da8eSWarner Losh
1100fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1101fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1102fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1103fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1104fdb9f54dSWarner Losh	the UPDATING entries.
1105ba26da8eSWarner Losh
11061dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
11071dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
11081dece4a9SWarner Losh	your sources that you have read and understood all the recent
11091dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
11101dece4a9SWarner Losh	much fewer pitfalls.
11111dece4a9SWarner Losh
1112134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1113134d2e86SWarner Losh	should disable them at this point so they don't crash your
1114134d2e86SWarner Losh	system on reboot.
1115134d2e86SWarner Losh
11169c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
11179c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
11189c1a7444SWarner Losh	configuration.
11199c1a7444SWarner Losh
1120ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1121ee6e1fc3SWarner Losh		fsck -p
1122ee6e1fc3SWarner Losh		mount -u /
1123ee6e1fc3SWarner Losh		mount -a
1124ee6e1fc3SWarner Losh		cd /usr/src
112547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1126f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1127f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1128b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1129b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1130b705ae10SWarner Losh	be ignored while you proceed to the next step.
1131ee6e1fc3SWarner Losh
1132a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1133a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1134a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1135a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1136a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1137a6cd4f9dSWarner Losh	for potential gotchas.
1138a6cd4f9dSWarner Losh
1139835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1140835284beSWarner Losh	you may need to do this if you get unknown user in the following
1141835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1142835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1143835284beSWarner Losh	install) after the buildworld before this step if you last updated
1144835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1145835284beSWarner Losh
1146bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1147bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1148bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1149bd79cf40SWarner Losh		ok unload
1150bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1151bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1152bd79cf40SWarner Losh	described here.
1153fc8c157fSWarner Losh
1154fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1155fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1156fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1157fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1158fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1159fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1160fc8c157fSWarner Losh
1161c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1162c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1163c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1164c74fe6afSWarner Losh	that is hard to boot to recover.
1165c74fe6afSWarner Losh
116621c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
116721c075eaSWarner Losh	cvs prune empty directories.
1168dc0dbf5cSWarner LoshFORMAT:
1169dc0dbf5cSWarner Losh
1170f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
11711fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1172f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1173f8ab1dd6SWarner Loshprevious releases if your system is older than this.
11741fc1a0dcSWarner Losh
1175e72fd46aSWarner LoshCopyright information:
1176e72fd46aSWarner Losh
11779698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1178e72fd46aSWarner Losh
1179772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1180772730c7SWarner Loshmodification, in full or in part, in any form or format of this
11819698f2c0SWarner Loshdocument are permitted without further permission from the author.
1182e72fd46aSWarner Losh
1183e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1184e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1185e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1186e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1187e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1188e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1189e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1190e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1191e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1192e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1193e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1194e72fd46aSWarner Losh
1195e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1196e72fd46aSWarner Loshauthor a beer.
1197e72fd46aSWarner Losh
119822306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1199772730c7SWarner Loshthis document.
1200772730c7SWarner Losh
120197d92980SPeter Wemm$FreeBSD$
1202