xref: /freebsd/UPDATING (revision 6e1afae3e8fdc5bb9624f7ec8b7772922210190b)
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
446e1afae3SWarner Losh	With the upgrade of the system compiler, the kernel has been upgraded
456e1afae3SWarner Losh	to match the new system compiler.  This makes it impossible to build
466e1afae3SWarner Losh	a new kernel with the old compiler.  Upgrade your system via
476e1afae3SWarner Losh	make buildworld and make kernel (see below) to fix this problem.
486e1afae3SWarner Losh
4936ed21e6SRobert Watson20040727:
5036ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
5136ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
5236ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
5336ed21e6SRobert Watson	a result.
5436ed21e6SRobert Watson
556305ac24SSeigo Tanimura20040716:
566305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
576305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
586305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
596305ac24SSeigo Tanimura
60e623dcb7SMarcel Moolenaar20040710:
61e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
62e623dcb7SMarcel Moolenaar
63e623dcb7SMarcel Moolenaar20040710:
64e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
65e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
66e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
67e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
68e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
69e623dcb7SMarcel Moolenaar	of this.
70e623dcb7SMarcel Moolenaar
71e623dcb7SMarcel Moolenaar20040710:
72e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
73e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
74e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
75e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
76e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
77e623dcb7SMarcel Moolenaar	   option for this.
78e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
79e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
80e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
81e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
825bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
83e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
84e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
85e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
86e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
87e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
88e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
89e623dcb7SMarcel Moolenaar
906421d1dbSMaksim Yevmenkin20040708:
916421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
926421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
936421d1dbSMaksim Yevmenkin
9458af3216SWarner Losh20040702:
9558af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
965bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
975bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
985bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
9958af3216SWarner Losh	scheduler as a workaround.
10058af3216SWarner Losh
101c2dba668SNate Lawson20040630:
1028ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
1038ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
104a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
105a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
106a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
107a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
108a6c26e1cSBruce M Simpson	example of such changes.
1098ed370fdSJulian Elischer
11058af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
11158af3216SWarner Losh	over.
11258af3216SWarner Losh
1138ed370fdSJulian Elischer20040630:
114c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
1155bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
116c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
117c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
118c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
119c2dba668SNate Lawson	loader prompt.
120c2dba668SNate Lawson
1218ee2ac9eSMax Laier20040623:
1225bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
1238ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
1248ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
1258ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
1268ee2ac9eSMax Laier
1273db5687dSBrooks Davis20040622:
1283db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
1293db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
1303db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
1313db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
1323db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
1333db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
1343db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
1353db5687dSBrooks Davis
136e0ae81f3SDag-Erling Smørgrav20040621:
137e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
138e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
139e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
140e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
141e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
142e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
143e0ae81f3SDag-Erling Smørgrav	during the next reboot.
144e0ae81f3SDag-Erling Smørgrav
1454717d22aSJohn Polstra20040614:
1464717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1474717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1484717d22aSJohn Polstra	the ips module and any third-party modules which call
1494717d22aSJohn Polstra	sema_timedwait.
1504717d22aSJohn Polstra
1516cb7a382SMax Laier20040613:
1526cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1536cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
154df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
155df843493SMax Laier	please recompile and reinstall world.
1566cb7a382SMax Laier
1572454685eSJulian Elischer20040607:
1582454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1592454685eSJulian Elischer	requires that you re-run config after updating your tree.
1602454685eSJulian Elischer
16164fef830SSeigo Tanimura20040601:
16264fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
16364fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
16464fef830SSeigo Tanimura	kernel configuration.
16564fef830SSeigo Tanimura
166bb4f06e7SAndre Oppermann20040423:
167bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
168bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
169bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
170bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
171bb4f06e7SAndre Oppermann
17205641e82SColin Percival20040420:
17305641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
17405641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
17505641e82SColin Percival	20040406.
17605641e82SColin Percival
177d0dc9183SWarner Losh20040414:
178d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
179d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
180d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
181d0dc9183SWarner Losh
182d0dc9183SWarner Losh20040412:
183d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
184d0dc9183SWarner Losh	drive is still broken.
185d0dc9183SWarner Losh
186d0dc9183SWarner Losh20040410:
187d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
188d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
189d0dc9183SWarner Losh	the unanticipated problems have been resolved.
190d0dc9183SWarner Losh
1918633bbeaSBrooks Davis20040409:
1928633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1938633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1948633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1958633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
19676c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1978633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1988633bbeaSBrooks Davis
199d40d033aSRobert Watson20040322:
200d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
201d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
202d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
203d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
204d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
205d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
206d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
207d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
208d40d033aSRobert Watson	locking is merged to permit this to take place.
209d40d033aSRobert Watson
210ec9b318eSGarance A Drosehn20040310:
211ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
212ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
213ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
214ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
215ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
216ec9b318eSGarance A Drosehn
217fc28f1ffSMax Laier20040308:
218fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
219fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
2204c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
2214c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
222fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
223fc28f1ffSMax Laier	pf system consists of the following three devices:
224fc28f1ffSMax Laier	device		pf		# required
225fc28f1ffSMax Laier	device		pflog		# optional
226fc28f1ffSMax Laier	device		pfsync		# optional
227fc28f1ffSMax Laier
2283aff5d06SDag-Erling Smørgrav20040303:
2293aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
2303aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
2313aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
2323aff5d06SDag-Erling Smørgrav
2333aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
2343aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
2353aff5d06SDag-Erling Smørgrav
2363aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
2373aff5d06SDag-Erling Smørgrav	to use libpthread instead.
2383aff5d06SDag-Erling Smørgrav
239fd63c5b3SDag-Erling Smørgrav20040226:
2409d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
241fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
242fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
243fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
244fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
245fd63c5b3SDag-Erling Smørgrav
246714ae42aSBruce M Simpson20040225:
247e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
248e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
249e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
250e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
251e07a40f3SBrian Feldman	should remain unaffected.
252e07a40f3SBrian Feldman
253e07a40f3SBrian Feldman20040225:
254714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
255714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
256714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
257714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
258714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
259714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
260714ae42aSBruce M Simpson
261fbd2e692SAndre Oppermann20040224:
262fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
2635bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
264fbd2e692SAndre Oppermann
265158b90daSWarner Losh20040222:
266158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
267158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
268158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
269158b90daSWarner Losh	Drivers outside the tree will need to be updated.
270158b90daSWarner Losh
271b7b1e150SMike Makonnen20040207:
272b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
273b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
274b7b1e150SMike Makonnen
275aca89ee6SDaniel Eischen20040130:
276aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
277aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
278aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
279aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
280aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
281aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
282aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
283aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
284aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
285aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
286aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
287aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
288aca89ee6SDaniel Eischen	do not work with libpthread.
289aca89ee6SDaniel Eischen
29068b7b3a9SAlex Dupre20040125:
29168b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
29268b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
29368b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
29468b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
29568b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
29668b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
29768b7b3a9SAlex Dupre
298ff46e0deSWarner Losh20040125:
299ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
300ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
301ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
302ff46e0deSWarner Losh
303ce41f4bfSRobert Watson20031213:
304ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
305ce41f4bfSRobert Watson	if the login process is unable to successfully set the
306ce41f4bfSRobert Watson	process credentials to include all groups defined for the
307ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
308ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
309ce41f4bfSRobert Watson	defined, or they will be unable to log in.
310ce41f4bfSRobert Watson
311c124fa05SJohn Baldwin20031203:
312c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
313c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
314c124fa05SJohn Baldwin
3158ad1f5e4SHartmut Brandt20031112:
31630093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
31730093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
31897209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
31997209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
32097209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
32197209ca3SRobert Watson	not know about the new system calls that support the new statfs
3223f631d52SMarcel Moolenaar	structure.
3233f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
3243f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
3253f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
3263f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
3273f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
3283f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
3293f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
3303f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
3313f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
3323f631d52SMarcel Moolenaar	these changes are installed.
33330093b05SWarner Losh
33430093b05SWarner Losh	****************************DANGER*******************************
33530093b05SWarner Losh
33630093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
33730093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
33830093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
33930093b05SWarner Losh	kernel.
34064a18d6fSKirk McKusick
34164a18d6fSKirk McKusick20031112:
3428ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3438ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3448ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3458ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3468ad1f5e4SHartmut Brandt	sync before rebooting.
3478ad1f5e4SHartmut Brandt
348c53a5d8fSJohn Baldwin20031111:
349c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
350c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
351c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
352c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
353c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
354c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
355c53a5d8fSJohn Baldwin
3568bf455a5SJohn Baldwin20031103:
3578bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3588bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3592a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3608bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3618bf455a5SJohn Baldwin
3629bf40edeSBrooks Davis20031031:
3639bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
3649bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
3659bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
3669bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
3679bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
3689bf40edeSBrooks Davis	reflect this change.
3699bf40edeSBrooks Davis
37047a42c7aSPoul-Henning Kamp20030928:
37147a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
37247a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
3735bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
37447a42c7aSPoul-Henning Kamp
37507105342SMax Khon20030926:
37607105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
37707105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
37807105342SMax Khon
37917dcd026SSam Leffler20030925:
38017dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
38117dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
38217dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
38317dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
38417dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
38517dcd026SSam Leffler
386fedf1d01SBruce M Simpson20030923:
387fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
388fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
389fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
390fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
391fedf1d01SBruce M Simpson
392db38f9cbSJacques Vidrine20030915:
393db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
394db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
395db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
396db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
397db38f9cbSJacques Vidrine
398c09d2c2bSMike Makonnen20030829:
399c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
400c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
401c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
402c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
403c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
404c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
405c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
406c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
407c09d2c2bSMike Makonnen	may or may not exist on your system.
408c09d2c2bSMike Makonnen
40917c159dcSSøren Schmidt20030824:
41017c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
41117c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
412f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
413f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
41417c159dcSSøren Schmidt
415c1f61aa9SDavid E. O'Brien20030819:
416c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
417c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
418c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
419c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
42069f7bcf3SWarner Losh
42138c962e7SNate Lawson20030728:
42238c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
42338c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
42438c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
42538c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
42638c962e7SNate Lawson	so the quirk can be re-enabled.
42738c962e7SNate Lawson
42874111097SWarner Losh20030724:
42974111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
43074111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
43174111097SWarner Losh
432178cf4e9SWarner Losh20030722:
433178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
434178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
435178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
436178cf4e9SWarner Losh	FPU hardware.
437178cf4e9SWarner Losh
438178cf4e9SWarner Losh20030714:
439178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
440178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
441178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
442178cf4e9SWarner Losh	People should report those issues to current@.
443178cf4e9SWarner Losh
444157c629aSWarner Losh20030711:
445157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4468b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
44705538fa9SWarner Losh	/usr/obj.
448157c629aSWarner Losh
44974111097SWarner Losh20030610:
45074111097SWarner Losh	Remove deprecated locale names and transition period code
45174111097SWarner Losh	for them, finishing switching to the new scheme. Check your
45274111097SWarner Losh	LANG environment variable.
45374111097SWarner Losh
45474111097SWarner Losh20030609:
45574111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
45674111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
45774111097SWarner Losh	important to remember beforehand if your source tree is on
45874111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
45974111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
46074111097SWarner Losh	kernel.
46174111097SWarner Losh
46274111097SWarner Losh20030605:
4636cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
4646cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
4656cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
4666cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
4676cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
4686cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
4696cc6353fSMarcel Moolenaar
4706cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
4716cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
4726cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
4736cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
4746cc6353fSMarcel Moolenaar		:
4756cc6353fSMarcel Moolenaar
4766cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
4776cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
4786cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
4796cc6353fSMarcel Moolenaar
48052b47445SMark Murray20030505:
48152b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
48252b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
48352b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
48452b47445SMark Murray
485a26df538SWarner Losh20030502:
486a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
487a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
488a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
489a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
490a26df538SWarner Losh
4914b065e2cSDoug Barton20030501:
4924b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4934b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4944b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4954b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4964b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4974b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4984b065e2cSDoug Barton
49981cda3d9SWarner Losh20030423:
50081cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
50181cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
50281cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
50381cda3d9SWarner Losh	have until then to upgrade your kernel before updating
50481cda3d9SWarner Losh	userland.  In general, you should have a userland and
50581cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
50681cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
50781cda3d9SWarner Losh	allowances are made.
50881cda3d9SWarner Losh
50947a657d1SRuslan Ermilov20030329:
51047a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
51147a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
51247a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
51347a657d1SRuslan Ermilov
51447a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
51547a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
51647a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
51747a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
51847a657d1SRuslan Ermilov
51947a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
52047a657d1SRuslan Ermilov	    make cleandir && make obj && \
52147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
52247a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
52347a657d1SRuslan Ermilov
5245d2af00cSGregory Neil Shapiro20030208:
5255d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
5265d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
5275d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
5285d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
5295d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
5305d2af00cSGregory Neil Shapiro
5315d2af00cSGregory Neil Shapiro20030128:
5329db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
533ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
5349db58771SPoul-Henning Kamp	be removed when convenient.
5359db58771SPoul-Henning Kamp
5368d9b3f57SJake Burkholder20030126:
5378d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
5388d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
5398d9b3f57SJake Burkholder
5401c5efda5SJeff Roberson20030125:
5411c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5421c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
543ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5441c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5451c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5461c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5471c5efda5SJeff Roberson
5489d1d64f5SWarner Losh20030115:
5499d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5509d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5519d1d64f5SWarner Losh	properly.
5529d1d64f5SWarner Losh
553c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
554c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
555c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
556c9fdb80aSWarner Losh	with NetBSD.
557c9fdb80aSWarner Losh
558161dc364SAlexander Kabaev20021222:
559161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
560161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
561161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
562161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
563161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
564161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
56584cc83efSAlexander Kabaev	rebuilt.
566161dc364SAlexander Kabaev
567fb4c8061SMartin Blapp20021216:
568fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
56989056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
570fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
5719d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
572fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
573fb4c8061SMartin Blapp
57417d47eb3SGiorgos Keramidas20021202:
57517d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
57617d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
57717d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
57817d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
57917d47eb3SGiorgos Keramidas
580a4459294SBill Fenner20021029:
581a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
582a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
583a4459294SBill Fenner	consumers in sync.
584a4459294SBill Fenner
585fc8c157fSWarner Losh20021024:
586c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
587c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
588c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
589c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
590c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
591c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
592c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
593c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
59469f7bcf3SWarner Losh
595fd9e8bdaSAndrew Gallatin20021023:
596fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
597fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
598fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
599fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
600fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
601fd9e8bdaSAndrew Gallatin
602fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
603fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
604fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
605fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
606fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
607fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
608fd9e8bdaSAndrew Gallatin
609f8a4c901SWarner Losh20020831:
610f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
611f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
612f8a4c901SWarner Losh	programs and libraries need to be recompiled.
613f8a4c901SWarner Losh
614f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
615f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
616f8a4c901SWarner Losh
617c2248fa2SJens Schweikhardt20020827:
618c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
619c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
620c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
621c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
622c2248fa2SJens Schweikhardt
6230d533e43SRuslan Ermilov20020815:
6240d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
6250d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
6260d533e43SRuslan Ermilov	again.
6270d533e43SRuslan Ermilov
62833c1de7dSRuslan Ermilov20020729:
62933c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
63033c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
63133c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
63233c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
63333c1de7dSRuslan Ermilov
6342b877facSJulian Elischer20020702:
6352b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
6362b877facSJulian Elischer	There are still some minor problems with some signals but the
6372b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
6382b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
6392b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6402b877facSJulian Elischer
64106596d37SWarner Losh20020701:
64206596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
64306596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
64406596d37SWarner Losh	GNOME.
64506596d37SWarner Losh
64695ba4330SJacques Vidrine20020511:
64795ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
64895ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
64995ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
65095ba4330SJacques Vidrine	with the set-user-ID bit set.
65195ba4330SJacques Vidrine
652a81da3c9SDavid E. O'Brien20020510:
653f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
654f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6554b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
656f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
657f50caf6fSDavid E. O'Brien
658f50caf6fSDavid E. O'Brien20020510:
659a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
660a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
661a81da3c9SDavid E. O'Brien	and then do a cvs update.
662a81da3c9SDavid E. O'Brien
663528a0ef5SJacques Vidrine20020421:
664528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
665528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
666528a0ef5SJacques Vidrine
66785aa5a2eSGregory Neil Shapiro20020404:
66885aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
66985aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
67085aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
67185aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
67285aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
67385aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
67485aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
67585aa5a2eSGregory Neil Shapiro
6768f1e4358SRuslan Ermilov20020403:
6778f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
6788f1e4358SRuslan Ermilov
6792292c02eSWarner Losh20020315:
6802292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
6812292c02eSWarner Losh
68269f7bcf3SWarner Losh20020225:
68369f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
68469f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
68569f7bcf3SWarner Losh
6868f35c493SWarner Losh20020217:
6878f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6888f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6898f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6908f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6918f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6928f35c493SWarner Losh
693835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
694835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
695835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
696835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
697835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
698835284beSWarner Losh	and group must be merged from src/etc/group and
699835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
700835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
701835284beSWarner Losh	mergemaster before this will work if you are updating from a
702835284beSWarner Losh	very old version of current.  The updating recipe has changed
703835284beSWarner Losh	as of this date.
704835284beSWarner Losh
705fa9401c1SWarner Losh20020112:
706fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
707fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
708fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
709fa9401c1SWarner Losh	you have local modifications, you can use
710fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
711fa9401c1SWarner Losh	/etc/pam.d.
712fa9401c1SWarner Losh
713fa9401c1SWarner Losh	Please see the following url for more details:
714fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
71547d0d01fSWarner Losh20011229:
71647d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
71747d0d01fSWarner Losh	networkfs_types, please note that it has changed
71847d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
71947d0d01fSWarner Losh
720514318a8SWarner Losh20011220:
721514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
722514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
723514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
724514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
725514318a8SWarner Losh	version have now been merged back into the base system's
726514318a8SWarner Losh	version now.  The only user-visible change resulting from this
727514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
728514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
729514318a8SWarner Losh	as well.  (There has never been rc file support for
730514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
731514318a8SWarner Losh	reverted by the time the changes are MFCed.)
732514318a8SWarner Losh
733514318a8SWarner Losh20011215:
734514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
735514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
736514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
737514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
738514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
739514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
740514318a8SWarner Losh	will need to be customized then for `odd' densities using
741514318a8SWarner Losh	fdcontrol(8).
742514318a8SWarner Losh
7432d22e2bfSWarner Losh20011209:
7442d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7452d22e2bfSWarner Losh	and truss(1) now works again.
7462d22e2bfSWarner Losh
7479e0428e2SWarner Losh20011207:
7489e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7499e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7509e0428e2SWarner Losh	see
7519e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7529e0428e2SWarner Losh	for details.
7539e0428e2SWarner Losh
7549bab8c59SWarner Losh20011204:
7559bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7569bab8c59SWarner Losh	kernel and burncd to be in sync.
7579bab8c59SWarner Losh
758e57d8b01SWarner Losh20011203:
759e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
760e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
761e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
762e57d8b01SWarner Losh	not there already.
763e57d8b01SWarner Losh
764e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
765e57d8b01SWarner Losh	until the issue has been resolved.
766e57d8b01SWarner Losh
767b001d36fSJacques Vidrine20011202:
768b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
769b001d36fSJacques Vidrine	patched.
770b001d36fSJacques Vidrine
7714b676ec1SWarner Losh20011126:
7724b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
7735ebbf43eSWarner Losh	after this date.  You need to do this only once.
7744b676ec1SWarner Losh
775d961e462SWarner Losh20011103:
776d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
777d961e462SWarner Losh	edges may be left, but for the most part things should be
7784b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
779d961e462SWarner Losh
780d961e462SWarner Losh20011030:
781d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
782d961e462SWarner Losh	choppy waves in the upgrade process.
783d961e462SWarner Losh
7841fe003b6SWarner Losh20011030:
785a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7861fe003b6SWarner Losh
7871fe003b6SWarner Losh20011027:
7881fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7891fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7901fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7911fe003b6SWarner Losh	try to use from this date forward.
7921fe003b6SWarner Losh
7931fe003b6SWarner Losh20011025:
7941fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7951fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7961fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7971fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7981fe003b6SWarner Losh	TARGET_ARCH=i386.
7991fe003b6SWarner Losh
800d05f9643SWarner Losh20011001:
801d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
802d05f9643SWarner Losh	You must recompile both the kernel and userland applications
803d05f9643SWarner Losh	at the same time.
804d05f9643SWarner Losh
80558970f85SWarner Losh20010929:
80658970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
80758970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
80858970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
80958970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
8109d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
81158970f85SWarner Losh
81258970f85SWarner Losh20010927:
81358970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
81458970f85SWarner Losh	To disable ACPI you can add
81566ff0e67SMax Khon		hint.acpi.0.disabled="1"
81658970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
81758970f85SWarner Losh	loader "ok" prompt).
81858970f85SWarner Losh
81958970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
82058970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
82158970f85SWarner Losh	file and not list acpi in that list.
822378f4486SAlfred Perlstein
8235119d237SWarner Losh20010924:
8245119d237SWarner Losh	The buildworld has been fixed.  You may need to install
8255119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8268b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
8278b039fffSWarner Losh	get them installed on every installworld, or execute the
8288b039fffSWarner Losh	following to get them installed only once:
8298b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
83058970f85SWarner Losh		make all install
8318b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
8325119d237SWarner Losh
8333c293725SWarner Losh20010919:
8343c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
8353c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
8363c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
837772730c7SWarner Losh	workaround is to add
8383c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
8393c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8403c293725SWarner Losh	can be removed afterwards.
8413c293725SWarner Losh
8423c293725SWarner Losh	A proper fix to the buildworld target is needed.
8433c293725SWarner Losh
8443c293725SWarner Losh20010918:
8453c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8463c293725SWarner Losh	NFS may be unstable after this date.
8473c293725SWarner Losh
8483c293725SWarner Losh20010912:
8493c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8503c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8513c293725SWarner Losh	initial commit, most of the major ones have been found and
8523c293725SWarner Losh	corrected.
8533c293725SWarner Losh
8543c293725SWarner Losh20010901:
8553c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8563c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8573c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8583c293725SWarner Losh	have been rectified around this date.
8593c293725SWarner Losh
86098b17b95SWarner Losh20010823:
86198b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
86298b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
86398b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
86498b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
86598b17b95SWarner Losh 	sure that user or group bind has read (and not write)
86698b17b95SWarner Losh 	permission for your name server configuration and that it
86798b17b95SWarner Losh 	has read and write permission for your slave zone files and
86898b17b95SWarner Losh 	directory.
86998b17b95SWarner Losh
87098b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
87198b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
87298b17b95SWarner Losh
87398b17b95SWarner Losh 		named_flags=
87498b17b95SWarner Losh
8757b9786edSMark Murray20010709:
8767b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
8777b9786edSMark Murray	the ability of the shared library major number to handle.
8787b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
8797b9786edSMark Murray	solution is to rebuild those ports.
8807b9786edSMark Murray
8811d28950eSWarner Losh20010628:
8821d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
8831d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8841d28950eSWarner Losh
885e72fd46aSWarner Losh20010625:
88698b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
88798b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
88898b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
88998b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
89098b17b95SWarner Losh	IRQ configuration needs more safety belts.
89116de1a07SWarner Losh
8920d415dffSWarner Losh20010617:
893e72fd46aSWarner Losh	Softupdates problems have been corrected.
8940d415dffSWarner Losh
8950d415dffSWarner Losh20010614:
8960d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8970d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8980d415dffSWarner Losh	kernel building methods.
8990d415dffSWarner Losh
9008b9959adSWarner Losh20010613:
9018b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
9028b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
903e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
904e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
9058b9959adSWarner Losh
906e72fd46aSWarner Losh20010613:
9078b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
908e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
909e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
9108b9959adSWarner Losh
9110d415dffSWarner Losh20010612:
9120d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
9130d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
9140d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
9150d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
9160d415dffSWarner Losh	until this bug is fixed.
9170d415dffSWarner Losh
918e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
919e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
920ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
921e72fd46aSWarner Losh
9220d415dffSWarner Losh20010610:
9230d415dffSWarner Losh	Locale names have changed to match other systems better.
9240d415dffSWarner Losh
9256ccdb5e4SWarner Losh20010604:
9266ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
9276ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
9286ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
9293590182eSWarner Losh	Interrupt storms look a lot like a hang.
9303590182eSWarner Losh
9313590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
9323590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
9333590182eSWarner Losh	it is).
9343590182eSWarner Losh
9353590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
9363590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
9373590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
9383590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
9396ccdb5e4SWarner Losh
9400bc62786SWarner Losh20010530:
9410bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9420bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9430bc62786SWarner Losh	a limited time.  If you see
9440bc62786SWarner Losh
9450bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9460bc62786SWarner Losh
9470bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9480bc62786SWarner Losh	COPY=-C.
9490bc62786SWarner Losh
95068a38c6cSWarner Losh20010525:
951b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
952c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
953c4f4a728SWarner Losh	definitely is in bad shape.
95468a38c6cSWarner Losh
955ed0f29caSWarner Losh20010521:
956ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
957ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
958ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
959ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
960ed0f29caSWarner Losh	is
961ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
962ed0f29caSWarner Losh
96380c16af9SWarner Losh20010520:
96468a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
96580c16af9SWarner Losh
96680c16af9SWarner Losh20010519:
96780c16af9SWarner Losh	pccard has had much reorganizational work done to it over
96880c16af9SWarner Losh	the past few days.  Everything should still work, but if
96980c16af9SWarner Losh	not, please contact imp@freebsd.org.
97080c16af9SWarner Losh
971a45f2d05SWarner Losh20010517:
972a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
973a45f2d05SWarner Losh	userland at the same time.
974a45f2d05SWarner Losh
975a45f2d05SWarner Losh20010517:
976a45f2d05SWarner Losh	New ncurses imported.
977a45f2d05SWarner Losh
9782988afcaSWarner Losh20010512:
9792988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
9802988afcaSWarner Losh	will be the only way to go starting July 1.
9812988afcaSWarner Losh
9821a33dba7SWarner Losh20010504:
9831a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9841a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9851a33dba7SWarner Losh
98609946a51SWarner Losh20010502:
98709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
98809946a51SWarner Losh
98909946a51SWarner Losh20010501:
99009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
99109946a51SWarner Losh
99209946a51SWarner Losh20010430:
993a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
99409946a51SWarner Losh	go back in the water.
99509946a51SWarner Losh
99609946a51SWarner Losh20010429:
99709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
99809946a51SWarner Losh	this date, but before the correction date.
99909946a51SWarner Losh
100091dd3b53SWarner Losh20010423:
100191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
100291dd3b53SWarner Losh
100391dd3b53SWarner Losh20010411:
100491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
100591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
100691dd3b53SWarner Losh	Update only if you understand that you must not use the old
100791dd3b53SWarner Losh	fsck with the new kernel ever.
100891dd3b53SWarner Losh
1009933b3269SWarner Losh20010330:
1010933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
1011c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
1012933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
1013933b3269SWarner Losh
1014933b3269SWarner Losh20010319:
1015933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1016933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1017933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1018f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
101909946a51SWarner Losh
102009946a51SWarner Losh20010315:
102109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1022ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
102309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1024933b3269SWarner Losh
1025933b3269SWarner Losh20010312:
1026933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1027933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1028933b3269SWarner Losh
1029933b3269SWarner Losh20010312:
1030933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1031933b3269SWarner Losh	instead of ad-hoc.
1032933b3269SWarner Losh
1033933b3269SWarner Losh20010310:
1034f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1035933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1036933b3269SWarner Losh	ssh might not work if you don't.
1037933b3269SWarner Losh
103862353691SWarner Losh20010303:
103962353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
104062353691SWarner Losh	which means that you must include the miibus in your kernel if
104162353691SWarner Losh	you use the ed driver.
104262353691SWarner Losh
1043d325cf65SWarner Losh20010220:
1044d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1045d325cf65SWarner Losh	safe to go back into the water.
1046d325cf65SWarner Losh
1047024daae6SWarner Losh20010211:
1048024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1049024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1050024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1051024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1052024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1053024daae6SWarner Losh
1054024daae6SWarner Losh	To get to the new system, you'll need to use the following
1055024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1056024daae6SWarner Losh	don't have to move this to the updating section.
1057024daae6SWarner Losh
1058024daae6SWarner Losh	To get around the installworld problem, do:
1059024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1060024daae6SWarner Losh		# make install
1061024daae6SWarner Losh		# cd /usr/src
1062024daae6SWarner Losh		# make installworld
1063024daae6SWarner Losh	If that doesn't work, then try:
1064024daae6SWarner Losh		# make -k installworld
1065024daae6SWarner Losh		# make installworld
1066024daae6SWarner Losh
1067024daae6SWarner Losh20010207:
1068024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1069024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1070024daae6SWarner Losh
1071024daae6SWarner Losh20010205:
10727595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1073024daae6SWarner Losh	Remove them from your config.
1074024daae6SWarner Losh
10751e159248SWarner Losh20010122:
10761e159248SWarner Losh	****************************** WARNING ******************************
10771e159248SWarner Losh			buildkernel has been changed slightly
10781e159248SWarner Losh	****************************** WARNING ******************************
10791e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
10801e159248SWarner Losh	should update your scripts and make.conf accordingly.
10811e159248SWarner Losh
10821e159248SWarner Losh20010119:
10831e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10841e159248SWarner Losh	This requires a new config to build correctly.
10851e159248SWarner Losh
1086aac7dfeaSWarner Losh20010116:
1087ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1088aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1089aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1090aac7dfeaSWarner Losh
1091aac7dfeaSWarner Losh20010110:
1092aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1093aac7dfeaSWarner Losh
1094aac7dfeaSWarner Losh20010102:
1095aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1096aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1097aac7dfeaSWarner Losh
109863c90c9eSWarner Losh20010101:
109963c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
110063c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
11015fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
110263c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
110363c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
110463c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
110563c90c9eSWarner Losh	might have been ignored by the -k option.
110663c90c9eSWarner Losh
11075fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
11085fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
11095fd2a895SWarner Losh	of this working.
11105fd2a895SWarner Losh
1111aac7dfeaSWarner Losh20001228:
1112aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1113ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1114aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1115aac7dfeaSWarner Losh
1116de2bcc63SWarner Losh20001218:
1117de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1118de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1119de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1120de2bcc63SWarner Losh	cards will not be recognized without it.
1121de2bcc63SWarner Losh
1122960773f7SWarner Losh20001205:
1123960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1124960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1125960773f7SWarner Losh	adding the following in pam.conf:
1126960773f7SWarner Losh
1127960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1128960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1129960773f7SWarner Losh	sshd    session required        pam_permit.so
1130960773f7SWarner Losh
11310acc635eSWarner Losh20001031:
11320acc635eSWarner Losh	cvs updated to 1.11.
11330acc635eSWarner Losh
11340acc635eSWarner Losh20001020:
11350acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
11360acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
11370acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
11380acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
11390acc635eSWarner Losh	workaround.
11400acc635eSWarner Losh
11410acc635eSWarner Losh20001010:
11420acc635eSWarner Losh	****************************** WARNING ******************************
11430acc635eSWarner Losh				Sendmail has been updated.
11440acc635eSWarner Losh	****************************** WARNING ******************************
11450acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11460acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11470acc635eSWarner Losh	  is set.
11480acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11490acc635eSWarner Losh	  commands.
11500acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11510acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11520acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11530acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11540acc635eSWarner Losh
11550acc635eSWarner Losh	More details can be found at
11560acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11570acc635eSWarner Losh
11586e98a146SWarner Losh20001009:
11596e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11606e98a146SWarner Losh	your entire ports tree, or you will have problems.
11616e98a146SWarner Losh
11626e98a146SWarner Losh20001006:
1163685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
11646e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
11656e98a146SWarner Losh	/usr/bin/miniperl.
11666e98a146SWarner Losh
1167073113a4SWarner Losh20001005:
1168073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1169685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1170073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1171073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1172073113a4SWarner Losh	tree for anything to work.
1173073113a4SWarner Losh
11740acc635eSWarner Losh20000928:
11750acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
11760acc635eSWarner Losh
1177be3885b3SWarner Losh20000916:
1178be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1179be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1180be3885b3SWarner Losh	same time as your kernel.
1181be3885b3SWarner Losh
118276ec9675SWarner Losh20000914:
118376ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
118476ec9675SWarner Losh	include the device will cause suspended laptops losing time
118576ec9675SWarner Losh	when they resume.  Include
118676ec9675SWarner Losh		device		pmtimer
118776ec9675SWarner Losh	in your config file and
118801b9a434SWarner Losh		hint.pmtimer.0.at="isa"
118976ec9675SWarner Losh	to your /boot/device.hints file.
119076ec9675SWarner Losh
1191f4865386SMark Murray20000911:
1192f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1193f4865386SMark Murray	rather than an option. The supplied kernel config files have
1194f4865386SMark Murray	been updated. You will need to do something similar in your
1195f4865386SMark Murray	own kernel config file.
1196f4865386SMark Murray	Remove:
1197f4865386SMark Murray		options		RANDOMDEV
1198f4865386SMark Murray	Add:
1199f4865386SMark Murray		device		random
1200f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1201f4865386SMark Murray	nothing.
1202f4865386SMark Murray
1203d594498fSWarner Losh20000909:
1204d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1205d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1206d594498fSWarner Losh	reflect this if you load this module at boot time.
1207d594498fSWarner Losh	The line should read:
1208d594498fSWarner Losh		random_load="YES"
1209d594498fSWarner Losh
12100deb7ddcSWarner Losh20000907:
12110deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
121216eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
121316eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
121416eb772dSWarner Losh	sure you don't have model loading problems which might at
121516eb772dSWarner Losh	first blush appear related to SMP.
121652bf24e7SWarner Losh
12175a01880bSWarner Losh20000906:
12185a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
12195a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
12205a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
12215a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
12225a01880bSWarner Losh	don't have one, and you have host.conf.
12235a01880bSWarner Losh
12242b41163cSWarner Losh20000905:
122538d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
122638d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
122738d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
122838d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
122938d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
123038d6ecd2SWarner Losh
123138d6ecd2SWarner Losh20000905:
12328aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
12338aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
12348aab4bc7SWarner Losh	is /boot/kernel.
12358aab4bc7SWarner Losh
12368aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
123738d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
123838d6ecd2SWarner Losh	installkernel/installworld dance.
12392b41163cSWarner Losh
1240d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1241d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1242d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1243d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1244d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1245d594498fSWarner Losh
1246d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1247d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1248d594498fSWarner Losh		chflags noschg /kernel.old
1249d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1250d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1251d594498fSWarner Losh	fi
1252d594498fSWarner Losh
1253c22a309cSWarner Losh20000904:
1254c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1255c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1256c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1257c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1258c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1259c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1260c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1261c22a309cSWarner Losh	is not likely to be generated.
1262c22a309cSWarner Losh
1263fdb9f54dSWarner Losh20000825:
1264fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
12659c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
12669c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
12679c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
12689c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
12699c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
12709c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
12719c1a7444SWarner Losh	kernel.
12729c1a7444SWarner Losh
12739c1a7444SWarner Losh20000821:
12749c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
12759c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
12769c1a7444SWarner Losh	/boot/loader.conf.
1277fdb9f54dSWarner Losh
12788f250aa7SWarner Losh20000812:
12795da0d091SWarner Losh	suidperl is now always built and installed on the system, but
12805da0d091SWarner Losh	with permissions of 511.  If you have applications that use
12815da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
12825da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
12835da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12845da0d091SWarner Losh	will fix this until the next build.
12855da0d091SWarner Losh
12865da0d091SWarner Losh20000812:
12878f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12888f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12898f250aa7SWarner Losh	include:
12908f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12918f250aa7SWarner Losh	- newaliases limited to root and trusted users
12928f250aa7SWarner Losh	- MSA port (587) turned on by default
12938f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12948f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12958f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12968f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12978f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12988f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12998f250aa7SWarner Losh
130071c38472SWarner Losh20000810:
130171c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
130271c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
130371c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
130471c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
130571c38472SWarner Losh	specific use for it.
130671c38472SWarner Losh
130771c38472SWarner Losh20000729:
130871c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
130971c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
131071c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
131171c38472SWarner Losh	afterwards (unless the variables already are set, of course):
131271c38472SWarner Losh		# Enable network daemons for user convenience.
131371c38472SWarner Losh		inetd_enable="YES"
131471c38472SWarner Losh		portmap_enable="YES"
131571c38472SWarner Losh		sendmail_enable="YES"
131671c38472SWarner Losh
131771c38472SWarner Losh20000728:
131871c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
131971c38472SWarner Losh	will need to change that to nullfs_load="YES".
132071c38472SWarner Losh
13211dece4a9SWarner Losh20000728:
13221dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
13231dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
13241dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
13251dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
13261dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
13271dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
13281dece4a9SWarner Losh	to /MYKERNEL.
13291dece4a9SWarner Losh
1330409e887cSWarner Losh20000711:
1331409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1332409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1333409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1334409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1335409e887cSWarner Losh	for details on potential problems that you might have and how
1336409e887cSWarner Losh	to get around them.
1337409e887cSWarner Losh
1338409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1339409e887cSWarner Losh	clauses above, you needn't worry.
1340409e887cSWarner Losh
1341409e887cSWarner Losh20000711:
1342409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1343409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1344409e887cSWarner Losh	in the number of changed programs the first time when you run
1345409e887cSWarner Losh	mergemaster to get a new /etc/security.
1346409e887cSWarner Losh
1347673d13f2SWarner Losh20000710:
1348673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1349673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1350673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1351673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1352673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1353673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1354673d13f2SWarner Losh	errors. (see below, 20000624).
1355673d13f2SWarner Losh
1356bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13571dece4a9SWarner Losh
1358673d13f2SWarner Losh20000709:
1359c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1360c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1361c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1362673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1363673d13f2SWarner Losh
1364e98e26cdSWarner Losh20000706:
1365e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1366e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1367e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1368f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1369e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
13702c021c6cSMark Ovens	interim if needed.
1371e98e26cdSWarner Losh
1372e98e26cdSWarner Losh20000705:
1373e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1374e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1375e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1376e98e26cdSWarner Losh	details.
1377e98e26cdSWarner Losh
1378c373950eSWarner Losh20000704:
13792f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
13802f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
13812f961bc8SWarner Losh
13822f961bc8SWarner Losh20000704:
1383c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1384c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1385c373950eSWarner Losh	rc.d scripts that haven't been updated.
1386c373950eSWarner Losh
138727dc3a2bSWarner Losh20000630:
138827dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
138927dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
139027dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
139127dc3a2bSWarner Losh
1392b8c215acSWarner Losh20000625:
1393b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
139427dc3a2bSWarner Losh	system installed in order to build the system and kernel.
139527dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
139627dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
139727dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
139827dc3a2bSWarner Losh	were required.  You should check with the latest collections
139927dc3a2bSWarner Losh	to make sure that these haven't changed.
1400b8c215acSWarner Losh
14017b990719SWarner Losh20000624:
14027b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
14037b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
14047b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
14051a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
14067b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
14077b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
14087b990719SWarner Losh	date to the completion of the work.
14097b990719SWarner Losh
141027dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
141127dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
141227dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
141327dc3a2bSWarner Losh	recreate the random and urandom devices.
141427dc3a2bSWarner Losh
141581e54c50SWarner Losh20000622:
141681e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
141781e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
141881e54c50SWarner Losh	that used to be required when updating.
141981e54c50SWarner Losh
142039943833SWarner Losh20000621:
14212c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
14222a2f33fbSDaniel Baker	the config file update procedure.
14232a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1424c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
142559df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
142659df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
142739943833SWarner Losh
1428290f9ad8SWarner Losh20000620:
1429290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1430290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1431290f9ad8SWarner Losh	that workaround will no longer be required.
1432290f9ad8SWarner Losh
143390fb6346SWarner Losh20000615:
143490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
143590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
143690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
143790fb6346SWarner Losh	devices.
143890fb6346SWarner Losh
1439f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1440f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1441f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1442f75f65bbSWarner Losh	may work).
1443f75f65bbSWarner Losh
1444ba26da8eSWarner Losh20000612:
1445ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1446290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1447c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1448290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1449f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1450f54a3542SWarner Losh	NEWCARD for examples of the new format.
1451290f9ad8SWarner Losh
14529698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14539698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14549698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14559698f2c0SWarner Losh	in it.
1456bbcc5149SWarner Losh
1457d65850ebSWarner Losh20000522:
1458ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1459d65850ebSWarner Losh	building a kernel after this point is advised that they need
1460d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1461d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1462d65850ebSWarner Losh
1463d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1464d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1465d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1466d9583a00SWarner Losh	is resolved.
1467d9583a00SWarner Losh
14688039cedeSWarner Losh20000513:
14698039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
14708039cedeSWarner Losh
1471d65850ebSWarner Losh20000510:
14728039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
14738039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
14748039cedeSWarner Losh	is requires for the boot blocks to build properly.
14758039cedeSWarner Losh
14768039cedeSWarner Losh20000503:
14778039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
14788039cedeSWarner Losh	is now available.
14798039cedeSWarner Losh
1480d65850ebSWarner Losh20000502:
1481d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1482d65850ebSWarner Losh	connected to the kernel building instead.
1483d65850ebSWarner Losh
1484be149406SNik Clayton20000427:
14858039cedeSWarner Losh	You may need to build gperf
14868039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14878039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14888039cedeSWarner Losh	an option only in -current.
14898039cedeSWarner Losh
14902b8dd5f4SWarner Losh20000417:
14912b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1492f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14932b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14942b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14952c021c6cSMark Ovens	before you reboot, you'll need to issue:
14962b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14972b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14982b8dd5f4SWarner Losh
14998d9f1945SWarner Losh20000320:
15002b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
15012b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
15022b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1503ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
15042b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
15058d9f1945SWarner Losh
1506f8ab1dd6SWarner Losh20000319:
1507f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1508f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1509f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1510f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1511f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1512f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1513f8ab1dd6SWarner Losh
151419cada77SWarner Losh20000318:
1515f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
151619cada77SWarner Losh	Large kernel changes are being committed and are in the
151719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
151819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
151919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
152019cada77SWarner Losh	that you are loading are up to date.
1521ba228352SWarner Losh
152219cada77SWarner Losh20000315:
15236d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
15246d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
15256d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
15266d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
15276d23c382SWarner Losh	boot.
15286d23c382SWarner Losh
15296d23c382SWarner Losh20000315:
153019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
153119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
153257199806SWarner Losh
1533dc0dbf5cSWarner LoshCOMMON ITEMS:
1534dc0dbf5cSWarner Losh
1535a24eff53SWarner Losh	General Notes
1536a24eff53SWarner Losh	-------------
1537a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1538a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1539a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1540a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1541a24eff53SWarner Losh	or several minor releases, or when several months have passed
1542a24eff53SWarner Losh	on the -current branch).
1543a24eff53SWarner Losh
15445780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15455780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15465780f3baSWarner Losh	environment when searching for values for global variables.
15475780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15485780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15495780f3baSWarner Losh	page for more details.
15505780f3baSWarner Losh
1551dc0dbf5cSWarner Losh	To build a kernel
1552dc0dbf5cSWarner Losh	-----------------
1553ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1554f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1555ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1556282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1557282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1558dc0dbf5cSWarner Losh
1559ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1560ba01eb20SWarner Losh	--------------------------------------------------------------
15610fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15620fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
15630fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
15640fbd2da9SKen Smith
15650fbd2da9SKen Smith	cd src/sys/${arch}/conf
156647d0d01fSWarner Losh	config KERNEL_NAME_HERE
15670fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1568ba01eb20SWarner Losh	make depend
1569ba01eb20SWarner Losh	make
1570ba01eb20SWarner Losh	make install
1571ba01eb20SWarner Losh
1572ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1573ba01eb20SWarner Losh
1574ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1575ba01eb20SWarner Losh	-----------------------------------------------------------
157663cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
157763cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
157863cb445eSWarner Losh
1579f643de42SWarner Losh	<make sure you have good level 0 dumps>
158063cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
158163cb445eSWarner Losh	make buildworld
158263cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
158363cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
158463cb445eSWarner Losh							[1]
158563cb445eSWarner Losh	<reboot in single user>				[3]
15868633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
158763cb445eSWarner Losh	mergemaster -p					[5]
158863cb445eSWarner Losh	make installworld
158963cb445eSWarner Losh	mergemaster					[4]
159063cb445eSWarner Losh	<reboot>
159163cb445eSWarner Losh
1592759f0aefSWarner Losh
1593f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1594f27b1fceSJoseph Koshy	--------------------------------------------------
1595f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1596f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1597f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1598f27b1fceSJoseph Koshy	# size.
1599f27b1fceSJoseph Koshy
1600f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1601f27b1fceSJoseph Koshy	<boot into -stable>
1602f27b1fceSJoseph Koshy	make buildworld
1603f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1604f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1605f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1606f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1607f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1608f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1609f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1610f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1611f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1612f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1613f27b1fceSJoseph Koshy	<reboot into current>
1614f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1615f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1616f27b1fceSJoseph Koshy 	<reboot>
1617f27b1fceSJoseph Koshy
1618f27b1fceSJoseph Koshy
1619f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1620f27b1fceSJoseph Koshy	----------------------------------------------
16215c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
16225c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
16235c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
16245c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1625ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1626f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1627f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1628f643de42SWarner Losh	# space on /.
1629f643de42SWarner Losh
1630f643de42SWarner Losh	<make sure you have good level 0 dumps>
1631fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
163221c075eaSWarner Losh	make buildworld					[9]
1633c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1634802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1635be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1636802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1637fc8c157fSWarner Losh							[1]
1638fc8c157fSWarner Losh	<reboot in single user>				[3]
1639802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1640835284beSWarner Losh	mergemaster -p					[5]
1641f8a4c901SWarner Losh	rm -rf /usr/include/g++
1642ba26da8eSWarner Losh	make installworld
1643802fc49dSBrian Feldman	mergemaster -i					[4]
1644ba26da8eSWarner Losh	<reboot>
1645ba26da8eSWarner Losh
1646fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1647fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1648fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1649fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1650fdb9f54dSWarner Losh	the UPDATING entries.
1651ba26da8eSWarner Losh
16521dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16531dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16541dece4a9SWarner Losh	your sources that you have read and understood all the recent
16551dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16561dece4a9SWarner Losh	much fewer pitfalls.
16571dece4a9SWarner Losh
1658134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1659134d2e86SWarner Losh	should disable them at this point so they don't crash your
1660134d2e86SWarner Losh	system on reboot.
1661134d2e86SWarner Losh
16629c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
16639c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
16649c1a7444SWarner Losh	configuration.
16659c1a7444SWarner Losh
1666ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1667ee6e1fc3SWarner Losh		fsck -p
1668ee6e1fc3SWarner Losh		mount -u /
1669ee6e1fc3SWarner Losh		mount -a
1670ee6e1fc3SWarner Losh		cd /usr/src
167147d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1672f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1673f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1674b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1675b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1676b705ae10SWarner Losh	be ignored while you proceed to the next step.
1677ee6e1fc3SWarner Losh
1678a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1679a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1680a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1681a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1682a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1683a6cd4f9dSWarner Losh	for potential gotchas.
1684a6cd4f9dSWarner Losh
1685835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1686835284beSWarner Losh	you may need to do this if you get unknown user in the following
1687835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1688835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1689835284beSWarner Losh	install) after the buildworld before this step if you last updated
1690835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1691835284beSWarner Losh
1692bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1693bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1694bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1695bd79cf40SWarner Losh		ok unload
1696bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1697bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1698bd79cf40SWarner Losh	described here.
1699fc8c157fSWarner Losh
1700fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1701fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1702fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1703fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1704fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1705fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1706fc8c157fSWarner Losh
1707c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1708c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1709c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1710c74fe6afSWarner Losh	that is hard to boot to recover.
1711c74fe6afSWarner Losh
171221c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1713802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1714802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1715802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1716802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1717802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1718802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1719802fc49dSBrian Feldman	using your existing software for a while.
17208633bbeaSBrooks Davis
17218633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
17228633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
17238633bbeaSBrooks Davis	takes care of this.
1724dc0dbf5cSWarner LoshFORMAT:
1725dc0dbf5cSWarner Losh
1726f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
17271fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1728f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1729f8ab1dd6SWarner Loshprevious releases if your system is older than this.
17301fc1a0dcSWarner Losh
1731e72fd46aSWarner LoshCopyright information:
1732e72fd46aSWarner Losh
17339698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1734e72fd46aSWarner Losh
1735772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1736772730c7SWarner Loshmodification, in full or in part, in any form or format of this
17379698f2c0SWarner Loshdocument are permitted without further permission from the author.
1738e72fd46aSWarner Losh
1739e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1740e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1741e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1742e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1743e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1744e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1745e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1746e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1747e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1748e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1749e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1750e72fd46aSWarner Losh
1751e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1752e72fd46aSWarner Loshauthor a beer.
1753e72fd46aSWarner Losh
175422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1755772730c7SWarner Loshthis document.
1756772730c7SWarner Losh
175797d92980SPeter Wemm$FreeBSD$
1758