xref: /freebsd/UPDATING (revision 17c159dce6d6c0427c41d431217dc0631f7a8c5c)
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
18a19f8ddaSDavid E. O'Brien	to maximize performance.
19c1f61aa9SDavid E. O'Brien
2017c159dcSSøren Schmidt20030824:
2117c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
2217c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
2317c159dcSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your 			kernel config file, as it is no longer pulled in automatically.
2417c159dcSSøren Schmidt
25c1f61aa9SDavid E. O'Brien20030819:
26c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
27c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
28c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
29c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
3069f7bcf3SWarner Losh
3138c962e7SNate Lawson20030728:
3238c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
3338c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
3438c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
3538c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
3638c962e7SNate Lawson	so the quirk can be re-enabled.
3738c962e7SNate Lawson
38178cf4e9SWarner Losh20030722:
39178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
40178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
41178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
42178cf4e9SWarner Losh	FPU hardware.
43178cf4e9SWarner Losh
44178cf4e9SWarner Losh20030714:
45178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
46178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
47178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
48178cf4e9SWarner Losh	People should report those issues to current@.
49178cf4e9SWarner Losh
50157c629aSWarner Losh20030711:
51157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
528b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
5305538fa9SWarner Losh	/usr/obj.
54157c629aSWarner Losh
556cc6353fSMarcel Moolenaar20030613: [retrospective]
566cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
576cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
586cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
596cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
606cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
616cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
626cc6353fSMarcel Moolenaar
636cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
646cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
656cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
666cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
676cc6353fSMarcel Moolenaar		:
686cc6353fSMarcel Moolenaar
696cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
706cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
716cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
726cc6353fSMarcel Moolenaar
73766c34e4SAndrey A. Chernov20030610:
74766c34e4SAndrey A. Chernov	Remove deprecated locale names and transition period code
75766c34e4SAndrey A. Chernov	for them, finishing switching to the new scheme. Check your
76766c34e4SAndrey A. Chernov	LANG environment variable.
77766c34e4SAndrey A. Chernov
787ddc2528SPoul-Henning Kamp20030609:
79df622d54SPoul-Henning Kamp	CCD has been changed to be a fully GEOMified class.  Kernel
80df622d54SPoul-Henning Kamp	and ccdconfig(8) needs to be in sync, this is particularly
81df622d54SPoul-Henning Kamp	important to remember beforehand if your source tree is on
82df622d54SPoul-Henning Kamp	a ccd device.  Consider making a copy of the old ccdconfig
83df622d54SPoul-Henning Kamp	into /boot/kernel.good or wherever you keep your backup
84df622d54SPoul-Henning Kamp	kernel.
85df622d54SPoul-Henning Kamp
8652b47445SMark Murray20030505:
8752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
8852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
8952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
9052b47445SMark Murray
91a26df538SWarner Losh20030502:
92a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
93a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
94a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
95a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
96a26df538SWarner Losh
974b065e2cSDoug Barton20030501:
984b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
994b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
1004b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
1014b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
1024b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
1034b065e2cSDoug Barton	utilizes these old scripts has also been removed.
1044b065e2cSDoug Barton
10581cda3d9SWarner Losh20030423:
10681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
10781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
10881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
10981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
11081cda3d9SWarner Losh	userland.  In general, you should have a userland and
11181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
11281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
11381cda3d9SWarner Losh	allowances are made.
11481cda3d9SWarner Losh
11547a657d1SRuslan Ermilov20030329:
11647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
11747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
11847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
11947a657d1SRuslan Ermilov
12047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
12147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
12247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
12347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
12447a657d1SRuslan Ermilov
12547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
12647a657d1SRuslan Ermilov	    make cleandir && make obj && \
12747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
12847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
12947a657d1SRuslan Ermilov
1305d2af00cSGregory Neil Shapiro20030208:
1315d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
1325d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
1335d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
1345d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
1355d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
1365d2af00cSGregory Neil Shapiro
1375d2af00cSGregory Neil Shapiro20030128:
1389db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
139ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
1409db58771SPoul-Henning Kamp	be removed when convenient.
1419db58771SPoul-Henning Kamp
1428d9b3f57SJake Burkholder20030126:
1438d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
1448d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
1458d9b3f57SJake Burkholder
1461c5efda5SJeff Roberson20030125:
1471c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
1481c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
149ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
1501c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
1511c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
1521c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
1531c5efda5SJeff Roberson
1549d1d64f5SWarner Losh20030115:
1559d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
1569d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
1579d1d64f5SWarner Losh	properly.
1589d1d64f5SWarner Losh
159c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
160c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
161c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
162c9fdb80aSWarner Losh	with NetBSD.
163c9fdb80aSWarner Losh
164161dc364SAlexander Kabaev20021222:
165161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
166161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
167161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
168161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
169161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
170161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
17184cc83efSAlexander Kabaev	rebuilt.
172161dc364SAlexander Kabaev
173fb4c8061SMartin Blapp20021216:
174fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
17589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
176fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
1779d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
178fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
179fb4c8061SMartin Blapp
18017d47eb3SGiorgos Keramidas20021202:
18117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
18217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
18317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
18417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
18517d47eb3SGiorgos Keramidas
186a4459294SBill Fenner20021029:
187a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
188a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
189a4459294SBill Fenner	consumers in sync.
190a4459294SBill Fenner
191fc8c157fSWarner Losh20021024:
192c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
193c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
194c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
195c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
196c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
197c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
198c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
199c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
20069f7bcf3SWarner Losh
201fd9e8bdaSAndrew Gallatin20021023:
202fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
203fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
204fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
205fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
206fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
207fd9e8bdaSAndrew Gallatin
208fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
209fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
210fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
211fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
212fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
213fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
214fd9e8bdaSAndrew Gallatin
215f8a4c901SWarner Losh20020831:
216f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
217f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
218f8a4c901SWarner Losh	programs and libraries need to be recompiled.
219f8a4c901SWarner Losh
220f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
221f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
222f8a4c901SWarner Losh
223c2248fa2SJens Schweikhardt20020827:
224c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
225c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
226c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
227c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
228c2248fa2SJens Schweikhardt
2290d533e43SRuslan Ermilov20020815:
2300d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
2310d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
2320d533e43SRuslan Ermilov	again.
2330d533e43SRuslan Ermilov
23433c1de7dSRuslan Ermilov20020729:
23533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
23633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
23733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
23833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
23933c1de7dSRuslan Ermilov
2402b877facSJulian Elischer20020702:
2412b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
2422b877facSJulian Elischer	There are still some minor problems with some signals but the
2432b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
2442b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
2452b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
2462b877facSJulian Elischer
24706596d37SWarner Losh20020701:
24806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
24906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
25006596d37SWarner Losh	GNOME.
25106596d37SWarner Losh
25295ba4330SJacques Vidrine20020511:
25395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
25495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
25595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
25695ba4330SJacques Vidrine	with the set-user-ID bit set.
25795ba4330SJacques Vidrine
258a81da3c9SDavid E. O'Brien20020510:
259f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
260f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
2614b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
262f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
263f50caf6fSDavid E. O'Brien
264f50caf6fSDavid E. O'Brien20020510:
265a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
266a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
267a81da3c9SDavid E. O'Brien	and then do a cvs update.
268a81da3c9SDavid E. O'Brien
269528a0ef5SJacques Vidrine20020421:
270528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
271528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
272528a0ef5SJacques Vidrine
27385aa5a2eSGregory Neil Shapiro20020404:
27485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
27585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
27685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
27785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
27885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
27985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
28085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
28185aa5a2eSGregory Neil Shapiro
2828f1e4358SRuslan Ermilov20020403:
2838f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
2848f1e4358SRuslan Ermilov
2852292c02eSWarner Losh20020315:
2862292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
2872292c02eSWarner Losh
28869f7bcf3SWarner Losh20020225:
28969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
29069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
29169f7bcf3SWarner Losh
2928f35c493SWarner Losh20020217:
2938f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
2948f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
2958f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
2968f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
2978f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
2988f35c493SWarner Losh
299835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
300835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
301835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
302835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
303835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
304835284beSWarner Losh	and group must be merged from src/etc/group and
305835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
306835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
307835284beSWarner Losh	mergemaster before this will work if you are updating from a
308835284beSWarner Losh	very old version of current.  The updating recipe has changed
309835284beSWarner Losh	as of this date.
310835284beSWarner Losh
311fa9401c1SWarner Losh20020112:
312fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
313fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
314fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
315fa9401c1SWarner Losh	you have local modifications, you can use
316fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
317fa9401c1SWarner Losh	/etc/pam.d.
318fa9401c1SWarner Losh
319fa9401c1SWarner Losh	Please see the following url for more details:
320fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
32147d0d01fSWarner Losh20011229:
32247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
32347d0d01fSWarner Losh	networkfs_types, please note that it has changed
32447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
32547d0d01fSWarner Losh
326514318a8SWarner Losh20011220:
327514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
328514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
329514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
330514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
331514318a8SWarner Losh	version have now been merged back into the base system's
332514318a8SWarner Losh	version now.  The only user-visible change resulting from this
333514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
334514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
335514318a8SWarner Losh	as well.  (There has never been rc file support for
336514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
337514318a8SWarner Losh	reverted by the time the changes are MFCed.)
338514318a8SWarner Losh
339514318a8SWarner Losh20011215:
340514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
341514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
342514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
343514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
344514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
345514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
346514318a8SWarner Losh	will need to be customized then for `odd' densities using
347514318a8SWarner Losh	fdcontrol(8).
348514318a8SWarner Losh
3492d22e2bfSWarner Losh20011209:
3502d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
3512d22e2bfSWarner Losh	and truss(1) now works again.
3522d22e2bfSWarner Losh
3539e0428e2SWarner Losh20011207:
3549e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
3559e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
3569e0428e2SWarner Losh	see
3579e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
3589e0428e2SWarner Losh	for details.
3599e0428e2SWarner Losh
3609bab8c59SWarner Losh20011204:
3619bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
3629bab8c59SWarner Losh	kernel and burncd to be in sync.
3639bab8c59SWarner Losh
364e57d8b01SWarner Losh20011203:
365e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
366e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
367e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
368e57d8b01SWarner Losh	not there already.
369e57d8b01SWarner Losh
370e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
371e57d8b01SWarner Losh	until the issue has been resolved.
372e57d8b01SWarner Losh
373b001d36fSJacques Vidrine20011202:
374b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
375b001d36fSJacques Vidrine	patched.
376b001d36fSJacques Vidrine
3774b676ec1SWarner Losh20011126:
3784b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
3795ebbf43eSWarner Losh	after this date.  You need to do this only once.
3804b676ec1SWarner Losh
381d961e462SWarner Losh20011103:
382d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
383d961e462SWarner Losh	edges may be left, but for the most part things should be
3844b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
385d961e462SWarner Losh
386d961e462SWarner Losh20011030:
387d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
388d961e462SWarner Losh	choppy waves in the upgrade process.
389d961e462SWarner Losh
3901fe003b6SWarner Losh20011030:
391a4b6fda0SWarner Losh	The asr driver problem has been resolved.
3921fe003b6SWarner Losh
3931fe003b6SWarner Losh20011027:
3941fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
3951fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
3961fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
3971fe003b6SWarner Losh	try to use from this date forward.
3981fe003b6SWarner Losh
3991fe003b6SWarner Losh20011025:
4001fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
4011fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
4021fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
4031fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
4041fe003b6SWarner Losh	TARGET_ARCH=i386.
4051fe003b6SWarner Losh
406d05f9643SWarner Losh20011001:
407d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
408d05f9643SWarner Losh	You must recompile both the kernel and userland applications
409d05f9643SWarner Losh	at the same time.
410d05f9643SWarner Losh
41158970f85SWarner Losh20010929:
41258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
41358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
41458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
41558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
4169d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
41758970f85SWarner Losh
41858970f85SWarner Losh20010927:
41958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
42058970f85SWarner Losh	To disable ACPI you can add
42166ff0e67SMax Khon		hint.acpi.0.disabled="1"
42258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
42358970f85SWarner Losh	loader "ok" prompt).
42458970f85SWarner Losh
42558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
42658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
42758970f85SWarner Losh	file and not list acpi in that list.
428378f4486SAlfred Perlstein
4295119d237SWarner Losh20010924:
4305119d237SWarner Losh	The buildworld has been fixed.  You may need to install
4315119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
4328b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
4338b039fffSWarner Losh	get them installed on every installworld, or execute the
4348b039fffSWarner Losh	following to get them installed only once:
4358b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
43658970f85SWarner Losh		make all install
4378b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
4385119d237SWarner Losh
4393c293725SWarner Losh20010919:
4403c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
4413c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
4423c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
443772730c7SWarner Losh	workaround is to add
4443c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
4453c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
4463c293725SWarner Losh	can be removed afterwards.
4473c293725SWarner Losh
4483c293725SWarner Losh	A proper fix to the buildworld target is needed.
4493c293725SWarner Losh
4503c293725SWarner Losh20010918:
4513c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
4523c293725SWarner Losh	NFS may be unstable after this date.
4533c293725SWarner Losh
4543c293725SWarner Losh20010912:
4553c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
4563c293725SWarner Losh	the kernel.  While a few problems were introduced in the
4573c293725SWarner Losh	initial commit, most of the major ones have been found and
4583c293725SWarner Losh	corrected.
4593c293725SWarner Losh
4603c293725SWarner Losh20010901:
4613c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
4623c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
4633c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
4643c293725SWarner Losh	have been rectified around this date.
4653c293725SWarner Losh
46698b17b95SWarner Losh20010823:
46798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
46898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
46998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
47098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
47198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
47298b17b95SWarner Losh 	permission for your name server configuration and that it
47398b17b95SWarner Losh 	has read and write permission for your slave zone files and
47498b17b95SWarner Losh 	directory.
47598b17b95SWarner Losh
47698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
47798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
47898b17b95SWarner Losh
47998b17b95SWarner Losh 		named_flags=
48098b17b95SWarner Losh
4817b9786edSMark Murray20010709:
4827b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
4837b9786edSMark Murray	the ability of the shared library major number to handle.
4847b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
4857b9786edSMark Murray	solution is to rebuild those ports.
4867b9786edSMark Murray
4871d28950eSWarner Losh20010628:
4881d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
4891d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
4901d28950eSWarner Losh
491e72fd46aSWarner Losh20010625:
49298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
49398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
49498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
49598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
49698b17b95SWarner Losh	IRQ configuration needs more safety belts.
49716de1a07SWarner Losh
4980d415dffSWarner Losh20010617:
499e72fd46aSWarner Losh	Softupdates problems have been corrected.
5000d415dffSWarner Losh
5010d415dffSWarner Losh20010614:
5020d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
5030d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
5040d415dffSWarner Losh	kernel building methods.
5050d415dffSWarner Losh
5068b9959adSWarner Losh20010613:
5078b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
5088b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
509e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
510e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
5118b9959adSWarner Losh
512e72fd46aSWarner Losh20010613:
5138b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
514e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
515e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
5168b9959adSWarner Losh
5170d415dffSWarner Losh20010612:
5180d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
5190d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
5200d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
5210d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
5220d415dffSWarner Losh	until this bug is fixed.
5230d415dffSWarner Losh
524e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
525e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
526ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
527e72fd46aSWarner Losh
5280d415dffSWarner Losh20010610:
5290d415dffSWarner Losh	Locale names have changed to match other systems better.
5300d415dffSWarner Losh
5316ccdb5e4SWarner Losh20010604:
5326ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
5336ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
5346ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
5353590182eSWarner Losh	Interrupt storms look a lot like a hang.
5363590182eSWarner Losh
5373590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
5383590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
5393590182eSWarner Losh	it is).
5403590182eSWarner Losh
5413590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
5423590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
5433590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
5443590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
5456ccdb5e4SWarner Losh
5460bc62786SWarner Losh20010530:
5470bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
5480bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
5490bc62786SWarner Losh	a limited time.  If you see
5500bc62786SWarner Losh
5510bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
5520bc62786SWarner Losh
5530bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
5540bc62786SWarner Losh	COPY=-C.
5550bc62786SWarner Losh
55668a38c6cSWarner Losh20010525:
557b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
558c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
559c4f4a728SWarner Losh	definitely is in bad shape.
56068a38c6cSWarner Losh
561ed0f29caSWarner Losh20010521:
562ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
563ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
564ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
565ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
566ed0f29caSWarner Losh	is
567ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
568ed0f29caSWarner Losh
56980c16af9SWarner Losh20010520:
57068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
57180c16af9SWarner Losh
57280c16af9SWarner Losh20010519:
57380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
57480c16af9SWarner Losh	the past few days.  Everything should still work, but if
57580c16af9SWarner Losh	not, please contact imp@freebsd.org.
57680c16af9SWarner Losh
577a45f2d05SWarner Losh20010517:
578a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
579a45f2d05SWarner Losh	userland at the same time.
580a45f2d05SWarner Losh
581a45f2d05SWarner Losh20010517:
582a45f2d05SWarner Losh	New ncurses imported.
583a45f2d05SWarner Losh
5842988afcaSWarner Losh20010512:
5852988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
5862988afcaSWarner Losh	will be the only way to go starting July 1.
5872988afcaSWarner Losh
5881a33dba7SWarner Losh20010504:
5891a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
5901a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
5911a33dba7SWarner Losh
59209946a51SWarner Losh20010502:
59309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
59409946a51SWarner Losh
59509946a51SWarner Losh20010501:
59609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
59709946a51SWarner Losh
59809946a51SWarner Losh20010430:
599a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
60009946a51SWarner Losh	go back in the water.
60109946a51SWarner Losh
60209946a51SWarner Losh20010429:
60309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
60409946a51SWarner Losh	this date, but before the correction date.
60509946a51SWarner Losh
60691dd3b53SWarner Losh20010423:
60791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
60891dd3b53SWarner Losh
60991dd3b53SWarner Losh20010411:
61091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
61191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
61291dd3b53SWarner Losh	Update only if you understand that you must not use the old
61391dd3b53SWarner Losh	fsck with the new kernel ever.
61491dd3b53SWarner Losh
615933b3269SWarner Losh20010330:
616933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
617c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
618933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
619933b3269SWarner Losh
620933b3269SWarner Losh20010319:
621933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
622933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
623933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
624f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
62509946a51SWarner Losh
62609946a51SWarner Losh20010315:
62709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
628ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
62909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
630933b3269SWarner Losh
631933b3269SWarner Losh20010312:
632933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
633933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
634933b3269SWarner Losh
635933b3269SWarner Losh20010312:
636933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
637933b3269SWarner Losh	instead of ad-hoc.
638933b3269SWarner Losh
639933b3269SWarner Losh20010310:
640f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
641933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
642933b3269SWarner Losh	ssh might not work if you don't.
643933b3269SWarner Losh
64462353691SWarner Losh20010303:
64562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
64662353691SWarner Losh	which means that you must include the miibus in your kernel if
64762353691SWarner Losh	you use the ed driver.
64862353691SWarner Losh
649d325cf65SWarner Losh20010220:
650d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
651d325cf65SWarner Losh	safe to go back into the water.
652d325cf65SWarner Losh
653024daae6SWarner Losh20010211:
654024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
655024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
656024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
657024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
658024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
659024daae6SWarner Losh
660024daae6SWarner Losh	To get to the new system, you'll need to use the following
661024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
662024daae6SWarner Losh	don't have to move this to the updating section.
663024daae6SWarner Losh
664024daae6SWarner Losh	To get around the installworld problem, do:
665024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
666024daae6SWarner Losh		# make install
667024daae6SWarner Losh		# cd /usr/src
668024daae6SWarner Losh		# make installworld
669024daae6SWarner Losh	If that doesn't work, then try:
670024daae6SWarner Losh		# make -k installworld
671024daae6SWarner Losh		# make installworld
672024daae6SWarner Losh
673024daae6SWarner Losh20010207:
674024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
675024daae6SWarner Losh	do not include devfs in your kernel as problems result.
676024daae6SWarner Losh
677024daae6SWarner Losh20010205:
6787595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
679024daae6SWarner Losh	Remove them from your config.
680024daae6SWarner Losh
6811e159248SWarner Losh20010122:
6821e159248SWarner Losh	****************************** WARNING ******************************
6831e159248SWarner Losh			buildkernel has been changed slightly
6841e159248SWarner Losh	****************************** WARNING ******************************
6851e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
6861e159248SWarner Losh	should update your scripts and make.conf accordingly.
6871e159248SWarner Losh
6881e159248SWarner Losh20010119:
6891e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
6901e159248SWarner Losh	This requires a new config to build correctly.
6911e159248SWarner Losh
692aac7dfeaSWarner Losh20010116:
693ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
694aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
695aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
696aac7dfeaSWarner Losh
697aac7dfeaSWarner Losh20010110:
698aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
699aac7dfeaSWarner Losh
700aac7dfeaSWarner Losh20010102:
701aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
702aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
703aac7dfeaSWarner Losh
70463c90c9eSWarner Losh20010101:
70563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
70663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
7075fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
70863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
70963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
71063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
71163c90c9eSWarner Losh	might have been ignored by the -k option.
71263c90c9eSWarner Losh
7135fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
7145fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
7155fd2a895SWarner Losh	of this working.
7165fd2a895SWarner Losh
717aac7dfeaSWarner Losh20001228:
718aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
719ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
720aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
721aac7dfeaSWarner Losh
722de2bcc63SWarner Losh20001218:
723de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
724de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
725de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
726de2bcc63SWarner Losh	cards will not be recognized without it.
727de2bcc63SWarner Losh
728960773f7SWarner Losh20001205:
729960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
730960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
731960773f7SWarner Losh	adding the following in pam.conf:
732960773f7SWarner Losh
733960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
734960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
735960773f7SWarner Losh	sshd    session required        pam_permit.so
736960773f7SWarner Losh
7370acc635eSWarner Losh20001031:
7380acc635eSWarner Losh	cvs updated to 1.11.
7390acc635eSWarner Losh
7400acc635eSWarner Losh20001020:
7410acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
7420acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
7430acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
7440acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
7450acc635eSWarner Losh	workaround.
7460acc635eSWarner Losh
7470acc635eSWarner Losh20001010:
7480acc635eSWarner Losh	****************************** WARNING ******************************
7490acc635eSWarner Losh				Sendmail has been updated.
7500acc635eSWarner Losh	****************************** WARNING ******************************
7510acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
7520acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
7530acc635eSWarner Losh	  is set.
7540acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
7550acc635eSWarner Losh	  commands.
7560acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
7570acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
7580acc635eSWarner Losh	  in /usr/share/sendmail/cf.
7590acc635eSWarner Losh	o sendmail.cw changed to local-host-names
7600acc635eSWarner Losh
7610acc635eSWarner Losh	More details can be found at
7620acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
7630acc635eSWarner Losh
7646e98a146SWarner Losh20001009:
7656e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
7666e98a146SWarner Losh	your entire ports tree, or you will have problems.
7676e98a146SWarner Losh
7686e98a146SWarner Losh20001006:
769685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
7706e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
7716e98a146SWarner Losh	/usr/bin/miniperl.
7726e98a146SWarner Losh
773073113a4SWarner Losh20001005:
774073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
775685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
776073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
777073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
778073113a4SWarner Losh	tree for anything to work.
779073113a4SWarner Losh
7800acc635eSWarner Losh20000928:
7810acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
7820acc635eSWarner Losh
783be3885b3SWarner Losh20000916:
784be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
785be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
786be3885b3SWarner Losh	same time as your kernel.
787be3885b3SWarner Losh
78876ec9675SWarner Losh20000914:
78976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
79076ec9675SWarner Losh	include the device will cause suspended laptops losing time
79176ec9675SWarner Losh	when they resume.  Include
79276ec9675SWarner Losh		device		pmtimer
79376ec9675SWarner Losh	in your config file and
79401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
79576ec9675SWarner Losh	to your /boot/device.hints file.
79676ec9675SWarner Losh
797f4865386SMark Murray20000911:
798f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
799f4865386SMark Murray	rather than an option. The supplied kernel config files have
800f4865386SMark Murray	been updated. You will need to do something similar in your
801f4865386SMark Murray	own kernel config file.
802f4865386SMark Murray	Remove:
803f4865386SMark Murray		options		RANDOMDEV
804f4865386SMark Murray	Add:
805f4865386SMark Murray		device		random
806f4865386SMark Murray	If you prefer to load the loadable module, you need to do
807f4865386SMark Murray	nothing.
808f4865386SMark Murray
809d594498fSWarner Losh20000909:
810d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
811d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
812d594498fSWarner Losh	reflect this if you load this module at boot time.
813d594498fSWarner Losh	The line should read:
814d594498fSWarner Losh		random_load="YES"
815d594498fSWarner Losh
8160deb7ddcSWarner Losh20000907:
8170deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
81816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
81916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
82016eb772dSWarner Losh	sure you don't have model loading problems which might at
82116eb772dSWarner Losh	first blush appear related to SMP.
82252bf24e7SWarner Losh
8235a01880bSWarner Losh20000906:
8245a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
8255a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
8265a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
8275a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
8285a01880bSWarner Losh	don't have one, and you have host.conf.
8295a01880bSWarner Losh
8302b41163cSWarner Losh20000905:
83138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
83238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
83338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
83438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
83538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
83638d6ecd2SWarner Losh
83738d6ecd2SWarner Losh20000905:
8388aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
8398aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
8408aab4bc7SWarner Losh	is /boot/kernel.
8418aab4bc7SWarner Losh
8428aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
84338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
84438d6ecd2SWarner Losh	installkernel/installworld dance.
8452b41163cSWarner Losh
846d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
847d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
848d594498fSWarner Losh	modules in that directory instead of finding them in the correct
849d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
850d594498fSWarner Losh	is that the linux module crashes your machine after the update.
851d594498fSWarner Losh
852d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
853d594498fSWarner Losh		mv /modules.old /boot/kernel.old
854d594498fSWarner Losh		chflags noschg /kernel.old
855d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
856d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
857d594498fSWarner Losh	fi
858d594498fSWarner Losh
859c22a309cSWarner Losh20000904:
860c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
861c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
862c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
863c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
864c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
865c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
866c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
867c22a309cSWarner Losh	is not likely to be generated.
868c22a309cSWarner Losh
869fdb9f54dSWarner Losh20000825:
870fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
8719c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
8729c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
8739c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
8749c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
8759c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
8769c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
8779c1a7444SWarner Losh	kernel.
8789c1a7444SWarner Losh
8799c1a7444SWarner Losh20000821:
8809c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
8819c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
8829c1a7444SWarner Losh	/boot/loader.conf.
883fdb9f54dSWarner Losh
8848f250aa7SWarner Losh20000812:
8855da0d091SWarner Losh	suidperl is now always built and installed on the system, but
8865da0d091SWarner Losh	with permissions of 511.  If you have applications that use
8875da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
8885da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
8895da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
8905da0d091SWarner Losh	will fix this until the next build.
8915da0d091SWarner Losh
8925da0d091SWarner Losh20000812:
8938f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
8948f250aa7SWarner Losh	visible changes that may immediately affect your configuration
8958f250aa7SWarner Losh	include:
8968f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
8978f250aa7SWarner Losh	- newaliases limited to root and trusted users
8988f250aa7SWarner Losh	- MSA port (587) turned on by default
8998f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
9008f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
9018f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
9028f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
9038f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
9048f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
9058f250aa7SWarner Losh
90671c38472SWarner Losh20000810:
90771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
90871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
90971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
91071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
91171c38472SWarner Losh	specific use for it.
91271c38472SWarner Losh
91371c38472SWarner Losh20000729:
91471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
91571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
91671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
91771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
91871c38472SWarner Losh		# Enable network daemons for user convenience.
91971c38472SWarner Losh		inetd_enable="YES"
92071c38472SWarner Losh		portmap_enable="YES"
92171c38472SWarner Losh		sendmail_enable="YES"
92271c38472SWarner Losh
92371c38472SWarner Losh20000728:
92471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
92571c38472SWarner Losh	will need to change that to nullfs_load="YES".
92671c38472SWarner Losh
9271dece4a9SWarner Losh20000728:
9281dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
9291dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
9301dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
9311dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
9321dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
9331dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
9341dece4a9SWarner Losh	to /MYKERNEL.
9351dece4a9SWarner Losh
936409e887cSWarner Losh20000711:
937409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
938409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
939409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
940409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
941409e887cSWarner Losh	for details on potential problems that you might have and how
942409e887cSWarner Losh	to get around them.
943409e887cSWarner Losh
944409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
945409e887cSWarner Losh	clauses above, you needn't worry.
946409e887cSWarner Losh
947409e887cSWarner Losh20000711:
948409e887cSWarner Losh	/etc/security has been updated to print the inode number of
949409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
950409e887cSWarner Losh	in the number of changed programs the first time when you run
951409e887cSWarner Losh	mergemaster to get a new /etc/security.
952409e887cSWarner Losh
953673d13f2SWarner Losh20000710:
954673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
955673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
956673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
957673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
958673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
959673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
960673d13f2SWarner Losh	errors. (see below, 20000624).
961673d13f2SWarner Losh
962bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
9631dece4a9SWarner Losh
964673d13f2SWarner Losh20000709:
965c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
966c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
967c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
968673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
969673d13f2SWarner Losh
970e98e26cdSWarner Losh20000706:
971e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
972e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
973e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
974f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
975e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
9762c021c6cSMark Ovens	interim if needed.
977e98e26cdSWarner Losh
978e98e26cdSWarner Losh20000705:
979e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
980e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
981e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
982e98e26cdSWarner Losh	details.
983e98e26cdSWarner Losh
984c373950eSWarner Losh20000704:
9852f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
9862f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
9872f961bc8SWarner Losh
9882f961bc8SWarner Losh20000704:
989c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
990c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
991c373950eSWarner Losh	rc.d scripts that haven't been updated.
992c373950eSWarner Losh
99327dc3a2bSWarner Losh20000630:
99427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
99527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
99627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
99727dc3a2bSWarner Losh
998b8c215acSWarner Losh20000625:
999b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
100027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
100127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
100227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
100327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
100427dc3a2bSWarner Losh	were required.  You should check with the latest collections
100527dc3a2bSWarner Losh	to make sure that these haven't changed.
1006b8c215acSWarner Losh
10077b990719SWarner Losh20000624:
10087b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
10097b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
10107b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
10111a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
10127b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
10137b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
10147b990719SWarner Losh	date to the completion of the work.
10157b990719SWarner Losh
101627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
101727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
101827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
101927dc3a2bSWarner Losh	recreate the random and urandom devices.
102027dc3a2bSWarner Losh
102181e54c50SWarner Losh20000622:
102281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
102381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
102481e54c50SWarner Losh	that used to be required when updating.
102581e54c50SWarner Losh
102639943833SWarner Losh20000621:
10272c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
10282a2f33fbSDaniel Baker	the config file update procedure.
10292a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1030c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
103159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
103259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
103339943833SWarner Losh
1034290f9ad8SWarner Losh20000620:
1035290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1036290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1037290f9ad8SWarner Losh	that workaround will no longer be required.
1038290f9ad8SWarner Losh
103990fb6346SWarner Losh20000615:
104090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
104190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
104290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
104390fb6346SWarner Losh	devices.
104490fb6346SWarner Losh
1045f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1046f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1047f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1048f75f65bbSWarner Losh	may work).
1049f75f65bbSWarner Losh
1050ba26da8eSWarner Losh20000612:
1051ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1052290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1053c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1054290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1055f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1056f54a3542SWarner Losh	NEWCARD for examples of the new format.
1057290f9ad8SWarner Losh
10589698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
10599698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
10609698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
10619698f2c0SWarner Losh	in it.
1062bbcc5149SWarner Losh
1063d65850ebSWarner Losh20000522:
1064ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1065d65850ebSWarner Losh	building a kernel after this point is advised that they need
1066d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1067d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1068d65850ebSWarner Losh
1069d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1070d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1071d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1072d9583a00SWarner Losh	is resolved.
1073d9583a00SWarner Losh
10748039cedeSWarner Losh20000513:
10758039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
10768039cedeSWarner Losh
1077d65850ebSWarner Losh20000510:
10788039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
10798039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
10808039cedeSWarner Losh	is requires for the boot blocks to build properly.
10818039cedeSWarner Losh
10828039cedeSWarner Losh20000503:
10838039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
10848039cedeSWarner Losh	is now available.
10858039cedeSWarner Losh
1086d65850ebSWarner Losh20000502:
1087d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1088d65850ebSWarner Losh	connected to the kernel building instead.
1089d65850ebSWarner Losh
1090be149406SNik Clayton20000427:
10918039cedeSWarner Losh	You may need to build gperf
10928039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
10938039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
10948039cedeSWarner Losh	an option only in -current.
10958039cedeSWarner Losh
10962b8dd5f4SWarner Losh20000417:
10972b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1098f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
10992b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
11002b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
11012c021c6cSMark Ovens	before you reboot, you'll need to issue:
11022b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
11032b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
11042b8dd5f4SWarner Losh
11058d9f1945SWarner Losh20000320:
11062b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
11072b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
11082b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1109ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
11102b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
11118d9f1945SWarner Losh
1112f8ab1dd6SWarner Losh20000319:
1113f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1114f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1115f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1116f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1117f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1118f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1119f8ab1dd6SWarner Losh
112019cada77SWarner Losh20000318:
1121f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
112219cada77SWarner Losh	Large kernel changes are being committed and are in the
112319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
112419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
112519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
112619cada77SWarner Losh	that you are loading are up to date.
1127ba228352SWarner Losh
112819cada77SWarner Losh20000315:
11296d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
11306d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
11316d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
11326d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
11336d23c382SWarner Losh	boot.
11346d23c382SWarner Losh
11356d23c382SWarner Losh20000315:
113619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
113719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
113857199806SWarner Losh
1139dc0dbf5cSWarner LoshCOMMON ITEMS:
1140dc0dbf5cSWarner Losh
1141a24eff53SWarner Losh	General Notes
1142a24eff53SWarner Losh	-------------
1143a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1144a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1145a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1146a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1147a24eff53SWarner Losh	or several minor releases, or when several months have passed
1148a24eff53SWarner Losh	on the -current branch).
1149a24eff53SWarner Losh
11505780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
11515780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
11525780f3baSWarner Losh	environment when searching for values for global variables.
11535780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
11545780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
11555780f3baSWarner Losh	page for more details.
11565780f3baSWarner Losh
1157dc0dbf5cSWarner Losh	To build a kernel
1158dc0dbf5cSWarner Losh	-----------------
1159ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1160f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1161ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
11621e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
11631e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
1164dc0dbf5cSWarner Losh
1165ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1166ba01eb20SWarner Losh	--------------------------------------------------------------
1167ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
116847d0d01fSWarner Losh	config KERNEL_NAME_HERE
1169ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1170ba01eb20SWarner Losh	make depend
1171ba01eb20SWarner Losh	make
1172ba01eb20SWarner Losh	make install
1173ba01eb20SWarner Losh
1174ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1175ba01eb20SWarner Losh
1176ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1177ba01eb20SWarner Losh	-----------------------------------------------------------
117863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
117963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
118063cb445eSWarner Losh
1181f643de42SWarner Losh	<make sure you have good level 0 dumps>
118263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
118363cb445eSWarner Losh	make buildworld
118463cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
118563cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
118663cb445eSWarner Losh							[1]
118763cb445eSWarner Losh	<reboot in single user>				[3]
118863cb445eSWarner Losh	mergemaster -p					[5]
118963cb445eSWarner Losh	make installworld
119063cb445eSWarner Losh	mergemaster					[4]
119163cb445eSWarner Losh	<reboot>
119263cb445eSWarner Losh
1193759f0aefSWarner Losh
1194f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1195f27b1fceSJoseph Koshy	--------------------------------------------------
1196f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1197f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1198f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1199f27b1fceSJoseph Koshy	# size.
1200f27b1fceSJoseph Koshy
1201f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1202f27b1fceSJoseph Koshy	<boot into -stable>
1203f27b1fceSJoseph Koshy	make buildworld
1204f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1205f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1206f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1207f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1208f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1209f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1210f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1211f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1212f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1213f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1214f27b1fceSJoseph Koshy	<reboot into current>
1215f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1216f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1217f27b1fceSJoseph Koshy 	<reboot>
1218f27b1fceSJoseph Koshy
1219f27b1fceSJoseph Koshy
1220f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1221f27b1fceSJoseph Koshy	----------------------------------------------
12225c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
12235c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
12245c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
12255c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1226ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1227f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1228f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1229f643de42SWarner Losh	# space on /.
1230f643de42SWarner Losh
1231f643de42SWarner Losh	<make sure you have good level 0 dumps>
1232fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
123321c075eaSWarner Losh	make buildworld					[9]
1234c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1235d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1236be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1237fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1238fc8c157fSWarner Losh							[1]
1239fc8c157fSWarner Losh	<reboot in single user>				[3]
1240835284beSWarner Losh	mergemaster -p					[5]
1241f8a4c901SWarner Losh	rm -rf /usr/include/g++
1242ba26da8eSWarner Losh	make installworld
1243a6cd4f9dSWarner Losh	mergemaster					[4]
1244ba26da8eSWarner Losh	<reboot>
1245ba26da8eSWarner Losh
1246fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1247fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1248fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1249fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1250fdb9f54dSWarner Losh	the UPDATING entries.
1251ba26da8eSWarner Losh
12521dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
12531dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
12541dece4a9SWarner Losh	your sources that you have read and understood all the recent
12551dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
12561dece4a9SWarner Losh	much fewer pitfalls.
12571dece4a9SWarner Losh
1258134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1259134d2e86SWarner Losh	should disable them at this point so they don't crash your
1260134d2e86SWarner Losh	system on reboot.
1261134d2e86SWarner Losh
12629c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
12639c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
12649c1a7444SWarner Losh	configuration.
12659c1a7444SWarner Losh
1266ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1267ee6e1fc3SWarner Losh		fsck -p
1268ee6e1fc3SWarner Losh		mount -u /
1269ee6e1fc3SWarner Losh		mount -a
1270ee6e1fc3SWarner Losh		cd /usr/src
127147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1272f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1273f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1274b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1275b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1276b705ae10SWarner Losh	be ignored while you proceed to the next step.
1277ee6e1fc3SWarner Losh
1278a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1279a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1280a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1281a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1282a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1283a6cd4f9dSWarner Losh	for potential gotchas.
1284a6cd4f9dSWarner Losh
1285835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1286835284beSWarner Losh	you may need to do this if you get unknown user in the following
1287835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1288835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1289835284beSWarner Losh	install) after the buildworld before this step if you last updated
1290835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1291835284beSWarner Losh
1292bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1293bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1294bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1295bd79cf40SWarner Losh		ok unload
1296bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1297bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1298bd79cf40SWarner Losh	described here.
1299fc8c157fSWarner Losh
1300fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1301fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1302fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1303fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1304fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1305fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1306fc8c157fSWarner Losh
1307c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1308c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1309c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1310c74fe6afSWarner Losh	that is hard to boot to recover.
1311c74fe6afSWarner Losh
131221c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
131321c075eaSWarner Losh	cvs prune empty directories.
1314dc0dbf5cSWarner LoshFORMAT:
1315dc0dbf5cSWarner Losh
1316f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
13171fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1318f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1319f8ab1dd6SWarner Loshprevious releases if your system is older than this.
13201fc1a0dcSWarner Losh
1321e72fd46aSWarner LoshCopyright information:
1322e72fd46aSWarner Losh
13239698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1324e72fd46aSWarner Losh
1325772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1326772730c7SWarner Loshmodification, in full or in part, in any form or format of this
13279698f2c0SWarner Loshdocument are permitted without further permission from the author.
1328e72fd46aSWarner Losh
1329e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1330e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1331e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1332e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1333e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1334e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1335e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1336e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1337e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1338e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1339e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1340e72fd46aSWarner Losh
1341e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1342e72fd46aSWarner Loshauthor a beer.
1343e72fd46aSWarner Losh
134422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1345772730c7SWarner Loshthis document.
1346772730c7SWarner Losh
134797d92980SPeter Wemm$FreeBSD$
1348