xref: /freebsd/UPDATING (revision 9bab8c59e92dbb264c95a369d5178029760a3e7f)
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
89bab8c59SWarner Losh20011204:
99bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
109bab8c59SWarner Losh	kernel and burncd to be in sync.
119bab8c59SWarner Losh
12e57d8b01SWarner Losh20011203:
13e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
14e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
15e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
16e57d8b01SWarner Losh	not there already.
17e57d8b01SWarner Losh
18e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
19e57d8b01SWarner Losh	until the issue has been resolved.
20e57d8b01SWarner Losh
21b001d36fSJacques Vidrine20011202:
22b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
23b001d36fSJacques Vidrine	patched.
24b001d36fSJacques Vidrine
254b676ec1SWarner Losh20011126:
264b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
274b676ec1SWarner Losh	after this date.
284b676ec1SWarner Losh
29d961e462SWarner Losh20011103:
30d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
31d961e462SWarner Losh	edges may be left, but for the most part things should be
324b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
33d961e462SWarner Losh
34d961e462SWarner Losh20011030:
35d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
36d961e462SWarner Losh	choppy waves in the upgrade process.
37d961e462SWarner Losh
381fe003b6SWarner Losh20011030:
39a4b6fda0SWarner Losh	The asr driver problem has been resolved.
401fe003b6SWarner Losh
411fe003b6SWarner Losh20011027:
421fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
431fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
441fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
451fe003b6SWarner Losh	try to use from this date forward.
461fe003b6SWarner Losh
471fe003b6SWarner Losh20011025:
481fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
491fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
501fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
511fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
521fe003b6SWarner Losh	TARGET_ARCH=i386.
531fe003b6SWarner Losh
54d05f9643SWarner Losh20011001:
55d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
56d05f9643SWarner Losh	You must recompile both the kernel and userland applications
57d05f9643SWarner Losh	at the same time.
58d05f9643SWarner Losh
5958970f85SWarner Losh20010929:
6058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
6158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
6258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
6358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
6458970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
6558970f85SWarner Losh
6658970f85SWarner Losh20010927:
6758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
6858970f85SWarner Losh	To disable ACPI you can add
69378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
7058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
7158970f85SWarner Losh	loader "ok" prompt).
7258970f85SWarner Losh
7358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
7458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
7558970f85SWarner Losh	file and not list acpi in that list.
76378f4486SAlfred Perlstein
775119d237SWarner Losh20010924:
785119d237SWarner Losh	The buildworld has been fixed.  You may need to install
795119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
8058970f85SWarner Losh	to work.
8158970f85SWarner Losh		cd src/lib/compat/compat4x.i386
8258970f85SWarner Losh		make all install
835119d237SWarner Losh
843c293725SWarner Losh20010919:
853c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
863c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
873c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
88772730c7SWarner Losh	workaround is to add
893c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
903c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
913c293725SWarner Losh	can be removed afterwards.
923c293725SWarner Losh
933c293725SWarner Losh	A proper fix to the buildworld target is needed.
943c293725SWarner Losh
953c293725SWarner Losh20010918:
963c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
973c293725SWarner Losh	NFS may be unstable after this date.
983c293725SWarner Losh
993c293725SWarner Losh20010912:
1003c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
1013c293725SWarner Losh	the kernel.  While a few problems were introduced in the
1023c293725SWarner Losh	initial commit, most of the major ones have been found and
1033c293725SWarner Losh	corrected.
1043c293725SWarner Losh
1053c293725SWarner Losh20010901:
1063c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
1073c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
1083c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
1093c293725SWarner Losh	have been rectified around this date.
1103c293725SWarner Losh
11198b17b95SWarner Losh20010823:
11298b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
11398b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
11498b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
11598b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
11698b17b95SWarner Losh 	sure that user or group bind has read (and not write)
11798b17b95SWarner Losh 	permission for your name server configuration and that it
11898b17b95SWarner Losh 	has read and write permission for your slave zone files and
11998b17b95SWarner Losh 	directory.
12098b17b95SWarner Losh
12198b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
12298b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
12398b17b95SWarner Losh
12498b17b95SWarner Losh 		named_flags=
12598b17b95SWarner Losh
1267b9786edSMark Murray20010709:
1277b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1287b9786edSMark Murray	the ability of the shared library major number to handle.
1297b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1307b9786edSMark Murray	solution is to rebuild those ports.
1317b9786edSMark Murray
1321d28950eSWarner Losh20010628:
1331d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1341d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1351d28950eSWarner Losh
136e72fd46aSWarner Losh20010625:
13798b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
13898b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
13998b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
14098b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
14198b17b95SWarner Losh	IRQ configuration needs more safety belts.
14216de1a07SWarner Losh
1430d415dffSWarner Losh20010617:
144e72fd46aSWarner Losh	Softupdates problems have been corrected.
1450d415dffSWarner Losh
1460d415dffSWarner Losh20010614:
1470d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
1480d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
1490d415dffSWarner Losh	kernel building methods.
1500d415dffSWarner Losh
1518b9959adSWarner Losh20010613:
1528b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
1538b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
154e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
155e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
1568b9959adSWarner Losh
157e72fd46aSWarner Losh20010613:
1588b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
159e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
160e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
1618b9959adSWarner Losh
1620d415dffSWarner Losh20010612:
1630d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
1640d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
1650d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
1660d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
1670d415dffSWarner Losh	until this bug is fixed.
1680d415dffSWarner Losh
169e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
170e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
171e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
172e72fd46aSWarner Losh
1730d415dffSWarner Losh20010610:
1740d415dffSWarner Losh	Locale names have changed to match other systems better.
1750d415dffSWarner Losh
1766ccdb5e4SWarner Losh20010604:
1776ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
1786ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
1796ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
1803590182eSWarner Losh	Interrupt storms look a lot like a hang.
1813590182eSWarner Losh
1823590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
1833590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
1843590182eSWarner Losh	it is).
1853590182eSWarner Losh
1863590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
1873590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
1883590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
1893590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
1906ccdb5e4SWarner Losh
1910bc62786SWarner Losh20010530:
1920bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
1930bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
1940bc62786SWarner Losh	a limited time.  If you see
1950bc62786SWarner Losh
1960bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
1970bc62786SWarner Losh
1980bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
1990bc62786SWarner Losh	COPY=-C.
2000bc62786SWarner Losh
20168a38c6cSWarner Losh20010525:
202b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
203c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
204c4f4a728SWarner Losh	definitely is in bad shape.
20568a38c6cSWarner Losh
206ed0f29caSWarner Losh20010521:
207f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
208ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
209ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
210ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
211ed0f29caSWarner Losh	is
212ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
213ed0f29caSWarner Losh
21480c16af9SWarner Losh20010520:
21568a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
21680c16af9SWarner Losh
21780c16af9SWarner Losh20010519:
21880c16af9SWarner Losh	pccard has had much reorganizational work done to it over
21980c16af9SWarner Losh	the past few days.  Everything should still work, but if
22080c16af9SWarner Losh	not, please contact imp@freebsd.org.
22180c16af9SWarner Losh
222a45f2d05SWarner Losh20010517:
223a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
224a45f2d05SWarner Losh	userland at the same time.
225a45f2d05SWarner Losh
226a45f2d05SWarner Losh20010517:
227a45f2d05SWarner Losh	New ncurses imported.
228a45f2d05SWarner Losh
2292988afcaSWarner Losh20010512:
2302988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2312988afcaSWarner Losh	will be the only way to go starting July 1.
2322988afcaSWarner Losh
23309946a51SWarner Losh20010502:
23409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
23509946a51SWarner Losh
23609946a51SWarner Losh20010501:
23709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
23809946a51SWarner Losh
23909946a51SWarner Losh20010430:
240a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
24109946a51SWarner Losh	go back in the water.
24209946a51SWarner Losh
24309946a51SWarner Losh20010429:
24409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
24509946a51SWarner Losh	this date, but before the correction date.
24609946a51SWarner Losh
24791dd3b53SWarner Losh20010423:
24891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
24991dd3b53SWarner Losh
25091dd3b53SWarner Losh20010411:
25191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
25291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
25391dd3b53SWarner Losh	Update only if you understand that you must not use the old
25491dd3b53SWarner Losh	fsck with the new kernel ever.
25591dd3b53SWarner Losh
256933b3269SWarner Losh20010330:
257933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
258c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
259933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
260933b3269SWarner Losh
261933b3269SWarner Losh20010319:
262933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
263933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
264933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
265f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
26609946a51SWarner Losh
26709946a51SWarner Losh20010315:
26809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
26909946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
27009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
271933b3269SWarner Losh
272933b3269SWarner Losh20010312:
273933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
274933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
275933b3269SWarner Losh
276933b3269SWarner Losh20010312:
277933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
278933b3269SWarner Losh	instead of ad-hoc.
279933b3269SWarner Losh
280933b3269SWarner Losh20010310:
281f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
282933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
283933b3269SWarner Losh	ssh might not work if you don't.
284933b3269SWarner Losh
28562353691SWarner Losh20010303:
28662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
28762353691SWarner Losh	which means that you must include the miibus in your kernel if
28862353691SWarner Losh	you use the ed driver.
28962353691SWarner Losh
290d325cf65SWarner Losh20010220:
291d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
292d325cf65SWarner Losh	safe to go back into the water.
293d325cf65SWarner Losh
294024daae6SWarner Losh20010211:
295024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
296024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
297024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
298024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
299024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
300024daae6SWarner Losh
301024daae6SWarner Losh	To get to the new system, you'll need to use the following
302024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
303024daae6SWarner Losh	don't have to move this to the updating section.
304024daae6SWarner Losh
305024daae6SWarner Losh	To get around the installworld problem, do:
306024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
307024daae6SWarner Losh		# make install
308024daae6SWarner Losh		# cd /usr/src
309024daae6SWarner Losh		# make installworld
310024daae6SWarner Losh	If that doesn't work, then try:
311024daae6SWarner Losh		# make -k installworld
312024daae6SWarner Losh		# make installworld
313024daae6SWarner Losh
314024daae6SWarner Losh20010207:
315024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
316024daae6SWarner Losh	do not include devfs in your kernel as problems result.
317024daae6SWarner Losh
318024daae6SWarner Losh20010205:
3197595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
320024daae6SWarner Losh	Remove them from your config.
321024daae6SWarner Losh
3221e159248SWarner Losh20010122:
3231e159248SWarner Losh	****************************** WARNING ******************************
3241e159248SWarner Losh			buildkernel has been changed slightly
3251e159248SWarner Losh	****************************** WARNING ******************************
3261e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
3271e159248SWarner Losh	should update your scripts and make.conf accordingly.
3281e159248SWarner Losh
3291e159248SWarner Losh20010119:
3301e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3311e159248SWarner Losh	This requires a new config to build correctly.
3321e159248SWarner Losh
333aac7dfeaSWarner Losh20010116:
334aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
335aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
336aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
337aac7dfeaSWarner Losh
338aac7dfeaSWarner Losh20010110:
339aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
340aac7dfeaSWarner Losh
341aac7dfeaSWarner Losh20010102:
342aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
343aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
344aac7dfeaSWarner Losh
34563c90c9eSWarner Losh20010101:
34663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
34763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
3485fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
34963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
35063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
35163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
35263c90c9eSWarner Losh	might have been ignored by the -k option.
35363c90c9eSWarner Losh
3545fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
3555fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
3565fd2a895SWarner Losh	of this working.
3575fd2a895SWarner Losh
358aac7dfeaSWarner Losh20001228:
359aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
360aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
361aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
362aac7dfeaSWarner Losh
363de2bcc63SWarner Losh20001218:
364de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
365de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
366de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
367de2bcc63SWarner Losh	cards will not be recognized without it.
368de2bcc63SWarner Losh
369960773f7SWarner Losh20001205:
370960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
371960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
372960773f7SWarner Losh	adding the following in pam.conf:
373960773f7SWarner Losh
374960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
375960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
376960773f7SWarner Losh	sshd    session required        pam_permit.so
377960773f7SWarner Losh
3780acc635eSWarner Losh20001031:
3790acc635eSWarner Losh	cvs updated to 1.11.
3800acc635eSWarner Losh
3810acc635eSWarner Losh20001020:
3820acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
3830acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
3840acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
3850acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
3860acc635eSWarner Losh	workaround.
3870acc635eSWarner Losh
3880acc635eSWarner Losh20001010:
3890acc635eSWarner Losh	****************************** WARNING ******************************
3900acc635eSWarner Losh				Sendmail has been updated.
3910acc635eSWarner Losh	****************************** WARNING ******************************
3920acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
3930acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
3940acc635eSWarner Losh	  is set.
3950acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
3960acc635eSWarner Losh	  commands.
3970acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
3980acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
3990acc635eSWarner Losh	  in /usr/share/sendmail/cf.
4000acc635eSWarner Losh	o sendmail.cw changed to local-host-names
4010acc635eSWarner Losh
4020acc635eSWarner Losh	More details can be found at
4030acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
4040acc635eSWarner Losh
4056e98a146SWarner Losh20001009:
4066e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
4076e98a146SWarner Losh	your entire ports tree, or you will have problems.
4086e98a146SWarner Losh
4096e98a146SWarner Losh20001006:
410685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
4116e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
4126e98a146SWarner Losh	/usr/bin/miniperl.
4136e98a146SWarner Losh
414073113a4SWarner Losh20001005:
415073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
416685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
417073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
418073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
419073113a4SWarner Losh	tree for anything to work.
420073113a4SWarner Losh
4210acc635eSWarner Losh20000928:
4220acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
4230acc635eSWarner Losh
424be3885b3SWarner Losh20000916:
425be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
426be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
427be3885b3SWarner Losh	same time as your kernel.
428be3885b3SWarner Losh
42976ec9675SWarner Losh20000914:
43076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
43176ec9675SWarner Losh	include the device will cause suspended laptops losing time
43276ec9675SWarner Losh	when they resume.  Include
43376ec9675SWarner Losh		device		pmtimer
43476ec9675SWarner Losh	in your config file and
43501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
43676ec9675SWarner Losh	to your /boot/device.hints file.
43776ec9675SWarner Losh
438f4865386SMark Murray20000911:
439f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
440f4865386SMark Murray	rather than an option. The supplied kernel config files have
441f4865386SMark Murray	been updated. You will need to do something similar in your
442f4865386SMark Murray	own kernel config file.
443f4865386SMark Murray	Remove:
444f4865386SMark Murray		options		RANDOMDEV
445f4865386SMark Murray	Add:
446f4865386SMark Murray		device		random
447f4865386SMark Murray	If you prefer to load the loadable module, you need to do
448f4865386SMark Murray	nothing.
449f4865386SMark Murray
450d594498fSWarner Losh20000909:
451d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
452d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
453d594498fSWarner Losh	reflect this if you load this module at boot time.
454d594498fSWarner Losh	The line should read:
455d594498fSWarner Losh		random_load="YES"
456d594498fSWarner Losh
4570deb7ddcSWarner Losh20000907:
4580deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
45916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
46016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
46116eb772dSWarner Losh	sure you don't have model loading problems which might at
46216eb772dSWarner Losh	first blush appear related to SMP.
46352bf24e7SWarner Losh
4645a01880bSWarner Losh20000906:
4655a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
4665a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
4675a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
4685a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
4695a01880bSWarner Losh	don't have one, and you have host.conf.
4705a01880bSWarner Losh
4712b41163cSWarner Losh20000905:
47238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
47338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
47438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
47538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
47638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
47738d6ecd2SWarner Losh
47838d6ecd2SWarner Losh20000905:
4798aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
4808aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
4818aab4bc7SWarner Losh	is /boot/kernel.
4828aab4bc7SWarner Losh
4838aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
48438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
48538d6ecd2SWarner Losh	installkernel/installworld dance.
4862b41163cSWarner Losh
487d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
488d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
489d594498fSWarner Losh	modules in that directory instead of finding them in the correct
490d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
491d594498fSWarner Losh	is that the linux module crashes your machine after the update.
492d594498fSWarner Losh
493d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
494d594498fSWarner Losh		mv /modules.old /boot/kernel.old
495d594498fSWarner Losh		chflags noschg /kernel.old
496d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
497d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
498d594498fSWarner Losh	fi
499d594498fSWarner Losh
500c22a309cSWarner Losh20000904:
501c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
502c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
503c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
504c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
505c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
506c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
507c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
508c22a309cSWarner Losh	is not likely to be generated.
509c22a309cSWarner Losh
510fdb9f54dSWarner Losh20000825:
511fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
5129c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
5139c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
5149c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
5159c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
5169c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
5179c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
5189c1a7444SWarner Losh	kernel.
5199c1a7444SWarner Losh
5209c1a7444SWarner Losh20000821:
5219c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
5229c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
5239c1a7444SWarner Losh	/boot/loader.conf.
524fdb9f54dSWarner Losh
5258f250aa7SWarner Losh20000812:
5265da0d091SWarner Losh	suidperl is now always built and installed on the system, but
5275da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5285da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5295da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5305da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5315da0d091SWarner Losh	will fix this until the next build.
5325da0d091SWarner Losh
5335da0d091SWarner Losh20000812:
5348f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5358f250aa7SWarner Losh	visible changes that may immediately affect your configuration
5368f250aa7SWarner Losh	include:
5378f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
5388f250aa7SWarner Losh	- newaliases limited to root and trusted users
5398f250aa7SWarner Losh	- MSA port (587) turned on by default
5408f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
5418f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
5428f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
5438f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
5448f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
5458f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
5468f250aa7SWarner Losh
54771c38472SWarner Losh20000810:
54871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
54971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
55071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
55171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
55271c38472SWarner Losh	specific use for it.
55371c38472SWarner Losh
55471c38472SWarner Losh20000729:
55571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
55671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
55771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
55871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
55971c38472SWarner Losh		# Enable network daemons for user convenience.
56071c38472SWarner Losh		inetd_enable="YES"
56171c38472SWarner Losh		portmap_enable="YES"
56271c38472SWarner Losh		sendmail_enable="YES"
56371c38472SWarner Losh
56471c38472SWarner Losh20000728:
56571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
56671c38472SWarner Losh	will need to change that to nullfs_load="YES".
56771c38472SWarner Losh
5681dece4a9SWarner Losh20000728:
5691dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
5701dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
5711dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
5721dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
5731dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
5741dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
5751dece4a9SWarner Losh	to /MYKERNEL.
5761dece4a9SWarner Losh
577409e887cSWarner Losh20000711:
578409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
579409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
580409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
581409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
582409e887cSWarner Losh	for details on potential problems that you might have and how
583409e887cSWarner Losh	to get around them.
584409e887cSWarner Losh
585409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
586409e887cSWarner Losh	clauses above, you needn't worry.
587409e887cSWarner Losh
588409e887cSWarner Losh20000711:
589409e887cSWarner Losh	/etc/security has been updated to print the inode number of
590409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
591409e887cSWarner Losh	in the number of changed programs the first time when you run
592409e887cSWarner Losh	mergemaster to get a new /etc/security.
593409e887cSWarner Losh
594673d13f2SWarner Losh20000710:
595673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
596673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
597673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
598673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
599673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
600673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
601673d13f2SWarner Losh	errors. (see below, 20000624).
602673d13f2SWarner Losh
603bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
6041dece4a9SWarner Losh
605673d13f2SWarner Losh20000709:
606c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
607c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
608c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
609673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
610673d13f2SWarner Losh
611e98e26cdSWarner Losh20000706:
612e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
613e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
614e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
615f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
616e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
6172c021c6cSMark Ovens	interim if needed.
618e98e26cdSWarner Losh
619e98e26cdSWarner Losh20000705:
620e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
621e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
622e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
623e98e26cdSWarner Losh	details.
624e98e26cdSWarner Losh
625c373950eSWarner Losh20000704:
6262f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
6272f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6282f961bc8SWarner Losh
6292f961bc8SWarner Losh20000704:
630c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
631c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
632c373950eSWarner Losh	rc.d scripts that haven't been updated.
633c373950eSWarner Losh
63427dc3a2bSWarner Losh20000630:
63527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
63627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
63727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
63827dc3a2bSWarner Losh
639b8c215acSWarner Losh20000625:
640b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
64127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
64227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
64327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
64427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
64527dc3a2bSWarner Losh	were required.  You should check with the latest collections
64627dc3a2bSWarner Losh	to make sure that these haven't changed.
647b8c215acSWarner Losh
6487b990719SWarner Losh20000624:
6497b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
6507b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
6517b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
6527b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
6537b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
6547b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
6557b990719SWarner Losh	date to the completion of the work.
6567b990719SWarner Losh
65727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
65827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
65927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
66027dc3a2bSWarner Losh	recreate the random and urandom devices.
66127dc3a2bSWarner Losh
66281e54c50SWarner Losh20000622:
66381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
66481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
66581e54c50SWarner Losh	that used to be required when updating.
66681e54c50SWarner Losh
66739943833SWarner Losh20000621:
6682c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
6692a2f33fbSDaniel Baker	the config file update procedure.
6702a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
671c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
672a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
67339943833SWarner Losh
674290f9ad8SWarner Losh20000620:
675290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
676290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
677290f9ad8SWarner Losh	that workaround will no longer be required.
678290f9ad8SWarner Losh
67990fb6346SWarner Losh20000615:
68090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
68190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
68290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
68390fb6346SWarner Losh	devices.
68490fb6346SWarner Losh
685f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
686f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
687f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
688f75f65bbSWarner Losh	may work).
689f75f65bbSWarner Losh
690ba26da8eSWarner Losh20000612:
691ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
692290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
693c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
694290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
695f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
696f54a3542SWarner Losh	NEWCARD for examples of the new format.
697290f9ad8SWarner Losh
698d65850ebSWarner Losh20000522:
699ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
700d65850ebSWarner Losh	building a kernel after this point is advised that they need
701d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
702d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
703d65850ebSWarner Losh
704d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
705d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
706d9583a00SWarner Losh	is recommended that you don't set this option until the problem
707d9583a00SWarner Losh	is resolved.
708d9583a00SWarner Losh
7098039cedeSWarner Losh20000513:
7108039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
7118039cedeSWarner Losh
712d65850ebSWarner Losh20000510:
7138039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
7148039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
7158039cedeSWarner Losh	is requires for the boot blocks to build properly.
7168039cedeSWarner Losh
7178039cedeSWarner Losh20000503:
7188039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
7198039cedeSWarner Losh	is now available.
7208039cedeSWarner Losh
721d65850ebSWarner Losh20000502:
722d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
723d65850ebSWarner Losh	connected to the kernel building instead.
724d65850ebSWarner Losh
725be149406SNik Clayton20000427:
7268039cedeSWarner Losh	You may need to build gperf
7278039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7288039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7298039cedeSWarner Losh	an option only in -current.
7308039cedeSWarner Losh
7312b8dd5f4SWarner Losh20000417:
7322b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
733f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7342b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7352b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
7362c021c6cSMark Ovens	before you reboot, you'll need to issue:
7372b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
7382b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
7392b8dd5f4SWarner Losh
7408d9f1945SWarner Losh20000320:
7412b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
7422b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
7432b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
7448d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
7452b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
7468d9f1945SWarner Losh
747f8ab1dd6SWarner Losh20000319:
748f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
749f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
750f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
751f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
752f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
753f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
754f8ab1dd6SWarner Losh
75519cada77SWarner Losh20000318:
756f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
75719cada77SWarner Losh	Large kernel changes are being committed and are in the
75819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
75919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
76019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
76119cada77SWarner Losh	that you are loading are up to date.
762ba228352SWarner Losh
76319cada77SWarner Losh20000315:
7646d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
7656d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
7666d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
7676d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
7686d23c382SWarner Losh	boot.
7696d23c382SWarner Losh
7706d23c382SWarner Losh20000315:
77119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
77219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
77357199806SWarner Losh
774dc0dbf5cSWarner LoshCOMMON ITEMS:
775dc0dbf5cSWarner Losh
776a24eff53SWarner Losh	General Notes
777a24eff53SWarner Losh	-------------
778a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
779a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
780a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
781a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
782a24eff53SWarner Losh	or several minor releases, or when several months have passed
783a24eff53SWarner Losh	on the -current branch).
784a24eff53SWarner Losh
785dc0dbf5cSWarner Losh	To build a kernel
786dc0dbf5cSWarner Losh	-----------------
787ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
788f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
789ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
7901e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
7911e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
792dc0dbf5cSWarner Losh
793ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
794ba01eb20SWarner Losh	--------------------------------------------------------------
795ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
796ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
797ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
798ba01eb20SWarner Losh	make depend
799ba01eb20SWarner Losh	make
800ba01eb20SWarner Losh	make install
801ba01eb20SWarner Losh
802ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
803ba01eb20SWarner Losh
804ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
805ba01eb20SWarner Losh
806ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
807ba01eb20SWarner Losh	-----------------------------------------------------------
808759f0aefSWarner Losh	make world
809fdb9f54dSWarner Losh	Build a new kernel, see above.
810759f0aefSWarner Losh
8111dece4a9SWarner Losh	To upgrade from 4.x-stable to current
812ba26da8eSWarner Losh	-------------------------------------
813ba26da8eSWarner Losh	make buildworld
8141e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8157595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
8161e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
817ee6e1fc3SWarner Losh	reboot in single user [3]
818ba26da8eSWarner Losh	make installworld
819a6cd4f9dSWarner Losh	mergemaster		[4]
820134d2e86SWarner Losh	[1]
821ba26da8eSWarner Losh	<reboot>
822ba26da8eSWarner Losh
823fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
824fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
825fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
826fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
827fdb9f54dSWarner Losh	the UPDATING entries.
828ba26da8eSWarner Losh
8291dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8301dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8311dece4a9SWarner Losh	your sources that you have read and understood all the recent
8321dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8331dece4a9SWarner Losh	much fewer pitfalls.
8341dece4a9SWarner Losh
835134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
836134d2e86SWarner Losh	should disable them at this point so they don't crash your
837134d2e86SWarner Losh	system on reboot.
838134d2e86SWarner Losh
8399c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
8409c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
8419c1a7444SWarner Losh	configuration.
8429c1a7444SWarner Losh
843ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
844ee6e1fc3SWarner Losh		fsck -p
845ee6e1fc3SWarner Losh		mount -u /
846ee6e1fc3SWarner Losh		mount -a
847ee6e1fc3SWarner Losh		cd /usr/src
848ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
849ee6e1fc3SWarner Losh
850a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
851a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
852a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
853a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
854a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
855a6cd4f9dSWarner Losh	for potential gotchas.
856a6cd4f9dSWarner Losh
857dc0dbf5cSWarner LoshFORMAT:
858dc0dbf5cSWarner Losh
859f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
8601fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
861f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
862f8ab1dd6SWarner Loshprevious releases if your system is older than this.
8631fc1a0dcSWarner Losh
8643645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
8653645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
866f8c77507SWarner Losh
867e72fd46aSWarner LoshCopyright information:
868e72fd46aSWarner Losh
869e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
870e72fd46aSWarner Losh
871772730c7SWarner LoshRedistribution, publication, translation and use, with or without
872772730c7SWarner Loshmodification, in full or in part, in any form or format of this
873772730c7SWarner Loshdocument are permitted.
874e72fd46aSWarner Losh
875e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
876e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
877e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
878e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
879e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
880e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
881e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
882e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
883e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
884e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
885e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
886e72fd46aSWarner Losh
887e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
888e72fd46aSWarner Loshauthor a beer.
889e72fd46aSWarner Losh
89022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
891772730c7SWarner Loshthis document.
892772730c7SWarner Losh
89397d92980SPeter Wemm$FreeBSD$
894