xref: /freebsd/UPDATING (revision 22306abc9e52b4acb70c7639290398283e7db864)
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
83c293725SWarner Losh20010919:
93c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
103c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
113c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
12772730c7SWarner Losh	workaround is to add
133c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
143c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
153c293725SWarner Losh	can be removed afterwards.
163c293725SWarner Losh
173c293725SWarner Losh	A proper fix to the buildworld target is needed.
183c293725SWarner Losh
193c293725SWarner Losh20010918:
203c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
213c293725SWarner Losh	NFS may be unstable after this date.
223c293725SWarner Losh
233c293725SWarner Losh20010912:
243c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
253c293725SWarner Losh	the kernel.  While a few problems were introduced in the
263c293725SWarner Losh	initial commit, most of the major ones have been found and
273c293725SWarner Losh	corrected.
283c293725SWarner Losh
293c293725SWarner Losh20010901:
303c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
313c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
323c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
333c293725SWarner Losh	have been rectified around this date.
343c293725SWarner Losh
3598b17b95SWarner Losh20010823:
3698b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
3798b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
3898b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
3998b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
4098b17b95SWarner Losh 	sure that user or group bind has read (and not write)
4198b17b95SWarner Losh 	permission for your name server configuration and that it
4298b17b95SWarner Losh 	has read and write permission for your slave zone files and
4398b17b95SWarner Losh 	directory.
4498b17b95SWarner Losh
4598b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
4698b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
4798b17b95SWarner Losh
4898b17b95SWarner Losh 		named_flags=
4998b17b95SWarner Losh
507b9786edSMark Murray20010709:
517b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
527b9786edSMark Murray	the ability of the shared library major number to handle.
537b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
547b9786edSMark Murray	solution is to rebuild those ports.
557b9786edSMark Murray
561d28950eSWarner Losh20010628:
571d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
581d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
591d28950eSWarner Losh
60e72fd46aSWarner Losh20010625:
6198b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
6298b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
6398b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
6498b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
6598b17b95SWarner Losh	IRQ configuration needs more safety belts.
6616de1a07SWarner Losh
670d415dffSWarner Losh20010617:
68e72fd46aSWarner Losh	Softupdates problems have been corrected.
690d415dffSWarner Losh
700d415dffSWarner Losh20010614:
710d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
720d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
730d415dffSWarner Losh	kernel building methods.
740d415dffSWarner Losh
758b9959adSWarner Losh20010613:
768b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
778b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
78e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
79e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
808b9959adSWarner Losh
81e72fd46aSWarner Losh20010613:
828b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
83e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
84e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
858b9959adSWarner Losh
860d415dffSWarner Losh20010612:
870d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
880d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
890d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
900d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
910d415dffSWarner Losh	until this bug is fixed.
920d415dffSWarner Losh
93e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
94e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
95e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
96e72fd46aSWarner Losh
970d415dffSWarner Losh20010610:
980d415dffSWarner Losh	Locale names have changed to match other systems better.
990d415dffSWarner Losh
1006ccdb5e4SWarner Losh20010604:
1016ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
1026ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
1036ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
1043590182eSWarner Losh	Interrupt storms look a lot like a hang.
1053590182eSWarner Losh
1063590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
1073590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
1083590182eSWarner Losh	it is).
1093590182eSWarner Losh
1103590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
1113590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
1123590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
1133590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
1146ccdb5e4SWarner Losh
1150bc62786SWarner Losh20010530:
1160bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
1170bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
1180bc62786SWarner Losh	a limited time.  If you see
1190bc62786SWarner Losh
1200bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
1210bc62786SWarner Losh
1220bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
1230bc62786SWarner Losh	COPY=-C.
1240bc62786SWarner Losh
12568a38c6cSWarner Losh20010525:
126b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
127c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
128c4f4a728SWarner Losh	definitely is in bad shape.
12968a38c6cSWarner Losh
130ed0f29caSWarner Losh20010521:
131f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
132ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
133ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
134ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
135ed0f29caSWarner Losh	is
136ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
137ed0f29caSWarner Losh
13880c16af9SWarner Losh20010520:
13968a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
14080c16af9SWarner Losh
14180c16af9SWarner Losh20010519:
14280c16af9SWarner Losh	pccard has had much reorganizational work done to it over
14380c16af9SWarner Losh	the past few days.  Everything should still work, but if
14480c16af9SWarner Losh	not, please contact imp@freebsd.org.
14580c16af9SWarner Losh
146a45f2d05SWarner Losh20010517:
147a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
148a45f2d05SWarner Losh	userland at the same time.
149a45f2d05SWarner Losh
150a45f2d05SWarner Losh20010517:
151a45f2d05SWarner Losh	New ncurses imported.
152a45f2d05SWarner Losh
1532988afcaSWarner Losh20010512:
1542988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
1552988afcaSWarner Losh	will be the only way to go starting July 1.
1562988afcaSWarner Losh
15709946a51SWarner Losh20010502:
15809946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
15909946a51SWarner Losh
16009946a51SWarner Losh20010501:
16109946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
16209946a51SWarner Losh
16309946a51SWarner Losh20010430:
164a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
16509946a51SWarner Losh	go back in the water.
16609946a51SWarner Losh
16709946a51SWarner Losh20010429:
16809946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
16909946a51SWarner Losh	this date, but before the correction date.
17009946a51SWarner Losh
17191dd3b53SWarner Losh20010423:
17291dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
17391dd3b53SWarner Losh
17491dd3b53SWarner Losh20010411:
17591dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
17691dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
17791dd3b53SWarner Losh	Update only if you understand that you must not use the old
17891dd3b53SWarner Losh	fsck with the new kernel ever.
17991dd3b53SWarner Losh
180933b3269SWarner Losh20010330:
181933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
182c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
183933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
184933b3269SWarner Losh
185933b3269SWarner Losh20010319:
186933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
187933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
188933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
189f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
19009946a51SWarner Losh
19109946a51SWarner Losh20010315:
19209946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
19309946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
19409946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
195933b3269SWarner Losh
196933b3269SWarner Losh20010312:
197933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
198933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
199933b3269SWarner Losh
200933b3269SWarner Losh20010312:
201933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
202933b3269SWarner Losh	instead of ad-hoc.
203933b3269SWarner Losh
204933b3269SWarner Losh20010310:
205f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
206933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
207933b3269SWarner Losh	ssh might not work if you don't.
208933b3269SWarner Losh
20962353691SWarner Losh20010303:
21062353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
21162353691SWarner Losh	which means that you must include the miibus in your kernel if
21262353691SWarner Losh	you use the ed driver.
21362353691SWarner Losh
214d325cf65SWarner Losh20010220:
215d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
216d325cf65SWarner Losh	safe to go back into the water.
217d325cf65SWarner Losh
218024daae6SWarner Losh20010211:
219024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
220024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
221024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
222024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
223024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
224024daae6SWarner Losh
225024daae6SWarner Losh	To get to the new system, you'll need to use the following
226024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
227024daae6SWarner Losh	don't have to move this to the updating section.
228024daae6SWarner Losh
229024daae6SWarner Losh	To get around the installworld problem, do:
230024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
231024daae6SWarner Losh		# make install
232024daae6SWarner Losh		# cd /usr/src
233024daae6SWarner Losh		# make installworld
234024daae6SWarner Losh	If that doesn't work, then try:
235024daae6SWarner Losh		# make -k installworld
236024daae6SWarner Losh		# make installworld
237024daae6SWarner Losh
238024daae6SWarner Losh20010207:
239024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
240024daae6SWarner Losh	do not include devfs in your kernel as problems result.
241024daae6SWarner Losh
242024daae6SWarner Losh20010205:
2437595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
244024daae6SWarner Losh	Remove them from your config.
245024daae6SWarner Losh
2461e159248SWarner Losh20010122:
2471e159248SWarner Losh	****************************** WARNING ******************************
2481e159248SWarner Losh			buildkernel has been changed slightly
2491e159248SWarner Losh	****************************** WARNING ******************************
2501e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
2511e159248SWarner Losh	should update your scripts and make.conf accordingly.
2521e159248SWarner Losh
2531e159248SWarner Losh20010119:
2541e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
2551e159248SWarner Losh	This requires a new config to build correctly.
2561e159248SWarner Losh
257aac7dfeaSWarner Losh20010116:
258aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
259aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
260aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
261aac7dfeaSWarner Losh
262aac7dfeaSWarner Losh20010110:
263aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
264aac7dfeaSWarner Losh
265aac7dfeaSWarner Losh20010102:
266aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
267aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
268aac7dfeaSWarner Losh
26963c90c9eSWarner Losh20010101:
27063c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
27163c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
2725fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
27363c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
27463c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
27563c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
27663c90c9eSWarner Losh	might have been ignored by the -k option.
27763c90c9eSWarner Losh
2785fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
2795fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
2805fd2a895SWarner Losh	of this working.
2815fd2a895SWarner Losh
282aac7dfeaSWarner Losh20001228:
283aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
284aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
285aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
286aac7dfeaSWarner Losh
287de2bcc63SWarner Losh20001218:
288de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
289de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
290de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
291de2bcc63SWarner Losh	cards will not be recognized without it.
292de2bcc63SWarner Losh
293960773f7SWarner Losh20001205:
294960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
295960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
296960773f7SWarner Losh	adding the following in pam.conf:
297960773f7SWarner Losh
298960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
299960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
300960773f7SWarner Losh	sshd    session required        pam_permit.so
301960773f7SWarner Losh
3020acc635eSWarner Losh20001031:
3030acc635eSWarner Losh	cvs updated to 1.11.
3040acc635eSWarner Losh
3050acc635eSWarner Losh20001020:
3060acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
3070acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
3080acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
3090acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
3100acc635eSWarner Losh	workaround.
3110acc635eSWarner Losh
3120acc635eSWarner Losh20001010:
3130acc635eSWarner Losh	****************************** WARNING ******************************
3140acc635eSWarner Losh				Sendmail has been updated.
3150acc635eSWarner Losh	****************************** WARNING ******************************
3160acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
3170acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
3180acc635eSWarner Losh	  is set.
3190acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
3200acc635eSWarner Losh	  commands.
3210acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
3220acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
3230acc635eSWarner Losh	  in /usr/share/sendmail/cf.
3240acc635eSWarner Losh	o sendmail.cw changed to local-host-names
3250acc635eSWarner Losh
3260acc635eSWarner Losh	More details can be found at
3270acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
3280acc635eSWarner Losh
3296e98a146SWarner Losh20001009:
3306e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
3316e98a146SWarner Losh	your entire ports tree, or you will have problems.
3326e98a146SWarner Losh
3336e98a146SWarner Losh20001006:
334685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
3356e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
3366e98a146SWarner Losh	/usr/bin/miniperl.
3376e98a146SWarner Losh
338073113a4SWarner Losh20001005:
339073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
340685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
341073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
342073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
343073113a4SWarner Losh	tree for anything to work.
344073113a4SWarner Losh
3450acc635eSWarner Losh20000928:
3460acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
3470acc635eSWarner Losh
348be3885b3SWarner Losh20000916:
349be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
350be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
351be3885b3SWarner Losh	same time as your kernel.
352be3885b3SWarner Losh
35376ec9675SWarner Losh20000914:
35476ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
35576ec9675SWarner Losh	include the device will cause suspended laptops losing time
35676ec9675SWarner Losh	when they resume.  Include
35776ec9675SWarner Losh		device		pmtimer
35876ec9675SWarner Losh	in your config file and
35901b9a434SWarner Losh		hint.pmtimer.0.at="isa"
36076ec9675SWarner Losh	to your /boot/device.hints file.
36176ec9675SWarner Losh
362f4865386SMark Murray20000911:
363f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
364f4865386SMark Murray	rather than an option. The supplied kernel config files have
365f4865386SMark Murray	been updated. You will need to do something similar in your
366f4865386SMark Murray	own kernel config file.
367f4865386SMark Murray	Remove:
368f4865386SMark Murray		options		RANDOMDEV
369f4865386SMark Murray	Add:
370f4865386SMark Murray		device		random
371f4865386SMark Murray	If you prefer to load the loadable module, you need to do
372f4865386SMark Murray	nothing.
373f4865386SMark Murray
374d594498fSWarner Losh20000909:
375d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
376d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
377d594498fSWarner Losh	reflect this if you load this module at boot time.
378d594498fSWarner Losh	The line should read:
379d594498fSWarner Losh		random_load="YES"
380d594498fSWarner Losh
3810deb7ddcSWarner Losh20000907:
3820deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
38316eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
38416eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
38516eb772dSWarner Losh	sure you don't have model loading problems which might at
38616eb772dSWarner Losh	first blush appear related to SMP.
38752bf24e7SWarner Losh
3885a01880bSWarner Losh20000906:
3895a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
3905a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
3915a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
3925a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
3935a01880bSWarner Losh	don't have one, and you have host.conf.
3945a01880bSWarner Losh
3952b41163cSWarner Losh20000905:
39638d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
39738d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
39838d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
39938d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
40038d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
40138d6ecd2SWarner Losh
40238d6ecd2SWarner Losh20000905:
4038aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
4048aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
4058aab4bc7SWarner Losh	is /boot/kernel.
4068aab4bc7SWarner Losh
4078aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
40838d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
40938d6ecd2SWarner Losh	installkernel/installworld dance.
4102b41163cSWarner Losh
411d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
412d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
413d594498fSWarner Losh	modules in that directory instead of finding them in the correct
414d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
415d594498fSWarner Losh	is that the linux module crashes your machine after the update.
416d594498fSWarner Losh
417d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
418d594498fSWarner Losh		mv /modules.old /boot/kernel.old
419d594498fSWarner Losh		chflags noschg /kernel.old
420d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
421d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
422d594498fSWarner Losh	fi
423d594498fSWarner Losh
424c22a309cSWarner Losh20000904:
425c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
426c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
427c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
428c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
429c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
430c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
431c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
432c22a309cSWarner Losh	is not likely to be generated.
433c22a309cSWarner Losh
434fdb9f54dSWarner Losh20000825:
435fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
4369c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
4379c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
4389c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
4399c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
4409c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
4419c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
4429c1a7444SWarner Losh	kernel.
4439c1a7444SWarner Losh
4449c1a7444SWarner Losh20000821:
4459c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
4469c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
4479c1a7444SWarner Losh	/boot/loader.conf.
448fdb9f54dSWarner Losh
4498f250aa7SWarner Losh20000812:
4505da0d091SWarner Losh	suidperl is now always built and installed on the system, but
4515da0d091SWarner Losh	with permissions of 511.  If you have applications that use
4525da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
4535da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
4545da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
4555da0d091SWarner Losh	will fix this until the next build.
4565da0d091SWarner Losh
4575da0d091SWarner Losh20000812:
4588f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
4598f250aa7SWarner Losh	visible changes that may immediately affect your configuration
4608f250aa7SWarner Losh	include:
4618f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
4628f250aa7SWarner Losh	- newaliases limited to root and trusted users
4638f250aa7SWarner Losh	- MSA port (587) turned on by default
4648f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
4658f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
4668f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
4678f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
4688f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
4698f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
4708f250aa7SWarner Losh
47171c38472SWarner Losh20000810:
47271c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
47371c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
47471c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
47571c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
47671c38472SWarner Losh	specific use for it.
47771c38472SWarner Losh
47871c38472SWarner Losh20000729:
47971c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
48071c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
48171c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
48271c38472SWarner Losh	afterwards (unless the variables already are set, of course):
48371c38472SWarner Losh		# Enable network daemons for user convenience.
48471c38472SWarner Losh		inetd_enable="YES"
48571c38472SWarner Losh		portmap_enable="YES"
48671c38472SWarner Losh		sendmail_enable="YES"
48771c38472SWarner Losh
48871c38472SWarner Losh20000728:
48971c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
49071c38472SWarner Losh	will need to change that to nullfs_load="YES".
49171c38472SWarner Losh
4921dece4a9SWarner Losh20000728:
4931dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
4941dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
4951dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
4961dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
4971dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
4981dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
4991dece4a9SWarner Losh	to /MYKERNEL.
5001dece4a9SWarner Losh
501409e887cSWarner Losh20000711:
502409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
503409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
504409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
505409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
506409e887cSWarner Losh	for details on potential problems that you might have and how
507409e887cSWarner Losh	to get around them.
508409e887cSWarner Losh
509409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
510409e887cSWarner Losh	clauses above, you needn't worry.
511409e887cSWarner Losh
512409e887cSWarner Losh20000711:
513409e887cSWarner Losh	/etc/security has been updated to print the inode number of
514409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
515409e887cSWarner Losh	in the number of changed programs the first time when you run
516409e887cSWarner Losh	mergemaster to get a new /etc/security.
517409e887cSWarner Losh
518673d13f2SWarner Losh20000710:
519673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
520673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
521673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
522673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
523673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
524673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
525673d13f2SWarner Losh	errors. (see below, 20000624).
526673d13f2SWarner Losh
527bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
5281dece4a9SWarner Losh
529673d13f2SWarner Losh20000709:
530c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
531c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
532c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
533673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
534673d13f2SWarner Losh
535e98e26cdSWarner Losh20000706:
536e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
537e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
538e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
539f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
540e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
5412c021c6cSMark Ovens	interim if needed.
542e98e26cdSWarner Losh
543e98e26cdSWarner Losh20000705:
544e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
545e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
546e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
547e98e26cdSWarner Losh	details.
548e98e26cdSWarner Losh
549c373950eSWarner Losh20000704:
5502f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
5512f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
5522f961bc8SWarner Losh
5532f961bc8SWarner Losh20000704:
554c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
555c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
556c373950eSWarner Losh	rc.d scripts that haven't been updated.
557c373950eSWarner Losh
55827dc3a2bSWarner Losh20000630:
55927dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
56027dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
56127dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
56227dc3a2bSWarner Losh
563b8c215acSWarner Losh20000625:
564b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
56527dc3a2bSWarner Losh	system installed in order to build the system and kernel.
56627dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
56727dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
56827dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
56927dc3a2bSWarner Losh	were required.  You should check with the latest collections
57027dc3a2bSWarner Losh	to make sure that these haven't changed.
571b8c215acSWarner Losh
5727b990719SWarner Losh20000624:
5737b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
5747b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
5757b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
5767b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
5777b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
5787b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
5797b990719SWarner Losh	date to the completion of the work.
5807b990719SWarner Losh
58127dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
58227dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
58327dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
58427dc3a2bSWarner Losh	recreate the random and urandom devices.
58527dc3a2bSWarner Losh
58681e54c50SWarner Losh20000622:
58781e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
58881e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
58981e54c50SWarner Losh	that used to be required when updating.
59081e54c50SWarner Losh
59139943833SWarner Losh20000621:
5922c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
5932a2f33fbSDaniel Baker	the config file update procedure.
5942a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
595c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
596a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
59739943833SWarner Losh
598290f9ad8SWarner Losh20000620:
599290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
600290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
601290f9ad8SWarner Losh	that workaround will no longer be required.
602290f9ad8SWarner Losh
60390fb6346SWarner Losh20000615:
60490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
60590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
60690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
60790fb6346SWarner Losh	devices.
60890fb6346SWarner Losh
609f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
610f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
611f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
612f75f65bbSWarner Losh	may work).
613f75f65bbSWarner Losh
614ba26da8eSWarner Losh20000612:
615ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
616290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
617c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
618290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
619f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
620f54a3542SWarner Losh	NEWCARD for examples of the new format.
621290f9ad8SWarner Losh
622d65850ebSWarner Losh20000522:
623ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
624d65850ebSWarner Losh	building a kernel after this point is advised that they need
625d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
626d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
627d65850ebSWarner Losh
628d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
629d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
630d9583a00SWarner Losh	is recommended that you don't set this option until the problem
631d9583a00SWarner Losh	is resolved.
632d9583a00SWarner Losh
6338039cedeSWarner Losh20000513:
6348039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
6358039cedeSWarner Losh
636d65850ebSWarner Losh20000510:
6378039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
6388039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
6398039cedeSWarner Losh	is requires for the boot blocks to build properly.
6408039cedeSWarner Losh
6418039cedeSWarner Losh20000503:
6428039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
6438039cedeSWarner Losh	is now available.
6448039cedeSWarner Losh
645d65850ebSWarner Losh20000502:
646d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
647d65850ebSWarner Losh	connected to the kernel building instead.
648d65850ebSWarner Losh
649be149406SNik Clayton20000427:
6508039cedeSWarner Losh	You may need to build gperf
6518039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
6528039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
6538039cedeSWarner Losh	an option only in -current.
6548039cedeSWarner Losh
6552b8dd5f4SWarner Losh20000417:
6562b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
657f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
6582b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
6592b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
6602c021c6cSMark Ovens	before you reboot, you'll need to issue:
6612b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
6622b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
6632b8dd5f4SWarner Losh
6648d9f1945SWarner Losh20000320:
6652b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
6662b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
6672b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
6688d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
6692b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
6708d9f1945SWarner Losh
671f8ab1dd6SWarner Losh20000319:
672f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
673f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
674f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
675f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
676f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
677f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
678f8ab1dd6SWarner Losh
67919cada77SWarner Losh20000318:
680f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
68119cada77SWarner Losh	Large kernel changes are being committed and are in the
68219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
68319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
68419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
68519cada77SWarner Losh	that you are loading are up to date.
686ba228352SWarner Losh
68719cada77SWarner Losh20000315:
6886d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
6896d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
6906d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
6916d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
6926d23c382SWarner Losh	boot.
6936d23c382SWarner Losh
6946d23c382SWarner Losh20000315:
69519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
69619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
69757199806SWarner Losh
698dc0dbf5cSWarner LoshCOMMON ITEMS:
699dc0dbf5cSWarner Losh
700a24eff53SWarner Losh	General Notes
701a24eff53SWarner Losh	-------------
702a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
703a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
704a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
705a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
706a24eff53SWarner Losh	or several minor releases, or when several months have passed
707a24eff53SWarner Losh	on the -current branch).
708a24eff53SWarner Losh
709dc0dbf5cSWarner Losh	To build a kernel
710dc0dbf5cSWarner Losh	-----------------
711ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
712f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
713ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
7141e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7151e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
716dc0dbf5cSWarner Losh
717ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
718ba01eb20SWarner Losh	--------------------------------------------------------------
719ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
720ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
721ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
722ba01eb20SWarner Losh	make depend
723ba01eb20SWarner Losh	make
724ba01eb20SWarner Losh	make install
725ba01eb20SWarner Losh
726ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
727ba01eb20SWarner Losh
728ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
729ba01eb20SWarner Losh
730ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
731ba01eb20SWarner Losh	-----------------------------------------------------------
732759f0aefSWarner Losh	make world
733fdb9f54dSWarner Losh	Build a new kernel, see above.
734759f0aefSWarner Losh
7351dece4a9SWarner Losh	To upgrade from 4.x-stable to current
736ba26da8eSWarner Losh	-------------------------------------
737ba26da8eSWarner Losh	make buildworld
7381e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7397595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
7401e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
741ee6e1fc3SWarner Losh	reboot in single user [3]
742ba26da8eSWarner Losh	make installworld
743a6cd4f9dSWarner Losh	mergemaster		[4]
744134d2e86SWarner Losh	[1]
745ba26da8eSWarner Losh	<reboot>
746ba26da8eSWarner Losh
747fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
748fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
749fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
750fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
751fdb9f54dSWarner Losh	the UPDATING entries.
752ba26da8eSWarner Losh
7531dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
7541dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
7551dece4a9SWarner Losh	your sources that you have read and understood all the recent
7561dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
7571dece4a9SWarner Losh	much fewer pitfalls.
7581dece4a9SWarner Losh
759134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
760134d2e86SWarner Losh	should disable them at this point so they don't crash your
761134d2e86SWarner Losh	system on reboot.
762134d2e86SWarner Losh
7639c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
7649c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
7659c1a7444SWarner Losh	configuration.
7669c1a7444SWarner Losh
767ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
768ee6e1fc3SWarner Losh		fsck -p
769ee6e1fc3SWarner Losh		mount -u /
770ee6e1fc3SWarner Losh		mount -a
771ee6e1fc3SWarner Losh		cd /usr/src
772ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
773ee6e1fc3SWarner Losh
774a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
775a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
776a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
777a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
778a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
779a6cd4f9dSWarner Losh	for potential gotchas.
780a6cd4f9dSWarner Losh
781dc0dbf5cSWarner LoshFORMAT:
782dc0dbf5cSWarner Losh
783f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
7841fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
785f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
786f8ab1dd6SWarner Loshprevious releases if your system is older than this.
7871fc1a0dcSWarner Losh
7883645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
7893645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
790f8c77507SWarner Losh
791e72fd46aSWarner LoshCopyright information:
792e72fd46aSWarner Losh
793e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
794e72fd46aSWarner Losh
795772730c7SWarner LoshRedistribution, publication, translation and use, with or without
796772730c7SWarner Loshmodification, in full or in part, in any form or format of this
797772730c7SWarner Loshdocument are permitted.
798e72fd46aSWarner Losh
799e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
800e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
801e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
802e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
803e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
804e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
805e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
806e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
807e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
808e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
809e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
810e72fd46aSWarner Losh
811e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
812e72fd46aSWarner Loshauthor a beer.
813e72fd46aSWarner Losh
81422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
815772730c7SWarner Loshthis document.
816772730c7SWarner Losh
81797d92980SPeter Wemm$FreeBSD$
818