xref: /freebsd/UPDATING (revision 2a2cfa95fff3f419a940e8345f21759f2812854c)
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
7f59d5f7aSPoul-Henning KampNOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
8f59d5f7aSPoul-Henning Kamp	FreeBSD 5.x has many debugging features turned on, in
969f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1069f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1169f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1269f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1369f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1469f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1569f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1669f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1769f7bcf3SWarner Losh	developers choose to disable these features on build machines
18a19f8ddaSDavid E. O'Brien	to maximize performance.
19c1f61aa9SDavid E. O'Brien
208bf455a5SJohn Baldwin20031103:
218bf455a5SJohn Baldwin	The i386 APIC_IO kernel option has been replaced by
228bf455a5SJohn Baldwin        'device apic'.  The ACPI module has also been temporarily
232a2cfa95SCeri Davies	disabled, so ACPI must be statically compiled into your
248bf455a5SJohn Baldwin	kernel using 'device acpi' if you wish to use the ACPI driver.
258bf455a5SJohn Baldwin
269bf40edeSBrooks Davis20031031:
279bf40edeSBrooks Davis	The API and ABI of struct ifnet have been changed by removing
289bf40edeSBrooks Davis	the if_name and if_unit members and replacing them with
299bf40edeSBrooks Davis	if_xname, if_dname, and if_dunit.  All network drivers and most
309bf40edeSBrooks Davis	userland programs which include net/if_var.h must be updated
319bf40edeSBrooks Davis	and recompiled.  __FreeBSD_version has been bumped to 501113 to
329bf40edeSBrooks Davis	reflect this change.
339bf40edeSBrooks Davis
3447a42c7aSPoul-Henning Kamp20030928:
3547a42c7aSPoul-Henning Kamp	Changes to the cdevsw default functions have been made to remove
3647a42c7aSPoul-Henning Kamp	the need to specify nullopen() and nullclose() explicitly.
3747a42c7aSPoul-Henning Kamp	__FreeBSD_version bumpted to 501110.
3847a42c7aSPoul-Henning Kamp
3907105342SMax Khon20030926:
4007105342SMax Khon	kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
4107105342SMax Khon	mount_cd9660(8) need to be in sync with kernel.
4207105342SMax Khon
4317dcd026SSam Leffler20030925:
4417dcd026SSam Leffler	Configuring a system to use IPFILTER now requires that PFIL_HOOKS
4517dcd026SSam Leffler	also be explicitly configured.  Previously this dependency was
4617dcd026SSam Leffler	magically handled through some cruft in net/pfil.h; but that has
4717dcd026SSam Leffler	been removed.  Building a kernel with IPFILTER but not PFIL_HOOKS
4817dcd026SSam Leffler	will fail with obtuse errors in ip_fil.c.
4917dcd026SSam Leffler
50fedf1d01SBruce M Simpson20030923:
51fedf1d01SBruce M Simpson	Fix a bug in arplookup(), whereby a hostile party on a locally
52fedf1d01SBruce M Simpson	attached network could exhaust kernel memory, and cause a system
53fedf1d01SBruce M Simpson	panic, by sending a flood of spoofed ARP requests. See
54fedf1d01SBruce M Simpson	FreeBSD-SA-03:14.arp.
55fedf1d01SBruce M Simpson
56db38f9cbSJacques Vidrine20030915:
57db38f9cbSJacques Vidrine	A change to /etc/defaults/rc.conf now causes inetd to be started
58db38f9cbSJacques Vidrine	with `-C 60' if it is not overridden in /etc/rc.conf.  This
59db38f9cbSJacques Vidrine	causes inetd to stop accepting connections from an IP address
60db38f9cbSJacques Vidrine	that exceeds the rate of 60 connections per minute.
61db38f9cbSJacques Vidrine
62c09d2c2bSMike Makonnen20030829:
63c09d2c2bSMike Makonnen	The following rc.d scripts have been removed and should be
64c09d2c2bSMike Makonnen	deleted from your installation: atm2.sh atm3.sh devdb
65c09d2c2bSMike Makonnen	localdaemons network1 network2 network3. Depending on when
66c09d2c2bSMike Makonnen	you last updated world and used mergemaster(8) you may or
67c09d2c2bSMike Makonnen	may not have problems during the rc boot sequence. The simplest
68c09d2c2bSMike Makonnen	solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
69c09d2c2bSMike Makonnen	The atm2.sh atm3.sh and devdb scripts were removed some time
70c09d2c2bSMike Makonnen	ago, so depending on when you installed -CURRENT these scripts
71c09d2c2bSMike Makonnen	may or may not exist on your system.
72c09d2c2bSMike Makonnen
7317c159dcSSøren Schmidt20030824:
7417c159dcSSøren Schmidt	ATAng has been committed. You need to build world as sys/ata.h
7517c159dcSSøren Schmidt	has changed, and userland atacontrol depends on it.
76f240812bSSøren Schmidt	If you use ATA SW raids you need "device ataraid" in your
77f240812bSSøren Schmidt	kernel config file, as it is no longer pulled in automatically.
7817c159dcSSøren Schmidt
79c1f61aa9SDavid E. O'Brien20030819:
80c1f61aa9SDavid E. O'Brien	The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
81c1f61aa9SDavid E. O'Brien	Among other things, this changes the device enumeration to be
82c1f61aa9SDavid E. O'Brien	closer to Solaris.  Be aware that, this can even cause the machine
83c1f61aa9SDavid E. O'Brien	to not boot without manual intervention before the fstab is adjusted.
8469f7bcf3SWarner Losh
8538c962e7SNate Lawson20030728:
8638c962e7SNate Lawson	All current USB and Firewire quirks in da(4) have been deprecated
8738c962e7SNate Lawson	and will be removed for 5.2.  If this causes failure for your
8838c962e7SNate Lawson	umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
8938c962e7SNate Lawson	and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
9038c962e7SNate Lawson	so the quirk can be re-enabled.
9138c962e7SNate Lawson
92178cf4e9SWarner Losh20030722:
93178cf4e9SWarner Losh	FPU-less support has been removed from FreeBSD.  Chances are you won't
94178cf4e9SWarner Losh	notice.  386+387 support should still work after this change, but
95178cf4e9SWarner Losh	it is now a minimum requirement for the i386 port that you have real
96178cf4e9SWarner Losh	FPU hardware.
97178cf4e9SWarner Losh
98178cf4e9SWarner Losh20030714:
99178cf4e9SWarner Losh	Some people are having problems with changes related to /rescue.
100178cf4e9SWarner Losh	If you are building -j N, you will need to define NO_RESCUE.  Others
101178cf4e9SWarner Losh	will need to define it if /rescue has issues with their environment.
102178cf4e9SWarner Losh	People should report those issues to current@.
103178cf4e9SWarner Losh
104157c629aSWarner Losh20030711:
105157c629aSWarner Losh	gcc was upgraded to 3.3.  You are advised to not build -DNOCLEAN
1068b71efcaSCeri Davies	across this point.  Further, it might be a good idea to remove
10705538fa9SWarner Losh	/usr/obj.
108157c629aSWarner Losh
1096cc6353fSMarcel Moolenaar20030613: [retrospective]
1106cc6353fSMarcel Moolenaar	There was a small window in which sed(1) was broken.  If you
1116cc6353fSMarcel Moolenaar	happen to have sed(1) installed during that window, which is
1126cc6353fSMarcel Moolenaar	evidenced by an inability to build world with the failure
1136cc6353fSMarcel Moolenaar	given below, you need to manually build and install sed(1)
1146cc6353fSMarcel Moolenaar	(and only sed(1)) before doing anything else. This is a one-
1156cc6353fSMarcel Moolenaar	time snafu. Typical failure mode:
1166cc6353fSMarcel Moolenaar
1176cc6353fSMarcel Moolenaar	In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
1186cc6353fSMarcel Moolenaar	targmatch.h:7:1: null character(s) ignored
1196cc6353fSMarcel Moolenaar	targmatch.h:12:1: null character(s) ignored
1206cc6353fSMarcel Moolenaar	targmatch.h:16:1: null character(s) ignored
1216cc6353fSMarcel Moolenaar		:
1226cc6353fSMarcel Moolenaar
1236cc6353fSMarcel Moolenaar	The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
1246cc6353fSMarcel Moolenaar	to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
1256cc6353fSMarcel Moolenaar	usr.bin/sed/process.c).
1266cc6353fSMarcel Moolenaar
127766c34e4SAndrey A. Chernov20030610:
128766c34e4SAndrey A. Chernov	Remove deprecated locale names and transition period code
129766c34e4SAndrey A. Chernov	for them, finishing switching to the new scheme. Check your
130766c34e4SAndrey A. Chernov	LANG environment variable.
131766c34e4SAndrey A. Chernov
1327ddc2528SPoul-Henning Kamp20030609:
133df622d54SPoul-Henning Kamp	CCD has been changed to be a fully GEOMified class.  Kernel
134df622d54SPoul-Henning Kamp	and ccdconfig(8) needs to be in sync, this is particularly
135df622d54SPoul-Henning Kamp	important to remember beforehand if your source tree is on
136df622d54SPoul-Henning Kamp	a ccd device.  Consider making a copy of the old ccdconfig
137df622d54SPoul-Henning Kamp	into /boot/kernel.good or wherever you keep your backup
138df622d54SPoul-Henning Kamp	kernel.
139df622d54SPoul-Henning Kamp
14052b47445SMark Murray20030505:
14152b47445SMark Murray	Kerberos 5 (Heimdal) is now built by default. Setting
14252b47445SMark Murray	MAKE_KERBEROS5 no longer has any effect. If you do NOT
14352b47445SMark Murray	want the "base" Kerberos 5, you need to set NO_KERBEROS.
14452b47445SMark Murray
145a26df538SWarner Losh20030502:
146a26df538SWarner Losh	groff has been updated.  If you try to do a buildworld and
147a26df538SWarner Losh	get an infinite loop in troff, update to May 4th or newer.  If you
148a26df538SWarner Losh	have a newer kernel than userland, you may need to set the OSRELDATE
149a26df538SWarner Losh	to 500110 in your environment before starting a buildworld.
150a26df538SWarner Losh
1514b065e2cSDoug Barton20030501:
1524b065e2cSDoug Barton	The old rc system has been removed.  Please report any problems
1534b065e2cSDoug Barton	to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
1544b065e2cSDoug Barton	Your personal versions of these files will not be removed, so you can
1554b065e2cSDoug Barton	continue to use them. However, you should take great care when updating,
1564b065e2cSDoug Barton	especially when using mergemaster, since the compatibility code that
1574b065e2cSDoug Barton	utilizes these old scripts has also been removed.
1584b065e2cSDoug Barton
15981cda3d9SWarner Losh20030423:
16081cda3d9SWarner Losh	A bug has been fixed in /dev/devctl which would cause devd
16181cda3d9SWarner Losh	to hang on boot, were it not for a workaround in devd.  The
16281cda3d9SWarner Losh	work around in devd will be removed around 20030507.  You
16381cda3d9SWarner Losh	have until then to upgrade your kernel before updating
16481cda3d9SWarner Losh	userland.  In general, you should have a userland and
16581cda3d9SWarner Losh	kernel that's in sync with each other.  However, given the
16681cda3d9SWarner Losh	effects of this bug (hang on boot when starting devd), some
16781cda3d9SWarner Losh	allowances are made.
16881cda3d9SWarner Losh
16947a657d1SRuslan Ermilov20030329:
17047a657d1SRuslan Ermilov	Alphas with libc from between 20030312 and 20030329 exhibit
17147a657d1SRuslan Ermilov	floating point exceptions (FPEs), most notably in awk(1)
17247a657d1SRuslan Ermilov	while upgrading the system through a buildworld.
17347a657d1SRuslan Ermilov
17447a657d1SRuslan Ermilov	So, to successfully upgrade your Alpha, you must either
17547a657d1SRuslan Ermilov	downgrade your libc.so to a pre-20030312 version, or update
17647a657d1SRuslan Ermilov	/usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
17747a657d1SRuslan Ermilov	to CFLAGS, then forcibly rebuild and install libc:
17847a657d1SRuslan Ermilov
17947a657d1SRuslan Ermilov	cd /usr/src/lib/libc && \
18047a657d1SRuslan Ermilov	    make cleandir && make obj && \
18147a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE all && \
18247a657d1SRuslan Ermilov	    make -DNOMAN -DNOPROFILE install
18347a657d1SRuslan Ermilov
1845d2af00cSGregory Neil Shapiro20030208:
1855d2af00cSGregory Neil Shapiro	sendmail 8.12.7 has been imported.  It has one important
1865d2af00cSGregory Neil Shapiro	change for IPv6 users.  The default submit.mc now uses
1875d2af00cSGregory Neil Shapiro	'[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
1885d2af00cSGregory Neil Shapiro	used to connect to the MTA.  Users on IPv6-only machines
1895d2af00cSGregory Neil Shapiro	will need to edit /etc/mail/submit.mc appropriately.
1905d2af00cSGregory Neil Shapiro
1915d2af00cSGregory Neil Shapiro20030128:
1929db58771SPoul-Henning Kamp	NODEVFS option has been removed and DEVFS thereby made standard.
193ca22e652SJens Schweikhardt	This makes all references to MAKEDEV obsolete, and they should
1949db58771SPoul-Henning Kamp	be removed when convenient.
1959db58771SPoul-Henning Kamp
1968d9b3f57SJake Burkholder20030126:
1978d9b3f57SJake Burkholder	The name of the device for the ofw console has changed, sparc64 users
1988d9b3f57SJake Burkholder	must run mergemaster to update their installed /etc/ttys.
1998d9b3f57SJake Burkholder
2001c5efda5SJeff Roberson20030125:
2011c5efda5SJeff Roberson	The scheduler framework has grown a second scheduler and consequently
2021c5efda5SJeff Roberson	you must specify one and only one scheduler in your kernel config.
203ca22e652SJens Schweikhardt	The cvs config files have been updated to use the old scheduler
2041c5efda5SJeff Roberson	which may be selected via 'options SCHED_4BSD'.  If you would like
2051c5efda5SJeff Roberson	to try the new, much more experimental, scheduler please try
2061c5efda5SJeff Roberson	'options SCHED_ULE' and contribute to the arch@ discussion.
2071c5efda5SJeff Roberson
2089d1d64f5SWarner Losh20030115:
2099d1d64f5SWarner Losh	A new version of the wi driver has been imported into the tree.
2109d1d64f5SWarner Losh	One now must have device wlan in the config file for it to operate
2119d1d64f5SWarner Losh	properly.
2129d1d64f5SWarner Losh
213c9fdb80aSWarner Losh	In addition, there have been some changes to how wi devices are
214c9fdb80aSWarner Losh	configured for point to point links to bring it more in line
215c9fdb80aSWarner Losh	with the former way of doing things, as well as compatibility
216c9fdb80aSWarner Losh	with NetBSD.
217c9fdb80aSWarner Losh
218161dc364SAlexander Kabaev20021222:
219161dc364SAlexander Kabaev 	For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
220161dc364SAlexander Kabaev 	used an incompatible form of ABI for returning structures and unions
221161dc364SAlexander Kabaev 	which FreeBSD's GCC maintainers were not aware of relative to previous
222161dc364SAlexander Kabaev 	versions of FreeBSD.  We have gone back to the ABI for now, and any
223161dc364SAlexander Kabaev 	code compiled which is required to interoperate with other code (not
224161dc364SAlexander Kabaev 	built at the same time) returning structs or unions should be
22584cc83efSAlexander Kabaev	rebuilt.
226161dc364SAlexander Kabaev
227fb4c8061SMartin Blapp20021216:
228fb4c8061SMartin Blapp	A name change in /etc/netconfig has been reverted to stay
22989056245SJens Schweikhardt	compatible with suns TIRPC and also with NetBSD. You need
230fb4c8061SMartin Blapp	to run mergemaster after make world. A new libc does still work
2319d5abbddSJens Schweikhardt	with an outdated /etc/netconfig for some time, but you'll get
232fb4c8061SMartin Blapp	a warning. This warning will be removed in 20030301.
233fb4c8061SMartin Blapp
23417d47eb3SGiorgos Keramidas20021202:
23517d47eb3SGiorgos Keramidas	The recent binutils upgrade marks a kernel flag day on
23617d47eb3SGiorgos Keramidas	sparc64: modules built with the old binutils will not work
23717d47eb3SGiorgos Keramidas	with new kernels and vice versa. Mismatches will result in
23817d47eb3SGiorgos Keramidas	panics.  Make sure your kernel and modules are in sync.
23917d47eb3SGiorgos Keramidas
240a4459294SBill Fenner20021029:
241a4459294SBill Fenner	The value of IPPROTO_DIVERT has changed.  Make sure to keep
242a4459294SBill Fenner	your kernel, netstat, natd and any third-party DIVERT
243a4459294SBill Fenner	consumers in sync.
244a4459294SBill Fenner
245fc8c157fSWarner Losh20021024:
246c57404feSRuslan Ermilov	Old, compatibility slices have been removed in GEOM kernels.
247c57404feSRuslan Ermilov	This means that you will have to update your /etc/fstab to
248c57404feSRuslan Ermilov	not use disk devices of the form /dev/ad0a.  Instead, you
249c57404feSRuslan Ermilov	now must specify /dev/ad0s1a, or whatever slice your FreeBSD
250c57404feSRuslan Ermilov	partition really is on.  The old device names have gone
251c57404feSRuslan Ermilov	away, so if you use them anywhere else, you must also adjust
252c57404feSRuslan Ermilov	those uses.  (This doesn't affect the disks formatted in
253c57404feSRuslan Ermilov	the ``dangerously-dedicated'' mode.)
25469f7bcf3SWarner Losh
255fd9e8bdaSAndrew Gallatin20021023:
256fd9e8bdaSAndrew Gallatin	Alphas with kernels from between 20020830 and 20021023 and/or
257fd9e8bdaSAndrew Gallatin	rtld (ld-elf.so.1) older than 20021023 may experience problems
258fd9e8bdaSAndrew Gallatin	with groff while doing a buildworld (kernel: "out of memory",
259fd9e8bdaSAndrew Gallatin	fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
260fd9e8bdaSAndrew Gallatin	segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
261fd9e8bdaSAndrew Gallatin
262fd9e8bdaSAndrew Gallatin	So, to successfully upgrade your Alpha, you must either
263fd9e8bdaSAndrew Gallatin	upgrade your kernel and rtld first (which might be a bit
264fd9e8bdaSAndrew Gallatin	tricky), or avoid running the bootstrapped groff during the
265fd9e8bdaSAndrew Gallatin	"transitional" buildworld.  To avoid running groff during the
266fd9e8bdaSAndrew Gallatin	transitional upgrade run make buildworld with -DNOMAN,
267fd9e8bdaSAndrew Gallatin	-DNO_SHAREDOCS, and -DNO_LPR.
268fd9e8bdaSAndrew Gallatin
269f8a4c901SWarner Losh20020831:
270f8a4c901SWarner Losh	gcc has been upgraded to 3.2.  It is not all binary compatible
271f8a4c901SWarner Losh	with earlier versions of gcc for c++ programs.  All c++
272f8a4c901SWarner Losh	programs and libraries need to be recompiled.
273f8a4c901SWarner Losh
274f8a4c901SWarner Losh	Also, if you encounter g++ issues, rm /usr/include/g++/* before
275f8a4c901SWarner Losh	doing an installworld to make sure that stale files are removed.
276f8a4c901SWarner Losh
277c2248fa2SJens Schweikhardt20020827:
278c2248fa2SJens Schweikhardt	Our /etc/termcap now has all the entries from the XFree86 xterm
279c2248fa2SJens Schweikhardt	almost unchanged. This means xterm now supports color by default.
280c2248fa2SJens Schweikhardt	If you used TERM=xterm-color in the past you now should use
281c2248fa2SJens Schweikhardt	TERM=xterm. (xterm-color will lead to benign warnings).
282c2248fa2SJens Schweikhardt
2830d533e43SRuslan Ermilov20020815:
2840d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
2850d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
2860d533e43SRuslan Ermilov	again.
2870d533e43SRuslan Ermilov
28833c1de7dSRuslan Ermilov20020729:
28933c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
29033c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
29133c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
29233c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
29333c1de7dSRuslan Ermilov
2942b877facSJulian Elischer20020702:
2952b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
2962b877facSJulian Elischer	There are still some minor problems with some signals but the
2972b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
2982b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
2992b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
3002b877facSJulian Elischer
30106596d37SWarner Losh20020701:
30206596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
30306596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
30406596d37SWarner Losh	GNOME.
30506596d37SWarner Losh
30695ba4330SJacques Vidrine20020511:
30795ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
30895ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
30995ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
31095ba4330SJacques Vidrine	with the set-user-ID bit set.
31195ba4330SJacques Vidrine
312a81da3c9SDavid E. O'Brien20020510:
313f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
314f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
3154b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
316f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
317f50caf6fSDavid E. O'Brien
318f50caf6fSDavid E. O'Brien20020510:
319a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
320a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
321a81da3c9SDavid E. O'Brien	and then do a cvs update.
322a81da3c9SDavid E. O'Brien
323528a0ef5SJacques Vidrine20020421:
324528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
325528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
326528a0ef5SJacques Vidrine
32785aa5a2eSGregory Neil Shapiro20020404:
32885aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
32985aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
33085aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
33185aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
33285aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
33385aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
33485aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
33585aa5a2eSGregory Neil Shapiro
3368f1e4358SRuslan Ermilov20020403:
3378f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
3388f1e4358SRuslan Ermilov
3392292c02eSWarner Losh20020315:
3402292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
3412292c02eSWarner Losh
34269f7bcf3SWarner Losh20020225:
34369f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
34469f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
34569f7bcf3SWarner Losh
3468f35c493SWarner Losh20020217:
3478f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
3488f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
3498f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
3508f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
3518f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
3528f35c493SWarner Losh
353835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
354835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
355835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
356835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
357835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
358835284beSWarner Losh	and group must be merged from src/etc/group and
359835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
360835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
361835284beSWarner Losh	mergemaster before this will work if you are updating from a
362835284beSWarner Losh	very old version of current.  The updating recipe has changed
363835284beSWarner Losh	as of this date.
364835284beSWarner Losh
365fa9401c1SWarner Losh20020112:
366fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
367fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
368fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
369fa9401c1SWarner Losh	you have local modifications, you can use
370fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
371fa9401c1SWarner Losh	/etc/pam.d.
372fa9401c1SWarner Losh
373fa9401c1SWarner Losh	Please see the following url for more details:
374fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
37547d0d01fSWarner Losh20011229:
37647d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
37747d0d01fSWarner Losh	networkfs_types, please note that it has changed
37847d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
37947d0d01fSWarner Losh
380514318a8SWarner Losh20011220:
381514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
382514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
383514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
384514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
385514318a8SWarner Losh	version have now been merged back into the base system's
386514318a8SWarner Losh	version now.  The only user-visible change resulting from this
387514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
388514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
389514318a8SWarner Losh	as well.  (There has never been rc file support for
390514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
391514318a8SWarner Losh	reverted by the time the changes are MFCed.)
392514318a8SWarner Losh
393514318a8SWarner Losh20011215:
394514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
395514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
396514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
397514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
398514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
399514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
400514318a8SWarner Losh	will need to be customized then for `odd' densities using
401514318a8SWarner Losh	fdcontrol(8).
402514318a8SWarner Losh
4032d22e2bfSWarner Losh20011209:
4042d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
4052d22e2bfSWarner Losh	and truss(1) now works again.
4062d22e2bfSWarner Losh
4079e0428e2SWarner Losh20011207:
4089e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
4099e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
4109e0428e2SWarner Losh	see
4119e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
4129e0428e2SWarner Losh	for details.
4139e0428e2SWarner Losh
4149bab8c59SWarner Losh20011204:
4159bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
4169bab8c59SWarner Losh	kernel and burncd to be in sync.
4179bab8c59SWarner Losh
418e57d8b01SWarner Losh20011203:
419e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
420e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
421e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
422e57d8b01SWarner Losh	not there already.
423e57d8b01SWarner Losh
424e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
425e57d8b01SWarner Losh	until the issue has been resolved.
426e57d8b01SWarner Losh
427b001d36fSJacques Vidrine20011202:
428b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
429b001d36fSJacques Vidrine	patched.
430b001d36fSJacques Vidrine
4314b676ec1SWarner Losh20011126:
4324b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
4335ebbf43eSWarner Losh	after this date.  You need to do this only once.
4344b676ec1SWarner Losh
435d961e462SWarner Losh20011103:
436d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
437d961e462SWarner Losh	edges may be left, but for the most part things should be
4384b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
439d961e462SWarner Losh
440d961e462SWarner Losh20011030:
441d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
442d961e462SWarner Losh	choppy waves in the upgrade process.
443d961e462SWarner Losh
4441fe003b6SWarner Losh20011030:
445a4b6fda0SWarner Losh	The asr driver problem has been resolved.
4461fe003b6SWarner Losh
4471fe003b6SWarner Losh20011027:
4481fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
4491fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
4501fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
4511fe003b6SWarner Losh	try to use from this date forward.
4521fe003b6SWarner Losh
4531fe003b6SWarner Losh20011025:
4541fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
4551fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
4561fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
4571fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
4581fe003b6SWarner Losh	TARGET_ARCH=i386.
4591fe003b6SWarner Losh
460d05f9643SWarner Losh20011001:
461d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
462d05f9643SWarner Losh	You must recompile both the kernel and userland applications
463d05f9643SWarner Losh	at the same time.
464d05f9643SWarner Losh
46558970f85SWarner Losh20010929:
46658970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
46758970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
46858970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
46958970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
4709d5abbddSJens Schweikhardt	(eg, you can build pc98 on an i386 machine and vice versa).
47158970f85SWarner Losh
47258970f85SWarner Losh20010927:
47358970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
47458970f85SWarner Losh	To disable ACPI you can add
47566ff0e67SMax Khon		hint.acpi.0.disabled="1"
47658970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
47758970f85SWarner Losh	loader "ok" prompt).
47858970f85SWarner Losh
47958970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
48058970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
48158970f85SWarner Losh	file and not list acpi in that list.
482378f4486SAlfred Perlstein
4835119d237SWarner Losh20010924:
4845119d237SWarner Losh	The buildworld has been fixed.  You may need to install
4855119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
4868b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
4878b039fffSWarner Losh	get them installed on every installworld, or execute the
4888b039fffSWarner Losh	following to get them installed only once:
4898b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
49058970f85SWarner Losh		make all install
4918b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
4925119d237SWarner Losh
4933c293725SWarner Losh20010919:
4943c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
4953c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
4963c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
497772730c7SWarner Losh	workaround is to add
4983c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
4993c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
5003c293725SWarner Losh	can be removed afterwards.
5013c293725SWarner Losh
5023c293725SWarner Losh	A proper fix to the buildworld target is needed.
5033c293725SWarner Losh
5043c293725SWarner Losh20010918:
5053c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
5063c293725SWarner Losh	NFS may be unstable after this date.
5073c293725SWarner Losh
5083c293725SWarner Losh20010912:
5093c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
5103c293725SWarner Losh	the kernel.  While a few problems were introduced in the
5113c293725SWarner Losh	initial commit, most of the major ones have been found and
5123c293725SWarner Losh	corrected.
5133c293725SWarner Losh
5143c293725SWarner Losh20010901:
5153c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
5163c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
5173c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
5183c293725SWarner Losh	have been rectified around this date.
5193c293725SWarner Losh
52098b17b95SWarner Losh20010823:
52198b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
52298b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
52398b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
52498b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
52598b17b95SWarner Losh 	sure that user or group bind has read (and not write)
52698b17b95SWarner Losh 	permission for your name server configuration and that it
52798b17b95SWarner Losh 	has read and write permission for your slave zone files and
52898b17b95SWarner Losh 	directory.
52998b17b95SWarner Losh
53098b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
53198b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
53298b17b95SWarner Losh
53398b17b95SWarner Losh 		named_flags=
53498b17b95SWarner Losh
5357b9786edSMark Murray20010709:
5367b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
5377b9786edSMark Murray	the ability of the shared library major number to handle.
5387b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
5397b9786edSMark Murray	solution is to rebuild those ports.
5407b9786edSMark Murray
5411d28950eSWarner Losh20010628:
5421d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
5431d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
5441d28950eSWarner Losh
545e72fd46aSWarner Losh20010625:
54698b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
54798b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
54898b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
54998b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
55098b17b95SWarner Losh	IRQ configuration needs more safety belts.
55116de1a07SWarner Losh
5520d415dffSWarner Losh20010617:
553e72fd46aSWarner Losh	Softupdates problems have been corrected.
5540d415dffSWarner Losh
5550d415dffSWarner Losh20010614:
5560d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
5570d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
5580d415dffSWarner Losh	kernel building methods.
5590d415dffSWarner Losh
5608b9959adSWarner Losh20010613:
5618b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
5628b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
563e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
564e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
5658b9959adSWarner Losh
566e72fd46aSWarner Losh20010613:
5678b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
568e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
569e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
5708b9959adSWarner Losh
5710d415dffSWarner Losh20010612:
5720d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
5730d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
5740d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
5750d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
5760d415dffSWarner Losh	until this bug is fixed.
5770d415dffSWarner Losh
578e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
579e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
580ca22e652SJens Schweikhardt	hints.c file, whether you want it to or not.
581e72fd46aSWarner Losh
5820d415dffSWarner Losh20010610:
5830d415dffSWarner Losh	Locale names have changed to match other systems better.
5840d415dffSWarner Losh
5856ccdb5e4SWarner Losh20010604:
5866ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
5876ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
5886ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
5893590182eSWarner Losh	Interrupt storms look a lot like a hang.
5903590182eSWarner Losh
5913590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
5923590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
5933590182eSWarner Losh	it is).
5943590182eSWarner Losh
5953590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
5963590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
5973590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
5983590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
5996ccdb5e4SWarner Losh
6000bc62786SWarner Losh20010530:
6010bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
6020bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
6030bc62786SWarner Losh	a limited time.  If you see
6040bc62786SWarner Losh
6050bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
6060bc62786SWarner Losh
6070bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
6080bc62786SWarner Losh	COPY=-C.
6090bc62786SWarner Losh
61068a38c6cSWarner Losh20010525:
611b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
612c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
613c4f4a728SWarner Losh	definitely is in bad shape.
61468a38c6cSWarner Losh
615ed0f29caSWarner Losh20010521:
616ca22e652SJens Schweikhardt	Minor repo damage has happened.  This may cause problems
617ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
618ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
619ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
620ed0f29caSWarner Losh	is
621ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
622ed0f29caSWarner Losh
62380c16af9SWarner Losh20010520:
62468a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
62580c16af9SWarner Losh
62680c16af9SWarner Losh20010519:
62780c16af9SWarner Losh	pccard has had much reorganizational work done to it over
62880c16af9SWarner Losh	the past few days.  Everything should still work, but if
62980c16af9SWarner Losh	not, please contact imp@freebsd.org.
63080c16af9SWarner Losh
631a45f2d05SWarner Losh20010517:
632a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
633a45f2d05SWarner Losh	userland at the same time.
634a45f2d05SWarner Losh
635a45f2d05SWarner Losh20010517:
636a45f2d05SWarner Losh	New ncurses imported.
637a45f2d05SWarner Losh
6382988afcaSWarner Losh20010512:
6392988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
6402988afcaSWarner Losh	will be the only way to go starting July 1.
6412988afcaSWarner Losh
6421a33dba7SWarner Losh20010504:
6431a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
6441a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
6451a33dba7SWarner Losh
64609946a51SWarner Losh20010502:
64709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
64809946a51SWarner Losh
64909946a51SWarner Losh20010501:
65009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
65109946a51SWarner Losh
65209946a51SWarner Losh20010430:
653a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
65409946a51SWarner Losh	go back in the water.
65509946a51SWarner Losh
65609946a51SWarner Losh20010429:
65709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
65809946a51SWarner Losh	this date, but before the correction date.
65909946a51SWarner Losh
66091dd3b53SWarner Losh20010423:
66191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
66291dd3b53SWarner Losh
66391dd3b53SWarner Losh20010411:
66491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
66591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
66691dd3b53SWarner Losh	Update only if you understand that you must not use the old
66791dd3b53SWarner Losh	fsck with the new kernel ever.
66891dd3b53SWarner Losh
669933b3269SWarner Losh20010330:
670933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
671c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
672933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
673933b3269SWarner Losh
674933b3269SWarner Losh20010319:
675933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
676933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
677933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
678f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
67909946a51SWarner Losh
68009946a51SWarner Losh20010315:
68109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
682ca22e652SJens Schweikhardt	and ATA_ENABLE_TAGS are no longer kernel options.  They have
68309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
684933b3269SWarner Losh
685933b3269SWarner Losh20010312:
686933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
687933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
688933b3269SWarner Losh
689933b3269SWarner Losh20010312:
690933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
691933b3269SWarner Losh	instead of ad-hoc.
692933b3269SWarner Losh
693933b3269SWarner Losh20010310:
694f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
695933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
696933b3269SWarner Losh	ssh might not work if you don't.
697933b3269SWarner Losh
69862353691SWarner Losh20010303:
69962353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
70062353691SWarner Losh	which means that you must include the miibus in your kernel if
70162353691SWarner Losh	you use the ed driver.
70262353691SWarner Losh
703d325cf65SWarner Losh20010220:
704d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
705d325cf65SWarner Losh	safe to go back into the water.
706d325cf65SWarner Losh
707024daae6SWarner Losh20010211:
708024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
709024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
710024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
711024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
712024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
713024daae6SWarner Losh
714024daae6SWarner Losh	To get to the new system, you'll need to use the following
715024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
716024daae6SWarner Losh	don't have to move this to the updating section.
717024daae6SWarner Losh
718024daae6SWarner Losh	To get around the installworld problem, do:
719024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
720024daae6SWarner Losh		# make install
721024daae6SWarner Losh		# cd /usr/src
722024daae6SWarner Losh		# make installworld
723024daae6SWarner Losh	If that doesn't work, then try:
724024daae6SWarner Losh		# make -k installworld
725024daae6SWarner Losh		# make installworld
726024daae6SWarner Losh
727024daae6SWarner Losh20010207:
728024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
729024daae6SWarner Losh	do not include devfs in your kernel as problems result.
730024daae6SWarner Losh
731024daae6SWarner Losh20010205:
7327595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
733024daae6SWarner Losh	Remove them from your config.
734024daae6SWarner Losh
7351e159248SWarner Losh20010122:
7361e159248SWarner Losh	****************************** WARNING ******************************
7371e159248SWarner Losh			buildkernel has been changed slightly
7381e159248SWarner Losh	****************************** WARNING ******************************
7391e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
7401e159248SWarner Losh	should update your scripts and make.conf accordingly.
7411e159248SWarner Losh
7421e159248SWarner Losh20010119:
7431e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
7441e159248SWarner Losh	This requires a new config to build correctly.
7451e159248SWarner Losh
746aac7dfeaSWarner Losh20010116:
747ca22e652SJens Schweikhardt	The kernel option I386_CPU is now mutually exclusive with the
748aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
749aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
750aac7dfeaSWarner Losh
751aac7dfeaSWarner Losh20010110:
752aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
753aac7dfeaSWarner Losh
754aac7dfeaSWarner Losh20010102:
755aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
756aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
757aac7dfeaSWarner Losh
75863c90c9eSWarner Losh20010101:
75963c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
76063c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
7615fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
76263c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
76363c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
76463c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
76563c90c9eSWarner Losh	might have been ignored by the -k option.
76663c90c9eSWarner Losh
7675fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
7685fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
7695fd2a895SWarner Losh	of this working.
7705fd2a895SWarner Losh
771aac7dfeaSWarner Losh20001228:
772aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
773ca22e652SJens Schweikhardt	libscrypt/libdescrypt symlink silliness is gone and the installed
774aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
775aac7dfeaSWarner Losh
776de2bcc63SWarner Losh20001218:
777de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
778de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
779de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
780de2bcc63SWarner Losh	cards will not be recognized without it.
781de2bcc63SWarner Losh
782960773f7SWarner Losh20001205:
783960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
784960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
785960773f7SWarner Losh	adding the following in pam.conf:
786960773f7SWarner Losh
787960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
788960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
789960773f7SWarner Losh	sshd    session required        pam_permit.so
790960773f7SWarner Losh
7910acc635eSWarner Losh20001031:
7920acc635eSWarner Losh	cvs updated to 1.11.
7930acc635eSWarner Losh
7940acc635eSWarner Losh20001020:
7950acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
7960acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
7970acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
7980acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
7990acc635eSWarner Losh	workaround.
8000acc635eSWarner Losh
8010acc635eSWarner Losh20001010:
8020acc635eSWarner Losh	****************************** WARNING ******************************
8030acc635eSWarner Losh				Sendmail has been updated.
8040acc635eSWarner Losh	****************************** WARNING ******************************
8050acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
8060acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
8070acc635eSWarner Losh	  is set.
8080acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
8090acc635eSWarner Losh	  commands.
8100acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
8110acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
8120acc635eSWarner Losh	  in /usr/share/sendmail/cf.
8130acc635eSWarner Losh	o sendmail.cw changed to local-host-names
8140acc635eSWarner Losh
8150acc635eSWarner Losh	More details can be found at
8160acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
8170acc635eSWarner Losh
8186e98a146SWarner Losh20001009:
8196e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
8206e98a146SWarner Losh	your entire ports tree, or you will have problems.
8216e98a146SWarner Losh
8226e98a146SWarner Losh20001006:
823685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
8246e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
8256e98a146SWarner Losh	/usr/bin/miniperl.
8266e98a146SWarner Losh
827073113a4SWarner Losh20001005:
828073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
829685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
830073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
831073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
832073113a4SWarner Losh	tree for anything to work.
833073113a4SWarner Losh
8340acc635eSWarner Losh20000928:
8350acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
8360acc635eSWarner Losh
837be3885b3SWarner Losh20000916:
838be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
839be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
840be3885b3SWarner Losh	same time as your kernel.
841be3885b3SWarner Losh
84276ec9675SWarner Losh20000914:
84376ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
84476ec9675SWarner Losh	include the device will cause suspended laptops losing time
84576ec9675SWarner Losh	when they resume.  Include
84676ec9675SWarner Losh		device		pmtimer
84776ec9675SWarner Losh	in your config file and
84801b9a434SWarner Losh		hint.pmtimer.0.at="isa"
84976ec9675SWarner Losh	to your /boot/device.hints file.
85076ec9675SWarner Losh
851f4865386SMark Murray20000911:
852f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
853f4865386SMark Murray	rather than an option. The supplied kernel config files have
854f4865386SMark Murray	been updated. You will need to do something similar in your
855f4865386SMark Murray	own kernel config file.
856f4865386SMark Murray	Remove:
857f4865386SMark Murray		options		RANDOMDEV
858f4865386SMark Murray	Add:
859f4865386SMark Murray		device		random
860f4865386SMark Murray	If you prefer to load the loadable module, you need to do
861f4865386SMark Murray	nothing.
862f4865386SMark Murray
863d594498fSWarner Losh20000909:
864d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
865d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
866d594498fSWarner Losh	reflect this if you load this module at boot time.
867d594498fSWarner Losh	The line should read:
868d594498fSWarner Losh		random_load="YES"
869d594498fSWarner Losh
8700deb7ddcSWarner Losh20000907:
8710deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
87216eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
87316eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
87416eb772dSWarner Losh	sure you don't have model loading problems which might at
87516eb772dSWarner Losh	first blush appear related to SMP.
87652bf24e7SWarner Losh
8775a01880bSWarner Losh20000906:
8785a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
8795a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
8805a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
8815a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
8825a01880bSWarner Losh	don't have one, and you have host.conf.
8835a01880bSWarner Losh
8842b41163cSWarner Losh20000905:
88538d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
88638d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
88738d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
88838d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
88938d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
89038d6ecd2SWarner Losh
89138d6ecd2SWarner Losh20000905:
8928aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
8938aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
8948aab4bc7SWarner Losh	is /boot/kernel.
8958aab4bc7SWarner Losh
8968aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
89738d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
89838d6ecd2SWarner Losh	installkernel/installworld dance.
8992b41163cSWarner Losh
900d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
901d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
902d594498fSWarner Losh	modules in that directory instead of finding them in the correct
903d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
904d594498fSWarner Losh	is that the linux module crashes your machine after the update.
905d594498fSWarner Losh
906d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
907d594498fSWarner Losh		mv /modules.old /boot/kernel.old
908d594498fSWarner Losh		chflags noschg /kernel.old
909d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
910d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
911d594498fSWarner Losh	fi
912d594498fSWarner Losh
913c22a309cSWarner Losh20000904:
914c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
915c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
916c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
917c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
918c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
919c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
920c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
921c22a309cSWarner Losh	is not likely to be generated.
922c22a309cSWarner Losh
923fdb9f54dSWarner Losh20000825:
924fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
9259c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
9269c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
9279c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
9289c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
9299c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
9309c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
9319c1a7444SWarner Losh	kernel.
9329c1a7444SWarner Losh
9339c1a7444SWarner Losh20000821:
9349c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
9359c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
9369c1a7444SWarner Losh	/boot/loader.conf.
937fdb9f54dSWarner Losh
9388f250aa7SWarner Losh20000812:
9395da0d091SWarner Losh	suidperl is now always built and installed on the system, but
9405da0d091SWarner Losh	with permissions of 511.  If you have applications that use
9415da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
9425da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
9435da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
9445da0d091SWarner Losh	will fix this until the next build.
9455da0d091SWarner Losh
9465da0d091SWarner Losh20000812:
9478f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
9488f250aa7SWarner Losh	visible changes that may immediately affect your configuration
9498f250aa7SWarner Losh	include:
9508f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
9518f250aa7SWarner Losh	- newaliases limited to root and trusted users
9528f250aa7SWarner Losh	- MSA port (587) turned on by default
9538f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
9548f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
9558f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
9568f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
9578f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
9588f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
9598f250aa7SWarner Losh
96071c38472SWarner Losh20000810:
96171c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
96271c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
96371c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
96471c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
96571c38472SWarner Losh	specific use for it.
96671c38472SWarner Losh
96771c38472SWarner Losh20000729:
96871c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
96971c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
97071c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
97171c38472SWarner Losh	afterwards (unless the variables already are set, of course):
97271c38472SWarner Losh		# Enable network daemons for user convenience.
97371c38472SWarner Losh		inetd_enable="YES"
97471c38472SWarner Losh		portmap_enable="YES"
97571c38472SWarner Losh		sendmail_enable="YES"
97671c38472SWarner Losh
97771c38472SWarner Losh20000728:
97871c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
97971c38472SWarner Losh	will need to change that to nullfs_load="YES".
98071c38472SWarner Losh
9811dece4a9SWarner Losh20000728:
9821dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
9831dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
9841dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
9851dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
9861dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
9871dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
9881dece4a9SWarner Losh	to /MYKERNEL.
9891dece4a9SWarner Losh
990409e887cSWarner Losh20000711:
991409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
992409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
993409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
994409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
995409e887cSWarner Losh	for details on potential problems that you might have and how
996409e887cSWarner Losh	to get around them.
997409e887cSWarner Losh
998409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
999409e887cSWarner Losh	clauses above, you needn't worry.
1000409e887cSWarner Losh
1001409e887cSWarner Losh20000711:
1002409e887cSWarner Losh	/etc/security has been updated to print the inode number of
1003409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
1004409e887cSWarner Losh	in the number of changed programs the first time when you run
1005409e887cSWarner Losh	mergemaster to get a new /etc/security.
1006409e887cSWarner Losh
1007673d13f2SWarner Losh20000710:
1008673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
1009673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
1010673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
1011673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
1012673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
1013673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
1014673d13f2SWarner Losh	errors. (see below, 20000624).
1015673d13f2SWarner Losh
1016bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
10171dece4a9SWarner Losh
1018673d13f2SWarner Losh20000709:
1019c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
1020c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
1021c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
1022673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
1023673d13f2SWarner Losh
1024e98e26cdSWarner Losh20000706:
1025e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
1026e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
1027e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
1028f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
1029e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
10302c021c6cSMark Ovens	interim if needed.
1031e98e26cdSWarner Losh
1032e98e26cdSWarner Losh20000705:
1033e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
1034e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
1035e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
1036e98e26cdSWarner Losh	details.
1037e98e26cdSWarner Losh
1038c373950eSWarner Losh20000704:
10392f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
10402f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
10412f961bc8SWarner Losh
10422f961bc8SWarner Losh20000704:
1043c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
1044c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
1045c373950eSWarner Losh	rc.d scripts that haven't been updated.
1046c373950eSWarner Losh
104727dc3a2bSWarner Losh20000630:
104827dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
104927dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
105027dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
105127dc3a2bSWarner Losh
1052b8c215acSWarner Losh20000625:
1053b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
105427dc3a2bSWarner Losh	system installed in order to build the system and kernel.
105527dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
105627dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
105727dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
105827dc3a2bSWarner Losh	were required.  You should check with the latest collections
105927dc3a2bSWarner Losh	to make sure that these haven't changed.
1060b8c215acSWarner Losh
10617b990719SWarner Losh20000624:
10627b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
10637b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
10647b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
10651a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
10667b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
10677b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
10687b990719SWarner Losh	date to the completion of the work.
10697b990719SWarner Losh
107027dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
107127dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
107227dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
107327dc3a2bSWarner Losh	recreate the random and urandom devices.
107427dc3a2bSWarner Losh
107581e54c50SWarner Losh20000622:
107681e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
107781e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
107881e54c50SWarner Losh	that used to be required when updating.
107981e54c50SWarner Losh
108039943833SWarner Losh20000621:
10812c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
10822a2f33fbSDaniel Baker	the config file update procedure.
10832a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
1084c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
108559df1173SDavid E. O'Brien	isn't buildable.  However, you can generate a LINT file:
108659df1173SDavid E. O'Brien		cd /sys/<ARCH>/conf && make LINT
108739943833SWarner Losh
1088290f9ad8SWarner Losh20000620:
1089290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
1090290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
1091290f9ad8SWarner Losh	that workaround will no longer be required.
1092290f9ad8SWarner Losh
109390fb6346SWarner Losh20000615:
109490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
109590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
109690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
109790fb6346SWarner Losh	devices.
109890fb6346SWarner Losh
1099f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
1100f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
1101f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
1102f75f65bbSWarner Losh	may work).
1103f75f65bbSWarner Losh
1104ba26da8eSWarner Losh20000612:
1105ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
1106290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
1107c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
1108290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
1109f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
1110f54a3542SWarner Losh	NEWCARD for examples of the new format.
1111290f9ad8SWarner Losh
11129698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
11139698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
11149698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
11159698f2c0SWarner Losh	in it.
1116bbcc5149SWarner Losh
1117d65850ebSWarner Losh20000522:
1118ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
1119d65850ebSWarner Losh	building a kernel after this point is advised that they need
1120d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
1121d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
1122d65850ebSWarner Losh
1123d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1124d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
1125d9583a00SWarner Losh	is recommended that you don't set this option until the problem
1126d9583a00SWarner Losh	is resolved.
1127d9583a00SWarner Losh
11288039cedeSWarner Losh20000513:
11298039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
11308039cedeSWarner Losh
1131d65850ebSWarner Losh20000510:
11328039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
11338039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
11348039cedeSWarner Losh	is requires for the boot blocks to build properly.
11358039cedeSWarner Losh
11368039cedeSWarner Losh20000503:
11378039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
11388039cedeSWarner Losh	is now available.
11398039cedeSWarner Losh
1140d65850ebSWarner Losh20000502:
1141d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
1142d65850ebSWarner Losh	connected to the kernel building instead.
1143d65850ebSWarner Losh
1144be149406SNik Clayton20000427:
11458039cedeSWarner Losh	You may need to build gperf
11468039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
11478039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
11488039cedeSWarner Losh	an option only in -current.
11498039cedeSWarner Losh
11502b8dd5f4SWarner Losh20000417:
11512b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
1152f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
11532b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
11542b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
11552c021c6cSMark Ovens	before you reboot, you'll need to issue:
11562b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
11572b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
11582b8dd5f4SWarner Losh
11598d9f1945SWarner Losh20000320:
11602b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
11612b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
11622b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
1163ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
11642b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
11658d9f1945SWarner Losh
1166f8ab1dd6SWarner Losh20000319:
1167f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
1168f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
1169f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1170f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
1171f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
1172f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
1173f8ab1dd6SWarner Losh
117419cada77SWarner Losh20000318:
1175f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
117619cada77SWarner Losh	Large kernel changes are being committed and are in the
117719cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
117819cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
117919cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
118019cada77SWarner Losh	that you are loading are up to date.
1181ba228352SWarner Losh
118219cada77SWarner Losh20000315:
11836d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
11846d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
11856d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
11866d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
11876d23c382SWarner Losh	boot.
11886d23c382SWarner Losh
11896d23c382SWarner Losh20000315:
119019cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
119119cada77SWarner Losh	to upgrade to 4.0 from 3.x.
119257199806SWarner Losh
1193dc0dbf5cSWarner LoshCOMMON ITEMS:
1194dc0dbf5cSWarner Losh
1195a24eff53SWarner Losh	General Notes
1196a24eff53SWarner Losh	-------------
1197a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
1198a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
1199a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
1200a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
1201a24eff53SWarner Losh	or several minor releases, or when several months have passed
1202a24eff53SWarner Losh	on the -current branch).
1203a24eff53SWarner Losh
12045780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
12055780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
12065780f3baSWarner Losh	environment when searching for values for global variables.
12075780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
12085780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
12095780f3baSWarner Losh	page for more details.
12105780f3baSWarner Losh
1211dc0dbf5cSWarner Losh	To build a kernel
1212dc0dbf5cSWarner Losh	-----------------
1213ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
1214f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
1215ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
1216282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1217282e0f01SRuslan Ermilov	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1218dc0dbf5cSWarner Losh
1219ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
1220ba01eb20SWarner Losh	--------------------------------------------------------------
1221ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
122247d0d01fSWarner Losh	config KERNEL_NAME_HERE
1223ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
1224ba01eb20SWarner Losh	make depend
1225ba01eb20SWarner Losh	make
1226ba01eb20SWarner Losh	make install
1227ba01eb20SWarner Losh
1228ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
1229ba01eb20SWarner Losh
1230ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
1231ba01eb20SWarner Losh	-----------------------------------------------------------
123263cb445eSWarner Losh	# Note: sometimes if you are running current you gotta do more than
123363cb445eSWarner Losh	# is listed here if you are upgrading from a really old current.
123463cb445eSWarner Losh
1235f643de42SWarner Losh	<make sure you have good level 0 dumps>
123663cb445eSWarner Losh	<maybe fix /etc/fstab>				[7]
123763cb445eSWarner Losh	make buildworld
123863cb445eSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
123963cb445eSWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
124063cb445eSWarner Losh							[1]
124163cb445eSWarner Losh	<reboot in single user>				[3]
124263cb445eSWarner Losh	mergemaster -p					[5]
124363cb445eSWarner Losh	make installworld
124463cb445eSWarner Losh	mergemaster					[4]
124563cb445eSWarner Losh	<reboot>
124663cb445eSWarner Losh
1247759f0aefSWarner Losh
1248f27b1fceSJoseph Koshy	To cross-install current onto a separate partition
1249f27b1fceSJoseph Koshy	--------------------------------------------------
1250f27b1fceSJoseph Koshy	# In this approach we use a separate partition to hold
1251f27b1fceSJoseph Koshy	# current's root, 'usr', and 'var' directories.   A partition
1252f27b1fceSJoseph Koshy	# holding "/", "/usr" and "/var" should be about 2GB in
1253f27b1fceSJoseph Koshy	# size.
1254f27b1fceSJoseph Koshy
1255f27b1fceSJoseph Koshy	<make sure you have good level 0 dumps>
1256f27b1fceSJoseph Koshy	<boot into -stable>
1257f27b1fceSJoseph Koshy	make buildworld
1258f27b1fceSJoseph Koshy	<maybe newfs current's root partition>
1259f27b1fceSJoseph Koshy	<mount current's root partition on directory ${CURRENT_ROOT}>
1260f27b1fceSJoseph Koshy	make installworld DESTDIR=${CURRENT_ROOT}
1261f27b1fceSJoseph Koshy	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1262f27b1fceSJoseph Koshy	cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1263f27b1fceSJoseph Koshy		${CURRENT_ROOT}/boot/device.hints	# as needed
1264f27b1fceSJoseph Koshy	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1265f27b1fceSJoseph Koshy	cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1266f27b1fceSJoseph Koshy	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1267f27b1fceSJoseph Koshy	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1268f27b1fceSJoseph Koshy	<reboot into current>
1269f27b1fceSJoseph Koshy	<do a "native" rebuild/install as described in the previous section>
1270f27b1fceSJoseph Koshy	<maybe install compatibility libraries from /usr/src/lib/compat>
1271f27b1fceSJoseph Koshy 	<reboot>
1272f27b1fceSJoseph Koshy
1273f27b1fceSJoseph Koshy
1274f27b1fceSJoseph Koshy	To upgrade in-place from 4.x-stable to current
1275f27b1fceSJoseph Koshy	----------------------------------------------
12765c195f59SWarner Losh	# 5.x uses more space than 4.x.  Also, the location of kernel
12775c195f59SWarner Losh	# modules has changed.  If you are installing 5.0 onto a 4.x
12785c195f59SWarner Losh	# system, you'll need about 30MB of free disk space on your /
12795c195f59SWarner Losh	# partition.  If you have less than this, you may encounter difficult
1280ca22e652SJens Schweikhardt	# to back out of problems with this procedure.  If /tmp is on
1281f643de42SWarner Losh	# the / partition, you may want to completely remove all its content
1282f643de42SWarner Losh	# before upgrading, as this can be a common source of shortage of
1283f643de42SWarner Losh	# space on /.
1284f643de42SWarner Losh
1285f643de42SWarner Losh	<make sure you have good level 0 dumps>
1286fc8c157fSWarner Losh	<maybe fix /etc/fstab>				[7]
128721c075eaSWarner Losh	make buildworld					[9]
1288c74fe6afSWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1289d2125802SWarner Losh	cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1290be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
1291fc8c157fSWarner Losh	cd src/sys/boot ; make install			[6]
1292fc8c157fSWarner Losh							[1]
1293fc8c157fSWarner Losh	<reboot in single user>				[3]
1294835284beSWarner Losh	mergemaster -p					[5]
1295f8a4c901SWarner Losh	rm -rf /usr/include/g++
1296ba26da8eSWarner Losh	make installworld
1297a6cd4f9dSWarner Losh	mergemaster					[4]
1298ba26da8eSWarner Losh	<reboot>
1299ba26da8eSWarner Losh
1300fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
1301fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
1302fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
1303fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
1304fdb9f54dSWarner Losh	the UPDATING entries.
1305ba26da8eSWarner Losh
13061dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
13071dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
13081dece4a9SWarner Losh	your sources that you have read and understood all the recent
13091dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
13101dece4a9SWarner Losh	much fewer pitfalls.
13111dece4a9SWarner Losh
1312134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1313134d2e86SWarner Losh	should disable them at this point so they don't crash your
1314134d2e86SWarner Losh	system on reboot.
1315134d2e86SWarner Losh
13169c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
13179c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
13189c1a7444SWarner Losh	configuration.
13199c1a7444SWarner Losh
1320ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1321ee6e1fc3SWarner Losh		fsck -p
1322ee6e1fc3SWarner Losh		mount -u /
1323ee6e1fc3SWarner Losh		mount -a
1324ee6e1fc3SWarner Losh		cd /usr/src
132547d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1326f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1327f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1328b705ae10SWarner Losh	For the 4.x -> 5.0 upgrade, you will also see many messages about
1329b705ae10SWarner Losh	needing to recompile your userland.  These are harmless and can
1330b705ae10SWarner Losh	be ignored while you proceed to the next step.
1331ee6e1fc3SWarner Losh
1332a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1333a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1334a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1335a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1336a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1337a6cd4f9dSWarner Losh	for potential gotchas.
1338a6cd4f9dSWarner Losh
1339835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1340835284beSWarner Losh	you may need to do this if you get unknown user in the following
1341835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1342835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1343835284beSWarner Losh	install) after the buildworld before this step if you last updated
1344835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1345835284beSWarner Losh
1346bd79cf40SWarner Losh	[6] 4.x boot loader can be used to boot a 5.x system, however
1347bd79cf40SWarner Losh	it is difficult to do that at best.  If you wish to try, then
1348bd79cf40SWarner Losh	you should interrupt the boot and at the ok prompt type:
1349bd79cf40SWarner Losh		ok unload
1350bd79cf40SWarner Losh		ok boot /boot/kernel/kernel
1351bd79cf40SWarner Losh	If this fails to work, you must install a new boot loader as
1352bd79cf40SWarner Losh	described here.
1353fc8c157fSWarner Losh
1354fc8c157fSWarner Losh	[7] Before you upgrade, please make sure that you are not using
1355fc8c157fSWarner Losh	compatibility slices.  These are device names of the form, on i386
1356fc8c157fSWarner Losh	and other architectures that use MBR slicing, /dev/ad0a without the
1357fc8c157fSWarner Losh	actual slice name.  Chances are excellent that these will break.
1358fc8c157fSWarner Losh	You generally must update these entries to use the post FreeBSD
1359fc8c157fSWarner Losh	2.x form of /dev/ad0s1a.
1360fc8c157fSWarner Losh
1361c74fe6afSWarner Losh	[8] In order to have a kernel that can run the 4.x binaries
1362c74fe6afSWarner Losh	needed to do an installworld, you must include the COMPAT_FREEBSD4
1363c74fe6afSWarner Losh	option in your kernel.  Failure to do so may leave you with a system
1364c74fe6afSWarner Losh	that is hard to boot to recover.
1365c74fe6afSWarner Losh
136621c075eaSWarner Losh	[9] When checking out sources, you must include the -P flag to have
136721c075eaSWarner Losh	cvs prune empty directories.
1368dc0dbf5cSWarner LoshFORMAT:
1369dc0dbf5cSWarner Losh
1370f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
13711fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1372f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1373f8ab1dd6SWarner Loshprevious releases if your system is older than this.
13741fc1a0dcSWarner Losh
1375e72fd46aSWarner LoshCopyright information:
1376e72fd46aSWarner Losh
13779698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1378e72fd46aSWarner Losh
1379772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1380772730c7SWarner Loshmodification, in full or in part, in any form or format of this
13819698f2c0SWarner Loshdocument are permitted without further permission from the author.
1382e72fd46aSWarner Losh
1383e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1384e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1385e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1386e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1387e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1388e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1389e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1390e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1391e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1392e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1393e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1394e72fd46aSWarner Losh
1395e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1396e72fd46aSWarner Loshauthor a beer.
1397e72fd46aSWarner Losh
139822306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1399772730c7SWarner Loshthis document.
1400772730c7SWarner Losh
140197d92980SPeter Wemm$FreeBSD$
1402