xref: /freebsd/UPDATING (revision 5a01880bbfb79ff6c4c06a535172732347b33579)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3f8c77507SWarner LoshThis file is maintained by imp@village.org.  Please send new entries
4dc0dbf5cSWarner Loshdirectly to him.  See end of file for further details.  For commonly
516de1a07SWarner Loshdone items, please see the end of the file.  Search for 'COMMON
616de1a07SWarner LoshITEMS:'
716de1a07SWarner Losh
85a01880bSWarner Losh20000906:
95a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
105a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
115a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
125a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
135a01880bSWarner Losh	don't have one, and you have host.conf.
145a01880bSWarner Losh
152b41163cSWarner Losh20000905:
162b41163cSWarner Losh	This just in.  The boot loader has been updated.  The new
172b41163cSWarner Losh	default kernel is /kernel.ko.  The new default module location
182b41163cSWarner Losh	is /boot/modules.  You *MUST* upgrade your boot loader and
192b41163cSWarner Losh	kernel at the same time.  Film at 11.
202b41163cSWarner Losh
21c22a309cSWarner Losh20000904:
22c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
23c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
24c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
25c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
26c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
27c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
28c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
29c22a309cSWarner Losh	is not likely to be generated.
30c22a309cSWarner Losh
31fdb9f54dSWarner Losh20000825:
32fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
339c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
349c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
359c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
369c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
379c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
389c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
399c1a7444SWarner Losh	kernel.
409c1a7444SWarner Losh
419c1a7444SWarner Losh20000821:
429c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
439c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
449c1a7444SWarner Losh	/boot/loader.conf.
45fdb9f54dSWarner Losh
468f250aa7SWarner Losh20000812:
475da0d091SWarner Losh	suidperl is now always built and installed on the system, but
485da0d091SWarner Losh	with permissions of 511.  If you have applications that use
495da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
505da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
515da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
525da0d091SWarner Losh	will fix this until the next build.
535da0d091SWarner Losh
545da0d091SWarner Losh20000812:
558f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
568f250aa7SWarner Losh	visible changes that may immediately affect your configuration
578f250aa7SWarner Losh	include:
588f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
598f250aa7SWarner Losh	- newaliases limited to root and trusted users
608f250aa7SWarner Losh	- MSA port (587) turned on by default
618f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
628f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
638f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
648f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
658f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
668f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
678f250aa7SWarner Losh
6871c38472SWarner Losh20000810:
6971c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
7071c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
7171c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
7271c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
7371c38472SWarner Losh	specific use for it.
7471c38472SWarner Losh
7571c38472SWarner Losh20000729:
7671c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
7771c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
7871c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
7971c38472SWarner Losh	afterwards (unless the variables already are set, of course):
8071c38472SWarner Losh		# Enable network daemons for user convenience.
8171c38472SWarner Losh		inetd_enable="YES"
8271c38472SWarner Losh		portmap_enable="YES"
8371c38472SWarner Losh		sendmail_enable="YES"
8471c38472SWarner Losh
8571c38472SWarner Losh20000728:
8671c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
8771c38472SWarner Losh	will need to change that to nullfs_load="YES".
8871c38472SWarner Losh
891dece4a9SWarner Losh20000728:
901dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
911dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
921dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
931dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
941dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
951dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
961dece4a9SWarner Losh	to /MYKERNEL.
971dece4a9SWarner Losh
98409e887cSWarner Losh20000711:
99409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
100409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
101409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
102409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
103409e887cSWarner Losh	for details on potential problems that you might have and how
104409e887cSWarner Losh	to get around them.
105409e887cSWarner Losh
106409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
107409e887cSWarner Losh	clauses above, you needn't worry.
108409e887cSWarner Losh
109409e887cSWarner Losh20000711:
110409e887cSWarner Losh	/etc/security has been updated to print the inode number of
111409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
112409e887cSWarner Losh	in the number of changed programs the first time when you run
113409e887cSWarner Losh	mergemaster to get a new /etc/security.
114409e887cSWarner Losh
115673d13f2SWarner Losh20000710:
116673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
117673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
118673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
119673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
120673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
121673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
122673d13f2SWarner Losh	errors. (see below, 20000624).
123673d13f2SWarner Losh
124bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
1251dece4a9SWarner Losh
126673d13f2SWarner Losh20000709:
127c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
128c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
129c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
130673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
131673d13f2SWarner Losh
132e98e26cdSWarner Losh20000706:
133e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
134e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
135e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
136f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
137e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
138e98e26cdSWarner Losh	interrum if needed.
139e98e26cdSWarner Losh
140e98e26cdSWarner Losh20000705:
141e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
142e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
143e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
144e98e26cdSWarner Losh	details.
145e98e26cdSWarner Losh
146c373950eSWarner Losh20000704:
1472f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
1482f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
1492f961bc8SWarner Losh
1502f961bc8SWarner Losh20000704:
151c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
152c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
153c373950eSWarner Losh	rc.d scripts that haven't been updated.
154c373950eSWarner Losh
15527dc3a2bSWarner Losh20000630:
15627dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
15727dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
15827dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
15927dc3a2bSWarner Losh
160b8c215acSWarner Losh20000625:
161b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
16227dc3a2bSWarner Losh	system installed in order to build the system and kernel.
16327dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
16427dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
16527dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
16627dc3a2bSWarner Losh	were required.  You should check with the latest collections
16727dc3a2bSWarner Losh	to make sure that these haven't changed.
168b8c215acSWarner Losh
1697b990719SWarner Losh20000624:
1707b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
1717b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
1727b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1737b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
1747b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
1757b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
1767b990719SWarner Losh	date to the completion of the work.
1777b990719SWarner Losh
17827dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
17927dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
18027dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
18127dc3a2bSWarner Losh	recreate the random and urandom devices.
18227dc3a2bSWarner Losh
18381e54c50SWarner Losh20000622:
18481e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
18581e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
18681e54c50SWarner Losh	that used to be required when updating.
18781e54c50SWarner Losh
18839943833SWarner Losh20000621:
18939943833SWarner Losh	Scott Flatman <sf@aracnet.com> sent in a decent writeup on
1902a2f33fbSDaniel Baker	the config file update procedure.
1912a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
192c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
193a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
19439943833SWarner Losh
195290f9ad8SWarner Losh20000620:
196290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
197290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
198290f9ad8SWarner Losh	that workaround will no longer be required.
199290f9ad8SWarner Losh
20090fb6346SWarner Losh20000615:
20190fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
20290fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
20390fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
20490fb6346SWarner Losh	devices.
20590fb6346SWarner Losh
206f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
207f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
208f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
209f75f65bbSWarner Losh	may work).
210f75f65bbSWarner Losh
211ba26da8eSWarner Losh20000612:
212ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
213290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
214c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
215290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
216f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
217f54a3542SWarner Losh	NEWCARD for examples of the new format.
218290f9ad8SWarner Losh
219d65850ebSWarner Losh20000522:
220ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
221d65850ebSWarner Losh	building a kernel after this point is advised that they need
222d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
223d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
224d65850ebSWarner Losh
225d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
226d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
227d9583a00SWarner Losh	is recommended that you don't set this option until the problem
228d9583a00SWarner Losh	is resolved.
229d9583a00SWarner Losh
2308039cedeSWarner Losh20000513:
2318039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
2328039cedeSWarner Losh
233d65850ebSWarner Losh20000510:
2348039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
2358039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
2368039cedeSWarner Losh	is requires for the boot blocks to build properly.
2378039cedeSWarner Losh
2388039cedeSWarner Losh20000503:
2398039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
2408039cedeSWarner Losh	is now available.
2418039cedeSWarner Losh
242d65850ebSWarner Losh20000502:
243d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
244d65850ebSWarner Losh	connected to the kernel building instead.
245d65850ebSWarner Losh
2468039cedeSWarner Losh2000427:
2478039cedeSWarner Losh	You may need to build gperf
2488039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
2498039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
2508039cedeSWarner Losh	an option only in -current.
2518039cedeSWarner Losh
2522b8dd5f4SWarner Losh20000417:
2532b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
254f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
2552b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
2562b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
2572b8dd5f4SWarner Losh	before you reboot, you'll neeed to issue:
2582b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
2592b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
2602b8dd5f4SWarner Losh
2618d9f1945SWarner Losh20000320:
2622b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
2632b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
2642b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
2658d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
2662b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
2678d9f1945SWarner Losh
268f8ab1dd6SWarner Losh20000319:
269f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
270f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
271f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
272f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
273f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
274f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
275f8ab1dd6SWarner Losh
27619cada77SWarner Losh20000318:
277f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
27819cada77SWarner Losh	Large kernel changes are being committed and are in the
27919cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
28019cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
28119cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
28219cada77SWarner Losh	that you are loading are up to date.
283ba228352SWarner Losh
28419cada77SWarner Losh20000315:
2856d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
2866d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
2876d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
2886d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
2896d23c382SWarner Losh	boot.
2906d23c382SWarner Losh
2916d23c382SWarner Losh20000315:
29219cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
29319cada77SWarner Losh	to upgrade to 4.0 from 3.x.
29457199806SWarner Losh
295dc0dbf5cSWarner LoshCOMMON ITEMS:
296dc0dbf5cSWarner Losh
297a24eff53SWarner Losh	General Notes
298a24eff53SWarner Losh	-------------
299a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
300a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
301a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
302a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
303a24eff53SWarner Losh	or several minor releases, or when several months have passed
304a24eff53SWarner Losh	on the -current branch).
305a24eff53SWarner Losh
306dc0dbf5cSWarner Losh	To build a kernel
307dc0dbf5cSWarner Losh	-----------------
308ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
309f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
310ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
311ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
312ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
313dc0dbf5cSWarner Losh
314ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
315ba01eb20SWarner Losh	--------------------------------------------------------------
316ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
317ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
318ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
319ba01eb20SWarner Losh	make depend
320ba01eb20SWarner Losh	make
321ba01eb20SWarner Losh	make install
322ba01eb20SWarner Losh
323ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
324ba01eb20SWarner Losh
325ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
326ba01eb20SWarner Losh
327ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
328ba01eb20SWarner Losh	-----------------------------------------------------------
329759f0aefSWarner Losh	make world
330fdb9f54dSWarner Losh	Build a new kernel, see above.
331759f0aefSWarner Losh
3321dece4a9SWarner Losh	To upgrade from 4.x-stable to current
333ba26da8eSWarner Losh	-------------------------------------
334ba26da8eSWarner Losh	make buildworld
335ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
3369c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
337ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
338ba26da8eSWarner Losh	make installworld
339134d2e86SWarner Losh	[1]
340ba26da8eSWarner Losh	<reboot>
341ba26da8eSWarner Losh
342fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
343fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
344fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
345fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
346fdb9f54dSWarner Losh	the UPDATING entries.
347ba26da8eSWarner Losh
3481dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
3491dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
3501dece4a9SWarner Losh	your sources that you have read and understood all the recent
3511dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
3521dece4a9SWarner Losh	much fewer pitfalls.
3531dece4a9SWarner Losh
354134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
355134d2e86SWarner Losh	should disable them at this point so they don't crash your
356134d2e86SWarner Losh	system on reboot.
357134d2e86SWarner Losh
3589c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
3599c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
3609c1a7444SWarner Losh	configuration.
3619c1a7444SWarner Losh
362dc0dbf5cSWarner LoshFORMAT:
363dc0dbf5cSWarner Losh
364f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
3651fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
366f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
367f8ab1dd6SWarner Loshprevious releases if your system is older than this.
3681fc1a0dcSWarner Losh
3693645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
3703645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
371f8c77507SWarner Losh
37297d92980SPeter Wemm$FreeBSD$
373