xref: /freebsd/UPDATING (revision 514318a8137ae1ca2ffdd493b901750b09d4ec8c)
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
8fa9401c1SWarner Losh20020112:
9fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
10fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
11fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
12fa9401c1SWarner Losh	you have local modifications, you can use
13fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
14fa9401c1SWarner Losh	/etc/pam.d.
15fa9401c1SWarner Losh
16fa9401c1SWarner Losh	Please see the following url for more details:
17fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
18fa9401c1SWarner Losh
1947d0d01fSWarner Losh20011229:
2047d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
2147d0d01fSWarner Losh	networkfs_types, please note that it has changed
2247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
2347d0d01fSWarner Losh
24514318a8SWarner Losh20011220:
25514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
26514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
27514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
28514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
29514318a8SWarner Losh	version have now been merged back into the base system's
30514318a8SWarner Losh	version now.  The only user-visible change resulting from this
31514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
32514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
33514318a8SWarner Losh	as well.  (There has never been rc file support for
34514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
35514318a8SWarner Losh	reverted by the time the changes are MFCed.)
36514318a8SWarner Losh
37514318a8SWarner Losh20011215:
38514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
39514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
40514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
41514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
42514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
43514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
44514318a8SWarner Losh	will need to be customized then for `odd' densities using
45514318a8SWarner Losh	fdcontrol(8).
46514318a8SWarner Losh
472d22e2bfSWarner Losh20011209:
482d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
492d22e2bfSWarner Losh	and truss(1) now works again.
502d22e2bfSWarner Losh
519e0428e2SWarner Losh20011207:
529e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
539e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
549e0428e2SWarner Losh	see
559e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
569e0428e2SWarner Losh	for details.
579e0428e2SWarner Losh
589bab8c59SWarner Losh20011204:
599bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
609bab8c59SWarner Losh	kernel and burncd to be in sync.
619bab8c59SWarner Losh
62e57d8b01SWarner Losh20011203:
63e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
64e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
65e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
66e57d8b01SWarner Losh	not there already.
67e57d8b01SWarner Losh
68e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
69e57d8b01SWarner Losh	until the issue has been resolved.
70e57d8b01SWarner Losh
71b001d36fSJacques Vidrine20011202:
72b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
73b001d36fSJacques Vidrine	patched.
74b001d36fSJacques Vidrine
754b676ec1SWarner Losh20011126:
764b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
775ebbf43eSWarner Losh	after this date.  You need to do this only once.
784b676ec1SWarner Losh
79d961e462SWarner Losh20011103:
80d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
81d961e462SWarner Losh	edges may be left, but for the most part things should be
824b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
83d961e462SWarner Losh
84d961e462SWarner Losh20011030:
85d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
86d961e462SWarner Losh	choppy waves in the upgrade process.
87d961e462SWarner Losh
881fe003b6SWarner Losh20011030:
89a4b6fda0SWarner Losh	The asr driver problem has been resolved.
901fe003b6SWarner Losh
911fe003b6SWarner Losh20011027:
921fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
931fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
941fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
951fe003b6SWarner Losh	try to use from this date forward.
961fe003b6SWarner Losh
971fe003b6SWarner Losh20011025:
981fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
991fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1001fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1011fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
1021fe003b6SWarner Losh	TARGET_ARCH=i386.
1031fe003b6SWarner Losh
104d05f9643SWarner Losh20011001:
105d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
106d05f9643SWarner Losh	You must recompile both the kernel and userland applications
107d05f9643SWarner Losh	at the same time.
108d05f9643SWarner Losh
10958970f85SWarner Losh20010929:
11058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
11158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
11258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
11358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
11458970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
11558970f85SWarner Losh
11658970f85SWarner Losh20010927:
11758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
11858970f85SWarner Losh	To disable ACPI you can add
119378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
12058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
12158970f85SWarner Losh	loader "ok" prompt).
12258970f85SWarner Losh
12358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
12458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
12558970f85SWarner Losh	file and not list acpi in that list.
126378f4486SAlfred Perlstein
1275119d237SWarner Losh20010924:
1285119d237SWarner Losh	The buildworld has been fixed.  You may need to install
1295119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
1308b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
1318b039fffSWarner Losh	get them installed on every installworld, or execute the
1328b039fffSWarner Losh	following to get them installed only once:
1338b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
13458970f85SWarner Losh		make all install
1358b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
1365119d237SWarner Losh
1373c293725SWarner Losh20010919:
1383c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
1393c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
1403c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
141772730c7SWarner Losh	workaround is to add
1423c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
1433c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
1443c293725SWarner Losh	can be removed afterwards.
1453c293725SWarner Losh
1463c293725SWarner Losh	A proper fix to the buildworld target is needed.
1473c293725SWarner Losh
1483c293725SWarner Losh20010918:
1493c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
1503c293725SWarner Losh	NFS may be unstable after this date.
1513c293725SWarner Losh
1523c293725SWarner Losh20010912:
1533c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
1543c293725SWarner Losh	the kernel.  While a few problems were introduced in the
1553c293725SWarner Losh	initial commit, most of the major ones have been found and
1563c293725SWarner Losh	corrected.
1573c293725SWarner Losh
1583c293725SWarner Losh20010901:
1593c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
1603c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
1613c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
1623c293725SWarner Losh	have been rectified around this date.
1633c293725SWarner Losh
16498b17b95SWarner Losh20010823:
16598b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
16698b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
16798b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
16898b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
16998b17b95SWarner Losh 	sure that user or group bind has read (and not write)
17098b17b95SWarner Losh 	permission for your name server configuration and that it
17198b17b95SWarner Losh 	has read and write permission for your slave zone files and
17298b17b95SWarner Losh 	directory.
17398b17b95SWarner Losh
17498b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
17598b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
17698b17b95SWarner Losh
17798b17b95SWarner Losh 		named_flags=
17898b17b95SWarner Losh
1797b9786edSMark Murray20010709:
1807b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1817b9786edSMark Murray	the ability of the shared library major number to handle.
1827b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1837b9786edSMark Murray	solution is to rebuild those ports.
1847b9786edSMark Murray
1851d28950eSWarner Losh20010628:
1861d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1871d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1881d28950eSWarner Losh
189e72fd46aSWarner Losh20010625:
19098b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
19198b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
19298b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
19398b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
19498b17b95SWarner Losh	IRQ configuration needs more safety belts.
19516de1a07SWarner Losh
1960d415dffSWarner Losh20010617:
197e72fd46aSWarner Losh	Softupdates problems have been corrected.
1980d415dffSWarner Losh
1990d415dffSWarner Losh20010614:
2000d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2010d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
2020d415dffSWarner Losh	kernel building methods.
2030d415dffSWarner Losh
2048b9959adSWarner Losh20010613:
2058b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
2068b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
207e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
208e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
2098b9959adSWarner Losh
210e72fd46aSWarner Losh20010613:
2118b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
212e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
213e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
2148b9959adSWarner Losh
2150d415dffSWarner Losh20010612:
2160d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
2170d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
2180d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
2190d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
2200d415dffSWarner Losh	until this bug is fixed.
2210d415dffSWarner Losh
222e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
223e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
224e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
225e72fd46aSWarner Losh
2260d415dffSWarner Losh20010610:
2270d415dffSWarner Losh	Locale names have changed to match other systems better.
2280d415dffSWarner Losh
2296ccdb5e4SWarner Losh20010604:
2306ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
2316ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
2326ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
2333590182eSWarner Losh	Interrupt storms look a lot like a hang.
2343590182eSWarner Losh
2353590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
2363590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
2373590182eSWarner Losh	it is).
2383590182eSWarner Losh
2393590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
2403590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
2413590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
2423590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
2436ccdb5e4SWarner Losh
2440bc62786SWarner Losh20010530:
2450bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
2460bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
2470bc62786SWarner Losh	a limited time.  If you see
2480bc62786SWarner Losh
2490bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
2500bc62786SWarner Losh
2510bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
2520bc62786SWarner Losh	COPY=-C.
2530bc62786SWarner Losh
25468a38c6cSWarner Losh20010525:
255b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
256c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
257c4f4a728SWarner Losh	definitely is in bad shape.
25868a38c6cSWarner Losh
259ed0f29caSWarner Losh20010521:
260f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
261ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
262ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
263ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
264ed0f29caSWarner Losh	is
265ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
266ed0f29caSWarner Losh
26780c16af9SWarner Losh20010520:
26868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
26980c16af9SWarner Losh
27080c16af9SWarner Losh20010519:
27180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
27280c16af9SWarner Losh	the past few days.  Everything should still work, but if
27380c16af9SWarner Losh	not, please contact imp@freebsd.org.
27480c16af9SWarner Losh
275a45f2d05SWarner Losh20010517:
276a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
277a45f2d05SWarner Losh	userland at the same time.
278a45f2d05SWarner Losh
279a45f2d05SWarner Losh20010517:
280a45f2d05SWarner Losh	New ncurses imported.
281a45f2d05SWarner Losh
2822988afcaSWarner Losh20010512:
2832988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2842988afcaSWarner Losh	will be the only way to go starting July 1.
2852988afcaSWarner Losh
2861a33dba7SWarner Losh20010504:
2871a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
2881a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
2891a33dba7SWarner Losh
29009946a51SWarner Losh20010502:
29109946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
29209946a51SWarner Losh
29309946a51SWarner Losh20010501:
29409946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
29509946a51SWarner Losh
29609946a51SWarner Losh20010430:
297a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
29809946a51SWarner Losh	go back in the water.
29909946a51SWarner Losh
30009946a51SWarner Losh20010429:
30109946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
30209946a51SWarner Losh	this date, but before the correction date.
30309946a51SWarner Losh
30491dd3b53SWarner Losh20010423:
30591dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
30691dd3b53SWarner Losh
30791dd3b53SWarner Losh20010411:
30891dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
30991dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
31091dd3b53SWarner Losh	Update only if you understand that you must not use the old
31191dd3b53SWarner Losh	fsck with the new kernel ever.
31291dd3b53SWarner Losh
313933b3269SWarner Losh20010330:
314933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
315c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
316933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
317933b3269SWarner Losh
318933b3269SWarner Losh20010319:
319933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
320933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
321933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
322f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
32309946a51SWarner Losh
32409946a51SWarner Losh20010315:
32509946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
32609946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
32709946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
328933b3269SWarner Losh
329933b3269SWarner Losh20010312:
330933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
331933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
332933b3269SWarner Losh
333933b3269SWarner Losh20010312:
334933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
335933b3269SWarner Losh	instead of ad-hoc.
336933b3269SWarner Losh
337933b3269SWarner Losh20010310:
338f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
339933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
340933b3269SWarner Losh	ssh might not work if you don't.
341933b3269SWarner Losh
34262353691SWarner Losh20010303:
34362353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
34462353691SWarner Losh	which means that you must include the miibus in your kernel if
34562353691SWarner Losh	you use the ed driver.
34662353691SWarner Losh
347d325cf65SWarner Losh20010220:
348d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
349d325cf65SWarner Losh	safe to go back into the water.
350d325cf65SWarner Losh
351024daae6SWarner Losh20010211:
352024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
353024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
354024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
355024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
356024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
357024daae6SWarner Losh
358024daae6SWarner Losh	To get to the new system, you'll need to use the following
359024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
360024daae6SWarner Losh	don't have to move this to the updating section.
361024daae6SWarner Losh
362024daae6SWarner Losh	To get around the installworld problem, do:
363024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
364024daae6SWarner Losh		# make install
365024daae6SWarner Losh		# cd /usr/src
366024daae6SWarner Losh		# make installworld
367024daae6SWarner Losh	If that doesn't work, then try:
368024daae6SWarner Losh		# make -k installworld
369024daae6SWarner Losh		# make installworld
370024daae6SWarner Losh
371024daae6SWarner Losh20010207:
372024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
373024daae6SWarner Losh	do not include devfs in your kernel as problems result.
374024daae6SWarner Losh
375024daae6SWarner Losh20010205:
3767595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
377024daae6SWarner Losh	Remove them from your config.
378024daae6SWarner Losh
3791e159248SWarner Losh20010122:
3801e159248SWarner Losh	****************************** WARNING ******************************
3811e159248SWarner Losh			buildkernel has been changed slightly
3821e159248SWarner Losh	****************************** WARNING ******************************
3831e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
3841e159248SWarner Losh	should update your scripts and make.conf accordingly.
3851e159248SWarner Losh
3861e159248SWarner Losh20010119:
3871e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3881e159248SWarner Losh	This requires a new config to build correctly.
3891e159248SWarner Losh
390aac7dfeaSWarner Losh20010116:
391aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
392aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
393aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
394aac7dfeaSWarner Losh
395aac7dfeaSWarner Losh20010110:
396aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
397aac7dfeaSWarner Losh
398aac7dfeaSWarner Losh20010102:
399aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
400aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
401aac7dfeaSWarner Losh
40263c90c9eSWarner Losh20010101:
40363c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
40463c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
4055fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
40663c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
40763c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
40863c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
40963c90c9eSWarner Losh	might have been ignored by the -k option.
41063c90c9eSWarner Losh
4115fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
4125fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
4135fd2a895SWarner Losh	of this working.
4145fd2a895SWarner Losh
415aac7dfeaSWarner Losh20001228:
416aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
417aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
418aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
419aac7dfeaSWarner Losh
420de2bcc63SWarner Losh20001218:
421de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
422de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
423de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
424de2bcc63SWarner Losh	cards will not be recognized without it.
425de2bcc63SWarner Losh
426960773f7SWarner Losh20001205:
427960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
428960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
429960773f7SWarner Losh	adding the following in pam.conf:
430960773f7SWarner Losh
431960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
432960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
433960773f7SWarner Losh	sshd    session required        pam_permit.so
434960773f7SWarner Losh
4350acc635eSWarner Losh20001031:
4360acc635eSWarner Losh	cvs updated to 1.11.
4370acc635eSWarner Losh
4380acc635eSWarner Losh20001020:
4390acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
4400acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
4410acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
4420acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
4430acc635eSWarner Losh	workaround.
4440acc635eSWarner Losh
4450acc635eSWarner Losh20001010:
4460acc635eSWarner Losh	****************************** WARNING ******************************
4470acc635eSWarner Losh				Sendmail has been updated.
4480acc635eSWarner Losh	****************************** WARNING ******************************
4490acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
4500acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
4510acc635eSWarner Losh	  is set.
4520acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
4530acc635eSWarner Losh	  commands.
4540acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
4550acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
4560acc635eSWarner Losh	  in /usr/share/sendmail/cf.
4570acc635eSWarner Losh	o sendmail.cw changed to local-host-names
4580acc635eSWarner Losh
4590acc635eSWarner Losh	More details can be found at
4600acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
4610acc635eSWarner Losh
4626e98a146SWarner Losh20001009:
4636e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
4646e98a146SWarner Losh	your entire ports tree, or you will have problems.
4656e98a146SWarner Losh
4666e98a146SWarner Losh20001006:
467685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
4686e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
4696e98a146SWarner Losh	/usr/bin/miniperl.
4706e98a146SWarner Losh
471073113a4SWarner Losh20001005:
472073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
473685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
474073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
475073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
476073113a4SWarner Losh	tree for anything to work.
477073113a4SWarner Losh
4780acc635eSWarner Losh20000928:
4790acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
4800acc635eSWarner Losh
481be3885b3SWarner Losh20000916:
482be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
483be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
484be3885b3SWarner Losh	same time as your kernel.
485be3885b3SWarner Losh
48676ec9675SWarner Losh20000914:
48776ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
48876ec9675SWarner Losh	include the device will cause suspended laptops losing time
48976ec9675SWarner Losh	when they resume.  Include
49076ec9675SWarner Losh		device		pmtimer
49176ec9675SWarner Losh	in your config file and
49201b9a434SWarner Losh		hint.pmtimer.0.at="isa"
49376ec9675SWarner Losh	to your /boot/device.hints file.
49476ec9675SWarner Losh
495f4865386SMark Murray20000911:
496f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
497f4865386SMark Murray	rather than an option. The supplied kernel config files have
498f4865386SMark Murray	been updated. You will need to do something similar in your
499f4865386SMark Murray	own kernel config file.
500f4865386SMark Murray	Remove:
501f4865386SMark Murray		options		RANDOMDEV
502f4865386SMark Murray	Add:
503f4865386SMark Murray		device		random
504f4865386SMark Murray	If you prefer to load the loadable module, you need to do
505f4865386SMark Murray	nothing.
506f4865386SMark Murray
507d594498fSWarner Losh20000909:
508d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
509d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
510d594498fSWarner Losh	reflect this if you load this module at boot time.
511d594498fSWarner Losh	The line should read:
512d594498fSWarner Losh		random_load="YES"
513d594498fSWarner Losh
5140deb7ddcSWarner Losh20000907:
5150deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
51616eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
51716eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
51816eb772dSWarner Losh	sure you don't have model loading problems which might at
51916eb772dSWarner Losh	first blush appear related to SMP.
52052bf24e7SWarner Losh
5215a01880bSWarner Losh20000906:
5225a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
5235a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
5245a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
5255a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
5265a01880bSWarner Losh	don't have one, and you have host.conf.
5275a01880bSWarner Losh
5282b41163cSWarner Losh20000905:
52938d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
53038d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
53138d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
53238d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
53338d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
53438d6ecd2SWarner Losh
53538d6ecd2SWarner Losh20000905:
5368aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
5378aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
5388aab4bc7SWarner Losh	is /boot/kernel.
5398aab4bc7SWarner Losh
5408aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
54138d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
54238d6ecd2SWarner Losh	installkernel/installworld dance.
5432b41163cSWarner Losh
544d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
545d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
546d594498fSWarner Losh	modules in that directory instead of finding them in the correct
547d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
548d594498fSWarner Losh	is that the linux module crashes your machine after the update.
549d594498fSWarner Losh
550d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
551d594498fSWarner Losh		mv /modules.old /boot/kernel.old
552d594498fSWarner Losh		chflags noschg /kernel.old
553d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
554d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
555d594498fSWarner Losh	fi
556d594498fSWarner Losh
557c22a309cSWarner Losh20000904:
558c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
559c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
560c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
561c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
562c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
563c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
564c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
565c22a309cSWarner Losh	is not likely to be generated.
566c22a309cSWarner Losh
567fdb9f54dSWarner Losh20000825:
568fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
5699c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
5709c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
5719c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
5729c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
5739c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
5749c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
5759c1a7444SWarner Losh	kernel.
5769c1a7444SWarner Losh
5779c1a7444SWarner Losh20000821:
5789c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
5799c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
5809c1a7444SWarner Losh	/boot/loader.conf.
581fdb9f54dSWarner Losh
5828f250aa7SWarner Losh20000812:
5835da0d091SWarner Losh	suidperl is now always built and installed on the system, but
5845da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5855da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5865da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5875da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5885da0d091SWarner Losh	will fix this until the next build.
5895da0d091SWarner Losh
5905da0d091SWarner Losh20000812:
5918f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5928f250aa7SWarner Losh	visible changes that may immediately affect your configuration
5938f250aa7SWarner Losh	include:
5948f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
5958f250aa7SWarner Losh	- newaliases limited to root and trusted users
5968f250aa7SWarner Losh	- MSA port (587) turned on by default
5978f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
5988f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
5998f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6008f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6018f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
6028f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
6038f250aa7SWarner Losh
60471c38472SWarner Losh20000810:
60571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
60671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
60771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
60871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
60971c38472SWarner Losh	specific use for it.
61071c38472SWarner Losh
61171c38472SWarner Losh20000729:
61271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
61371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
61471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
61571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
61671c38472SWarner Losh		# Enable network daemons for user convenience.
61771c38472SWarner Losh		inetd_enable="YES"
61871c38472SWarner Losh		portmap_enable="YES"
61971c38472SWarner Losh		sendmail_enable="YES"
62071c38472SWarner Losh
62171c38472SWarner Losh20000728:
62271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
62371c38472SWarner Losh	will need to change that to nullfs_load="YES".
62471c38472SWarner Losh
6251dece4a9SWarner Losh20000728:
6261dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
6271dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
6281dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
6291dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
6301dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
6311dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
6321dece4a9SWarner Losh	to /MYKERNEL.
6331dece4a9SWarner Losh
634409e887cSWarner Losh20000711:
635409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
636409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
637409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
638409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
639409e887cSWarner Losh	for details on potential problems that you might have and how
640409e887cSWarner Losh	to get around them.
641409e887cSWarner Losh
642409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
643409e887cSWarner Losh	clauses above, you needn't worry.
644409e887cSWarner Losh
645409e887cSWarner Losh20000711:
646409e887cSWarner Losh	/etc/security has been updated to print the inode number of
647409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
648409e887cSWarner Losh	in the number of changed programs the first time when you run
649409e887cSWarner Losh	mergemaster to get a new /etc/security.
650409e887cSWarner Losh
651673d13f2SWarner Losh20000710:
652673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
653673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
654673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
655673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
656673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
657673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
658673d13f2SWarner Losh	errors. (see below, 20000624).
659673d13f2SWarner Losh
660bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
6611dece4a9SWarner Losh
662673d13f2SWarner Losh20000709:
663c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
664c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
665c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
666673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
667673d13f2SWarner Losh
668e98e26cdSWarner Losh20000706:
669e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
670e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
671e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
672f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
673e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
6742c021c6cSMark Ovens	interim if needed.
675e98e26cdSWarner Losh
676e98e26cdSWarner Losh20000705:
677e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
678e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
679e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
680e98e26cdSWarner Losh	details.
681e98e26cdSWarner Losh
682c373950eSWarner Losh20000704:
6832f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
6842f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6852f961bc8SWarner Losh
6862f961bc8SWarner Losh20000704:
687c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
688c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
689c373950eSWarner Losh	rc.d scripts that haven't been updated.
690c373950eSWarner Losh
69127dc3a2bSWarner Losh20000630:
69227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
69327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
69427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
69527dc3a2bSWarner Losh
696b8c215acSWarner Losh20000625:
697b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
69827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
69927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
70027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
70127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
70227dc3a2bSWarner Losh	were required.  You should check with the latest collections
70327dc3a2bSWarner Losh	to make sure that these haven't changed.
704b8c215acSWarner Losh
7057b990719SWarner Losh20000624:
7067b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
7077b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
7087b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
7091a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
7107b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
7117b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
7127b990719SWarner Losh	date to the completion of the work.
7137b990719SWarner Losh
71427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
71527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
71627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
71727dc3a2bSWarner Losh	recreate the random and urandom devices.
71827dc3a2bSWarner Losh
71981e54c50SWarner Losh20000622:
72081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
72181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
72281e54c50SWarner Losh	that used to be required when updating.
72381e54c50SWarner Losh
72439943833SWarner Losh20000621:
7252c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
7262a2f33fbSDaniel Baker	the config file update procedure.
7272a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
728c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
729a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
73039943833SWarner Losh
731290f9ad8SWarner Losh20000620:
732290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
733290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
734290f9ad8SWarner Losh	that workaround will no longer be required.
735290f9ad8SWarner Losh
73690fb6346SWarner Losh20000615:
73790fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
73890fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
73990fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
74090fb6346SWarner Losh	devices.
74190fb6346SWarner Losh
742f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
743f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
744f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
745f75f65bbSWarner Losh	may work).
746f75f65bbSWarner Losh
747ba26da8eSWarner Losh20000612:
748ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
749290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
750c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
751290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
752f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
753f54a3542SWarner Losh	NEWCARD for examples of the new format.
754290f9ad8SWarner Losh
755d65850ebSWarner Losh20000522:
756ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
757d65850ebSWarner Losh	building a kernel after this point is advised that they need
758d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
759d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
760d65850ebSWarner Losh
761d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
762d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
763d9583a00SWarner Losh	is recommended that you don't set this option until the problem
764d9583a00SWarner Losh	is resolved.
765d9583a00SWarner Losh
7668039cedeSWarner Losh20000513:
7678039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
7688039cedeSWarner Losh
769d65850ebSWarner Losh20000510:
7708039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
7718039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
7728039cedeSWarner Losh	is requires for the boot blocks to build properly.
7738039cedeSWarner Losh
7748039cedeSWarner Losh20000503:
7758039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
7768039cedeSWarner Losh	is now available.
7778039cedeSWarner Losh
778d65850ebSWarner Losh20000502:
779d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
780d65850ebSWarner Losh	connected to the kernel building instead.
781d65850ebSWarner Losh
782be149406SNik Clayton20000427:
7838039cedeSWarner Losh	You may need to build gperf
7848039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7858039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7868039cedeSWarner Losh	an option only in -current.
7878039cedeSWarner Losh
7882b8dd5f4SWarner Losh20000417:
7892b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
790f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7912b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7922b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
7932c021c6cSMark Ovens	before you reboot, you'll need to issue:
7942b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
7952b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
7962b8dd5f4SWarner Losh
7978d9f1945SWarner Losh20000320:
7982b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
7992b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
8002b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
8018d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
8022b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
8038d9f1945SWarner Losh
804f8ab1dd6SWarner Losh20000319:
805f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
806f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
807f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
808f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
809f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
810f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
811f8ab1dd6SWarner Losh
81219cada77SWarner Losh20000318:
813f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
81419cada77SWarner Losh	Large kernel changes are being committed and are in the
81519cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
81619cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
81719cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
81819cada77SWarner Losh	that you are loading are up to date.
819ba228352SWarner Losh
82019cada77SWarner Losh20000315:
8216d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
8226d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
8236d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
8246d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
8256d23c382SWarner Losh	boot.
8266d23c382SWarner Losh
8276d23c382SWarner Losh20000315:
82819cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
82919cada77SWarner Losh	to upgrade to 4.0 from 3.x.
83057199806SWarner Losh
831dc0dbf5cSWarner LoshCOMMON ITEMS:
832dc0dbf5cSWarner Losh
833a24eff53SWarner Losh	General Notes
834a24eff53SWarner Losh	-------------
835a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
836a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
837a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
838a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
839a24eff53SWarner Losh	or several minor releases, or when several months have passed
840a24eff53SWarner Losh	on the -current branch).
841a24eff53SWarner Losh
8425780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
8435780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
8445780f3baSWarner Losh	environment when searching for values for global variables.
8455780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
8465780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
8475780f3baSWarner Losh	page for more details.
8485780f3baSWarner Losh
849dc0dbf5cSWarner Losh	To build a kernel
850dc0dbf5cSWarner Losh	-----------------
851ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
852f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
853ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
8541e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8551e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
856dc0dbf5cSWarner Losh
857ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
858ba01eb20SWarner Losh	--------------------------------------------------------------
859ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
86047d0d01fSWarner Losh	config KERNEL_NAME_HERE
861ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
862ba01eb20SWarner Losh	make depend
863ba01eb20SWarner Losh	make
864ba01eb20SWarner Losh	make install
865ba01eb20SWarner Losh
866ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
867ba01eb20SWarner Losh
868ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
869ba01eb20SWarner Losh	-----------------------------------------------------------
870759f0aefSWarner Losh	make world
871fdb9f54dSWarner Losh	Build a new kernel, see above.
872759f0aefSWarner Losh
8731dece4a9SWarner Losh	To upgrade from 4.x-stable to current
874ba26da8eSWarner Losh	-------------------------------------
875ba26da8eSWarner Losh	make buildworld
8761e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8777595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
8781e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
879ee6e1fc3SWarner Losh	reboot in single user [3]
880ba26da8eSWarner Losh	make installworld
881a6cd4f9dSWarner Losh	mergemaster		[4]
882134d2e86SWarner Losh	[1]
883ba26da8eSWarner Losh	<reboot>
884ba26da8eSWarner Losh
885fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
886fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
887fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
888fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
889fdb9f54dSWarner Losh	the UPDATING entries.
890ba26da8eSWarner Losh
8911dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8921dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8931dece4a9SWarner Losh	your sources that you have read and understood all the recent
8941dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8951dece4a9SWarner Losh	much fewer pitfalls.
8961dece4a9SWarner Losh
897134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
898134d2e86SWarner Losh	should disable them at this point so they don't crash your
899134d2e86SWarner Losh	system on reboot.
900134d2e86SWarner Losh
9019c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
9029c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
9039c1a7444SWarner Losh	configuration.
9049c1a7444SWarner Losh
905ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
906ee6e1fc3SWarner Losh		fsck -p
907ee6e1fc3SWarner Losh		mount -u /
908ee6e1fc3SWarner Losh		mount -a
909ee6e1fc3SWarner Losh		cd /usr/src
91047d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
911ee6e1fc3SWarner Losh
912a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
913a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
914a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
915a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
916a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
917a6cd4f9dSWarner Losh	for potential gotchas.
918a6cd4f9dSWarner Losh
919dc0dbf5cSWarner LoshFORMAT:
920dc0dbf5cSWarner Losh
921f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
9221fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
923f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
924f8ab1dd6SWarner Loshprevious releases if your system is older than this.
9251fc1a0dcSWarner Losh
9263645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
9273645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
928f8c77507SWarner Losh
929e72fd46aSWarner LoshCopyright information:
930e72fd46aSWarner Losh
931e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
932e72fd46aSWarner Losh
933772730c7SWarner LoshRedistribution, publication, translation and use, with or without
934772730c7SWarner Loshmodification, in full or in part, in any form or format of this
935772730c7SWarner Loshdocument are permitted.
936e72fd46aSWarner Losh
937e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
938e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
939e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
940e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
941e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
942e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
943e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
944e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
945e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
946e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
947e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
948e72fd46aSWarner Losh
949e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
950e72fd46aSWarner Loshauthor a beer.
951e72fd46aSWarner Losh
95222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
953772730c7SWarner Loshthis document.
954772730c7SWarner Losh
95597d92980SPeter Wemm$FreeBSD$
956