xref: /freebsd/UPDATING (revision 9e0428e2cb0dba5c765a313a79c5277b10621bb1)
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
89e0428e2SWarner Losh20011207:
99e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
109e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
119e0428e2SWarner Losh	see
129e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
139e0428e2SWarner Losh	for details.
149e0428e2SWarner Losh
159bab8c59SWarner Losh20011204:
169bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
179bab8c59SWarner Losh	kernel and burncd to be in sync.
189bab8c59SWarner Losh
19e57d8b01SWarner Losh20011203:
20e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
21e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
22e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
23e57d8b01SWarner Losh	not there already.
24e57d8b01SWarner Losh
25e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
26e57d8b01SWarner Losh	until the issue has been resolved.
27e57d8b01SWarner Losh
28b001d36fSJacques Vidrine20011202:
29b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
30b001d36fSJacques Vidrine	patched.
31b001d36fSJacques Vidrine
324b676ec1SWarner Losh20011126:
334b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
344b676ec1SWarner Losh	after this date.
354b676ec1SWarner Losh
36d961e462SWarner Losh20011103:
37d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
38d961e462SWarner Losh	edges may be left, but for the most part things should be
394b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
40d961e462SWarner Losh
41d961e462SWarner Losh20011030:
42d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
43d961e462SWarner Losh	choppy waves in the upgrade process.
44d961e462SWarner Losh
451fe003b6SWarner Losh20011030:
46a4b6fda0SWarner Losh	The asr driver problem has been resolved.
471fe003b6SWarner Losh
481fe003b6SWarner Losh20011027:
491fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
501fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
511fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
521fe003b6SWarner Losh	try to use from this date forward.
531fe003b6SWarner Losh
541fe003b6SWarner Losh20011025:
551fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
561fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
571fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
581fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
591fe003b6SWarner Losh	TARGET_ARCH=i386.
601fe003b6SWarner Losh
61d05f9643SWarner Losh20011001:
62d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
63d05f9643SWarner Losh	You must recompile both the kernel and userland applications
64d05f9643SWarner Losh	at the same time.
65d05f9643SWarner Losh
6658970f85SWarner Losh20010929:
6758970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
6858970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
6958970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
7058970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
7158970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
7258970f85SWarner Losh
7358970f85SWarner Losh20010927:
7458970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
7558970f85SWarner Losh	To disable ACPI you can add
76378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
7758970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
7858970f85SWarner Losh	loader "ok" prompt).
7958970f85SWarner Losh
8058970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
8158970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
8258970f85SWarner Losh	file and not list acpi in that list.
83378f4486SAlfred Perlstein
845119d237SWarner Losh20010924:
855119d237SWarner Losh	The buildworld has been fixed.  You may need to install
865119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
878b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
888b039fffSWarner Losh	get them installed on every installworld, or execute the
898b039fffSWarner Losh	following to get them installed only once:
908b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
9158970f85SWarner Losh		make all install
928b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
935119d237SWarner Losh
943c293725SWarner Losh20010919:
953c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
963c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
973c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
98772730c7SWarner Losh	workaround is to add
993c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
1003c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
1013c293725SWarner Losh	can be removed afterwards.
1023c293725SWarner Losh
1033c293725SWarner Losh	A proper fix to the buildworld target is needed.
1043c293725SWarner Losh
1053c293725SWarner Losh20010918:
1063c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
1073c293725SWarner Losh	NFS may be unstable after this date.
1083c293725SWarner Losh
1093c293725SWarner Losh20010912:
1103c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
1113c293725SWarner Losh	the kernel.  While a few problems were introduced in the
1123c293725SWarner Losh	initial commit, most of the major ones have been found and
1133c293725SWarner Losh	corrected.
1143c293725SWarner Losh
1153c293725SWarner Losh20010901:
1163c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
1173c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
1183c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
1193c293725SWarner Losh	have been rectified around this date.
1203c293725SWarner Losh
12198b17b95SWarner Losh20010823:
12298b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
12398b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
12498b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
12598b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
12698b17b95SWarner Losh 	sure that user or group bind has read (and not write)
12798b17b95SWarner Losh 	permission for your name server configuration and that it
12898b17b95SWarner Losh 	has read and write permission for your slave zone files and
12998b17b95SWarner Losh 	directory.
13098b17b95SWarner Losh
13198b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
13298b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
13398b17b95SWarner Losh
13498b17b95SWarner Losh 		named_flags=
13598b17b95SWarner Losh
1367b9786edSMark Murray20010709:
1377b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1387b9786edSMark Murray	the ability of the shared library major number to handle.
1397b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1407b9786edSMark Murray	solution is to rebuild those ports.
1417b9786edSMark Murray
1421d28950eSWarner Losh20010628:
1431d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1441d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1451d28950eSWarner Losh
146e72fd46aSWarner Losh20010625:
14798b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
14898b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
14998b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
15098b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
15198b17b95SWarner Losh	IRQ configuration needs more safety belts.
15216de1a07SWarner Losh
1530d415dffSWarner Losh20010617:
154e72fd46aSWarner Losh	Softupdates problems have been corrected.
1550d415dffSWarner Losh
1560d415dffSWarner Losh20010614:
1570d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
1580d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
1590d415dffSWarner Losh	kernel building methods.
1600d415dffSWarner Losh
1618b9959adSWarner Losh20010613:
1628b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
1638b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
164e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
165e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
1668b9959adSWarner Losh
167e72fd46aSWarner Losh20010613:
1688b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
169e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
170e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
1718b9959adSWarner Losh
1720d415dffSWarner Losh20010612:
1730d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
1740d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
1750d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
1760d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
1770d415dffSWarner Losh	until this bug is fixed.
1780d415dffSWarner Losh
179e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
180e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
181e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
182e72fd46aSWarner Losh
1830d415dffSWarner Losh20010610:
1840d415dffSWarner Losh	Locale names have changed to match other systems better.
1850d415dffSWarner Losh
1866ccdb5e4SWarner Losh20010604:
1876ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
1886ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
1896ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
1903590182eSWarner Losh	Interrupt storms look a lot like a hang.
1913590182eSWarner Losh
1923590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
1933590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
1943590182eSWarner Losh	it is).
1953590182eSWarner Losh
1963590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
1973590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
1983590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
1993590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
2006ccdb5e4SWarner Losh
2010bc62786SWarner Losh20010530:
2020bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
2030bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
2040bc62786SWarner Losh	a limited time.  If you see
2050bc62786SWarner Losh
2060bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
2070bc62786SWarner Losh
2080bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
2090bc62786SWarner Losh	COPY=-C.
2100bc62786SWarner Losh
21168a38c6cSWarner Losh20010525:
212b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
213c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
214c4f4a728SWarner Losh	definitely is in bad shape.
21568a38c6cSWarner Losh
216ed0f29caSWarner Losh20010521:
217f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
218ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
219ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
220ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
221ed0f29caSWarner Losh	is
222ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
223ed0f29caSWarner Losh
22480c16af9SWarner Losh20010520:
22568a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
22680c16af9SWarner Losh
22780c16af9SWarner Losh20010519:
22880c16af9SWarner Losh	pccard has had much reorganizational work done to it over
22980c16af9SWarner Losh	the past few days.  Everything should still work, but if
23080c16af9SWarner Losh	not, please contact imp@freebsd.org.
23180c16af9SWarner Losh
232a45f2d05SWarner Losh20010517:
233a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
234a45f2d05SWarner Losh	userland at the same time.
235a45f2d05SWarner Losh
236a45f2d05SWarner Losh20010517:
237a45f2d05SWarner Losh	New ncurses imported.
238a45f2d05SWarner Losh
2392988afcaSWarner Losh20010512:
2402988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2412988afcaSWarner Losh	will be the only way to go starting July 1.
2422988afcaSWarner Losh
24309946a51SWarner Losh20010502:
24409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
24509946a51SWarner Losh
24609946a51SWarner Losh20010501:
24709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
24809946a51SWarner Losh
24909946a51SWarner Losh20010430:
250a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
25109946a51SWarner Losh	go back in the water.
25209946a51SWarner Losh
25309946a51SWarner Losh20010429:
25409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
25509946a51SWarner Losh	this date, but before the correction date.
25609946a51SWarner Losh
25791dd3b53SWarner Losh20010423:
25891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
25991dd3b53SWarner Losh
26091dd3b53SWarner Losh20010411:
26191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
26291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
26391dd3b53SWarner Losh	Update only if you understand that you must not use the old
26491dd3b53SWarner Losh	fsck with the new kernel ever.
26591dd3b53SWarner Losh
266933b3269SWarner Losh20010330:
267933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
268c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
269933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
270933b3269SWarner Losh
271933b3269SWarner Losh20010319:
272933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
273933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
274933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
275f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
27609946a51SWarner Losh
27709946a51SWarner Losh20010315:
27809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
27909946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
28009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
281933b3269SWarner Losh
282933b3269SWarner Losh20010312:
283933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
284933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
285933b3269SWarner Losh
286933b3269SWarner Losh20010312:
287933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
288933b3269SWarner Losh	instead of ad-hoc.
289933b3269SWarner Losh
290933b3269SWarner Losh20010310:
291f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
292933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
293933b3269SWarner Losh	ssh might not work if you don't.
294933b3269SWarner Losh
29562353691SWarner Losh20010303:
29662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
29762353691SWarner Losh	which means that you must include the miibus in your kernel if
29862353691SWarner Losh	you use the ed driver.
29962353691SWarner Losh
300d325cf65SWarner Losh20010220:
301d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
302d325cf65SWarner Losh	safe to go back into the water.
303d325cf65SWarner Losh
304024daae6SWarner Losh20010211:
305024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
306024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
307024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
308024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
309024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
310024daae6SWarner Losh
311024daae6SWarner Losh	To get to the new system, you'll need to use the following
312024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
313024daae6SWarner Losh	don't have to move this to the updating section.
314024daae6SWarner Losh
315024daae6SWarner Losh	To get around the installworld problem, do:
316024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
317024daae6SWarner Losh		# make install
318024daae6SWarner Losh		# cd /usr/src
319024daae6SWarner Losh		# make installworld
320024daae6SWarner Losh	If that doesn't work, then try:
321024daae6SWarner Losh		# make -k installworld
322024daae6SWarner Losh		# make installworld
323024daae6SWarner Losh
324024daae6SWarner Losh20010207:
325024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
326024daae6SWarner Losh	do not include devfs in your kernel as problems result.
327024daae6SWarner Losh
328024daae6SWarner Losh20010205:
3297595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
330024daae6SWarner Losh	Remove them from your config.
331024daae6SWarner Losh
3321e159248SWarner Losh20010122:
3331e159248SWarner Losh	****************************** WARNING ******************************
3341e159248SWarner Losh			buildkernel has been changed slightly
3351e159248SWarner Losh	****************************** WARNING ******************************
3361e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
3371e159248SWarner Losh	should update your scripts and make.conf accordingly.
3381e159248SWarner Losh
3391e159248SWarner Losh20010119:
3401e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3411e159248SWarner Losh	This requires a new config to build correctly.
3421e159248SWarner Losh
343aac7dfeaSWarner Losh20010116:
344aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
345aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
346aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
347aac7dfeaSWarner Losh
348aac7dfeaSWarner Losh20010110:
349aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
350aac7dfeaSWarner Losh
351aac7dfeaSWarner Losh20010102:
352aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
353aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
354aac7dfeaSWarner Losh
35563c90c9eSWarner Losh20010101:
35663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
35763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
3585fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
35963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
36063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
36163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
36263c90c9eSWarner Losh	might have been ignored by the -k option.
36363c90c9eSWarner Losh
3645fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
3655fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
3665fd2a895SWarner Losh	of this working.
3675fd2a895SWarner Losh
368aac7dfeaSWarner Losh20001228:
369aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
370aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
371aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
372aac7dfeaSWarner Losh
373de2bcc63SWarner Losh20001218:
374de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
375de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
376de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
377de2bcc63SWarner Losh	cards will not be recognized without it.
378de2bcc63SWarner Losh
379960773f7SWarner Losh20001205:
380960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
381960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
382960773f7SWarner Losh	adding the following in pam.conf:
383960773f7SWarner Losh
384960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
385960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
386960773f7SWarner Losh	sshd    session required        pam_permit.so
387960773f7SWarner Losh
3880acc635eSWarner Losh20001031:
3890acc635eSWarner Losh	cvs updated to 1.11.
3900acc635eSWarner Losh
3910acc635eSWarner Losh20001020:
3920acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
3930acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
3940acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
3950acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
3960acc635eSWarner Losh	workaround.
3970acc635eSWarner Losh
3980acc635eSWarner Losh20001010:
3990acc635eSWarner Losh	****************************** WARNING ******************************
4000acc635eSWarner Losh				Sendmail has been updated.
4010acc635eSWarner Losh	****************************** WARNING ******************************
4020acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
4030acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
4040acc635eSWarner Losh	  is set.
4050acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
4060acc635eSWarner Losh	  commands.
4070acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
4080acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
4090acc635eSWarner Losh	  in /usr/share/sendmail/cf.
4100acc635eSWarner Losh	o sendmail.cw changed to local-host-names
4110acc635eSWarner Losh
4120acc635eSWarner Losh	More details can be found at
4130acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
4140acc635eSWarner Losh
4156e98a146SWarner Losh20001009:
4166e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
4176e98a146SWarner Losh	your entire ports tree, or you will have problems.
4186e98a146SWarner Losh
4196e98a146SWarner Losh20001006:
420685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
4216e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
4226e98a146SWarner Losh	/usr/bin/miniperl.
4236e98a146SWarner Losh
424073113a4SWarner Losh20001005:
425073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
426685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
427073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
428073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
429073113a4SWarner Losh	tree for anything to work.
430073113a4SWarner Losh
4310acc635eSWarner Losh20000928:
4320acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
4330acc635eSWarner Losh
434be3885b3SWarner Losh20000916:
435be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
436be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
437be3885b3SWarner Losh	same time as your kernel.
438be3885b3SWarner Losh
43976ec9675SWarner Losh20000914:
44076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
44176ec9675SWarner Losh	include the device will cause suspended laptops losing time
44276ec9675SWarner Losh	when they resume.  Include
44376ec9675SWarner Losh		device		pmtimer
44476ec9675SWarner Losh	in your config file and
44501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
44676ec9675SWarner Losh	to your /boot/device.hints file.
44776ec9675SWarner Losh
448f4865386SMark Murray20000911:
449f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
450f4865386SMark Murray	rather than an option. The supplied kernel config files have
451f4865386SMark Murray	been updated. You will need to do something similar in your
452f4865386SMark Murray	own kernel config file.
453f4865386SMark Murray	Remove:
454f4865386SMark Murray		options		RANDOMDEV
455f4865386SMark Murray	Add:
456f4865386SMark Murray		device		random
457f4865386SMark Murray	If you prefer to load the loadable module, you need to do
458f4865386SMark Murray	nothing.
459f4865386SMark Murray
460d594498fSWarner Losh20000909:
461d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
462d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
463d594498fSWarner Losh	reflect this if you load this module at boot time.
464d594498fSWarner Losh	The line should read:
465d594498fSWarner Losh		random_load="YES"
466d594498fSWarner Losh
4670deb7ddcSWarner Losh20000907:
4680deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
46916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
47016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
47116eb772dSWarner Losh	sure you don't have model loading problems which might at
47216eb772dSWarner Losh	first blush appear related to SMP.
47352bf24e7SWarner Losh
4745a01880bSWarner Losh20000906:
4755a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
4765a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
4775a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
4785a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
4795a01880bSWarner Losh	don't have one, and you have host.conf.
4805a01880bSWarner Losh
4812b41163cSWarner Losh20000905:
48238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
48338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
48438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
48538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
48638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
48738d6ecd2SWarner Losh
48838d6ecd2SWarner Losh20000905:
4898aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
4908aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
4918aab4bc7SWarner Losh	is /boot/kernel.
4928aab4bc7SWarner Losh
4938aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
49438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
49538d6ecd2SWarner Losh	installkernel/installworld dance.
4962b41163cSWarner Losh
497d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
498d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
499d594498fSWarner Losh	modules in that directory instead of finding them in the correct
500d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
501d594498fSWarner Losh	is that the linux module crashes your machine after the update.
502d594498fSWarner Losh
503d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
504d594498fSWarner Losh		mv /modules.old /boot/kernel.old
505d594498fSWarner Losh		chflags noschg /kernel.old
506d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
507d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
508d594498fSWarner Losh	fi
509d594498fSWarner Losh
510c22a309cSWarner Losh20000904:
511c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
512c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
513c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
514c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
515c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
516c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
517c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
518c22a309cSWarner Losh	is not likely to be generated.
519c22a309cSWarner Losh
520fdb9f54dSWarner Losh20000825:
521fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
5229c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
5239c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
5249c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
5259c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
5269c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
5279c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
5289c1a7444SWarner Losh	kernel.
5299c1a7444SWarner Losh
5309c1a7444SWarner Losh20000821:
5319c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
5329c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
5339c1a7444SWarner Losh	/boot/loader.conf.
534fdb9f54dSWarner Losh
5358f250aa7SWarner Losh20000812:
5365da0d091SWarner Losh	suidperl is now always built and installed on the system, but
5375da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5385da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5395da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5405da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5415da0d091SWarner Losh	will fix this until the next build.
5425da0d091SWarner Losh
5435da0d091SWarner Losh20000812:
5448f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5458f250aa7SWarner Losh	visible changes that may immediately affect your configuration
5468f250aa7SWarner Losh	include:
5478f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
5488f250aa7SWarner Losh	- newaliases limited to root and trusted users
5498f250aa7SWarner Losh	- MSA port (587) turned on by default
5508f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
5518f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
5528f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
5538f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
5548f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
5558f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
5568f250aa7SWarner Losh
55771c38472SWarner Losh20000810:
55871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
55971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
56071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
56171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
56271c38472SWarner Losh	specific use for it.
56371c38472SWarner Losh
56471c38472SWarner Losh20000729:
56571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
56671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
56771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
56871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
56971c38472SWarner Losh		# Enable network daemons for user convenience.
57071c38472SWarner Losh		inetd_enable="YES"
57171c38472SWarner Losh		portmap_enable="YES"
57271c38472SWarner Losh		sendmail_enable="YES"
57371c38472SWarner Losh
57471c38472SWarner Losh20000728:
57571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
57671c38472SWarner Losh	will need to change that to nullfs_load="YES".
57771c38472SWarner Losh
5781dece4a9SWarner Losh20000728:
5791dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
5801dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
5811dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
5821dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
5831dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
5841dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
5851dece4a9SWarner Losh	to /MYKERNEL.
5861dece4a9SWarner Losh
587409e887cSWarner Losh20000711:
588409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
589409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
590409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
591409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
592409e887cSWarner Losh	for details on potential problems that you might have and how
593409e887cSWarner Losh	to get around them.
594409e887cSWarner Losh
595409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
596409e887cSWarner Losh	clauses above, you needn't worry.
597409e887cSWarner Losh
598409e887cSWarner Losh20000711:
599409e887cSWarner Losh	/etc/security has been updated to print the inode number of
600409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
601409e887cSWarner Losh	in the number of changed programs the first time when you run
602409e887cSWarner Losh	mergemaster to get a new /etc/security.
603409e887cSWarner Losh
604673d13f2SWarner Losh20000710:
605673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
606673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
607673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
608673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
609673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
610673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
611673d13f2SWarner Losh	errors. (see below, 20000624).
612673d13f2SWarner Losh
613bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
6141dece4a9SWarner Losh
615673d13f2SWarner Losh20000709:
616c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
617c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
618c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
619673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
620673d13f2SWarner Losh
621e98e26cdSWarner Losh20000706:
622e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
623e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
624e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
625f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
626e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
6272c021c6cSMark Ovens	interim if needed.
628e98e26cdSWarner Losh
629e98e26cdSWarner Losh20000705:
630e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
631e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
632e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
633e98e26cdSWarner Losh	details.
634e98e26cdSWarner Losh
635c373950eSWarner Losh20000704:
6362f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
6372f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6382f961bc8SWarner Losh
6392f961bc8SWarner Losh20000704:
640c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
641c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
642c373950eSWarner Losh	rc.d scripts that haven't been updated.
643c373950eSWarner Losh
64427dc3a2bSWarner Losh20000630:
64527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
64627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
64727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
64827dc3a2bSWarner Losh
649b8c215acSWarner Losh20000625:
650b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
65127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
65227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
65327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
65427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
65527dc3a2bSWarner Losh	were required.  You should check with the latest collections
65627dc3a2bSWarner Losh	to make sure that these haven't changed.
657b8c215acSWarner Losh
6587b990719SWarner Losh20000624:
6597b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
6607b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
6617b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
6627b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
6637b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
6647b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
6657b990719SWarner Losh	date to the completion of the work.
6667b990719SWarner Losh
66727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
66827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
66927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
67027dc3a2bSWarner Losh	recreate the random and urandom devices.
67127dc3a2bSWarner Losh
67281e54c50SWarner Losh20000622:
67381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
67481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
67581e54c50SWarner Losh	that used to be required when updating.
67681e54c50SWarner Losh
67739943833SWarner Losh20000621:
6782c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
6792a2f33fbSDaniel Baker	the config file update procedure.
6802a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
681c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
682a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
68339943833SWarner Losh
684290f9ad8SWarner Losh20000620:
685290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
686290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
687290f9ad8SWarner Losh	that workaround will no longer be required.
688290f9ad8SWarner Losh
68990fb6346SWarner Losh20000615:
69090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
69190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
69290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
69390fb6346SWarner Losh	devices.
69490fb6346SWarner Losh
695f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
696f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
697f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
698f75f65bbSWarner Losh	may work).
699f75f65bbSWarner Losh
700ba26da8eSWarner Losh20000612:
701ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
702290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
703c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
704290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
705f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
706f54a3542SWarner Losh	NEWCARD for examples of the new format.
707290f9ad8SWarner Losh
708d65850ebSWarner Losh20000522:
709ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
710d65850ebSWarner Losh	building a kernel after this point is advised that they need
711d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
712d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
713d65850ebSWarner Losh
714d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
715d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
716d9583a00SWarner Losh	is recommended that you don't set this option until the problem
717d9583a00SWarner Losh	is resolved.
718d9583a00SWarner Losh
7198039cedeSWarner Losh20000513:
7208039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
7218039cedeSWarner Losh
722d65850ebSWarner Losh20000510:
7238039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
7248039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
7258039cedeSWarner Losh	is requires for the boot blocks to build properly.
7268039cedeSWarner Losh
7278039cedeSWarner Losh20000503:
7288039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
7298039cedeSWarner Losh	is now available.
7308039cedeSWarner Losh
731d65850ebSWarner Losh20000502:
732d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
733d65850ebSWarner Losh	connected to the kernel building instead.
734d65850ebSWarner Losh
735be149406SNik Clayton20000427:
7368039cedeSWarner Losh	You may need to build gperf
7378039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7388039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7398039cedeSWarner Losh	an option only in -current.
7408039cedeSWarner Losh
7412b8dd5f4SWarner Losh20000417:
7422b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
743f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7442b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7452b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
7462c021c6cSMark Ovens	before you reboot, you'll need to issue:
7472b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
7482b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
7492b8dd5f4SWarner Losh
7508d9f1945SWarner Losh20000320:
7512b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
7522b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
7532b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
7548d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
7552b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
7568d9f1945SWarner Losh
757f8ab1dd6SWarner Losh20000319:
758f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
759f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
760f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
761f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
762f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
763f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
764f8ab1dd6SWarner Losh
76519cada77SWarner Losh20000318:
766f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
76719cada77SWarner Losh	Large kernel changes are being committed and are in the
76819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
76919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
77019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
77119cada77SWarner Losh	that you are loading are up to date.
772ba228352SWarner Losh
77319cada77SWarner Losh20000315:
7746d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
7756d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
7766d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
7776d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
7786d23c382SWarner Losh	boot.
7796d23c382SWarner Losh
7806d23c382SWarner Losh20000315:
78119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
78219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
78357199806SWarner Losh
784dc0dbf5cSWarner LoshCOMMON ITEMS:
785dc0dbf5cSWarner Losh
786a24eff53SWarner Losh	General Notes
787a24eff53SWarner Losh	-------------
788a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
789a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
790a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
791a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
792a24eff53SWarner Losh	or several minor releases, or when several months have passed
793a24eff53SWarner Losh	on the -current branch).
794a24eff53SWarner Losh
795dc0dbf5cSWarner Losh	To build a kernel
796dc0dbf5cSWarner Losh	-----------------
797ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
798f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
799ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
8001e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8011e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
802dc0dbf5cSWarner Losh
803ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
804ba01eb20SWarner Losh	--------------------------------------------------------------
805ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
806ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
807ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
808ba01eb20SWarner Losh	make depend
809ba01eb20SWarner Losh	make
810ba01eb20SWarner Losh	make install
811ba01eb20SWarner Losh
812ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
813ba01eb20SWarner Losh
814ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
815ba01eb20SWarner Losh
816ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
817ba01eb20SWarner Losh	-----------------------------------------------------------
818759f0aefSWarner Losh	make world
819fdb9f54dSWarner Losh	Build a new kernel, see above.
820759f0aefSWarner Losh
8211dece4a9SWarner Losh	To upgrade from 4.x-stable to current
822ba26da8eSWarner Losh	-------------------------------------
823ba26da8eSWarner Losh	make buildworld
8241e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8257595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
8261e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
827ee6e1fc3SWarner Losh	reboot in single user [3]
828ba26da8eSWarner Losh	make installworld
829a6cd4f9dSWarner Losh	mergemaster		[4]
830134d2e86SWarner Losh	[1]
831ba26da8eSWarner Losh	<reboot>
832ba26da8eSWarner Losh
833fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
834fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
835fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
836fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
837fdb9f54dSWarner Losh	the UPDATING entries.
838ba26da8eSWarner Losh
8391dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8401dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8411dece4a9SWarner Losh	your sources that you have read and understood all the recent
8421dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8431dece4a9SWarner Losh	much fewer pitfalls.
8441dece4a9SWarner Losh
845134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
846134d2e86SWarner Losh	should disable them at this point so they don't crash your
847134d2e86SWarner Losh	system on reboot.
848134d2e86SWarner Losh
8499c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
8509c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
8519c1a7444SWarner Losh	configuration.
8529c1a7444SWarner Losh
853ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
854ee6e1fc3SWarner Losh		fsck -p
855ee6e1fc3SWarner Losh		mount -u /
856ee6e1fc3SWarner Losh		mount -a
857ee6e1fc3SWarner Losh		cd /usr/src
858ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
859ee6e1fc3SWarner Losh
860a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
861a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
862a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
863a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
864a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
865a6cd4f9dSWarner Losh	for potential gotchas.
866a6cd4f9dSWarner Losh
867dc0dbf5cSWarner LoshFORMAT:
868dc0dbf5cSWarner Losh
869f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
8701fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
871f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
872f8ab1dd6SWarner Loshprevious releases if your system is older than this.
8731fc1a0dcSWarner Losh
8743645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
8753645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
876f8c77507SWarner Losh
877e72fd46aSWarner LoshCopyright information:
878e72fd46aSWarner Losh
879e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
880e72fd46aSWarner Losh
881772730c7SWarner LoshRedistribution, publication, translation and use, with or without
882772730c7SWarner Loshmodification, in full or in part, in any form or format of this
883772730c7SWarner Loshdocument are permitted.
884e72fd46aSWarner Losh
885e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
886e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
887e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
888e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
889e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
890e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
891e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
892e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
893e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
894e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
895e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
896e72fd46aSWarner Losh
897e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
898e72fd46aSWarner Loshauthor a beer.
899e72fd46aSWarner Losh
90022306abcSWarner LoshContact Warner Losh if you have any questions about your use of
901772730c7SWarner Loshthis document.
902772730c7SWarner Losh
90397d92980SPeter Wemm$FreeBSD$
904