xref: /freebsd/UPDATING (revision 71c1c49abbf1b91b02b250f791a6c3122e8e1e32)
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
2671c1c49aSBrian Somers20041213:
2771c1c49aSBrian Somers	The behaviour of ppp(8) has changed slightly.  If lqr is enabled
2871c1c49aSBrian Somers	(``enable lqr''), older versions would revert to LCP ECHO mode on
2971c1c49aSBrian Somers	negotiation failure.  Now, ``enable echo'' is required for this
3071c1c49aSBrian Somers	behaviour.  The ppp version number has been bumped to 3.4.2 to
3171c1c49aSBrian Somers	reflect the change.
3271c1c49aSBrian Somers
3388046524SSam Leffler20041201:
3488046524SSam Leffler	The wlan support has been updated to split the crypto support
3588046524SSam Leffler	into separate modules.  For static WEP you must configure the
3688046524SSam Leffler	wlan_wep module in your system or build and install the module
3788046524SSam Leffler	in place where it can be loaded (the kernel will auto-load
3888046524SSam Leffler	the module when a wep key is configured).
3988046524SSam Leffler
4088046524SSam Leffler20041201:
4188046524SSam Leffler	The ath driver has been updated to split the tx rate control
4288046524SSam Leffler	algorithm into a separate module.  You need to include either
4388046524SSam Leffler	ath_rate_onoe or ath_rate_amrr when configuring the kernel.
4488046524SSam Leffler
4581adddf3SJohn Baldwin20041116:
4681adddf3SJohn Baldwin	Support for systems with an 80386 CPU has been removed.  Please
4781adddf3SJohn Baldwin	use FreeBSD 5.x or earlier on systems with an 80386.
4881adddf3SJohn Baldwin
4942ba1c57SPoul-Henning Kamp20041110:
5042ba1c57SPoul-Henning Kamp	We have had a hack which would mount the root filesystem
5142ba1c57SPoul-Henning Kamp	R/W if the device were named 'md*'.  As part of the vnode
5242ba1c57SPoul-Henning Kamp	work I'm doing I have had to remove this hack.  People
5342ba1c57SPoul-Henning Kamp	building systems which use preloaded MD root filesystems
5442ba1c57SPoul-Henning Kamp	may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
5542ba1c57SPoul-Henning Kamp	their /etc/rc scripts.
5642ba1c57SPoul-Henning Kamp
57c94c54e4SAndre Oppermann20041102:
58c94c54e4SAndre Oppermann	The size of struct tcpcb has changed again due to the removal
59c94c54e4SAndre Oppermann	of RFC1644 T/TCP.  You have to recompile userland programs that
60c94c54e4SAndre Oppermann	read kmem for tcp sockets directly (netstat, sockstat, etc.)
61c94c54e4SAndre Oppermann
62cd109b0dSAndre Oppermann20041022:
63cd109b0dSAndre Oppermann	The size of struct tcpcb has changed.  You have to recompile
64cd109b0dSAndre Oppermann	userland programs that read kmem for tcp sockets directly
65cd109b0dSAndre Oppermann	(netstat, sockstat, etc.)
66cd109b0dSAndre Oppermann
67cf0684aeSMike Makonnen20041007:
68028a5b92SMike Makonnen	The FreeBSD keyword is no longer a requirement for a valid
69028a5b92SMike Makonnen	rc.d script. The rc(8) and rc.shutdown(8) scripts no longer check
70028a5b92SMike Makonnen	for the existence of this keyword when ordering rc.d scripts.
7100bd8f10SMike Makonnen	This change touches most of the file in /etc/rc.d; therefore,
7200bd8f10SMike Makonnen	if you have not modified any files in that directory it may
7300bd8f10SMike Makonnen	be easier to rm -rf /etc/rc.d and then use the -i switch with
7400bd8f10SMike Makonnen	mergemaster(8).
75028a5b92SMike Makonnen
76028a5b92SMike Makonnen20041007:
77cf0684aeSMike Makonnen	One of the syscalls the 1:1 threading library libthr uses has
78cf0684aeSMike Makonnen	changed, thus breaking ABI compatibility. Make sure you rebuild
79cf0684aeSMike Makonnen	this library with the kernel.
80cf0684aeSMike Makonnen
81773322d5SDavid E. O'Brien20041004:
82773322d5SDavid E. O'Brien	A major sweep over the tty drivers to elimnate approx 3100
83773322d5SDavid E. O'Brien	lines of copy&pasted code have been performed.  As a part of
84773322d5SDavid E. O'Brien	this change some tty devices have changed names:
85773322d5SDavid E. O'Brien	sio devices are now named:	{tty,cua}d%d[.init,.lock]
86773322d5SDavid E. O'Brien	ucom devices are now named:	{tty,cua}U%d[.init,.lock]
87773322d5SDavid E. O'Brien	For other drivers see the commit logs.
88773322d5SDavid E. O'Brien
8985a8b887SKen Smith20041001:
9085a8b887SKen Smith	The following libraries had their version number bumped up:
9185a8b887SKen Smith		/lib/libm.so.2 -> libm.so.3
9285a8b887SKen Smith		/lib/libreadline.so.4 -> libreadline.so.5
9385a8b887SKen Smith		/usr/lib/libhistory.so.4 -> libhistory.so.5
9485a8b887SKen Smith		/usr/lib/libopie.so.2 -> libopie.so.3
9585a8b887SKen Smith		/usr/lib/libpcap.so.2 -> libpcap.so.3
9685a8b887SKen Smith	FreeBSD 4.10 versions of these libraries will be added to the
9785a8b887SKen Smith	compat4x collection.  If you expect to be able to run old 4.X
9885a8b887SKen Smith	executables you will need to remove the old versions of these
9985a8b887SKen Smith	libraries.  However note that any 5.X executables you have built
10085a8b887SKen Smith	will stop working once you remove those old libraries.  You should
10185a8b887SKen Smith	have all your ports/packages rebuilt before removing the old
10285a8b887SKen Smith	libraries.
10385a8b887SKen Smith
104d6a8d588SMax Laier20040929:
105d6a8d588SMax Laier	The pfil API has gained an additional argument to pass an inpcb.
106d6a8d588SMax Laier	You should rebuild all pfil consuming modules: ipfw, ipfilter
107d6a8d588SMax Laier	and pf.
108d6a8d588SMax Laier
1098f1bb389SDoug Barton20040928:
110cfeb1f52SDoug Barton	If named is enabled, the default is now to run it in a chroot
1118f1bb389SDoug Barton	"sandbox." For users with existing configurations in
1128f1bb389SDoug Barton	/etc/namedb the migration should be simple. Upgrade your
1138f1bb389SDoug Barton	world as usual, then after installworld but before
1148f1bb389SDoug Barton	mergemaster do the following:
1158f1bb389SDoug Barton
1168f1bb389SDoug Barton	If named is running: /etc/rc.d/named stop
1178f1bb389SDoug Barton	cd /etc
1188f1bb389SDoug Barton	mv namedb namedb.bak
1198f1bb389SDoug Barton	mkdir -p /var/named/etc/namedb
1208f1bb389SDoug Barton	cp -Rp namedb.bak/* /var/named/etc/namedb/
1218f1bb389SDoug Barton	mergemaster (with your usual options)
1228f1bb389SDoug Barton	If using the generated localhost* files:
1238f1bb389SDoug Barton		cd /var/named/etc/namedb
1248f1bb389SDoug Barton		/bin/sh make-localhost
1258f1bb389SDoug Barton		rm -f localhost-v6.rev localhost.rev
126cfeb1f52SDoug Barton	/etc/rc.d/syslogd restart
1278f1bb389SDoug Barton	/etc/rc.d/named start
1288f1bb389SDoug Barton
1298f1bb389SDoug Barton	If you are using a custom configuration, or if you have
1308f1bb389SDoug Barton	customised the named_* variables in /etc/rc.conf[.local]
1318f1bb389SDoug Barton	then you may have to adjust the instructions accordingly.
1328f1bb389SDoug Barton	It is suggested that you carefully examine the new named
1338f1bb389SDoug Barton	variables in /etc/defaults/rc.conf and the options in
1348f1bb389SDoug Barton	/var/named/etc/namedb/named.conf to see if they might
1358f1bb389SDoug Barton	now be more suitable.
1368f1bb389SDoug Barton
1375d36721aSDoug Barton20040925:
1385d36721aSDoug Barton	BIND 9 has been imported into the base, and is now fully
1395d36721aSDoug Barton	functional. BIND 8 has now been removed. There are numerous
1405d36721aSDoug Barton	differences between BIND 8 and 9, and users with critical
1415d36721aSDoug Barton	named installations should read the migration documentation
1425d36721aSDoug Barton	in /usr/share/doc/bind9/misc/migration. There is also a
1435d36721aSDoug Barton	new instruction manual in /usr/share/doc/bind9/arm.
1445d36721aSDoug Barton
1455d36721aSDoug Barton	The key differences that most users will experience are in
1465d36721aSDoug Barton	how picky BIND 9 is about zone file format. If you are using
1475d36721aSDoug Barton	named as a resolving (caching) name server, you will likely
1485d36721aSDoug Barton	not have trouble.
1495d36721aSDoug Barton
150f50b1bdbSDoug Barton	The following files are part of the old BIND 8 installation
151f50b1bdbSDoug Barton	and should be removed:
152f50b1bdbSDoug Barton	/usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
153f50b1bdbSDoug Barton	/usr/sbin/named.restart /usr/sbin/ndc
154f50b1bdbSDoug Barton
155f50b1bdbSDoug Barton	The following files have moved to /usr/bin, and should be
156f50b1bdbSDoug Barton	removed from their old locations:
157f50b1bdbSDoug Barton	/usr/sbin/nslookup /usr/sbin/nsupdate
158f50b1bdbSDoug Barton
159f5ee5a8bSMax Laier20040914:
160f5ee5a8bSMax Laier	The format of the pflogd(8) logfile "/var/log/pflog" has changed for
161f5ee5a8bSMax Laier	architectures that have a 64 bit long type to make it compatible to
162f5ee5a8bSMax Laier	the standard pcap format. In order to prevent corruption move away
163f5ee5a8bSMax Laier	any old logfile before using a new pflogd(8).
164f5ee5a8bSMax Laier
165d698cdb3SJohn-Mark Gurney20040906:
166d698cdb3SJohn-Mark Gurney	debug.witness_* has been renamed to debug.witness.*.  There are
167d698cdb3SJohn-Mark Gurney	compatibility tunables left in for a few days.  Update loader.conf
168d698cdb3SJohn-Mark Gurney	as necessary.
169d698cdb3SJohn-Mark Gurney
1704ff62bd9SBrooks Davis20040902:
1714ff62bd9SBrooks Davis	The ifi_epoch change has been reverted because the ABI breakage
1724ff62bd9SBrooks Davis	was too extensive.  If you are running with a kernel/userland
1734ff62bd9SBrooks Davis	containing the initial change (20040830), you should heed the
1744ff62bd9SBrooks Davis	warning about ifconfig incompatibility when upgrading again.
1754ff62bd9SBrooks Davis	With this change, 5.3 and 6.0 ifconfigs and kernels are once
1764ff62bd9SBrooks Davis	again interoperable.
1774ff62bd9SBrooks Davis
1781fc4519bSBrooks Davis20040830:
1791fc4519bSBrooks Davis	A new variable, ifi_epoch, has been added to struct if_data
1801fc4519bSBrooks Davis	which is part if struct ifnet.  This means all network drivers
1811fc4519bSBrooks Davis	and network monitoring applications need to be recompiled.
1821fc4519bSBrooks Davis
1833789fb75SBrooks Davis        WARNING WARNING WARNING WARNING WARNING WARNING WARNING
1843789fb75SBrooks Davis
1853789fb75SBrooks Davis        This also breaks ifconfig compatibility.  An old ifconfig will
1863789fb75SBrooks Davis        not work with the new kernel and a new ifconfig will not work
1873789fb75SBrooks Davis        with the old.  It is strongly recommended that you make a copy
1883789fb75SBrooks Davis        of your old ifconfig before installworld.  If you are installing
1893789fb75SBrooks Davis        remotely, you must copy over a new ifconfig before rebooting in
1903789fb75SBrooks Davis        to the new kernel.
1913789fb75SBrooks Davis
192c1c94d5cSRobert Watson20040828:
193c1c94d5cSRobert Watson	The default configuration for the network stack has been changed
194c1c94d5cSRobert Watson	such that it now runs without the Giant lock unless configured
195c1c94d5cSRobert Watson	otherwise.  If you experience network-related instability, you
196c1c94d5cSRobert Watson	may wish to try setting "debug.mpsafenet=0" or compiling the
197c1c94d5cSRobert Watson	kernel with "options NET_WITH_GIANT".  Details on the netperf
198c1c94d5cSRobert Watson	project may be found at:
199c1c94d5cSRobert Watson
200c1c94d5cSRobert Watson	    http://www.watson.org/~robert/freebsd/netperf/
201c1c94d5cSRobert Watson
202c1c94d5cSRobert Watson	Including the 20040828 announcement of configuration change
203c1c94d5cSRobert Watson	details.
204c1c94d5cSRobert Watson
205c21fd232SAndre Oppermann20040827:
206c21fd232SAndre Oppermann	PFIL_HOOKS are a fixed part of the network stack now and do not
207c21fd232SAndre Oppermann	need to be specified in the kernel configuration file anymore.
208c21fd232SAndre Oppermann
209f036d408SJulian Elischer20040819:
210f036d408SJulian Elischer	Netgraph changed its message format slightly to align the data
211f036d408SJulian Elischer	portion well on 64 bit machines.
212f036d408SJulian Elischer	Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
213f036d408SJulian Elischer	pppoed, bluetooth, ATM) should be recompiled when a new kernel
214f036d408SJulian Elischer	is installed.
215f036d408SJulian Elischer
216b067abfaSAndre Oppermann20040817:
217b05bb3e7SMax Laier	IPFW has been converted to use pfil(9).  This change is
218b067abfaSAndre Oppermann	transparent to userland and preserves the ipfw ABI.  The ipfw
219b067abfaSAndre Oppermann	core packet inspection and filtering functions have not been
220b05bb3e7SMax Laier	changed, only how ipfw is invoked is different.
221b067abfaSAndre Oppermann
222f13a7951SDavid Malone20040814:
223f13a7951SDavid Malone	The RANDOM_IP_ID option has been replaced by the sysctl
224f13a7951SDavid Malone	net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
225f13a7951SDavid Malone	you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
226f13a7951SDavid Malone
2273a004637SMax Laier20040807:
2283a004637SMax Laier	The size of 'struct ifnet' has changed due to the addition of the
2293a004637SMax Laier	if_carp placeholder.  All kernel modules implementing network
2303a004637SMax Laier	interfaces must be recompiled as a result.
2313a004637SMax Laier
2324f34d8d1SJohn-Mark Gurney20040806:
2334f34d8d1SJohn-Mark Gurney	Module loading has been fixed.  Some older installations will
234ac41c814SRuslan Ermilov	drop proper module_path initialization and modules will fail to
2354f34d8d1SJohn-Mark Gurney	load properly.  If you have a line in /boot/loader.rc that says:
2364f34d8d1SJohn-Mark Gurney	"initialize drop", do (i386 only):
2374f34d8d1SJohn-Mark Gurney		cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
2384f34d8d1SJohn-Mark Gurney		chown root:wheel /boot/loader.rc
2394f34d8d1SJohn-Mark Gurney		chmod 444 /boot/loader.rc
2404f34d8d1SJohn-Mark Gurney
2418f075db4SMark Murray20040802:
2428f075db4SMark Murray	making /dev/(null|zero) into a module proved to be too unpopular,
2438f075db4SMark Murray	so this bit has been revoked from the previous (20040801) entry.
2448f075db4SMark Murray
245d064d6dbSMark Murray20040801:
246d064d6dbSMark Murray	The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
247d064d6dbSMark Murray	so you may wish to add them to your kernel config file. See
248d064d6dbSMark Murray	GENERIC for examples.
249d064d6dbSMark Murray
250b289983eSAlexander Kabaev20040728:
25154bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
25254bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
25354bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
25454bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
255d0e54ab4SDavid E. O'Brien	compiler. If you are getting run-time error such as
256d0e54ab4SDavid E. O'Brien	/libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
257d0e54ab4SDavid E. O'Brien	This entry does apply to you.
258d0e54ab4SDavid E. O'Brien
259d0e54ab4SDavid E. O'Brien	A new unit-at-a-time optimization mode, which is default in this
260d0e54ab4SDavid E. O'Brien	compiler release, is more aggressive in removing unused static
261d0e54ab4SDavid E. O'Brien	symbols. This is the likely cause of 'make buildworld' breakages
262cd5f061cSWarner Losh	with non-default CFLAGS where optimization level is set to -O2
263cd5f061cSWarner Losh	or higher.
26454bd5271SAlexander Kabaev
2656e1afae3SWarner Losh	With the upgrade of the system compiler, the kernel has been upgraded
2666e1afae3SWarner Losh	to match the new system compiler.  This makes it impossible to build
2676e1afae3SWarner Losh	a new kernel with the old compiler.  Upgrade your system via
2686e1afae3SWarner Losh	make buildworld and make kernel (see below) to fix this problem.
2696e1afae3SWarner Losh
27036ed21e6SRobert Watson20040727:
27136ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
27236ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
27336ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
27436ed21e6SRobert Watson	a result.
27536ed21e6SRobert Watson
2766305ac24SSeigo Tanimura20040716:
2776305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
2786305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
2796305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
2806305ac24SSeigo Tanimura
281e623dcb7SMarcel Moolenaar20040710:
282e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
283e623dcb7SMarcel Moolenaar
284e623dcb7SMarcel Moolenaar20040710:
285e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
286e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
287e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
288773322d5SDavid E. O'Brien	hints (hint.sio.0.flags="0x10") are now required for the sio(4)
289773322d5SDavid E. O'Brien	driver to become a console or debug port.  The NO_SIO option has
290773322d5SDavid E. O'Brien	been decommissioned because of this.
291773322d5SDavid E. O'Brien	Running mergemaster is the easiest way to ensure your
292773322d5SDavid E. O'Brien	'boot/device.hints' has the needed line.
293e623dcb7SMarcel Moolenaar
294e623dcb7SMarcel Moolenaar20040710:
295e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
296e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
297e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
298e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
299e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
300e623dcb7SMarcel Moolenaar	   option for this.
301e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
302e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
303e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
304e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
3055bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
306e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
307e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
308e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
309e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
310e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
311e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
312e623dcb7SMarcel Moolenaar
3136421d1dbSMaksim Yevmenkin20040708:
3146421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
3156421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
3166421d1dbSMaksim Yevmenkin
31758af3216SWarner Losh20040702:
31858af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
3195bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
3205bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
3215bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
32258af3216SWarner Losh	scheduler as a workaround.
32358af3216SWarner Losh
324c2dba668SNate Lawson20040630:
3258ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
3268ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
327a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
328a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
329a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
330a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
331a6c26e1cSBruce M Simpson	example of such changes.
3328ed370fdSJulian Elischer
33358af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
33458af3216SWarner Losh	over.
33558af3216SWarner Losh
3368ed370fdSJulian Elischer20040630:
337c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
3385bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
339c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
340c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
341c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
342c2dba668SNate Lawson	loader prompt.
343c2dba668SNate Lawson
3448ee2ac9eSMax Laier20040623:
3455bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
3468ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
3478ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
3488ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
3498ee2ac9eSMax Laier
3503db5687dSBrooks Davis20040622:
3513db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
3523db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
3533db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
3543db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
3553db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
3563db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
3573db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
3583db5687dSBrooks Davis
359e0ae81f3SDag-Erling Smørgrav20040621:
360e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
361e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
362e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
363e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
364e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
365e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
366e0ae81f3SDag-Erling Smørgrav	during the next reboot.
367e0ae81f3SDag-Erling Smørgrav
3684717d22aSJohn Polstra20040614:
3694717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
3704717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
3714717d22aSJohn Polstra	the ips module and any third-party modules which call
3724717d22aSJohn Polstra	sema_timedwait.
3734717d22aSJohn Polstra
3746cb7a382SMax Laier20040613:
3756cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
3766cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
377df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
378df843493SMax Laier	please recompile and reinstall world.
3796cb7a382SMax Laier
3802454685eSJulian Elischer20040607:
3812454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
3822454685eSJulian Elischer	requires that you re-run config after updating your tree.
3832454685eSJulian Elischer
38464fef830SSeigo Tanimura20040601:
38564fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
38664fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
38764fef830SSeigo Tanimura	kernel configuration.
38864fef830SSeigo Tanimura
389bb4f06e7SAndre Oppermann20040423:
390bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
391bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
392bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
393bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
394bb4f06e7SAndre Oppermann
39505641e82SColin Percival20040420:
39605641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
39705641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
39805641e82SColin Percival	20040406.
39905641e82SColin Percival
400d0dc9183SWarner Losh20040414:
401d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
402d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
403d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
404d0dc9183SWarner Losh
405d0dc9183SWarner Losh20040412:
406d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
407d0dc9183SWarner Losh	drive is still broken.
408d0dc9183SWarner Losh
409d0dc9183SWarner Losh20040410:
410d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
411d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
412d0dc9183SWarner Losh	the unanticipated problems have been resolved.
413d0dc9183SWarner Losh
4148633bbeaSBrooks Davis20040409:
4158633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
4168633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
4178633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
4188633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
41976c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
4208633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
4218633bbeaSBrooks Davis
422d40d033aSRobert Watson20040322:
423d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
424d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
425d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
426d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
427d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
428d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
429d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
430d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
431d40d033aSRobert Watson	locking is merged to permit this to take place.
432d40d033aSRobert Watson
433ec9b318eSGarance A Drosehn20040310:
434ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
435ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
436ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
437ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
438ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
439ec9b318eSGarance A Drosehn
440fc28f1ffSMax Laier20040308:
441fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
442fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
4434c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
4444c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
445b05bb3e7SMax Laier	The pf system consists of the following three devices:
446fc28f1ffSMax Laier	device		pf		# required
447fc28f1ffSMax Laier	device		pflog		# optional
448fc28f1ffSMax Laier	device		pfsync		# optional
449fc28f1ffSMax Laier
4503aff5d06SDag-Erling Smørgrav20040303:
4513aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
4523aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
4533aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
4543aff5d06SDag-Erling Smørgrav
4553aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
4563aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
4573aff5d06SDag-Erling Smørgrav
4583aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
4593aff5d06SDag-Erling Smørgrav	to use libpthread instead.
4603aff5d06SDag-Erling Smørgrav
461fd63c5b3SDag-Erling Smørgrav20040226:
4629d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
463fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
464fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
465fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
466fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
467fd63c5b3SDag-Erling Smørgrav
468714ae42aSBruce M Simpson20040225:
469e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
470e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
471e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
472e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
473e07a40f3SBrian Feldman	should remain unaffected.
474e07a40f3SBrian Feldman
475e07a40f3SBrian Feldman20040225:
476714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
477714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
478714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
479714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
480714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
481714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
482714ae42aSBruce M Simpson
483fbd2e692SAndre Oppermann20040224:
484fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
4855bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
486fbd2e692SAndre Oppermann
487158b90daSWarner Losh20040222:
488158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
489158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
490158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
491158b90daSWarner Losh	Drivers outside the tree will need to be updated.
492158b90daSWarner Losh
493b7b1e150SMike Makonnen20040207:
494b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
495b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
496b7b1e150SMike Makonnen
497aca89ee6SDaniel Eischen20040130:
498aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
499aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
500aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
501aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
502aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
503aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
504aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
505aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
506aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
507aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
508aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
509aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
510aca89ee6SDaniel Eischen	do not work with libpthread.
511aca89ee6SDaniel Eischen
51268b7b3a9SAlex Dupre20040125:
51368b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
51468b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
51568b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
51668b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
51768b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
51868b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
51968b7b3a9SAlex Dupre
520ff46e0deSWarner Losh20040125:
521ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
522ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
523ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
524ff46e0deSWarner Losh
525ce41f4bfSRobert Watson20031213:
526ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
527ce41f4bfSRobert Watson	if the login process is unable to successfully set the
528ce41f4bfSRobert Watson	process credentials to include all groups defined for the
529ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
530ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
531ce41f4bfSRobert Watson	defined, or they will be unable to log in.
532ce41f4bfSRobert Watson
533c124fa05SJohn Baldwin20031203:
534c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
535c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
536c124fa05SJohn Baldwin
5378ad1f5e4SHartmut Brandt20031112:
53830093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
53930093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
54097209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
54197209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
54297209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
54397209ca3SRobert Watson	not know about the new system calls that support the new statfs
5443f631d52SMarcel Moolenaar	structure.
5453f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
5463f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
5473f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
5483f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
5493f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
5503f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
5513f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
5523f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
5533f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
5543f631d52SMarcel Moolenaar	these changes are installed.
55530093b05SWarner Losh
55630093b05SWarner Losh	****************************DANGER*******************************
55730093b05SWarner Losh
55830093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
55930093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
56030093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
56130093b05SWarner Losh	kernel.
56264a18d6fSKirk McKusick
56364a18d6fSKirk McKusick20031112:
5648ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
5658ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
5668ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
5678ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
5688ad1f5e4SHartmut Brandt	sync before rebooting.
5698ad1f5e4SHartmut Brandt
570c53a5d8fSJohn Baldwin20031111:
571c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
572c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
573c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
574c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
575c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
576c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
577c53a5d8fSJohn Baldwin
5788bf455a5SJohn Baldwin20031103:
5798bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
5808bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
5812a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
5828bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
5838bf455a5SJohn Baldwin
5849bf40edeSBrooks Davis20031031:
5859bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
5869bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
5879bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
5889bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
5899bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
5909bf40edeSBrooks Davis	reflect this change.
5919bf40edeSBrooks Davis
59247a42c7aSPoul-Henning Kamp20030928:
59347a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
59447a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
5955bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
59647a42c7aSPoul-Henning Kamp
59707105342SMax Khon20030926:
59807105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
59907105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
60007105342SMax Khon
601fedf1d01SBruce M Simpson20030923:
602fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
603fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
604fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
605fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
606fedf1d01SBruce M Simpson
607db38f9cbSJacques Vidrine20030915:
608db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
609db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
610db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
611db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
612db38f9cbSJacques Vidrine
613c09d2c2bSMike Makonnen20030829:
614c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
615c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
616c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
617c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
618c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
619c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
620c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
621c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
622c09d2c2bSMike Makonnen	may or may not exist on your system.
623c09d2c2bSMike Makonnen
62417c159dcSSøren Schmidt20030824:
62517c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
62617c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
627f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
628f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
62917c159dcSSøren Schmidt
630c1f61aa9SDavid E. O'Brien20030819:
631c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
632c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
633c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
634c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
63569f7bcf3SWarner Losh
63638c962e7SNate Lawson20030728:
63738c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
63838c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
63938c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
64038c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
64138c962e7SNate Lawson	so the quirk can be re-enabled.
64238c962e7SNate Lawson
64374111097SWarner Losh20030724:
64474111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
64574111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
64674111097SWarner Losh
647178cf4e9SWarner Losh20030722:
648178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
649178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
650178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
651178cf4e9SWarner Losh	FPU hardware.
652178cf4e9SWarner Losh
653178cf4e9SWarner Losh20030714:
654178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
655178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
656178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
657178cf4e9SWarner Losh	People should report those issues to current@.
658178cf4e9SWarner Losh
659157c629aSWarner Losh20030711:
660157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
6618b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
66205538fa9SWarner Losh	/usr/obj.
663157c629aSWarner Losh
66474111097SWarner Losh20030610:
66574111097SWarner Losh	Remove deprecated locale names and transition period code
66674111097SWarner Losh	for them, finishing switching to the new scheme. Check your
66774111097SWarner Losh	LANG environment variable.
66874111097SWarner Losh
66974111097SWarner Losh20030609:
67074111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
67174111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
67274111097SWarner Losh	important to remember beforehand if your source tree is on
67374111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
67474111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
67574111097SWarner Losh	kernel.
67674111097SWarner Losh
67774111097SWarner Losh20030605:
6786cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
6796cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
6806cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
6816cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
6826cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
6836cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
6846cc6353fSMarcel Moolenaar
6856cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
6866cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
6876cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
6886cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
6896cc6353fSMarcel Moolenaar		:
6906cc6353fSMarcel Moolenaar
6916cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
6926cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
6936cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
6946cc6353fSMarcel Moolenaar
69552b47445SMark Murray20030505:
69652b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
69752b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
69852b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
69952b47445SMark Murray
700a26df538SWarner Losh20030502:
701a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
702a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
703a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
704a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
705a26df538SWarner Losh
7064b065e2cSDoug Barton20030501:
7074b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
7084b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
7094b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
7104b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
7114b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
7124b065e2cSDoug Barton	utilizes these old scripts has also been removed.
7134b065e2cSDoug Barton
71481cda3d9SWarner Losh20030423:
71581cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
71681cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
71781cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
71881cda3d9SWarner Losh	have until then to upgrade your kernel before updating
71981cda3d9SWarner Losh	userland.  In general, you should have a userland and
72081cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
72181cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
72281cda3d9SWarner Losh	allowances are made.
72381cda3d9SWarner Losh
72447a657d1SRuslan Ermilov20030329:
72547a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
72647a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
72747a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
72847a657d1SRuslan Ermilov
72947a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
73047a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
73147a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
73247a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
73347a657d1SRuslan Ermilov
73447a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
73547a657d1SRuslan Ermilov	    make cleandir && make obj && \
73647a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
73747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
73847a657d1SRuslan Ermilov
7395d2af00cSGregory Neil Shapiro20030208:
7405d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
7415d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
7425d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
7435d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
7445d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
7455d2af00cSGregory Neil Shapiro
7465d2af00cSGregory Neil Shapiro20030128:
7479db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
748ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
7499db58771SPoul-Henning Kamp	be removed when convenient.
7509db58771SPoul-Henning Kamp
7518d9b3f57SJake Burkholder20030126:
7528d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
7538d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
7548d9b3f57SJake Burkholder
7551c5efda5SJeff Roberson20030125:
7561c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
7571c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
758ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
7591c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
7601c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
7611c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
7621c5efda5SJeff Roberson
7639d1d64f5SWarner Losh20030115:
7649d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
7659d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
7669d1d64f5SWarner Losh	properly.
7679d1d64f5SWarner Losh
768c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
769c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
770c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
771c9fdb80aSWarner Losh	with NetBSD.
772c9fdb80aSWarner Losh
773161dc364SAlexander Kabaev20021222:
774161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
775161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
776161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
777161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
778161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
779161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
78084cc83efSAlexander Kabaev	rebuilt.
781161dc364SAlexander Kabaev
782fb4c8061SMartin Blapp20021216:
783fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
78489056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
785fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
7869d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
787fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
788fb4c8061SMartin Blapp
78917d47eb3SGiorgos Keramidas20021202:
79017d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
79117d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
79217d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
79317d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
79417d47eb3SGiorgos Keramidas
795a4459294SBill Fenner20021029:
796a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
797a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
798a4459294SBill Fenner	consumers in sync.
799a4459294SBill Fenner
800fc8c157fSWarner Losh20021024:
801c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
802c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
803c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
804c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
805c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
806c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
807c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
808c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
80969f7bcf3SWarner Losh
810fd9e8bdaSAndrew Gallatin20021023:
811fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
812fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
813fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
814fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
815fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
816fd9e8bdaSAndrew Gallatin
817fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
818fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
819fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
820fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
821fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
822fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
823fd9e8bdaSAndrew Gallatin
824f8a4c901SWarner Losh20020831:
825f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
826f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
827f8a4c901SWarner Losh	programs and libraries need to be recompiled.
828f8a4c901SWarner Losh
829f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
830f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
831f8a4c901SWarner Losh
832c2248fa2SJens Schweikhardt20020827:
833c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
834c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
835c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
836c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
837c2248fa2SJens Schweikhardt
8380d533e43SRuslan Ermilov20020815:
8390d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
8400d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
8410d533e43SRuslan Ermilov	again.
8420d533e43SRuslan Ermilov
84333c1de7dSRuslan Ermilov20020729:
84433c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
84533c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
84633c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
84733c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
84833c1de7dSRuslan Ermilov
8492b877facSJulian Elischer20020702:
8502b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
8512b877facSJulian Elischer	There are still some minor problems with some signals but the
8522b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
8532b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
8542b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
8552b877facSJulian Elischer
85606596d37SWarner Losh20020701:
85706596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
85806596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
85906596d37SWarner Losh	GNOME.
86006596d37SWarner Losh
86195ba4330SJacques Vidrine20020511:
86295ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
86395ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
86495ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
86595ba4330SJacques Vidrine	with the set-user-ID bit set.
86695ba4330SJacques Vidrine
867a81da3c9SDavid E. O'Brien20020510:
868f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
869f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
8704b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
871f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
872f50caf6fSDavid E. O'Brien
873f50caf6fSDavid E. O'Brien20020510:
874a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
875a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
876a81da3c9SDavid E. O'Brien	and then do a cvs update.
877a81da3c9SDavid E. O'Brien
878528a0ef5SJacques Vidrine20020421:
879528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
880528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
881528a0ef5SJacques Vidrine
88285aa5a2eSGregory Neil Shapiro20020404:
88385aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
88485aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
88585aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
88685aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
88785aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
88885aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
88985aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
89085aa5a2eSGregory Neil Shapiro
8918f1e4358SRuslan Ermilov20020403:
8928f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
8938f1e4358SRuslan Ermilov
8942292c02eSWarner Losh20020315:
8952292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
8962292c02eSWarner Losh
89769f7bcf3SWarner Losh20020225:
89869f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
89969f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
90069f7bcf3SWarner Losh
9018f35c493SWarner Losh20020217:
9028f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
9038f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
9048f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
9058f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
9068f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
9078f35c493SWarner Losh
908835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
909835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
910835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
911835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
912835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
913835284beSWarner Losh	and group must be merged from src/etc/group and
914835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
915835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
916835284beSWarner Losh	mergemaster before this will work if you are updating from a
917835284beSWarner Losh	very old version of current.  The updating recipe has changed
918835284beSWarner Losh	as of this date.
919835284beSWarner Losh
920fa9401c1SWarner Losh20020112:
921fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
922fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
923fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
924fa9401c1SWarner Losh	you have local modifications, you can use
925fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
926fa9401c1SWarner Losh	/etc/pam.d.
927fa9401c1SWarner Losh
928fa9401c1SWarner Losh	Please see the following url for more details:
929fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
93047d0d01fSWarner Losh20011229:
93147d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
93247d0d01fSWarner Losh	networkfs_types, please note that it has changed
93347d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
93447d0d01fSWarner Losh
935514318a8SWarner Losh20011220:
936514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
937514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
938514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
939514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
940514318a8SWarner Losh	version have now been merged back into the base system's
941514318a8SWarner Losh	version now.  The only user-visible change resulting from this
942514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
943514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
944514318a8SWarner Losh	as well.  (There has never been rc file support for
945514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
946514318a8SWarner Losh	reverted by the time the changes are MFCed.)
947514318a8SWarner Losh
948514318a8SWarner Losh20011215:
949514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
950514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
951514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
952514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
953514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
954514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
955514318a8SWarner Losh	will need to be customized then for `odd' densities using
956514318a8SWarner Losh	fdcontrol(8).
957514318a8SWarner Losh
9582d22e2bfSWarner Losh20011209:
9592d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
9602d22e2bfSWarner Losh	and truss(1) now works again.
9612d22e2bfSWarner Losh
9629e0428e2SWarner Losh20011207:
9639e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
9649e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
9659e0428e2SWarner Losh	see
9669e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
9679e0428e2SWarner Losh	for details.
9689e0428e2SWarner Losh
9699bab8c59SWarner Losh20011204:
9709bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
9719bab8c59SWarner Losh	kernel and burncd to be in sync.
9729bab8c59SWarner Losh
973e57d8b01SWarner Losh20011203:
974e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
975e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
976e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
977e57d8b01SWarner Losh	not there already.
978e57d8b01SWarner Losh
979e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
980e57d8b01SWarner Losh	until the issue has been resolved.
981e57d8b01SWarner Losh
982b001d36fSJacques Vidrine20011202:
983b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
984b001d36fSJacques Vidrine	patched.
985b001d36fSJacques Vidrine
9864b676ec1SWarner Losh20011126:
9874b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
9885ebbf43eSWarner Losh	after this date.  You need to do this only once.
9894b676ec1SWarner Losh
990d961e462SWarner Losh20011103:
991d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
992d961e462SWarner Losh	edges may be left, but for the most part things should be
9934b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
994d961e462SWarner Losh
995d961e462SWarner Losh20011030:
996d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
997d961e462SWarner Losh	choppy waves in the upgrade process.
998d961e462SWarner Losh
9991fe003b6SWarner Losh20011030:
1000a4b6fda0SWarner Losh	The asr driver problem has been resolved.
10011fe003b6SWarner Losh
10021fe003b6SWarner Losh20011027:
10031fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
10041fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
10051fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
10061fe003b6SWarner Losh	try to use from this date forward.
10071fe003b6SWarner Losh
10081fe003b6SWarner Losh20011025:
10091fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
10101fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
10111fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
10121fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
10131fe003b6SWarner Losh	TARGET_ARCH=i386.
10141fe003b6SWarner Losh
1015d05f9643SWarner Losh20011001:
1016d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
1017d05f9643SWarner Losh	You must recompile both the kernel and userland applications
1018d05f9643SWarner Losh	at the same time.
1019d05f9643SWarner Losh
102058970f85SWarner Losh20010929:
102158970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
102258970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
102358970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
102458970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
10259d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
102658970f85SWarner Losh
102758970f85SWarner Losh20010927:
102858970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
102958970f85SWarner Losh	To disable ACPI you can add
103066ff0e67SMax Khon		hint.acpi.0.disabled="1"
103158970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
103258970f85SWarner Losh	loader "ok" prompt).
103358970f85SWarner Losh
103458970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
103558970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
103658970f85SWarner Losh	file and not list acpi in that list.
1037378f4486SAlfred Perlstein
10385119d237SWarner Losh20010924:
10395119d237SWarner Losh	The buildworld has been fixed.  You may need to install
10405119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
10418b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
10428b039fffSWarner Losh	get them installed on every installworld, or execute the
10438b039fffSWarner Losh	following to get them installed only once:
10448b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
104558970f85SWarner Losh		make all install
10468b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
10475119d237SWarner Losh
10483c293725SWarner Losh20010919:
10493c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
10503c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
10513c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
1052772730c7SWarner Losh	workaround is to add
10533c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
10543c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
10553c293725SWarner Losh	can be removed afterwards.
10563c293725SWarner Losh
10573c293725SWarner Losh	A proper fix to the buildworld target is needed.
10583c293725SWarner Losh
10593c293725SWarner Losh20010918:
10603c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
10613c293725SWarner Losh	NFS may be unstable after this date.
10623c293725SWarner Losh
10633c293725SWarner Losh20010912:
10643c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
10653c293725SWarner Losh	the kernel.  While a few problems were introduced in the
10663c293725SWarner Losh	initial commit, most of the major ones have been found and
10673c293725SWarner Losh	corrected.
10683c293725SWarner Losh
10693c293725SWarner Losh20010901:
10703c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
10713c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
10723c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
10733c293725SWarner Losh	have been rectified around this date.
10743c293725SWarner Losh
107598b17b95SWarner Losh20010823:
107698b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
107798b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
107898b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
107998b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
108098b17b95SWarner Losh 	sure that user or group bind has read (and not write)
108198b17b95SWarner Losh 	permission for your name server configuration and that it
108298b17b95SWarner Losh 	has read and write permission for your slave zone files and
108398b17b95SWarner Losh 	directory.
108498b17b95SWarner Losh
108598b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
108698b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
108798b17b95SWarner Losh
108898b17b95SWarner Losh 		named_flags=
108998b17b95SWarner Losh
10907b9786edSMark Murray20010709:
10917b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
10927b9786edSMark Murray	the ability of the shared library major number to handle.
10937b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
10947b9786edSMark Murray	solution is to rebuild those ports.
10957b9786edSMark Murray
10961d28950eSWarner Losh20010628:
10971d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
10981d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
10991d28950eSWarner Losh
1100e72fd46aSWarner Losh20010625:
110198b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
110298b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
110398b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
110498b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
110598b17b95SWarner Losh	IRQ configuration needs more safety belts.
110616de1a07SWarner Losh
11070d415dffSWarner Losh20010617:
1108e72fd46aSWarner Losh	Softupdates problems have been corrected.
11090d415dffSWarner Losh
11100d415dffSWarner Losh20010614:
11110d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
11120d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
11130d415dffSWarner Losh	kernel building methods.
11140d415dffSWarner Losh
11158b9959adSWarner Losh20010613:
11168b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
11178b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
1118e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
1119e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
11208b9959adSWarner Losh
1121e72fd46aSWarner Losh20010613:
11228b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
1123e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
1124e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
11258b9959adSWarner Losh
11260d415dffSWarner Losh20010612:
11270d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
11280d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
11290d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
11300d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
11310d415dffSWarner Losh	until this bug is fixed.
11320d415dffSWarner Losh
1133e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
1134e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
1135ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
1136e72fd46aSWarner Losh
11370d415dffSWarner Losh20010610:
11380d415dffSWarner Losh	Locale names have changed to match other systems better.
11390d415dffSWarner Losh
11406ccdb5e4SWarner Losh20010604:
11416ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
11426ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
11436ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
11443590182eSWarner Losh	Interrupt storms look a lot like a hang.
11453590182eSWarner Losh
11463590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
11473590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
11483590182eSWarner Losh	it is).
11493590182eSWarner Losh
11503590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
11513590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
11523590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
11533590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
11546ccdb5e4SWarner Losh
11550bc62786SWarner Losh20010530:
11560bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
11570bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
11580bc62786SWarner Losh	a limited time.  If you see
11590bc62786SWarner Losh
11600bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
11610bc62786SWarner Losh
11620bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
11630bc62786SWarner Losh	COPY=-C.
11640bc62786SWarner Losh
116568a38c6cSWarner Losh20010525:
1166b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
1167c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
1168c4f4a728SWarner Losh	definitely is in bad shape.
116968a38c6cSWarner Losh
1170ed0f29caSWarner Losh20010521:
1171ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
1172ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
1173ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1174ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
1175ed0f29caSWarner Losh	is
1176ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1177ed0f29caSWarner Losh
117880c16af9SWarner Losh20010520:
117968a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
118080c16af9SWarner Losh
118180c16af9SWarner Losh20010519:
118280c16af9SWarner Losh	pccard has had much reorganizational work done to it over
118380c16af9SWarner Losh	the past few days.  Everything should still work, but if
118480c16af9SWarner Losh	not, please contact imp@freebsd.org.
118580c16af9SWarner Losh
1186a45f2d05SWarner Losh20010517:
1187a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
1188a45f2d05SWarner Losh	userland at the same time.
1189a45f2d05SWarner Losh
1190a45f2d05SWarner Losh20010517:
1191a45f2d05SWarner Losh	New ncurses imported.
1192a45f2d05SWarner Losh
11932988afcaSWarner Losh20010512:
11942988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
11952988afcaSWarner Losh	will be the only way to go starting July 1.
11962988afcaSWarner Losh
11971a33dba7SWarner Losh20010504:
11981a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
11991a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
12001a33dba7SWarner Losh
120109946a51SWarner Losh20010502:
120209946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
120309946a51SWarner Losh
120409946a51SWarner Losh20010501:
120509946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
120609946a51SWarner Losh
120709946a51SWarner Losh20010430:
1208a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
120909946a51SWarner Losh	go back in the water.
121009946a51SWarner Losh
121109946a51SWarner Losh20010429:
121209946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
121309946a51SWarner Losh	this date, but before the correction date.
121409946a51SWarner Losh
121591dd3b53SWarner Losh20010423:
121691dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
121791dd3b53SWarner Losh
121891dd3b53SWarner Losh20010411:
121991dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
122091dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
122191dd3b53SWarner Losh	Update only if you understand that you must not use the old
122291dd3b53SWarner Losh	fsck with the new kernel ever.
122391dd3b53SWarner Losh
1224933b3269SWarner Losh20010330:
1225933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1226c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1227933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1228933b3269SWarner Losh
1229933b3269SWarner Losh20010319:
1230933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1231933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1232933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1233f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
123409946a51SWarner Losh
123509946a51SWarner Losh20010315:
123609946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1237ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
123809946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1239933b3269SWarner Losh
1240933b3269SWarner Losh20010312:
1241933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1242933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1243933b3269SWarner Losh
1244933b3269SWarner Losh20010312:
1245933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1246933b3269SWarner Losh	instead of ad-hoc.
1247933b3269SWarner Losh
1248933b3269SWarner Losh20010310:
1249f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1250933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1251933b3269SWarner Losh	ssh might not work if you don't.
1252933b3269SWarner Losh
125362353691SWarner Losh20010303:
125462353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
125562353691SWarner Losh	which means that you must include the miibus in your kernel if
125662353691SWarner Losh	you use the ed driver.
125762353691SWarner Losh
1258d325cf65SWarner Losh20010220:
1259d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1260d325cf65SWarner Losh	safe to go back into the water.
1261d325cf65SWarner Losh
1262024daae6SWarner Losh20010211:
1263024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1264024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1265024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1266024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1267024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1268024daae6SWarner Losh
1269024daae6SWarner Losh	To get to the new system, you'll need to use the following
1270024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1271024daae6SWarner Losh	don't have to move this to the updating section.
1272024daae6SWarner Losh
1273024daae6SWarner Losh	To get around the installworld problem, do:
1274024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1275024daae6SWarner Losh		# make install
1276024daae6SWarner Losh		# cd /usr/src
1277024daae6SWarner Losh		# make installworld
1278024daae6SWarner Losh	If that doesn't work, then try:
1279024daae6SWarner Losh		# make -k installworld
1280024daae6SWarner Losh		# make installworld
1281024daae6SWarner Losh
1282024daae6SWarner Losh20010207:
1283024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1284024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1285024daae6SWarner Losh
1286024daae6SWarner Losh20010205:
12877595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1288024daae6SWarner Losh	Remove them from your config.
1289024daae6SWarner Losh
12901e159248SWarner Losh20010122:
12911e159248SWarner Losh	****************************** WARNING ******************************
12921e159248SWarner Losh			buildkernel has been changed slightly
12931e159248SWarner Losh	****************************** WARNING ******************************
12941e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
12951e159248SWarner Losh	should update your scripts and make.conf accordingly.
12961e159248SWarner Losh
12971e159248SWarner Losh20010119:
12981e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
12991e159248SWarner Losh	This requires a new config to build correctly.
13001e159248SWarner Losh
1301aac7dfeaSWarner Losh20010116:
1302ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1303aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1304aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1305aac7dfeaSWarner Losh
1306aac7dfeaSWarner Losh20010110:
1307aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1308aac7dfeaSWarner Losh
1309aac7dfeaSWarner Losh20010102:
1310aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1311aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1312aac7dfeaSWarner Losh
131363c90c9eSWarner Losh20010101:
131463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
131563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
13165fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
131763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
131863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
131963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
132063c90c9eSWarner Losh	might have been ignored by the -k option.
132163c90c9eSWarner Losh
13225fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
13235fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
13245fd2a895SWarner Losh	of this working.
13255fd2a895SWarner Losh
1326aac7dfeaSWarner Losh20001228:
1327aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1328ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1329aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1330aac7dfeaSWarner Losh
1331de2bcc63SWarner Losh20001218:
1332de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1333de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1334de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1335de2bcc63SWarner Losh	cards will not be recognized without it.
1336de2bcc63SWarner Losh
1337960773f7SWarner Losh20001205:
1338960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1339960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1340960773f7SWarner Losh	adding the following in pam.conf:
1341960773f7SWarner Losh
1342960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1343960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1344960773f7SWarner Losh	sshd    session required        pam_permit.so
1345960773f7SWarner Losh
13460acc635eSWarner Losh20001031:
13470acc635eSWarner Losh	cvs updated to 1.11.
13480acc635eSWarner Losh
13490acc635eSWarner Losh20001020:
13500acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
13510acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
13520acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
13530acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
13540acc635eSWarner Losh	workaround.
13550acc635eSWarner Losh
13560acc635eSWarner Losh20001010:
13570acc635eSWarner Losh	****************************** WARNING ******************************
13580acc635eSWarner Losh				Sendmail has been updated.
13590acc635eSWarner Losh	****************************** WARNING ******************************
13600acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
13610acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
13620acc635eSWarner Losh	  is set.
13630acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
13640acc635eSWarner Losh	  commands.
13650acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
13660acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
13670acc635eSWarner Losh	  in /usr/share/sendmail/cf.
13680acc635eSWarner Losh	o sendmail.cw changed to local-host-names
13690acc635eSWarner Losh
13700acc635eSWarner Losh	More details can be found at
13710acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
13720acc635eSWarner Losh
13736e98a146SWarner Losh20001009:
13746e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
13756e98a146SWarner Losh	your entire ports tree, or you will have problems.
13766e98a146SWarner Losh
13776e98a146SWarner Losh20001006:
1378685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
13796e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
13806e98a146SWarner Losh	/usr/bin/miniperl.
13816e98a146SWarner Losh
1382073113a4SWarner Losh20001005:
1383073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1384685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1385073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1386073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1387073113a4SWarner Losh	tree for anything to work.
1388073113a4SWarner Losh
13890acc635eSWarner Losh20000928:
13900acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
13910acc635eSWarner Losh
1392be3885b3SWarner Losh20000916:
1393be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1394be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1395be3885b3SWarner Losh	same time as your kernel.
1396be3885b3SWarner Losh
139776ec9675SWarner Losh20000914:
139876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
139976ec9675SWarner Losh	include the device will cause suspended laptops losing time
140076ec9675SWarner Losh	when they resume.  Include
140176ec9675SWarner Losh		device		pmtimer
140276ec9675SWarner Losh	in your config file and
140301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
140476ec9675SWarner Losh	to your /boot/device.hints file.
140576ec9675SWarner Losh
1406f4865386SMark Murray20000911:
1407f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1408f4865386SMark Murray	rather than an option. The supplied kernel config files have
1409f4865386SMark Murray	been updated. You will need to do something similar in your
1410f4865386SMark Murray	own kernel config file.
1411f4865386SMark Murray	Remove:
1412f4865386SMark Murray		options		RANDOMDEV
1413f4865386SMark Murray	Add:
1414f4865386SMark Murray		device		random
1415f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1416f4865386SMark Murray	nothing.
1417f4865386SMark Murray
1418d594498fSWarner Losh20000909:
1419d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1420d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1421d594498fSWarner Losh	reflect this if you load this module at boot time.
1422d594498fSWarner Losh	The line should read:
1423d594498fSWarner Losh		random_load="YES"
1424d594498fSWarner Losh
14250deb7ddcSWarner Losh20000907:
14260deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
142716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
142816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
142916eb772dSWarner Losh	sure you don't have model loading problems which might at
143016eb772dSWarner Losh	first blush appear related to SMP.
143152bf24e7SWarner Losh
14325a01880bSWarner Losh20000906:
14335a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
14345a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
14355a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
14365a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
14375a01880bSWarner Losh	don't have one, and you have host.conf.
14385a01880bSWarner Losh
14392b41163cSWarner Losh20000905:
144038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
144138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
144238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
144338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
144438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
144538d6ecd2SWarner Losh
144638d6ecd2SWarner Losh20000905:
14478aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
14488aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
14498aab4bc7SWarner Losh	is /boot/kernel.
14508aab4bc7SWarner Losh
14518aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
145238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
145338d6ecd2SWarner Losh	installkernel/installworld dance.
14542b41163cSWarner Losh
1455d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1456d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1457d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1458d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1459d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1460d594498fSWarner Losh
1461d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1462d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1463d594498fSWarner Losh		chflags noschg /kernel.old
1464d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1465d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1466d594498fSWarner Losh	fi
1467d594498fSWarner Losh
1468c22a309cSWarner Losh20000904:
1469c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1470c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1471c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1472c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1473c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1474c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1475c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1476c22a309cSWarner Losh	is not likely to be generated.
1477c22a309cSWarner Losh
1478fdb9f54dSWarner Losh20000825:
1479fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
14809c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
14819c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
14829c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
14839c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
14849c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
14859c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
14869c1a7444SWarner Losh	kernel.
14879c1a7444SWarner Losh
14889c1a7444SWarner Losh20000821:
14899c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
14909c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
14919c1a7444SWarner Losh	/boot/loader.conf.
1492fdb9f54dSWarner Losh
14938f250aa7SWarner Losh20000812:
14945da0d091SWarner Losh	suidperl is now always built and installed on the system, but
14955da0d091SWarner Losh	with permissions of 511.  If you have applications that use
14965da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
14975da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
14985da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
14995da0d091SWarner Losh	will fix this until the next build.
15005da0d091SWarner Losh
15015da0d091SWarner Losh20000812:
15028f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
15038f250aa7SWarner Losh	visible changes that may immediately affect your configuration
15048f250aa7SWarner Losh	include:
15058f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
15068f250aa7SWarner Losh	- newaliases limited to root and trusted users
15078f250aa7SWarner Losh	- MSA port (587) turned on by default
15088f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
15098f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
15108f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
15118f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
15128f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
15138f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
15148f250aa7SWarner Losh
151571c38472SWarner Losh20000810:
151671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
151771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
151871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
151971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
152071c38472SWarner Losh	specific use for it.
152171c38472SWarner Losh
152271c38472SWarner Losh20000729:
152371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
152471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
152571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
152671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
152771c38472SWarner Losh		# Enable network daemons for user convenience.
152871c38472SWarner Losh		inetd_enable="YES"
152971c38472SWarner Losh		portmap_enable="YES"
153071c38472SWarner Losh		sendmail_enable="YES"
153171c38472SWarner Losh
153271c38472SWarner Losh20000728:
153371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
153471c38472SWarner Losh	will need to change that to nullfs_load="YES".
153571c38472SWarner Losh
15361dece4a9SWarner Losh20000728:
15371dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
15381dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
15391dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
15401dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
15411dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
15421dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
15431dece4a9SWarner Losh	to /MYKERNEL.
15441dece4a9SWarner Losh
1545409e887cSWarner Losh20000711:
1546409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1547409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1548409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1549409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1550409e887cSWarner Losh	for details on potential problems that you might have and how
1551409e887cSWarner Losh	to get around them.
1552409e887cSWarner Losh
1553409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1554409e887cSWarner Losh	clauses above, you needn't worry.
1555409e887cSWarner Losh
1556409e887cSWarner Losh20000711:
1557409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1558409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1559409e887cSWarner Losh	in the number of changed programs the first time when you run
1560409e887cSWarner Losh	mergemaster to get a new /etc/security.
1561409e887cSWarner Losh
1562673d13f2SWarner Losh20000710:
1563673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1564673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1565673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1566673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1567673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1568673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1569673d13f2SWarner Losh	errors. (see below, 20000624).
1570673d13f2SWarner Losh
1571bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
15721dece4a9SWarner Losh
1573673d13f2SWarner Losh20000709:
1574c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1575c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1576c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1577673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1578673d13f2SWarner Losh
1579e98e26cdSWarner Losh20000706:
1580e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1581e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1582e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1583f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1584e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
15852c021c6cSMark Ovens	interim if needed.
1586e98e26cdSWarner Losh
1587e98e26cdSWarner Losh20000705:
1588e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1589e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1590e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1591e98e26cdSWarner Losh	details.
1592e98e26cdSWarner Losh
1593c373950eSWarner Losh20000704:
15942f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
15952f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
15962f961bc8SWarner Losh
15972f961bc8SWarner Losh20000704:
1598c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1599c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1600c373950eSWarner Losh	rc.d scripts that haven't been updated.
1601c373950eSWarner Losh
160227dc3a2bSWarner Losh20000630:
160327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
160427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
160527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
160627dc3a2bSWarner Losh
1607b8c215acSWarner Losh20000625:
1608b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
160927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
161027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
161127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
161227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
161327dc3a2bSWarner Losh	were required.  You should check with the latest collections
161427dc3a2bSWarner Losh	to make sure that these haven't changed.
1615b8c215acSWarner Losh
16167b990719SWarner Losh20000624:
16177b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
16187b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
16197b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
16201a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
16217b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
16227b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
16237b990719SWarner Losh	date to the completion of the work.
16247b990719SWarner Losh
162527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
162627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
162727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
162827dc3a2bSWarner Losh	recreate the random and urandom devices.
162927dc3a2bSWarner Losh
163081e54c50SWarner Losh20000622:
163181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
163281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
163381e54c50SWarner Losh	that used to be required when updating.
163481e54c50SWarner Losh
163539943833SWarner Losh20000621:
16362c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
16372a2f33fbSDaniel Baker	the config file update procedure.
16382a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1639c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
164059df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
164159df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
164239943833SWarner Losh
1643290f9ad8SWarner Losh20000620:
1644290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1645290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1646290f9ad8SWarner Losh	that workaround will no longer be required.
1647290f9ad8SWarner Losh
164890fb6346SWarner Losh20000615:
164990fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
165090fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
165190fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
165290fb6346SWarner Losh	devices.
165390fb6346SWarner Losh
1654f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1655f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1656f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1657f75f65bbSWarner Losh	may work).
1658f75f65bbSWarner Losh
1659ba26da8eSWarner Losh20000612:
1660ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1661290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1662c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1663290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1664f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1665f54a3542SWarner Losh	NEWCARD for examples of the new format.
1666290f9ad8SWarner Losh
16679698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
16689698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
16699698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
16709698f2c0SWarner Losh	in it.
1671bbcc5149SWarner Losh
1672d65850ebSWarner Losh20000522:
1673ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1674d65850ebSWarner Losh	building a kernel after this point is advised that they need
1675d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1676d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1677d65850ebSWarner Losh
1678d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1679d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1680d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1681d9583a00SWarner Losh	is resolved.
1682d9583a00SWarner Losh
16838039cedeSWarner Losh20000513:
16848039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
16858039cedeSWarner Losh
1686d65850ebSWarner Losh20000510:
16878039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
16888039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
16898039cedeSWarner Losh	is requires for the boot blocks to build properly.
16908039cedeSWarner Losh
16918039cedeSWarner Losh20000503:
16928039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
16938039cedeSWarner Losh	is now available.
16948039cedeSWarner Losh
1695d65850ebSWarner Losh20000502:
1696d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1697d65850ebSWarner Losh	connected to the kernel building instead.
1698d65850ebSWarner Losh
1699be149406SNik Clayton20000427:
17008039cedeSWarner Losh	You may need to build gperf
17018039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
17028039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
17038039cedeSWarner Losh	an option only in -current.
17048039cedeSWarner Losh
17052b8dd5f4SWarner Losh20000417:
17062b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1707f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
17082b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
17092b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
17102c021c6cSMark Ovens	before you reboot, you'll need to issue:
17112b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
17122b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
17132b8dd5f4SWarner Losh
17148d9f1945SWarner Losh20000320:
17152b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
17162b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
17172b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1718ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
17192b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
17208d9f1945SWarner Losh
1721f8ab1dd6SWarner Losh20000319:
1722f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1723f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1724f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1725f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1726f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1727f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1728f8ab1dd6SWarner Losh
172919cada77SWarner Losh20000318:
1730f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
173119cada77SWarner Losh	Large kernel changes are being committed and are in the
173219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
173319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
173419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
173519cada77SWarner Losh	that you are loading are up to date.
1736ba228352SWarner Losh
173719cada77SWarner Losh20000315:
17386d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
17396d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
17406d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
17416d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
17426d23c382SWarner Losh	boot.
17436d23c382SWarner Losh
17446d23c382SWarner Losh20000315:
174519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
174619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
174757199806SWarner Losh
1748dc0dbf5cSWarner LoshCOMMON ITEMS:
1749dc0dbf5cSWarner Losh
1750cd5f061cSWarner Losh	# NOTE: 5.x below applies to 6.0-currrent as well, for the
1751cd5f061cSWarner Losh	# momemnt.  4.any -> 5.any upgrade support will remain in
1752cd5f061cSWarner Losh	# place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1753cd5f061cSWarner Losh	# 6.0-current upgrade path will require moving through 5.3
1754cd5f061cSWarner Losh	# RELEASE or newer.
1755cd5f061cSWarner Losh
1756a24eff53SWarner Losh	General Notes
1757a24eff53SWarner Losh	-------------
1758a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1759a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1760a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1761a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1762a24eff53SWarner Losh	or several minor releases, or when several months have passed
1763a24eff53SWarner Losh	on the -current branch).
1764a24eff53SWarner Losh
17655780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
17665780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
17675780f3baSWarner Losh	environment when searching for values for global variables.
17685780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
17695780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
17705780f3baSWarner Losh	page for more details.
17715780f3baSWarner Losh
1772dc0dbf5cSWarner Losh	To build a kernel
1773dc0dbf5cSWarner Losh	-----------------
1774ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1775f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1776ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1777282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1778282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1779dc0dbf5cSWarner Losh
1780ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1781ba01eb20SWarner Losh	--------------------------------------------------------------
17820fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
17830fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
17840fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
17850fbd2da9SKen Smith
17860fbd2da9SKen Smith	cd src/sys/${arch}/conf
178747d0d01fSWarner Losh	config KERNEL_NAME_HERE
17880fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1789ba01eb20SWarner Losh	make depend
1790ba01eb20SWarner Losh	make
1791ba01eb20SWarner Losh	make install
1792ba01eb20SWarner Losh
1793ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1794ba01eb20SWarner Losh
1795ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1796ba01eb20SWarner Losh	-----------------------------------------------------------
179763cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
179863cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
179963cb445eSWarner Losh
1800f643de42SWarner Losh	<make sure you have good level 0 dumps>
180163cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
180263cb445eSWarner Losh	make buildworld
18036586253aSWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE
180463cb445eSWarner Losh							[1]
180563cb445eSWarner Losh	<reboot in single user>				[3]
18066586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
180763cb445eSWarner Losh	mergemaster -p					[5]
180863cb445eSWarner Losh	make installworld
180963cb445eSWarner Losh	mergemaster					[4]
181063cb445eSWarner Losh	<reboot>
181163cb445eSWarner Losh
1812759f0aefSWarner Losh
1813f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1814f27b1fceSJoseph Koshy	--------------------------------------------------
1815f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1816f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1817f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1818f27b1fceSJoseph Koshy	# size.
1819f27b1fceSJoseph Koshy
1820f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1821f27b1fceSJoseph Koshy	<boot into -stable>
1822f27b1fceSJoseph Koshy	make buildworld
1823f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1824f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1825f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1826f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
18276586253aSWarner Losh	cp src/sys/${ARCH}/conf/GENERIC.hints \
1828f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1829f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
18306586253aSWarner Losh	cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1831f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1832f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1833f27b1fceSJoseph Koshy	<reboot into current>
1834f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
18356586253aSWarner Losh	<maybe install compatibility libraries from src/lib/compat>
1836f27b1fceSJoseph Koshy 	<reboot>
1837f27b1fceSJoseph Koshy
1838f27b1fceSJoseph Koshy
1839f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1840f27b1fceSJoseph Koshy	----------------------------------------------
18415c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
1842e5dc5f61SWarner Losh	# modules has changed.  If you are installing 5.x onto a 4.x
18435c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
18445c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1845ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1846f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1847f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1848f643de42SWarner Losh	# space on /.
1849f643de42SWarner Losh
1850f643de42SWarner Losh	<make sure you have good level 0 dumps>
1851fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
185221c075eaSWarner Losh	make buildworld					[9]
1853802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1854e5dc5f61SWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
1855802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install		[6]
1856fc8c157fSWarner Losh							[1]
1857fc8c157fSWarner Losh	<reboot in single user>				[3]
18586586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
1859835284beSWarner Losh	mergemaster -p					[5]
1860f8a4c901SWarner Losh	rm -rf /usr/include/g++
1861ba26da8eSWarner Losh	make installworld
1862802fc49dSBrian Feldman	mergemaster -i					[4]
1863ba26da8eSWarner Losh	<reboot>
1864ba26da8eSWarner Losh
1865fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1866fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1867fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1868fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1869fdb9f54dSWarner Losh	the UPDATING entries.
1870ba26da8eSWarner Losh
18711dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
18721dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
18731dece4a9SWarner Losh	your sources that you have read and understood all the recent
18741dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
18751dece4a9SWarner Losh	much fewer pitfalls.
18761dece4a9SWarner Losh
1877134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1878134d2e86SWarner Losh	should disable them at this point so they don't crash your
1879134d2e86SWarner Losh	system on reboot.
1880134d2e86SWarner Losh
18819c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
18829c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
18839c1a7444SWarner Losh	configuration.
18849c1a7444SWarner Losh
1885ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1886ee6e1fc3SWarner Losh		fsck -p
1887ee6e1fc3SWarner Losh		mount -u /
1888ee6e1fc3SWarner Losh		mount -a
18896586253aSWarner Losh		cd src
189047d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1891f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1892f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
189366986952SRuslan Ermilov	For the 4.x -> 5.x upgrade, you will also see many messages about
1894b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1895b705ae10SWarner Losh	be ignored while you proceed to the next step.
1896ee6e1fc3SWarner Losh
1897a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1898a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1899a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1900a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1901a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1902a6cd4f9dSWarner Losh	for potential gotchas.
1903a6cd4f9dSWarner Losh
1904835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1905835284beSWarner Losh	you may need to do this if you get unknown user in the following
1906835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1907835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1908835284beSWarner Losh	install) after the buildworld before this step if you last updated
1909835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1910835284beSWarner Losh
1911bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1912bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1913bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1914bd79cf40SWarner Losh		ok unload
1915bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1916bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1917bd79cf40SWarner Losh	described here.
1918fc8c157fSWarner Losh
1919fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1920e5dc5f61SWarner Losh	compatibility slices.  These are device names of the form /dev/ad0a
1921e5dc5f61SWarner Losh	without the actual slice name.  These will break with 5.x and newer.
1922fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1923e5dc5f61SWarner Losh	2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1924e5dc5f61SWarner Losh	is not.
1925fc8c157fSWarner Losh
1926c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1927c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1928c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1929c74fe6afSWarner Losh	that is hard to boot to recover.
1930c74fe6afSWarner Losh
1931e5dc5f61SWarner Losh	Make sure that you merge any new devices from GENERIC since the
1932e5dc5f61SWarner Losh	last time you updated your kernel config file.
1933e5dc5f61SWarner Losh
193421c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1935e5dc5f61SWarner Losh	cvs prune empty directories.
1936e5dc5f61SWarner Losh
1937e5dc5f61SWarner Losh	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1938e5dc5f61SWarner Losh	"?=" instead of the "=" assignment operator, so that buildworld can
1939e5dc5f61SWarner Losh	override the CPUTYPE if it needs to.
1940e5dc5f61SWarner Losh
1941e5dc5f61SWarner Losh	MAKEOBJDIRPREFIX must be defined in an environment variable, and
1942e5dc5f61SWarner Losh	not on the command line, or in /etc/make.conf.  buildworld will
1943e5dc5f61SWarner Losh	warn if it is improperly defined.
1944e5dc5f61SWarner Losh
1945802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1946802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
194766986952SRuslan Ermilov	compatibility libraries are built which should allow you to continue
1948e5dc5f61SWarner Losh	using your existing software for a while.  Alternatively, you can
1949e5dc5f61SWarner Losh	install the misc/compat4x port.
19508633bbeaSBrooks Davis
19518633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
19526586253aSWarner Losh	initialized by feeding data into it.  src/etc/rc.d/preseedrandom
19538633bbeaSBrooks Davis	takes care of this.
1954dc0dbf5cSWarner LoshFORMAT:
1955dc0dbf5cSWarner Losh
1956f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
19571fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1958f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1959f8ab1dd6SWarner Loshprevious releases if your system is older than this.
19601fc1a0dcSWarner Losh
1961e72fd46aSWarner LoshCopyright information:
1962e72fd46aSWarner Losh
1963e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh.  All Rights Reserved.
1964e72fd46aSWarner Losh
1965772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1966772730c7SWarner Loshmodification, in full or in part, in any form or format of this
19679698f2c0SWarner Loshdocument are permitted without further permission from the author.
1968e72fd46aSWarner Losh
1969e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1970e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1971e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1972e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1973e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1974e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1975e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1976e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1977e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1978e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1979e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1980e72fd46aSWarner Losh
1981e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1982e72fd46aSWarner Loshauthor a beer.
1983e72fd46aSWarner Losh
198422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1985772730c7SWarner Loshthis document.
1986772730c7SWarner Losh
198797d92980SPeter Wemm$FreeBSD$
1988