xref: /freebsd/UPDATING (revision 8804652415e5d69d3b144571d493307caaf6d840)
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
72c724730SWarner LoshItems affecting the ports and packages system can be found in
82c724730SWarner Losh/usr/ports/UPDATING.  Please read that file before running
92c724730SWarner Loshportupgrade.  Important recent entries: 20040724 (default X changes).
102c724730SWarner Losh
11f692e7ecSWarner Losh[[ The UPDATING file will be trimmed to 20040814 on or about Oct 1, 2004 ]]
12f692e7ecSWarner Losh
13f692e7ecSWarner LoshNOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW:
14f692e7ecSWarner Losh	FreeBSD 6.x has many debugging features turned on, in
1569f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1669f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1769f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1869f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1969f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
2069f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
2169f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
2269f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
2369f7bcf3SWarner Losh	developers choose to disable these features on build machines
24a19f8ddaSDavid E. O'Brien	to maximize performance.
25c1f61aa9SDavid E. O'Brien
2688046524SSam Leffler20041201:
2788046524SSam Leffler	The wlan support has been updated to split the crypto support
2888046524SSam Leffler	into separate modules.  For static WEP you must configure the
2988046524SSam Leffler	wlan_wep module in your system or build and install the module
3088046524SSam Leffler	in place where it can be loaded (the kernel will auto-load
3188046524SSam Leffler	the module when a wep key is configured).
3288046524SSam Leffler
3388046524SSam Leffler20041201:
3488046524SSam Leffler	The ath driver has been updated to split the tx rate control
3588046524SSam Leffler	algorithm into a separate module.  You need to include either
3688046524SSam Leffler	ath_rate_onoe or ath_rate_amrr when configuring the kernel.
3788046524SSam Leffler
3881adddf3SJohn Baldwin20041116:
3981adddf3SJohn Baldwin	Support for systems with an 80386 CPU has been removed.  Please
4081adddf3SJohn Baldwin	use FreeBSD 5.x or earlier on systems with an 80386.
4181adddf3SJohn Baldwin
4242ba1c57SPoul-Henning Kamp20041110:
4342ba1c57SPoul-Henning Kamp	We have had a hack which would mount the root filesystem
4442ba1c57SPoul-Henning Kamp	R/W if the device were named 'md*'.  As part of the vnode
4542ba1c57SPoul-Henning Kamp	work I'm doing I have had to remove this hack.  People
4642ba1c57SPoul-Henning Kamp	building systems which use preloaded MD root filesystems
4742ba1c57SPoul-Henning Kamp	may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
4842ba1c57SPoul-Henning Kamp	their /etc/rc scripts.
4942ba1c57SPoul-Henning Kamp
50c94c54e4SAndre Oppermann20041102:
51c94c54e4SAndre Oppermann	The size of struct tcpcb has changed again due to the removal
52c94c54e4SAndre Oppermann	of RFC1644 T/TCP.  You have to recompile userland programs that
53c94c54e4SAndre Oppermann	read kmem for tcp sockets directly (netstat, sockstat, etc.)
54c94c54e4SAndre Oppermann
55cd109b0dSAndre Oppermann20041022:
56cd109b0dSAndre Oppermann	The size of struct tcpcb has changed.  You have to recompile
57cd109b0dSAndre Oppermann	userland programs that read kmem for tcp sockets directly
58cd109b0dSAndre Oppermann	(netstat, sockstat, etc.)
59cd109b0dSAndre Oppermann
607b606583SPoul-Henning Kamp20041018:
617b606583SPoul-Henning Kamp	A major sweep over the tty drivers to elimnate approx 3100
627b606583SPoul-Henning Kamp	lines of copy&pasted code have been performed.  As a part of
637b606583SPoul-Henning Kamp	this change some tty devices have changed names:
647b606583SPoul-Henning Kamp	sio devices are now named:	{tty,cua}d%d[.init,.lock]
657b606583SPoul-Henning Kamp	ucom devices are now named:	{tty,cua}U%d[.init,.lock]
667b606583SPoul-Henning Kamp	For other drivers see the commit logs.
677b606583SPoul-Henning Kamp
68cf0684aeSMike Makonnen20041007:
69028a5b92SMike Makonnen	The FreeBSD keyword is no longer a requirement for a valid
70028a5b92SMike Makonnen	rc.d script. The rc(8) and rc.shutdown(8) scripts no longer check
71028a5b92SMike Makonnen	for the existence of this keyword when ordering rc.d scripts.
7200bd8f10SMike Makonnen	This change touches most of the file in /etc/rc.d; therefore,
7300bd8f10SMike Makonnen	if you have not modified any files in that directory it may
7400bd8f10SMike Makonnen	be easier to rm -rf /etc/rc.d and then use the -i switch with
7500bd8f10SMike Makonnen	mergemaster(8).
76028a5b92SMike Makonnen
77028a5b92SMike Makonnen20041007:
78cf0684aeSMike Makonnen	One of the syscalls the 1:1 threading library libthr uses has
79cf0684aeSMike Makonnen	changed, thus breaking ABI compatibility. Make sure you rebuild
80cf0684aeSMike Makonnen	this library with the kernel.
81cf0684aeSMike Makonnen
8285a8b887SKen Smith20041001:
8385a8b887SKen Smith	The following libraries had their version number bumped up:
8485a8b887SKen Smith		/lib/libm.so.2 -> libm.so.3
8585a8b887SKen Smith		/lib/libreadline.so.4 -> libreadline.so.5
8685a8b887SKen Smith		/usr/lib/libhistory.so.4 -> libhistory.so.5
8785a8b887SKen Smith		/usr/lib/libopie.so.2 -> libopie.so.3
8885a8b887SKen Smith		/usr/lib/libpcap.so.2 -> libpcap.so.3
8985a8b887SKen Smith	FreeBSD 4.10 versions of these libraries will be added to the
9085a8b887SKen Smith	compat4x collection.  If you expect to be able to run old 4.X
9185a8b887SKen Smith	executables you will need to remove the old versions of these
9285a8b887SKen Smith	libraries.  However note that any 5.X executables you have built
9385a8b887SKen Smith	will stop working once you remove those old libraries.  You should
9485a8b887SKen Smith	have all your ports/packages rebuilt before removing the old
9585a8b887SKen Smith	libraries.
9685a8b887SKen Smith
97d6a8d588SMax Laier20040929:
98d6a8d588SMax Laier	The pfil API has gained an additional argument to pass an inpcb.
99d6a8d588SMax Laier	You should rebuild all pfil consuming modules: ipfw, ipfilter
100d6a8d588SMax Laier	and pf.
101d6a8d588SMax Laier
1028f1bb389SDoug Barton20040928:
103cfeb1f52SDoug Barton	If named is enabled, the default is now to run it in a chroot
1048f1bb389SDoug Barton	"sandbox." For users with existing configurations in
1058f1bb389SDoug Barton	/etc/namedb the migration should be simple. Upgrade your
1068f1bb389SDoug Barton	world as usual, then after installworld but before
1078f1bb389SDoug Barton	mergemaster do the following:
1088f1bb389SDoug Barton
1098f1bb389SDoug Barton	If named is running: /etc/rc.d/named stop
1108f1bb389SDoug Barton	cd /etc
1118f1bb389SDoug Barton	mv namedb namedb.bak
1128f1bb389SDoug Barton	mkdir -p /var/named/etc/namedb
1138f1bb389SDoug Barton	cp -Rp namedb.bak/* /var/named/etc/namedb/
1148f1bb389SDoug Barton	mergemaster (with your usual options)
1158f1bb389SDoug Barton	If using the generated localhost* files:
1168f1bb389SDoug Barton		cd /var/named/etc/namedb
1178f1bb389SDoug Barton		/bin/sh make-localhost
1188f1bb389SDoug Barton		rm -f localhost-v6.rev localhost.rev
119cfeb1f52SDoug Barton	/etc/rc.d/syslogd restart
1208f1bb389SDoug Barton	/etc/rc.d/named start
1218f1bb389SDoug Barton
1228f1bb389SDoug Barton	If you are using a custom configuration, or if you have
1238f1bb389SDoug Barton	customised the named_* variables in /etc/rc.conf[.local]
1248f1bb389SDoug Barton	then you may have to adjust the instructions accordingly.
1258f1bb389SDoug Barton	It is suggested that you carefully examine the new named
1268f1bb389SDoug Barton	variables in /etc/defaults/rc.conf and the options in
1278f1bb389SDoug Barton	/var/named/etc/namedb/named.conf to see if they might
1288f1bb389SDoug Barton	now be more suitable.
1298f1bb389SDoug Barton
1305d36721aSDoug Barton20040925:
1315d36721aSDoug Barton	BIND 9 has been imported into the base, and is now fully
1325d36721aSDoug Barton	functional. BIND 8 has now been removed. There are numerous
1335d36721aSDoug Barton	differences between BIND 8 and 9, and users with critical
1345d36721aSDoug Barton	named installations should read the migration documentation
1355d36721aSDoug Barton	in /usr/share/doc/bind9/misc/migration. There is also a
1365d36721aSDoug Barton	new instruction manual in /usr/share/doc/bind9/arm.
1375d36721aSDoug Barton
1385d36721aSDoug Barton	The key differences that most users will experience are in
1395d36721aSDoug Barton	how picky BIND 9 is about zone file format. If you are using
1405d36721aSDoug Barton	named as a resolving (caching) name server, you will likely
1415d36721aSDoug Barton	not have trouble.
1425d36721aSDoug Barton
143f50b1bdbSDoug Barton	The following files are part of the old BIND 8 installation
144f50b1bdbSDoug Barton	and should be removed:
145f50b1bdbSDoug Barton	/usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
146f50b1bdbSDoug Barton	/usr/sbin/named.restart /usr/sbin/ndc
147f50b1bdbSDoug Barton
148f50b1bdbSDoug Barton	The following files have moved to /usr/bin, and should be
149f50b1bdbSDoug Barton	removed from their old locations:
150f50b1bdbSDoug Barton	/usr/sbin/nslookup /usr/sbin/nsupdate
151f50b1bdbSDoug Barton
152f5ee5a8bSMax Laier20040914:
153f5ee5a8bSMax Laier	The format of the pflogd(8) logfile "/var/log/pflog" has changed for
154f5ee5a8bSMax Laier	architectures that have a 64 bit long type to make it compatible to
155f5ee5a8bSMax Laier	the standard pcap format. In order to prevent corruption move away
156f5ee5a8bSMax Laier	any old logfile before using a new pflogd(8).
157f5ee5a8bSMax Laier
158d698cdb3SJohn-Mark Gurney20040906:
159d698cdb3SJohn-Mark Gurney	debug.witness_* has been renamed to debug.witness.*.  There are
160d698cdb3SJohn-Mark Gurney	compatibility tunables left in for a few days.  Update loader.conf
161d698cdb3SJohn-Mark Gurney	as necessary.
162d698cdb3SJohn-Mark Gurney
1634ff62bd9SBrooks Davis20040902:
1644ff62bd9SBrooks Davis	The ifi_epoch change has been reverted because the ABI breakage
1654ff62bd9SBrooks Davis	was too extensive.  If you are running with a kernel/userland
1664ff62bd9SBrooks Davis	containing the initial change (20040830), you should heed the
1674ff62bd9SBrooks Davis	warning about ifconfig incompatibility when upgrading again.
1684ff62bd9SBrooks Davis	With this change, 5.3 and 6.0 ifconfigs and kernels are once
1694ff62bd9SBrooks Davis	again interoperable.
1704ff62bd9SBrooks Davis
1711fc4519bSBrooks Davis20040830:
1721fc4519bSBrooks Davis	A new variable, ifi_epoch, has been added to struct if_data
1731fc4519bSBrooks Davis	which is part if struct ifnet.  This means all network drivers
1741fc4519bSBrooks Davis	and network monitoring applications need to be recompiled.
1751fc4519bSBrooks Davis
1763789fb75SBrooks Davis        WARNING WARNING WARNING WARNING WARNING WARNING WARNING
1773789fb75SBrooks Davis
1783789fb75SBrooks Davis        This also breaks ifconfig compatibility.  An old ifconfig will
1793789fb75SBrooks Davis        not work with the new kernel and a new ifconfig will not work
1803789fb75SBrooks Davis        with the old.  It is strongly recommended that you make a copy
1813789fb75SBrooks Davis        of your old ifconfig before installworld.  If you are installing
1823789fb75SBrooks Davis        remotely, you must copy over a new ifconfig before rebooting in
1833789fb75SBrooks Davis        to the new kernel.
1843789fb75SBrooks Davis
185c1c94d5cSRobert Watson20040828:
186c1c94d5cSRobert Watson	The default configuration for the network stack has been changed
187c1c94d5cSRobert Watson	such that it now runs without the Giant lock unless configured
188c1c94d5cSRobert Watson	otherwise.  If you experience network-related instability, you
189c1c94d5cSRobert Watson	may wish to try setting "debug.mpsafenet=0" or compiling the
190c1c94d5cSRobert Watson	kernel with "options NET_WITH_GIANT".  Details on the netperf
191c1c94d5cSRobert Watson	project may be found at:
192c1c94d5cSRobert Watson
193c1c94d5cSRobert Watson	    http://www.watson.org/~robert/freebsd/netperf/
194c1c94d5cSRobert Watson
195c1c94d5cSRobert Watson	Including the 20040828 announcement of configuration change
196c1c94d5cSRobert Watson	details.
197c1c94d5cSRobert Watson
198c21fd232SAndre Oppermann20040827:
199c21fd232SAndre Oppermann	PFIL_HOOKS are a fixed part of the network stack now and do not
200c21fd232SAndre Oppermann	need to be specified in the kernel configuration file anymore.
201c21fd232SAndre Oppermann
202f036d408SJulian Elischer20040819:
203f036d408SJulian Elischer	Netgraph changed its message format slightly to align the data
204f036d408SJulian Elischer	portion well on 64 bit machines.
205f036d408SJulian Elischer	Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
206f036d408SJulian Elischer	pppoed, bluetooth, ATM) should be recompiled when a new kernel
207f036d408SJulian Elischer	is installed.
208f036d408SJulian Elischer
209b067abfaSAndre Oppermann20040817:
210b05bb3e7SMax Laier	IPFW has been converted to use pfil(9).  This change is
211b067abfaSAndre Oppermann	transparent to userland and preserves the ipfw ABI.  The ipfw
212b067abfaSAndre Oppermann	core packet inspection and filtering functions have not been
213b05bb3e7SMax Laier	changed, only how ipfw is invoked is different.
214b067abfaSAndre Oppermann
215f13a7951SDavid Malone20040814:
216f13a7951SDavid Malone	The RANDOM_IP_ID option has been replaced by the sysctl
217f13a7951SDavid Malone	net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
218f13a7951SDavid Malone	you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
219f13a7951SDavid Malone
2203a004637SMax Laier20040807:
2213a004637SMax Laier	The size of 'struct ifnet' has changed due to the addition of the
2223a004637SMax Laier	if_carp placeholder.  All kernel modules implementing network
2233a004637SMax Laier	interfaces must be recompiled as a result.
2243a004637SMax Laier
2254f34d8d1SJohn-Mark Gurney20040806:
2264f34d8d1SJohn-Mark Gurney	Module loading has been fixed.  Some older installations will
227ac41c814SRuslan Ermilov	drop proper module_path initialization and modules will fail to
2284f34d8d1SJohn-Mark Gurney	load properly.  If you have a line in /boot/loader.rc that says:
2294f34d8d1SJohn-Mark Gurney	"initialize drop", do (i386 only):
2304f34d8d1SJohn-Mark Gurney		cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
2314f34d8d1SJohn-Mark Gurney		chown root:wheel /boot/loader.rc
2324f34d8d1SJohn-Mark Gurney		chmod 444 /boot/loader.rc
2334f34d8d1SJohn-Mark Gurney
2348f075db4SMark Murray20040802:
2358f075db4SMark Murray	making /dev/(null|zero) into a module proved to be too unpopular,
2368f075db4SMark Murray	so this bit has been revoked from the previous (20040801) entry.
2378f075db4SMark Murray
238d064d6dbSMark Murray20040801:
239d064d6dbSMark Murray	The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
240d064d6dbSMark Murray	so you may wish to add them to your kernel config file. See
241d064d6dbSMark Murray	GENERIC for examples.
242d064d6dbSMark Murray
243b289983eSAlexander Kabaev20040728:
24454bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
24554bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
24654bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
24754bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
248d0e54ab4SDavid E. O'Brien	compiler. If you are getting run-time error such as
249d0e54ab4SDavid E. O'Brien	/libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
250d0e54ab4SDavid E. O'Brien	This entry does apply to you.
251d0e54ab4SDavid E. O'Brien
252d0e54ab4SDavid E. O'Brien	A new unit-at-a-time optimization mode, which is default in this
253d0e54ab4SDavid E. O'Brien	compiler release, is more aggressive in removing unused static
254d0e54ab4SDavid E. O'Brien	symbols. This is the likely cause of 'make buildworld' breakages
255cd5f061cSWarner Losh	with non-default CFLAGS where optimization level is set to -O2
256cd5f061cSWarner Losh	or higher.
25754bd5271SAlexander Kabaev
2586e1afae3SWarner Losh	With the upgrade of the system compiler, the kernel has been upgraded
2596e1afae3SWarner Losh	to match the new system compiler.  This makes it impossible to build
2606e1afae3SWarner Losh	a new kernel with the old compiler.  Upgrade your system via
2616e1afae3SWarner Losh	make buildworld and make kernel (see below) to fix this problem.
2626e1afae3SWarner Losh
26336ed21e6SRobert Watson20040727:
26436ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
26536ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
26636ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
26736ed21e6SRobert Watson	a result.
26836ed21e6SRobert Watson
2696305ac24SSeigo Tanimura20040716:
2706305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
2716305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
2726305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
2736305ac24SSeigo Tanimura
274e623dcb7SMarcel Moolenaar20040710:
275e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
276e623dcb7SMarcel Moolenaar
277e623dcb7SMarcel Moolenaar20040710:
278e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
279e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
280e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
281e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
282e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
283e623dcb7SMarcel Moolenaar	of this.
284e623dcb7SMarcel Moolenaar
285e623dcb7SMarcel Moolenaar20040710:
286e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
287e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
288e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
289e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
290e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
291e623dcb7SMarcel Moolenaar	   option for this.
292e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
293e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
294e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
295e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
2965bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
297e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
298e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
299e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
300e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
301e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
302e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
303e623dcb7SMarcel Moolenaar
3046421d1dbSMaksim Yevmenkin20040708:
3056421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
3066421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
3076421d1dbSMaksim Yevmenkin
30858af3216SWarner Losh20040702:
30958af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
3105bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
3115bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
3125bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
31358af3216SWarner Losh	scheduler as a workaround.
31458af3216SWarner Losh
315c2dba668SNate Lawson20040630:
3168ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
3178ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
318a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
319a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
320a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
321a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
322a6c26e1cSBruce M Simpson	example of such changes.
3238ed370fdSJulian Elischer
32458af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
32558af3216SWarner Losh	over.
32658af3216SWarner Losh
3278ed370fdSJulian Elischer20040630:
328c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
3295bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
330c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
331c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
332c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
333c2dba668SNate Lawson	loader prompt.
334c2dba668SNate Lawson
3358ee2ac9eSMax Laier20040623:
3365bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
3378ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
3388ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
3398ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
3408ee2ac9eSMax Laier
3413db5687dSBrooks Davis20040622:
3423db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
3433db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
3443db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
3453db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
3463db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
3473db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
3483db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
3493db5687dSBrooks Davis
350e0ae81f3SDag-Erling Smørgrav20040621:
351e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
352e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
353e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
354e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
355e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
356e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
357e0ae81f3SDag-Erling Smørgrav	during the next reboot.
358e0ae81f3SDag-Erling Smørgrav
3594717d22aSJohn Polstra20040614:
3604717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
3614717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
3624717d22aSJohn Polstra	the ips module and any third-party modules which call
3634717d22aSJohn Polstra	sema_timedwait.
3644717d22aSJohn Polstra
3656cb7a382SMax Laier20040613:
3666cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
3676cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
368df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
369df843493SMax Laier	please recompile and reinstall world.
3706cb7a382SMax Laier
3712454685eSJulian Elischer20040607:
3722454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
3732454685eSJulian Elischer	requires that you re-run config after updating your tree.
3742454685eSJulian Elischer
37564fef830SSeigo Tanimura20040601:
37664fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
37764fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
37864fef830SSeigo Tanimura	kernel configuration.
37964fef830SSeigo Tanimura
380bb4f06e7SAndre Oppermann20040423:
381bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
382bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
383bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
384bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
385bb4f06e7SAndre Oppermann
38605641e82SColin Percival20040420:
38705641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
38805641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
38905641e82SColin Percival	20040406.
39005641e82SColin Percival
391d0dc9183SWarner Losh20040414:
392d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
393d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
394d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
395d0dc9183SWarner Losh
396d0dc9183SWarner Losh20040412:
397d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
398d0dc9183SWarner Losh	drive is still broken.
399d0dc9183SWarner Losh
400d0dc9183SWarner Losh20040410:
401d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
402d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
403d0dc9183SWarner Losh	the unanticipated problems have been resolved.
404d0dc9183SWarner Losh
4058633bbeaSBrooks Davis20040409:
4068633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
4078633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
4088633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
4098633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
41076c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
4118633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
4128633bbeaSBrooks Davis
413d40d033aSRobert Watson20040322:
414d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
415d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
416d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
417d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
418d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
419d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
420d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
421d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
422d40d033aSRobert Watson	locking is merged to permit this to take place.
423d40d033aSRobert Watson
424ec9b318eSGarance A Drosehn20040310:
425ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
426ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
427ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
428ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
429ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
430ec9b318eSGarance A Drosehn
431fc28f1ffSMax Laier20040308:
432fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
433fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
4344c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
4354c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
436b05bb3e7SMax Laier	The pf system consists of the following three devices:
437fc28f1ffSMax Laier	device		pf		# required
438fc28f1ffSMax Laier	device		pflog		# optional
439fc28f1ffSMax Laier	device		pfsync		# optional
440fc28f1ffSMax Laier
4413aff5d06SDag-Erling Smørgrav20040303:
4423aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
4433aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
4443aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
4453aff5d06SDag-Erling Smørgrav
4463aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
4473aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
4483aff5d06SDag-Erling Smørgrav
4493aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
4503aff5d06SDag-Erling Smørgrav	to use libpthread instead.
4513aff5d06SDag-Erling Smørgrav
452fd63c5b3SDag-Erling Smørgrav20040226:
4539d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
454fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
455fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
456fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
457fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
458fd63c5b3SDag-Erling Smørgrav
459714ae42aSBruce M Simpson20040225:
460e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
461e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
462e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
463e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
464e07a40f3SBrian Feldman	should remain unaffected.
465e07a40f3SBrian Feldman
466e07a40f3SBrian Feldman20040225:
467714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
468714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
469714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
470714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
471714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
472714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
473714ae42aSBruce M Simpson
474fbd2e692SAndre Oppermann20040224:
475fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
4765bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
477fbd2e692SAndre Oppermann
478158b90daSWarner Losh20040222:
479158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
480158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
481158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
482158b90daSWarner Losh	Drivers outside the tree will need to be updated.
483158b90daSWarner Losh
484b7b1e150SMike Makonnen20040207:
485b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
486b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
487b7b1e150SMike Makonnen
488aca89ee6SDaniel Eischen20040130:
489aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
490aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
491aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
492aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
493aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
494aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
495aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
496aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
497aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
498aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
499aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
500aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
501aca89ee6SDaniel Eischen	do not work with libpthread.
502aca89ee6SDaniel Eischen
50368b7b3a9SAlex Dupre20040125:
50468b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
50568b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
50668b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
50768b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
50868b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
50968b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
51068b7b3a9SAlex Dupre
511ff46e0deSWarner Losh20040125:
512ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
513ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
514ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
515ff46e0deSWarner Losh
516ce41f4bfSRobert Watson20031213:
517ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
518ce41f4bfSRobert Watson	if the login process is unable to successfully set the
519ce41f4bfSRobert Watson	process credentials to include all groups defined for the
520ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
521ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
522ce41f4bfSRobert Watson	defined, or they will be unable to log in.
523ce41f4bfSRobert Watson
524c124fa05SJohn Baldwin20031203:
525c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
526c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
527c124fa05SJohn Baldwin
5288ad1f5e4SHartmut Brandt20031112:
52930093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
53030093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
53197209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
53297209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
53397209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
53497209ca3SRobert Watson	not know about the new system calls that support the new statfs
5353f631d52SMarcel Moolenaar	structure.
5363f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
5373f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
5383f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
5393f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
5403f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
5413f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
5423f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
5433f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
5443f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
5453f631d52SMarcel Moolenaar	these changes are installed.
54630093b05SWarner Losh
54730093b05SWarner Losh	****************************DANGER*******************************
54830093b05SWarner Losh
54930093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
55030093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
55130093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
55230093b05SWarner Losh	kernel.
55364a18d6fSKirk McKusick
55464a18d6fSKirk McKusick20031112:
5558ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
5568ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
5578ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
5588ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
5598ad1f5e4SHartmut Brandt	sync before rebooting.
5608ad1f5e4SHartmut Brandt
561c53a5d8fSJohn Baldwin20031111:
562c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
563c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
564c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
565c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
566c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
567c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
568c53a5d8fSJohn Baldwin
5698bf455a5SJohn Baldwin20031103:
5708bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
5718bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
5722a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
5738bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
5748bf455a5SJohn Baldwin
5759bf40edeSBrooks Davis20031031:
5769bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
5779bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
5789bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
5799bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
5809bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
5819bf40edeSBrooks Davis	reflect this change.
5829bf40edeSBrooks Davis
58347a42c7aSPoul-Henning Kamp20030928:
58447a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
58547a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
5865bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
58747a42c7aSPoul-Henning Kamp
58807105342SMax Khon20030926:
58907105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
59007105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
59107105342SMax Khon
592fedf1d01SBruce M Simpson20030923:
593fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
594fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
595fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
596fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
597fedf1d01SBruce M Simpson
598db38f9cbSJacques Vidrine20030915:
599db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
600db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
601db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
602db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
603db38f9cbSJacques Vidrine
604c09d2c2bSMike Makonnen20030829:
605c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
606c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
607c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
608c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
609c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
610c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
611c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
612c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
613c09d2c2bSMike Makonnen	may or may not exist on your system.
614c09d2c2bSMike Makonnen
61517c159dcSSøren Schmidt20030824:
61617c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
61717c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
618f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
619f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
62017c159dcSSøren Schmidt
621c1f61aa9SDavid E. O'Brien20030819:
622c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
623c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
624c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
625c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
62669f7bcf3SWarner Losh
62738c962e7SNate Lawson20030728:
62838c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
62938c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
63038c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
63138c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
63238c962e7SNate Lawson	so the quirk can be re-enabled.
63338c962e7SNate Lawson
63474111097SWarner Losh20030724:
63574111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
63674111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
63774111097SWarner Losh
638178cf4e9SWarner Losh20030722:
639178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
640178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
641178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
642178cf4e9SWarner Losh	FPU hardware.
643178cf4e9SWarner Losh
644178cf4e9SWarner Losh20030714:
645178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
646178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
647178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
648178cf4e9SWarner Losh	People should report those issues to current@.
649178cf4e9SWarner Losh
650157c629aSWarner Losh20030711:
651157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
6528b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
65305538fa9SWarner Losh	/usr/obj.
654157c629aSWarner Losh
65574111097SWarner Losh20030610:
65674111097SWarner Losh	Remove deprecated locale names and transition period code
65774111097SWarner Losh	for them, finishing switching to the new scheme. Check your
65874111097SWarner Losh	LANG environment variable.
65974111097SWarner Losh
66074111097SWarner Losh20030609:
66174111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
66274111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
66374111097SWarner Losh	important to remember beforehand if your source tree is on
66474111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
66574111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
66674111097SWarner Losh	kernel.
66774111097SWarner Losh
66874111097SWarner Losh20030605:
6696cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
6706cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
6716cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
6726cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
6736cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
6746cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
6756cc6353fSMarcel Moolenaar
6766cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
6776cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
6786cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
6796cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
6806cc6353fSMarcel Moolenaar		:
6816cc6353fSMarcel Moolenaar
6826cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
6836cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
6846cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
6856cc6353fSMarcel Moolenaar
68652b47445SMark Murray20030505:
68752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
68852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
68952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
69052b47445SMark Murray
691a26df538SWarner Losh20030502:
692a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
693a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
694a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
695a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
696a26df538SWarner Losh
6974b065e2cSDoug Barton20030501:
6984b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
6994b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
7004b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
7014b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
7024b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
7034b065e2cSDoug Barton	utilizes these old scripts has also been removed.
7044b065e2cSDoug Barton
70581cda3d9SWarner Losh20030423:
70681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
70781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
70881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
70981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
71081cda3d9SWarner Losh	userland.  In general, you should have a userland and
71181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
71281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
71381cda3d9SWarner Losh	allowances are made.
71481cda3d9SWarner Losh
71547a657d1SRuslan Ermilov20030329:
71647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
71747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
71847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
71947a657d1SRuslan Ermilov
72047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
72147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
72247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
72347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
72447a657d1SRuslan Ermilov
72547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
72647a657d1SRuslan Ermilov	    make cleandir && make obj && \
72747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
72847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
72947a657d1SRuslan Ermilov
7305d2af00cSGregory Neil Shapiro20030208:
7315d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
7325d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
7335d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
7345d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
7355d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
7365d2af00cSGregory Neil Shapiro
7375d2af00cSGregory Neil Shapiro20030128:
7389db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
739ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
7409db58771SPoul-Henning Kamp	be removed when convenient.
7419db58771SPoul-Henning Kamp
7428d9b3f57SJake Burkholder20030126:
7438d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
7448d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
7458d9b3f57SJake Burkholder
7461c5efda5SJeff Roberson20030125:
7471c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
7481c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
749ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
7501c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
7511c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
7521c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
7531c5efda5SJeff Roberson
7549d1d64f5SWarner Losh20030115:
7559d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
7569d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
7579d1d64f5SWarner Losh	properly.
7589d1d64f5SWarner Losh
759c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
760c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
761c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
762c9fdb80aSWarner Losh	with NetBSD.
763c9fdb80aSWarner Losh
764161dc364SAlexander Kabaev20021222:
765161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
766161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
767161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
768161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
769161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
770161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
77184cc83efSAlexander Kabaev	rebuilt.
772161dc364SAlexander Kabaev
773fb4c8061SMartin Blapp20021216:
774fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
77589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
776fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
7779d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
778fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
779fb4c8061SMartin Blapp
78017d47eb3SGiorgos Keramidas20021202:
78117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
78217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
78317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
78417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
78517d47eb3SGiorgos Keramidas
786a4459294SBill Fenner20021029:
787a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
788a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
789a4459294SBill Fenner	consumers in sync.
790a4459294SBill Fenner
791fc8c157fSWarner Losh20021024:
792c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
793c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
794c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
795c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
796c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
797c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
798c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
799c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
80069f7bcf3SWarner Losh
801fd9e8bdaSAndrew Gallatin20021023:
802fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
803fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
804fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
805fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
806fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
807fd9e8bdaSAndrew Gallatin
808fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
809fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
810fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
811fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
812fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
813fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
814fd9e8bdaSAndrew Gallatin
815f8a4c901SWarner Losh20020831:
816f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
817f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
818f8a4c901SWarner Losh	programs and libraries need to be recompiled.
819f8a4c901SWarner Losh
820f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
821f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
822f8a4c901SWarner Losh
823c2248fa2SJens Schweikhardt20020827:
824c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
825c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
826c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
827c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
828c2248fa2SJens Schweikhardt
8290d533e43SRuslan Ermilov20020815:
8300d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
8310d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
8320d533e43SRuslan Ermilov	again.
8330d533e43SRuslan Ermilov
83433c1de7dSRuslan Ermilov20020729:
83533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
83633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
83733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
83833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
83933c1de7dSRuslan Ermilov
8402b877facSJulian Elischer20020702:
8412b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
8422b877facSJulian Elischer	There are still some minor problems with some signals but the
8432b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
8442b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
8452b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
8462b877facSJulian Elischer
84706596d37SWarner Losh20020701:
84806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
84906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
85006596d37SWarner Losh	GNOME.
85106596d37SWarner Losh
85295ba4330SJacques Vidrine20020511:
85395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
85495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
85595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
85695ba4330SJacques Vidrine	with the set-user-ID bit set.
85795ba4330SJacques Vidrine
858a81da3c9SDavid E. O'Brien20020510:
859f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
860f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
8614b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
862f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
863f50caf6fSDavid E. O'Brien
864f50caf6fSDavid E. O'Brien20020510:
865a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
866a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
867a81da3c9SDavid E. O'Brien	and then do a cvs update.
868a81da3c9SDavid E. O'Brien
869528a0ef5SJacques Vidrine20020421:
870528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
871528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
872528a0ef5SJacques Vidrine
87385aa5a2eSGregory Neil Shapiro20020404:
87485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
87585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
87685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
87785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
87885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
87985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
88085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
88185aa5a2eSGregory Neil Shapiro
8828f1e4358SRuslan Ermilov20020403:
8838f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
8848f1e4358SRuslan Ermilov
8852292c02eSWarner Losh20020315:
8862292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
8872292c02eSWarner Losh
88869f7bcf3SWarner Losh20020225:
88969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
89069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
89169f7bcf3SWarner Losh
8928f35c493SWarner Losh20020217:
8938f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
8948f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
8958f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
8968f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
8978f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
8988f35c493SWarner Losh
899835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
900835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
901835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
902835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
903835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
904835284beSWarner Losh	and group must be merged from src/etc/group and
905835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
906835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
907835284beSWarner Losh	mergemaster before this will work if you are updating from a
908835284beSWarner Losh	very old version of current.  The updating recipe has changed
909835284beSWarner Losh	as of this date.
910835284beSWarner Losh
911fa9401c1SWarner Losh20020112:
912fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
913fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
914fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
915fa9401c1SWarner Losh	you have local modifications, you can use
916fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
917fa9401c1SWarner Losh	/etc/pam.d.
918fa9401c1SWarner Losh
919fa9401c1SWarner Losh	Please see the following url for more details:
920fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
92147d0d01fSWarner Losh20011229:
92247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
92347d0d01fSWarner Losh	networkfs_types, please note that it has changed
92447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
92547d0d01fSWarner Losh
926514318a8SWarner Losh20011220:
927514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
928514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
929514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
930514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
931514318a8SWarner Losh	version have now been merged back into the base system's
932514318a8SWarner Losh	version now.  The only user-visible change resulting from this
933514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
934514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
935514318a8SWarner Losh	as well.  (There has never been rc file support for
936514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
937514318a8SWarner Losh	reverted by the time the changes are MFCed.)
938514318a8SWarner Losh
939514318a8SWarner Losh20011215:
940514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
941514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
942514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
943514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
944514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
945514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
946514318a8SWarner Losh	will need to be customized then for `odd' densities using
947514318a8SWarner Losh	fdcontrol(8).
948514318a8SWarner Losh
9492d22e2bfSWarner Losh20011209:
9502d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
9512d22e2bfSWarner Losh	and truss(1) now works again.
9522d22e2bfSWarner Losh
9539e0428e2SWarner Losh20011207:
9549e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
9559e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
9569e0428e2SWarner Losh	see
9579e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
9589e0428e2SWarner Losh	for details.
9599e0428e2SWarner Losh
9609bab8c59SWarner Losh20011204:
9619bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
9629bab8c59SWarner Losh	kernel and burncd to be in sync.
9639bab8c59SWarner Losh
964e57d8b01SWarner Losh20011203:
965e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
966e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
967e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
968e57d8b01SWarner Losh	not there already.
969e57d8b01SWarner Losh
970e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
971e57d8b01SWarner Losh	until the issue has been resolved.
972e57d8b01SWarner Losh
973b001d36fSJacques Vidrine20011202:
974b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
975b001d36fSJacques Vidrine	patched.
976b001d36fSJacques Vidrine
9774b676ec1SWarner Losh20011126:
9784b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
9795ebbf43eSWarner Losh	after this date.  You need to do this only once.
9804b676ec1SWarner Losh
981d961e462SWarner Losh20011103:
982d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
983d961e462SWarner Losh	edges may be left, but for the most part things should be
9844b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
985d961e462SWarner Losh
986d961e462SWarner Losh20011030:
987d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
988d961e462SWarner Losh	choppy waves in the upgrade process.
989d961e462SWarner Losh
9901fe003b6SWarner Losh20011030:
991a4b6fda0SWarner Losh	The asr driver problem has been resolved.
9921fe003b6SWarner Losh
9931fe003b6SWarner Losh20011027:
9941fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
9951fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
9961fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
9971fe003b6SWarner Losh	try to use from this date forward.
9981fe003b6SWarner Losh
9991fe003b6SWarner Losh20011025:
10001fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
10011fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
10021fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
10031fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
10041fe003b6SWarner Losh	TARGET_ARCH=i386.
10051fe003b6SWarner Losh
1006d05f9643SWarner Losh20011001:
1007d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
1008d05f9643SWarner Losh	You must recompile both the kernel and userland applications
1009d05f9643SWarner Losh	at the same time.
1010d05f9643SWarner Losh
101158970f85SWarner Losh20010929:
101258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
101358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
101458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
101558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
10169d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
101758970f85SWarner Losh
101858970f85SWarner Losh20010927:
101958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
102058970f85SWarner Losh	To disable ACPI you can add
102166ff0e67SMax Khon		hint.acpi.0.disabled="1"
102258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
102358970f85SWarner Losh	loader "ok" prompt).
102458970f85SWarner Losh
102558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
102658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
102758970f85SWarner Losh	file and not list acpi in that list.
1028378f4486SAlfred Perlstein
10295119d237SWarner Losh20010924:
10305119d237SWarner Losh	The buildworld has been fixed.  You may need to install
10315119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
10328b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
10338b039fffSWarner Losh	get them installed on every installworld, or execute the
10348b039fffSWarner Losh	following to get them installed only once:
10358b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
103658970f85SWarner Losh		make all install
10378b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
10385119d237SWarner Losh
10393c293725SWarner Losh20010919:
10403c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
10413c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
10423c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
1043772730c7SWarner Losh	workaround is to add
10443c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
10453c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
10463c293725SWarner Losh	can be removed afterwards.
10473c293725SWarner Losh
10483c293725SWarner Losh	A proper fix to the buildworld target is needed.
10493c293725SWarner Losh
10503c293725SWarner Losh20010918:
10513c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
10523c293725SWarner Losh	NFS may be unstable after this date.
10533c293725SWarner Losh
10543c293725SWarner Losh20010912:
10553c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
10563c293725SWarner Losh	the kernel.  While a few problems were introduced in the
10573c293725SWarner Losh	initial commit, most of the major ones have been found and
10583c293725SWarner Losh	corrected.
10593c293725SWarner Losh
10603c293725SWarner Losh20010901:
10613c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
10623c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
10633c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
10643c293725SWarner Losh	have been rectified around this date.
10653c293725SWarner Losh
106698b17b95SWarner Losh20010823:
106798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
106898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
106998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
107098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
107198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
107298b17b95SWarner Losh 	permission for your name server configuration and that it
107398b17b95SWarner Losh 	has read and write permission for your slave zone files and
107498b17b95SWarner Losh 	directory.
107598b17b95SWarner Losh
107698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
107798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
107898b17b95SWarner Losh
107998b17b95SWarner Losh 		named_flags=
108098b17b95SWarner Losh
10817b9786edSMark Murray20010709:
10827b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
10837b9786edSMark Murray	the ability of the shared library major number to handle.
10847b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
10857b9786edSMark Murray	solution is to rebuild those ports.
10867b9786edSMark Murray
10871d28950eSWarner Losh20010628:
10881d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
10891d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
10901d28950eSWarner Losh
1091e72fd46aSWarner Losh20010625:
109298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
109398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
109498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
109598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
109698b17b95SWarner Losh	IRQ configuration needs more safety belts.
109716de1a07SWarner Losh
10980d415dffSWarner Losh20010617:
1099e72fd46aSWarner Losh	Softupdates problems have been corrected.
11000d415dffSWarner Losh
11010d415dffSWarner Losh20010614:
11020d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
11030d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
11040d415dffSWarner Losh	kernel building methods.
11050d415dffSWarner Losh
11068b9959adSWarner Losh20010613:
11078b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
11088b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
1109e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
1110e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
11118b9959adSWarner Losh
1112e72fd46aSWarner Losh20010613:
11138b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
1114e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
1115e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
11168b9959adSWarner Losh
11170d415dffSWarner Losh20010612:
11180d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
11190d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
11200d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
11210d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
11220d415dffSWarner Losh	until this bug is fixed.
11230d415dffSWarner Losh
1124e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
1125e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
1126ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
1127e72fd46aSWarner Losh
11280d415dffSWarner Losh20010610:
11290d415dffSWarner Losh	Locale names have changed to match other systems better.
11300d415dffSWarner Losh
11316ccdb5e4SWarner Losh20010604:
11326ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
11336ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
11346ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
11353590182eSWarner Losh	Interrupt storms look a lot like a hang.
11363590182eSWarner Losh
11373590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
11383590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
11393590182eSWarner Losh	it is).
11403590182eSWarner Losh
11413590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
11423590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
11433590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
11443590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
11456ccdb5e4SWarner Losh
11460bc62786SWarner Losh20010530:
11470bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
11480bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
11490bc62786SWarner Losh	a limited time.  If you see
11500bc62786SWarner Losh
11510bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
11520bc62786SWarner Losh
11530bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
11540bc62786SWarner Losh	COPY=-C.
11550bc62786SWarner Losh
115668a38c6cSWarner Losh20010525:
1157b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
1158c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
1159c4f4a728SWarner Losh	definitely is in bad shape.
116068a38c6cSWarner Losh
1161ed0f29caSWarner Losh20010521:
1162ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
1163ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
1164ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1165ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
1166ed0f29caSWarner Losh	is
1167ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1168ed0f29caSWarner Losh
116980c16af9SWarner Losh20010520:
117068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
117180c16af9SWarner Losh
117280c16af9SWarner Losh20010519:
117380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
117480c16af9SWarner Losh	the past few days.  Everything should still work, but if
117580c16af9SWarner Losh	not, please contact imp@freebsd.org.
117680c16af9SWarner Losh
1177a45f2d05SWarner Losh20010517:
1178a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
1179a45f2d05SWarner Losh	userland at the same time.
1180a45f2d05SWarner Losh
1181a45f2d05SWarner Losh20010517:
1182a45f2d05SWarner Losh	New ncurses imported.
1183a45f2d05SWarner Losh
11842988afcaSWarner Losh20010512:
11852988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
11862988afcaSWarner Losh	will be the only way to go starting July 1.
11872988afcaSWarner Losh
11881a33dba7SWarner Losh20010504:
11891a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
11901a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
11911a33dba7SWarner Losh
119209946a51SWarner Losh20010502:
119309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
119409946a51SWarner Losh
119509946a51SWarner Losh20010501:
119609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
119709946a51SWarner Losh
119809946a51SWarner Losh20010430:
1199a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
120009946a51SWarner Losh	go back in the water.
120109946a51SWarner Losh
120209946a51SWarner Losh20010429:
120309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
120409946a51SWarner Losh	this date, but before the correction date.
120509946a51SWarner Losh
120691dd3b53SWarner Losh20010423:
120791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
120891dd3b53SWarner Losh
120991dd3b53SWarner Losh20010411:
121091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
121191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
121291dd3b53SWarner Losh	Update only if you understand that you must not use the old
121391dd3b53SWarner Losh	fsck with the new kernel ever.
121491dd3b53SWarner Losh
1215933b3269SWarner Losh20010330:
1216933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1217c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1218933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1219933b3269SWarner Losh
1220933b3269SWarner Losh20010319:
1221933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1222933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1223933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1224f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
122509946a51SWarner Losh
122609946a51SWarner Losh20010315:
122709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1228ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
122909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1230933b3269SWarner Losh
1231933b3269SWarner Losh20010312:
1232933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1233933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1234933b3269SWarner Losh
1235933b3269SWarner Losh20010312:
1236933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1237933b3269SWarner Losh	instead of ad-hoc.
1238933b3269SWarner Losh
1239933b3269SWarner Losh20010310:
1240f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1241933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1242933b3269SWarner Losh	ssh might not work if you don't.
1243933b3269SWarner Losh
124462353691SWarner Losh20010303:
124562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
124662353691SWarner Losh	which means that you must include the miibus in your kernel if
124762353691SWarner Losh	you use the ed driver.
124862353691SWarner Losh
1249d325cf65SWarner Losh20010220:
1250d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1251d325cf65SWarner Losh	safe to go back into the water.
1252d325cf65SWarner Losh
1253024daae6SWarner Losh20010211:
1254024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1255024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1256024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1257024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1258024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1259024daae6SWarner Losh
1260024daae6SWarner Losh	To get to the new system, you'll need to use the following
1261024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1262024daae6SWarner Losh	don't have to move this to the updating section.
1263024daae6SWarner Losh
1264024daae6SWarner Losh	To get around the installworld problem, do:
1265024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1266024daae6SWarner Losh		# make install
1267024daae6SWarner Losh		# cd /usr/src
1268024daae6SWarner Losh		# make installworld
1269024daae6SWarner Losh	If that doesn't work, then try:
1270024daae6SWarner Losh		# make -k installworld
1271024daae6SWarner Losh		# make installworld
1272024daae6SWarner Losh
1273024daae6SWarner Losh20010207:
1274024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1275024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1276024daae6SWarner Losh
1277024daae6SWarner Losh20010205:
12787595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1279024daae6SWarner Losh	Remove them from your config.
1280024daae6SWarner Losh
12811e159248SWarner Losh20010122:
12821e159248SWarner Losh	****************************** WARNING ******************************
12831e159248SWarner Losh			buildkernel has been changed slightly
12841e159248SWarner Losh	****************************** WARNING ******************************
12851e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
12861e159248SWarner Losh	should update your scripts and make.conf accordingly.
12871e159248SWarner Losh
12881e159248SWarner Losh20010119:
12891e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
12901e159248SWarner Losh	This requires a new config to build correctly.
12911e159248SWarner Losh
1292aac7dfeaSWarner Losh20010116:
1293ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1294aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1295aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1296aac7dfeaSWarner Losh
1297aac7dfeaSWarner Losh20010110:
1298aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1299aac7dfeaSWarner Losh
1300aac7dfeaSWarner Losh20010102:
1301aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1302aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1303aac7dfeaSWarner Losh
130463c90c9eSWarner Losh20010101:
130563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
130663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
13075fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
130863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
130963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
131063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
131163c90c9eSWarner Losh	might have been ignored by the -k option.
131263c90c9eSWarner Losh
13135fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
13145fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
13155fd2a895SWarner Losh	of this working.
13165fd2a895SWarner Losh
1317aac7dfeaSWarner Losh20001228:
1318aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1319ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1320aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1321aac7dfeaSWarner Losh
1322de2bcc63SWarner Losh20001218:
1323de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1324de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1325de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1326de2bcc63SWarner Losh	cards will not be recognized without it.
1327de2bcc63SWarner Losh
1328960773f7SWarner Losh20001205:
1329960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1330960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1331960773f7SWarner Losh	adding the following in pam.conf:
1332960773f7SWarner Losh
1333960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1334960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1335960773f7SWarner Losh	sshd    session required        pam_permit.so
1336960773f7SWarner Losh
13370acc635eSWarner Losh20001031:
13380acc635eSWarner Losh	cvs updated to 1.11.
13390acc635eSWarner Losh
13400acc635eSWarner Losh20001020:
13410acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
13420acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
13430acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
13440acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
13450acc635eSWarner Losh	workaround.
13460acc635eSWarner Losh
13470acc635eSWarner Losh20001010:
13480acc635eSWarner Losh	****************************** WARNING ******************************
13490acc635eSWarner Losh				Sendmail has been updated.
13500acc635eSWarner Losh	****************************** WARNING ******************************
13510acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
13520acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
13530acc635eSWarner Losh	  is set.
13540acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
13550acc635eSWarner Losh	  commands.
13560acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
13570acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
13580acc635eSWarner Losh	  in /usr/share/sendmail/cf.
13590acc635eSWarner Losh	o sendmail.cw changed to local-host-names
13600acc635eSWarner Losh
13610acc635eSWarner Losh	More details can be found at
13620acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
13630acc635eSWarner Losh
13646e98a146SWarner Losh20001009:
13656e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
13666e98a146SWarner Losh	your entire ports tree, or you will have problems.
13676e98a146SWarner Losh
13686e98a146SWarner Losh20001006:
1369685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
13706e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
13716e98a146SWarner Losh	/usr/bin/miniperl.
13726e98a146SWarner Losh
1373073113a4SWarner Losh20001005:
1374073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1375685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1376073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1377073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1378073113a4SWarner Losh	tree for anything to work.
1379073113a4SWarner Losh
13800acc635eSWarner Losh20000928:
13810acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
13820acc635eSWarner Losh
1383be3885b3SWarner Losh20000916:
1384be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1385be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1386be3885b3SWarner Losh	same time as your kernel.
1387be3885b3SWarner Losh
138876ec9675SWarner Losh20000914:
138976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
139076ec9675SWarner Losh	include the device will cause suspended laptops losing time
139176ec9675SWarner Losh	when they resume.  Include
139276ec9675SWarner Losh		device		pmtimer
139376ec9675SWarner Losh	in your config file and
139401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
139576ec9675SWarner Losh	to your /boot/device.hints file.
139676ec9675SWarner Losh
1397f4865386SMark Murray20000911:
1398f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1399f4865386SMark Murray	rather than an option. The supplied kernel config files have
1400f4865386SMark Murray	been updated. You will need to do something similar in your
1401f4865386SMark Murray	own kernel config file.
1402f4865386SMark Murray	Remove:
1403f4865386SMark Murray		options		RANDOMDEV
1404f4865386SMark Murray	Add:
1405f4865386SMark Murray		device		random
1406f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1407f4865386SMark Murray	nothing.
1408f4865386SMark Murray
1409d594498fSWarner Losh20000909:
1410d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1411d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1412d594498fSWarner Losh	reflect this if you load this module at boot time.
1413d594498fSWarner Losh	The line should read:
1414d594498fSWarner Losh		random_load="YES"
1415d594498fSWarner Losh
14160deb7ddcSWarner Losh20000907:
14170deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
141816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
141916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
142016eb772dSWarner Losh	sure you don't have model loading problems which might at
142116eb772dSWarner Losh	first blush appear related to SMP.
142252bf24e7SWarner Losh
14235a01880bSWarner Losh20000906:
14245a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
14255a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
14265a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
14275a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
14285a01880bSWarner Losh	don't have one, and you have host.conf.
14295a01880bSWarner Losh
14302b41163cSWarner Losh20000905:
143138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
143238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
143338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
143438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
143538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
143638d6ecd2SWarner Losh
143738d6ecd2SWarner Losh20000905:
14388aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
14398aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
14408aab4bc7SWarner Losh	is /boot/kernel.
14418aab4bc7SWarner Losh
14428aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
144338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
144438d6ecd2SWarner Losh	installkernel/installworld dance.
14452b41163cSWarner Losh
1446d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1447d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1448d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1449d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1450d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1451d594498fSWarner Losh
1452d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1453d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1454d594498fSWarner Losh		chflags noschg /kernel.old
1455d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1456d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1457d594498fSWarner Losh	fi
1458d594498fSWarner Losh
1459c22a309cSWarner Losh20000904:
1460c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1461c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1462c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1463c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1464c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1465c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1466c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1467c22a309cSWarner Losh	is not likely to be generated.
1468c22a309cSWarner Losh
1469fdb9f54dSWarner Losh20000825:
1470fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
14719c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
14729c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
14739c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
14749c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
14759c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
14769c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
14779c1a7444SWarner Losh	kernel.
14789c1a7444SWarner Losh
14799c1a7444SWarner Losh20000821:
14809c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
14819c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
14829c1a7444SWarner Losh	/boot/loader.conf.
1483fdb9f54dSWarner Losh
14848f250aa7SWarner Losh20000812:
14855da0d091SWarner Losh	suidperl is now always built and installed on the system, but
14865da0d091SWarner Losh	with permissions of 511.  If you have applications that use
14875da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
14885da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
14895da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
14905da0d091SWarner Losh	will fix this until the next build.
14915da0d091SWarner Losh
14925da0d091SWarner Losh20000812:
14938f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
14948f250aa7SWarner Losh	visible changes that may immediately affect your configuration
14958f250aa7SWarner Losh	include:
14968f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
14978f250aa7SWarner Losh	- newaliases limited to root and trusted users
14988f250aa7SWarner Losh	- MSA port (587) turned on by default
14998f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
15008f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
15018f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
15028f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
15038f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
15048f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
15058f250aa7SWarner Losh
150671c38472SWarner Losh20000810:
150771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
150871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
150971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
151071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
151171c38472SWarner Losh	specific use for it.
151271c38472SWarner Losh
151371c38472SWarner Losh20000729:
151471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
151571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
151671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
151771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
151871c38472SWarner Losh		# Enable network daemons for user convenience.
151971c38472SWarner Losh		inetd_enable="YES"
152071c38472SWarner Losh		portmap_enable="YES"
152171c38472SWarner Losh		sendmail_enable="YES"
152271c38472SWarner Losh
152371c38472SWarner Losh20000728:
152471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
152571c38472SWarner Losh	will need to change that to nullfs_load="YES".
152671c38472SWarner Losh
15271dece4a9SWarner Losh20000728:
15281dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
15291dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
15301dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
15311dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
15321dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
15331dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
15341dece4a9SWarner Losh	to /MYKERNEL.
15351dece4a9SWarner Losh
1536409e887cSWarner Losh20000711:
1537409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1538409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1539409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1540409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1541409e887cSWarner Losh	for details on potential problems that you might have and how
1542409e887cSWarner Losh	to get around them.
1543409e887cSWarner Losh
1544409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1545409e887cSWarner Losh	clauses above, you needn't worry.
1546409e887cSWarner Losh
1547409e887cSWarner Losh20000711:
1548409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1549409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1550409e887cSWarner Losh	in the number of changed programs the first time when you run
1551409e887cSWarner Losh	mergemaster to get a new /etc/security.
1552409e887cSWarner Losh
1553673d13f2SWarner Losh20000710:
1554673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1555673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1556673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1557673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1558673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1559673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1560673d13f2SWarner Losh	errors. (see below, 20000624).
1561673d13f2SWarner Losh
1562bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
15631dece4a9SWarner Losh
1564673d13f2SWarner Losh20000709:
1565c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1566c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1567c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1568673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1569673d13f2SWarner Losh
1570e98e26cdSWarner Losh20000706:
1571e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1572e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1573e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1574f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1575e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
15762c021c6cSMark Ovens	interim if needed.
1577e98e26cdSWarner Losh
1578e98e26cdSWarner Losh20000705:
1579e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1580e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1581e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1582e98e26cdSWarner Losh	details.
1583e98e26cdSWarner Losh
1584c373950eSWarner Losh20000704:
15852f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
15862f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
15872f961bc8SWarner Losh
15882f961bc8SWarner Losh20000704:
1589c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1590c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1591c373950eSWarner Losh	rc.d scripts that haven't been updated.
1592c373950eSWarner Losh
159327dc3a2bSWarner Losh20000630:
159427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
159527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
159627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
159727dc3a2bSWarner Losh
1598b8c215acSWarner Losh20000625:
1599b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
160027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
160127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
160227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
160327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
160427dc3a2bSWarner Losh	were required.  You should check with the latest collections
160527dc3a2bSWarner Losh	to make sure that these haven't changed.
1606b8c215acSWarner Losh
16077b990719SWarner Losh20000624:
16087b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
16097b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
16107b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
16111a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
16127b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
16137b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
16147b990719SWarner Losh	date to the completion of the work.
16157b990719SWarner Losh
161627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
161727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
161827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
161927dc3a2bSWarner Losh	recreate the random and urandom devices.
162027dc3a2bSWarner Losh
162181e54c50SWarner Losh20000622:
162281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
162381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
162481e54c50SWarner Losh	that used to be required when updating.
162581e54c50SWarner Losh
162639943833SWarner Losh20000621:
16272c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
16282a2f33fbSDaniel Baker	the config file update procedure.
16292a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1630c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
163159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
163259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
163339943833SWarner Losh
1634290f9ad8SWarner Losh20000620:
1635290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1636290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1637290f9ad8SWarner Losh	that workaround will no longer be required.
1638290f9ad8SWarner Losh
163990fb6346SWarner Losh20000615:
164090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
164190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
164290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
164390fb6346SWarner Losh	devices.
164490fb6346SWarner Losh
1645f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1646f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1647f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1648f75f65bbSWarner Losh	may work).
1649f75f65bbSWarner Losh
1650ba26da8eSWarner Losh20000612:
1651ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1652290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1653c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1654290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1655f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1656f54a3542SWarner Losh	NEWCARD for examples of the new format.
1657290f9ad8SWarner Losh
16589698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
16599698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
16609698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
16619698f2c0SWarner Losh	in it.
1662bbcc5149SWarner Losh
1663d65850ebSWarner Losh20000522:
1664ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1665d65850ebSWarner Losh	building a kernel after this point is advised that they need
1666d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1667d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1668d65850ebSWarner Losh
1669d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1670d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1671d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1672d9583a00SWarner Losh	is resolved.
1673d9583a00SWarner Losh
16748039cedeSWarner Losh20000513:
16758039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
16768039cedeSWarner Losh
1677d65850ebSWarner Losh20000510:
16788039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
16798039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
16808039cedeSWarner Losh	is requires for the boot blocks to build properly.
16818039cedeSWarner Losh
16828039cedeSWarner Losh20000503:
16838039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
16848039cedeSWarner Losh	is now available.
16858039cedeSWarner Losh
1686d65850ebSWarner Losh20000502:
1687d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1688d65850ebSWarner Losh	connected to the kernel building instead.
1689d65850ebSWarner Losh
1690be149406SNik Clayton20000427:
16918039cedeSWarner Losh	You may need to build gperf
16928039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
16938039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
16948039cedeSWarner Losh	an option only in -current.
16958039cedeSWarner Losh
16962b8dd5f4SWarner Losh20000417:
16972b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1698f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
16992b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
17002b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
17012c021c6cSMark Ovens	before you reboot, you'll need to issue:
17022b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
17032b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
17042b8dd5f4SWarner Losh
17058d9f1945SWarner Losh20000320:
17062b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
17072b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
17082b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1709ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
17102b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
17118d9f1945SWarner Losh
1712f8ab1dd6SWarner Losh20000319:
1713f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1714f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1715f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1716f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1717f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1718f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1719f8ab1dd6SWarner Losh
172019cada77SWarner Losh20000318:
1721f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
172219cada77SWarner Losh	Large kernel changes are being committed and are in the
172319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
172419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
172519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
172619cada77SWarner Losh	that you are loading are up to date.
1727ba228352SWarner Losh
172819cada77SWarner Losh20000315:
17296d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
17306d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
17316d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
17326d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
17336d23c382SWarner Losh	boot.
17346d23c382SWarner Losh
17356d23c382SWarner Losh20000315:
173619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
173719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
173857199806SWarner Losh
1739dc0dbf5cSWarner LoshCOMMON ITEMS:
1740dc0dbf5cSWarner Losh
1741cd5f061cSWarner Losh	# NOTE: 5.x below applies to 6.0-currrent as well, for the
1742cd5f061cSWarner Losh	# momemnt.  4.any -> 5.any upgrade support will remain in
1743cd5f061cSWarner Losh	# place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1744cd5f061cSWarner Losh	# 6.0-current upgrade path will require moving through 5.3
1745cd5f061cSWarner Losh	# RELEASE or newer.
1746cd5f061cSWarner Losh
1747a24eff53SWarner Losh	General Notes
1748a24eff53SWarner Losh	-------------
1749a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1750a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1751a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1752a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1753a24eff53SWarner Losh	or several minor releases, or when several months have passed
1754a24eff53SWarner Losh	on the -current branch).
1755a24eff53SWarner Losh
17565780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
17575780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
17585780f3baSWarner Losh	environment when searching for values for global variables.
17595780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
17605780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
17615780f3baSWarner Losh	page for more details.
17625780f3baSWarner Losh
1763dc0dbf5cSWarner Losh	To build a kernel
1764dc0dbf5cSWarner Losh	-----------------
1765ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1766f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1767ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1768282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1769282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1770dc0dbf5cSWarner Losh
1771ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1772ba01eb20SWarner Losh	--------------------------------------------------------------
17730fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
17740fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
17750fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
17760fbd2da9SKen Smith
17770fbd2da9SKen Smith	cd src/sys/${arch}/conf
177847d0d01fSWarner Losh	config KERNEL_NAME_HERE
17790fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1780ba01eb20SWarner Losh	make depend
1781ba01eb20SWarner Losh	make
1782ba01eb20SWarner Losh	make install
1783ba01eb20SWarner Losh
1784ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1785ba01eb20SWarner Losh
1786ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1787ba01eb20SWarner Losh	-----------------------------------------------------------
178863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
178963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
179063cb445eSWarner Losh
1791f643de42SWarner Losh	<make sure you have good level 0 dumps>
179263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
179363cb445eSWarner Losh	make buildworld
17946586253aSWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE
179563cb445eSWarner Losh							[1]
179663cb445eSWarner Losh	<reboot in single user>				[3]
17976586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
179863cb445eSWarner Losh	mergemaster -p					[5]
179963cb445eSWarner Losh	make installworld
180063cb445eSWarner Losh	mergemaster					[4]
180163cb445eSWarner Losh	<reboot>
180263cb445eSWarner Losh
1803759f0aefSWarner Losh
1804f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1805f27b1fceSJoseph Koshy	--------------------------------------------------
1806f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1807f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1808f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1809f27b1fceSJoseph Koshy	# size.
1810f27b1fceSJoseph Koshy
1811f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1812f27b1fceSJoseph Koshy	<boot into -stable>
1813f27b1fceSJoseph Koshy	make buildworld
1814f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1815f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1816f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1817f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
18186586253aSWarner Losh	cp src/sys/${ARCH}/conf/GENERIC.hints \
1819f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1820f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
18216586253aSWarner Losh	cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1822f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1823f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1824f27b1fceSJoseph Koshy	<reboot into current>
1825f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
18266586253aSWarner Losh	<maybe install compatibility libraries from src/lib/compat>
1827f27b1fceSJoseph Koshy 	<reboot>
1828f27b1fceSJoseph Koshy
1829f27b1fceSJoseph Koshy
1830f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1831f27b1fceSJoseph Koshy	----------------------------------------------
18325c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
1833e5dc5f61SWarner Losh	# modules has changed.  If you are installing 5.x onto a 4.x
18345c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
18355c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1836ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1837f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1838f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1839f643de42SWarner Losh	# space on /.
1840f643de42SWarner Losh
1841f643de42SWarner Losh	<make sure you have good level 0 dumps>
1842fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
184321c075eaSWarner Losh	make buildworld					[9]
1844802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1845e5dc5f61SWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
1846802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install		[6]
1847fc8c157fSWarner Losh							[1]
1848fc8c157fSWarner Losh	<reboot in single user>				[3]
18496586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
1850835284beSWarner Losh	mergemaster -p					[5]
1851f8a4c901SWarner Losh	rm -rf /usr/include/g++
1852ba26da8eSWarner Losh	make installworld
1853802fc49dSBrian Feldman	mergemaster -i					[4]
1854ba26da8eSWarner Losh	<reboot>
1855ba26da8eSWarner Losh
1856fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1857fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1858fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1859fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1860fdb9f54dSWarner Losh	the UPDATING entries.
1861ba26da8eSWarner Losh
18621dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
18631dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
18641dece4a9SWarner Losh	your sources that you have read and understood all the recent
18651dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
18661dece4a9SWarner Losh	much fewer pitfalls.
18671dece4a9SWarner Losh
1868134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1869134d2e86SWarner Losh	should disable them at this point so they don't crash your
1870134d2e86SWarner Losh	system on reboot.
1871134d2e86SWarner Losh
18729c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
18739c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
18749c1a7444SWarner Losh	configuration.
18759c1a7444SWarner Losh
1876ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1877ee6e1fc3SWarner Losh		fsck -p
1878ee6e1fc3SWarner Losh		mount -u /
1879ee6e1fc3SWarner Losh		mount -a
18806586253aSWarner Losh		cd src
188147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1882f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1883f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
188466986952SRuslan Ermilov	For the 4.x -> 5.x upgrade, you will also see many messages about
1885b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1886b705ae10SWarner Losh	be ignored while you proceed to the next step.
1887ee6e1fc3SWarner Losh
1888a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1889a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1890a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1891a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1892a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1893a6cd4f9dSWarner Losh	for potential gotchas.
1894a6cd4f9dSWarner Losh
1895835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1896835284beSWarner Losh	you may need to do this if you get unknown user in the following
1897835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1898835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1899835284beSWarner Losh	install) after the buildworld before this step if you last updated
1900835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1901835284beSWarner Losh
1902bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1903bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1904bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1905bd79cf40SWarner Losh		ok unload
1906bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1907bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1908bd79cf40SWarner Losh	described here.
1909fc8c157fSWarner Losh
1910fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1911e5dc5f61SWarner Losh	compatibility slices.  These are device names of the form /dev/ad0a
1912e5dc5f61SWarner Losh	without the actual slice name.  These will break with 5.x and newer.
1913fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1914e5dc5f61SWarner Losh	2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1915e5dc5f61SWarner Losh	is not.
1916fc8c157fSWarner Losh
1917c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1918c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1919c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1920c74fe6afSWarner Losh	that is hard to boot to recover.
1921c74fe6afSWarner Losh
1922e5dc5f61SWarner Losh	Make sure that you merge any new devices from GENERIC since the
1923e5dc5f61SWarner Losh	last time you updated your kernel config file.
1924e5dc5f61SWarner Losh
192521c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1926e5dc5f61SWarner Losh	cvs prune empty directories.
1927e5dc5f61SWarner Losh
1928e5dc5f61SWarner Losh	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1929e5dc5f61SWarner Losh	"?=" instead of the "=" assignment operator, so that buildworld can
1930e5dc5f61SWarner Losh	override the CPUTYPE if it needs to.
1931e5dc5f61SWarner Losh
1932e5dc5f61SWarner Losh	MAKEOBJDIRPREFIX must be defined in an environment variable, and
1933e5dc5f61SWarner Losh	not on the command line, or in /etc/make.conf.  buildworld will
1934e5dc5f61SWarner Losh	warn if it is improperly defined.
1935e5dc5f61SWarner Losh
1936802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1937802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
193866986952SRuslan Ermilov	compatibility libraries are built which should allow you to continue
1939e5dc5f61SWarner Losh	using your existing software for a while.  Alternatively, you can
1940e5dc5f61SWarner Losh	install the misc/compat4x port.
19418633bbeaSBrooks Davis
19428633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
19436586253aSWarner Losh	initialized by feeding data into it.  src/etc/rc.d/preseedrandom
19448633bbeaSBrooks Davis	takes care of this.
1945dc0dbf5cSWarner LoshFORMAT:
1946dc0dbf5cSWarner Losh
1947f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
19481fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1949f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1950f8ab1dd6SWarner Loshprevious releases if your system is older than this.
19511fc1a0dcSWarner Losh
1952e72fd46aSWarner LoshCopyright information:
1953e72fd46aSWarner Losh
1954e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh.  All Rights Reserved.
1955e72fd46aSWarner Losh
1956772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1957772730c7SWarner Loshmodification, in full or in part, in any form or format of this
19589698f2c0SWarner Loshdocument are permitted without further permission from the author.
1959e72fd46aSWarner Losh
1960e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1961e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1962e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1963e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1964e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1965e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1966e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1967e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1968e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1969e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1970e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1971e72fd46aSWarner Losh
1972e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1973e72fd46aSWarner Loshauthor a beer.
1974e72fd46aSWarner Losh
197522306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1976772730c7SWarner Loshthis document.
1977772730c7SWarner Losh
197897d92980SPeter Wemm$FreeBSD$
1979