xref: /freebsd/UPDATING (revision 8f35c49373f259563c346934dcddaad7f7f08d4f)
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
88f35c493SWarner Losh20020217:
98f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
108f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
118f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
128f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
138f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
148f35c493SWarner Losh
15fa9401c1SWarner Losh20020112:
16fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
17fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
18fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
19fa9401c1SWarner Losh	you have local modifications, you can use
20fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
21fa9401c1SWarner Losh	/etc/pam.d.
22fa9401c1SWarner Losh
23fa9401c1SWarner Losh	Please see the following url for more details:
24fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
25fa9401c1SWarner Losh
2647d0d01fSWarner Losh20011229:
2747d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
2847d0d01fSWarner Losh	networkfs_types, please note that it has changed
2947d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
3047d0d01fSWarner Losh
31514318a8SWarner Losh20011220:
32514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
33514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
34514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
35514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
36514318a8SWarner Losh	version have now been merged back into the base system's
37514318a8SWarner Losh	version now.  The only user-visible change resulting from this
38514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
39514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
40514318a8SWarner Losh	as well.  (There has never been rc file support for
41514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
42514318a8SWarner Losh	reverted by the time the changes are MFCed.)
43514318a8SWarner Losh
44514318a8SWarner Losh20011215:
45514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
46514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
47514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
48514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
49514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
50514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
51514318a8SWarner Losh	will need to be customized then for `odd' densities using
52514318a8SWarner Losh	fdcontrol(8).
53514318a8SWarner Losh
542d22e2bfSWarner Losh20011209:
552d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
562d22e2bfSWarner Losh	and truss(1) now works again.
572d22e2bfSWarner Losh
589e0428e2SWarner Losh20011207:
599e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
609e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
619e0428e2SWarner Losh	see
629e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
639e0428e2SWarner Losh	for details.
649e0428e2SWarner Losh
659bab8c59SWarner Losh20011204:
669bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
679bab8c59SWarner Losh	kernel and burncd to be in sync.
689bab8c59SWarner Losh
69e57d8b01SWarner Losh20011203:
70e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
71e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
72e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
73e57d8b01SWarner Losh	not there already.
74e57d8b01SWarner Losh
75e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
76e57d8b01SWarner Losh	until the issue has been resolved.
77e57d8b01SWarner Losh
78b001d36fSJacques Vidrine20011202:
79b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
80b001d36fSJacques Vidrine	patched.
81b001d36fSJacques Vidrine
824b676ec1SWarner Losh20011126:
834b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
845ebbf43eSWarner Losh	after this date.  You need to do this only once.
854b676ec1SWarner Losh
86d961e462SWarner Losh20011103:
87d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
88d961e462SWarner Losh	edges may be left, but for the most part things should be
894b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
90d961e462SWarner Losh
91d961e462SWarner Losh20011030:
92d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
93d961e462SWarner Losh	choppy waves in the upgrade process.
94d961e462SWarner Losh
951fe003b6SWarner Losh20011030:
96a4b6fda0SWarner Losh	The asr driver problem has been resolved.
971fe003b6SWarner Losh
981fe003b6SWarner Losh20011027:
991fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
1001fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
1011fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
1021fe003b6SWarner Losh	try to use from this date forward.
1031fe003b6SWarner Losh
1041fe003b6SWarner Losh20011025:
1051fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
1061fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1071fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1081fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
1091fe003b6SWarner Losh	TARGET_ARCH=i386.
1101fe003b6SWarner Losh
111d05f9643SWarner Losh20011001:
112d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
113d05f9643SWarner Losh	You must recompile both the kernel and userland applications
114d05f9643SWarner Losh	at the same time.
115d05f9643SWarner Losh
11658970f85SWarner Losh20010929:
11758970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
11858970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
11958970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
12058970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
12158970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
12258970f85SWarner Losh
12358970f85SWarner Losh20010927:
12458970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
12558970f85SWarner Losh	To disable ACPI you can add
126378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
12758970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
12858970f85SWarner Losh	loader "ok" prompt).
12958970f85SWarner Losh
13058970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
13158970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
13258970f85SWarner Losh	file and not list acpi in that list.
133378f4486SAlfred Perlstein
1345119d237SWarner Losh20010924:
1355119d237SWarner Losh	The buildworld has been fixed.  You may need to install
1365119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
1378b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
1388b039fffSWarner Losh	get them installed on every installworld, or execute the
1398b039fffSWarner Losh	following to get them installed only once:
1408b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
14158970f85SWarner Losh		make all install
1428b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
1435119d237SWarner Losh
1443c293725SWarner Losh20010919:
1453c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
1463c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
1473c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
148772730c7SWarner Losh	workaround is to add
1493c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
1503c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
1513c293725SWarner Losh	can be removed afterwards.
1523c293725SWarner Losh
1533c293725SWarner Losh	A proper fix to the buildworld target is needed.
1543c293725SWarner Losh
1553c293725SWarner Losh20010918:
1563c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
1573c293725SWarner Losh	NFS may be unstable after this date.
1583c293725SWarner Losh
1593c293725SWarner Losh20010912:
1603c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
1613c293725SWarner Losh	the kernel.  While a few problems were introduced in the
1623c293725SWarner Losh	initial commit, most of the major ones have been found and
1633c293725SWarner Losh	corrected.
1643c293725SWarner Losh
1653c293725SWarner Losh20010901:
1663c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
1673c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
1683c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
1693c293725SWarner Losh	have been rectified around this date.
1703c293725SWarner Losh
17198b17b95SWarner Losh20010823:
17298b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
17398b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
17498b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
17598b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
17698b17b95SWarner Losh 	sure that user or group bind has read (and not write)
17798b17b95SWarner Losh 	permission for your name server configuration and that it
17898b17b95SWarner Losh 	has read and write permission for your slave zone files and
17998b17b95SWarner Losh 	directory.
18098b17b95SWarner Losh
18198b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
18298b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
18398b17b95SWarner Losh
18498b17b95SWarner Losh 		named_flags=
18598b17b95SWarner Losh
1867b9786edSMark Murray20010709:
1877b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1887b9786edSMark Murray	the ability of the shared library major number to handle.
1897b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1907b9786edSMark Murray	solution is to rebuild those ports.
1917b9786edSMark Murray
1921d28950eSWarner Losh20010628:
1931d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1941d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1951d28950eSWarner Losh
196e72fd46aSWarner Losh20010625:
19798b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
19898b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
19998b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
20098b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
20198b17b95SWarner Losh	IRQ configuration needs more safety belts.
20216de1a07SWarner Losh
2030d415dffSWarner Losh20010617:
204e72fd46aSWarner Losh	Softupdates problems have been corrected.
2050d415dffSWarner Losh
2060d415dffSWarner Losh20010614:
2070d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2080d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
2090d415dffSWarner Losh	kernel building methods.
2100d415dffSWarner Losh
2118b9959adSWarner Losh20010613:
2128b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
2138b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
214e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
215e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
2168b9959adSWarner Losh
217e72fd46aSWarner Losh20010613:
2188b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
219e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
220e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
2218b9959adSWarner Losh
2220d415dffSWarner Losh20010612:
2230d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
2240d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
2250d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
2260d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
2270d415dffSWarner Losh	until this bug is fixed.
2280d415dffSWarner Losh
229e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
230e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
231e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
232e72fd46aSWarner Losh
2330d415dffSWarner Losh20010610:
2340d415dffSWarner Losh	Locale names have changed to match other systems better.
2350d415dffSWarner Losh
2366ccdb5e4SWarner Losh20010604:
2376ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
2386ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
2396ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
2403590182eSWarner Losh	Interrupt storms look a lot like a hang.
2413590182eSWarner Losh
2423590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
2433590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
2443590182eSWarner Losh	it is).
2453590182eSWarner Losh
2463590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
2473590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
2483590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
2493590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
2506ccdb5e4SWarner Losh
2510bc62786SWarner Losh20010530:
2520bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
2530bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
2540bc62786SWarner Losh	a limited time.  If you see
2550bc62786SWarner Losh
2560bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
2570bc62786SWarner Losh
2580bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
2590bc62786SWarner Losh	COPY=-C.
2600bc62786SWarner Losh
26168a38c6cSWarner Losh20010525:
262b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
263c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
264c4f4a728SWarner Losh	definitely is in bad shape.
26568a38c6cSWarner Losh
266ed0f29caSWarner Losh20010521:
267f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
268ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
269ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
270ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
271ed0f29caSWarner Losh	is
272ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
273ed0f29caSWarner Losh
27480c16af9SWarner Losh20010520:
27568a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
27680c16af9SWarner Losh
27780c16af9SWarner Losh20010519:
27880c16af9SWarner Losh	pccard has had much reorganizational work done to it over
27980c16af9SWarner Losh	the past few days.  Everything should still work, but if
28080c16af9SWarner Losh	not, please contact imp@freebsd.org.
28180c16af9SWarner Losh
282a45f2d05SWarner Losh20010517:
283a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
284a45f2d05SWarner Losh	userland at the same time.
285a45f2d05SWarner Losh
286a45f2d05SWarner Losh20010517:
287a45f2d05SWarner Losh	New ncurses imported.
288a45f2d05SWarner Losh
2892988afcaSWarner Losh20010512:
2902988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2912988afcaSWarner Losh	will be the only way to go starting July 1.
2922988afcaSWarner Losh
2931a33dba7SWarner Losh20010504:
2941a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
2951a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
2961a33dba7SWarner Losh
29709946a51SWarner Losh20010502:
29809946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
29909946a51SWarner Losh
30009946a51SWarner Losh20010501:
30109946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
30209946a51SWarner Losh
30309946a51SWarner Losh20010430:
304a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
30509946a51SWarner Losh	go back in the water.
30609946a51SWarner Losh
30709946a51SWarner Losh20010429:
30809946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
30909946a51SWarner Losh	this date, but before the correction date.
31009946a51SWarner Losh
31191dd3b53SWarner Losh20010423:
31291dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
31391dd3b53SWarner Losh
31491dd3b53SWarner Losh20010411:
31591dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
31691dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
31791dd3b53SWarner Losh	Update only if you understand that you must not use the old
31891dd3b53SWarner Losh	fsck with the new kernel ever.
31991dd3b53SWarner Losh
320933b3269SWarner Losh20010330:
321933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
322c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
323933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
324933b3269SWarner Losh
325933b3269SWarner Losh20010319:
326933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
327933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
328933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
329f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
33009946a51SWarner Losh
33109946a51SWarner Losh20010315:
33209946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
33309946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
33409946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
335933b3269SWarner Losh
336933b3269SWarner Losh20010312:
337933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
338933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
339933b3269SWarner Losh
340933b3269SWarner Losh20010312:
341933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
342933b3269SWarner Losh	instead of ad-hoc.
343933b3269SWarner Losh
344933b3269SWarner Losh20010310:
345f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
346933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
347933b3269SWarner Losh	ssh might not work if you don't.
348933b3269SWarner Losh
34962353691SWarner Losh20010303:
35062353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
35162353691SWarner Losh	which means that you must include the miibus in your kernel if
35262353691SWarner Losh	you use the ed driver.
35362353691SWarner Losh
354d325cf65SWarner Losh20010220:
355d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
356d325cf65SWarner Losh	safe to go back into the water.
357d325cf65SWarner Losh
358024daae6SWarner Losh20010211:
359024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
360024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
361024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
362024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
363024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
364024daae6SWarner Losh
365024daae6SWarner Losh	To get to the new system, you'll need to use the following
366024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
367024daae6SWarner Losh	don't have to move this to the updating section.
368024daae6SWarner Losh
369024daae6SWarner Losh	To get around the installworld problem, do:
370024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
371024daae6SWarner Losh		# make install
372024daae6SWarner Losh		# cd /usr/src
373024daae6SWarner Losh		# make installworld
374024daae6SWarner Losh	If that doesn't work, then try:
375024daae6SWarner Losh		# make -k installworld
376024daae6SWarner Losh		# make installworld
377024daae6SWarner Losh
378024daae6SWarner Losh20010207:
379024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
380024daae6SWarner Losh	do not include devfs in your kernel as problems result.
381024daae6SWarner Losh
382024daae6SWarner Losh20010205:
3837595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
384024daae6SWarner Losh	Remove them from your config.
385024daae6SWarner Losh
3861e159248SWarner Losh20010122:
3871e159248SWarner Losh	****************************** WARNING ******************************
3881e159248SWarner Losh			buildkernel has been changed slightly
3891e159248SWarner Losh	****************************** WARNING ******************************
3901e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
3911e159248SWarner Losh	should update your scripts and make.conf accordingly.
3921e159248SWarner Losh
3931e159248SWarner Losh20010119:
3941e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3951e159248SWarner Losh	This requires a new config to build correctly.
3961e159248SWarner Losh
397aac7dfeaSWarner Losh20010116:
398aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
399aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
400aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
401aac7dfeaSWarner Losh
402aac7dfeaSWarner Losh20010110:
403aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
404aac7dfeaSWarner Losh
405aac7dfeaSWarner Losh20010102:
406aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
407aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
408aac7dfeaSWarner Losh
40963c90c9eSWarner Losh20010101:
41063c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
41163c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
4125fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
41363c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
41463c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
41563c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
41663c90c9eSWarner Losh	might have been ignored by the -k option.
41763c90c9eSWarner Losh
4185fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
4195fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
4205fd2a895SWarner Losh	of this working.
4215fd2a895SWarner Losh
422aac7dfeaSWarner Losh20001228:
423aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
424aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
425aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
426aac7dfeaSWarner Losh
427de2bcc63SWarner Losh20001218:
428de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
429de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
430de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
431de2bcc63SWarner Losh	cards will not be recognized without it.
432de2bcc63SWarner Losh
433960773f7SWarner Losh20001205:
434960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
435960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
436960773f7SWarner Losh	adding the following in pam.conf:
437960773f7SWarner Losh
438960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
439960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
440960773f7SWarner Losh	sshd    session required        pam_permit.so
441960773f7SWarner Losh
4420acc635eSWarner Losh20001031:
4430acc635eSWarner Losh	cvs updated to 1.11.
4440acc635eSWarner Losh
4450acc635eSWarner Losh20001020:
4460acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
4470acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
4480acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
4490acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
4500acc635eSWarner Losh	workaround.
4510acc635eSWarner Losh
4520acc635eSWarner Losh20001010:
4530acc635eSWarner Losh	****************************** WARNING ******************************
4540acc635eSWarner Losh				Sendmail has been updated.
4550acc635eSWarner Losh	****************************** WARNING ******************************
4560acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
4570acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
4580acc635eSWarner Losh	  is set.
4590acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
4600acc635eSWarner Losh	  commands.
4610acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
4620acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
4630acc635eSWarner Losh	  in /usr/share/sendmail/cf.
4640acc635eSWarner Losh	o sendmail.cw changed to local-host-names
4650acc635eSWarner Losh
4660acc635eSWarner Losh	More details can be found at
4670acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
4680acc635eSWarner Losh
4696e98a146SWarner Losh20001009:
4706e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
4716e98a146SWarner Losh	your entire ports tree, or you will have problems.
4726e98a146SWarner Losh
4736e98a146SWarner Losh20001006:
474685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
4756e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
4766e98a146SWarner Losh	/usr/bin/miniperl.
4776e98a146SWarner Losh
478073113a4SWarner Losh20001005:
479073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
480685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
481073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
482073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
483073113a4SWarner Losh	tree for anything to work.
484073113a4SWarner Losh
4850acc635eSWarner Losh20000928:
4860acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
4870acc635eSWarner Losh
488be3885b3SWarner Losh20000916:
489be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
490be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
491be3885b3SWarner Losh	same time as your kernel.
492be3885b3SWarner Losh
49376ec9675SWarner Losh20000914:
49476ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
49576ec9675SWarner Losh	include the device will cause suspended laptops losing time
49676ec9675SWarner Losh	when they resume.  Include
49776ec9675SWarner Losh		device		pmtimer
49876ec9675SWarner Losh	in your config file and
49901b9a434SWarner Losh		hint.pmtimer.0.at="isa"
50076ec9675SWarner Losh	to your /boot/device.hints file.
50176ec9675SWarner Losh
502f4865386SMark Murray20000911:
503f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
504f4865386SMark Murray	rather than an option. The supplied kernel config files have
505f4865386SMark Murray	been updated. You will need to do something similar in your
506f4865386SMark Murray	own kernel config file.
507f4865386SMark Murray	Remove:
508f4865386SMark Murray		options		RANDOMDEV
509f4865386SMark Murray	Add:
510f4865386SMark Murray		device		random
511f4865386SMark Murray	If you prefer to load the loadable module, you need to do
512f4865386SMark Murray	nothing.
513f4865386SMark Murray
514d594498fSWarner Losh20000909:
515d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
516d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
517d594498fSWarner Losh	reflect this if you load this module at boot time.
518d594498fSWarner Losh	The line should read:
519d594498fSWarner Losh		random_load="YES"
520d594498fSWarner Losh
5210deb7ddcSWarner Losh20000907:
5220deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
52316eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
52416eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
52516eb772dSWarner Losh	sure you don't have model loading problems which might at
52616eb772dSWarner Losh	first blush appear related to SMP.
52752bf24e7SWarner Losh
5285a01880bSWarner Losh20000906:
5295a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
5305a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
5315a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
5325a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
5335a01880bSWarner Losh	don't have one, and you have host.conf.
5345a01880bSWarner Losh
5352b41163cSWarner Losh20000905:
53638d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
53738d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
53838d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
53938d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
54038d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
54138d6ecd2SWarner Losh
54238d6ecd2SWarner Losh20000905:
5438aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
5448aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
5458aab4bc7SWarner Losh	is /boot/kernel.
5468aab4bc7SWarner Losh
5478aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
54838d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
54938d6ecd2SWarner Losh	installkernel/installworld dance.
5502b41163cSWarner Losh
551d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
552d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
553d594498fSWarner Losh	modules in that directory instead of finding them in the correct
554d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
555d594498fSWarner Losh	is that the linux module crashes your machine after the update.
556d594498fSWarner Losh
557d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
558d594498fSWarner Losh		mv /modules.old /boot/kernel.old
559d594498fSWarner Losh		chflags noschg /kernel.old
560d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
561d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
562d594498fSWarner Losh	fi
563d594498fSWarner Losh
564c22a309cSWarner Losh20000904:
565c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
566c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
567c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
568c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
569c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
570c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
571c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
572c22a309cSWarner Losh	is not likely to be generated.
573c22a309cSWarner Losh
574fdb9f54dSWarner Losh20000825:
575fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
5769c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
5779c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
5789c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
5799c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
5809c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
5819c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
5829c1a7444SWarner Losh	kernel.
5839c1a7444SWarner Losh
5849c1a7444SWarner Losh20000821:
5859c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
5869c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
5879c1a7444SWarner Losh	/boot/loader.conf.
588fdb9f54dSWarner Losh
5898f250aa7SWarner Losh20000812:
5905da0d091SWarner Losh	suidperl is now always built and installed on the system, but
5915da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5925da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5935da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5945da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5955da0d091SWarner Losh	will fix this until the next build.
5965da0d091SWarner Losh
5975da0d091SWarner Losh20000812:
5988f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5998f250aa7SWarner Losh	visible changes that may immediately affect your configuration
6008f250aa7SWarner Losh	include:
6018f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
6028f250aa7SWarner Losh	- newaliases limited to root and trusted users
6038f250aa7SWarner Losh	- MSA port (587) turned on by default
6048f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
6058f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
6068f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6078f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6088f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
6098f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
6108f250aa7SWarner Losh
61171c38472SWarner Losh20000810:
61271c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
61371c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
61471c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
61571c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
61671c38472SWarner Losh	specific use for it.
61771c38472SWarner Losh
61871c38472SWarner Losh20000729:
61971c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
62071c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
62171c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
62271c38472SWarner Losh	afterwards (unless the variables already are set, of course):
62371c38472SWarner Losh		# Enable network daemons for user convenience.
62471c38472SWarner Losh		inetd_enable="YES"
62571c38472SWarner Losh		portmap_enable="YES"
62671c38472SWarner Losh		sendmail_enable="YES"
62771c38472SWarner Losh
62871c38472SWarner Losh20000728:
62971c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
63071c38472SWarner Losh	will need to change that to nullfs_load="YES".
63171c38472SWarner Losh
6321dece4a9SWarner Losh20000728:
6331dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
6341dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
6351dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
6361dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
6371dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
6381dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
6391dece4a9SWarner Losh	to /MYKERNEL.
6401dece4a9SWarner Losh
641409e887cSWarner Losh20000711:
642409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
643409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
644409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
645409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
646409e887cSWarner Losh	for details on potential problems that you might have and how
647409e887cSWarner Losh	to get around them.
648409e887cSWarner Losh
649409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
650409e887cSWarner Losh	clauses above, you needn't worry.
651409e887cSWarner Losh
652409e887cSWarner Losh20000711:
653409e887cSWarner Losh	/etc/security has been updated to print the inode number of
654409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
655409e887cSWarner Losh	in the number of changed programs the first time when you run
656409e887cSWarner Losh	mergemaster to get a new /etc/security.
657409e887cSWarner Losh
658673d13f2SWarner Losh20000710:
659673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
660673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
661673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
662673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
663673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
664673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
665673d13f2SWarner Losh	errors. (see below, 20000624).
666673d13f2SWarner Losh
667bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
6681dece4a9SWarner Losh
669673d13f2SWarner Losh20000709:
670c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
671c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
672c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
673673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
674673d13f2SWarner Losh
675e98e26cdSWarner Losh20000706:
676e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
677e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
678e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
679f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
680e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
6812c021c6cSMark Ovens	interim if needed.
682e98e26cdSWarner Losh
683e98e26cdSWarner Losh20000705:
684e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
685e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
686e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
687e98e26cdSWarner Losh	details.
688e98e26cdSWarner Losh
689c373950eSWarner Losh20000704:
6902f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
6912f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6922f961bc8SWarner Losh
6932f961bc8SWarner Losh20000704:
694c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
695c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
696c373950eSWarner Losh	rc.d scripts that haven't been updated.
697c373950eSWarner Losh
69827dc3a2bSWarner Losh20000630:
69927dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
70027dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
70127dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
70227dc3a2bSWarner Losh
703b8c215acSWarner Losh20000625:
704b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
70527dc3a2bSWarner Losh	system installed in order to build the system and kernel.
70627dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
70727dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
70827dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
70927dc3a2bSWarner Losh	were required.  You should check with the latest collections
71027dc3a2bSWarner Losh	to make sure that these haven't changed.
711b8c215acSWarner Losh
7127b990719SWarner Losh20000624:
7137b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
7147b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
7157b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
7161a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
7177b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
7187b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
7197b990719SWarner Losh	date to the completion of the work.
7207b990719SWarner Losh
72127dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
72227dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
72327dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
72427dc3a2bSWarner Losh	recreate the random and urandom devices.
72527dc3a2bSWarner Losh
72681e54c50SWarner Losh20000622:
72781e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
72881e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
72981e54c50SWarner Losh	that used to be required when updating.
73081e54c50SWarner Losh
73139943833SWarner Losh20000621:
7322c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
7332a2f33fbSDaniel Baker	the config file update procedure.
7342a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
735c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
736a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
73739943833SWarner Losh
738290f9ad8SWarner Losh20000620:
739290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
740290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
741290f9ad8SWarner Losh	that workaround will no longer be required.
742290f9ad8SWarner Losh
74390fb6346SWarner Losh20000615:
74490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
74590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
74690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
74790fb6346SWarner Losh	devices.
74890fb6346SWarner Losh
749f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
750f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
751f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
752f75f65bbSWarner Losh	may work).
753f75f65bbSWarner Losh
754ba26da8eSWarner Losh20000612:
755ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
756290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
757c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
758290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
759f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
760f54a3542SWarner Losh	NEWCARD for examples of the new format.
761290f9ad8SWarner Losh
762d65850ebSWarner Losh20000522:
763ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
764d65850ebSWarner Losh	building a kernel after this point is advised that they need
765d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
766d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
767d65850ebSWarner Losh
768d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
769d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
770d9583a00SWarner Losh	is recommended that you don't set this option until the problem
771d9583a00SWarner Losh	is resolved.
772d9583a00SWarner Losh
7738039cedeSWarner Losh20000513:
7748039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
7758039cedeSWarner Losh
776d65850ebSWarner Losh20000510:
7778039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
7788039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
7798039cedeSWarner Losh	is requires for the boot blocks to build properly.
7808039cedeSWarner Losh
7818039cedeSWarner Losh20000503:
7828039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
7838039cedeSWarner Losh	is now available.
7848039cedeSWarner Losh
785d65850ebSWarner Losh20000502:
786d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
787d65850ebSWarner Losh	connected to the kernel building instead.
788d65850ebSWarner Losh
789be149406SNik Clayton20000427:
7908039cedeSWarner Losh	You may need to build gperf
7918039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7928039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7938039cedeSWarner Losh	an option only in -current.
7948039cedeSWarner Losh
7952b8dd5f4SWarner Losh20000417:
7962b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
797f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7982b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7992b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
8002c021c6cSMark Ovens	before you reboot, you'll need to issue:
8012b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
8022b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
8032b8dd5f4SWarner Losh
8048d9f1945SWarner Losh20000320:
8052b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
8062b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
8072b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
8088d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
8092b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
8108d9f1945SWarner Losh
811f8ab1dd6SWarner Losh20000319:
812f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
813f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
814f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
815f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
816f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
817f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
818f8ab1dd6SWarner Losh
81919cada77SWarner Losh20000318:
820f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
82119cada77SWarner Losh	Large kernel changes are being committed and are in the
82219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
82319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
82419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
82519cada77SWarner Losh	that you are loading are up to date.
826ba228352SWarner Losh
82719cada77SWarner Losh20000315:
8286d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
8296d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
8306d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
8316d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
8326d23c382SWarner Losh	boot.
8336d23c382SWarner Losh
8346d23c382SWarner Losh20000315:
83519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
83619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
83757199806SWarner Losh
838dc0dbf5cSWarner LoshCOMMON ITEMS:
839dc0dbf5cSWarner Losh
840a24eff53SWarner Losh	General Notes
841a24eff53SWarner Losh	-------------
842a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
843a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
844a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
845a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
846a24eff53SWarner Losh	or several minor releases, or when several months have passed
847a24eff53SWarner Losh	on the -current branch).
848a24eff53SWarner Losh
8495780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
8505780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
8515780f3baSWarner Losh	environment when searching for values for global variables.
8525780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
8535780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
8545780f3baSWarner Losh	page for more details.
8555780f3baSWarner Losh
856dc0dbf5cSWarner Losh	To build a kernel
857dc0dbf5cSWarner Losh	-----------------
858ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
859f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
860ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
8611e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8621e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
863dc0dbf5cSWarner Losh
864ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
865ba01eb20SWarner Losh	--------------------------------------------------------------
866ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
86747d0d01fSWarner Losh	config KERNEL_NAME_HERE
868ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
869ba01eb20SWarner Losh	make depend
870ba01eb20SWarner Losh	make
871ba01eb20SWarner Losh	make install
872ba01eb20SWarner Losh
873ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
874ba01eb20SWarner Losh
875ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
876ba01eb20SWarner Losh	-----------------------------------------------------------
877759f0aefSWarner Losh	make world
878fdb9f54dSWarner Losh	Build a new kernel, see above.
879759f0aefSWarner Losh
8801dece4a9SWarner Losh	To upgrade from 4.x-stable to current
881ba26da8eSWarner Losh	-------------------------------------
882ba26da8eSWarner Losh	make buildworld
8831e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8847595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
8851e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
886ee6e1fc3SWarner Losh	reboot in single user [3]
887ba26da8eSWarner Losh	make installworld
888a6cd4f9dSWarner Losh	mergemaster		[4]
889134d2e86SWarner Losh	[1]
890ba26da8eSWarner Losh	<reboot>
891ba26da8eSWarner Losh
892fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
893fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
894fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
895fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
896fdb9f54dSWarner Losh	the UPDATING entries.
897ba26da8eSWarner Losh
8981dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8991dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
9001dece4a9SWarner Losh	your sources that you have read and understood all the recent
9011dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
9021dece4a9SWarner Losh	much fewer pitfalls.
9031dece4a9SWarner Losh
904134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
905134d2e86SWarner Losh	should disable them at this point so they don't crash your
906134d2e86SWarner Losh	system on reboot.
907134d2e86SWarner Losh
9089c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
9099c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
9109c1a7444SWarner Losh	configuration.
9119c1a7444SWarner Losh
912ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
913ee6e1fc3SWarner Losh		fsck -p
914ee6e1fc3SWarner Losh		mount -u /
915ee6e1fc3SWarner Losh		mount -a
916ee6e1fc3SWarner Losh		cd /usr/src
91747d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
918ee6e1fc3SWarner Losh
919a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
920a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
921a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
922a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
923a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
924a6cd4f9dSWarner Losh	for potential gotchas.
925a6cd4f9dSWarner Losh
926dc0dbf5cSWarner LoshFORMAT:
927dc0dbf5cSWarner Losh
928f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
9291fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
930f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
931f8ab1dd6SWarner Loshprevious releases if your system is older than this.
9321fc1a0dcSWarner Losh
9333645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
9343645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
935f8c77507SWarner Losh
936e72fd46aSWarner LoshCopyright information:
937e72fd46aSWarner Losh
938e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
939e72fd46aSWarner Losh
940772730c7SWarner LoshRedistribution, publication, translation and use, with or without
941772730c7SWarner Loshmodification, in full or in part, in any form or format of this
942772730c7SWarner Loshdocument are permitted.
943e72fd46aSWarner Losh
944e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
945e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
946e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
947e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
948e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
949e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
950e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
951e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
952e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
953e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
954e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
955e72fd46aSWarner Losh
956e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
957e72fd46aSWarner Loshauthor a beer.
958e72fd46aSWarner Losh
95922306abcSWarner LoshContact Warner Losh if you have any questions about your use of
960772730c7SWarner Loshthis document.
961772730c7SWarner Losh
96297d92980SPeter Wemm$FreeBSD$
963