xref: /freebsd/UPDATING (revision 8f075db49af6db4f5fd29408aa19593cfa217d20)
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
248f075db4SMark Murray20040802:
258f075db4SMark Murray	making /dev/(null|zero) into a module proved to be too unpopular,
268f075db4SMark Murray	so this bit has been revoked from the previous (20040801) entry.
278f075db4SMark Murray
28d064d6dbSMark Murray20040801:
29d064d6dbSMark Murray	The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
30d064d6dbSMark Murray	so you may wish to add them to your kernel config file. See
31d064d6dbSMark Murray	GENERIC for examples.
32d064d6dbSMark Murray
33b289983eSAlexander Kabaev20040728:
3454bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
3554bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
3654bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
3754bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
3854bd5271SAlexander Kabaev	compiler. A new unit-at-a-time optimization mode, which is default
3954bd5271SAlexander Kabaev	in this compiler release, is more aggressive in removing unused
4054bd5271SAlexander Kabaev	static symbols. This is the likely cause of 'make buildworld'
4154bd5271SAlexander Kabaev	breakages with non-default CFLAGS where optimization level is set
4254bd5271SAlexander Kabaev	to -O2 or higher.
4354bd5271SAlexander Kabaev
4436ed21e6SRobert Watson20040727:
4536ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
4636ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
4736ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
4836ed21e6SRobert Watson	a result.
4936ed21e6SRobert Watson
506305ac24SSeigo Tanimura20040716:
516305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
526305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
536305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
546305ac24SSeigo Tanimura
55e623dcb7SMarcel Moolenaar20040710:
56e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
57e623dcb7SMarcel Moolenaar
58e623dcb7SMarcel Moolenaar20040710:
59e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
60e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
61e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
62e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
63e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
64e623dcb7SMarcel Moolenaar	of this.
65e623dcb7SMarcel Moolenaar
66e623dcb7SMarcel Moolenaar20040710:
67e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
68e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
69e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
70e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
71e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
72e623dcb7SMarcel Moolenaar	   option for this.
73e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
74e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
75e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
76e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
775bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
78e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
79e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
80e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
81e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
82e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
83e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
84e623dcb7SMarcel Moolenaar
856421d1dbSMaksim Yevmenkin20040708:
866421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
876421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
886421d1dbSMaksim Yevmenkin
8958af3216SWarner Losh20040702:
9058af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
915bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
925bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
935bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
9458af3216SWarner Losh	scheduler as a workaround.
9558af3216SWarner Losh
96c2dba668SNate Lawson20040630:
978ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
988ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
99a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
100a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
101a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
102a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
103a6c26e1cSBruce M Simpson	example of such changes.
1048ed370fdSJulian Elischer
10558af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
10658af3216SWarner Losh	over.
10758af3216SWarner Losh
1088ed370fdSJulian Elischer20040630:
109c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
1105bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
111c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
112c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
113c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
114c2dba668SNate Lawson	loader prompt.
115c2dba668SNate Lawson
1168ee2ac9eSMax Laier20040623:
1175bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
1188ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
1198ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
1208ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
1218ee2ac9eSMax Laier
1223db5687dSBrooks Davis20040622:
1233db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
1243db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
1253db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
1263db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
1273db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
1283db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
1293db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
1303db5687dSBrooks Davis
131e0ae81f3SDag-Erling Smørgrav20040621:
132e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
133e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
134e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
135e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
136e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
137e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
138e0ae81f3SDag-Erling Smørgrav	during the next reboot.
139e0ae81f3SDag-Erling Smørgrav
1404717d22aSJohn Polstra20040614:
1414717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1424717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1434717d22aSJohn Polstra	the ips module and any third-party modules which call
1444717d22aSJohn Polstra	sema_timedwait.
1454717d22aSJohn Polstra
1466cb7a382SMax Laier20040613:
1476cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1486cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
149df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
150df843493SMax Laier	please recompile and reinstall world.
1516cb7a382SMax Laier
1522454685eSJulian Elischer20040607:
1532454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1542454685eSJulian Elischer	requires that you re-run config after updating your tree.
1552454685eSJulian Elischer
15664fef830SSeigo Tanimura20040601:
15764fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
15864fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
15964fef830SSeigo Tanimura	kernel configuration.
16064fef830SSeigo Tanimura
161bb4f06e7SAndre Oppermann20040423:
162bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
163bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
164bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
165bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
166bb4f06e7SAndre Oppermann
16705641e82SColin Percival20040420:
16805641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
16905641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
17005641e82SColin Percival	20040406.
17105641e82SColin Percival
172d0dc9183SWarner Losh20040414:
173d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
174d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
175d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
176d0dc9183SWarner Losh
177d0dc9183SWarner Losh20040412:
178d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
179d0dc9183SWarner Losh	drive is still broken.
180d0dc9183SWarner Losh
181d0dc9183SWarner Losh20040410:
182d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
183d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
184d0dc9183SWarner Losh	the unanticipated problems have been resolved.
185d0dc9183SWarner Losh
1868633bbeaSBrooks Davis20040409:
1878633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1888633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1898633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1908633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
19176c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1928633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1938633bbeaSBrooks Davis
194d40d033aSRobert Watson20040322:
195d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
196d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
197d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
198d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
199d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
200d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
201d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
202d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
203d40d033aSRobert Watson	locking is merged to permit this to take place.
204d40d033aSRobert Watson
205ec9b318eSGarance A Drosehn20040310:
206ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
207ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
208ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
209ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
210ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
211ec9b318eSGarance A Drosehn
212fc28f1ffSMax Laier20040308:
213fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
214fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
2154c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
2164c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
217fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
218fc28f1ffSMax Laier	pf system consists of the following three devices:
219fc28f1ffSMax Laier	device		pf		# required
220fc28f1ffSMax Laier	device		pflog		# optional
221fc28f1ffSMax Laier	device		pfsync		# optional
222fc28f1ffSMax Laier
2233aff5d06SDag-Erling Smørgrav20040303:
2243aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
2253aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
2263aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
2273aff5d06SDag-Erling Smørgrav
2283aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
2293aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
2303aff5d06SDag-Erling Smørgrav
2313aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
2323aff5d06SDag-Erling Smørgrav	to use libpthread instead.
2333aff5d06SDag-Erling Smørgrav
234fd63c5b3SDag-Erling Smørgrav20040226:
2359d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
236fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
237fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
238fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
239fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
240fd63c5b3SDag-Erling Smørgrav
241714ae42aSBruce M Simpson20040225:
242e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
243e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
244e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
245e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
246e07a40f3SBrian Feldman	should remain unaffected.
247e07a40f3SBrian Feldman
248e07a40f3SBrian Feldman20040225:
249714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
250714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
251714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
252714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
253714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
254714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
255714ae42aSBruce M Simpson
256fbd2e692SAndre Oppermann20040224:
257fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
2585bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
259fbd2e692SAndre Oppermann
260158b90daSWarner Losh20040222:
261158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
262158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
263158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
264158b90daSWarner Losh	Drivers outside the tree will need to be updated.
265158b90daSWarner Losh
266b7b1e150SMike Makonnen20040207:
267b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
268b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
269b7b1e150SMike Makonnen
270aca89ee6SDaniel Eischen20040130:
271aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
272aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
273aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
274aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
275aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
276aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
277aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
278aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
279aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
280aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
281aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
282aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
283aca89ee6SDaniel Eischen	do not work with libpthread.
284aca89ee6SDaniel Eischen
28568b7b3a9SAlex Dupre20040125:
28668b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
28768b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
28868b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
28968b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
29068b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
29168b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
29268b7b3a9SAlex Dupre
293ff46e0deSWarner Losh20040125:
294ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
295ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
296ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
297ff46e0deSWarner Losh
298ce41f4bfSRobert Watson20031213:
299ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
300ce41f4bfSRobert Watson	if the login process is unable to successfully set the
301ce41f4bfSRobert Watson	process credentials to include all groups defined for the
302ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
303ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
304ce41f4bfSRobert Watson	defined, or they will be unable to log in.
305ce41f4bfSRobert Watson
306c124fa05SJohn Baldwin20031203:
307c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
308c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
309c124fa05SJohn Baldwin
3108ad1f5e4SHartmut Brandt20031112:
31130093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
31230093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
31397209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
31497209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
31597209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
31697209ca3SRobert Watson	not know about the new system calls that support the new statfs
3173f631d52SMarcel Moolenaar	structure.
3183f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
3193f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
3203f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
3213f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
3223f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
3233f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
3243f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
3253f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
3263f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
3273f631d52SMarcel Moolenaar	these changes are installed.
32830093b05SWarner Losh
32930093b05SWarner Losh	****************************DANGER*******************************
33030093b05SWarner Losh
33130093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
33230093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
33330093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
33430093b05SWarner Losh	kernel.
33564a18d6fSKirk McKusick
33664a18d6fSKirk McKusick20031112:
3378ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3388ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3398ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3408ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3418ad1f5e4SHartmut Brandt	sync before rebooting.
3428ad1f5e4SHartmut Brandt
343c53a5d8fSJohn Baldwin20031111:
344c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
345c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
346c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
347c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
348c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
349c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
350c53a5d8fSJohn Baldwin
3518bf455a5SJohn Baldwin20031103:
3528bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3538bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3542a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3558bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3568bf455a5SJohn Baldwin
3579bf40edeSBrooks Davis20031031:
3589bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
3599bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
3609bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
3619bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
3629bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
3639bf40edeSBrooks Davis	reflect this change.
3649bf40edeSBrooks Davis
36547a42c7aSPoul-Henning Kamp20030928:
36647a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
36747a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
3685bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
36947a42c7aSPoul-Henning Kamp
37007105342SMax Khon20030926:
37107105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
37207105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
37307105342SMax Khon
37417dcd026SSam Leffler20030925:
37517dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
37617dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
37717dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
37817dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
37917dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
38017dcd026SSam Leffler
381fedf1d01SBruce M Simpson20030923:
382fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
383fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
384fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
385fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
386fedf1d01SBruce M Simpson
387db38f9cbSJacques Vidrine20030915:
388db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
389db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
390db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
391db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
392db38f9cbSJacques Vidrine
393c09d2c2bSMike Makonnen20030829:
394c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
395c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
396c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
397c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
398c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
399c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
400c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
401c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
402c09d2c2bSMike Makonnen	may or may not exist on your system.
403c09d2c2bSMike Makonnen
40417c159dcSSøren Schmidt20030824:
40517c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
40617c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
407f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
408f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
40917c159dcSSøren Schmidt
410c1f61aa9SDavid E. O'Brien20030819:
411c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
412c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
413c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
414c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
41569f7bcf3SWarner Losh
41638c962e7SNate Lawson20030728:
41738c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
41838c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
41938c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
42038c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
42138c962e7SNate Lawson	so the quirk can be re-enabled.
42238c962e7SNate Lawson
42374111097SWarner Losh20030724:
42474111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
42574111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
42674111097SWarner Losh
427178cf4e9SWarner Losh20030722:
428178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
429178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
430178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
431178cf4e9SWarner Losh	FPU hardware.
432178cf4e9SWarner Losh
433178cf4e9SWarner Losh20030714:
434178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
435178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
436178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
437178cf4e9SWarner Losh	People should report those issues to current@.
438178cf4e9SWarner Losh
439157c629aSWarner Losh20030711:
440157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4418b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
44205538fa9SWarner Losh	/usr/obj.
443157c629aSWarner Losh
44474111097SWarner Losh20030610:
44574111097SWarner Losh	Remove deprecated locale names and transition period code
44674111097SWarner Losh	for them, finishing switching to the new scheme. Check your
44774111097SWarner Losh	LANG environment variable.
44874111097SWarner Losh
44974111097SWarner Losh20030609:
45074111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
45174111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
45274111097SWarner Losh	important to remember beforehand if your source tree is on
45374111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
45474111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
45574111097SWarner Losh	kernel.
45674111097SWarner Losh
45774111097SWarner Losh20030605:
4586cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
4596cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
4606cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
4616cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
4626cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
4636cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
4646cc6353fSMarcel Moolenaar
4656cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
4666cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
4676cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
4686cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
4696cc6353fSMarcel Moolenaar		:
4706cc6353fSMarcel Moolenaar
4716cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
4726cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
4736cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
4746cc6353fSMarcel Moolenaar
47552b47445SMark Murray20030505:
47652b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
47752b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
47852b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
47952b47445SMark Murray
480a26df538SWarner Losh20030502:
481a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
482a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
483a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
484a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
485a26df538SWarner Losh
4864b065e2cSDoug Barton20030501:
4874b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4884b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4894b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4904b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4914b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4924b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4934b065e2cSDoug Barton
49481cda3d9SWarner Losh20030423:
49581cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
49681cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
49781cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
49881cda3d9SWarner Losh	have until then to upgrade your kernel before updating
49981cda3d9SWarner Losh	userland.  In general, you should have a userland and
50081cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
50181cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
50281cda3d9SWarner Losh	allowances are made.
50381cda3d9SWarner Losh
50447a657d1SRuslan Ermilov20030329:
50547a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
50647a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
50747a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
50847a657d1SRuslan Ermilov
50947a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
51047a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
51147a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
51247a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
51347a657d1SRuslan Ermilov
51447a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
51547a657d1SRuslan Ermilov	    make cleandir && make obj && \
51647a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
51747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
51847a657d1SRuslan Ermilov
5195d2af00cSGregory Neil Shapiro20030208:
5205d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
5215d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
5225d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
5235d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
5245d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
5255d2af00cSGregory Neil Shapiro
5265d2af00cSGregory Neil Shapiro20030128:
5279db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
528ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
5299db58771SPoul-Henning Kamp	be removed when convenient.
5309db58771SPoul-Henning Kamp
5318d9b3f57SJake Burkholder20030126:
5328d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
5338d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
5348d9b3f57SJake Burkholder
5351c5efda5SJeff Roberson20030125:
5361c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5371c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
538ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5391c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5401c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5411c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5421c5efda5SJeff Roberson
5439d1d64f5SWarner Losh20030115:
5449d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5459d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5469d1d64f5SWarner Losh	properly.
5479d1d64f5SWarner Losh
548c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
549c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
550c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
551c9fdb80aSWarner Losh	with NetBSD.
552c9fdb80aSWarner Losh
553161dc364SAlexander Kabaev20021222:
554161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
555161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
556161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
557161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
558161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
559161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
56084cc83efSAlexander Kabaev	rebuilt.
561161dc364SAlexander Kabaev
562fb4c8061SMartin Blapp20021216:
563fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
56489056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
565fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
5669d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
567fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
568fb4c8061SMartin Blapp
56917d47eb3SGiorgos Keramidas20021202:
57017d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
57117d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
57217d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
57317d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
57417d47eb3SGiorgos Keramidas
575a4459294SBill Fenner20021029:
576a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
577a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
578a4459294SBill Fenner	consumers in sync.
579a4459294SBill Fenner
580fc8c157fSWarner Losh20021024:
581c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
582c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
583c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
584c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
585c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
586c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
587c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
588c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
58969f7bcf3SWarner Losh
590fd9e8bdaSAndrew Gallatin20021023:
591fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
592fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
593fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
594fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
595fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
596fd9e8bdaSAndrew Gallatin
597fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
598fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
599fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
600fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
601fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
602fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
603fd9e8bdaSAndrew Gallatin
604f8a4c901SWarner Losh20020831:
605f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
606f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
607f8a4c901SWarner Losh	programs and libraries need to be recompiled.
608f8a4c901SWarner Losh
609f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
610f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
611f8a4c901SWarner Losh
612c2248fa2SJens Schweikhardt20020827:
613c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
614c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
615c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
616c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
617c2248fa2SJens Schweikhardt
6180d533e43SRuslan Ermilov20020815:
6190d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
6200d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
6210d533e43SRuslan Ermilov	again.
6220d533e43SRuslan Ermilov
62333c1de7dSRuslan Ermilov20020729:
62433c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
62533c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
62633c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
62733c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
62833c1de7dSRuslan Ermilov
6292b877facSJulian Elischer20020702:
6302b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
6312b877facSJulian Elischer	There are still some minor problems with some signals but the
6322b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
6332b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
6342b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6352b877facSJulian Elischer
63606596d37SWarner Losh20020701:
63706596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
63806596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
63906596d37SWarner Losh	GNOME.
64006596d37SWarner Losh
64195ba4330SJacques Vidrine20020511:
64295ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
64395ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
64495ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
64595ba4330SJacques Vidrine	with the set-user-ID bit set.
64695ba4330SJacques Vidrine
647a81da3c9SDavid E. O'Brien20020510:
648f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
649f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6504b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
651f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
652f50caf6fSDavid E. O'Brien
653f50caf6fSDavid E. O'Brien20020510:
654a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
655a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
656a81da3c9SDavid E. O'Brien	and then do a cvs update.
657a81da3c9SDavid E. O'Brien
658528a0ef5SJacques Vidrine20020421:
659528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
660528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
661528a0ef5SJacques Vidrine
66285aa5a2eSGregory Neil Shapiro20020404:
66385aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
66485aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
66585aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
66685aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
66785aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
66885aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
66985aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
67085aa5a2eSGregory Neil Shapiro
6718f1e4358SRuslan Ermilov20020403:
6728f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
6738f1e4358SRuslan Ermilov
6742292c02eSWarner Losh20020315:
6752292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
6762292c02eSWarner Losh
67769f7bcf3SWarner Losh20020225:
67869f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
67969f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
68069f7bcf3SWarner Losh
6818f35c493SWarner Losh20020217:
6828f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6838f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6848f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6858f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6868f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6878f35c493SWarner Losh
688835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
689835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
690835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
691835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
692835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
693835284beSWarner Losh	and group must be merged from src/etc/group and
694835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
695835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
696835284beSWarner Losh	mergemaster before this will work if you are updating from a
697835284beSWarner Losh	very old version of current.  The updating recipe has changed
698835284beSWarner Losh	as of this date.
699835284beSWarner Losh
700fa9401c1SWarner Losh20020112:
701fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
702fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
703fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
704fa9401c1SWarner Losh	you have local modifications, you can use
705fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
706fa9401c1SWarner Losh	/etc/pam.d.
707fa9401c1SWarner Losh
708fa9401c1SWarner Losh	Please see the following url for more details:
709fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
71047d0d01fSWarner Losh20011229:
71147d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
71247d0d01fSWarner Losh	networkfs_types, please note that it has changed
71347d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
71447d0d01fSWarner Losh
715514318a8SWarner Losh20011220:
716514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
717514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
718514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
719514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
720514318a8SWarner Losh	version have now been merged back into the base system's
721514318a8SWarner Losh	version now.  The only user-visible change resulting from this
722514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
723514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
724514318a8SWarner Losh	as well.  (There has never been rc file support for
725514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
726514318a8SWarner Losh	reverted by the time the changes are MFCed.)
727514318a8SWarner Losh
728514318a8SWarner Losh20011215:
729514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
730514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
731514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
732514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
733514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
734514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
735514318a8SWarner Losh	will need to be customized then for `odd' densities using
736514318a8SWarner Losh	fdcontrol(8).
737514318a8SWarner Losh
7382d22e2bfSWarner Losh20011209:
7392d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7402d22e2bfSWarner Losh	and truss(1) now works again.
7412d22e2bfSWarner Losh
7429e0428e2SWarner Losh20011207:
7439e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7449e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7459e0428e2SWarner Losh	see
7469e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7479e0428e2SWarner Losh	for details.
7489e0428e2SWarner Losh
7499bab8c59SWarner Losh20011204:
7509bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7519bab8c59SWarner Losh	kernel and burncd to be in sync.
7529bab8c59SWarner Losh
753e57d8b01SWarner Losh20011203:
754e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
755e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
756e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
757e57d8b01SWarner Losh	not there already.
758e57d8b01SWarner Losh
759e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
760e57d8b01SWarner Losh	until the issue has been resolved.
761e57d8b01SWarner Losh
762b001d36fSJacques Vidrine20011202:
763b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
764b001d36fSJacques Vidrine	patched.
765b001d36fSJacques Vidrine
7664b676ec1SWarner Losh20011126:
7674b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
7685ebbf43eSWarner Losh	after this date.  You need to do this only once.
7694b676ec1SWarner Losh
770d961e462SWarner Losh20011103:
771d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
772d961e462SWarner Losh	edges may be left, but for the most part things should be
7734b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
774d961e462SWarner Losh
775d961e462SWarner Losh20011030:
776d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
777d961e462SWarner Losh	choppy waves in the upgrade process.
778d961e462SWarner Losh
7791fe003b6SWarner Losh20011030:
780a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7811fe003b6SWarner Losh
7821fe003b6SWarner Losh20011027:
7831fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7841fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7851fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7861fe003b6SWarner Losh	try to use from this date forward.
7871fe003b6SWarner Losh
7881fe003b6SWarner Losh20011025:
7891fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7901fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7911fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7921fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7931fe003b6SWarner Losh	TARGET_ARCH=i386.
7941fe003b6SWarner Losh
795d05f9643SWarner Losh20011001:
796d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
797d05f9643SWarner Losh	You must recompile both the kernel and userland applications
798d05f9643SWarner Losh	at the same time.
799d05f9643SWarner Losh
80058970f85SWarner Losh20010929:
80158970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
80258970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
80358970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
80458970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
8059d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
80658970f85SWarner Losh
80758970f85SWarner Losh20010927:
80858970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
80958970f85SWarner Losh	To disable ACPI you can add
81066ff0e67SMax Khon		hint.acpi.0.disabled="1"
81158970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
81258970f85SWarner Losh	loader "ok" prompt).
81358970f85SWarner Losh
81458970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
81558970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
81658970f85SWarner Losh	file and not list acpi in that list.
817378f4486SAlfred Perlstein
8185119d237SWarner Losh20010924:
8195119d237SWarner Losh	The buildworld has been fixed.  You may need to install
8205119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8218b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
8228b039fffSWarner Losh	get them installed on every installworld, or execute the
8238b039fffSWarner Losh	following to get them installed only once:
8248b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
82558970f85SWarner Losh		make all install
8268b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
8275119d237SWarner Losh
8283c293725SWarner Losh20010919:
8293c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
8303c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
8313c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
832772730c7SWarner Losh	workaround is to add
8333c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
8343c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8353c293725SWarner Losh	can be removed afterwards.
8363c293725SWarner Losh
8373c293725SWarner Losh	A proper fix to the buildworld target is needed.
8383c293725SWarner Losh
8393c293725SWarner Losh20010918:
8403c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8413c293725SWarner Losh	NFS may be unstable after this date.
8423c293725SWarner Losh
8433c293725SWarner Losh20010912:
8443c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8453c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8463c293725SWarner Losh	initial commit, most of the major ones have been found and
8473c293725SWarner Losh	corrected.
8483c293725SWarner Losh
8493c293725SWarner Losh20010901:
8503c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8513c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8523c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8533c293725SWarner Losh	have been rectified around this date.
8543c293725SWarner Losh
85598b17b95SWarner Losh20010823:
85698b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
85798b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
85898b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
85998b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
86098b17b95SWarner Losh 	sure that user or group bind has read (and not write)
86198b17b95SWarner Losh 	permission for your name server configuration and that it
86298b17b95SWarner Losh 	has read and write permission for your slave zone files and
86398b17b95SWarner Losh 	directory.
86498b17b95SWarner Losh
86598b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
86698b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
86798b17b95SWarner Losh
86898b17b95SWarner Losh 		named_flags=
86998b17b95SWarner Losh
8707b9786edSMark Murray20010709:
8717b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
8727b9786edSMark Murray	the ability of the shared library major number to handle.
8737b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
8747b9786edSMark Murray	solution is to rebuild those ports.
8757b9786edSMark Murray
8761d28950eSWarner Losh20010628:
8771d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
8781d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8791d28950eSWarner Losh
880e72fd46aSWarner Losh20010625:
88198b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
88298b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
88398b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
88498b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
88598b17b95SWarner Losh	IRQ configuration needs more safety belts.
88616de1a07SWarner Losh
8870d415dffSWarner Losh20010617:
888e72fd46aSWarner Losh	Softupdates problems have been corrected.
8890d415dffSWarner Losh
8900d415dffSWarner Losh20010614:
8910d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8920d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8930d415dffSWarner Losh	kernel building methods.
8940d415dffSWarner Losh
8958b9959adSWarner Losh20010613:
8968b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
8978b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
898e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
899e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
9008b9959adSWarner Losh
901e72fd46aSWarner Losh20010613:
9028b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
903e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
904e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
9058b9959adSWarner Losh
9060d415dffSWarner Losh20010612:
9070d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
9080d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
9090d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
9100d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
9110d415dffSWarner Losh	until this bug is fixed.
9120d415dffSWarner Losh
913e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
914e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
915ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
916e72fd46aSWarner Losh
9170d415dffSWarner Losh20010610:
9180d415dffSWarner Losh	Locale names have changed to match other systems better.
9190d415dffSWarner Losh
9206ccdb5e4SWarner Losh20010604:
9216ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
9226ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
9236ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
9243590182eSWarner Losh	Interrupt storms look a lot like a hang.
9253590182eSWarner Losh
9263590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
9273590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
9283590182eSWarner Losh	it is).
9293590182eSWarner Losh
9303590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
9313590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
9323590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
9333590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
9346ccdb5e4SWarner Losh
9350bc62786SWarner Losh20010530:
9360bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9370bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9380bc62786SWarner Losh	a limited time.  If you see
9390bc62786SWarner Losh
9400bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9410bc62786SWarner Losh
9420bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9430bc62786SWarner Losh	COPY=-C.
9440bc62786SWarner Losh
94568a38c6cSWarner Losh20010525:
946b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
947c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
948c4f4a728SWarner Losh	definitely is in bad shape.
94968a38c6cSWarner Losh
950ed0f29caSWarner Losh20010521:
951ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
952ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
953ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
954ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
955ed0f29caSWarner Losh	is
956ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
957ed0f29caSWarner Losh
95880c16af9SWarner Losh20010520:
95968a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
96080c16af9SWarner Losh
96180c16af9SWarner Losh20010519:
96280c16af9SWarner Losh	pccard has had much reorganizational work done to it over
96380c16af9SWarner Losh	the past few days.  Everything should still work, but if
96480c16af9SWarner Losh	not, please contact imp@freebsd.org.
96580c16af9SWarner Losh
966a45f2d05SWarner Losh20010517:
967a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
968a45f2d05SWarner Losh	userland at the same time.
969a45f2d05SWarner Losh
970a45f2d05SWarner Losh20010517:
971a45f2d05SWarner Losh	New ncurses imported.
972a45f2d05SWarner Losh
9732988afcaSWarner Losh20010512:
9742988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
9752988afcaSWarner Losh	will be the only way to go starting July 1.
9762988afcaSWarner Losh
9771a33dba7SWarner Losh20010504:
9781a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9791a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9801a33dba7SWarner Losh
98109946a51SWarner Losh20010502:
98209946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
98309946a51SWarner Losh
98409946a51SWarner Losh20010501:
98509946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
98609946a51SWarner Losh
98709946a51SWarner Losh20010430:
988a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
98909946a51SWarner Losh	go back in the water.
99009946a51SWarner Losh
99109946a51SWarner Losh20010429:
99209946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
99309946a51SWarner Losh	this date, but before the correction date.
99409946a51SWarner Losh
99591dd3b53SWarner Losh20010423:
99691dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
99791dd3b53SWarner Losh
99891dd3b53SWarner Losh20010411:
99991dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
100091dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
100191dd3b53SWarner Losh	Update only if you understand that you must not use the old
100291dd3b53SWarner Losh	fsck with the new kernel ever.
100391dd3b53SWarner Losh
1004933b3269SWarner Losh20010330:
1005933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1006c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1007933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1008933b3269SWarner Losh
1009933b3269SWarner Losh20010319:
1010933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1011933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1012933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1013f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
101409946a51SWarner Losh
101509946a51SWarner Losh20010315:
101609946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1017ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
101809946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1019933b3269SWarner Losh
1020933b3269SWarner Losh20010312:
1021933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1022933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1023933b3269SWarner Losh
1024933b3269SWarner Losh20010312:
1025933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1026933b3269SWarner Losh	instead of ad-hoc.
1027933b3269SWarner Losh
1028933b3269SWarner Losh20010310:
1029f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1030933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1031933b3269SWarner Losh	ssh might not work if you don't.
1032933b3269SWarner Losh
103362353691SWarner Losh20010303:
103462353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
103562353691SWarner Losh	which means that you must include the miibus in your kernel if
103662353691SWarner Losh	you use the ed driver.
103762353691SWarner Losh
1038d325cf65SWarner Losh20010220:
1039d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1040d325cf65SWarner Losh	safe to go back into the water.
1041d325cf65SWarner Losh
1042024daae6SWarner Losh20010211:
1043024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1044024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1045024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1046024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1047024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1048024daae6SWarner Losh
1049024daae6SWarner Losh	To get to the new system, you'll need to use the following
1050024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1051024daae6SWarner Losh	don't have to move this to the updating section.
1052024daae6SWarner Losh
1053024daae6SWarner Losh	To get around the installworld problem, do:
1054024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1055024daae6SWarner Losh		# make install
1056024daae6SWarner Losh		# cd /usr/src
1057024daae6SWarner Losh		# make installworld
1058024daae6SWarner Losh	If that doesn't work, then try:
1059024daae6SWarner Losh		# make -k installworld
1060024daae6SWarner Losh		# make installworld
1061024daae6SWarner Losh
1062024daae6SWarner Losh20010207:
1063024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1064024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1065024daae6SWarner Losh
1066024daae6SWarner Losh20010205:
10677595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1068024daae6SWarner Losh	Remove them from your config.
1069024daae6SWarner Losh
10701e159248SWarner Losh20010122:
10711e159248SWarner Losh	****************************** WARNING ******************************
10721e159248SWarner Losh			buildkernel has been changed slightly
10731e159248SWarner Losh	****************************** WARNING ******************************
10741e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
10751e159248SWarner Losh	should update your scripts and make.conf accordingly.
10761e159248SWarner Losh
10771e159248SWarner Losh20010119:
10781e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10791e159248SWarner Losh	This requires a new config to build correctly.
10801e159248SWarner Losh
1081aac7dfeaSWarner Losh20010116:
1082ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1083aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1084aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1085aac7dfeaSWarner Losh
1086aac7dfeaSWarner Losh20010110:
1087aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1088aac7dfeaSWarner Losh
1089aac7dfeaSWarner Losh20010102:
1090aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1091aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1092aac7dfeaSWarner Losh
109363c90c9eSWarner Losh20010101:
109463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
109563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
10965fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
109763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
109863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
109963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
110063c90c9eSWarner Losh	might have been ignored by the -k option.
110163c90c9eSWarner Losh
11025fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
11035fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
11045fd2a895SWarner Losh	of this working.
11055fd2a895SWarner Losh
1106aac7dfeaSWarner Losh20001228:
1107aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1108ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1109aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1110aac7dfeaSWarner Losh
1111de2bcc63SWarner Losh20001218:
1112de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1113de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1114de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1115de2bcc63SWarner Losh	cards will not be recognized without it.
1116de2bcc63SWarner Losh
1117960773f7SWarner Losh20001205:
1118960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1119960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1120960773f7SWarner Losh	adding the following in pam.conf:
1121960773f7SWarner Losh
1122960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1123960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1124960773f7SWarner Losh	sshd    session required        pam_permit.so
1125960773f7SWarner Losh
11260acc635eSWarner Losh20001031:
11270acc635eSWarner Losh	cvs updated to 1.11.
11280acc635eSWarner Losh
11290acc635eSWarner Losh20001020:
11300acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
11310acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
11320acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
11330acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
11340acc635eSWarner Losh	workaround.
11350acc635eSWarner Losh
11360acc635eSWarner Losh20001010:
11370acc635eSWarner Losh	****************************** WARNING ******************************
11380acc635eSWarner Losh				Sendmail has been updated.
11390acc635eSWarner Losh	****************************** WARNING ******************************
11400acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11410acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11420acc635eSWarner Losh	  is set.
11430acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11440acc635eSWarner Losh	  commands.
11450acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11460acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11470acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11480acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11490acc635eSWarner Losh
11500acc635eSWarner Losh	More details can be found at
11510acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11520acc635eSWarner Losh
11536e98a146SWarner Losh20001009:
11546e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11556e98a146SWarner Losh	your entire ports tree, or you will have problems.
11566e98a146SWarner Losh
11576e98a146SWarner Losh20001006:
1158685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
11596e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
11606e98a146SWarner Losh	/usr/bin/miniperl.
11616e98a146SWarner Losh
1162073113a4SWarner Losh20001005:
1163073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1164685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1165073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1166073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1167073113a4SWarner Losh	tree for anything to work.
1168073113a4SWarner Losh
11690acc635eSWarner Losh20000928:
11700acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
11710acc635eSWarner Losh
1172be3885b3SWarner Losh20000916:
1173be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1174be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1175be3885b3SWarner Losh	same time as your kernel.
1176be3885b3SWarner Losh
117776ec9675SWarner Losh20000914:
117876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
117976ec9675SWarner Losh	include the device will cause suspended laptops losing time
118076ec9675SWarner Losh	when they resume.  Include
118176ec9675SWarner Losh		device		pmtimer
118276ec9675SWarner Losh	in your config file and
118301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
118476ec9675SWarner Losh	to your /boot/device.hints file.
118576ec9675SWarner Losh
1186f4865386SMark Murray20000911:
1187f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1188f4865386SMark Murray	rather than an option. The supplied kernel config files have
1189f4865386SMark Murray	been updated. You will need to do something similar in your
1190f4865386SMark Murray	own kernel config file.
1191f4865386SMark Murray	Remove:
1192f4865386SMark Murray		options		RANDOMDEV
1193f4865386SMark Murray	Add:
1194f4865386SMark Murray		device		random
1195f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1196f4865386SMark Murray	nothing.
1197f4865386SMark Murray
1198d594498fSWarner Losh20000909:
1199d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1200d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1201d594498fSWarner Losh	reflect this if you load this module at boot time.
1202d594498fSWarner Losh	The line should read:
1203d594498fSWarner Losh		random_load="YES"
1204d594498fSWarner Losh
12050deb7ddcSWarner Losh20000907:
12060deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
120716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
120816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
120916eb772dSWarner Losh	sure you don't have model loading problems which might at
121016eb772dSWarner Losh	first blush appear related to SMP.
121152bf24e7SWarner Losh
12125a01880bSWarner Losh20000906:
12135a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
12145a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
12155a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
12165a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
12175a01880bSWarner Losh	don't have one, and you have host.conf.
12185a01880bSWarner Losh
12192b41163cSWarner Losh20000905:
122038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
122138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
122238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
122338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
122438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
122538d6ecd2SWarner Losh
122638d6ecd2SWarner Losh20000905:
12278aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
12288aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
12298aab4bc7SWarner Losh	is /boot/kernel.
12308aab4bc7SWarner Losh
12318aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
123238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
123338d6ecd2SWarner Losh	installkernel/installworld dance.
12342b41163cSWarner Losh
1235d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1236d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1237d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1238d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1239d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1240d594498fSWarner Losh
1241d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1242d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1243d594498fSWarner Losh		chflags noschg /kernel.old
1244d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1245d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1246d594498fSWarner Losh	fi
1247d594498fSWarner Losh
1248c22a309cSWarner Losh20000904:
1249c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1250c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1251c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1252c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1253c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1254c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1255c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1256c22a309cSWarner Losh	is not likely to be generated.
1257c22a309cSWarner Losh
1258fdb9f54dSWarner Losh20000825:
1259fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
12609c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
12619c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
12629c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
12639c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
12649c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
12659c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
12669c1a7444SWarner Losh	kernel.
12679c1a7444SWarner Losh
12689c1a7444SWarner Losh20000821:
12699c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
12709c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
12719c1a7444SWarner Losh	/boot/loader.conf.
1272fdb9f54dSWarner Losh
12738f250aa7SWarner Losh20000812:
12745da0d091SWarner Losh	suidperl is now always built and installed on the system, but
12755da0d091SWarner Losh	with permissions of 511.  If you have applications that use
12765da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
12775da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
12785da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12795da0d091SWarner Losh	will fix this until the next build.
12805da0d091SWarner Losh
12815da0d091SWarner Losh20000812:
12828f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12838f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12848f250aa7SWarner Losh	include:
12858f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12868f250aa7SWarner Losh	- newaliases limited to root and trusted users
12878f250aa7SWarner Losh	- MSA port (587) turned on by default
12888f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12898f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12908f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12918f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12928f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12938f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12948f250aa7SWarner Losh
129571c38472SWarner Losh20000810:
129671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
129771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
129871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
129971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
130071c38472SWarner Losh	specific use for it.
130171c38472SWarner Losh
130271c38472SWarner Losh20000729:
130371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
130471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
130571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
130671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
130771c38472SWarner Losh		# Enable network daemons for user convenience.
130871c38472SWarner Losh		inetd_enable="YES"
130971c38472SWarner Losh		portmap_enable="YES"
131071c38472SWarner Losh		sendmail_enable="YES"
131171c38472SWarner Losh
131271c38472SWarner Losh20000728:
131371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
131471c38472SWarner Losh	will need to change that to nullfs_load="YES".
131571c38472SWarner Losh
13161dece4a9SWarner Losh20000728:
13171dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
13181dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
13191dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
13201dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
13211dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
13221dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
13231dece4a9SWarner Losh	to /MYKERNEL.
13241dece4a9SWarner Losh
1325409e887cSWarner Losh20000711:
1326409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1327409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1328409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1329409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1330409e887cSWarner Losh	for details on potential problems that you might have and how
1331409e887cSWarner Losh	to get around them.
1332409e887cSWarner Losh
1333409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1334409e887cSWarner Losh	clauses above, you needn't worry.
1335409e887cSWarner Losh
1336409e887cSWarner Losh20000711:
1337409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1338409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1339409e887cSWarner Losh	in the number of changed programs the first time when you run
1340409e887cSWarner Losh	mergemaster to get a new /etc/security.
1341409e887cSWarner Losh
1342673d13f2SWarner Losh20000710:
1343673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1344673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1345673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1346673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1347673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1348673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1349673d13f2SWarner Losh	errors. (see below, 20000624).
1350673d13f2SWarner Losh
1351bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13521dece4a9SWarner Losh
1353673d13f2SWarner Losh20000709:
1354c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1355c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1356c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1357673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1358673d13f2SWarner Losh
1359e98e26cdSWarner Losh20000706:
1360e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1361e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1362e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1363f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1364e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
13652c021c6cSMark Ovens	interim if needed.
1366e98e26cdSWarner Losh
1367e98e26cdSWarner Losh20000705:
1368e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1369e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1370e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1371e98e26cdSWarner Losh	details.
1372e98e26cdSWarner Losh
1373c373950eSWarner Losh20000704:
13742f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
13752f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
13762f961bc8SWarner Losh
13772f961bc8SWarner Losh20000704:
1378c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1379c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1380c373950eSWarner Losh	rc.d scripts that haven't been updated.
1381c373950eSWarner Losh
138227dc3a2bSWarner Losh20000630:
138327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
138427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
138527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
138627dc3a2bSWarner Losh
1387b8c215acSWarner Losh20000625:
1388b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
138927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
139027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
139127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
139227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
139327dc3a2bSWarner Losh	were required.  You should check with the latest collections
139427dc3a2bSWarner Losh	to make sure that these haven't changed.
1395b8c215acSWarner Losh
13967b990719SWarner Losh20000624:
13977b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
13987b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
13997b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
14001a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
14017b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
14027b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
14037b990719SWarner Losh	date to the completion of the work.
14047b990719SWarner Losh
140527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
140627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
140727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
140827dc3a2bSWarner Losh	recreate the random and urandom devices.
140927dc3a2bSWarner Losh
141081e54c50SWarner Losh20000622:
141181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
141281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
141381e54c50SWarner Losh	that used to be required when updating.
141481e54c50SWarner Losh
141539943833SWarner Losh20000621:
14162c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
14172a2f33fbSDaniel Baker	the config file update procedure.
14182a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1419c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
142059df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
142159df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
142239943833SWarner Losh
1423290f9ad8SWarner Losh20000620:
1424290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1425290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1426290f9ad8SWarner Losh	that workaround will no longer be required.
1427290f9ad8SWarner Losh
142890fb6346SWarner Losh20000615:
142990fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
143090fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
143190fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
143290fb6346SWarner Losh	devices.
143390fb6346SWarner Losh
1434f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1435f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1436f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1437f75f65bbSWarner Losh	may work).
1438f75f65bbSWarner Losh
1439ba26da8eSWarner Losh20000612:
1440ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1441290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1442c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1443290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1444f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1445f54a3542SWarner Losh	NEWCARD for examples of the new format.
1446290f9ad8SWarner Losh
14479698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14489698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14499698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14509698f2c0SWarner Losh	in it.
1451bbcc5149SWarner Losh
1452d65850ebSWarner Losh20000522:
1453ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1454d65850ebSWarner Losh	building a kernel after this point is advised that they need
1455d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1456d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1457d65850ebSWarner Losh
1458d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1459d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1460d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1461d9583a00SWarner Losh	is resolved.
1462d9583a00SWarner Losh
14638039cedeSWarner Losh20000513:
14648039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
14658039cedeSWarner Losh
1466d65850ebSWarner Losh20000510:
14678039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
14688039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
14698039cedeSWarner Losh	is requires for the boot blocks to build properly.
14708039cedeSWarner Losh
14718039cedeSWarner Losh20000503:
14728039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
14738039cedeSWarner Losh	is now available.
14748039cedeSWarner Losh
1475d65850ebSWarner Losh20000502:
1476d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1477d65850ebSWarner Losh	connected to the kernel building instead.
1478d65850ebSWarner Losh
1479be149406SNik Clayton20000427:
14808039cedeSWarner Losh	You may need to build gperf
14818039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14828039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14838039cedeSWarner Losh	an option only in -current.
14848039cedeSWarner Losh
14852b8dd5f4SWarner Losh20000417:
14862b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1487f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14882b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14892b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14902c021c6cSMark Ovens	before you reboot, you'll need to issue:
14912b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14922b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14932b8dd5f4SWarner Losh
14948d9f1945SWarner Losh20000320:
14952b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
14962b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
14972b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1498ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
14992b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
15008d9f1945SWarner Losh
1501f8ab1dd6SWarner Losh20000319:
1502f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1503f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1504f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1505f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1506f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1507f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1508f8ab1dd6SWarner Losh
150919cada77SWarner Losh20000318:
1510f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
151119cada77SWarner Losh	Large kernel changes are being committed and are in the
151219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
151319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
151419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
151519cada77SWarner Losh	that you are loading are up to date.
1516ba228352SWarner Losh
151719cada77SWarner Losh20000315:
15186d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
15196d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
15206d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
15216d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
15226d23c382SWarner Losh	boot.
15236d23c382SWarner Losh
15246d23c382SWarner Losh20000315:
152519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
152619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
152757199806SWarner Losh
1528dc0dbf5cSWarner LoshCOMMON ITEMS:
1529dc0dbf5cSWarner Losh
1530a24eff53SWarner Losh	General Notes
1531a24eff53SWarner Losh	-------------
1532a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1533a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1534a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1535a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1536a24eff53SWarner Losh	or several minor releases, or when several months have passed
1537a24eff53SWarner Losh	on the -current branch).
1538a24eff53SWarner Losh
15395780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15405780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15415780f3baSWarner Losh	environment when searching for values for global variables.
15425780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15435780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15445780f3baSWarner Losh	page for more details.
15455780f3baSWarner Losh
1546dc0dbf5cSWarner Losh	To build a kernel
1547dc0dbf5cSWarner Losh	-----------------
1548ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1549f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1550ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1551282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1552282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1553dc0dbf5cSWarner Losh
1554ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1555ba01eb20SWarner Losh	--------------------------------------------------------------
15560fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15570fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
15580fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
15590fbd2da9SKen Smith
15600fbd2da9SKen Smith	cd src/sys/${arch}/conf
156147d0d01fSWarner Losh	config KERNEL_NAME_HERE
15620fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1563ba01eb20SWarner Losh	make depend
1564ba01eb20SWarner Losh	make
1565ba01eb20SWarner Losh	make install
1566ba01eb20SWarner Losh
1567ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1568ba01eb20SWarner Losh
1569ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1570ba01eb20SWarner Losh	-----------------------------------------------------------
157163cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
157263cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
157363cb445eSWarner Losh
1574f643de42SWarner Losh	<make sure you have good level 0 dumps>
157563cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
157663cb445eSWarner Losh	make buildworld
157763cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
157863cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
157963cb445eSWarner Losh							[1]
158063cb445eSWarner Losh	<reboot in single user>				[3]
15818633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
158263cb445eSWarner Losh	mergemaster -p					[5]
158363cb445eSWarner Losh	make installworld
158463cb445eSWarner Losh	mergemaster					[4]
158563cb445eSWarner Losh	<reboot>
158663cb445eSWarner Losh
1587759f0aefSWarner Losh
1588f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1589f27b1fceSJoseph Koshy	--------------------------------------------------
1590f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1591f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1592f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1593f27b1fceSJoseph Koshy	# size.
1594f27b1fceSJoseph Koshy
1595f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1596f27b1fceSJoseph Koshy	<boot into -stable>
1597f27b1fceSJoseph Koshy	make buildworld
1598f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1599f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1600f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1601f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1602f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1603f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1604f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1605f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1606f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1607f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1608f27b1fceSJoseph Koshy	<reboot into current>
1609f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1610f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1611f27b1fceSJoseph Koshy 	<reboot>
1612f27b1fceSJoseph Koshy
1613f27b1fceSJoseph Koshy
1614f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1615f27b1fceSJoseph Koshy	----------------------------------------------
16165c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
16175c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
16185c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
16195c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1620ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1621f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1622f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1623f643de42SWarner Losh	# space on /.
1624f643de42SWarner Losh
1625f643de42SWarner Losh	<make sure you have good level 0 dumps>
1626fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
162721c075eaSWarner Losh	make buildworld					[9]
1628c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1629802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1630be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1631802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1632fc8c157fSWarner Losh							[1]
1633fc8c157fSWarner Losh	<reboot in single user>				[3]
1634802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1635835284beSWarner Losh	mergemaster -p					[5]
1636f8a4c901SWarner Losh	rm -rf /usr/include/g++
1637ba26da8eSWarner Losh	make installworld
1638802fc49dSBrian Feldman	mergemaster -i					[4]
1639ba26da8eSWarner Losh	<reboot>
1640ba26da8eSWarner Losh
1641fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1642fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1643fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1644fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1645fdb9f54dSWarner Losh	the UPDATING entries.
1646ba26da8eSWarner Losh
16471dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16481dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16491dece4a9SWarner Losh	your sources that you have read and understood all the recent
16501dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16511dece4a9SWarner Losh	much fewer pitfalls.
16521dece4a9SWarner Losh
1653134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1654134d2e86SWarner Losh	should disable them at this point so they don't crash your
1655134d2e86SWarner Losh	system on reboot.
1656134d2e86SWarner Losh
16579c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
16589c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
16599c1a7444SWarner Losh	configuration.
16609c1a7444SWarner Losh
1661ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1662ee6e1fc3SWarner Losh		fsck -p
1663ee6e1fc3SWarner Losh		mount -u /
1664ee6e1fc3SWarner Losh		mount -a
1665ee6e1fc3SWarner Losh		cd /usr/src
166647d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1667f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1668f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1669b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1670b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1671b705ae10SWarner Losh	be ignored while you proceed to the next step.
1672ee6e1fc3SWarner Losh
1673a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1674a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1675a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1676a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1677a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1678a6cd4f9dSWarner Losh	for potential gotchas.
1679a6cd4f9dSWarner Losh
1680835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1681835284beSWarner Losh	you may need to do this if you get unknown user in the following
1682835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1683835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1684835284beSWarner Losh	install) after the buildworld before this step if you last updated
1685835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1686835284beSWarner Losh
1687bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1688bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1689bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1690bd79cf40SWarner Losh		ok unload
1691bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1692bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1693bd79cf40SWarner Losh	described here.
1694fc8c157fSWarner Losh
1695fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1696fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1697fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1698fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1699fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1700fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1701fc8c157fSWarner Losh
1702c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1703c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1704c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1705c74fe6afSWarner Losh	that is hard to boot to recover.
1706c74fe6afSWarner Losh
170721c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1708802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1709802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1710802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1711802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1712802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1713802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1714802fc49dSBrian Feldman	using your existing software for a while.
17158633bbeaSBrooks Davis
17168633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
17178633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
17188633bbeaSBrooks Davis	takes care of this.
1719dc0dbf5cSWarner LoshFORMAT:
1720dc0dbf5cSWarner Losh
1721f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
17221fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1723f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1724f8ab1dd6SWarner Loshprevious releases if your system is older than this.
17251fc1a0dcSWarner Losh
1726e72fd46aSWarner LoshCopyright information:
1727e72fd46aSWarner Losh
17289698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1729e72fd46aSWarner Losh
1730772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1731772730c7SWarner Loshmodification, in full or in part, in any form or format of this
17329698f2c0SWarner Loshdocument are permitted without further permission from the author.
1733e72fd46aSWarner Losh
1734e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1735e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1736e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1737e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1738e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1739e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1740e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1741e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1742e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1743e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1744e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1745e72fd46aSWarner Losh
1746e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1747e72fd46aSWarner Loshauthor a beer.
1748e72fd46aSWarner Losh
174922306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1750772730c7SWarner Loshthis document.
1751772730c7SWarner Losh
175297d92980SPeter Wemm$FreeBSD$
1753