xref: /freebsd/UPDATING (revision a6cd4f9de3dd59c158bd2c618bb052076618688d)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
4e72fd46aSWarner Losh<imp@village.org>.  Please send new entries directly to him.  See end
5e72fd46aSWarner Loshof file for further details.  For commonly done items, please see the
6e72fd46aSWarner LoshCOMMON ITEMS: section later in the file.
7e72fd46aSWarner Losh
8f34a9421SWarner LoshThis is for the 4.3 release branch.  All entries since 4.3 are an
9f34a9421SWarner Loshitemized list of commits to this branch, numbered from the beginning.
10f34a9421SWarner LoshBy this count, we're at 4.3.0p9
11f34a9421SWarner Losh
127b9786edSMark Murray20010709:
137b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
147b9786edSMark Murray	the ability of the shared library major number to handle.
157b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
167b9786edSMark Murray	solution is to rebuild those ports.
177b9786edSMark Murray
181d28950eSWarner Losh20010628:
191d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
201d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
211d28950eSWarner Losh
22e72fd46aSWarner Losh20010625:
23e72fd46aSWarner Losh	The pccard modem issue has been corrected.  OLDCARD support is
24e72fd46aSWarner Losh	still a little weak in -current.  slot 1 is known not to work
25e72fd46aSWarner Losh	on some TI based cardbus bridges.  Some cardbus bridges do not
26e72fd46aSWarner Losh	properly detect insert/removal events.  IRQ configuration needs
27e72fd46aSWarner Losh	more safety belts.
2816de1a07SWarner Losh
290d415dffSWarner Losh20010617:
30e72fd46aSWarner Losh	Softupdates problems have been corrected.
310d415dffSWarner Losh
320d415dffSWarner Losh20010614:
330d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
340d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
350d415dffSWarner Losh	kernel building methods.
360d415dffSWarner Losh
378b9959adSWarner Losh20010613:
388b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
398b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
40e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
41e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
428b9959adSWarner Losh
43e72fd46aSWarner Losh20010613:
448b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
45e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
46e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
478b9959adSWarner Losh
480d415dffSWarner Losh20010612:
490d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
500d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
510d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
520d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
530d415dffSWarner Losh	until this bug is fixed.
540d415dffSWarner Losh
55e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
56e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
57e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
58e72fd46aSWarner Losh
590d415dffSWarner Losh20010610:
600d415dffSWarner Losh	Locale names have changed to match other systems better.
610d415dffSWarner Losh
626ccdb5e4SWarner Losh20010604:
636ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
646ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
656ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
663590182eSWarner Losh	Interrupt storms look a lot like a hang.
673590182eSWarner Losh
683590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
693590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
703590182eSWarner Losh	it is).
713590182eSWarner Losh
723590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
733590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
743590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
753590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
766ccdb5e4SWarner Losh
770bc62786SWarner Losh20010530:
780bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
790bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
800bc62786SWarner Losh	a limited time.  If you see
810bc62786SWarner Losh
820bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
830bc62786SWarner Losh
840bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
850bc62786SWarner Losh	COPY=-C.
860bc62786SWarner Losh
8768a38c6cSWarner Losh20010525:
88b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
89c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
90c4f4a728SWarner Losh	definitely is in bad shape.
9168a38c6cSWarner Losh
92ed0f29caSWarner Losh20010521:
93ed0f29caSWarner Losh	Minor repo damanged has happened.  This may cause problems
94ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
95ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
96ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
97ed0f29caSWarner Losh	is
98ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
99ed0f29caSWarner Losh
10080c16af9SWarner Losh20010520:
10168a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
10280c16af9SWarner Losh
10380c16af9SWarner Losh20010519:
10480c16af9SWarner Losh	pccard has had much reorganizational work done to it over
10580c16af9SWarner Losh	the past few days.  Everything should still work, but if
10680c16af9SWarner Losh	not, please contact imp@freebsd.org.
10780c16af9SWarner Losh
108a45f2d05SWarner Losh20010517:
109a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
110a45f2d05SWarner Losh	userland at the same time.
111a45f2d05SWarner Losh
112a45f2d05SWarner Losh20010517:
113a45f2d05SWarner Losh	New ncurses imported.
114a45f2d05SWarner Losh
1152988afcaSWarner Losh20010512:
1162988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
1172988afcaSWarner Losh	will be the only way to go starting July 1.
1182988afcaSWarner Losh
11909946a51SWarner Losh20010502:
12009946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
12109946a51SWarner Losh
12209946a51SWarner Losh20010501:
12309946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
12409946a51SWarner Losh
12509946a51SWarner Losh20010430:
126a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
12709946a51SWarner Losh	go back in the water.
12809946a51SWarner Losh
12909946a51SWarner Losh20010429:
13009946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
13109946a51SWarner Losh	this date, but before the correction date.
13209946a51SWarner Losh
13391dd3b53SWarner Losh20010423:
13491dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
13591dd3b53SWarner Losh
13691dd3b53SWarner Losh20010411:
13791dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
13891dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
13991dd3b53SWarner Losh	Update only if you understand that you must not use the old
14091dd3b53SWarner Losh	fsck with the new kernel ever.
14191dd3b53SWarner Losh
142933b3269SWarner Losh20010330:
143933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
144c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
145933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
146933b3269SWarner Losh
147933b3269SWarner Losh20010319:
148933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
149933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
150933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
151f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
15209946a51SWarner Losh
15309946a51SWarner Losh20010315:
15409946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
15509946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
15609946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
157933b3269SWarner Losh
158933b3269SWarner Losh20010312:
159933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
160933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
161933b3269SWarner Losh
162933b3269SWarner Losh20010312:
163933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
164933b3269SWarner Losh	instead of ad-hoc.
165933b3269SWarner Losh
166933b3269SWarner Losh20010310:
167f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
168933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
169933b3269SWarner Losh	ssh might not work if you don't.
170933b3269SWarner Losh
17162353691SWarner Losh20010303:
17262353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
17362353691SWarner Losh	which means that you must include the miibus in your kernel if
17462353691SWarner Losh	you use the ed driver.
17562353691SWarner Losh
176d325cf65SWarner Losh20010220:
177d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
178d325cf65SWarner Losh	safe to go back into the water.
179d325cf65SWarner Losh
180024daae6SWarner Losh20010211:
181024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
182024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
183024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
184024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
185024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
186024daae6SWarner Losh
187024daae6SWarner Losh	To get to the new system, you'll need to use the following
188024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
189024daae6SWarner Losh	don't have to move this to the updating section.
190024daae6SWarner Losh
191024daae6SWarner Losh	To get around the installworld problem, do:
192024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
193024daae6SWarner Losh		# make install
194024daae6SWarner Losh		# cd /usr/src
195024daae6SWarner Losh		# make installworld
196024daae6SWarner Losh	If that doesn't work, then try:
197024daae6SWarner Losh		# make -k installworld
198024daae6SWarner Losh		# make installworld
199024daae6SWarner Losh
200024daae6SWarner Losh20010207:
201024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
202024daae6SWarner Losh	do not include devfs in your kernel as problems result.
203024daae6SWarner Losh
204024daae6SWarner Losh20010205:
2057595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
206024daae6SWarner Losh	Remove them from your config.
207024daae6SWarner Losh
2081e159248SWarner Losh20010122:
2091e159248SWarner Losh	****************************** WARNING ******************************
2101e159248SWarner Losh			buildkernel has been changed slightly
2111e159248SWarner Losh	****************************** WARNING ******************************
2121e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
2131e159248SWarner Losh	should update your scripts and make.conf accordingly.
2141e159248SWarner Losh
2151e159248SWarner Losh20010119:
2161e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
2171e159248SWarner Losh	This requires a new config to build correctly.
2181e159248SWarner Losh
219aac7dfeaSWarner Losh20010116:
220aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
221aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
222aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
223aac7dfeaSWarner Losh
224aac7dfeaSWarner Losh20010110:
225aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
226aac7dfeaSWarner Losh
227aac7dfeaSWarner Losh20010102:
228aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
229aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
230aac7dfeaSWarner Losh
23163c90c9eSWarner Losh20010101:
23263c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
23363c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
2345fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
23563c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
23663c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
23763c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
23863c90c9eSWarner Losh	might have been ignored by the -k option.
23963c90c9eSWarner Losh
2405fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
2415fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
2425fd2a895SWarner Losh	of this working.
2435fd2a895SWarner Losh
244aac7dfeaSWarner Losh20001228:
245aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
246aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
247aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
248aac7dfeaSWarner Losh
249de2bcc63SWarner Losh20001218:
250de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
251de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
252de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
253de2bcc63SWarner Losh	cards will not be recognized without it.
254de2bcc63SWarner Losh
255960773f7SWarner Losh20001205:
256960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
257960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
258960773f7SWarner Losh	adding the following in pam.conf:
259960773f7SWarner Losh
260960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
261960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
262960773f7SWarner Losh	sshd    session required        pam_permit.so
263960773f7SWarner Losh
2640acc635eSWarner Losh20001031:
2650acc635eSWarner Losh	cvs updated to 1.11.
2660acc635eSWarner Losh
2670acc635eSWarner Losh20001020:
2680acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
2690acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
2700acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
2710acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
2720acc635eSWarner Losh	workaround.
2730acc635eSWarner Losh
2740acc635eSWarner Losh20001010:
2750acc635eSWarner Losh	****************************** WARNING ******************************
2760acc635eSWarner Losh				Sendmail has been updated.
2770acc635eSWarner Losh	****************************** WARNING ******************************
2780acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
2790acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
2800acc635eSWarner Losh	  is set.
2810acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
2820acc635eSWarner Losh	  commands.
2830acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
2840acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
2850acc635eSWarner Losh	  in /usr/share/sendmail/cf.
2860acc635eSWarner Losh	o sendmail.cw changed to local-host-names
2870acc635eSWarner Losh
2880acc635eSWarner Losh	More details can be found at
2890acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
2900acc635eSWarner Losh
2916e98a146SWarner Losh20001009:
2926e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
2936e98a146SWarner Losh	your entire ports tree, or you will have problems.
2946e98a146SWarner Losh
2956e98a146SWarner Losh20001006:
296685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
2976e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
2986e98a146SWarner Losh	/usr/bin/miniperl.
2996e98a146SWarner Losh
300073113a4SWarner Losh20001005:
301073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
302685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
303073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
304073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
305073113a4SWarner Losh	tree for anything to work.
306073113a4SWarner Losh
3070acc635eSWarner Losh20000928:
3080acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
3090acc635eSWarner Losh
310be3885b3SWarner Losh20000916:
311be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
312be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
313be3885b3SWarner Losh	same time as your kernel.
314be3885b3SWarner Losh
31576ec9675SWarner Losh20000914:
31676ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
31776ec9675SWarner Losh	include the device will cause suspended laptops losing time
31876ec9675SWarner Losh	when they resume.  Include
31976ec9675SWarner Losh		device		pmtimer
32076ec9675SWarner Losh	in your config file and
32101b9a434SWarner Losh		hint.pmtimer.0.at="isa"
32276ec9675SWarner Losh	to your /boot/device.hints file.
32376ec9675SWarner Losh
324f4865386SMark Murray20000911:
325f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
326f4865386SMark Murray	rather than an option. The supplied kernel config files have
327f4865386SMark Murray	been updated. You will need to do something similar in your
328f4865386SMark Murray	own kernel config file.
329f4865386SMark Murray	Remove:
330f4865386SMark Murray		options		RANDOMDEV
331f4865386SMark Murray	Add:
332f4865386SMark Murray		device		random
333f4865386SMark Murray	If you prefer to load the loadable module, you need to do
334f4865386SMark Murray	nothing.
335f4865386SMark Murray
336d594498fSWarner Losh20000909:
337d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
338d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
339d594498fSWarner Losh	reflect this if you load this module at boot time.
340d594498fSWarner Losh	The line should read:
341d594498fSWarner Losh		random_load="YES"
342d594498fSWarner Losh
3430deb7ddcSWarner Losh20000907:
3440deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
34516eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
34616eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
34716eb772dSWarner Losh	sure you don't have model loading problems which might at
34816eb772dSWarner Losh	first blush appear related to SMP.
34952bf24e7SWarner Losh
3505a01880bSWarner Losh20000906:
3515a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
3525a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
3535a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
3545a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
3555a01880bSWarner Losh	don't have one, and you have host.conf.
3565a01880bSWarner Losh
3572b41163cSWarner Losh20000905:
35838d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
35938d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
36038d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
36138d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
36238d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
36338d6ecd2SWarner Losh
36438d6ecd2SWarner Losh20000905:
3658aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
3668aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
3678aab4bc7SWarner Losh	is /boot/kernel.
3688aab4bc7SWarner Losh
3698aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
37038d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
37138d6ecd2SWarner Losh	installkernel/installworld dance.
3722b41163cSWarner Losh
373d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
374d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
375d594498fSWarner Losh	modules in that directory instead of finding them in the correct
376d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
377d594498fSWarner Losh	is that the linux module crashes your machine after the update.
378d594498fSWarner Losh
379d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
380d594498fSWarner Losh		mv /modules.old /boot/kernel.old
381d594498fSWarner Losh		chflags noschg /kernel.old
382d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
383d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
384d594498fSWarner Losh	fi
385d594498fSWarner Losh
386c22a309cSWarner Losh20000904:
387c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
388c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
389c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
390c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
391c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
392c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
393c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
394c22a309cSWarner Losh	is not likely to be generated.
395c22a309cSWarner Losh
396fdb9f54dSWarner Losh20000825:
397fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
3989c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
3999c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
4009c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
4019c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
4029c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
4039c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
4049c1a7444SWarner Losh	kernel.
4059c1a7444SWarner Losh
4069c1a7444SWarner Losh20000821:
4079c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
4089c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
4099c1a7444SWarner Losh	/boot/loader.conf.
410fdb9f54dSWarner Losh
4118f250aa7SWarner Losh20000812:
4125da0d091SWarner Losh	suidperl is now always built and installed on the system, but
4135da0d091SWarner Losh	with permissions of 511.  If you have applications that use
4145da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
4155da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
4165da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
4175da0d091SWarner Losh	will fix this until the next build.
4185da0d091SWarner Losh
4195da0d091SWarner Losh20000812:
4208f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
4218f250aa7SWarner Losh	visible changes that may immediately affect your configuration
4228f250aa7SWarner Losh	include:
4238f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
4248f250aa7SWarner Losh	- newaliases limited to root and trusted users
4258f250aa7SWarner Losh	- MSA port (587) turned on by default
4268f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
4278f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
4288f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
4298f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
4308f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
4318f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
4328f250aa7SWarner Losh
43371c38472SWarner Losh20000810:
43471c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
43571c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
43671c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
43771c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
43871c38472SWarner Losh	specific use for it.
43971c38472SWarner Losh
44071c38472SWarner Losh20000729:
44171c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
44271c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
44371c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
44471c38472SWarner Losh	afterwards (unless the variables already are set, of course):
44571c38472SWarner Losh		# Enable network daemons for user convenience.
44671c38472SWarner Losh		inetd_enable="YES"
44771c38472SWarner Losh		portmap_enable="YES"
44871c38472SWarner Losh		sendmail_enable="YES"
44971c38472SWarner Losh
45071c38472SWarner Losh20000728:
45171c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
45271c38472SWarner Losh	will need to change that to nullfs_load="YES".
45371c38472SWarner Losh
4541dece4a9SWarner Losh20000728:
4551dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
4561dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
4571dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
4581dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
4591dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
4601dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
4611dece4a9SWarner Losh	to /MYKERNEL.
4621dece4a9SWarner Losh
463409e887cSWarner Losh20000711:
464409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
465409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
466409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
467409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
468409e887cSWarner Losh	for details on potential problems that you might have and how
469409e887cSWarner Losh	to get around them.
470409e887cSWarner Losh
471409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
472409e887cSWarner Losh	clauses above, you needn't worry.
473409e887cSWarner Losh
474409e887cSWarner Losh20000711:
475409e887cSWarner Losh	/etc/security has been updated to print the inode number of
476409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
477409e887cSWarner Losh	in the number of changed programs the first time when you run
478409e887cSWarner Losh	mergemaster to get a new /etc/security.
479409e887cSWarner Losh
480673d13f2SWarner Losh20000710:
481673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
482673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
483673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
484673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
485673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
486673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
487673d13f2SWarner Losh	errors. (see below, 20000624).
488673d13f2SWarner Losh
489bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
4901dece4a9SWarner Losh
491673d13f2SWarner Losh20000709:
492c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
493c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
494c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
495673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
496673d13f2SWarner Losh
497e98e26cdSWarner Losh20000706:
498e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
499e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
500e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
501f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
502e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
5032c021c6cSMark Ovens	interim if needed.
504e98e26cdSWarner Losh
505e98e26cdSWarner Losh20000705:
506e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
507e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
508e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
509e98e26cdSWarner Losh	details.
510e98e26cdSWarner Losh
511c373950eSWarner Losh20000704:
5122f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
5132f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
5142f961bc8SWarner Losh
5152f961bc8SWarner Losh20000704:
516c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
517c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
518c373950eSWarner Losh	rc.d scripts that haven't been updated.
519c373950eSWarner Losh
52027dc3a2bSWarner Losh20000630:
52127dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
52227dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
52327dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
52427dc3a2bSWarner Losh
525b8c215acSWarner Losh20000625:
526b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
52727dc3a2bSWarner Losh	system installed in order to build the system and kernel.
52827dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
52927dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
53027dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
53127dc3a2bSWarner Losh	were required.  You should check with the latest collections
53227dc3a2bSWarner Losh	to make sure that these haven't changed.
533b8c215acSWarner Losh
5347b990719SWarner Losh20000624:
5357b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
5367b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
5377b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
5387b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
5397b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
5407b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
5417b990719SWarner Losh	date to the completion of the work.
5427b990719SWarner Losh
54327dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
54427dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
54527dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
54627dc3a2bSWarner Losh	recreate the random and urandom devices.
54727dc3a2bSWarner Losh
54881e54c50SWarner Losh20000622:
54981e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
55081e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
55181e54c50SWarner Losh	that used to be required when updating.
55281e54c50SWarner Losh
55339943833SWarner Losh20000621:
5542c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
5552a2f33fbSDaniel Baker	the config file update procedure.
5562a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
557c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
558a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
55939943833SWarner Losh
560290f9ad8SWarner Losh20000620:
561290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
562290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
563290f9ad8SWarner Losh	that workaround will no longer be required.
564290f9ad8SWarner Losh
56590fb6346SWarner Losh20000615:
56690fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
56790fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
56890fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
56990fb6346SWarner Losh	devices.
57090fb6346SWarner Losh
571f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
572f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
573f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
574f75f65bbSWarner Losh	may work).
575f75f65bbSWarner Losh
576ba26da8eSWarner Losh20000612:
577ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
578290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
579c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
580290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
581f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
582f54a3542SWarner Losh	NEWCARD for examples of the new format.
583290f9ad8SWarner Losh
584d65850ebSWarner Losh20000522:
585ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
586d65850ebSWarner Losh	building a kernel after this point is advised that they need
587d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
588d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
589d65850ebSWarner Losh
590d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
591d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
592d9583a00SWarner Losh	is recommended that you don't set this option until the problem
593d9583a00SWarner Losh	is resolved.
594d9583a00SWarner Losh
5958039cedeSWarner Losh20000513:
5968039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
5978039cedeSWarner Losh
598d65850ebSWarner Losh20000510:
5998039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
6008039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
6018039cedeSWarner Losh	is requires for the boot blocks to build properly.
6028039cedeSWarner Losh
6038039cedeSWarner Losh20000503:
6048039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
6058039cedeSWarner Losh	is now available.
6068039cedeSWarner Losh
607d65850ebSWarner Losh20000502:
608d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
609d65850ebSWarner Losh	connected to the kernel building instead.
610d65850ebSWarner Losh
611be149406SNik Clayton20000427:
6128039cedeSWarner Losh	You may need to build gperf
6138039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
6148039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
6158039cedeSWarner Losh	an option only in -current.
6168039cedeSWarner Losh
6172b8dd5f4SWarner Losh20000417:
6182b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
619f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
6202b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
6212b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
6222c021c6cSMark Ovens	before you reboot, you'll need to issue:
6232b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
6242b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
6252b8dd5f4SWarner Losh
6268d9f1945SWarner Losh20000320:
6272b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
6282b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
6292b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
6308d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
6312b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
6328d9f1945SWarner Losh
633f8ab1dd6SWarner Losh20000319:
634f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
635f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
636f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
637f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
638f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
639f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
640f8ab1dd6SWarner Losh
64119cada77SWarner Losh20000318:
642f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
64319cada77SWarner Losh	Large kernel changes are being committed and are in the
64419cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
64519cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
64619cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
64719cada77SWarner Losh	that you are loading are up to date.
648ba228352SWarner Losh
64919cada77SWarner Losh20000315:
6506d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
6516d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
6526d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
6536d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
6546d23c382SWarner Losh	boot.
6556d23c382SWarner Losh
6566d23c382SWarner Losh20000315:
65719cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
65819cada77SWarner Losh	to upgrade to 4.0 from 3.x.
65957199806SWarner Losh
660dc0dbf5cSWarner LoshCOMMON ITEMS:
661dc0dbf5cSWarner Losh
662a24eff53SWarner Losh	General Notes
663a24eff53SWarner Losh	-------------
664a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
665a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
666a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
667a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
668a24eff53SWarner Losh	or several minor releases, or when several months have passed
669a24eff53SWarner Losh	on the -current branch).
670a24eff53SWarner Losh
671dc0dbf5cSWarner Losh	To build a kernel
672dc0dbf5cSWarner Losh	-----------------
673ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
674f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
675ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
6761e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
6771e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
678dc0dbf5cSWarner Losh
679ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
680ba01eb20SWarner Losh	--------------------------------------------------------------
681ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
682ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
683ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
684ba01eb20SWarner Losh	make depend
685ba01eb20SWarner Losh	make
686ba01eb20SWarner Losh	make install
687ba01eb20SWarner Losh
688ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
689ba01eb20SWarner Losh
690ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
691ba01eb20SWarner Losh
692ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
693ba01eb20SWarner Losh	-----------------------------------------------------------
694759f0aefSWarner Losh	make world
695fdb9f54dSWarner Losh	Build a new kernel, see above.
696759f0aefSWarner Losh
6971dece4a9SWarner Losh	To upgrade from 4.x-stable to current
698ba26da8eSWarner Losh	-------------------------------------
699ba26da8eSWarner Losh	make buildworld
7001e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7017595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
7021e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
703ee6e1fc3SWarner Losh	reboot in single user [3]
704ba26da8eSWarner Losh	make installworld
705a6cd4f9dSWarner Losh	mergemaster		[4]
706134d2e86SWarner Losh	[1]
707ba26da8eSWarner Losh	<reboot>
708ba26da8eSWarner Losh
709fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
710fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
711fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
712fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
713fdb9f54dSWarner Losh	the UPDATING entries.
714ba26da8eSWarner Losh
7151dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
7161dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
7171dece4a9SWarner Losh	your sources that you have read and understood all the recent
7181dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
7191dece4a9SWarner Losh	much fewer pitfalls.
7201dece4a9SWarner Losh
721134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
722134d2e86SWarner Losh	should disable them at this point so they don't crash your
723134d2e86SWarner Losh	system on reboot.
724134d2e86SWarner Losh
7259c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
7269c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
7279c1a7444SWarner Losh	configuration.
7289c1a7444SWarner Losh
729ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
730ee6e1fc3SWarner Losh		fsck -p
731ee6e1fc3SWarner Losh		mount -u /
732ee6e1fc3SWarner Losh		mount -a
733ee6e1fc3SWarner Losh		cd /usr/src
734ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
735ee6e1fc3SWarner Losh
736a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
737a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
738a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
739a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
740a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
741a6cd4f9dSWarner Losh	for potential gotchas.
742a6cd4f9dSWarner Losh
743dc0dbf5cSWarner LoshFORMAT:
744dc0dbf5cSWarner Losh
745f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
7461fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
747f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
748f8ab1dd6SWarner Loshprevious releases if your system is older than this.
7491fc1a0dcSWarner Losh
7503645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
7513645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
752f8c77507SWarner Losh
753e72fd46aSWarner LoshCopyright information:
754e72fd46aSWarner Losh
755e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
756e72fd46aSWarner Losh
757e72fd46aSWarner LoshRedistribution, translation and use, with or without modification, in
758e72fd46aSWarner Loshfull or in part, are permitted provided that the above copyright
759e72fd46aSWarner Loshnotice is retained.
760e72fd46aSWarner Losh
761e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
762e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
763e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
764e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
765e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
766e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
767e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
768e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
769e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
770e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
771e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
772e72fd46aSWarner Losh
773e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
774e72fd46aSWarner Loshauthor a beer.
775e72fd46aSWarner Losh
77697d92980SPeter Wemm$FreeBSD$
777