xref: /freebsd/UPDATING (revision 2c724730d4d615dbf8d5333c126cd1308428ac9d)
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
2454bd5271SAlexander Kabaev20030728:
2554bd5271SAlexander Kabaev	System compiler has been upgraded to GCC 3.4.2-pre. As with any major
2654bd5271SAlexander Kabaev	compiler upgrade, there are several issues to be aware of. GCC 3.4.x
2754bd5271SAlexander Kabaev	has broken C++ ABI compatibility with previous releases yet again
2854bd5271SAlexander Kabaev	and users will have to rebuild all their C++ programs with the new
2954bd5271SAlexander Kabaev	compiler. A new unit-at-a-time optimization mode, which is default
3054bd5271SAlexander Kabaev	in this compiler release, is more aggressive in removing unused
3154bd5271SAlexander Kabaev	static symbols. This is the likely cause of 'make buildworld'
3254bd5271SAlexander Kabaev	breakages with non-default CFLAGS where optimization level is set
3354bd5271SAlexander Kabaev	to -O2 or higher.
3454bd5271SAlexander Kabaev
3536ed21e6SRobert Watson20040727:
3636ed21e6SRobert Watson	The size of 'struct ifnet' has changed due to the addition of
3736ed21e6SRobert Watson	the IFF_NEEDSGIANT flag (and what it implies).  All kernel
3836ed21e6SRobert Watson	modules implementing network interfaces must be recompiled as
3936ed21e6SRobert Watson	a result.
4036ed21e6SRobert Watson
416305ac24SSeigo Tanimura20040716:
426305ac24SSeigo Tanimura	The sound device drivers are renamed.  `sound' is always required,
436305ac24SSeigo Tanimura	while `snd_*' should be configured accordingly to your hardware.
446305ac24SSeigo Tanimura	Refer to NOTES for the detail of the drivers.
456305ac24SSeigo Tanimura
46e623dcb7SMarcel Moolenaar20040710:
47e623dcb7SMarcel Moolenaar	__FreeBSD_version bumped to 502122.
48e623dcb7SMarcel Moolenaar
49e623dcb7SMarcel Moolenaar20040710:
50e623dcb7SMarcel Moolenaar	The console initialization on Alpha has been reworked and is now
51e623dcb7SMarcel Moolenaar	identical to other platforms. This means that the hardcoding of
52e623dcb7SMarcel Moolenaar	the serial console and the debug port has been removed. As such,
53e623dcb7SMarcel Moolenaar	hints are now required for the sio(4) driver to become a console
54e623dcb7SMarcel Moolenaar	or debug port. The NO_SIO option has been decommissioned because
55e623dcb7SMarcel Moolenaar	of this.
56e623dcb7SMarcel Moolenaar
57e623dcb7SMarcel Moolenaar20040710:
58e623dcb7SMarcel Moolenaar	A revamp of the debugging code in the kernel with some visible
59e623dcb7SMarcel Moolenaar	changes beyond just the debugging experience:
60e623dcb7SMarcel Moolenaar	o  The DDB option is now specific to the DDB debugger backend
61e623dcb7SMarcel Moolenaar	   and should not be used any more for conditional compilation
62e623dcb7SMarcel Moolenaar	   of debugging code for when debugging is enabled. Use the KDB
63e623dcb7SMarcel Moolenaar	   option for this.
64e623dcb7SMarcel Moolenaar	o  The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
65e623dcb7SMarcel Moolenaar	   been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
66e623dcb7SMarcel Moolenaar	   respectively. This is in line with the first bullet.
67e623dcb7SMarcel Moolenaar	o  The remote GDB support has been untangled from DDB and needs
685bd7ce0aSJens Schweikhardt	   to be enabled separately now. Use the GDB option for this.
69e623dcb7SMarcel Moolenaar	o  The GDB_REMOTE_CHAT option has been removed. Support for this
70e623dcb7SMarcel Moolenaar	   homegrown feature is discontinued. The GDB remote protocol
71e623dcb7SMarcel Moolenaar	   supports console output and it makes sense to use that.
72e623dcb7SMarcel Moolenaar	o  The DDB_NOKLDSYM option has been removed. The DDB debugger
73e623dcb7SMarcel Moolenaar	   now supports both direct symbol table lookups as well as KLD
74e623dcb7SMarcel Moolenaar	   symbol lookups through the linker.
75e623dcb7SMarcel Moolenaar
766421d1dbSMaksim Yevmenkin20040708:
776421d1dbSMaksim Yevmenkin	Bluetooth code has been marked as non-i386 specific.
786421d1dbSMaksim Yevmenkin	__FreeBSD_version has been bumped to 502121 to mark this change.
796421d1dbSMaksim Yevmenkin
8058af3216SWarner Losh20040702:
8158af3216SWarner Losh	The native preemption has been added to the kernel scheduler.
825bd7ce0aSJens Schweikhardt	There is some report that the ULE scheduler was broken in some
835bd7ce0aSJens Schweikhardt	machines and we encourage users using the ULE scheduler either
845bd7ce0aSJens Schweikhardt	stick with a known good kernel, or temporarily switch to the 4BSD
8558af3216SWarner Losh	scheduler as a workaround.
8658af3216SWarner Losh
87c2dba668SNate Lawson20040630:
888ed370fdSJulian Elischer	The netgraph ABI version number has been incremented to indicate
898ed370fdSJulian Elischer	an incompatible change in the ABI. Old netgraph nodes will refuse
90a6c26e1cSBruce M Simpson	to attach until recompiled. Netgraph now uses mbuf tags to move
91a6c26e1cSBruce M Simpson	metadata and this commit removes its home-grown metadata facility.
92a6c26e1cSBruce M Simpson	Nodes should just recompile, unless they use metadata, in which
93a6c26e1cSBruce M Simpson	case the changes are simple; the file ng_ksocket.c serves as an
94a6c26e1cSBruce M Simpson	example of such changes.
958ed370fdSJulian Elischer
9658af3216SWarner Losh	This also broke i4b, although the compile problem has been papered
9758af3216SWarner Losh	over.
9858af3216SWarner Losh
998ed370fdSJulian Elischer20040630:
100c2dba668SNate Lawson	ACPI has been updated to disable known-bad BIOS revisions.  A message
1015bd7ce0aSJens Schweikhardt	will be printed on the console indicating that ACPI has been disabled
102c2dba668SNate Lawson	automatically and that the user should use a newer BIOS, if possible.
103c2dba668SNate Lawson	If you think ACPI does work on your system and want to override
104c2dba668SNate Lawson	this (i.e., for testing), set hint.acpi.0.disabled="0" at the
105c2dba668SNate Lawson	loader prompt.
106c2dba668SNate Lawson
1078ee2ac9eSMax Laier20040623:
1085bd7ce0aSJens Schweikhardt	pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
1098ee2ac9eSMax Laier	separated now. It uses the newly created "_pflogd" user/group
1108ee2ac9eSMax Laier	combination. If you plan to use pflogd(8) make sure to run
1118ee2ac9eSMax Laier	mergemaster -p or install the "_pflogd" user and group manually.
1128ee2ac9eSMax Laier
1133db5687dSBrooks Davis20040622:
1143db5687dSBrooks Davis	Network interface cloning has been overhauled.  This change will
1153db5687dSBrooks Davis	require a recompile of modules using cloning and modification of
1163db5687dSBrooks Davis	external ones to the new API.  __FreeBSD_version has been bumped
1173db5687dSBrooks Davis	to 502119 to mark this change.  Additionally, users creating
1183db5687dSBrooks Davis	stf(4) interfaces via "ifconfig stf" will need to update their
1193db5687dSBrooks Davis	scripts as this will create an interface named "stf" instead of
1203db5687dSBrooks Davis	"stf0" and ifconfig will not print "stf0" to stdout.
1213db5687dSBrooks Davis
122e0ae81f3SDag-Erling Smørgrav20040621:
123e0ae81f3SDag-Erling Smørgrav	On 20040524, the /etc/rc.d/nsswitch script was modified to
124e0ae81f3SDag-Erling Smørgrav	automatically create /etc/nsswitch.conf on startup if it did
125e0ae81f3SDag-Erling Smørgrav	not already exist.  Unfortunately, an error in the man page
126e0ae81f3SDag-Erling Smørgrav	was carried over to the script, resulting in incorrect
127e0ae81f3SDag-Erling Smørgrav	nsswitch settings.  The simplest remedy is to remove both
128e0ae81f3SDag-Erling Smørgrav	/etc/nsswitch.conf and /etc/host.conf; they will be recreated
129e0ae81f3SDag-Erling Smørgrav	during the next reboot.
130e0ae81f3SDag-Erling Smørgrav
1314717d22aSJohn Polstra20040614:
1324717d22aSJohn Polstra	The return value of sema_timedwait(9) has been changed to
1334717d22aSJohn Polstra	make it consistent with cv_timedwait(9).  Be sure to recompile
1344717d22aSJohn Polstra	the ips module and any third-party modules which call
1354717d22aSJohn Polstra	sema_timedwait.
1364717d22aSJohn Polstra
1376cb7a382SMax Laier20040613:
1386cb7a382SMax Laier	ALTQ is now linked to the build. This breaks ABI for struct ifnet.
1396cb7a382SMax Laier	Make sure to recompile modules and any userland that makes use of
140df843493SMax Laier	sizeof(struct ifnet). In order to get the altq headers in place
141df843493SMax Laier	please recompile and reinstall world.
1426cb7a382SMax Laier
1432454685eSJulian Elischer20040607:
1442454685eSJulian Elischer	Splitting kern_thread.c into 2 files (adding kern_kse.c)
1452454685eSJulian Elischer	requires that you re-run config after updating your tree.
1462454685eSJulian Elischer
14764fef830SSeigo Tanimura20040601:
14864fef830SSeigo Tanimura	The MIDI drivers have been removed. Until the new module-friendly
14964fef830SSeigo Tanimura	ones are merged, remove or comment out midi and seq from your
15064fef830SSeigo Tanimura	kernel configuration.
15164fef830SSeigo Tanimura
152bb4f06e7SAndre Oppermann20040423:
153bb4f06e7SAndre Oppermann	Due to a new option in ipfw (versrcreach) the ipfw(8) command
154bb4f06e7SAndre Oppermann	needs to be recompiled.  Normal accept/reject rules without
155bb4f06e7SAndre Oppermann	options are not affected but those with options may break until
156bb4f06e7SAndre Oppermann	ipfw(8) is recompiled.
157bb4f06e7SAndre Oppermann
15805641e82SColin Percival20040420:
15905641e82SColin Percival	Due to changes in the callout ABI, kernels compiled after this
16005641e82SColin Percival	date may be incompatible with kernel modules compiled prior to
16105641e82SColin Percival	20040406.
16205641e82SColin Percival
163d0dc9183SWarner Losh20040414:
164d0dc9183SWarner Losh	The PCI bus power state stuff has been turned on.  If this causes
165d0dc9183SWarner Losh	problems for your system, please disable it using the tunable
166d0dc9183SWarner Losh	hw.pci.do_powerstate=0.
167d0dc9183SWarner Losh
168d0dc9183SWarner Losh20040412:
169d0dc9183SWarner Losh	The bulk of the pci problems have been fixed, although the floppy
170d0dc9183SWarner Losh	drive is still broken.
171d0dc9183SWarner Losh
172d0dc9183SWarner Losh20040410:
173d0dc9183SWarner Losh	A substantial update to the pci bus resource and power management
174d0dc9183SWarner Losh	have been committed.  Expect a bumpy ride for a few days until
175d0dc9183SWarner Losh	the unanticipated problems have been resolved.
176d0dc9183SWarner Losh
1778633bbeaSBrooks Davis20040409:
1788633bbeaSBrooks Davis        Due to changes in the the Yarrow initialization process,
1798633bbeaSBrooks Davis        /dev/random needs to be fed before operations requiring
1808633bbeaSBrooks Davis        temp files can succeed in single user mode.  This includes
1818633bbeaSBrooks Davis        running "make installworld". /dev/random may be fed by running
18276c3e0f7SBrooks Davis        "/etc/rc.d/initrandom start" or with 20040415 source by running
1838633bbeaSBrooks Davis        "/etc/rc.d/preseedrandom".
1848633bbeaSBrooks Davis
185d40d033aSRobert Watson20040322:
186d40d033aSRobert Watson	The debug.mpsafenet tunable controls whether the kernel Giant
187d40d033aSRobert Watson	lock is held across the lower levels of the network stack, and
188d40d033aSRobert Watson	by default is turned off.  In the few days following 20040322,
189d40d033aSRobert Watson	the behavior of debug.mpsafenet will change such that this
190d40d033aSRobert Watson	tunable controls Giant over all levels of the network stack.
191d40d033aSRobert Watson	If you are currently setting debug.mpsafenet to 1, you should
192d40d033aSRobert Watson	set it back to 0 (the default) again during the change-over.
193d40d033aSRobert Watson	An additional note will be added to UPDATING when sufficient
194d40d033aSRobert Watson	locking is merged to permit this to take place.
195d40d033aSRobert Watson
196ec9b318eSGarance A Drosehn20040310:
197ec9b318eSGarance A Drosehn	The FreeBSD/sparc64 platform is changing time_t from 32-bits to
198ec9b318eSGarance A Drosehn	64-bits.  This is a very major incompatible change, so people
199ec9b318eSGarance A Drosehn	using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
200ec9b318eSGarance A Drosehn	detailed instructions on how to make this upgrade.  People
201ec9b318eSGarance A Drosehn	upgrading FreeBSD on other platforms can ignore this event.
202ec9b318eSGarance A Drosehn
203fc28f1ffSMax Laier20040308:
204fc28f1ffSMax Laier	The packet filter (pf) is now installed with the base system. Make
205fc28f1ffSMax Laier	sure to run mergemaster -p before installworld to create required
2064c86458bSDavid E. O'Brien	user account ("proxy"). If you do not want to build pf with your
2074c86458bSDavid E. O'Brien	system you can use the NO_PF knob in make.conf.
208fc28f1ffSMax Laier	Also note that pf requires "options PFIL_HOOKS" in the kernel. The
209fc28f1ffSMax Laier	pf system consists of the following three devices:
210fc28f1ffSMax Laier	device		pf		# required
211fc28f1ffSMax Laier	device		pflog		# optional
212fc28f1ffSMax Laier	device		pfsync		# optional
213fc28f1ffSMax Laier
2143aff5d06SDag-Erling Smørgrav20040303:
2153aff5d06SDag-Erling Smørgrav	If you are having trouble with the libc_r -> libpthread transition
2163aff5d06SDag-Erling Smørgrav	(see the 20040130 entry), place the following lines at the top of
2173aff5d06SDag-Erling Smørgrav	/etc/libmap.conf:
2183aff5d06SDag-Erling Smørgrav
2193aff5d06SDag-Erling Smørgrav	libc_r.so.5		libpthread.so.1
2203aff5d06SDag-Erling Smørgrav	libc_r.so		libpthread.so
2213aff5d06SDag-Erling Smørgrav
2223aff5d06SDag-Erling Smørgrav	This will cause all programs and libraries linked against libc_r
2233aff5d06SDag-Erling Smørgrav	to use libpthread instead.
2243aff5d06SDag-Erling Smørgrav
225fd63c5b3SDag-Erling Smørgrav20040226:
2269d7f8c80SDag-Erling Smørgrav	Some sshd configuration defaults have changed: protocol version 1
227fd63c5b3SDag-Erling Smørgrav	is no longer enabled by default, and password authentication is
228fd63c5b3SDag-Erling Smørgrav	disabled by default if PAM is enabled (which it is by default).
229fd63c5b3SDag-Erling Smørgrav	OpenSSH clients should not be affected by this; other clients may
230fd63c5b3SDag-Erling Smørgrav	have to be reconfigured, upgraded or replaced.
231fd63c5b3SDag-Erling Smørgrav
232714ae42aSBruce M Simpson20040225:
233e07a40f3SBrian Feldman	The ABIs defined in <resolv.h> and <netdb.h> have been updated
234e07a40f3SBrian Feldman	to support improved reentrancy.  Multi-threaded programs that
235e07a40f3SBrian Feldman	reference the "_res" or "h_errno" symbols may experience some
236e07a40f3SBrian Feldman	problems if they are not recompiled.  Single-threaded programs
237e07a40f3SBrian Feldman	should remain unaffected.
238e07a40f3SBrian Feldman
239e07a40f3SBrian Feldman20040225:
240714ae42aSBruce M Simpson	routed has been updated in the base system from the vendor
241714ae42aSBruce M Simpson	sources, routed v2.27, from rhyolite.com. This change means that
242714ae42aSBruce M Simpson	for users who use RIP's MD5 authentication feature, FreeBSD
243714ae42aSBruce M Simpson	-CURRENT's routed is now incompatible with previous versions
244714ae42aSBruce M Simpson	of FreeBSD; however it is now compatible with implementations
245714ae42aSBruce M Simpson	from Sun, Cisco and other vendors.
246714ae42aSBruce M Simpson
247fbd2e692SAndre Oppermann20040224:
248fbd2e692SAndre Oppermann	The tcpcb structure has changed and makes a recompile of libkvm
2495bd7ce0aSJens Schweikhardt	and related userland network utilities necessary.
250fbd2e692SAndre Oppermann
251158b90daSWarner Losh20040222:
252158b90daSWarner Losh	The cdevsw structure has changed in two externally visible ways.
253158b90daSWarner Losh	First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
254158b90daSWarner Losh	Second, the d_version field must be filled in with D_VERSION.
255158b90daSWarner Losh	Drivers outside the tree will need to be updated.
256158b90daSWarner Losh
257b7b1e150SMike Makonnen20040207:
258b7b1e150SMike Makonnen	The /etc/rc.d/ttys script has been removed. It is no longer
259b7b1e150SMike Makonnen	necessary since devfs has been mandatory for some time.
260b7b1e150SMike Makonnen
261aca89ee6SDaniel Eischen20040130:
262aca89ee6SDaniel Eischen	libkse has been renamed back to libpthread and is now the
263aca89ee6SDaniel Eischen	default threads library.  The gcc -pthread option has also
264aca89ee6SDaniel Eischen	been changed to link to libpthread instead of libc_r.  For
265aca89ee6SDaniel Eischen	alpha and sparc64 machines, libkse is not renamed and links
266aca89ee6SDaniel Eischen	are installed so that libpthread points to libc_r.  Until
267aca89ee6SDaniel Eischen	the ports system is updated to handle this change, it is
268aca89ee6SDaniel Eischen	recommended that folks install an /etc/libmap.conf(5) that
269aca89ee6SDaniel Eischen	maps libc_r to libpthread.  If you have any binaries or
270aca89ee6SDaniel Eischen	libraries linked to libkse, then it is also recommended
271aca89ee6SDaniel Eischen	that you map libkse to libpthread.  Anyone that is using
272aca89ee6SDaniel Eischen	nvidia supplied drivers and libraries should use a libmap.conf
273aca89ee6SDaniel Eischen	that maps libpthread to libc_r since their drivers/libraries
274aca89ee6SDaniel Eischen	do not work with libpthread.
275aca89ee6SDaniel Eischen
27668b7b3a9SAlex Dupre20040125:
27768b7b3a9SAlex Dupre	ULE has entered into its probationary period as the default scheduler
27868b7b3a9SAlex Dupre	in GENERIC.  For the average user, interactivity is reported to be
27968b7b3a9SAlex Dupre	better in many cases.  On SMP machines ULE will be able to make more
28068b7b3a9SAlex Dupre	efficient use of the available parallel resources.  If you are not
28168b7b3a9SAlex Dupre	running it now, please switch over, replacing the kernel option
28268b7b3a9SAlex Dupre	SCHED_4BSD with SCHED_ULE.
28368b7b3a9SAlex Dupre
284ff46e0deSWarner Losh20040125:
285ff46e0deSWarner Losh	Move LongRun support out of identcpu.c, where it hardly
286ff46e0deSWarner Losh	belongs, into its own file and make it opt-in, not mandatory,
287ff46e0deSWarner Losh	depending on CPU_ENABLE_LONGRUN config(8) option.
288ff46e0deSWarner Losh
289ce41f4bfSRobert Watson20031213:
290ce41f4bfSRobert Watson	src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
291ce41f4bfSRobert Watson	if the login process is unable to successfully set the
292ce41f4bfSRobert Watson	process credentials to include all groups defined for the
293ce41f4bfSRobert Watson	user.  The current kernel limit is 16 groups; administrators
294ce41f4bfSRobert Watson	may wish to check that users do not have over 16 groups
295ce41f4bfSRobert Watson	defined, or they will be unable to log in.
296ce41f4bfSRobert Watson
297c124fa05SJohn Baldwin20031203:
298c124fa05SJohn Baldwin	The ACPI module has been reactivated.  It is no longer required
299c124fa05SJohn Baldwin	to compile ACPI support into kernels statically.
300c124fa05SJohn Baldwin
3018ad1f5e4SHartmut Brandt20031112:
30230093b05SWarner Losh	The statfs structure has been updated with 64-bit fields to
30330093b05SWarner Losh	allow accurate reporting of multi-terabyte filesystem
30497209ca3SRobert Watson	sizes. You should build world, then build and boot the new kernel
30597209ca3SRobert Watson	BEFORE doing a `installworld' as the new kernel will know about
30697209ca3SRobert Watson	binaries using the old statfs structure, but an old kernel will
30797209ca3SRobert Watson	not know about the new system calls that support the new statfs
3083f631d52SMarcel Moolenaar	structure.
3093f631d52SMarcel Moolenaar	Note that the backwards compatibility is only present when the
3103f631d52SMarcel Moolenaar	kernel is configured with the COMPAT_FREEBSD4 option. Since
3113f631d52SMarcel Moolenaar	even /bin/sh will not run with a new kernel without said option
3123f631d52SMarcel Moolenaar	you're pretty much dead in the water without it. Make sure you
3133f631d52SMarcel Moolenaar	have COMPAT_FREEBSD4!
3143f631d52SMarcel Moolenaar	Running an old kernel after a `make world' will cause programs
3153f631d52SMarcel Moolenaar	such as `df' that do a statfs system call to fail with a bad
3163f631d52SMarcel Moolenaar	system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
3173f631d52SMarcel Moolenaar	that cfsd (ports/security/cfs) needs to be recompiled after
3183f631d52SMarcel Moolenaar	these changes are installed.
31930093b05SWarner Losh
32030093b05SWarner Losh	****************************DANGER*******************************
32130093b05SWarner Losh
32230093b05SWarner Losh	DO NOT make installworld after the buildworld w/o building and
32330093b05SWarner Losh	installing a new kernel FIRST.  You will be unable to build a
32430093b05SWarner Losh	new kernel otherwise on a system with new binaries and an old
32530093b05SWarner Losh	kernel.
32664a18d6fSKirk McKusick
32764a18d6fSKirk McKusick20031112:
3288ad1f5e4SHartmut Brandt	Some netgraph string length constants have been changed. This
3298ad1f5e4SHartmut Brandt	change requires the netgraph kernel modules and all netgraph
3308ad1f5e4SHartmut Brandt	userland components to be in sync. Especially users who require
3318ad1f5e4SHartmut Brandt	netgraph to boot need to make sure to have world and kernel in
3328ad1f5e4SHartmut Brandt	sync before rebooting.
3338ad1f5e4SHartmut Brandt
334c53a5d8fSJohn Baldwin20031111:
335c53a5d8fSJohn Baldwin	Hyperthreading logical CPU's are no longer probed by default
336c53a5d8fSJohn Baldwin	when using the MP Table.  If ACPI is being used, then logical
337c53a5d8fSJohn Baldwin	CPUs will be probed if hyperthreading is enabled in the BIOS.
338c53a5d8fSJohn Baldwin	If ACPI is not being used and hyperthreading is enabled in the
339c53a5d8fSJohn Baldwin	BIOS, logical CPUs can be enabled by building a custom kernel
340c53a5d8fSJohn Baldwin	with the option MPTABLE_FORCE_HTT enabled.
341c53a5d8fSJohn Baldwin
3428bf455a5SJohn Baldwin20031103:
3438bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
3448bf455a5SJohn Baldwin	'device apic'.  The ACPI module has also been temporarily
3452a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
3468bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
3478bf455a5SJohn Baldwin
3489bf40edeSBrooks Davis20031031:
3499bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
3509bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
3519bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
3529bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
3539bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
3549bf40edeSBrooks Davis	reflect this change.
3559bf40edeSBrooks Davis
35647a42c7aSPoul-Henning Kamp20030928:
35747a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
35847a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
3595bd7ce0aSJens Schweikhardt	__FreeBSD_version bumped to 501110.
36047a42c7aSPoul-Henning Kamp
36107105342SMax Khon20030926:
36207105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
36307105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
36407105342SMax Khon
36517dcd026SSam Leffler20030925:
36617dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
36717dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
36817dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
36917dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
37017dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
37117dcd026SSam Leffler
372fedf1d01SBruce M Simpson20030923:
373fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
374fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
375fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
376fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
377fedf1d01SBruce M Simpson
378db38f9cbSJacques Vidrine20030915:
379db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
380db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
381db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
382db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
383db38f9cbSJacques Vidrine
384c09d2c2bSMike Makonnen20030829:
385c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
386c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
387c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
388c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
389c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
390c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
391c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
392c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
393c09d2c2bSMike Makonnen	may or may not exist on your system.
394c09d2c2bSMike Makonnen
39517c159dcSSøren Schmidt20030824:
39617c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
39717c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
398f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
399f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
40017c159dcSSøren Schmidt
401c1f61aa9SDavid E. O'Brien20030819:
402c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
403c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
404c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
405c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
40669f7bcf3SWarner Losh
40738c962e7SNate Lawson20030728:
40838c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
40938c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
41038c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
41138c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
41238c962e7SNate Lawson	so the quirk can be re-enabled.
41338c962e7SNate Lawson
41474111097SWarner Losh20030724:
41574111097SWarner Losh	Problems with entry 20030714 have been corrected and no known issues
41674111097SWarner Losh	with /rescue and -j exist for host systems after this point in time.
41774111097SWarner Losh
418178cf4e9SWarner Losh20030722:
419178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
420178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
421178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
422178cf4e9SWarner Losh	FPU hardware.
423178cf4e9SWarner Losh
424178cf4e9SWarner Losh20030714:
425178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
426178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
427178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
428178cf4e9SWarner Losh	People should report those issues to current@.
429178cf4e9SWarner Losh
430157c629aSWarner Losh20030711:
431157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
4328b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
43305538fa9SWarner Losh	/usr/obj.
434157c629aSWarner Losh
43574111097SWarner Losh20030610:
43674111097SWarner Losh	Remove deprecated locale names and transition period code
43774111097SWarner Losh	for them, finishing switching to the new scheme. Check your
43874111097SWarner Losh	LANG environment variable.
43974111097SWarner Losh
44074111097SWarner Losh20030609:
44174111097SWarner Losh	CCD has been changed to be a fully GEOMified class.  Kernel
44274111097SWarner Losh	and ccdconfig(8) needs to be in sync, this is particularly
44374111097SWarner Losh	important to remember beforehand if your source tree is on
44474111097SWarner Losh	a ccd device.  Consider making a copy of the old ccdconfig
44574111097SWarner Losh	into /boot/kernel.good or wherever you keep your backup
44674111097SWarner Losh	kernel.
44774111097SWarner Losh
44874111097SWarner Losh20030605:
4496cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
4506cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
4516cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
4526cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
4536cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
4546cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
4556cc6353fSMarcel Moolenaar
4566cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
4576cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
4586cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
4596cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
4606cc6353fSMarcel Moolenaar		:
4616cc6353fSMarcel Moolenaar
4626cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
4636cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
4646cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
4656cc6353fSMarcel Moolenaar
46652b47445SMark Murray20030505:
46752b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
46852b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
46952b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
47052b47445SMark Murray
471a26df538SWarner Losh20030502:
472a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
473a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
474a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
475a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
476a26df538SWarner Losh
4774b065e2cSDoug Barton20030501:
4784b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
4794b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
4804b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
4814b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
4824b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
4834b065e2cSDoug Barton	utilizes these old scripts has also been removed.
4844b065e2cSDoug Barton
48581cda3d9SWarner Losh20030423:
48681cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
48781cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
48881cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
48981cda3d9SWarner Losh	have until then to upgrade your kernel before updating
49081cda3d9SWarner Losh	userland.  In general, you should have a userland and
49181cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
49281cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
49381cda3d9SWarner Losh	allowances are made.
49481cda3d9SWarner Losh
49547a657d1SRuslan Ermilov20030329:
49647a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
49747a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
49847a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
49947a657d1SRuslan Ermilov
50047a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
50147a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
50247a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
50347a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
50447a657d1SRuslan Ermilov
50547a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
50647a657d1SRuslan Ermilov	    make cleandir && make obj && \
50747a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
50847a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
50947a657d1SRuslan Ermilov
5105d2af00cSGregory Neil Shapiro20030208:
5115d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
5125d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
5135d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
5145d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
5155d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
5165d2af00cSGregory Neil Shapiro
5175d2af00cSGregory Neil Shapiro20030128:
5189db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
519ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
5209db58771SPoul-Henning Kamp	be removed when convenient.
5219db58771SPoul-Henning Kamp
5228d9b3f57SJake Burkholder20030126:
5238d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
5248d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
5258d9b3f57SJake Burkholder
5261c5efda5SJeff Roberson20030125:
5271c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
5281c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
529ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
5301c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
5311c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
5321c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
5331c5efda5SJeff Roberson
5349d1d64f5SWarner Losh20030115:
5359d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
5369d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
5379d1d64f5SWarner Losh	properly.
5389d1d64f5SWarner Losh
539c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
540c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
541c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
542c9fdb80aSWarner Losh	with NetBSD.
543c9fdb80aSWarner Losh
544161dc364SAlexander Kabaev20021222:
545161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
546161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
547161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
548161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
549161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
550161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
55184cc83efSAlexander Kabaev	rebuilt.
552161dc364SAlexander Kabaev
553fb4c8061SMartin Blapp20021216:
554fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
55589056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
556fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
5579d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
558fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
559fb4c8061SMartin Blapp
56017d47eb3SGiorgos Keramidas20021202:
56117d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
56217d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
56317d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
56417d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
56517d47eb3SGiorgos Keramidas
566a4459294SBill Fenner20021029:
567a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
568a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
569a4459294SBill Fenner	consumers in sync.
570a4459294SBill Fenner
571fc8c157fSWarner Losh20021024:
572c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
573c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
574c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
575c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
576c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
577c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
578c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
579c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
58069f7bcf3SWarner Losh
581fd9e8bdaSAndrew Gallatin20021023:
582fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
583fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
584fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
585fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
586fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
587fd9e8bdaSAndrew Gallatin
588fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
589fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
590fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
591fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
592fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
593fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
594fd9e8bdaSAndrew Gallatin
595f8a4c901SWarner Losh20020831:
596f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
597f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
598f8a4c901SWarner Losh	programs and libraries need to be recompiled.
599f8a4c901SWarner Losh
600f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
601f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
602f8a4c901SWarner Losh
603c2248fa2SJens Schweikhardt20020827:
604c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
605c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
606c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
607c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
608c2248fa2SJens Schweikhardt
6090d533e43SRuslan Ermilov20020815:
6100d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
6110d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
6120d533e43SRuslan Ermilov	again.
6130d533e43SRuslan Ermilov
61433c1de7dSRuslan Ermilov20020729:
61533c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
61633c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
61733c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
61833c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
61933c1de7dSRuslan Ermilov
6202b877facSJulian Elischer20020702:
6212b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
6222b877facSJulian Elischer	There are still some minor problems with some signals but the
6232b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
6242b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
6252b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
6262b877facSJulian Elischer
62706596d37SWarner Losh20020701:
62806596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
62906596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
63006596d37SWarner Losh	GNOME.
63106596d37SWarner Losh
63295ba4330SJacques Vidrine20020511:
63395ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
63495ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
63595ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
63695ba4330SJacques Vidrine	with the set-user-ID bit set.
63795ba4330SJacques Vidrine
638a81da3c9SDavid E. O'Brien20020510:
639f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
640f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
6414b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
642f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
643f50caf6fSDavid E. O'Brien
644f50caf6fSDavid E. O'Brien20020510:
645a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
646a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
647a81da3c9SDavid E. O'Brien	and then do a cvs update.
648a81da3c9SDavid E. O'Brien
649528a0ef5SJacques Vidrine20020421:
650528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
651528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
652528a0ef5SJacques Vidrine
65385aa5a2eSGregory Neil Shapiro20020404:
65485aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
65585aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
65685aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
65785aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
65885aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
65985aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
66085aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
66185aa5a2eSGregory Neil Shapiro
6628f1e4358SRuslan Ermilov20020403:
6638f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
6648f1e4358SRuslan Ermilov
6652292c02eSWarner Losh20020315:
6662292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
6672292c02eSWarner Losh
66869f7bcf3SWarner Losh20020225:
66969f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
67069f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
67169f7bcf3SWarner Losh
6728f35c493SWarner Losh20020217:
6738f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
6748f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
6758f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
6768f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
6778f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
6788f35c493SWarner Losh
679835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
680835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
681835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
682835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
683835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
684835284beSWarner Losh	and group must be merged from src/etc/group and
685835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
686835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
687835284beSWarner Losh	mergemaster before this will work if you are updating from a
688835284beSWarner Losh	very old version of current.  The updating recipe has changed
689835284beSWarner Losh	as of this date.
690835284beSWarner Losh
691fa9401c1SWarner Losh20020112:
692fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
693fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
694fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
695fa9401c1SWarner Losh	you have local modifications, you can use
696fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
697fa9401c1SWarner Losh	/etc/pam.d.
698fa9401c1SWarner Losh
699fa9401c1SWarner Losh	Please see the following url for more details:
700fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
70147d0d01fSWarner Losh20011229:
70247d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
70347d0d01fSWarner Losh	networkfs_types, please note that it has changed
70447d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
70547d0d01fSWarner Losh
706514318a8SWarner Losh20011220:
707514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
708514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
709514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
710514318a8SWarner Losh	own.  All the accumulated features and bug fixes of the i4b
711514318a8SWarner Losh	version have now been merged back into the base system's
712514318a8SWarner Losh	version now.  The only user-visible change resulting from this
713514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
714514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
715514318a8SWarner Losh	as well.  (There has never been rc file support for
716514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
717514318a8SWarner Losh	reverted by the time the changes are MFCed.)
718514318a8SWarner Losh
719514318a8SWarner Losh20011215:
720514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
721514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
722514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
723514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
724514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
725514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
726514318a8SWarner Losh	will need to be customized then for `odd' densities using
727514318a8SWarner Losh	fdcontrol(8).
728514318a8SWarner Losh
7292d22e2bfSWarner Losh20011209:
7302d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
7312d22e2bfSWarner Losh	and truss(1) now works again.
7322d22e2bfSWarner Losh
7339e0428e2SWarner Losh20011207:
7349e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
7359e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
7369e0428e2SWarner Losh	see
7379e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
7389e0428e2SWarner Losh	for details.
7399e0428e2SWarner Losh
7409bab8c59SWarner Losh20011204:
7419bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
7429bab8c59SWarner Losh	kernel and burncd to be in sync.
7439bab8c59SWarner Losh
744e57d8b01SWarner Losh20011203:
745e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
746e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
747e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
748e57d8b01SWarner Losh	not there already.
749e57d8b01SWarner Losh
750e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
751e57d8b01SWarner Losh	until the issue has been resolved.
752e57d8b01SWarner Losh
753b001d36fSJacques Vidrine20011202:
754b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
755b001d36fSJacques Vidrine	patched.
756b001d36fSJacques Vidrine
7574b676ec1SWarner Losh20011126:
7584b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
7595ebbf43eSWarner Losh	after this date.  You need to do this only once.
7604b676ec1SWarner Losh
761d961e462SWarner Losh20011103:
762d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
763d961e462SWarner Losh	edges may be left, but for the most part things should be
7644b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
765d961e462SWarner Losh
766d961e462SWarner Losh20011030:
767d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
768d961e462SWarner Losh	choppy waves in the upgrade process.
769d961e462SWarner Losh
7701fe003b6SWarner Losh20011030:
771a4b6fda0SWarner Losh	The asr driver problem has been resolved.
7721fe003b6SWarner Losh
7731fe003b6SWarner Losh20011027:
7741fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
7751fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
7761fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
7771fe003b6SWarner Losh	try to use from this date forward.
7781fe003b6SWarner Losh
7791fe003b6SWarner Losh20011025:
7801fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
7811fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
7821fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
7831fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
7841fe003b6SWarner Losh	TARGET_ARCH=i386.
7851fe003b6SWarner Losh
786d05f9643SWarner Losh20011001:
787d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
788d05f9643SWarner Losh	You must recompile both the kernel and userland applications
789d05f9643SWarner Losh	at the same time.
790d05f9643SWarner Losh
79158970f85SWarner Losh20010929:
79258970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
79358970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
79458970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
79558970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
7969d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
79758970f85SWarner Losh
79858970f85SWarner Losh20010927:
79958970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
80058970f85SWarner Losh	To disable ACPI you can add
80166ff0e67SMax Khon		hint.acpi.0.disabled="1"
80258970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
80358970f85SWarner Losh	loader "ok" prompt).
80458970f85SWarner Losh
80558970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
80658970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
80758970f85SWarner Losh	file and not list acpi in that list.
808378f4486SAlfred Perlstein
8095119d237SWarner Losh20010924:
8105119d237SWarner Losh	The buildworld has been fixed.  You may need to install
8115119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8128b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
8138b039fffSWarner Losh	get them installed on every installworld, or execute the
8148b039fffSWarner Losh	following to get them installed only once:
8158b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
81658970f85SWarner Losh		make all install
8178b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
8185119d237SWarner Losh
8193c293725SWarner Losh20010919:
8203c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
8213c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
8223c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
823772730c7SWarner Losh	workaround is to add
8243c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
8253c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
8263c293725SWarner Losh	can be removed afterwards.
8273c293725SWarner Losh
8283c293725SWarner Losh	A proper fix to the buildworld target is needed.
8293c293725SWarner Losh
8303c293725SWarner Losh20010918:
8313c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
8323c293725SWarner Losh	NFS may be unstable after this date.
8333c293725SWarner Losh
8343c293725SWarner Losh20010912:
8353c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
8363c293725SWarner Losh	the kernel.  While a few problems were introduced in the
8373c293725SWarner Losh	initial commit, most of the major ones have been found and
8383c293725SWarner Losh	corrected.
8393c293725SWarner Losh
8403c293725SWarner Losh20010901:
8413c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
8423c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
8433c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
8443c293725SWarner Losh	have been rectified around this date.
8453c293725SWarner Losh
84698b17b95SWarner Losh20010823:
84798b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
84898b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
84998b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
85098b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
85198b17b95SWarner Losh 	sure that user or group bind has read (and not write)
85298b17b95SWarner Losh 	permission for your name server configuration and that it
85398b17b95SWarner Losh 	has read and write permission for your slave zone files and
85498b17b95SWarner Losh 	directory.
85598b17b95SWarner Losh
85698b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
85798b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
85898b17b95SWarner Losh
85998b17b95SWarner Losh 		named_flags=
86098b17b95SWarner Losh
8617b9786edSMark Murray20010709:
8627b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
8637b9786edSMark Murray	the ability of the shared library major number to handle.
8647b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
8657b9786edSMark Murray	solution is to rebuild those ports.
8667b9786edSMark Murray
8671d28950eSWarner Losh20010628:
8681d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
8691d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
8701d28950eSWarner Losh
871e72fd46aSWarner Losh20010625:
87298b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
87398b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
87498b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
87598b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
87698b17b95SWarner Losh	IRQ configuration needs more safety belts.
87716de1a07SWarner Losh
8780d415dffSWarner Losh20010617:
879e72fd46aSWarner Losh	Softupdates problems have been corrected.
8800d415dffSWarner Losh
8810d415dffSWarner Losh20010614:
8820d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
8830d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
8840d415dffSWarner Losh	kernel building methods.
8850d415dffSWarner Losh
8868b9959adSWarner Losh20010613:
8878b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
8888b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
889e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
890e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
8918b9959adSWarner Losh
892e72fd46aSWarner Losh20010613:
8938b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
894e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
895e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
8968b9959adSWarner Losh
8970d415dffSWarner Losh20010612:
8980d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
8990d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
9000d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
9010d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
9020d415dffSWarner Losh	until this bug is fixed.
9030d415dffSWarner Losh
904e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
905e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
906ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
907e72fd46aSWarner Losh
9080d415dffSWarner Losh20010610:
9090d415dffSWarner Losh	Locale names have changed to match other systems better.
9100d415dffSWarner Losh
9116ccdb5e4SWarner Losh20010604:
9126ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
9136ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
9146ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
9153590182eSWarner Losh	Interrupt storms look a lot like a hang.
9163590182eSWarner Losh
9173590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
9183590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
9193590182eSWarner Losh	it is).
9203590182eSWarner Losh
9213590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
9223590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
9233590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
9243590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
9256ccdb5e4SWarner Losh
9260bc62786SWarner Losh20010530:
9270bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
9280bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
9290bc62786SWarner Losh	a limited time.  If you see
9300bc62786SWarner Losh
9310bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
9320bc62786SWarner Losh
9330bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
9340bc62786SWarner Losh	COPY=-C.
9350bc62786SWarner Losh
93668a38c6cSWarner Losh20010525:
937b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
938c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
939c4f4a728SWarner Losh	definitely is in bad shape.
94068a38c6cSWarner Losh
941ed0f29caSWarner Losh20010521:
942ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
943ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
944ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
945ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
946ed0f29caSWarner Losh	is
947ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
948ed0f29caSWarner Losh
94980c16af9SWarner Losh20010520:
95068a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
95180c16af9SWarner Losh
95280c16af9SWarner Losh20010519:
95380c16af9SWarner Losh	pccard has had much reorganizational work done to it over
95480c16af9SWarner Losh	the past few days.  Everything should still work, but if
95580c16af9SWarner Losh	not, please contact imp@freebsd.org.
95680c16af9SWarner Losh
957a45f2d05SWarner Losh20010517:
958a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
959a45f2d05SWarner Losh	userland at the same time.
960a45f2d05SWarner Losh
961a45f2d05SWarner Losh20010517:
962a45f2d05SWarner Losh	New ncurses imported.
963a45f2d05SWarner Losh
9642988afcaSWarner Losh20010512:
9652988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
9662988afcaSWarner Losh	will be the only way to go starting July 1.
9672988afcaSWarner Losh
9681a33dba7SWarner Losh20010504:
9691a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
9701a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
9711a33dba7SWarner Losh
97209946a51SWarner Losh20010502:
97309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
97409946a51SWarner Losh
97509946a51SWarner Losh20010501:
97609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
97709946a51SWarner Losh
97809946a51SWarner Losh20010430:
979a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
98009946a51SWarner Losh	go back in the water.
98109946a51SWarner Losh
98209946a51SWarner Losh20010429:
98309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
98409946a51SWarner Losh	this date, but before the correction date.
98509946a51SWarner Losh
98691dd3b53SWarner Losh20010423:
98791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
98891dd3b53SWarner Losh
98991dd3b53SWarner Losh20010411:
99091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
99191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
99291dd3b53SWarner Losh	Update only if you understand that you must not use the old
99391dd3b53SWarner Losh	fsck with the new kernel ever.
99491dd3b53SWarner Losh
995933b3269SWarner Losh20010330:
996933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
997c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
998933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
999933b3269SWarner Losh
1000933b3269SWarner Losh20010319:
1001933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
1002933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
1003933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
1004f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
100509946a51SWarner Losh
100609946a51SWarner Losh20010315:
100709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1008ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
100909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
1010933b3269SWarner Losh
1011933b3269SWarner Losh20010312:
1012933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
1013933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
1014933b3269SWarner Losh
1015933b3269SWarner Losh20010312:
1016933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
1017933b3269SWarner Losh	instead of ad-hoc.
1018933b3269SWarner Losh
1019933b3269SWarner Losh20010310:
1020f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
1021933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
1022933b3269SWarner Losh	ssh might not work if you don't.
1023933b3269SWarner Losh
102462353691SWarner Losh20010303:
102562353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
102662353691SWarner Losh	which means that you must include the miibus in your kernel if
102762353691SWarner Losh	you use the ed driver.
102862353691SWarner Losh
1029d325cf65SWarner Losh20010220:
1030d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
1031d325cf65SWarner Losh	safe to go back into the water.
1032d325cf65SWarner Losh
1033024daae6SWarner Losh20010211:
1034024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
1035024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
1036024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
1037024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
1038024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
1039024daae6SWarner Losh
1040024daae6SWarner Losh	To get to the new system, you'll need to use the following
1041024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
1042024daae6SWarner Losh	don't have to move this to the updating section.
1043024daae6SWarner Losh
1044024daae6SWarner Losh	To get around the installworld problem, do:
1045024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
1046024daae6SWarner Losh		# make install
1047024daae6SWarner Losh		# cd /usr/src
1048024daae6SWarner Losh		# make installworld
1049024daae6SWarner Losh	If that doesn't work, then try:
1050024daae6SWarner Losh		# make -k installworld
1051024daae6SWarner Losh		# make installworld
1052024daae6SWarner Losh
1053024daae6SWarner Losh20010207:
1054024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
1055024daae6SWarner Losh	do not include devfs in your kernel as problems result.
1056024daae6SWarner Losh
1057024daae6SWarner Losh20010205:
10587595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1059024daae6SWarner Losh	Remove them from your config.
1060024daae6SWarner Losh
10611e159248SWarner Losh20010122:
10621e159248SWarner Losh	****************************** WARNING ******************************
10631e159248SWarner Losh			buildkernel has been changed slightly
10641e159248SWarner Losh	****************************** WARNING ******************************
10651e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
10661e159248SWarner Losh	should update your scripts and make.conf accordingly.
10671e159248SWarner Losh
10681e159248SWarner Losh20010119:
10691e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
10701e159248SWarner Losh	This requires a new config to build correctly.
10711e159248SWarner Losh
1072aac7dfeaSWarner Losh20010116:
1073ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
1074aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
1075aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
1076aac7dfeaSWarner Losh
1077aac7dfeaSWarner Losh20010110:
1078aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
1079aac7dfeaSWarner Losh
1080aac7dfeaSWarner Losh20010102:
1081aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
1082aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
1083aac7dfeaSWarner Losh
108463c90c9eSWarner Losh20010101:
108563c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
108663c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
10875fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
108863c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
108963c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
109063c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
109163c90c9eSWarner Losh	might have been ignored by the -k option.
109263c90c9eSWarner Losh
10935fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
10945fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
10955fd2a895SWarner Losh	of this working.
10965fd2a895SWarner Losh
1097aac7dfeaSWarner Losh20001228:
1098aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
1099ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
1100aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
1101aac7dfeaSWarner Losh
1102de2bcc63SWarner Losh20001218:
1103de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
1104de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
1105de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
1106de2bcc63SWarner Losh	cards will not be recognized without it.
1107de2bcc63SWarner Losh
1108960773f7SWarner Losh20001205:
1109960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
1110960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
1111960773f7SWarner Losh	adding the following in pam.conf:
1112960773f7SWarner Losh
1113960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
1114960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
1115960773f7SWarner Losh	sshd    session required        pam_permit.so
1116960773f7SWarner Losh
11170acc635eSWarner Losh20001031:
11180acc635eSWarner Losh	cvs updated to 1.11.
11190acc635eSWarner Losh
11200acc635eSWarner Losh20001020:
11210acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
11220acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
11230acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
11240acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
11250acc635eSWarner Losh	workaround.
11260acc635eSWarner Losh
11270acc635eSWarner Losh20001010:
11280acc635eSWarner Losh	****************************** WARNING ******************************
11290acc635eSWarner Losh				Sendmail has been updated.
11300acc635eSWarner Losh	****************************** WARNING ******************************
11310acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
11320acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
11330acc635eSWarner Losh	  is set.
11340acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
11350acc635eSWarner Losh	  commands.
11360acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
11370acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
11380acc635eSWarner Losh	  in /usr/share/sendmail/cf.
11390acc635eSWarner Losh	o sendmail.cw changed to local-host-names
11400acc635eSWarner Losh
11410acc635eSWarner Losh	More details can be found at
11420acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
11430acc635eSWarner Losh
11446e98a146SWarner Losh20001009:
11456e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
11466e98a146SWarner Losh	your entire ports tree, or you will have problems.
11476e98a146SWarner Losh
11486e98a146SWarner Losh20001006:
1149685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
11506e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
11516e98a146SWarner Losh	/usr/bin/miniperl.
11526e98a146SWarner Losh
1153073113a4SWarner Losh20001005:
1154073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
1155685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
1156073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
1157073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
1158073113a4SWarner Losh	tree for anything to work.
1159073113a4SWarner Losh
11600acc635eSWarner Losh20000928:
11610acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
11620acc635eSWarner Losh
1163be3885b3SWarner Losh20000916:
1164be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1165be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
1166be3885b3SWarner Losh	same time as your kernel.
1167be3885b3SWarner Losh
116876ec9675SWarner Losh20000914:
116976ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
117076ec9675SWarner Losh	include the device will cause suspended laptops losing time
117176ec9675SWarner Losh	when they resume.  Include
117276ec9675SWarner Losh		device		pmtimer
117376ec9675SWarner Losh	in your config file and
117401b9a434SWarner Losh		hint.pmtimer.0.at="isa"
117576ec9675SWarner Losh	to your /boot/device.hints file.
117676ec9675SWarner Losh
1177f4865386SMark Murray20000911:
1178f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
1179f4865386SMark Murray	rather than an option. The supplied kernel config files have
1180f4865386SMark Murray	been updated. You will need to do something similar in your
1181f4865386SMark Murray	own kernel config file.
1182f4865386SMark Murray	Remove:
1183f4865386SMark Murray		options		RANDOMDEV
1184f4865386SMark Murray	Add:
1185f4865386SMark Murray		device		random
1186f4865386SMark Murray	If you prefer to load the loadable module, you need to do
1187f4865386SMark Murray	nothing.
1188f4865386SMark Murray
1189d594498fSWarner Losh20000909:
1190d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
1191d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
1192d594498fSWarner Losh	reflect this if you load this module at boot time.
1193d594498fSWarner Losh	The line should read:
1194d594498fSWarner Losh		random_load="YES"
1195d594498fSWarner Losh
11960deb7ddcSWarner Losh20000907:
11970deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
119816eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
119916eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
120016eb772dSWarner Losh	sure you don't have model loading problems which might at
120116eb772dSWarner Losh	first blush appear related to SMP.
120252bf24e7SWarner Losh
12035a01880bSWarner Losh20000906:
12045a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
12055a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
12065a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
12075a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
12085a01880bSWarner Losh	don't have one, and you have host.conf.
12095a01880bSWarner Losh
12102b41163cSWarner Losh20000905:
121138d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
121238d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
121338d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
121438d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
121538d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
121638d6ecd2SWarner Losh
121738d6ecd2SWarner Losh20000905:
12188aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
12198aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
12208aab4bc7SWarner Losh	is /boot/kernel.
12218aab4bc7SWarner Losh
12228aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
122338d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
122438d6ecd2SWarner Losh	installkernel/installworld dance.
12252b41163cSWarner Losh
1226d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
1227d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
1228d594498fSWarner Losh	modules in that directory instead of finding them in the correct
1229d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
1230d594498fSWarner Losh	is that the linux module crashes your machine after the update.
1231d594498fSWarner Losh
1232d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
1233d594498fSWarner Losh		mv /modules.old /boot/kernel.old
1234d594498fSWarner Losh		chflags noschg /kernel.old
1235d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
1236d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
1237d594498fSWarner Losh	fi
1238d594498fSWarner Losh
1239c22a309cSWarner Losh20000904:
1240c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
1241c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
1242c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
1243c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
1244c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
1245c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
1246c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
1247c22a309cSWarner Losh	is not likely to be generated.
1248c22a309cSWarner Losh
1249fdb9f54dSWarner Losh20000825:
1250fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
12519c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
12529c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
12539c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
12549c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
12559c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
12569c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
12579c1a7444SWarner Losh	kernel.
12589c1a7444SWarner Losh
12599c1a7444SWarner Losh20000821:
12609c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
12619c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
12629c1a7444SWarner Losh	/boot/loader.conf.
1263fdb9f54dSWarner Losh
12648f250aa7SWarner Losh20000812:
12655da0d091SWarner Losh	suidperl is now always built and installed on the system, but
12665da0d091SWarner Losh	with permissions of 511.  If you have applications that use
12675da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
12685da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
12695da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
12705da0d091SWarner Losh	will fix this until the next build.
12715da0d091SWarner Losh
12725da0d091SWarner Losh20000812:
12738f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
12748f250aa7SWarner Losh	visible changes that may immediately affect your configuration
12758f250aa7SWarner Losh	include:
12768f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
12778f250aa7SWarner Losh	- newaliases limited to root and trusted users
12788f250aa7SWarner Losh	- MSA port (587) turned on by default
12798f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
12808f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
12818f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
12828f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
12838f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
12848f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
12858f250aa7SWarner Losh
128671c38472SWarner Losh20000810:
128771c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
128871c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
128971c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
129071c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
129171c38472SWarner Losh	specific use for it.
129271c38472SWarner Losh
129371c38472SWarner Losh20000729:
129471c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
129571c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
129671c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
129771c38472SWarner Losh	afterwards (unless the variables already are set, of course):
129871c38472SWarner Losh		# Enable network daemons for user convenience.
129971c38472SWarner Losh		inetd_enable="YES"
130071c38472SWarner Losh		portmap_enable="YES"
130171c38472SWarner Losh		sendmail_enable="YES"
130271c38472SWarner Losh
130371c38472SWarner Losh20000728:
130471c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
130571c38472SWarner Losh	will need to change that to nullfs_load="YES".
130671c38472SWarner Losh
13071dece4a9SWarner Losh20000728:
13081dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
13091dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
13101dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
13111dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
13121dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
13131dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
13141dece4a9SWarner Losh	to /MYKERNEL.
13151dece4a9SWarner Losh
1316409e887cSWarner Losh20000711:
1317409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
1318409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
1319409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
1320409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
1321409e887cSWarner Losh	for details on potential problems that you might have and how
1322409e887cSWarner Losh	to get around them.
1323409e887cSWarner Losh
1324409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
1325409e887cSWarner Losh	clauses above, you needn't worry.
1326409e887cSWarner Losh
1327409e887cSWarner Losh20000711:
1328409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1329409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1330409e887cSWarner Losh	in the number of changed programs the first time when you run
1331409e887cSWarner Losh	mergemaster to get a new /etc/security.
1332409e887cSWarner Losh
1333673d13f2SWarner Losh20000710:
1334673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1335673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1336673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1337673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1338673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1339673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1340673d13f2SWarner Losh	errors. (see below, 20000624).
1341673d13f2SWarner Losh
1342bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
13431dece4a9SWarner Losh
1344673d13f2SWarner Losh20000709:
1345c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1346c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1347c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1348673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1349673d13f2SWarner Losh
1350e98e26cdSWarner Losh20000706:
1351e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1352e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1353e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1354f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1355e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
13562c021c6cSMark Ovens	interim if needed.
1357e98e26cdSWarner Losh
1358e98e26cdSWarner Losh20000705:
1359e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1360e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1361e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1362e98e26cdSWarner Losh	details.
1363e98e26cdSWarner Losh
1364c373950eSWarner Losh20000704:
13652f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
13662f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
13672f961bc8SWarner Losh
13682f961bc8SWarner Losh20000704:
1369c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1370c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1371c373950eSWarner Losh	rc.d scripts that haven't been updated.
1372c373950eSWarner Losh
137327dc3a2bSWarner Losh20000630:
137427dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
137527dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
137627dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
137727dc3a2bSWarner Losh
1378b8c215acSWarner Losh20000625:
1379b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
138027dc3a2bSWarner Losh	system installed in order to build the system and kernel.
138127dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
138227dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
138327dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
138427dc3a2bSWarner Losh	were required.  You should check with the latest collections
138527dc3a2bSWarner Losh	to make sure that these haven't changed.
1386b8c215acSWarner Losh
13877b990719SWarner Losh20000624:
13887b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
13897b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
13907b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
13911a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
13927b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
13937b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
13947b990719SWarner Losh	date to the completion of the work.
13957b990719SWarner Losh
139627dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
139727dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
139827dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
139927dc3a2bSWarner Losh	recreate the random and urandom devices.
140027dc3a2bSWarner Losh
140181e54c50SWarner Losh20000622:
140281e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
140381e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
140481e54c50SWarner Losh	that used to be required when updating.
140581e54c50SWarner Losh
140639943833SWarner Losh20000621:
14072c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
14082a2f33fbSDaniel Baker	the config file update procedure.
14092a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1410c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
141159df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
141259df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
141339943833SWarner Losh
1414290f9ad8SWarner Losh20000620:
1415290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1416290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1417290f9ad8SWarner Losh	that workaround will no longer be required.
1418290f9ad8SWarner Losh
141990fb6346SWarner Losh20000615:
142090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
142190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
142290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
142390fb6346SWarner Losh	devices.
142490fb6346SWarner Losh
1425f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1426f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1427f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1428f75f65bbSWarner Losh	may work).
1429f75f65bbSWarner Losh
1430ba26da8eSWarner Losh20000612:
1431ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1432290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1433c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1434290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1435f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1436f54a3542SWarner Losh	NEWCARD for examples of the new format.
1437290f9ad8SWarner Losh
14389698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
14399698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
14409698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
14419698f2c0SWarner Losh	in it.
1442bbcc5149SWarner Losh
1443d65850ebSWarner Losh20000522:
1444ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1445d65850ebSWarner Losh	building a kernel after this point is advised that they need
1446d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1447d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1448d65850ebSWarner Losh
1449d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1450d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1451d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1452d9583a00SWarner Losh	is resolved.
1453d9583a00SWarner Losh
14548039cedeSWarner Losh20000513:
14558039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
14568039cedeSWarner Losh
1457d65850ebSWarner Losh20000510:
14588039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
14598039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
14608039cedeSWarner Losh	is requires for the boot blocks to build properly.
14618039cedeSWarner Losh
14628039cedeSWarner Losh20000503:
14638039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
14648039cedeSWarner Losh	is now available.
14658039cedeSWarner Losh
1466d65850ebSWarner Losh20000502:
1467d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1468d65850ebSWarner Losh	connected to the kernel building instead.
1469d65850ebSWarner Losh
1470be149406SNik Clayton20000427:
14718039cedeSWarner Losh	You may need to build gperf
14728039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
14738039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
14748039cedeSWarner Losh	an option only in -current.
14758039cedeSWarner Losh
14762b8dd5f4SWarner Losh20000417:
14772b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1478f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
14792b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
14802b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
14812c021c6cSMark Ovens	before you reboot, you'll need to issue:
14822b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
14832b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
14842b8dd5f4SWarner Losh
14858d9f1945SWarner Losh20000320:
14862b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
14872b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
14882b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1489ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
14902b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
14918d9f1945SWarner Losh
1492f8ab1dd6SWarner Losh20000319:
1493f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1494f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1495f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1496f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1497f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1498f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1499f8ab1dd6SWarner Losh
150019cada77SWarner Losh20000318:
1501f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
150219cada77SWarner Losh	Large kernel changes are being committed and are in the
150319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
150419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
150519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
150619cada77SWarner Losh	that you are loading are up to date.
1507ba228352SWarner Losh
150819cada77SWarner Losh20000315:
15096d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
15106d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
15116d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
15126d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
15136d23c382SWarner Losh	boot.
15146d23c382SWarner Losh
15156d23c382SWarner Losh20000315:
151619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
151719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
151857199806SWarner Losh
1519dc0dbf5cSWarner LoshCOMMON ITEMS:
1520dc0dbf5cSWarner Losh
1521a24eff53SWarner Losh	General Notes
1522a24eff53SWarner Losh	-------------
1523a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1524a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1525a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1526a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1527a24eff53SWarner Losh	or several minor releases, or when several months have passed
1528a24eff53SWarner Losh	on the -current branch).
1529a24eff53SWarner Losh
15305780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
15315780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
15325780f3baSWarner Losh	environment when searching for values for global variables.
15335780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
15345780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
15355780f3baSWarner Losh	page for more details.
15365780f3baSWarner Losh
1537dc0dbf5cSWarner Losh	To build a kernel
1538dc0dbf5cSWarner Losh	-----------------
1539ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1540f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1541ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1542282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1543282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1544dc0dbf5cSWarner Losh
1545ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1546ba01eb20SWarner Losh	--------------------------------------------------------------
15470fbd2da9SKen Smith	This assumes you are already running a 5.X system.  Replace
15480fbd2da9SKen Smith	${arch} with the architecture of your machine (e.g. "i386",
15490fbd2da9SKen Smith	"alpha", "amd64", "ia64", "pc98", "sparc64", etc).
15500fbd2da9SKen Smith
15510fbd2da9SKen Smith	cd src/sys/${arch}/conf
155247d0d01fSWarner Losh	config KERNEL_NAME_HERE
15530fbd2da9SKen Smith	cd ../compile/KERNEL_NAME_HERE
1554ba01eb20SWarner Losh	make depend
1555ba01eb20SWarner Losh	make
1556ba01eb20SWarner Losh	make install
1557ba01eb20SWarner Losh
1558ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1559ba01eb20SWarner Losh
1560ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1561ba01eb20SWarner Losh	-----------------------------------------------------------
156263cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
156363cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
156463cb445eSWarner Losh
1565f643de42SWarner Losh	<make sure you have good level 0 dumps>
156663cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
156763cb445eSWarner Losh	make buildworld
156863cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
156963cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
157063cb445eSWarner Losh							[1]
157163cb445eSWarner Losh	<reboot in single user>				[3]
15728633bbeaSBrooks Davis	/etc/rc.d/preseedrandom				[10]
157363cb445eSWarner Losh	mergemaster -p					[5]
157463cb445eSWarner Losh	make installworld
157563cb445eSWarner Losh	mergemaster					[4]
157663cb445eSWarner Losh	<reboot>
157763cb445eSWarner Losh
1578759f0aefSWarner Losh
1579f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1580f27b1fceSJoseph Koshy	--------------------------------------------------
1581f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1582f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1583f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1584f27b1fceSJoseph Koshy	# size.
1585f27b1fceSJoseph Koshy
1586f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1587f27b1fceSJoseph Koshy	<boot into -stable>
1588f27b1fceSJoseph Koshy	make buildworld
1589f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1590f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1591f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1592f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1593f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1594f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1595f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1596f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1597f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1598f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1599f27b1fceSJoseph Koshy	<reboot into current>
1600f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1601f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1602f27b1fceSJoseph Koshy 	<reboot>
1603f27b1fceSJoseph Koshy
1604f27b1fceSJoseph Koshy
1605f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1606f27b1fceSJoseph Koshy	----------------------------------------------
16075c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
16085c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
16095c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
16105c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1611ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1612f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1613f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1614f643de42SWarner Losh	# space on /.
1615f643de42SWarner Losh
1616f643de42SWarner Losh	<make sure you have good level 0 dumps>
1617fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
161821c075eaSWarner Losh	make buildworld					[9]
1619c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1620802fc49dSBrian Feldman	cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1621be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1622802fc49dSBrian Feldman	cd sys/boot ; make STRIP="" install			[6]
1623fc8c157fSWarner Losh							[1]
1624fc8c157fSWarner Losh	<reboot in single user>				[3]
1625802fc49dSBrian Feldman	/usr/src/etc/rc.d/preseedrandom				[10]
1626835284beSWarner Losh	mergemaster -p					[5]
1627f8a4c901SWarner Losh	rm -rf /usr/include/g++
1628ba26da8eSWarner Losh	make installworld
1629802fc49dSBrian Feldman	mergemaster -i					[4]
1630ba26da8eSWarner Losh	<reboot>
1631ba26da8eSWarner Losh
1632fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1633fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1634fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1635fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1636fdb9f54dSWarner Losh	the UPDATING entries.
1637ba26da8eSWarner Losh
16381dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
16391dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
16401dece4a9SWarner Losh	your sources that you have read and understood all the recent
16411dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
16421dece4a9SWarner Losh	much fewer pitfalls.
16431dece4a9SWarner Losh
1644134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1645134d2e86SWarner Losh	should disable them at this point so they don't crash your
1646134d2e86SWarner Losh	system on reboot.
1647134d2e86SWarner Losh
16489c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
16499c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
16509c1a7444SWarner Losh	configuration.
16519c1a7444SWarner Losh
1652ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1653ee6e1fc3SWarner Losh		fsck -p
1654ee6e1fc3SWarner Losh		mount -u /
1655ee6e1fc3SWarner Losh		mount -a
1656ee6e1fc3SWarner Losh		cd /usr/src
165747d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1658f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1659f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1660b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1661b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1662b705ae10SWarner Losh	be ignored while you proceed to the next step.
1663ee6e1fc3SWarner Losh
1664a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1665a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1666a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1667a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1668a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1669a6cd4f9dSWarner Losh	for potential gotchas.
1670a6cd4f9dSWarner Losh
1671835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1672835284beSWarner Losh	you may need to do this if you get unknown user in the following
1673835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1674835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1675835284beSWarner Losh	install) after the buildworld before this step if you last updated
1676835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1677835284beSWarner Losh
1678bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1679bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1680bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1681bd79cf40SWarner Losh		ok unload
1682bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1683bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1684bd79cf40SWarner Losh	described here.
1685fc8c157fSWarner Losh
1686fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1687fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1688fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1689fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1690fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1691fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1692fc8c157fSWarner Losh
1693c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1694c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1695c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1696c74fe6afSWarner Losh	that is hard to boot to recover.
1697c74fe6afSWarner Losh
169821c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
1699802fc49dSBrian Feldman	cvs prune empty directories. Also, if CPUTYPE is defined in your
1700802fc49dSBrian Feldman	/etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1701802fc49dSBrian Feldman	operator, so that buildworld can override the CPUTYPE if it needs to.
1702802fc49dSBrian Feldman	In case you would like to avoid installing new packages of everything,
1703802fc49dSBrian Feldman	you might want to uncomment the "COMPAT4X=	YES" entry, so that 4.x
1704802fc49dSBrian Feldman	compatibility libraries are build which should allow you to continue
1705802fc49dSBrian Feldman	using your existing software for a while.
17068633bbeaSBrooks Davis
17078633bbeaSBrooks Davis	[10] In order to create temporary files, /dev/random must be
17088633bbeaSBrooks Davis	initialized by feeding data into it.  /etc/rc.d/preseedrandom
17098633bbeaSBrooks Davis	takes care of this.
1710dc0dbf5cSWarner LoshFORMAT:
1711dc0dbf5cSWarner Losh
1712f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
17131fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1714f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1715f8ab1dd6SWarner Loshprevious releases if your system is older than this.
17161fc1a0dcSWarner Losh
1717e72fd46aSWarner LoshCopyright information:
1718e72fd46aSWarner Losh
17199698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1720e72fd46aSWarner Losh
1721772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1722772730c7SWarner Loshmodification, in full or in part, in any form or format of this
17239698f2c0SWarner Loshdocument are permitted without further permission from the author.
1724e72fd46aSWarner Losh
1725e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1726e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1727e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1728e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1729e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1730e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1731e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1732e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1733e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1734e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1735e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1736e72fd46aSWarner Losh
1737e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1738e72fd46aSWarner Loshauthor a beer.
1739e72fd46aSWarner Losh
174022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1741772730c7SWarner Loshthis document.
1742772730c7SWarner Losh
174397d92980SPeter Wemm$FreeBSD$
1744