xref: /freebsd/UPDATING (revision d0e54ab4ce200d0cdfc7140ca82cdbb4ecf9c186)
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
11f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
12f59d5f7aSPoul-Henning Kamp	FreeBSD 5.x has many debugging features turned on, in
1369f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1469f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1569f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1669f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1769f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1869f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1969f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
2069f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
2169f7bcf3SWarner Losh	developers choose to disable these features on build machines
22a19f8ddaSDavid E. O'Brien	to maximize performance.
23c1f61aa9SDavid E. O'Brien
24f036d408SJulian Elischer20040819:
25f036d408SJulian Elischer	Netgraph changed its message format slightly to align the data
26f036d408SJulian Elischer	portion well on 64 bit machines.
27f036d408SJulian Elischer	Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
28f036d408SJulian Elischer	pppoed, bluetooth, ATM) should be recompiled when a new kernel
29f036d408SJulian Elischer	is installed.
30f036d408SJulian Elischer
31b067abfaSAndre Oppermann20040817:
320ce70eb4SAndre Oppermann	IPFW has been converted to use PFIL_HOOKS.  This change is
33b067abfaSAndre Oppermann	transparent to userland and preserves the ipfw ABI.  The ipfw
34b067abfaSAndre Oppermann	core packet inspection and filtering functions have not been
35b067abfaSAndre Oppermann	changed, only how ipfw is invoked is different.  Note that
36b067abfaSAndre Oppermann	"option PFIL_HOOKS" is required to use IPFIREWALL compiled
37b067abfaSAndre Oppermann	into the kernel or as KLD.
38b067abfaSAndre Oppermann
39f13a7951SDavid Malone20040814:
40f13a7951SDavid Malone	The RANDOM_IP_ID option has been replaced by the sysctl
41f13a7951SDavid Malone	net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
42f13a7951SDavid Malone	you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
43f13a7951SDavid Malone
443a004637SMax Laier20040807:
453a004637SMax Laier	The size of 'struct ifnet' has changed due to the addition of the
463a004637SMax Laier	if_carp placeholder.  All kernel modules implementing network
473a004637SMax Laier	interfaces must be recompiled as a result.
483a004637SMax Laier
494f34d8d1SJohn-Mark Gurney20040806:
504f34d8d1SJohn-Mark Gurney	Module loading has been fixed.  Some older installations will
51ac41c814SRuslan Ermilov	drop proper module_path initialization and modules will fail to
524f34d8d1SJohn-Mark Gurney	load properly.  If you have a line in /boot/loader.rc that says:
534f34d8d1SJohn-Mark Gurney	"initialize drop", do (i386 only):
544f34d8d1SJohn-Mark Gurney		cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
554f34d8d1SJohn-Mark Gurney		chown root:wheel /boot/loader.rc
564f34d8d1SJohn-Mark Gurney		chmod 444 /boot/loader.rc
574f34d8d1SJohn-Mark Gurney
588f075db4SMark Murray20040802:
598f075db4SMark Murray	making /dev/(null|zero) into a module proved to be too unpopular,
608f075db4SMark Murray	so this bit has been revoked from the previous (20040801) entry.
618f075db4SMark Murray
62d064d6dbSMark Murray20040801:
63d064d6dbSMark Murray	The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
64d064d6dbSMark Murray	so you may wish to add them to your kernel config file. See
65d064d6dbSMark Murray	GENERIC for examples.
66d064d6dbSMark Murray
67b289983eSAlexander Kabaev20040728:
6854bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
6954bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
7054bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
7154bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
72d0e54ab4SDavid E. O'Brien	compiler. If you are getting run-time error such as
73d0e54ab4SDavid E. O'Brien	/libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
74d0e54ab4SDavid E. O'Brien	This entry does apply to you.
75d0e54ab4SDavid E. O'Brien
76d0e54ab4SDavid E. O'Brien	A new unit-at-a-time optimization mode, which is default in this
77d0e54ab4SDavid E. O'Brien	compiler release, is more aggressive in removing unused static
78d0e54ab4SDavid E. O'Brien	symbols. This is the likely cause of 'make buildworld' breakages
79d0e54ab4SDavid E. O'Brien	with non-default CFLAGS where optimization level is set to -O2 or higher.
8054bd5271SAlexander Kabaev
816e1afae3SWarner Losh	With the upgrade of the system compiler, the kernel has been upgraded
826e1afae3SWarner Losh	to match the new system compiler.  This makes it impossible to build
836e1afae3SWarner Losh	a new kernel with the old compiler.  Upgrade your system via
846e1afae3SWarner Losh	make buildworld and make kernel (see below) to fix this problem.
856e1afae3SWarner Losh
8636ed21e6SRobert Watson20040727:
8736ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
8836ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
8936ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
9036ed21e6SRobert Watson	a result.
9136ed21e6SRobert Watson
926305ac24SSeigo Tanimura20040716:
936305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
946305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
956305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
966305ac24SSeigo Tanimura
97e623dcb7SMarcel Moolenaar20040710:
98e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
99e623dcb7SMarcel Moolenaar
100e623dcb7SMarcel Moolenaar20040710:
101e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
102e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
103e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
104e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
105e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
106e623dcb7SMarcel Moolenaar	of this.
107e623dcb7SMarcel Moolenaar
108e623dcb7SMarcel Moolenaar20040710:
109e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
110e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
111e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
112e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
113e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
114e623dcb7SMarcel Moolenaar	   option for this.
115e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
116e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
117e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
118e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
1195bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
120e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
121e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
122e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
123e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
124e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
125e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
126e623dcb7SMarcel Moolenaar
1276421d1dbSMaksim Yevmenkin20040708:
1286421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
1296421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
1306421d1dbSMaksim Yevmenkin
13158af3216SWarner Losh20040702:
13258af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
1335bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
1345bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
1355bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
13658af3216SWarner Losh	scheduler as a workaround.
13758af3216SWarner Losh
138c2dba668SNate Lawson20040630:
1398ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
1408ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
141a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
142a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
143a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
144a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
145a6c26e1cSBruce M Simpson	example of such changes.
1468ed370fdSJulian Elischer
14758af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
14858af3216SWarner Losh	over.
14958af3216SWarner Losh
1508ed370fdSJulian Elischer20040630:
151c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
1525bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
153c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
154c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
155c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
156c2dba668SNate Lawson	loader prompt.
157c2dba668SNate Lawson
1588ee2ac9eSMax Laier20040623:
1595bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
1608ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
1618ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
1628ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
1638ee2ac9eSMax Laier
1643db5687dSBrooks Davis20040622:
1653db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
1663db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
1673db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
1683db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
1693db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
1703db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
1713db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
1723db5687dSBrooks Davis
173e0ae81f3SDag-Erling Smørgrav20040621:
174e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
175e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
176e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
177e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
178e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
179e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
180e0ae81f3SDag-Erling Smørgrav	during the next reboot.
181e0ae81f3SDag-Erling Smørgrav
1824717d22aSJohn Polstra20040614:
1834717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1844717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1854717d22aSJohn Polstra	the ips module and any third-party modules which call
1864717d22aSJohn Polstra	sema_timedwait.
1874717d22aSJohn Polstra
1886cb7a382SMax Laier20040613:
1896cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1906cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
191df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
192df843493SMax Laier	please recompile and reinstall world.
1936cb7a382SMax Laier
1942454685eSJulian Elischer20040607:
1952454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1962454685eSJulian Elischer	requires that you re-run config after updating your tree.
1972454685eSJulian Elischer
19864fef830SSeigo Tanimura20040601:
19964fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
20064fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
20164fef830SSeigo Tanimura	kernel configuration.
20264fef830SSeigo Tanimura
203bb4f06e7SAndre Oppermann20040423:
204bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
205bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
206bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
207bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
208bb4f06e7SAndre Oppermann
20905641e82SColin Percival20040420:
21005641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
21105641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
21205641e82SColin Percival	20040406.
21305641e82SColin Percival
214d0dc9183SWarner Losh20040414:
215d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
216d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
217d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
218d0dc9183SWarner Losh
219d0dc9183SWarner Losh20040412:
220d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
221d0dc9183SWarner Losh	drive is still broken.
222d0dc9183SWarner Losh
223d0dc9183SWarner Losh20040410:
224d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
225d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
226d0dc9183SWarner Losh	the unanticipated problems have been resolved.
227d0dc9183SWarner Losh
2288633bbeaSBrooks Davis20040409:
2298633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
2308633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
2318633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
2328633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
23376c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
2348633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
2358633bbeaSBrooks Davis
236d40d033aSRobert Watson20040322:
237d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
238d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
239d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
240d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
241d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
242d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
243d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
244d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
245d40d033aSRobert Watson	locking is merged to permit this to take place.
246d40d033aSRobert Watson
247ec9b318eSGarance A Drosehn20040310:
248ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
249ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
250ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
251ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
252ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
253ec9b318eSGarance A Drosehn
254fc28f1ffSMax Laier20040308:
255fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
256fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
2574c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
2584c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
259fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
260fc28f1ffSMax Laier	pf system consists of the following three devices:
261fc28f1ffSMax Laier	device		pf		# required
262fc28f1ffSMax Laier	device		pflog		# optional
263fc28f1ffSMax Laier	device		pfsync		# optional
264fc28f1ffSMax Laier
2653aff5d06SDag-Erling Smørgrav20040303:
2663aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
2673aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
2683aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
2693aff5d06SDag-Erling Smørgrav
2703aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
2713aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
2723aff5d06SDag-Erling Smørgrav
2733aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
2743aff5d06SDag-Erling Smørgrav	to use libpthread instead.
2753aff5d06SDag-Erling Smørgrav
276fd63c5b3SDag-Erling Smørgrav20040226:
2779d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
278fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
279fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
280fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
281fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
282fd63c5b3SDag-Erling Smørgrav
283714ae42aSBruce M Simpson20040225:
284e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
285e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
286e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
287e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
288e07a40f3SBrian Feldman	should remain unaffected.
289e07a40f3SBrian Feldman
290e07a40f3SBrian Feldman20040225:
291714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
292714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
293714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
294714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
295714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
296714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
297714ae42aSBruce M Simpson
298fbd2e692SAndre Oppermann20040224:
299fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
3005bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
301fbd2e692SAndre Oppermann
302158b90daSWarner Losh20040222:
303158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
304158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
305158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
306158b90daSWarner Losh	Drivers outside the tree will need to be updated.
307158b90daSWarner Losh
308b7b1e150SMike Makonnen20040207:
309b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
310b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
311b7b1e150SMike Makonnen
312aca89ee6SDaniel Eischen20040130:
313aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
314aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
315aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
316aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
317aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
318aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
319aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
320aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
321aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
322aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
323aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
324aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
325aca89ee6SDaniel Eischen	do not work with libpthread.
326aca89ee6SDaniel Eischen
32768b7b3a9SAlex Dupre20040125:
32868b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
32968b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
33068b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
33168b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
33268b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
33368b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
33468b7b3a9SAlex Dupre
335ff46e0deSWarner Losh20040125:
336ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
337ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
338ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
339ff46e0deSWarner Losh
340ce41f4bfSRobert Watson20031213:
341ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
342ce41f4bfSRobert Watson	if the login process is unable to successfully set the
343ce41f4bfSRobert Watson	process credentials to include all groups defined for the
344ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
345ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
346ce41f4bfSRobert Watson	defined, or they will be unable to log in.
347ce41f4bfSRobert Watson
348c124fa05SJohn Baldwin20031203:
349c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
350c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
351c124fa05SJohn Baldwin
3528ad1f5e4SHartmut Brandt20031112:
35330093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
35430093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
35597209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
35697209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
35797209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
35897209ca3SRobert Watson	not know about the new system calls that support the new statfs
3593f631d52SMarcel Moolenaar	structure.
3603f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
3613f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
3623f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
3633f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
3643f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
3653f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
3663f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
3673f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
3683f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
3693f631d52SMarcel Moolenaar	these changes are installed.
37030093b05SWarner Losh
37130093b05SWarner Losh	****************************DANGER*******************************
37230093b05SWarner Losh
37330093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
37430093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
37530093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
37630093b05SWarner Losh	kernel.
37764a18d6fSKirk McKusick
37864a18d6fSKirk McKusick20031112:
3798ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3808ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3818ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3828ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3838ad1f5e4SHartmut Brandt	sync before rebooting.
3848ad1f5e4SHartmut Brandt
385c53a5d8fSJohn Baldwin20031111:
386c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
387c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
388c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
389c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
390c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
391c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
392c53a5d8fSJohn Baldwin
3938bf455a5SJohn Baldwin20031103:
3948bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3958bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3962a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3978bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3988bf455a5SJohn Baldwin
3999bf40edeSBrooks Davis20031031:
4009bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
4019bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
4029bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
4039bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
4049bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
4059bf40edeSBrooks Davis	reflect this change.
4069bf40edeSBrooks Davis
40747a42c7aSPoul-Henning Kamp20030928:
40847a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
40947a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
4105bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
41147a42c7aSPoul-Henning Kamp
41207105342SMax Khon20030926:
41307105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
41407105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
41507105342SMax Khon
41617dcd026SSam Leffler20030925:
41717dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
41817dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
41917dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
42017dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
42117dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
42217dcd026SSam Leffler
423fedf1d01SBruce M Simpson20030923:
424fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
425fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
426fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
427fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
428fedf1d01SBruce M Simpson
429db38f9cbSJacques Vidrine20030915:
430db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
431db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
432db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
433db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
434db38f9cbSJacques Vidrine
435c09d2c2bSMike Makonnen20030829:
436c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
437c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
438c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
439c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
440c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
441c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
442c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
443c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
444c09d2c2bSMike Makonnen	may or may not exist on your system.
445c09d2c2bSMike Makonnen
44617c159dcSSøren Schmidt20030824:
44717c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
44817c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
449f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
450f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
45117c159dcSSøren Schmidt
452c1f61aa9SDavid E. O'Brien20030819:
453c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
454c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
455c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
456c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
45769f7bcf3SWarner Losh
45838c962e7SNate Lawson20030728:
45938c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
46038c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
46138c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
46238c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
46338c962e7SNate Lawson	so the quirk can be re-enabled.
46438c962e7SNate Lawson
46574111097SWarner Losh20030724:
46674111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
46774111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
46874111097SWarner Losh
469178cf4e9SWarner Losh20030722:
470178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
471178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
472178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
473178cf4e9SWarner Losh	FPU hardware.
474178cf4e9SWarner Losh
475178cf4e9SWarner Losh20030714:
476178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
477178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
478178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
479178cf4e9SWarner Losh	People should report those issues to current@.
480178cf4e9SWarner Losh
481157c629aSWarner Losh20030711:
482157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4838b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
48405538fa9SWarner Losh	/usr/obj.
485157c629aSWarner Losh
48674111097SWarner Losh20030610:
48774111097SWarner Losh	Remove deprecated locale names and transition period code
48874111097SWarner Losh	for them, finishing switching to the new scheme. Check your
48974111097SWarner Losh	LANG environment variable.
49074111097SWarner Losh
49174111097SWarner Losh20030609:
49274111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
49374111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
49474111097SWarner Losh	important to remember beforehand if your source tree is on
49574111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
49674111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
49774111097SWarner Losh	kernel.
49874111097SWarner Losh
49974111097SWarner Losh20030605:
5006cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
5016cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
5026cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
5036cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
5046cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
5056cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
5066cc6353fSMarcel Moolenaar
5076cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
5086cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
5096cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
5106cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
5116cc6353fSMarcel Moolenaar		:
5126cc6353fSMarcel Moolenaar
5136cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
5146cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
5156cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
5166cc6353fSMarcel Moolenaar
51752b47445SMark Murray20030505:
51852b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
51952b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
52052b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
52152b47445SMark Murray
522a26df538SWarner Losh20030502:
523a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
524a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
525a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
526a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
527a26df538SWarner Losh
5284b065e2cSDoug Barton20030501:
5294b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
5304b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
5314b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
5324b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
5334b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
5344b065e2cSDoug Barton	utilizes these old scripts has also been removed.
5354b065e2cSDoug Barton
53681cda3d9SWarner Losh20030423:
53781cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
53881cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
53981cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
54081cda3d9SWarner Losh	have until then to upgrade your kernel before updating
54181cda3d9SWarner Losh	userland.  In general, you should have a userland and
54281cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
54381cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
54481cda3d9SWarner Losh	allowances are made.
54581cda3d9SWarner Losh
54647a657d1SRuslan Ermilov20030329:
54747a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
54847a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
54947a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
55047a657d1SRuslan Ermilov
55147a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
55247a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
55347a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
55447a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
55547a657d1SRuslan Ermilov
55647a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
55747a657d1SRuslan Ermilov	    make cleandir && make obj && \
55847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
55947a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
56047a657d1SRuslan Ermilov
5615d2af00cSGregory Neil Shapiro20030208:
5625d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
5635d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
5645d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
5655d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
5665d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
5675d2af00cSGregory Neil Shapiro
5685d2af00cSGregory Neil Shapiro20030128:
5699db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
570ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
5719db58771SPoul-Henning Kamp	be removed when convenient.
5729db58771SPoul-Henning Kamp
5738d9b3f57SJake Burkholder20030126:
5748d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
5758d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
5768d9b3f57SJake Burkholder
5771c5efda5SJeff Roberson20030125:
5781c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5791c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
580ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5811c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5821c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5831c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5841c5efda5SJeff Roberson
5859d1d64f5SWarner Losh20030115:
5869d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5879d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5889d1d64f5SWarner Losh	properly.
5899d1d64f5SWarner Losh
590c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
591c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
592c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
593c9fdb80aSWarner Losh	with NetBSD.
594c9fdb80aSWarner Losh
595161dc364SAlexander Kabaev20021222:
596161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
597161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
598161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
599161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
600161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
601161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
60284cc83efSAlexander Kabaev	rebuilt.
603161dc364SAlexander Kabaev
604fb4c8061SMartin Blapp20021216:
605fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
60689056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
607fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
6089d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
609fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
610fb4c8061SMartin Blapp
61117d47eb3SGiorgos Keramidas20021202:
61217d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
61317d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
61417d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
61517d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
61617d47eb3SGiorgos Keramidas
617a4459294SBill Fenner20021029:
618a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
619a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
620a4459294SBill Fenner	consumers in sync.
621a4459294SBill Fenner
622fc8c157fSWarner Losh20021024:
623c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
624c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
625c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
626c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
627c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
628c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
629c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
630c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
63169f7bcf3SWarner Losh
632fd9e8bdaSAndrew Gallatin20021023:
633fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
634fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
635fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
636fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
637fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
638fd9e8bdaSAndrew Gallatin
639fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
640fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
641fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
642fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
643fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
644fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
645fd9e8bdaSAndrew Gallatin
646f8a4c901SWarner Losh20020831:
647f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
648f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
649f8a4c901SWarner Losh	programs and libraries need to be recompiled.
650f8a4c901SWarner Losh
651f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
652f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
653f8a4c901SWarner Losh
654c2248fa2SJens Schweikhardt20020827:
655c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
656c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
657c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
658c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
659c2248fa2SJens Schweikhardt
6600d533e43SRuslan Ermilov20020815:
6610d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
6620d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
6630d533e43SRuslan Ermilov	again.
6640d533e43SRuslan Ermilov
66533c1de7dSRuslan Ermilov20020729:
66633c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
66733c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
66833c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
66933c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
67033c1de7dSRuslan Ermilov
6712b877facSJulian Elischer20020702:
6722b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
6732b877facSJulian Elischer	There are still some minor problems with some signals but the
6742b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
6752b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
6762b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6772b877facSJulian Elischer
67806596d37SWarner Losh20020701:
67906596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
68006596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
68106596d37SWarner Losh	GNOME.
68206596d37SWarner Losh
68395ba4330SJacques Vidrine20020511:
68495ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
68595ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
68695ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
68795ba4330SJacques Vidrine	with the set-user-ID bit set.
68895ba4330SJacques Vidrine
689a81da3c9SDavid E. O'Brien20020510:
690f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
691f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6924b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
693f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
694f50caf6fSDavid E. O'Brien
695f50caf6fSDavid E. O'Brien20020510:
696a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
697a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
698a81da3c9SDavid E. O'Brien	and then do a cvs update.
699a81da3c9SDavid E. O'Brien
700528a0ef5SJacques Vidrine20020421:
701528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
702528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
703528a0ef5SJacques Vidrine
70485aa5a2eSGregory Neil Shapiro20020404:
70585aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
70685aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
70785aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
70885aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
70985aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
71085aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
71185aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
71285aa5a2eSGregory Neil Shapiro
7138f1e4358SRuslan Ermilov20020403:
7148f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
7158f1e4358SRuslan Ermilov
7162292c02eSWarner Losh20020315:
7172292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
7182292c02eSWarner Losh
71969f7bcf3SWarner Losh20020225:
72069f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
72169f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
72269f7bcf3SWarner Losh
7238f35c493SWarner Losh20020217:
7248f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
7258f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
7268f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
7278f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
7288f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
7298f35c493SWarner Losh
730835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
731835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
732835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
733835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
734835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
735835284beSWarner Losh	and group must be merged from src/etc/group and
736835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
737835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
738835284beSWarner Losh	mergemaster before this will work if you are updating from a
739835284beSWarner Losh	very old version of current.  The updating recipe has changed
740835284beSWarner Losh	as of this date.
741835284beSWarner Losh
742fa9401c1SWarner Losh20020112:
743fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
744fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
745fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
746fa9401c1SWarner Losh	you have local modifications, you can use
747fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
748fa9401c1SWarner Losh	/etc/pam.d.
749fa9401c1SWarner Losh
750fa9401c1SWarner Losh	Please see the following url for more details:
751fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
75247d0d01fSWarner Losh20011229:
75347d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
75447d0d01fSWarner Losh	networkfs_types, please note that it has changed
75547d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
75647d0d01fSWarner Losh
757514318a8SWarner Losh20011220:
758514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
759514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
760514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
761514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
762514318a8SWarner Losh	version have now been merged back into the base system's
763514318a8SWarner Losh	version now.  The only user-visible change resulting from this
764514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
765514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
766514318a8SWarner Losh	as well.  (There has never been rc file support for
767514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
768514318a8SWarner Losh	reverted by the time the changes are MFCed.)
769514318a8SWarner Losh
770514318a8SWarner Losh20011215:
771514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
772514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
773514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
774514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
775514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
776514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
777514318a8SWarner Losh	will need to be customized then for `odd' densities using
778514318a8SWarner Losh	fdcontrol(8).
779514318a8SWarner Losh
7802d22e2bfSWarner Losh20011209:
7812d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7822d22e2bfSWarner Losh	and truss(1) now works again.
7832d22e2bfSWarner Losh
7849e0428e2SWarner Losh20011207:
7859e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7869e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7879e0428e2SWarner Losh	see
7889e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7899e0428e2SWarner Losh	for details.
7909e0428e2SWarner Losh
7919bab8c59SWarner Losh20011204:
7929bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7939bab8c59SWarner Losh	kernel and burncd to be in sync.
7949bab8c59SWarner Losh
795e57d8b01SWarner Losh20011203:
796e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
797e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
798e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
799e57d8b01SWarner Losh	not there already.
800e57d8b01SWarner Losh
801e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
802e57d8b01SWarner Losh	until the issue has been resolved.
803e57d8b01SWarner Losh
804b001d36fSJacques Vidrine20011202:
805b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
806b001d36fSJacques Vidrine	patched.
807b001d36fSJacques Vidrine
8084b676ec1SWarner Losh20011126:
8094b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
8105ebbf43eSWarner Losh	after this date.  You need to do this only once.
8114b676ec1SWarner Losh
812d961e462SWarner Losh20011103:
813d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
814d961e462SWarner Losh	edges may be left, but for the most part things should be
8154b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
816d961e462SWarner Losh
817d961e462SWarner Losh20011030:
818d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
819d961e462SWarner Losh	choppy waves in the upgrade process.
820d961e462SWarner Losh
8211fe003b6SWarner Losh20011030:
822a4b6fda0SWarner Losh	The asr driver problem has been resolved.
8231fe003b6SWarner Losh
8241fe003b6SWarner Losh20011027:
8251fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
8261fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
8271fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
8281fe003b6SWarner Losh	try to use from this date forward.
8291fe003b6SWarner Losh
8301fe003b6SWarner Losh20011025:
8311fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
8321fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
8331fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
8341fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
8351fe003b6SWarner Losh	TARGET_ARCH=i386.
8361fe003b6SWarner Losh
837d05f9643SWarner Losh20011001:
838d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
839d05f9643SWarner Losh	You must recompile both the kernel and userland applications
840d05f9643SWarner Losh	at the same time.
841d05f9643SWarner Losh
84258970f85SWarner Losh20010929:
84358970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
84458970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
84558970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
84658970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
8479d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
84858970f85SWarner Losh
84958970f85SWarner Losh20010927:
85058970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
85158970f85SWarner Losh	To disable ACPI you can add
85266ff0e67SMax Khon		hint.acpi.0.disabled="1"
85358970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
85458970f85SWarner Losh	loader "ok" prompt).
85558970f85SWarner Losh
85658970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
85758970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
85858970f85SWarner Losh	file and not list acpi in that list.
859378f4486SAlfred Perlstein
8605119d237SWarner Losh20010924:
8615119d237SWarner Losh	The buildworld has been fixed.  You may need to install
8625119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8638b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
8648b039fffSWarner Losh	get them installed on every installworld, or execute the
8658b039fffSWarner Losh	following to get them installed only once:
8668b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
86758970f85SWarner Losh		make all install
8688b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
8695119d237SWarner Losh
8703c293725SWarner Losh20010919:
8713c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
8723c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
8733c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
874772730c7SWarner Losh	workaround is to add
8753c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
8763c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8773c293725SWarner Losh	can be removed afterwards.
8783c293725SWarner Losh
8793c293725SWarner Losh	A proper fix to the buildworld target is needed.
8803c293725SWarner Losh
8813c293725SWarner Losh20010918:
8823c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8833c293725SWarner Losh	NFS may be unstable after this date.
8843c293725SWarner Losh
8853c293725SWarner Losh20010912:
8863c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8873c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8883c293725SWarner Losh	initial commit, most of the major ones have been found and
8893c293725SWarner Losh	corrected.
8903c293725SWarner Losh
8913c293725SWarner Losh20010901:
8923c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8933c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8943c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8953c293725SWarner Losh	have been rectified around this date.
8963c293725SWarner Losh
89798b17b95SWarner Losh20010823:
89898b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
89998b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
90098b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
90198b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
90298b17b95SWarner Losh 	sure that user or group bind has read (and not write)
90398b17b95SWarner Losh 	permission for your name server configuration and that it
90498b17b95SWarner Losh 	has read and write permission for your slave zone files and
90598b17b95SWarner Losh 	directory.
90698b17b95SWarner Losh
90798b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
90898b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
90998b17b95SWarner Losh
91098b17b95SWarner Losh 		named_flags=
91198b17b95SWarner Losh
9127b9786edSMark Murray20010709:
9137b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
9147b9786edSMark Murray	the ability of the shared library major number to handle.
9157b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
9167b9786edSMark Murray	solution is to rebuild those ports.
9177b9786edSMark Murray
9181d28950eSWarner Losh20010628:
9191d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
9201d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
9211d28950eSWarner Losh
922e72fd46aSWarner Losh20010625:
92398b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
92498b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
92598b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
92698b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
92798b17b95SWarner Losh	IRQ configuration needs more safety belts.
92816de1a07SWarner Losh
9290d415dffSWarner Losh20010617:
930e72fd46aSWarner Losh	Softupdates problems have been corrected.
9310d415dffSWarner Losh
9320d415dffSWarner Losh20010614:
9330d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
9340d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
9350d415dffSWarner Losh	kernel building methods.
9360d415dffSWarner Losh
9378b9959adSWarner Losh20010613:
9388b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
9398b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
940e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
941e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
9428b9959adSWarner Losh
943e72fd46aSWarner Losh20010613:
9448b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
945e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
946e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
9478b9959adSWarner Losh
9480d415dffSWarner Losh20010612:
9490d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
9500d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
9510d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
9520d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
9530d415dffSWarner Losh	until this bug is fixed.
9540d415dffSWarner Losh
955e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
956e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
957ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
958e72fd46aSWarner Losh
9590d415dffSWarner Losh20010610:
9600d415dffSWarner Losh	Locale names have changed to match other systems better.
9610d415dffSWarner Losh
9626ccdb5e4SWarner Losh20010604:
9636ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
9646ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
9656ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
9663590182eSWarner Losh	Interrupt storms look a lot like a hang.
9673590182eSWarner Losh
9683590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
9693590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
9703590182eSWarner Losh	it is).
9713590182eSWarner Losh
9723590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
9733590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
9743590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
9753590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
9766ccdb5e4SWarner Losh
9770bc62786SWarner Losh20010530:
9780bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9790bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9800bc62786SWarner Losh	a limited time.  If you see
9810bc62786SWarner Losh
9820bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9830bc62786SWarner Losh
9840bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9850bc62786SWarner Losh	COPY=-C.
9860bc62786SWarner Losh
98768a38c6cSWarner Losh20010525:
988b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
989c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
990c4f4a728SWarner Losh	definitely is in bad shape.
99168a38c6cSWarner Losh
992ed0f29caSWarner Losh20010521:
993ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
994ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
995ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
996ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
997ed0f29caSWarner Losh	is
998ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
999ed0f29caSWarner Losh
100080c16af9SWarner Losh20010520:
100168a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
100280c16af9SWarner Losh
100380c16af9SWarner Losh20010519:
100480c16af9SWarner Losh	pccard has had much reorganizational work done to it over
100580c16af9SWarner Losh	the past few days.  Everything should still work, but if
100680c16af9SWarner Losh	not, please contact imp@freebsd.org.
100780c16af9SWarner Losh
1008a45f2d05SWarner Losh20010517:
1009a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
1010a45f2d05SWarner Losh	userland at the same time.
1011a45f2d05SWarner Losh
1012a45f2d05SWarner Losh20010517:
1013a45f2d05SWarner Losh	New ncurses imported.
1014a45f2d05SWarner Losh
10152988afcaSWarner Losh20010512:
10162988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
10172988afcaSWarner Losh	will be the only way to go starting July 1.
10182988afcaSWarner Losh
10191a33dba7SWarner Losh20010504:
10201a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
10211a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
10221a33dba7SWarner Losh
102309946a51SWarner Losh20010502:
102409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
102509946a51SWarner Losh
102609946a51SWarner Losh20010501:
102709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
102809946a51SWarner Losh
102909946a51SWarner Losh20010430:
1030a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
103109946a51SWarner Losh	go back in the water.
103209946a51SWarner Losh
103309946a51SWarner Losh20010429:
103409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
103509946a51SWarner Losh	this date, but before the correction date.
103609946a51SWarner Losh
103791dd3b53SWarner Losh20010423:
103891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
103991dd3b53SWarner Losh
104091dd3b53SWarner Losh20010411:
104191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
104291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
104391dd3b53SWarner Losh	Update only if you understand that you must not use the old
104491dd3b53SWarner Losh	fsck with the new kernel ever.
104591dd3b53SWarner Losh
1046933b3269SWarner Losh20010330:
1047933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1048c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1049933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1050933b3269SWarner Losh
1051933b3269SWarner Losh20010319:
1052933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1053933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1054933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1055f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
105609946a51SWarner Losh
105709946a51SWarner Losh20010315:
105809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1059ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
106009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1061933b3269SWarner Losh
1062933b3269SWarner Losh20010312:
1063933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1064933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1065933b3269SWarner Losh
1066933b3269SWarner Losh20010312:
1067933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1068933b3269SWarner Losh	instead of ad-hoc.
1069933b3269SWarner Losh
1070933b3269SWarner Losh20010310:
1071f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1072933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1073933b3269SWarner Losh	ssh might not work if you don't.
1074933b3269SWarner Losh
107562353691SWarner Losh20010303:
107662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
107762353691SWarner Losh	which means that you must include the miibus in your kernel if
107862353691SWarner Losh	you use the ed driver.
107962353691SWarner Losh
1080d325cf65SWarner Losh20010220:
1081d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1082d325cf65SWarner Losh	safe to go back into the water.
1083d325cf65SWarner Losh
1084024daae6SWarner Losh20010211:
1085024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1086024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1087024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1088024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1089024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1090024daae6SWarner Losh
1091024daae6SWarner Losh	To get to the new system, you'll need to use the following
1092024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1093024daae6SWarner Losh	don't have to move this to the updating section.
1094024daae6SWarner Losh
1095024daae6SWarner Losh	To get around the installworld problem, do:
1096024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1097024daae6SWarner Losh		# make install
1098024daae6SWarner Losh		# cd /usr/src
1099024daae6SWarner Losh		# make installworld
1100024daae6SWarner Losh	If that doesn't work, then try:
1101024daae6SWarner Losh		# make -k installworld
1102024daae6SWarner Losh		# make installworld
1103024daae6SWarner Losh
1104024daae6SWarner Losh20010207:
1105024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1106024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1107024daae6SWarner Losh
1108024daae6SWarner Losh20010205:
11097595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1110024daae6SWarner Losh	Remove them from your config.
1111024daae6SWarner Losh
11121e159248SWarner Losh20010122:
11131e159248SWarner Losh	****************************** WARNING ******************************
11141e159248SWarner Losh			buildkernel has been changed slightly
11151e159248SWarner Losh	****************************** WARNING ******************************
11161e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
11171e159248SWarner Losh	should update your scripts and make.conf accordingly.
11181e159248SWarner Losh
11191e159248SWarner Losh20010119:
11201e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
11211e159248SWarner Losh	This requires a new config to build correctly.
11221e159248SWarner Losh
1123aac7dfeaSWarner Losh20010116:
1124ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1125aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1126aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1127aac7dfeaSWarner Losh
1128aac7dfeaSWarner Losh20010110:
1129aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1130aac7dfeaSWarner Losh
1131aac7dfeaSWarner Losh20010102:
1132aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1133aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1134aac7dfeaSWarner Losh
113563c90c9eSWarner Losh20010101:
113663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
113763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
11385fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
113963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
114063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
114163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
114263c90c9eSWarner Losh	might have been ignored by the -k option.
114363c90c9eSWarner Losh
11445fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
11455fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
11465fd2a895SWarner Losh	of this working.
11475fd2a895SWarner Losh
1148aac7dfeaSWarner Losh20001228:
1149aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1150ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1151aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1152aac7dfeaSWarner Losh
1153de2bcc63SWarner Losh20001218:
1154de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1155de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1156de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1157de2bcc63SWarner Losh	cards will not be recognized without it.
1158de2bcc63SWarner Losh
1159960773f7SWarner Losh20001205:
1160960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1161960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1162960773f7SWarner Losh	adding the following in pam.conf:
1163960773f7SWarner Losh
1164960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1165960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1166960773f7SWarner Losh	sshd    session required        pam_permit.so
1167960773f7SWarner Losh
11680acc635eSWarner Losh20001031:
11690acc635eSWarner Losh	cvs updated to 1.11.
11700acc635eSWarner Losh
11710acc635eSWarner Losh20001020:
11720acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
11730acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
11740acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
11750acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
11760acc635eSWarner Losh	workaround.
11770acc635eSWarner Losh
11780acc635eSWarner Losh20001010:
11790acc635eSWarner Losh	****************************** WARNING ******************************
11800acc635eSWarner Losh				Sendmail has been updated.
11810acc635eSWarner Losh	****************************** WARNING ******************************
11820acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11830acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11840acc635eSWarner Losh	  is set.
11850acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11860acc635eSWarner Losh	  commands.
11870acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11880acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11890acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11900acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11910acc635eSWarner Losh
11920acc635eSWarner Losh	More details can be found at
11930acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11940acc635eSWarner Losh
11956e98a146SWarner Losh20001009:
11966e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11976e98a146SWarner Losh	your entire ports tree, or you will have problems.
11986e98a146SWarner Losh
11996e98a146SWarner Losh20001006:
1200685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
12016e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
12026e98a146SWarner Losh	/usr/bin/miniperl.
12036e98a146SWarner Losh
1204073113a4SWarner Losh20001005:
1205073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1206685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1207073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1208073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1209073113a4SWarner Losh	tree for anything to work.
1210073113a4SWarner Losh
12110acc635eSWarner Losh20000928:
12120acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
12130acc635eSWarner Losh
1214be3885b3SWarner Losh20000916:
1215be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1216be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1217be3885b3SWarner Losh	same time as your kernel.
1218be3885b3SWarner Losh
121976ec9675SWarner Losh20000914:
122076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
122176ec9675SWarner Losh	include the device will cause suspended laptops losing time
122276ec9675SWarner Losh	when they resume.  Include
122376ec9675SWarner Losh		device		pmtimer
122476ec9675SWarner Losh	in your config file and
122501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
122676ec9675SWarner Losh	to your /boot/device.hints file.
122776ec9675SWarner Losh
1228f4865386SMark Murray20000911:
1229f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1230f4865386SMark Murray	rather than an option. The supplied kernel config files have
1231f4865386SMark Murray	been updated. You will need to do something similar in your
1232f4865386SMark Murray	own kernel config file.
1233f4865386SMark Murray	Remove:
1234f4865386SMark Murray		options		RANDOMDEV
1235f4865386SMark Murray	Add:
1236f4865386SMark Murray		device		random
1237f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1238f4865386SMark Murray	nothing.
1239f4865386SMark Murray
1240d594498fSWarner Losh20000909:
1241d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1242d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1243d594498fSWarner Losh	reflect this if you load this module at boot time.
1244d594498fSWarner Losh	The line should read:
1245d594498fSWarner Losh		random_load="YES"
1246d594498fSWarner Losh
12470deb7ddcSWarner Losh20000907:
12480deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
124916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
125016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
125116eb772dSWarner Losh	sure you don't have model loading problems which might at
125216eb772dSWarner Losh	first blush appear related to SMP.
125352bf24e7SWarner Losh
12545a01880bSWarner Losh20000906:
12555a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
12565a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
12575a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
12585a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
12595a01880bSWarner Losh	don't have one, and you have host.conf.
12605a01880bSWarner Losh
12612b41163cSWarner Losh20000905:
126238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
126338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
126438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
126538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
126638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
126738d6ecd2SWarner Losh
126838d6ecd2SWarner Losh20000905:
12698aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
12708aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
12718aab4bc7SWarner Losh	is /boot/kernel.
12728aab4bc7SWarner Losh
12738aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
127438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
127538d6ecd2SWarner Losh	installkernel/installworld dance.
12762b41163cSWarner Losh
1277d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1278d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1279d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1280d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1281d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1282d594498fSWarner Losh
1283d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1284d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1285d594498fSWarner Losh		chflags noschg /kernel.old
1286d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1287d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1288d594498fSWarner Losh	fi
1289d594498fSWarner Losh
1290c22a309cSWarner Losh20000904:
1291c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1292c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1293c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1294c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1295c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1296c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1297c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1298c22a309cSWarner Losh	is not likely to be generated.
1299c22a309cSWarner Losh
1300fdb9f54dSWarner Losh20000825:
1301fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
13029c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
13039c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
13049c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
13059c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
13069c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
13079c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
13089c1a7444SWarner Losh	kernel.
13099c1a7444SWarner Losh
13109c1a7444SWarner Losh20000821:
13119c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
13129c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
13139c1a7444SWarner Losh	/boot/loader.conf.
1314fdb9f54dSWarner Losh
13158f250aa7SWarner Losh20000812:
13165da0d091SWarner Losh	suidperl is now always built and installed on the system, but
13175da0d091SWarner Losh	with permissions of 511.  If you have applications that use
13185da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
13195da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
13205da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
13215da0d091SWarner Losh	will fix this until the next build.
13225da0d091SWarner Losh
13235da0d091SWarner Losh20000812:
13248f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
13258f250aa7SWarner Losh	visible changes that may immediately affect your configuration
13268f250aa7SWarner Losh	include:
13278f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
13288f250aa7SWarner Losh	- newaliases limited to root and trusted users
13298f250aa7SWarner Losh	- MSA port (587) turned on by default
13308f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
13318f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
13328f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
13338f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
13348f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
13358f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
13368f250aa7SWarner Losh
133771c38472SWarner Losh20000810:
133871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
133971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
134071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
134171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
134271c38472SWarner Losh	specific use for it.
134371c38472SWarner Losh
134471c38472SWarner Losh20000729:
134571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
134671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
134771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
134871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
134971c38472SWarner Losh		# Enable network daemons for user convenience.
135071c38472SWarner Losh		inetd_enable="YES"
135171c38472SWarner Losh		portmap_enable="YES"
135271c38472SWarner Losh		sendmail_enable="YES"
135371c38472SWarner Losh
135471c38472SWarner Losh20000728:
135571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
135671c38472SWarner Losh	will need to change that to nullfs_load="YES".
135771c38472SWarner Losh
13581dece4a9SWarner Losh20000728:
13591dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
13601dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
13611dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
13621dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
13631dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
13641dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
13651dece4a9SWarner Losh	to /MYKERNEL.
13661dece4a9SWarner Losh
1367409e887cSWarner Losh20000711:
1368409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1369409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1370409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1371409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1372409e887cSWarner Losh	for details on potential problems that you might have and how
1373409e887cSWarner Losh	to get around them.
1374409e887cSWarner Losh
1375409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1376409e887cSWarner Losh	clauses above, you needn't worry.
1377409e887cSWarner Losh
1378409e887cSWarner Losh20000711:
1379409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1380409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1381409e887cSWarner Losh	in the number of changed programs the first time when you run
1382409e887cSWarner Losh	mergemaster to get a new /etc/security.
1383409e887cSWarner Losh
1384673d13f2SWarner Losh20000710:
1385673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1386673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1387673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1388673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1389673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1390673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1391673d13f2SWarner Losh	errors. (see below, 20000624).
1392673d13f2SWarner Losh
1393bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13941dece4a9SWarner Losh
1395673d13f2SWarner Losh20000709:
1396c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1397c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1398c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1399673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1400673d13f2SWarner Losh
1401e98e26cdSWarner Losh20000706:
1402e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1403e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1404e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1405f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1406e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
14072c021c6cSMark Ovens	interim if needed.
1408e98e26cdSWarner Losh
1409e98e26cdSWarner Losh20000705:
1410e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1411e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1412e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1413e98e26cdSWarner Losh	details.
1414e98e26cdSWarner Losh
1415c373950eSWarner Losh20000704:
14162f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
14172f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
14182f961bc8SWarner Losh
14192f961bc8SWarner Losh20000704:
1420c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1421c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1422c373950eSWarner Losh	rc.d scripts that haven't been updated.
1423c373950eSWarner Losh
142427dc3a2bSWarner Losh20000630:
142527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
142627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
142727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
142827dc3a2bSWarner Losh
1429b8c215acSWarner Losh20000625:
1430b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
143127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
143227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
143327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
143427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
143527dc3a2bSWarner Losh	were required.  You should check with the latest collections
143627dc3a2bSWarner Losh	to make sure that these haven't changed.
1437b8c215acSWarner Losh
14387b990719SWarner Losh20000624:
14397b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
14407b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
14417b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
14421a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
14437b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
14447b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
14457b990719SWarner Losh	date to the completion of the work.
14467b990719SWarner Losh
144727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
144827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
144927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
145027dc3a2bSWarner Losh	recreate the random and urandom devices.
145127dc3a2bSWarner Losh
145281e54c50SWarner Losh20000622:
145381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
145481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
145581e54c50SWarner Losh	that used to be required when updating.
145681e54c50SWarner Losh
145739943833SWarner Losh20000621:
14582c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
14592a2f33fbSDaniel Baker	the config file update procedure.
14602a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1461c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
146259df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
146359df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
146439943833SWarner Losh
1465290f9ad8SWarner Losh20000620:
1466290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1467290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1468290f9ad8SWarner Losh	that workaround will no longer be required.
1469290f9ad8SWarner Losh
147090fb6346SWarner Losh20000615:
147190fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
147290fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
147390fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
147490fb6346SWarner Losh	devices.
147590fb6346SWarner Losh
1476f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1477f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1478f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1479f75f65bbSWarner Losh	may work).
1480f75f65bbSWarner Losh
1481ba26da8eSWarner Losh20000612:
1482ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1483290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1484c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1485290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1486f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1487f54a3542SWarner Losh	NEWCARD for examples of the new format.
1488290f9ad8SWarner Losh
14899698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14909698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14919698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14929698f2c0SWarner Losh	in it.
1493bbcc5149SWarner Losh
1494d65850ebSWarner Losh20000522:
1495ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1496d65850ebSWarner Losh	building a kernel after this point is advised that they need
1497d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1498d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1499d65850ebSWarner Losh
1500d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1501d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1502d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1503d9583a00SWarner Losh	is resolved.
1504d9583a00SWarner Losh
15058039cedeSWarner Losh20000513:
15068039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
15078039cedeSWarner Losh
1508d65850ebSWarner Losh20000510:
15098039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
15108039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
15118039cedeSWarner Losh	is requires for the boot blocks to build properly.
15128039cedeSWarner Losh
15138039cedeSWarner Losh20000503:
15148039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
15158039cedeSWarner Losh	is now available.
15168039cedeSWarner Losh
1517d65850ebSWarner Losh20000502:
1518d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1519d65850ebSWarner Losh	connected to the kernel building instead.
1520d65850ebSWarner Losh
1521be149406SNik Clayton20000427:
15228039cedeSWarner Losh	You may need to build gperf
15238039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
15248039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
15258039cedeSWarner Losh	an option only in -current.
15268039cedeSWarner Losh
15272b8dd5f4SWarner Losh20000417:
15282b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1529f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
15302b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
15312b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
15322c021c6cSMark Ovens	before you reboot, you'll need to issue:
15332b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
15342b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
15352b8dd5f4SWarner Losh
15368d9f1945SWarner Losh20000320:
15372b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
15382b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
15392b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1540ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
15412b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
15428d9f1945SWarner Losh
1543f8ab1dd6SWarner Losh20000319:
1544f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1545f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1546f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1547f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1548f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1549f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1550f8ab1dd6SWarner Losh
155119cada77SWarner Losh20000318:
1552f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
155319cada77SWarner Losh	Large kernel changes are being committed and are in the
155419cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
155519cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
155619cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
155719cada77SWarner Losh	that you are loading are up to date.
1558ba228352SWarner Losh
155919cada77SWarner Losh20000315:
15606d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
15616d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
15626d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
15636d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
15646d23c382SWarner Losh	boot.
15656d23c382SWarner Losh
15666d23c382SWarner Losh20000315:
156719cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
156819cada77SWarner Losh	to upgrade to 4.0 from 3.x.
156957199806SWarner Losh
1570dc0dbf5cSWarner LoshCOMMON ITEMS:
1571dc0dbf5cSWarner Losh
1572a24eff53SWarner Losh	General Notes
1573a24eff53SWarner Losh	-------------
1574a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1575a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1576a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1577a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1578a24eff53SWarner Losh	or several minor releases, or when several months have passed
1579a24eff53SWarner Losh	on the -current branch).
1580a24eff53SWarner Losh
15815780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15825780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15835780f3baSWarner Losh	environment when searching for values for global variables.
15845780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15855780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15865780f3baSWarner Losh	page for more details.
15875780f3baSWarner Losh
1588dc0dbf5cSWarner Losh	To build a kernel
1589dc0dbf5cSWarner Losh	-----------------
1590ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1591f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1592ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1593282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1594282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1595dc0dbf5cSWarner Losh
1596ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1597ba01eb20SWarner Losh	--------------------------------------------------------------
15980fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15990fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
16000fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
16010fbd2da9SKen Smith
16020fbd2da9SKen Smith	cd src/sys/${arch}/conf
160347d0d01fSWarner Losh	config KERNEL_NAME_HERE
16040fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1605ba01eb20SWarner Losh	make depend
1606ba01eb20SWarner Losh	make
1607ba01eb20SWarner Losh	make install
1608ba01eb20SWarner Losh
1609ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1610ba01eb20SWarner Losh
1611ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1612ba01eb20SWarner Losh	-----------------------------------------------------------
161363cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
161463cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
161563cb445eSWarner Losh
1616f643de42SWarner Losh	<make sure you have good level 0 dumps>
161763cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
161863cb445eSWarner Losh	make buildworld
161963cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
162063cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
162163cb445eSWarner Losh							[1]
162263cb445eSWarner Losh	<reboot in single user>				[3]
16238633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
162463cb445eSWarner Losh	mergemaster -p					[5]
162563cb445eSWarner Losh	make installworld
162663cb445eSWarner Losh	mergemaster					[4]
162763cb445eSWarner Losh	<reboot>
162863cb445eSWarner Losh
1629759f0aefSWarner Losh
1630f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1631f27b1fceSJoseph Koshy	--------------------------------------------------
1632f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1633f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1634f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1635f27b1fceSJoseph Koshy	# size.
1636f27b1fceSJoseph Koshy
1637f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1638f27b1fceSJoseph Koshy	<boot into -stable>
1639f27b1fceSJoseph Koshy	make buildworld
1640f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1641f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1642f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1643f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1644f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1645f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1646f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1647f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1648f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1649f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1650f27b1fceSJoseph Koshy	<reboot into current>
1651f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1652f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1653f27b1fceSJoseph Koshy 	<reboot>
1654f27b1fceSJoseph Koshy
1655f27b1fceSJoseph Koshy
1656f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1657f27b1fceSJoseph Koshy	----------------------------------------------
16585c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
16595c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
16605c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
16615c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1662ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1663f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1664f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1665f643de42SWarner Losh	# space on /.
1666f643de42SWarner Losh
1667f643de42SWarner Losh	<make sure you have good level 0 dumps>
1668fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
166921c075eaSWarner Losh	make buildworld					[9]
1670c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1671802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1672be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1673802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1674fc8c157fSWarner Losh							[1]
1675fc8c157fSWarner Losh	<reboot in single user>				[3]
1676802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1677835284beSWarner Losh	mergemaster -p					[5]
1678f8a4c901SWarner Losh	rm -rf /usr/include/g++
1679ba26da8eSWarner Losh	make installworld
1680802fc49dSBrian Feldman	mergemaster -i					[4]
1681ba26da8eSWarner Losh	<reboot>
1682ba26da8eSWarner Losh
1683fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1684fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1685fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1686fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1687fdb9f54dSWarner Losh	the UPDATING entries.
1688ba26da8eSWarner Losh
16891dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16901dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16911dece4a9SWarner Losh	your sources that you have read and understood all the recent
16921dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16931dece4a9SWarner Losh	much fewer pitfalls.
16941dece4a9SWarner Losh
1695134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1696134d2e86SWarner Losh	should disable them at this point so they don't crash your
1697134d2e86SWarner Losh	system on reboot.
1698134d2e86SWarner Losh
16999c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
17009c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
17019c1a7444SWarner Losh	configuration.
17029c1a7444SWarner Losh
1703ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1704ee6e1fc3SWarner Losh		fsck -p
1705ee6e1fc3SWarner Losh		mount -u /
1706ee6e1fc3SWarner Losh		mount -a
1707ee6e1fc3SWarner Losh		cd /usr/src
170847d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1709f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1710f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
171166986952SRuslan Ermilov	For the 4.x -> 5.x upgrade, you will also see many messages about
1712b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1713b705ae10SWarner Losh	be ignored while you proceed to the next step.
1714ee6e1fc3SWarner Losh
1715a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1716a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1717a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1718a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1719a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1720a6cd4f9dSWarner Losh	for potential gotchas.
1721a6cd4f9dSWarner Losh
1722835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1723835284beSWarner Losh	you may need to do this if you get unknown user in the following
1724835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1725835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1726835284beSWarner Losh	install) after the buildworld before this step if you last updated
1727835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1728835284beSWarner Losh
1729bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1730bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1731bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1732bd79cf40SWarner Losh		ok unload
1733bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1734bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1735bd79cf40SWarner Losh	described here.
1736fc8c157fSWarner Losh
1737fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1738fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1739fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1740fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1741fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1742fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1743fc8c157fSWarner Losh
1744c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1745c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1746c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1747c74fe6afSWarner Losh	that is hard to boot to recover.
1748c74fe6afSWarner Losh
174921c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1750802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1751802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1752802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1753802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1754802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
175566986952SRuslan Ermilov	compatibility libraries are built which should allow you to continue
1756802fc49dSBrian Feldman	using your existing software for a while.
17578633bbeaSBrooks Davis
17588633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
175966986952SRuslan Ermilov	initialized by feeding data into it.  /usr/src/etc/rc.d/preseedrandom
17608633bbeaSBrooks Davis	takes care of this.
1761dc0dbf5cSWarner LoshFORMAT:
1762dc0dbf5cSWarner Losh
1763f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
17641fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1765f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1766f8ab1dd6SWarner Loshprevious releases if your system is older than this.
17671fc1a0dcSWarner Losh
1768e72fd46aSWarner LoshCopyright information:
1769e72fd46aSWarner Losh
17709698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1771e72fd46aSWarner Losh
1772772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1773772730c7SWarner Loshmodification, in full or in part, in any form or format of this
17749698f2c0SWarner Loshdocument are permitted without further permission from the author.
1775e72fd46aSWarner Losh
1776e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1777e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1778e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1779e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1780e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1781e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1782e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1783e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1784e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1785e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1786e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1787e72fd46aSWarner Losh
1788e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1789e72fd46aSWarner Loshauthor a beer.
1790e72fd46aSWarner Losh
179122306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1792772730c7SWarner Loshthis document.
1793772730c7SWarner Losh
179497d92980SPeter Wemm$FreeBSD$
1795