xref: /freebsd/UPDATING (revision d6a8d588758b384d3fbf57425b886754c9ed710d)
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
26d6a8d588SMax Laier20040929:
27d6a8d588SMax Laier	The pfil API has gained an additional argument to pass an inpcb.
28d6a8d588SMax Laier	You should rebuild all pfil consuming modules: ipfw, ipfilter
29d6a8d588SMax Laier	and pf.
30d6a8d588SMax Laier
318f1bb389SDoug Barton20040928:
328f1bb389SDoug Barton	If enabled, the default is now to run named in a chroot
338f1bb389SDoug Barton	"sandbox." For users with existing configurations in
348f1bb389SDoug Barton	/etc/namedb the migration should be simple. Upgrade your
358f1bb389SDoug Barton	world as usual, then after installworld but before
368f1bb389SDoug Barton	mergemaster do the following:
378f1bb389SDoug Barton
38d6ec7d8cSDoug Barton	/etc/rc.d/syslogd stop
398f1bb389SDoug Barton	If named is running: /etc/rc.d/named stop
408f1bb389SDoug Barton	cd /etc
418f1bb389SDoug Barton	mv namedb namedb.bak
428f1bb389SDoug Barton	mkdir -p /var/named/etc/namedb
438f1bb389SDoug Barton	cp -Rp namedb.bak/* /var/named/etc/namedb/
448f1bb389SDoug Barton	mergemaster (with your usual options)
458f1bb389SDoug Barton	If using the generated localhost* files:
468f1bb389SDoug Barton		cd /var/named/etc/namedb
478f1bb389SDoug Barton		/bin/sh make-localhost
488f1bb389SDoug Barton		rm -f localhost-v6.rev localhost.rev
49d6ec7d8cSDoug Barton	/etc/rc.d/syslogd start
508f1bb389SDoug Barton	/etc/rc.d/named start
518f1bb389SDoug Barton
528f1bb389SDoug Barton	If you are using a custom configuration, or if you have
538f1bb389SDoug Barton	customised the named_* variables in /etc/rc.conf[.local]
548f1bb389SDoug Barton	then you may have to adjust the instructions accordingly.
558f1bb389SDoug Barton	It is suggested that you carefully examine the new named
568f1bb389SDoug Barton	variables in /etc/defaults/rc.conf and the options in
578f1bb389SDoug Barton	/var/named/etc/namedb/named.conf to see if they might
588f1bb389SDoug Barton	now be more suitable.
598f1bb389SDoug Barton
605d36721aSDoug Barton20040925:
615d36721aSDoug Barton	BIND 9 has been imported into the base, and is now fully
625d36721aSDoug Barton	functional. BIND 8 has now been removed. There are numerous
635d36721aSDoug Barton	differences between BIND 8 and 9, and users with critical
645d36721aSDoug Barton	named installations should read the migration documentation
655d36721aSDoug Barton	in /usr/share/doc/bind9/misc/migration. There is also a
665d36721aSDoug Barton	new instruction manual in /usr/share/doc/bind9/arm.
675d36721aSDoug Barton
685d36721aSDoug Barton	The key differences that most users will experience are in
695d36721aSDoug Barton	how picky BIND 9 is about zone file format. If you are using
705d36721aSDoug Barton	named as a resolving (caching) name server, you will likely
715d36721aSDoug Barton	not have trouble.
725d36721aSDoug Barton
73f50b1bdbSDoug Barton	The following files are part of the old BIND 8 installation
74f50b1bdbSDoug Barton	and should be removed:
75f50b1bdbSDoug Barton	/usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
76f50b1bdbSDoug Barton	/usr/sbin/named.restart /usr/sbin/ndc
77f50b1bdbSDoug Barton
78f50b1bdbSDoug Barton	The following files have moved to /usr/bin, and should be
79f50b1bdbSDoug Barton	removed from their old locations:
80f50b1bdbSDoug Barton	/usr/sbin/nslookup /usr/sbin/nsupdate
81f50b1bdbSDoug Barton
82f5ee5a8bSMax Laier20040914:
83f5ee5a8bSMax Laier	The format of the pflogd(8) logfile "/var/log/pflog" has changed for
84f5ee5a8bSMax Laier	architectures that have a 64 bit long type to make it compatible to
85f5ee5a8bSMax Laier	the standard pcap format. In order to prevent corruption move away
86f5ee5a8bSMax Laier	any old logfile before using a new pflogd(8).
87f5ee5a8bSMax Laier
88d698cdb3SJohn-Mark Gurney20040906:
89d698cdb3SJohn-Mark Gurney	debug.witness_* has been renamed to debug.witness.*.  There are
90d698cdb3SJohn-Mark Gurney	compatibility tunables left in for a few days.  Update loader.conf
91d698cdb3SJohn-Mark Gurney	as necessary.
92d698cdb3SJohn-Mark Gurney
934ff62bd9SBrooks Davis20040902:
944ff62bd9SBrooks Davis	The ifi_epoch change has been reverted because the ABI breakage
954ff62bd9SBrooks Davis	was too extensive.  If you are running with a kernel/userland
964ff62bd9SBrooks Davis	containing the initial change (20040830), you should heed the
974ff62bd9SBrooks Davis	warning about ifconfig incompatibility when upgrading again.
984ff62bd9SBrooks Davis	With this change, 5.3 and 6.0 ifconfigs and kernels are once
994ff62bd9SBrooks Davis	again interoperable.
1004ff62bd9SBrooks Davis
1011fc4519bSBrooks Davis20040830:
1021fc4519bSBrooks Davis	A new variable, ifi_epoch, has been added to struct if_data
1031fc4519bSBrooks Davis	which is part if struct ifnet.  This means all network drivers
1041fc4519bSBrooks Davis	and network monitoring applications need to be recompiled.
1051fc4519bSBrooks Davis
1063789fb75SBrooks Davis        WARNING WARNING WARNING WARNING WARNING WARNING WARNING
1073789fb75SBrooks Davis
1083789fb75SBrooks Davis        This also breaks ifconfig compatibility.  An old ifconfig will
1093789fb75SBrooks Davis        not work with the new kernel and a new ifconfig will not work
1103789fb75SBrooks Davis        with the old.  It is strongly recommended that you make a copy
1113789fb75SBrooks Davis        of your old ifconfig before installworld.  If you are installing
1123789fb75SBrooks Davis        remotely, you must copy over a new ifconfig before rebooting in
1133789fb75SBrooks Davis        to the new kernel.
1143789fb75SBrooks Davis
115c1c94d5cSRobert Watson20040828:
116c1c94d5cSRobert Watson	The default configuration for the network stack has been changed
117c1c94d5cSRobert Watson	such that it now runs without the Giant lock unless configured
118c1c94d5cSRobert Watson	otherwise.  If you experience network-related instability, you
119c1c94d5cSRobert Watson	may wish to try setting "debug.mpsafenet=0" or compiling the
120c1c94d5cSRobert Watson	kernel with "options NET_WITH_GIANT".  Details on the netperf
121c1c94d5cSRobert Watson	project may be found at:
122c1c94d5cSRobert Watson
123c1c94d5cSRobert Watson	    http://www.watson.org/~robert/freebsd/netperf/
124c1c94d5cSRobert Watson
125c1c94d5cSRobert Watson	Including the 20040828 announcement of configuration change
126c1c94d5cSRobert Watson	details.
127c1c94d5cSRobert Watson
128c21fd232SAndre Oppermann20040827:
129c21fd232SAndre Oppermann	PFIL_HOOKS are a fixed part of the network stack now and do not
130c21fd232SAndre Oppermann	need to be specified in the kernel configuration file anymore.
131c21fd232SAndre Oppermann
132f036d408SJulian Elischer20040819:
133f036d408SJulian Elischer	Netgraph changed its message format slightly to align the data
134f036d408SJulian Elischer	portion well on 64 bit machines.
135f036d408SJulian Elischer	Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
136f036d408SJulian Elischer	pppoed, bluetooth, ATM) should be recompiled when a new kernel
137f036d408SJulian Elischer	is installed.
138f036d408SJulian Elischer
139b067abfaSAndre Oppermann20040817:
1400ce70eb4SAndre Oppermann	IPFW has been converted to use PFIL_HOOKS.  This change is
141b067abfaSAndre Oppermann	transparent to userland and preserves the ipfw ABI.  The ipfw
142b067abfaSAndre Oppermann	core packet inspection and filtering functions have not been
143b067abfaSAndre Oppermann	changed, only how ipfw is invoked is different.  Note that
144b067abfaSAndre Oppermann	"option PFIL_HOOKS" is required to use IPFIREWALL compiled
145b067abfaSAndre Oppermann	into the kernel or as KLD.
146b067abfaSAndre Oppermann
147f13a7951SDavid Malone20040814:
148f13a7951SDavid Malone	The RANDOM_IP_ID option has been replaced by the sysctl
149f13a7951SDavid Malone	net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
150f13a7951SDavid Malone	you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
151f13a7951SDavid Malone
1523a004637SMax Laier20040807:
1533a004637SMax Laier	The size of 'struct ifnet' has changed due to the addition of the
1543a004637SMax Laier	if_carp placeholder.  All kernel modules implementing network
1553a004637SMax Laier	interfaces must be recompiled as a result.
1563a004637SMax Laier
1574f34d8d1SJohn-Mark Gurney20040806:
1584f34d8d1SJohn-Mark Gurney	Module loading has been fixed.  Some older installations will
159ac41c814SRuslan Ermilov	drop proper module_path initialization and modules will fail to
1604f34d8d1SJohn-Mark Gurney	load properly.  If you have a line in /boot/loader.rc that says:
1614f34d8d1SJohn-Mark Gurney	"initialize drop", do (i386 only):
1624f34d8d1SJohn-Mark Gurney		cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
1634f34d8d1SJohn-Mark Gurney		chown root:wheel /boot/loader.rc
1644f34d8d1SJohn-Mark Gurney		chmod 444 /boot/loader.rc
1654f34d8d1SJohn-Mark Gurney
1668f075db4SMark Murray20040802:
1678f075db4SMark Murray	making /dev/(null|zero) into a module proved to be too unpopular,
1688f075db4SMark Murray	so this bit has been revoked from the previous (20040801) entry.
1698f075db4SMark Murray
170d064d6dbSMark Murray20040801:
171d064d6dbSMark Murray	The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
172d064d6dbSMark Murray	so you may wish to add them to your kernel config file. See
173d064d6dbSMark Murray	GENERIC for examples.
174d064d6dbSMark Murray
175b289983eSAlexander Kabaev20040728:
17654bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
17754bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
17854bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
17954bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
180d0e54ab4SDavid E. O'Brien	compiler. If you are getting run-time error such as
181d0e54ab4SDavid E. O'Brien	/libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
182d0e54ab4SDavid E. O'Brien	This entry does apply to you.
183d0e54ab4SDavid E. O'Brien
184d0e54ab4SDavid E. O'Brien	A new unit-at-a-time optimization mode, which is default in this
185d0e54ab4SDavid E. O'Brien	compiler release, is more aggressive in removing unused static
186d0e54ab4SDavid E. O'Brien	symbols. This is the likely cause of 'make buildworld' breakages
187cd5f061cSWarner Losh	with non-default CFLAGS where optimization level is set to -O2
188cd5f061cSWarner Losh	or higher.
18954bd5271SAlexander Kabaev
1906e1afae3SWarner Losh	With the upgrade of the system compiler, the kernel has been upgraded
1916e1afae3SWarner Losh	to match the new system compiler.  This makes it impossible to build
1926e1afae3SWarner Losh	a new kernel with the old compiler.  Upgrade your system via
1936e1afae3SWarner Losh	make buildworld and make kernel (see below) to fix this problem.
1946e1afae3SWarner Losh
19536ed21e6SRobert Watson20040727:
19636ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
19736ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
19836ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
19936ed21e6SRobert Watson	a result.
20036ed21e6SRobert Watson
2016305ac24SSeigo Tanimura20040716:
2026305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
2036305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
2046305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
2056305ac24SSeigo Tanimura
206e623dcb7SMarcel Moolenaar20040710:
207e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
208e623dcb7SMarcel Moolenaar
209e623dcb7SMarcel Moolenaar20040710:
210e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
211e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
212e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
213e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
214e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
215e623dcb7SMarcel Moolenaar	of this.
216e623dcb7SMarcel Moolenaar
217e623dcb7SMarcel Moolenaar20040710:
218e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
219e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
220e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
221e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
222e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
223e623dcb7SMarcel Moolenaar	   option for this.
224e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
225e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
226e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
227e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
2285bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
229e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
230e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
231e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
232e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
233e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
234e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
235e623dcb7SMarcel Moolenaar
2366421d1dbSMaksim Yevmenkin20040708:
2376421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
2386421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
2396421d1dbSMaksim Yevmenkin
24058af3216SWarner Losh20040702:
24158af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
2425bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
2435bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
2445bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
24558af3216SWarner Losh	scheduler as a workaround.
24658af3216SWarner Losh
247c2dba668SNate Lawson20040630:
2488ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
2498ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
250a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
251a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
252a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
253a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
254a6c26e1cSBruce M Simpson	example of such changes.
2558ed370fdSJulian Elischer
25658af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
25758af3216SWarner Losh	over.
25858af3216SWarner Losh
2598ed370fdSJulian Elischer20040630:
260c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
2615bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
262c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
263c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
264c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
265c2dba668SNate Lawson	loader prompt.
266c2dba668SNate Lawson
2678ee2ac9eSMax Laier20040623:
2685bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
2698ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
2708ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
2718ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
2728ee2ac9eSMax Laier
2733db5687dSBrooks Davis20040622:
2743db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
2753db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
2763db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
2773db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
2783db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
2793db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
2803db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
2813db5687dSBrooks Davis
282e0ae81f3SDag-Erling Smørgrav20040621:
283e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
284e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
285e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
286e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
287e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
288e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
289e0ae81f3SDag-Erling Smørgrav	during the next reboot.
290e0ae81f3SDag-Erling Smørgrav
2914717d22aSJohn Polstra20040614:
2924717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
2934717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
2944717d22aSJohn Polstra	the ips module and any third-party modules which call
2954717d22aSJohn Polstra	sema_timedwait.
2964717d22aSJohn Polstra
2976cb7a382SMax Laier20040613:
2986cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
2996cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
300df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
301df843493SMax Laier	please recompile and reinstall world.
3026cb7a382SMax Laier
3032454685eSJulian Elischer20040607:
3042454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
3052454685eSJulian Elischer	requires that you re-run config after updating your tree.
3062454685eSJulian Elischer
30764fef830SSeigo Tanimura20040601:
30864fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
30964fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
31064fef830SSeigo Tanimura	kernel configuration.
31164fef830SSeigo Tanimura
312bb4f06e7SAndre Oppermann20040423:
313bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
314bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
315bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
316bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
317bb4f06e7SAndre Oppermann
31805641e82SColin Percival20040420:
31905641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
32005641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
32105641e82SColin Percival	20040406.
32205641e82SColin Percival
323d0dc9183SWarner Losh20040414:
324d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
325d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
326d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
327d0dc9183SWarner Losh
328d0dc9183SWarner Losh20040412:
329d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
330d0dc9183SWarner Losh	drive is still broken.
331d0dc9183SWarner Losh
332d0dc9183SWarner Losh20040410:
333d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
334d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
335d0dc9183SWarner Losh	the unanticipated problems have been resolved.
336d0dc9183SWarner Losh
3378633bbeaSBrooks Davis20040409:
3388633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
3398633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
3408633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
3418633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
34276c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
3438633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
3448633bbeaSBrooks Davis
345d40d033aSRobert Watson20040322:
346d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
347d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
348d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
349d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
350d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
351d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
352d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
353d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
354d40d033aSRobert Watson	locking is merged to permit this to take place.
355d40d033aSRobert Watson
356ec9b318eSGarance A Drosehn20040310:
357ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
358ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
359ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
360ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
361ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
362ec9b318eSGarance A Drosehn
363fc28f1ffSMax Laier20040308:
364fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
365fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
3664c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
3674c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
368fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
369fc28f1ffSMax Laier	pf system consists of the following three devices:
370fc28f1ffSMax Laier	device		pf		# required
371fc28f1ffSMax Laier	device		pflog		# optional
372fc28f1ffSMax Laier	device		pfsync		# optional
373fc28f1ffSMax Laier
3743aff5d06SDag-Erling Smørgrav20040303:
3753aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
3763aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
3773aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
3783aff5d06SDag-Erling Smørgrav
3793aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
3803aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
3813aff5d06SDag-Erling Smørgrav
3823aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
3833aff5d06SDag-Erling Smørgrav	to use libpthread instead.
3843aff5d06SDag-Erling Smørgrav
385fd63c5b3SDag-Erling Smørgrav20040226:
3869d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
387fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
388fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
389fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
390fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
391fd63c5b3SDag-Erling Smørgrav
392714ae42aSBruce M Simpson20040225:
393e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
394e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
395e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
396e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
397e07a40f3SBrian Feldman	should remain unaffected.
398e07a40f3SBrian Feldman
399e07a40f3SBrian Feldman20040225:
400714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
401714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
402714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
403714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
404714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
405714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
406714ae42aSBruce M Simpson
407fbd2e692SAndre Oppermann20040224:
408fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
4095bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
410fbd2e692SAndre Oppermann
411158b90daSWarner Losh20040222:
412158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
413158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
414158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
415158b90daSWarner Losh	Drivers outside the tree will need to be updated.
416158b90daSWarner Losh
417b7b1e150SMike Makonnen20040207:
418b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
419b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
420b7b1e150SMike Makonnen
421aca89ee6SDaniel Eischen20040130:
422aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
423aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
424aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
425aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
426aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
427aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
428aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
429aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
430aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
431aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
432aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
433aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
434aca89ee6SDaniel Eischen	do not work with libpthread.
435aca89ee6SDaniel Eischen
43668b7b3a9SAlex Dupre20040125:
43768b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
43868b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
43968b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
44068b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
44168b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
44268b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
44368b7b3a9SAlex Dupre
444ff46e0deSWarner Losh20040125:
445ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
446ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
447ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
448ff46e0deSWarner Losh
449ce41f4bfSRobert Watson20031213:
450ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
451ce41f4bfSRobert Watson	if the login process is unable to successfully set the
452ce41f4bfSRobert Watson	process credentials to include all groups defined for the
453ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
454ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
455ce41f4bfSRobert Watson	defined, or they will be unable to log in.
456ce41f4bfSRobert Watson
457c124fa05SJohn Baldwin20031203:
458c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
459c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
460c124fa05SJohn Baldwin
4618ad1f5e4SHartmut Brandt20031112:
46230093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
46330093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
46497209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
46597209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
46697209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
46797209ca3SRobert Watson	not know about the new system calls that support the new statfs
4683f631d52SMarcel Moolenaar	structure.
4693f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
4703f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
4713f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
4723f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
4733f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
4743f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
4753f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
4763f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
4773f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
4783f631d52SMarcel Moolenaar	these changes are installed.
47930093b05SWarner Losh
48030093b05SWarner Losh	****************************DANGER*******************************
48130093b05SWarner Losh
48230093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
48330093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
48430093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
48530093b05SWarner Losh	kernel.
48664a18d6fSKirk McKusick
48764a18d6fSKirk McKusick20031112:
4888ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
4898ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
4908ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
4918ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
4928ad1f5e4SHartmut Brandt	sync before rebooting.
4938ad1f5e4SHartmut Brandt
494c53a5d8fSJohn Baldwin20031111:
495c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
496c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
497c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
498c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
499c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
500c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
501c53a5d8fSJohn Baldwin
5028bf455a5SJohn Baldwin20031103:
5038bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
5048bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
5052a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
5068bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
5078bf455a5SJohn Baldwin
5089bf40edeSBrooks Davis20031031:
5099bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
5109bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
5119bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
5129bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
5139bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
5149bf40edeSBrooks Davis	reflect this change.
5159bf40edeSBrooks Davis
51647a42c7aSPoul-Henning Kamp20030928:
51747a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
51847a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
5195bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
52047a42c7aSPoul-Henning Kamp
52107105342SMax Khon20030926:
52207105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
52307105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
52407105342SMax Khon
52517dcd026SSam Leffler20030925:
52617dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
52717dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
52817dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
52917dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
53017dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
53117dcd026SSam Leffler
532fedf1d01SBruce M Simpson20030923:
533fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
534fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
535fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
536fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
537fedf1d01SBruce M Simpson
538db38f9cbSJacques Vidrine20030915:
539db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
540db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
541db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
542db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
543db38f9cbSJacques Vidrine
544c09d2c2bSMike Makonnen20030829:
545c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
546c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
547c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
548c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
549c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
550c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
551c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
552c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
553c09d2c2bSMike Makonnen	may or may not exist on your system.
554c09d2c2bSMike Makonnen
55517c159dcSSøren Schmidt20030824:
55617c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
55717c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
558f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
559f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
56017c159dcSSøren Schmidt
561c1f61aa9SDavid E. O'Brien20030819:
562c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
563c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
564c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
565c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
56669f7bcf3SWarner Losh
56738c962e7SNate Lawson20030728:
56838c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
56938c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
57038c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
57138c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
57238c962e7SNate Lawson	so the quirk can be re-enabled.
57338c962e7SNate Lawson
57474111097SWarner Losh20030724:
57574111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
57674111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
57774111097SWarner Losh
578178cf4e9SWarner Losh20030722:
579178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
580178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
581178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
582178cf4e9SWarner Losh	FPU hardware.
583178cf4e9SWarner Losh
584178cf4e9SWarner Losh20030714:
585178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
586178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
587178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
588178cf4e9SWarner Losh	People should report those issues to current@.
589178cf4e9SWarner Losh
590157c629aSWarner Losh20030711:
591157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
5928b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
59305538fa9SWarner Losh	/usr/obj.
594157c629aSWarner Losh
59574111097SWarner Losh20030610:
59674111097SWarner Losh	Remove deprecated locale names and transition period code
59774111097SWarner Losh	for them, finishing switching to the new scheme. Check your
59874111097SWarner Losh	LANG environment variable.
59974111097SWarner Losh
60074111097SWarner Losh20030609:
60174111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
60274111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
60374111097SWarner Losh	important to remember beforehand if your source tree is on
60474111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
60574111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
60674111097SWarner Losh	kernel.
60774111097SWarner Losh
60874111097SWarner Losh20030605:
6096cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
6106cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
6116cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
6126cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
6136cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
6146cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
6156cc6353fSMarcel Moolenaar
6166cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
6176cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
6186cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
6196cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
6206cc6353fSMarcel Moolenaar		:
6216cc6353fSMarcel Moolenaar
6226cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
6236cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
6246cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
6256cc6353fSMarcel Moolenaar
62652b47445SMark Murray20030505:
62752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
62852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
62952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
63052b47445SMark Murray
631a26df538SWarner Losh20030502:
632a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
633a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
634a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
635a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
636a26df538SWarner Losh
6374b065e2cSDoug Barton20030501:
6384b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
6394b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
6404b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
6414b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
6424b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
6434b065e2cSDoug Barton	utilizes these old scripts has also been removed.
6444b065e2cSDoug Barton
64581cda3d9SWarner Losh20030423:
64681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
64781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
64881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
64981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
65081cda3d9SWarner Losh	userland.  In general, you should have a userland and
65181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
65281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
65381cda3d9SWarner Losh	allowances are made.
65481cda3d9SWarner Losh
65547a657d1SRuslan Ermilov20030329:
65647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
65747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
65847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
65947a657d1SRuslan Ermilov
66047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
66147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
66247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
66347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
66447a657d1SRuslan Ermilov
66547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
66647a657d1SRuslan Ermilov	    make cleandir && make obj && \
66747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
66847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
66947a657d1SRuslan Ermilov
6705d2af00cSGregory Neil Shapiro20030208:
6715d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
6725d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
6735d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
6745d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
6755d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
6765d2af00cSGregory Neil Shapiro
6775d2af00cSGregory Neil Shapiro20030128:
6789db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
679ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
6809db58771SPoul-Henning Kamp	be removed when convenient.
6819db58771SPoul-Henning Kamp
6828d9b3f57SJake Burkholder20030126:
6838d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
6848d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
6858d9b3f57SJake Burkholder
6861c5efda5SJeff Roberson20030125:
6871c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
6881c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
689ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
6901c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
6911c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
6921c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
6931c5efda5SJeff Roberson
6949d1d64f5SWarner Losh20030115:
6959d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
6969d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
6979d1d64f5SWarner Losh	properly.
6989d1d64f5SWarner Losh
699c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
700c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
701c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
702c9fdb80aSWarner Losh	with NetBSD.
703c9fdb80aSWarner Losh
704161dc364SAlexander Kabaev20021222:
705161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
706161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
707161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
708161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
709161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
710161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
71184cc83efSAlexander Kabaev	rebuilt.
712161dc364SAlexander Kabaev
713fb4c8061SMartin Blapp20021216:
714fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
71589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
716fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
7179d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
718fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
719fb4c8061SMartin Blapp
72017d47eb3SGiorgos Keramidas20021202:
72117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
72217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
72317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
72417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
72517d47eb3SGiorgos Keramidas
726a4459294SBill Fenner20021029:
727a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
728a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
729a4459294SBill Fenner	consumers in sync.
730a4459294SBill Fenner
731fc8c157fSWarner Losh20021024:
732c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
733c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
734c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
735c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
736c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
737c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
738c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
739c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
74069f7bcf3SWarner Losh
741fd9e8bdaSAndrew Gallatin20021023:
742fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
743fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
744fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
745fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
746fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
747fd9e8bdaSAndrew Gallatin
748fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
749fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
750fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
751fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
752fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
753fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
754fd9e8bdaSAndrew Gallatin
755f8a4c901SWarner Losh20020831:
756f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
757f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
758f8a4c901SWarner Losh	programs and libraries need to be recompiled.
759f8a4c901SWarner Losh
760f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
761f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
762f8a4c901SWarner Losh
763c2248fa2SJens Schweikhardt20020827:
764c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
765c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
766c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
767c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
768c2248fa2SJens Schweikhardt
7690d533e43SRuslan Ermilov20020815:
7700d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
7710d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
7720d533e43SRuslan Ermilov	again.
7730d533e43SRuslan Ermilov
77433c1de7dSRuslan Ermilov20020729:
77533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
77633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
77733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
77833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
77933c1de7dSRuslan Ermilov
7802b877facSJulian Elischer20020702:
7812b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
7822b877facSJulian Elischer	There are still some minor problems with some signals but the
7832b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
7842b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
7852b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
7862b877facSJulian Elischer
78706596d37SWarner Losh20020701:
78806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
78906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
79006596d37SWarner Losh	GNOME.
79106596d37SWarner Losh
79295ba4330SJacques Vidrine20020511:
79395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
79495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
79595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
79695ba4330SJacques Vidrine	with the set-user-ID bit set.
79795ba4330SJacques Vidrine
798a81da3c9SDavid E. O'Brien20020510:
799f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
800f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
8014b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
802f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
803f50caf6fSDavid E. O'Brien
804f50caf6fSDavid E. O'Brien20020510:
805a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
806a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
807a81da3c9SDavid E. O'Brien	and then do a cvs update.
808a81da3c9SDavid E. O'Brien
809528a0ef5SJacques Vidrine20020421:
810528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
811528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
812528a0ef5SJacques Vidrine
81385aa5a2eSGregory Neil Shapiro20020404:
81485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
81585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
81685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
81785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
81885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
81985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
82085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
82185aa5a2eSGregory Neil Shapiro
8228f1e4358SRuslan Ermilov20020403:
8238f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
8248f1e4358SRuslan Ermilov
8252292c02eSWarner Losh20020315:
8262292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
8272292c02eSWarner Losh
82869f7bcf3SWarner Losh20020225:
82969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
83069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
83169f7bcf3SWarner Losh
8328f35c493SWarner Losh20020217:
8338f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
8348f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
8358f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
8368f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
8378f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
8388f35c493SWarner Losh
839835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
840835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
841835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
842835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
843835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
844835284beSWarner Losh	and group must be merged from src/etc/group and
845835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
846835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
847835284beSWarner Losh	mergemaster before this will work if you are updating from a
848835284beSWarner Losh	very old version of current.  The updating recipe has changed
849835284beSWarner Losh	as of this date.
850835284beSWarner Losh
851fa9401c1SWarner Losh20020112:
852fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
853fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
854fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
855fa9401c1SWarner Losh	you have local modifications, you can use
856fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
857fa9401c1SWarner Losh	/etc/pam.d.
858fa9401c1SWarner Losh
859fa9401c1SWarner Losh	Please see the following url for more details:
860fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
86147d0d01fSWarner Losh20011229:
86247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
86347d0d01fSWarner Losh	networkfs_types, please note that it has changed
86447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
86547d0d01fSWarner Losh
866514318a8SWarner Losh20011220:
867514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
868514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
869514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
870514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
871514318a8SWarner Losh	version have now been merged back into the base system's
872514318a8SWarner Losh	version now.  The only user-visible change resulting from this
873514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
874514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
875514318a8SWarner Losh	as well.  (There has never been rc file support for
876514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
877514318a8SWarner Losh	reverted by the time the changes are MFCed.)
878514318a8SWarner Losh
879514318a8SWarner Losh20011215:
880514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
881514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
882514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
883514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
884514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
885514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
886514318a8SWarner Losh	will need to be customized then for `odd' densities using
887514318a8SWarner Losh	fdcontrol(8).
888514318a8SWarner Losh
8892d22e2bfSWarner Losh20011209:
8902d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
8912d22e2bfSWarner Losh	and truss(1) now works again.
8922d22e2bfSWarner Losh
8939e0428e2SWarner Losh20011207:
8949e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
8959e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
8969e0428e2SWarner Losh	see
8979e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
8989e0428e2SWarner Losh	for details.
8999e0428e2SWarner Losh
9009bab8c59SWarner Losh20011204:
9019bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
9029bab8c59SWarner Losh	kernel and burncd to be in sync.
9039bab8c59SWarner Losh
904e57d8b01SWarner Losh20011203:
905e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
906e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
907e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
908e57d8b01SWarner Losh	not there already.
909e57d8b01SWarner Losh
910e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
911e57d8b01SWarner Losh	until the issue has been resolved.
912e57d8b01SWarner Losh
913b001d36fSJacques Vidrine20011202:
914b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
915b001d36fSJacques Vidrine	patched.
916b001d36fSJacques Vidrine
9174b676ec1SWarner Losh20011126:
9184b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
9195ebbf43eSWarner Losh	after this date.  You need to do this only once.
9204b676ec1SWarner Losh
921d961e462SWarner Losh20011103:
922d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
923d961e462SWarner Losh	edges may be left, but for the most part things should be
9244b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
925d961e462SWarner Losh
926d961e462SWarner Losh20011030:
927d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
928d961e462SWarner Losh	choppy waves in the upgrade process.
929d961e462SWarner Losh
9301fe003b6SWarner Losh20011030:
931a4b6fda0SWarner Losh	The asr driver problem has been resolved.
9321fe003b6SWarner Losh
9331fe003b6SWarner Losh20011027:
9341fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
9351fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
9361fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
9371fe003b6SWarner Losh	try to use from this date forward.
9381fe003b6SWarner Losh
9391fe003b6SWarner Losh20011025:
9401fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
9411fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
9421fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
9431fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
9441fe003b6SWarner Losh	TARGET_ARCH=i386.
9451fe003b6SWarner Losh
946d05f9643SWarner Losh20011001:
947d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
948d05f9643SWarner Losh	You must recompile both the kernel and userland applications
949d05f9643SWarner Losh	at the same time.
950d05f9643SWarner Losh
95158970f85SWarner Losh20010929:
95258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
95358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
95458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
95558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
9569d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
95758970f85SWarner Losh
95858970f85SWarner Losh20010927:
95958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
96058970f85SWarner Losh	To disable ACPI you can add
96166ff0e67SMax Khon		hint.acpi.0.disabled="1"
96258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
96358970f85SWarner Losh	loader "ok" prompt).
96458970f85SWarner Losh
96558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
96658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
96758970f85SWarner Losh	file and not list acpi in that list.
968378f4486SAlfred Perlstein
9695119d237SWarner Losh20010924:
9705119d237SWarner Losh	The buildworld has been fixed.  You may need to install
9715119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
9728b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
9738b039fffSWarner Losh	get them installed on every installworld, or execute the
9748b039fffSWarner Losh	following to get them installed only once:
9758b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
97658970f85SWarner Losh		make all install
9778b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
9785119d237SWarner Losh
9793c293725SWarner Losh20010919:
9803c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
9813c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
9823c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
983772730c7SWarner Losh	workaround is to add
9843c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
9853c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
9863c293725SWarner Losh	can be removed afterwards.
9873c293725SWarner Losh
9883c293725SWarner Losh	A proper fix to the buildworld target is needed.
9893c293725SWarner Losh
9903c293725SWarner Losh20010918:
9913c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
9923c293725SWarner Losh	NFS may be unstable after this date.
9933c293725SWarner Losh
9943c293725SWarner Losh20010912:
9953c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
9963c293725SWarner Losh	the kernel.  While a few problems were introduced in the
9973c293725SWarner Losh	initial commit, most of the major ones have been found and
9983c293725SWarner Losh	corrected.
9993c293725SWarner Losh
10003c293725SWarner Losh20010901:
10013c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
10023c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
10033c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
10043c293725SWarner Losh	have been rectified around this date.
10053c293725SWarner Losh
100698b17b95SWarner Losh20010823:
100798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
100898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
100998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
101098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
101198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
101298b17b95SWarner Losh 	permission for your name server configuration and that it
101398b17b95SWarner Losh 	has read and write permission for your slave zone files and
101498b17b95SWarner Losh 	directory.
101598b17b95SWarner Losh
101698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
101798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
101898b17b95SWarner Losh
101998b17b95SWarner Losh 		named_flags=
102098b17b95SWarner Losh
10217b9786edSMark Murray20010709:
10227b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
10237b9786edSMark Murray	the ability of the shared library major number to handle.
10247b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
10257b9786edSMark Murray	solution is to rebuild those ports.
10267b9786edSMark Murray
10271d28950eSWarner Losh20010628:
10281d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
10291d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
10301d28950eSWarner Losh
1031e72fd46aSWarner Losh20010625:
103298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
103398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
103498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
103598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
103698b17b95SWarner Losh	IRQ configuration needs more safety belts.
103716de1a07SWarner Losh
10380d415dffSWarner Losh20010617:
1039e72fd46aSWarner Losh	Softupdates problems have been corrected.
10400d415dffSWarner Losh
10410d415dffSWarner Losh20010614:
10420d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
10430d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
10440d415dffSWarner Losh	kernel building methods.
10450d415dffSWarner Losh
10468b9959adSWarner Losh20010613:
10478b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
10488b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
1049e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
1050e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
10518b9959adSWarner Losh
1052e72fd46aSWarner Losh20010613:
10538b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
1054e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
1055e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
10568b9959adSWarner Losh
10570d415dffSWarner Losh20010612:
10580d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
10590d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
10600d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
10610d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
10620d415dffSWarner Losh	until this bug is fixed.
10630d415dffSWarner Losh
1064e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
1065e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
1066ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
1067e72fd46aSWarner Losh
10680d415dffSWarner Losh20010610:
10690d415dffSWarner Losh	Locale names have changed to match other systems better.
10700d415dffSWarner Losh
10716ccdb5e4SWarner Losh20010604:
10726ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
10736ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
10746ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
10753590182eSWarner Losh	Interrupt storms look a lot like a hang.
10763590182eSWarner Losh
10773590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
10783590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
10793590182eSWarner Losh	it is).
10803590182eSWarner Losh
10813590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
10823590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
10833590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
10843590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
10856ccdb5e4SWarner Losh
10860bc62786SWarner Losh20010530:
10870bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
10880bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
10890bc62786SWarner Losh	a limited time.  If you see
10900bc62786SWarner Losh
10910bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
10920bc62786SWarner Losh
10930bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
10940bc62786SWarner Losh	COPY=-C.
10950bc62786SWarner Losh
109668a38c6cSWarner Losh20010525:
1097b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
1098c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
1099c4f4a728SWarner Losh	definitely is in bad shape.
110068a38c6cSWarner Losh
1101ed0f29caSWarner Losh20010521:
1102ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
1103ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
1104ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1105ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
1106ed0f29caSWarner Losh	is
1107ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1108ed0f29caSWarner Losh
110980c16af9SWarner Losh20010520:
111068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
111180c16af9SWarner Losh
111280c16af9SWarner Losh20010519:
111380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
111480c16af9SWarner Losh	the past few days.  Everything should still work, but if
111580c16af9SWarner Losh	not, please contact imp@freebsd.org.
111680c16af9SWarner Losh
1117a45f2d05SWarner Losh20010517:
1118a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
1119a45f2d05SWarner Losh	userland at the same time.
1120a45f2d05SWarner Losh
1121a45f2d05SWarner Losh20010517:
1122a45f2d05SWarner Losh	New ncurses imported.
1123a45f2d05SWarner Losh
11242988afcaSWarner Losh20010512:
11252988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
11262988afcaSWarner Losh	will be the only way to go starting July 1.
11272988afcaSWarner Losh
11281a33dba7SWarner Losh20010504:
11291a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
11301a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
11311a33dba7SWarner Losh
113209946a51SWarner Losh20010502:
113309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
113409946a51SWarner Losh
113509946a51SWarner Losh20010501:
113609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
113709946a51SWarner Losh
113809946a51SWarner Losh20010430:
1139a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
114009946a51SWarner Losh	go back in the water.
114109946a51SWarner Losh
114209946a51SWarner Losh20010429:
114309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
114409946a51SWarner Losh	this date, but before the correction date.
114509946a51SWarner Losh
114691dd3b53SWarner Losh20010423:
114791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
114891dd3b53SWarner Losh
114991dd3b53SWarner Losh20010411:
115091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
115191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
115291dd3b53SWarner Losh	Update only if you understand that you must not use the old
115391dd3b53SWarner Losh	fsck with the new kernel ever.
115491dd3b53SWarner Losh
1155933b3269SWarner Losh20010330:
1156933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1157c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1158933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1159933b3269SWarner Losh
1160933b3269SWarner Losh20010319:
1161933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1162933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1163933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1164f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
116509946a51SWarner Losh
116609946a51SWarner Losh20010315:
116709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1168ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
116909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1170933b3269SWarner Losh
1171933b3269SWarner Losh20010312:
1172933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1173933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1174933b3269SWarner Losh
1175933b3269SWarner Losh20010312:
1176933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1177933b3269SWarner Losh	instead of ad-hoc.
1178933b3269SWarner Losh
1179933b3269SWarner Losh20010310:
1180f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1181933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1182933b3269SWarner Losh	ssh might not work if you don't.
1183933b3269SWarner Losh
118462353691SWarner Losh20010303:
118562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
118662353691SWarner Losh	which means that you must include the miibus in your kernel if
118762353691SWarner Losh	you use the ed driver.
118862353691SWarner Losh
1189d325cf65SWarner Losh20010220:
1190d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1191d325cf65SWarner Losh	safe to go back into the water.
1192d325cf65SWarner Losh
1193024daae6SWarner Losh20010211:
1194024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1195024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1196024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1197024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1198024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1199024daae6SWarner Losh
1200024daae6SWarner Losh	To get to the new system, you'll need to use the following
1201024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1202024daae6SWarner Losh	don't have to move this to the updating section.
1203024daae6SWarner Losh
1204024daae6SWarner Losh	To get around the installworld problem, do:
1205024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1206024daae6SWarner Losh		# make install
1207024daae6SWarner Losh		# cd /usr/src
1208024daae6SWarner Losh		# make installworld
1209024daae6SWarner Losh	If that doesn't work, then try:
1210024daae6SWarner Losh		# make -k installworld
1211024daae6SWarner Losh		# make installworld
1212024daae6SWarner Losh
1213024daae6SWarner Losh20010207:
1214024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1215024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1216024daae6SWarner Losh
1217024daae6SWarner Losh20010205:
12187595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1219024daae6SWarner Losh	Remove them from your config.
1220024daae6SWarner Losh
12211e159248SWarner Losh20010122:
12221e159248SWarner Losh	****************************** WARNING ******************************
12231e159248SWarner Losh			buildkernel has been changed slightly
12241e159248SWarner Losh	****************************** WARNING ******************************
12251e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
12261e159248SWarner Losh	should update your scripts and make.conf accordingly.
12271e159248SWarner Losh
12281e159248SWarner Losh20010119:
12291e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
12301e159248SWarner Losh	This requires a new config to build correctly.
12311e159248SWarner Losh
1232aac7dfeaSWarner Losh20010116:
1233ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1234aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1235aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1236aac7dfeaSWarner Losh
1237aac7dfeaSWarner Losh20010110:
1238aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1239aac7dfeaSWarner Losh
1240aac7dfeaSWarner Losh20010102:
1241aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1242aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1243aac7dfeaSWarner Losh
124463c90c9eSWarner Losh20010101:
124563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
124663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
12475fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
124863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
124963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
125063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
125163c90c9eSWarner Losh	might have been ignored by the -k option.
125263c90c9eSWarner Losh
12535fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
12545fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
12555fd2a895SWarner Losh	of this working.
12565fd2a895SWarner Losh
1257aac7dfeaSWarner Losh20001228:
1258aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1259ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1260aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1261aac7dfeaSWarner Losh
1262de2bcc63SWarner Losh20001218:
1263de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1264de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1265de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1266de2bcc63SWarner Losh	cards will not be recognized without it.
1267de2bcc63SWarner Losh
1268960773f7SWarner Losh20001205:
1269960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1270960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1271960773f7SWarner Losh	adding the following in pam.conf:
1272960773f7SWarner Losh
1273960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1274960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1275960773f7SWarner Losh	sshd    session required        pam_permit.so
1276960773f7SWarner Losh
12770acc635eSWarner Losh20001031:
12780acc635eSWarner Losh	cvs updated to 1.11.
12790acc635eSWarner Losh
12800acc635eSWarner Losh20001020:
12810acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
12820acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
12830acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
12840acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
12850acc635eSWarner Losh	workaround.
12860acc635eSWarner Losh
12870acc635eSWarner Losh20001010:
12880acc635eSWarner Losh	****************************** WARNING ******************************
12890acc635eSWarner Losh				Sendmail has been updated.
12900acc635eSWarner Losh	****************************** WARNING ******************************
12910acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
12920acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
12930acc635eSWarner Losh	  is set.
12940acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
12950acc635eSWarner Losh	  commands.
12960acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
12970acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
12980acc635eSWarner Losh	  in /usr/share/sendmail/cf.
12990acc635eSWarner Losh	o sendmail.cw changed to local-host-names
13000acc635eSWarner Losh
13010acc635eSWarner Losh	More details can be found at
13020acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
13030acc635eSWarner Losh
13046e98a146SWarner Losh20001009:
13056e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
13066e98a146SWarner Losh	your entire ports tree, or you will have problems.
13076e98a146SWarner Losh
13086e98a146SWarner Losh20001006:
1309685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
13106e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
13116e98a146SWarner Losh	/usr/bin/miniperl.
13126e98a146SWarner Losh
1313073113a4SWarner Losh20001005:
1314073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1315685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1316073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1317073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1318073113a4SWarner Losh	tree for anything to work.
1319073113a4SWarner Losh
13200acc635eSWarner Losh20000928:
13210acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
13220acc635eSWarner Losh
1323be3885b3SWarner Losh20000916:
1324be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1325be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1326be3885b3SWarner Losh	same time as your kernel.
1327be3885b3SWarner Losh
132876ec9675SWarner Losh20000914:
132976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
133076ec9675SWarner Losh	include the device will cause suspended laptops losing time
133176ec9675SWarner Losh	when they resume.  Include
133276ec9675SWarner Losh		device		pmtimer
133376ec9675SWarner Losh	in your config file and
133401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
133576ec9675SWarner Losh	to your /boot/device.hints file.
133676ec9675SWarner Losh
1337f4865386SMark Murray20000911:
1338f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1339f4865386SMark Murray	rather than an option. The supplied kernel config files have
1340f4865386SMark Murray	been updated. You will need to do something similar in your
1341f4865386SMark Murray	own kernel config file.
1342f4865386SMark Murray	Remove:
1343f4865386SMark Murray		options		RANDOMDEV
1344f4865386SMark Murray	Add:
1345f4865386SMark Murray		device		random
1346f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1347f4865386SMark Murray	nothing.
1348f4865386SMark Murray
1349d594498fSWarner Losh20000909:
1350d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1351d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1352d594498fSWarner Losh	reflect this if you load this module at boot time.
1353d594498fSWarner Losh	The line should read:
1354d594498fSWarner Losh		random_load="YES"
1355d594498fSWarner Losh
13560deb7ddcSWarner Losh20000907:
13570deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
135816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
135916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
136016eb772dSWarner Losh	sure you don't have model loading problems which might at
136116eb772dSWarner Losh	first blush appear related to SMP.
136252bf24e7SWarner Losh
13635a01880bSWarner Losh20000906:
13645a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
13655a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
13665a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
13675a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
13685a01880bSWarner Losh	don't have one, and you have host.conf.
13695a01880bSWarner Losh
13702b41163cSWarner Losh20000905:
137138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
137238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
137338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
137438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
137538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
137638d6ecd2SWarner Losh
137738d6ecd2SWarner Losh20000905:
13788aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
13798aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
13808aab4bc7SWarner Losh	is /boot/kernel.
13818aab4bc7SWarner Losh
13828aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
138338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
138438d6ecd2SWarner Losh	installkernel/installworld dance.
13852b41163cSWarner Losh
1386d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1387d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1388d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1389d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1390d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1391d594498fSWarner Losh
1392d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1393d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1394d594498fSWarner Losh		chflags noschg /kernel.old
1395d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1396d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1397d594498fSWarner Losh	fi
1398d594498fSWarner Losh
1399c22a309cSWarner Losh20000904:
1400c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1401c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1402c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1403c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1404c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1405c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1406c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1407c22a309cSWarner Losh	is not likely to be generated.
1408c22a309cSWarner Losh
1409fdb9f54dSWarner Losh20000825:
1410fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
14119c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
14129c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
14139c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
14149c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
14159c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
14169c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
14179c1a7444SWarner Losh	kernel.
14189c1a7444SWarner Losh
14199c1a7444SWarner Losh20000821:
14209c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
14219c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
14229c1a7444SWarner Losh	/boot/loader.conf.
1423fdb9f54dSWarner Losh
14248f250aa7SWarner Losh20000812:
14255da0d091SWarner Losh	suidperl is now always built and installed on the system, but
14265da0d091SWarner Losh	with permissions of 511.  If you have applications that use
14275da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
14285da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
14295da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
14305da0d091SWarner Losh	will fix this until the next build.
14315da0d091SWarner Losh
14325da0d091SWarner Losh20000812:
14338f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
14348f250aa7SWarner Losh	visible changes that may immediately affect your configuration
14358f250aa7SWarner Losh	include:
14368f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
14378f250aa7SWarner Losh	- newaliases limited to root and trusted users
14388f250aa7SWarner Losh	- MSA port (587) turned on by default
14398f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
14408f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
14418f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
14428f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
14438f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
14448f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
14458f250aa7SWarner Losh
144671c38472SWarner Losh20000810:
144771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
144871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
144971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
145071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
145171c38472SWarner Losh	specific use for it.
145271c38472SWarner Losh
145371c38472SWarner Losh20000729:
145471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
145571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
145671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
145771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
145871c38472SWarner Losh		# Enable network daemons for user convenience.
145971c38472SWarner Losh		inetd_enable="YES"
146071c38472SWarner Losh		portmap_enable="YES"
146171c38472SWarner Losh		sendmail_enable="YES"
146271c38472SWarner Losh
146371c38472SWarner Losh20000728:
146471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
146571c38472SWarner Losh	will need to change that to nullfs_load="YES".
146671c38472SWarner Losh
14671dece4a9SWarner Losh20000728:
14681dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
14691dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
14701dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
14711dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
14721dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
14731dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
14741dece4a9SWarner Losh	to /MYKERNEL.
14751dece4a9SWarner Losh
1476409e887cSWarner Losh20000711:
1477409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1478409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1479409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1480409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1481409e887cSWarner Losh	for details on potential problems that you might have and how
1482409e887cSWarner Losh	to get around them.
1483409e887cSWarner Losh
1484409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1485409e887cSWarner Losh	clauses above, you needn't worry.
1486409e887cSWarner Losh
1487409e887cSWarner Losh20000711:
1488409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1489409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1490409e887cSWarner Losh	in the number of changed programs the first time when you run
1491409e887cSWarner Losh	mergemaster to get a new /etc/security.
1492409e887cSWarner Losh
1493673d13f2SWarner Losh20000710:
1494673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1495673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1496673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1497673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1498673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1499673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1500673d13f2SWarner Losh	errors. (see below, 20000624).
1501673d13f2SWarner Losh
1502bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
15031dece4a9SWarner Losh
1504673d13f2SWarner Losh20000709:
1505c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1506c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1507c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1508673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1509673d13f2SWarner Losh
1510e98e26cdSWarner Losh20000706:
1511e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1512e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1513e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1514f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1515e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
15162c021c6cSMark Ovens	interim if needed.
1517e98e26cdSWarner Losh
1518e98e26cdSWarner Losh20000705:
1519e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1520e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1521e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1522e98e26cdSWarner Losh	details.
1523e98e26cdSWarner Losh
1524c373950eSWarner Losh20000704:
15252f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
15262f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
15272f961bc8SWarner Losh
15282f961bc8SWarner Losh20000704:
1529c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1530c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1531c373950eSWarner Losh	rc.d scripts that haven't been updated.
1532c373950eSWarner Losh
153327dc3a2bSWarner Losh20000630:
153427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
153527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
153627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
153727dc3a2bSWarner Losh
1538b8c215acSWarner Losh20000625:
1539b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
154027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
154127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
154227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
154327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
154427dc3a2bSWarner Losh	were required.  You should check with the latest collections
154527dc3a2bSWarner Losh	to make sure that these haven't changed.
1546b8c215acSWarner Losh
15477b990719SWarner Losh20000624:
15487b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
15497b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
15507b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
15511a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
15527b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
15537b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
15547b990719SWarner Losh	date to the completion of the work.
15557b990719SWarner Losh
155627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
155727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
155827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
155927dc3a2bSWarner Losh	recreate the random and urandom devices.
156027dc3a2bSWarner Losh
156181e54c50SWarner Losh20000622:
156281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
156381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
156481e54c50SWarner Losh	that used to be required when updating.
156581e54c50SWarner Losh
156639943833SWarner Losh20000621:
15672c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
15682a2f33fbSDaniel Baker	the config file update procedure.
15692a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1570c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
157159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
157259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
157339943833SWarner Losh
1574290f9ad8SWarner Losh20000620:
1575290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1576290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1577290f9ad8SWarner Losh	that workaround will no longer be required.
1578290f9ad8SWarner Losh
157990fb6346SWarner Losh20000615:
158090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
158190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
158290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
158390fb6346SWarner Losh	devices.
158490fb6346SWarner Losh
1585f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1586f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1587f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1588f75f65bbSWarner Losh	may work).
1589f75f65bbSWarner Losh
1590ba26da8eSWarner Losh20000612:
1591ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1592290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1593c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1594290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1595f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1596f54a3542SWarner Losh	NEWCARD for examples of the new format.
1597290f9ad8SWarner Losh
15989698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
15999698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
16009698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
16019698f2c0SWarner Losh	in it.
1602bbcc5149SWarner Losh
1603d65850ebSWarner Losh20000522:
1604ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1605d65850ebSWarner Losh	building a kernel after this point is advised that they need
1606d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1607d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1608d65850ebSWarner Losh
1609d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1610d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1611d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1612d9583a00SWarner Losh	is resolved.
1613d9583a00SWarner Losh
16148039cedeSWarner Losh20000513:
16158039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
16168039cedeSWarner Losh
1617d65850ebSWarner Losh20000510:
16188039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
16198039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
16208039cedeSWarner Losh	is requires for the boot blocks to build properly.
16218039cedeSWarner Losh
16228039cedeSWarner Losh20000503:
16238039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
16248039cedeSWarner Losh	is now available.
16258039cedeSWarner Losh
1626d65850ebSWarner Losh20000502:
1627d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1628d65850ebSWarner Losh	connected to the kernel building instead.
1629d65850ebSWarner Losh
1630be149406SNik Clayton20000427:
16318039cedeSWarner Losh	You may need to build gperf
16328039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
16338039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
16348039cedeSWarner Losh	an option only in -current.
16358039cedeSWarner Losh
16362b8dd5f4SWarner Losh20000417:
16372b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1638f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
16392b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
16402b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
16412c021c6cSMark Ovens	before you reboot, you'll need to issue:
16422b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
16432b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
16442b8dd5f4SWarner Losh
16458d9f1945SWarner Losh20000320:
16462b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
16472b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
16482b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1649ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
16502b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
16518d9f1945SWarner Losh
1652f8ab1dd6SWarner Losh20000319:
1653f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1654f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1655f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1656f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1657f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1658f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1659f8ab1dd6SWarner Losh
166019cada77SWarner Losh20000318:
1661f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
166219cada77SWarner Losh	Large kernel changes are being committed and are in the
166319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
166419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
166519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
166619cada77SWarner Losh	that you are loading are up to date.
1667ba228352SWarner Losh
166819cada77SWarner Losh20000315:
16696d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
16706d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
16716d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
16726d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
16736d23c382SWarner Losh	boot.
16746d23c382SWarner Losh
16756d23c382SWarner Losh20000315:
167619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
167719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
167857199806SWarner Losh
1679dc0dbf5cSWarner LoshCOMMON ITEMS:
1680dc0dbf5cSWarner Losh
1681cd5f061cSWarner Losh	# NOTE: 5.x below applies to 6.0-currrent as well, for the
1682cd5f061cSWarner Losh	# momemnt.  4.any -> 5.any upgrade support will remain in
1683cd5f061cSWarner Losh	# place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1684cd5f061cSWarner Losh	# 6.0-current upgrade path will require moving through 5.3
1685cd5f061cSWarner Losh	# RELEASE or newer.
1686cd5f061cSWarner Losh
1687a24eff53SWarner Losh	General Notes
1688a24eff53SWarner Losh	-------------
1689a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1690a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1691a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1692a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1693a24eff53SWarner Losh	or several minor releases, or when several months have passed
1694a24eff53SWarner Losh	on the -current branch).
1695a24eff53SWarner Losh
16965780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
16975780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
16985780f3baSWarner Losh	environment when searching for values for global variables.
16995780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
17005780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
17015780f3baSWarner Losh	page for more details.
17025780f3baSWarner Losh
1703dc0dbf5cSWarner Losh	To build a kernel
1704dc0dbf5cSWarner Losh	-----------------
1705ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1706f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1707ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1708282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1709282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1710dc0dbf5cSWarner Losh
1711ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1712ba01eb20SWarner Losh	--------------------------------------------------------------
17130fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
17140fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
17150fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
17160fbd2da9SKen Smith
17170fbd2da9SKen Smith	cd src/sys/${arch}/conf
171847d0d01fSWarner Losh	config KERNEL_NAME_HERE
17190fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1720ba01eb20SWarner Losh	make depend
1721ba01eb20SWarner Losh	make
1722ba01eb20SWarner Losh	make install
1723ba01eb20SWarner Losh
1724ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1725ba01eb20SWarner Losh
1726ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1727ba01eb20SWarner Losh	-----------------------------------------------------------
172863cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
172963cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
173063cb445eSWarner Losh
1731f643de42SWarner Losh	<make sure you have good level 0 dumps>
173263cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
173363cb445eSWarner Losh	make buildworld
17346586253aSWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE
173563cb445eSWarner Losh							[1]
173663cb445eSWarner Losh	<reboot in single user>				[3]
17376586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
173863cb445eSWarner Losh	mergemaster -p					[5]
173963cb445eSWarner Losh	make installworld
174063cb445eSWarner Losh	mergemaster					[4]
174163cb445eSWarner Losh	<reboot>
174263cb445eSWarner Losh
1743759f0aefSWarner Losh
1744f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1745f27b1fceSJoseph Koshy	--------------------------------------------------
1746f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1747f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1748f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1749f27b1fceSJoseph Koshy	# size.
1750f27b1fceSJoseph Koshy
1751f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1752f27b1fceSJoseph Koshy	<boot into -stable>
1753f27b1fceSJoseph Koshy	make buildworld
1754f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1755f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1756f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1757f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
17586586253aSWarner Losh	cp src/sys/${ARCH}/conf/GENERIC.hints \
1759f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1760f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
17616586253aSWarner Losh	cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1762f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1763f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1764f27b1fceSJoseph Koshy	<reboot into current>
1765f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
17666586253aSWarner Losh	<maybe install compatibility libraries from src/lib/compat>
1767f27b1fceSJoseph Koshy 	<reboot>
1768f27b1fceSJoseph Koshy
1769f27b1fceSJoseph Koshy
1770f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1771f27b1fceSJoseph Koshy	----------------------------------------------
17725c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
1773e5dc5f61SWarner Losh	# modules has changed.  If you are installing 5.x onto a 4.x
17745c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
17755c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1776ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1777f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1778f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1779f643de42SWarner Losh	# space on /.
1780f643de42SWarner Losh
1781f643de42SWarner Losh	<make sure you have good level 0 dumps>
1782fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
178321c075eaSWarner Losh	make buildworld					[9]
1784802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1785e5dc5f61SWarner Losh	make kernel KERNCONF=YOUR_KERNEL_HERE		[8]
1786802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install		[6]
1787fc8c157fSWarner Losh							[1]
1788fc8c157fSWarner Losh	<reboot in single user>				[3]
17896586253aSWarner Losh	src/etc/rc.d/preseedrandom			[10]
1790835284beSWarner Losh	mergemaster -p					[5]
1791f8a4c901SWarner Losh	rm -rf /usr/include/g++
1792ba26da8eSWarner Losh	make installworld
1793802fc49dSBrian Feldman	mergemaster -i					[4]
1794ba26da8eSWarner Losh	<reboot>
1795ba26da8eSWarner Losh
1796fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1797fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1798fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1799fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1800fdb9f54dSWarner Losh	the UPDATING entries.
1801ba26da8eSWarner Losh
18021dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
18031dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
18041dece4a9SWarner Losh	your sources that you have read and understood all the recent
18051dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
18061dece4a9SWarner Losh	much fewer pitfalls.
18071dece4a9SWarner Losh
1808134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1809134d2e86SWarner Losh	should disable them at this point so they don't crash your
1810134d2e86SWarner Losh	system on reboot.
1811134d2e86SWarner Losh
18129c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
18139c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
18149c1a7444SWarner Losh	configuration.
18159c1a7444SWarner Losh
1816ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1817ee6e1fc3SWarner Losh		fsck -p
1818ee6e1fc3SWarner Losh		mount -u /
1819ee6e1fc3SWarner Losh		mount -a
18206586253aSWarner Losh		cd src
182147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1822f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1823f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
182466986952SRuslan Ermilov	For the 4.x -> 5.x upgrade, you will also see many messages about
1825b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1826b705ae10SWarner Losh	be ignored while you proceed to the next step.
1827ee6e1fc3SWarner Losh
1828a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1829a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1830a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1831a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1832a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1833a6cd4f9dSWarner Losh	for potential gotchas.
1834a6cd4f9dSWarner Losh
1835835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1836835284beSWarner Losh	you may need to do this if you get unknown user in the following
1837835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1838835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1839835284beSWarner Losh	install) after the buildworld before this step if you last updated
1840835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1841835284beSWarner Losh
1842bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1843bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1844bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1845bd79cf40SWarner Losh		ok unload
1846bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1847bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1848bd79cf40SWarner Losh	described here.
1849fc8c157fSWarner Losh
1850fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1851e5dc5f61SWarner Losh	compatibility slices.  These are device names of the form /dev/ad0a
1852e5dc5f61SWarner Losh	without the actual slice name.  These will break with 5.x and newer.
1853fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1854e5dc5f61SWarner Losh	2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1855e5dc5f61SWarner Losh	is not.
1856fc8c157fSWarner Losh
1857c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1858c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1859c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1860c74fe6afSWarner Losh	that is hard to boot to recover.
1861c74fe6afSWarner Losh
1862e5dc5f61SWarner Losh	Make sure that you merge any new devices from GENERIC since the
1863e5dc5f61SWarner Losh	last time you updated your kernel config file.
1864e5dc5f61SWarner Losh
186521c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1866e5dc5f61SWarner Losh	cvs prune empty directories.
1867e5dc5f61SWarner Losh
1868e5dc5f61SWarner Losh	If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1869e5dc5f61SWarner Losh	"?=" instead of the "=" assignment operator, so that buildworld can
1870e5dc5f61SWarner Losh	override the CPUTYPE if it needs to.
1871e5dc5f61SWarner Losh
1872e5dc5f61SWarner Losh	MAKEOBJDIRPREFIX must be defined in an environment variable, and
1873e5dc5f61SWarner Losh	not on the command line, or in /etc/make.conf.  buildworld will
1874e5dc5f61SWarner Losh	warn if it is improperly defined.
1875e5dc5f61SWarner Losh
1876802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1877802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
187866986952SRuslan Ermilov	compatibility libraries are built which should allow you to continue
1879e5dc5f61SWarner Losh	using your existing software for a while.  Alternatively, you can
1880e5dc5f61SWarner Losh	install the misc/compat4x port.
18818633bbeaSBrooks Davis
18828633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
18836586253aSWarner Losh	initialized by feeding data into it.  src/etc/rc.d/preseedrandom
18848633bbeaSBrooks Davis	takes care of this.
1885dc0dbf5cSWarner LoshFORMAT:
1886dc0dbf5cSWarner Losh
1887f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
18881fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1889f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1890f8ab1dd6SWarner Loshprevious releases if your system is older than this.
18911fc1a0dcSWarner Losh
1892e72fd46aSWarner LoshCopyright information:
1893e72fd46aSWarner Losh
1894e5dc5f61SWarner LoshCopyright 1998-2004 M. Warner Losh.  All Rights Reserved.
1895e72fd46aSWarner Losh
1896772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1897772730c7SWarner Loshmodification, in full or in part, in any form or format of this
18989698f2c0SWarner Loshdocument are permitted without further permission from the author.
1899e72fd46aSWarner Losh
1900e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1901e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1902e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1903e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1904e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1905e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1906e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1907e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1908e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1909e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1910e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1911e72fd46aSWarner Losh
1912e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1913e72fd46aSWarner Loshauthor a beer.
1914e72fd46aSWarner Losh
191522306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1916772730c7SWarner Loshthis document.
1917772730c7SWarner Losh
191897d92980SPeter Wemm$FreeBSD$
1919