xref: /freebsd/UPDATING (revision 52b4744563d747383c92af2002621d7ad3e75c3b)
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
2052b47445SMark Murray20030505:
2152b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
2252b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
2352b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
2452b47445SMark Murray
25a26df538SWarner Losh20030502:
26a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
27a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
28a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
29a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
30a26df538SWarner Losh
314b065e2cSDoug Barton20030501:
324b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
334b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
344b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
354b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
364b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
374b065e2cSDoug Barton	utilizes these old scripts has also been removed.
384b065e2cSDoug Barton
3981cda3d9SWarner Losh20030423:
4081cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
4181cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
4281cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
4381cda3d9SWarner Losh	have until then to upgrade your kernel before updating
4481cda3d9SWarner Losh	userland.  In general, you should have a userland and
4581cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
4681cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
4781cda3d9SWarner Losh	allowances are made.
4881cda3d9SWarner Losh
4947a657d1SRuslan Ermilov20030329:
5047a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
5147a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
5247a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
5347a657d1SRuslan Ermilov
5447a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
5547a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
5647a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
5747a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
5847a657d1SRuslan Ermilov
5947a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
6047a657d1SRuslan Ermilov	    make cleandir && make obj && \
6147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
6247a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
6347a657d1SRuslan Ermilov
645d2af00cSGregory Neil Shapiro20030208:
655d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
665d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
675d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
685d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
695d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
705d2af00cSGregory Neil Shapiro
715d2af00cSGregory Neil Shapiro20030128:
729db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
73ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
749db58771SPoul-Henning Kamp	be removed when convenient.
759db58771SPoul-Henning Kamp
768d9b3f57SJake Burkholder20030126:
778d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
788d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
798d9b3f57SJake Burkholder
801c5efda5SJeff Roberson20030125:
811c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
821c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
83ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
841c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
851c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
861c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
871c5efda5SJeff Roberson
889d1d64f5SWarner Losh20030115:
899d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
909d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
919d1d64f5SWarner Losh	properly.
929d1d64f5SWarner Losh
93c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
94c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
95c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
96c9fdb80aSWarner Losh	with NetBSD.
97c9fdb80aSWarner Losh
98161dc364SAlexander Kabaev20021222:
99161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
100161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
101161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
102161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
103161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
104161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
10584cc83efSAlexander Kabaev	rebuilt.
106161dc364SAlexander Kabaev
107fb4c8061SMartin Blapp20021216:
108fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
10989056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
110fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
1119d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
112fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
113fb4c8061SMartin Blapp
11417d47eb3SGiorgos Keramidas20021202:
11517d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
11617d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
11717d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
11817d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
11917d47eb3SGiorgos Keramidas
120a4459294SBill Fenner20021029:
121a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
122a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
123a4459294SBill Fenner	consumers in sync.
124a4459294SBill Fenner
125fc8c157fSWarner Losh20021024:
126c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
127c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
128c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
129c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
130c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
131c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
132c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
133c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
13469f7bcf3SWarner Losh
135fd9e8bdaSAndrew Gallatin20021023:
136fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
137fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
138fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
139fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
140fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
141fd9e8bdaSAndrew Gallatin
142fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
143fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
144fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
145fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
146fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
147fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
148fd9e8bdaSAndrew Gallatin
149f8a4c901SWarner Losh20020831:
150f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
151f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
152f8a4c901SWarner Losh	programs and libraries need to be recompiled.
153f8a4c901SWarner Losh
154f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
155f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
156f8a4c901SWarner Losh
157c2248fa2SJens Schweikhardt20020827:
158c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
159c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
160c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
161c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
162c2248fa2SJens Schweikhardt
1630d533e43SRuslan Ermilov20020815:
1640d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
1650d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
1660d533e43SRuslan Ermilov	again.
1670d533e43SRuslan Ermilov
16833c1de7dSRuslan Ermilov20020729:
16933c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
17033c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
17133c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
17233c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
17333c1de7dSRuslan Ermilov
1742b877facSJulian Elischer20020702:
1752b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
1762b877facSJulian Elischer	There are still some minor problems with some signals but the
1772b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
1782b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
1792b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
1802b877facSJulian Elischer
18106596d37SWarner Losh20020701:
18206596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
18306596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
18406596d37SWarner Losh	GNOME.
18506596d37SWarner Losh
18695ba4330SJacques Vidrine20020511:
18795ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
18895ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
18995ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
19095ba4330SJacques Vidrine	with the set-user-ID bit set.
19195ba4330SJacques Vidrine
192a81da3c9SDavid E. O'Brien20020510:
193f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
194f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
1954b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
196f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
197f50caf6fSDavid E. O'Brien
198f50caf6fSDavid E. O'Brien20020510:
199a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
200a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
201a81da3c9SDavid E. O'Brien	and then do a cvs update.
202a81da3c9SDavid E. O'Brien
203528a0ef5SJacques Vidrine20020421:
204528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
205528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
206528a0ef5SJacques Vidrine
20785aa5a2eSGregory Neil Shapiro20020404:
20885aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
20985aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
21085aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
21185aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
21285aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
21385aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
21485aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
21585aa5a2eSGregory Neil Shapiro
2168f1e4358SRuslan Ermilov20020403:
2178f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
2188f1e4358SRuslan Ermilov
2192292c02eSWarner Losh20020315:
2202292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
2212292c02eSWarner Losh
22269f7bcf3SWarner Losh20020225:
22369f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
22469f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
22569f7bcf3SWarner Losh
2268f35c493SWarner Losh20020217:
2278f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
2288f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
2298f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
2308f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
2318f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
2328f35c493SWarner Losh
233835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
234835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
235835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
236835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
237835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
238835284beSWarner Losh	and group must be merged from src/etc/group and
239835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
240835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
241835284beSWarner Losh	mergemaster before this will work if you are updating from a
242835284beSWarner Losh	very old version of current.  The updating recipe has changed
243835284beSWarner Losh	as of this date.
244835284beSWarner Losh
245fa9401c1SWarner Losh20020112:
246fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
247fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
248fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
249fa9401c1SWarner Losh	you have local modifications, you can use
250fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
251fa9401c1SWarner Losh	/etc/pam.d.
252fa9401c1SWarner Losh
253fa9401c1SWarner Losh	Please see the following url for more details:
254fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
25547d0d01fSWarner Losh20011229:
25647d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
25747d0d01fSWarner Losh	networkfs_types, please note that it has changed
25847d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
25947d0d01fSWarner Losh
260514318a8SWarner Losh20011220:
261514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
262514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
263514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
264514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
265514318a8SWarner Losh	version have now been merged back into the base system's
266514318a8SWarner Losh	version now.  The only user-visible change resulting from this
267514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
268514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
269514318a8SWarner Losh	as well.  (There has never been rc file support for
270514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
271514318a8SWarner Losh	reverted by the time the changes are MFCed.)
272514318a8SWarner Losh
273514318a8SWarner Losh20011215:
274514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
275514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
276514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
277514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
278514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
279514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
280514318a8SWarner Losh	will need to be customized then for `odd' densities using
281514318a8SWarner Losh	fdcontrol(8).
282514318a8SWarner Losh
2832d22e2bfSWarner Losh20011209:
2842d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
2852d22e2bfSWarner Losh	and truss(1) now works again.
2862d22e2bfSWarner Losh
2879e0428e2SWarner Losh20011207:
2889e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
2899e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
2909e0428e2SWarner Losh	see
2919e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
2929e0428e2SWarner Losh	for details.
2939e0428e2SWarner Losh
2949bab8c59SWarner Losh20011204:
2959bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
2969bab8c59SWarner Losh	kernel and burncd to be in sync.
2979bab8c59SWarner Losh
298e57d8b01SWarner Losh20011203:
299e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
300e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
301e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
302e57d8b01SWarner Losh	not there already.
303e57d8b01SWarner Losh
304e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
305e57d8b01SWarner Losh	until the issue has been resolved.
306e57d8b01SWarner Losh
307b001d36fSJacques Vidrine20011202:
308b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
309b001d36fSJacques Vidrine	patched.
310b001d36fSJacques Vidrine
3114b676ec1SWarner Losh20011126:
3124b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
3135ebbf43eSWarner Losh	after this date.  You need to do this only once.
3144b676ec1SWarner Losh
315d961e462SWarner Losh20011103:
316d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
317d961e462SWarner Losh	edges may be left, but for the most part things should be
3184b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
319d961e462SWarner Losh
320d961e462SWarner Losh20011030:
321d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
322d961e462SWarner Losh	choppy waves in the upgrade process.
323d961e462SWarner Losh
3241fe003b6SWarner Losh20011030:
325a4b6fda0SWarner Losh	The asr driver problem has been resolved.
3261fe003b6SWarner Losh
3271fe003b6SWarner Losh20011027:
3281fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
3291fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
3301fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
3311fe003b6SWarner Losh	try to use from this date forward.
3321fe003b6SWarner Losh
3331fe003b6SWarner Losh20011025:
3341fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
3351fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
3361fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
3371fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
3381fe003b6SWarner Losh	TARGET_ARCH=i386.
3391fe003b6SWarner Losh
340d05f9643SWarner Losh20011001:
341d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
342d05f9643SWarner Losh	You must recompile both the kernel and userland applications
343d05f9643SWarner Losh	at the same time.
344d05f9643SWarner Losh
34558970f85SWarner Losh20010929:
34658970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
34758970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
34858970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
34958970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
3509d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
35158970f85SWarner Losh
35258970f85SWarner Losh20010927:
35358970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
35458970f85SWarner Losh	To disable ACPI you can add
35566ff0e67SMax Khon		hint.acpi.0.disabled="1"
35658970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
35758970f85SWarner Losh	loader "ok" prompt).
35858970f85SWarner Losh
35958970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
36058970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
36158970f85SWarner Losh	file and not list acpi in that list.
362378f4486SAlfred Perlstein
3635119d237SWarner Losh20010924:
3645119d237SWarner Losh	The buildworld has been fixed.  You may need to install
3655119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
3668b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
3678b039fffSWarner Losh	get them installed on every installworld, or execute the
3688b039fffSWarner Losh	following to get them installed only once:
3698b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
37058970f85SWarner Losh		make all install
3718b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
3725119d237SWarner Losh
3733c293725SWarner Losh20010919:
3743c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
3753c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
3763c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
377772730c7SWarner Losh	workaround is to add
3783c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
3793c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
3803c293725SWarner Losh	can be removed afterwards.
3813c293725SWarner Losh
3823c293725SWarner Losh	A proper fix to the buildworld target is needed.
3833c293725SWarner Losh
3843c293725SWarner Losh20010918:
3853c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
3863c293725SWarner Losh	NFS may be unstable after this date.
3873c293725SWarner Losh
3883c293725SWarner Losh20010912:
3893c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
3903c293725SWarner Losh	the kernel.  While a few problems were introduced in the
3913c293725SWarner Losh	initial commit, most of the major ones have been found and
3923c293725SWarner Losh	corrected.
3933c293725SWarner Losh
3943c293725SWarner Losh20010901:
3953c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
3963c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
3973c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
3983c293725SWarner Losh	have been rectified around this date.
3993c293725SWarner Losh
40098b17b95SWarner Losh20010823:
40198b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
40298b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
40398b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
40498b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
40598b17b95SWarner Losh 	sure that user or group bind has read (and not write)
40698b17b95SWarner Losh 	permission for your name server configuration and that it
40798b17b95SWarner Losh 	has read and write permission for your slave zone files and
40898b17b95SWarner Losh 	directory.
40998b17b95SWarner Losh
41098b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
41198b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
41298b17b95SWarner Losh
41398b17b95SWarner Losh 		named_flags=
41498b17b95SWarner Losh
4157b9786edSMark Murray20010709:
4167b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
4177b9786edSMark Murray	the ability of the shared library major number to handle.
4187b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
4197b9786edSMark Murray	solution is to rebuild those ports.
4207b9786edSMark Murray
4211d28950eSWarner Losh20010628:
4221d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
4231d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
4241d28950eSWarner Losh
425e72fd46aSWarner Losh20010625:
42698b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
42798b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
42898b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
42998b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
43098b17b95SWarner Losh	IRQ configuration needs more safety belts.
43116de1a07SWarner Losh
4320d415dffSWarner Losh20010617:
433e72fd46aSWarner Losh	Softupdates problems have been corrected.
4340d415dffSWarner Losh
4350d415dffSWarner Losh20010614:
4360d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
4370d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
4380d415dffSWarner Losh	kernel building methods.
4390d415dffSWarner Losh
4408b9959adSWarner Losh20010613:
4418b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
4428b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
443e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
444e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
4458b9959adSWarner Losh
446e72fd46aSWarner Losh20010613:
4478b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
448e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
449e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
4508b9959adSWarner Losh
4510d415dffSWarner Losh20010612:
4520d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
4530d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
4540d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
4550d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
4560d415dffSWarner Losh	until this bug is fixed.
4570d415dffSWarner Losh
458e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
459e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
460ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
461e72fd46aSWarner Losh
4620d415dffSWarner Losh20010610:
4630d415dffSWarner Losh	Locale names have changed to match other systems better.
4640d415dffSWarner Losh
4656ccdb5e4SWarner Losh20010604:
4666ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
4676ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
4686ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
4693590182eSWarner Losh	Interrupt storms look a lot like a hang.
4703590182eSWarner Losh
4713590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
4723590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
4733590182eSWarner Losh	it is).
4743590182eSWarner Losh
4753590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
4763590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
4773590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
4783590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
4796ccdb5e4SWarner Losh
4800bc62786SWarner Losh20010530:
4810bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
4820bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
4830bc62786SWarner Losh	a limited time.  If you see
4840bc62786SWarner Losh
4850bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
4860bc62786SWarner Losh
4870bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
4880bc62786SWarner Losh	COPY=-C.
4890bc62786SWarner Losh
49068a38c6cSWarner Losh20010525:
491b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
492c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
493c4f4a728SWarner Losh	definitely is in bad shape.
49468a38c6cSWarner Losh
495ed0f29caSWarner Losh20010521:
496ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
497ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
498ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
499ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
500ed0f29caSWarner Losh	is
501ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
502ed0f29caSWarner Losh
50380c16af9SWarner Losh20010520:
50468a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
50580c16af9SWarner Losh
50680c16af9SWarner Losh20010519:
50780c16af9SWarner Losh	pccard has had much reorganizational work done to it over
50880c16af9SWarner Losh	the past few days.  Everything should still work, but if
50980c16af9SWarner Losh	not, please contact imp@freebsd.org.
51080c16af9SWarner Losh
511a45f2d05SWarner Losh20010517:
512a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
513a45f2d05SWarner Losh	userland at the same time.
514a45f2d05SWarner Losh
515a45f2d05SWarner Losh20010517:
516a45f2d05SWarner Losh	New ncurses imported.
517a45f2d05SWarner Losh
5182988afcaSWarner Losh20010512:
5192988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
5202988afcaSWarner Losh	will be the only way to go starting July 1.
5212988afcaSWarner Losh
5221a33dba7SWarner Losh20010504:
5231a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
5241a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
5251a33dba7SWarner Losh
52609946a51SWarner Losh20010502:
52709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
52809946a51SWarner Losh
52909946a51SWarner Losh20010501:
53009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
53109946a51SWarner Losh
53209946a51SWarner Losh20010430:
533a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
53409946a51SWarner Losh	go back in the water.
53509946a51SWarner Losh
53609946a51SWarner Losh20010429:
53709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
53809946a51SWarner Losh	this date, but before the correction date.
53909946a51SWarner Losh
54091dd3b53SWarner Losh20010423:
54191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
54291dd3b53SWarner Losh
54391dd3b53SWarner Losh20010411:
54491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
54591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
54691dd3b53SWarner Losh	Update only if you understand that you must not use the old
54791dd3b53SWarner Losh	fsck with the new kernel ever.
54891dd3b53SWarner Losh
549933b3269SWarner Losh20010330:
550933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
551c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
552933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
553933b3269SWarner Losh
554933b3269SWarner Losh20010319:
555933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
556933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
557933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
558f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
55909946a51SWarner Losh
56009946a51SWarner Losh20010315:
56109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
562ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
56309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
564933b3269SWarner Losh
565933b3269SWarner Losh20010312:
566933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
567933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
568933b3269SWarner Losh
569933b3269SWarner Losh20010312:
570933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
571933b3269SWarner Losh	instead of ad-hoc.
572933b3269SWarner Losh
573933b3269SWarner Losh20010310:
574f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
575933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
576933b3269SWarner Losh	ssh might not work if you don't.
577933b3269SWarner Losh
57862353691SWarner Losh20010303:
57962353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
58062353691SWarner Losh	which means that you must include the miibus in your kernel if
58162353691SWarner Losh	you use the ed driver.
58262353691SWarner Losh
583d325cf65SWarner Losh20010220:
584d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
585d325cf65SWarner Losh	safe to go back into the water.
586d325cf65SWarner Losh
587024daae6SWarner Losh20010211:
588024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
589024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
590024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
591024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
592024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
593024daae6SWarner Losh
594024daae6SWarner Losh	To get to the new system, you'll need to use the following
595024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
596024daae6SWarner Losh	don't have to move this to the updating section.
597024daae6SWarner Losh
598024daae6SWarner Losh	To get around the installworld problem, do:
599024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
600024daae6SWarner Losh		# make install
601024daae6SWarner Losh		# cd /usr/src
602024daae6SWarner Losh		# make installworld
603024daae6SWarner Losh	If that doesn't work, then try:
604024daae6SWarner Losh		# make -k installworld
605024daae6SWarner Losh		# make installworld
606024daae6SWarner Losh
607024daae6SWarner Losh20010207:
608024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
609024daae6SWarner Losh	do not include devfs in your kernel as problems result.
610024daae6SWarner Losh
611024daae6SWarner Losh20010205:
6127595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
613024daae6SWarner Losh	Remove them from your config.
614024daae6SWarner Losh
6151e159248SWarner Losh20010122:
6161e159248SWarner Losh	****************************** WARNING ******************************
6171e159248SWarner Losh			buildkernel has been changed slightly
6181e159248SWarner Losh	****************************** WARNING ******************************
6191e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
6201e159248SWarner Losh	should update your scripts and make.conf accordingly.
6211e159248SWarner Losh
6221e159248SWarner Losh20010119:
6231e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
6241e159248SWarner Losh	This requires a new config to build correctly.
6251e159248SWarner Losh
626aac7dfeaSWarner Losh20010116:
627ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
628aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
629aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
630aac7dfeaSWarner Losh
631aac7dfeaSWarner Losh20010110:
632aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
633aac7dfeaSWarner Losh
634aac7dfeaSWarner Losh20010102:
635aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
636aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
637aac7dfeaSWarner Losh
63863c90c9eSWarner Losh20010101:
63963c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
64063c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
6415fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
64263c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
64363c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
64463c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
64563c90c9eSWarner Losh	might have been ignored by the -k option.
64663c90c9eSWarner Losh
6475fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
6485fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
6495fd2a895SWarner Losh	of this working.
6505fd2a895SWarner Losh
651aac7dfeaSWarner Losh20001228:
652aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
653ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
654aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
655aac7dfeaSWarner Losh
656de2bcc63SWarner Losh20001218:
657de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
658de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
659de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
660de2bcc63SWarner Losh	cards will not be recognized without it.
661de2bcc63SWarner Losh
662960773f7SWarner Losh20001205:
663960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
664960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
665960773f7SWarner Losh	adding the following in pam.conf:
666960773f7SWarner Losh
667960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
668960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
669960773f7SWarner Losh	sshd    session required        pam_permit.so
670960773f7SWarner Losh
6710acc635eSWarner Losh20001031:
6720acc635eSWarner Losh	cvs updated to 1.11.
6730acc635eSWarner Losh
6740acc635eSWarner Losh20001020:
6750acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
6760acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
6770acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
6780acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
6790acc635eSWarner Losh	workaround.
6800acc635eSWarner Losh
6810acc635eSWarner Losh20001010:
6820acc635eSWarner Losh	****************************** WARNING ******************************
6830acc635eSWarner Losh				Sendmail has been updated.
6840acc635eSWarner Losh	****************************** WARNING ******************************
6850acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
6860acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
6870acc635eSWarner Losh	  is set.
6880acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
6890acc635eSWarner Losh	  commands.
6900acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
6910acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
6920acc635eSWarner Losh	  in /usr/share/sendmail/cf.
6930acc635eSWarner Losh	o sendmail.cw changed to local-host-names
6940acc635eSWarner Losh
6950acc635eSWarner Losh	More details can be found at
6960acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
6970acc635eSWarner Losh
6986e98a146SWarner Losh20001009:
6996e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
7006e98a146SWarner Losh	your entire ports tree, or you will have problems.
7016e98a146SWarner Losh
7026e98a146SWarner Losh20001006:
703685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
7046e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
7056e98a146SWarner Losh	/usr/bin/miniperl.
7066e98a146SWarner Losh
707073113a4SWarner Losh20001005:
708073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
709685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
710073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
711073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
712073113a4SWarner Losh	tree for anything to work.
713073113a4SWarner Losh
7140acc635eSWarner Losh20000928:
7150acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
7160acc635eSWarner Losh
717be3885b3SWarner Losh20000916:
718be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
719be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
720be3885b3SWarner Losh	same time as your kernel.
721be3885b3SWarner Losh
72276ec9675SWarner Losh20000914:
72376ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
72476ec9675SWarner Losh	include the device will cause suspended laptops losing time
72576ec9675SWarner Losh	when they resume.  Include
72676ec9675SWarner Losh		device		pmtimer
72776ec9675SWarner Losh	in your config file and
72801b9a434SWarner Losh		hint.pmtimer.0.at="isa"
72976ec9675SWarner Losh	to your /boot/device.hints file.
73076ec9675SWarner Losh
731f4865386SMark Murray20000911:
732f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
733f4865386SMark Murray	rather than an option. The supplied kernel config files have
734f4865386SMark Murray	been updated. You will need to do something similar in your
735f4865386SMark Murray	own kernel config file.
736f4865386SMark Murray	Remove:
737f4865386SMark Murray		options		RANDOMDEV
738f4865386SMark Murray	Add:
739f4865386SMark Murray		device		random
740f4865386SMark Murray	If you prefer to load the loadable module, you need to do
741f4865386SMark Murray	nothing.
742f4865386SMark Murray
743d594498fSWarner Losh20000909:
744d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
745d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
746d594498fSWarner Losh	reflect this if you load this module at boot time.
747d594498fSWarner Losh	The line should read:
748d594498fSWarner Losh		random_load="YES"
749d594498fSWarner Losh
7500deb7ddcSWarner Losh20000907:
7510deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
75216eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
75316eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
75416eb772dSWarner Losh	sure you don't have model loading problems which might at
75516eb772dSWarner Losh	first blush appear related to SMP.
75652bf24e7SWarner Losh
7575a01880bSWarner Losh20000906:
7585a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
7595a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
7605a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
7615a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
7625a01880bSWarner Losh	don't have one, and you have host.conf.
7635a01880bSWarner Losh
7642b41163cSWarner Losh20000905:
76538d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
76638d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
76738d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
76838d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
76938d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
77038d6ecd2SWarner Losh
77138d6ecd2SWarner Losh20000905:
7728aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
7738aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
7748aab4bc7SWarner Losh	is /boot/kernel.
7758aab4bc7SWarner Losh
7768aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
77738d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
77838d6ecd2SWarner Losh	installkernel/installworld dance.
7792b41163cSWarner Losh
780d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
781d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
782d594498fSWarner Losh	modules in that directory instead of finding them in the correct
783d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
784d594498fSWarner Losh	is that the linux module crashes your machine after the update.
785d594498fSWarner Losh
786d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
787d594498fSWarner Losh		mv /modules.old /boot/kernel.old
788d594498fSWarner Losh		chflags noschg /kernel.old
789d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
790d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
791d594498fSWarner Losh	fi
792d594498fSWarner Losh
793c22a309cSWarner Losh20000904:
794c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
795c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
796c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
797c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
798c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
799c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
800c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
801c22a309cSWarner Losh	is not likely to be generated.
802c22a309cSWarner Losh
803fdb9f54dSWarner Losh20000825:
804fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
8059c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
8069c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
8079c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
8089c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
8099c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
8109c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
8119c1a7444SWarner Losh	kernel.
8129c1a7444SWarner Losh
8139c1a7444SWarner Losh20000821:
8149c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
8159c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
8169c1a7444SWarner Losh	/boot/loader.conf.
817fdb9f54dSWarner Losh
8188f250aa7SWarner Losh20000812:
8195da0d091SWarner Losh	suidperl is now always built and installed on the system, but
8205da0d091SWarner Losh	with permissions of 511.  If you have applications that use
8215da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
8225da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
8235da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
8245da0d091SWarner Losh	will fix this until the next build.
8255da0d091SWarner Losh
8265da0d091SWarner Losh20000812:
8278f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
8288f250aa7SWarner Losh	visible changes that may immediately affect your configuration
8298f250aa7SWarner Losh	include:
8308f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
8318f250aa7SWarner Losh	- newaliases limited to root and trusted users
8328f250aa7SWarner Losh	- MSA port (587) turned on by default
8338f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
8348f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
8358f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
8368f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
8378f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
8388f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
8398f250aa7SWarner Losh
84071c38472SWarner Losh20000810:
84171c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
84271c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
84371c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
84471c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
84571c38472SWarner Losh	specific use for it.
84671c38472SWarner Losh
84771c38472SWarner Losh20000729:
84871c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
84971c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
85071c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
85171c38472SWarner Losh	afterwards (unless the variables already are set, of course):
85271c38472SWarner Losh		# Enable network daemons for user convenience.
85371c38472SWarner Losh		inetd_enable="YES"
85471c38472SWarner Losh		portmap_enable="YES"
85571c38472SWarner Losh		sendmail_enable="YES"
85671c38472SWarner Losh
85771c38472SWarner Losh20000728:
85871c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
85971c38472SWarner Losh	will need to change that to nullfs_load="YES".
86071c38472SWarner Losh
8611dece4a9SWarner Losh20000728:
8621dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
8631dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
8641dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
8651dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
8661dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
8671dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
8681dece4a9SWarner Losh	to /MYKERNEL.
8691dece4a9SWarner Losh
870409e887cSWarner Losh20000711:
871409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
872409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
873409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
874409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
875409e887cSWarner Losh	for details on potential problems that you might have and how
876409e887cSWarner Losh	to get around them.
877409e887cSWarner Losh
878409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
879409e887cSWarner Losh	clauses above, you needn't worry.
880409e887cSWarner Losh
881409e887cSWarner Losh20000711:
882409e887cSWarner Losh	/etc/security has been updated to print the inode number of
883409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
884409e887cSWarner Losh	in the number of changed programs the first time when you run
885409e887cSWarner Losh	mergemaster to get a new /etc/security.
886409e887cSWarner Losh
887673d13f2SWarner Losh20000710:
888673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
889673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
890673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
891673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
892673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
893673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
894673d13f2SWarner Losh	errors. (see below, 20000624).
895673d13f2SWarner Losh
896bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
8971dece4a9SWarner Losh
898673d13f2SWarner Losh20000709:
899c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
900c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
901c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
902673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
903673d13f2SWarner Losh
904e98e26cdSWarner Losh20000706:
905e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
906e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
907e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
908f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
909e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
9102c021c6cSMark Ovens	interim if needed.
911e98e26cdSWarner Losh
912e98e26cdSWarner Losh20000705:
913e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
914e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
915e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
916e98e26cdSWarner Losh	details.
917e98e26cdSWarner Losh
918c373950eSWarner Losh20000704:
9192f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
9202f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
9212f961bc8SWarner Losh
9222f961bc8SWarner Losh20000704:
923c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
924c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
925c373950eSWarner Losh	rc.d scripts that haven't been updated.
926c373950eSWarner Losh
92727dc3a2bSWarner Losh20000630:
92827dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
92927dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
93027dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
93127dc3a2bSWarner Losh
932b8c215acSWarner Losh20000625:
933b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
93427dc3a2bSWarner Losh	system installed in order to build the system and kernel.
93527dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
93627dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
93727dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
93827dc3a2bSWarner Losh	were required.  You should check with the latest collections
93927dc3a2bSWarner Losh	to make sure that these haven't changed.
940b8c215acSWarner Losh
9417b990719SWarner Losh20000624:
9427b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
9437b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
9447b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
9451a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
9467b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
9477b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
9487b990719SWarner Losh	date to the completion of the work.
9497b990719SWarner Losh
95027dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
95127dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
95227dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
95327dc3a2bSWarner Losh	recreate the random and urandom devices.
95427dc3a2bSWarner Losh
95581e54c50SWarner Losh20000622:
95681e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
95781e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
95881e54c50SWarner Losh	that used to be required when updating.
95981e54c50SWarner Losh
96039943833SWarner Losh20000621:
9612c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
9622a2f33fbSDaniel Baker	the config file update procedure.
9632a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
964c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
96559df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
96659df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
96739943833SWarner Losh
968290f9ad8SWarner Losh20000620:
969290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
970290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
971290f9ad8SWarner Losh	that workaround will no longer be required.
972290f9ad8SWarner Losh
97390fb6346SWarner Losh20000615:
97490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
97590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
97690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
97790fb6346SWarner Losh	devices.
97890fb6346SWarner Losh
979f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
980f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
981f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
982f75f65bbSWarner Losh	may work).
983f75f65bbSWarner Losh
984ba26da8eSWarner Losh20000612:
985ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
986290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
987c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
988290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
989f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
990f54a3542SWarner Losh	NEWCARD for examples of the new format.
991290f9ad8SWarner Losh
9929698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
9939698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
9949698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
9959698f2c0SWarner Losh	in it.
996bbcc5149SWarner Losh
997d65850ebSWarner Losh20000522:
998ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
999d65850ebSWarner Losh	building a kernel after this point is advised that they need
1000d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1001d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1002d65850ebSWarner Losh
1003d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1004d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1005d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1006d9583a00SWarner Losh	is resolved.
1007d9583a00SWarner Losh
10088039cedeSWarner Losh20000513:
10098039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
10108039cedeSWarner Losh
1011d65850ebSWarner Losh20000510:
10128039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
10138039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
10148039cedeSWarner Losh	is requires for the boot blocks to build properly.
10158039cedeSWarner Losh
10168039cedeSWarner Losh20000503:
10178039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
10188039cedeSWarner Losh	is now available.
10198039cedeSWarner Losh
1020d65850ebSWarner Losh20000502:
1021d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1022d65850ebSWarner Losh	connected to the kernel building instead.
1023d65850ebSWarner Losh
1024be149406SNik Clayton20000427:
10258039cedeSWarner Losh	You may need to build gperf
10268039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
10278039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
10288039cedeSWarner Losh	an option only in -current.
10298039cedeSWarner Losh
10302b8dd5f4SWarner Losh20000417:
10312b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1032f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
10332b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
10342b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
10352c021c6cSMark Ovens	before you reboot, you'll need to issue:
10362b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
10372b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
10382b8dd5f4SWarner Losh
10398d9f1945SWarner Losh20000320:
10402b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
10412b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
10422b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1043ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
10442b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
10458d9f1945SWarner Losh
1046f8ab1dd6SWarner Losh20000319:
1047f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1048f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1049f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1050f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1051f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1052f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1053f8ab1dd6SWarner Losh
105419cada77SWarner Losh20000318:
1055f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
105619cada77SWarner Losh	Large kernel changes are being committed and are in the
105719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
105819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
105919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
106019cada77SWarner Losh	that you are loading are up to date.
1061ba228352SWarner Losh
106219cada77SWarner Losh20000315:
10636d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
10646d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
10656d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
10666d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
10676d23c382SWarner Losh	boot.
10686d23c382SWarner Losh
10696d23c382SWarner Losh20000315:
107019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
107119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
107257199806SWarner Losh
1073dc0dbf5cSWarner LoshCOMMON ITEMS:
1074dc0dbf5cSWarner Losh
1075a24eff53SWarner Losh	General Notes
1076a24eff53SWarner Losh	-------------
1077a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1078a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1079a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1080a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1081a24eff53SWarner Losh	or several minor releases, or when several months have passed
1082a24eff53SWarner Losh	on the -current branch).
1083a24eff53SWarner Losh
10845780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
10855780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
10865780f3baSWarner Losh	environment when searching for values for global variables.
10875780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
10885780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
10895780f3baSWarner Losh	page for more details.
10905780f3baSWarner Losh
1091dc0dbf5cSWarner Losh	To build a kernel
1092dc0dbf5cSWarner Losh	-----------------
1093ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1094f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1095ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
10961e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
10971e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
1098dc0dbf5cSWarner Losh
1099ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1100ba01eb20SWarner Losh	--------------------------------------------------------------
1101ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
110247d0d01fSWarner Losh	config KERNEL_NAME_HERE
1103ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1104ba01eb20SWarner Losh	make depend
1105ba01eb20SWarner Losh	make
1106ba01eb20SWarner Losh	make install
1107ba01eb20SWarner Losh
1108ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1109ba01eb20SWarner Losh
1110ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1111ba01eb20SWarner Losh	-----------------------------------------------------------
111263cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
111363cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
111463cb445eSWarner Losh
1115f643de42SWarner Losh	<make sure you have good level 0 dumps>
111663cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
111763cb445eSWarner Losh	make buildworld
111863cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
111963cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
112063cb445eSWarner Losh							[1]
112163cb445eSWarner Losh	<reboot in single user>				[3]
112263cb445eSWarner Losh	mergemaster -p					[5]
112363cb445eSWarner Losh	make installworld
112463cb445eSWarner Losh	mergemaster					[4]
112563cb445eSWarner Losh	<reboot>
112663cb445eSWarner Losh
1127759f0aefSWarner Losh
1128f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1129f27b1fceSJoseph Koshy	--------------------------------------------------
1130f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1131f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1132f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1133f27b1fceSJoseph Koshy	# size.
1134f27b1fceSJoseph Koshy
1135f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1136f27b1fceSJoseph Koshy	<boot into -stable>
1137f27b1fceSJoseph Koshy	make buildworld
1138f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1139f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1140f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1141f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1142f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1143f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1144f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1145f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1146f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1147f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1148f27b1fceSJoseph Koshy	<reboot into current>
1149f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1150f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1151f27b1fceSJoseph Koshy 	<reboot>
1152f27b1fceSJoseph Koshy
1153f27b1fceSJoseph Koshy
1154f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1155f27b1fceSJoseph Koshy	----------------------------------------------
11565c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
11575c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
11585c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
11595c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1160ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1161f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1162f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1163f643de42SWarner Losh	# space on /.
1164f643de42SWarner Losh
1165f643de42SWarner Losh	<make sure you have good level 0 dumps>
1166fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
116721c075eaSWarner Losh	make buildworld					[9]
1168c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1169d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1170be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1171fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1172fc8c157fSWarner Losh							[1]
1173fc8c157fSWarner Losh	<reboot in single user>				[3]
1174835284beSWarner Losh	mergemaster -p					[5]
1175f8a4c901SWarner Losh	rm -rf /usr/include/g++
1176ba26da8eSWarner Losh	make installworld
1177a6cd4f9dSWarner Losh	mergemaster					[4]
1178ba26da8eSWarner Losh	<reboot>
1179ba26da8eSWarner Losh
1180fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1181fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1182fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1183fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1184fdb9f54dSWarner Losh	the UPDATING entries.
1185ba26da8eSWarner Losh
11861dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
11871dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
11881dece4a9SWarner Losh	your sources that you have read and understood all the recent
11891dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
11901dece4a9SWarner Losh	much fewer pitfalls.
11911dece4a9SWarner Losh
1192134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1193134d2e86SWarner Losh	should disable them at this point so they don't crash your
1194134d2e86SWarner Losh	system on reboot.
1195134d2e86SWarner Losh
11969c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
11979c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
11989c1a7444SWarner Losh	configuration.
11999c1a7444SWarner Losh
1200ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1201ee6e1fc3SWarner Losh		fsck -p
1202ee6e1fc3SWarner Losh		mount -u /
1203ee6e1fc3SWarner Losh		mount -a
1204ee6e1fc3SWarner Losh		cd /usr/src
120547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1206f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1207f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1208b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1209b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1210b705ae10SWarner Losh	be ignored while you proceed to the next step.
1211ee6e1fc3SWarner Losh
1212a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1213a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1214a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1215a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1216a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1217a6cd4f9dSWarner Losh	for potential gotchas.
1218a6cd4f9dSWarner Losh
1219835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1220835284beSWarner Losh	you may need to do this if you get unknown user in the following
1221835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1222835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1223835284beSWarner Losh	install) after the buildworld before this step if you last updated
1224835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1225835284beSWarner Losh
1226bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1227bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1228bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1229bd79cf40SWarner Losh		ok unload
1230bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1231bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1232bd79cf40SWarner Losh	described here.
1233fc8c157fSWarner Losh
1234fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1235fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1236fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1237fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1238fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1239fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1240fc8c157fSWarner Losh
1241c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1242c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1243c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1244c74fe6afSWarner Losh	that is hard to boot to recover.
1245c74fe6afSWarner Losh
124621c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
124721c075eaSWarner Losh	cvs prune empty directories.
1248dc0dbf5cSWarner LoshFORMAT:
1249dc0dbf5cSWarner Losh
1250f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
12511fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1252f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1253f8ab1dd6SWarner Loshprevious releases if your system is older than this.
12541fc1a0dcSWarner Losh
1255e72fd46aSWarner LoshCopyright information:
1256e72fd46aSWarner Losh
12579698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1258e72fd46aSWarner Losh
1259772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1260772730c7SWarner Loshmodification, in full or in part, in any form or format of this
12619698f2c0SWarner Loshdocument are permitted without further permission from the author.
1262e72fd46aSWarner Losh
1263e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1264e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1265e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1266e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1267e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1268e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1269e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1270e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1271e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1272e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1273e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1274e72fd46aSWarner Losh
1275e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1276e72fd46aSWarner Loshauthor a beer.
1277e72fd46aSWarner Losh
127822306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1279772730c7SWarner Loshthis document.
1280772730c7SWarner Losh
128197d92980SPeter Wemm$FreeBSD$
1282