xref: /freebsd/UPDATING (revision 5ebbf43ef7ea68f89085a2dc4164c3cb9baebf71)
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
242d22e2bfSWarner Losh20011209:
252d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
262d22e2bfSWarner Losh	and truss(1) now works again.
272d22e2bfSWarner Losh
289e0428e2SWarner Losh20011207:
299e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
309e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
319e0428e2SWarner Losh	see
329e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
339e0428e2SWarner Losh	for details.
349e0428e2SWarner Losh
359bab8c59SWarner Losh20011204:
369bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
379bab8c59SWarner Losh	kernel and burncd to be in sync.
389bab8c59SWarner Losh
39e57d8b01SWarner Losh20011203:
40e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
41e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
42e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
43e57d8b01SWarner Losh	not there already.
44e57d8b01SWarner Losh
45e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
46e57d8b01SWarner Losh	until the issue has been resolved.
47e57d8b01SWarner Losh
48b001d36fSJacques Vidrine20011202:
49b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
50b001d36fSJacques Vidrine	patched.
51b001d36fSJacques Vidrine
524b676ec1SWarner Losh20011126:
534b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
545ebbf43eSWarner Losh	after this date.  You need to do this only once.
554b676ec1SWarner Losh
56d961e462SWarner Losh20011103:
57d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
58d961e462SWarner Losh	edges may be left, but for the most part things should be
594b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
60d961e462SWarner Losh
61d961e462SWarner Losh20011030:
62d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
63d961e462SWarner Losh	choppy waves in the upgrade process.
64d961e462SWarner Losh
651fe003b6SWarner Losh20011030:
66a4b6fda0SWarner Losh	The asr driver problem has been resolved.
671fe003b6SWarner Losh
681fe003b6SWarner Losh20011027:
691fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
701fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
711fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
721fe003b6SWarner Losh	try to use from this date forward.
731fe003b6SWarner Losh
741fe003b6SWarner Losh20011025:
751fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
761fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
771fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
781fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
791fe003b6SWarner Losh	TARGET_ARCH=i386.
801fe003b6SWarner Losh
81d05f9643SWarner Losh20011001:
82d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
83d05f9643SWarner Losh	You must recompile both the kernel and userland applications
84d05f9643SWarner Losh	at the same time.
85d05f9643SWarner Losh
8658970f85SWarner Losh20010929:
8758970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
8858970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
8958970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
9058970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
9158970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
9258970f85SWarner Losh
9358970f85SWarner Losh20010927:
9458970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
9558970f85SWarner Losh	To disable ACPI you can add
96378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
9758970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
9858970f85SWarner Losh	loader "ok" prompt).
9958970f85SWarner Losh
10058970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
10158970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
10258970f85SWarner Losh	file and not list acpi in that list.
103378f4486SAlfred Perlstein
1045119d237SWarner Losh20010924:
1055119d237SWarner Losh	The buildworld has been fixed.  You may need to install
1065119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
1078b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
1088b039fffSWarner Losh	get them installed on every installworld, or execute the
1098b039fffSWarner Losh	following to get them installed only once:
1108b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
11158970f85SWarner Losh		make all install
1128b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
1135119d237SWarner Losh
1143c293725SWarner Losh20010919:
1153c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
1163c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
1173c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
118772730c7SWarner Losh	workaround is to add
1193c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
1203c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
1213c293725SWarner Losh	can be removed afterwards.
1223c293725SWarner Losh
1233c293725SWarner Losh	A proper fix to the buildworld target is needed.
1243c293725SWarner Losh
1253c293725SWarner Losh20010918:
1263c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
1273c293725SWarner Losh	NFS may be unstable after this date.
1283c293725SWarner Losh
1293c293725SWarner Losh20010912:
1303c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
1313c293725SWarner Losh	the kernel.  While a few problems were introduced in the
1323c293725SWarner Losh	initial commit, most of the major ones have been found and
1333c293725SWarner Losh	corrected.
1343c293725SWarner Losh
1353c293725SWarner Losh20010901:
1363c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
1373c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
1383c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
1393c293725SWarner Losh	have been rectified around this date.
1403c293725SWarner Losh
14198b17b95SWarner Losh20010823:
14298b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
14398b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
14498b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
14598b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
14698b17b95SWarner Losh 	sure that user or group bind has read (and not write)
14798b17b95SWarner Losh 	permission for your name server configuration and that it
14898b17b95SWarner Losh 	has read and write permission for your slave zone files and
14998b17b95SWarner Losh 	directory.
15098b17b95SWarner Losh
15198b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
15298b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
15398b17b95SWarner Losh
15498b17b95SWarner Losh 		named_flags=
15598b17b95SWarner Losh
1567b9786edSMark Murray20010709:
1577b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
1587b9786edSMark Murray	the ability of the shared library major number to handle.
1597b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
1607b9786edSMark Murray	solution is to rebuild those ports.
1617b9786edSMark Murray
1621d28950eSWarner Losh20010628:
1631d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
1641d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
1651d28950eSWarner Losh
166e72fd46aSWarner Losh20010625:
16798b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
16898b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
16998b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
17098b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
17198b17b95SWarner Losh	IRQ configuration needs more safety belts.
17216de1a07SWarner Losh
1730d415dffSWarner Losh20010617:
174e72fd46aSWarner Losh	Softupdates problems have been corrected.
1750d415dffSWarner Losh
1760d415dffSWarner Losh20010614:
1770d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
1780d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
1790d415dffSWarner Losh	kernel building methods.
1800d415dffSWarner Losh
1818b9959adSWarner Losh20010613:
1828b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
1838b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
184e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
185e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
1868b9959adSWarner Losh
187e72fd46aSWarner Losh20010613:
1888b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
189e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
190e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
1918b9959adSWarner Losh
1920d415dffSWarner Losh20010612:
1930d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
1940d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
1950d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
1960d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
1970d415dffSWarner Losh	until this bug is fixed.
1980d415dffSWarner Losh
199e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
200e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
201e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
202e72fd46aSWarner Losh
2030d415dffSWarner Losh20010610:
2040d415dffSWarner Losh	Locale names have changed to match other systems better.
2050d415dffSWarner Losh
2066ccdb5e4SWarner Losh20010604:
2076ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
2086ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
2096ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
2103590182eSWarner Losh	Interrupt storms look a lot like a hang.
2113590182eSWarner Losh
2123590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
2133590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
2143590182eSWarner Losh	it is).
2153590182eSWarner Losh
2163590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
2173590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
2183590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
2193590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
2206ccdb5e4SWarner Losh
2210bc62786SWarner Losh20010530:
2220bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
2230bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
2240bc62786SWarner Losh	a limited time.  If you see
2250bc62786SWarner Losh
2260bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
2270bc62786SWarner Losh
2280bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
2290bc62786SWarner Losh	COPY=-C.
2300bc62786SWarner Losh
23168a38c6cSWarner Losh20010525:
232b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
233c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
234c4f4a728SWarner Losh	definitely is in bad shape.
23568a38c6cSWarner Losh
236ed0f29caSWarner Losh20010521:
237f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
238ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
239ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
240ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
241ed0f29caSWarner Losh	is
242ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
243ed0f29caSWarner Losh
24480c16af9SWarner Losh20010520:
24568a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
24680c16af9SWarner Losh
24780c16af9SWarner Losh20010519:
24880c16af9SWarner Losh	pccard has had much reorganizational work done to it over
24980c16af9SWarner Losh	the past few days.  Everything should still work, but if
25080c16af9SWarner Losh	not, please contact imp@freebsd.org.
25180c16af9SWarner Losh
252a45f2d05SWarner Losh20010517:
253a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
254a45f2d05SWarner Losh	userland at the same time.
255a45f2d05SWarner Losh
256a45f2d05SWarner Losh20010517:
257a45f2d05SWarner Losh	New ncurses imported.
258a45f2d05SWarner Losh
2592988afcaSWarner Losh20010512:
2602988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
2612988afcaSWarner Losh	will be the only way to go starting July 1.
2622988afcaSWarner Losh
26309946a51SWarner Losh20010502:
26409946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
26509946a51SWarner Losh
26609946a51SWarner Losh20010501:
26709946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
26809946a51SWarner Losh
26909946a51SWarner Losh20010430:
270a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
27109946a51SWarner Losh	go back in the water.
27209946a51SWarner Losh
27309946a51SWarner Losh20010429:
27409946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
27509946a51SWarner Losh	this date, but before the correction date.
27609946a51SWarner Losh
27791dd3b53SWarner Losh20010423:
27891dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
27991dd3b53SWarner Losh
28091dd3b53SWarner Losh20010411:
28191dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
28291dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
28391dd3b53SWarner Losh	Update only if you understand that you must not use the old
28491dd3b53SWarner Losh	fsck with the new kernel ever.
28591dd3b53SWarner Losh
286933b3269SWarner Losh20010330:
287933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
288c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
289933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
290933b3269SWarner Losh
291933b3269SWarner Losh20010319:
292933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
293933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
294933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
295f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
29609946a51SWarner Losh
29709946a51SWarner Losh20010315:
29809946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
29909946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
30009946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
301933b3269SWarner Losh
302933b3269SWarner Losh20010312:
303933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
304933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
305933b3269SWarner Losh
306933b3269SWarner Losh20010312:
307933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
308933b3269SWarner Losh	instead of ad-hoc.
309933b3269SWarner Losh
310933b3269SWarner Losh20010310:
311f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
312933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
313933b3269SWarner Losh	ssh might not work if you don't.
314933b3269SWarner Losh
31562353691SWarner Losh20010303:
31662353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
31762353691SWarner Losh	which means that you must include the miibus in your kernel if
31862353691SWarner Losh	you use the ed driver.
31962353691SWarner Losh
320d325cf65SWarner Losh20010220:
321d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
322d325cf65SWarner Losh	safe to go back into the water.
323d325cf65SWarner Losh
324024daae6SWarner Losh20010211:
325024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
326024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
327024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
328024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
329024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
330024daae6SWarner Losh
331024daae6SWarner Losh	To get to the new system, you'll need to use the following
332024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
333024daae6SWarner Losh	don't have to move this to the updating section.
334024daae6SWarner Losh
335024daae6SWarner Losh	To get around the installworld problem, do:
336024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
337024daae6SWarner Losh		# make install
338024daae6SWarner Losh		# cd /usr/src
339024daae6SWarner Losh		# make installworld
340024daae6SWarner Losh	If that doesn't work, then try:
341024daae6SWarner Losh		# make -k installworld
342024daae6SWarner Losh		# make installworld
343024daae6SWarner Losh
344024daae6SWarner Losh20010207:
345024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
346024daae6SWarner Losh	do not include devfs in your kernel as problems result.
347024daae6SWarner Losh
348024daae6SWarner Losh20010205:
3497595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
350024daae6SWarner Losh	Remove them from your config.
351024daae6SWarner Losh
3521e159248SWarner Losh20010122:
3531e159248SWarner Losh	****************************** WARNING ******************************
3541e159248SWarner Losh			buildkernel has been changed slightly
3551e159248SWarner Losh	****************************** WARNING ******************************
3561e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
3571e159248SWarner Losh	should update your scripts and make.conf accordingly.
3581e159248SWarner Losh
3591e159248SWarner Losh20010119:
3601e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
3611e159248SWarner Losh	This requires a new config to build correctly.
3621e159248SWarner Losh
363aac7dfeaSWarner Losh20010116:
364aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
365aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
366aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
367aac7dfeaSWarner Losh
368aac7dfeaSWarner Losh20010110:
369aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
370aac7dfeaSWarner Losh
371aac7dfeaSWarner Losh20010102:
372aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
373aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
374aac7dfeaSWarner Losh
37563c90c9eSWarner Losh20010101:
37663c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
37763c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
3785fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
37963c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
38063c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
38163c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
38263c90c9eSWarner Losh	might have been ignored by the -k option.
38363c90c9eSWarner Losh
3845fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
3855fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
3865fd2a895SWarner Losh	of this working.
3875fd2a895SWarner Losh
388aac7dfeaSWarner Losh20001228:
389aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
390aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
391aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
392aac7dfeaSWarner Losh
393de2bcc63SWarner Losh20001218:
394de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
395de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
396de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
397de2bcc63SWarner Losh	cards will not be recognized without it.
398de2bcc63SWarner Losh
399960773f7SWarner Losh20001205:
400960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
401960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
402960773f7SWarner Losh	adding the following in pam.conf:
403960773f7SWarner Losh
404960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
405960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
406960773f7SWarner Losh	sshd    session required        pam_permit.so
407960773f7SWarner Losh
4080acc635eSWarner Losh20001031:
4090acc635eSWarner Losh	cvs updated to 1.11.
4100acc635eSWarner Losh
4110acc635eSWarner Losh20001020:
4120acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
4130acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
4140acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
4150acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
4160acc635eSWarner Losh	workaround.
4170acc635eSWarner Losh
4180acc635eSWarner Losh20001010:
4190acc635eSWarner Losh	****************************** WARNING ******************************
4200acc635eSWarner Losh				Sendmail has been updated.
4210acc635eSWarner Losh	****************************** WARNING ******************************
4220acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
4230acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
4240acc635eSWarner Losh	  is set.
4250acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
4260acc635eSWarner Losh	  commands.
4270acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
4280acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
4290acc635eSWarner Losh	  in /usr/share/sendmail/cf.
4300acc635eSWarner Losh	o sendmail.cw changed to local-host-names
4310acc635eSWarner Losh
4320acc635eSWarner Losh	More details can be found at
4330acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
4340acc635eSWarner Losh
4356e98a146SWarner Losh20001009:
4366e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
4376e98a146SWarner Losh	your entire ports tree, or you will have problems.
4386e98a146SWarner Losh
4396e98a146SWarner Losh20001006:
440685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
4416e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
4426e98a146SWarner Losh	/usr/bin/miniperl.
4436e98a146SWarner Losh
444073113a4SWarner Losh20001005:
445073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
446685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
447073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
448073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
449073113a4SWarner Losh	tree for anything to work.
450073113a4SWarner Losh
4510acc635eSWarner Losh20000928:
4520acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
4530acc635eSWarner Losh
454be3885b3SWarner Losh20000916:
455be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
456be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
457be3885b3SWarner Losh	same time as your kernel.
458be3885b3SWarner Losh
45976ec9675SWarner Losh20000914:
46076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
46176ec9675SWarner Losh	include the device will cause suspended laptops losing time
46276ec9675SWarner Losh	when they resume.  Include
46376ec9675SWarner Losh		device		pmtimer
46476ec9675SWarner Losh	in your config file and
46501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
46676ec9675SWarner Losh	to your /boot/device.hints file.
46776ec9675SWarner Losh
468f4865386SMark Murray20000911:
469f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
470f4865386SMark Murray	rather than an option. The supplied kernel config files have
471f4865386SMark Murray	been updated. You will need to do something similar in your
472f4865386SMark Murray	own kernel config file.
473f4865386SMark Murray	Remove:
474f4865386SMark Murray		options		RANDOMDEV
475f4865386SMark Murray	Add:
476f4865386SMark Murray		device		random
477f4865386SMark Murray	If you prefer to load the loadable module, you need to do
478f4865386SMark Murray	nothing.
479f4865386SMark Murray
480d594498fSWarner Losh20000909:
481d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
482d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
483d594498fSWarner Losh	reflect this if you load this module at boot time.
484d594498fSWarner Losh	The line should read:
485d594498fSWarner Losh		random_load="YES"
486d594498fSWarner Losh
4870deb7ddcSWarner Losh20000907:
4880deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
48916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
49016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
49116eb772dSWarner Losh	sure you don't have model loading problems which might at
49216eb772dSWarner Losh	first blush appear related to SMP.
49352bf24e7SWarner Losh
4945a01880bSWarner Losh20000906:
4955a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
4965a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
4975a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
4985a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
4995a01880bSWarner Losh	don't have one, and you have host.conf.
5005a01880bSWarner Losh
5012b41163cSWarner Losh20000905:
50238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
50338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
50438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
50538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
50638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
50738d6ecd2SWarner Losh
50838d6ecd2SWarner Losh20000905:
5098aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
5108aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
5118aab4bc7SWarner Losh	is /boot/kernel.
5128aab4bc7SWarner Losh
5138aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
51438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
51538d6ecd2SWarner Losh	installkernel/installworld dance.
5162b41163cSWarner Losh
517d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
518d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
519d594498fSWarner Losh	modules in that directory instead of finding them in the correct
520d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
521d594498fSWarner Losh	is that the linux module crashes your machine after the update.
522d594498fSWarner Losh
523d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
524d594498fSWarner Losh		mv /modules.old /boot/kernel.old
525d594498fSWarner Losh		chflags noschg /kernel.old
526d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
527d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
528d594498fSWarner Losh	fi
529d594498fSWarner Losh
530c22a309cSWarner Losh20000904:
531c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
532c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
533c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
534c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
535c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
536c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
537c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
538c22a309cSWarner Losh	is not likely to be generated.
539c22a309cSWarner Losh
540fdb9f54dSWarner Losh20000825:
541fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
5429c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
5439c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
5449c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
5459c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
5469c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
5479c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
5489c1a7444SWarner Losh	kernel.
5499c1a7444SWarner Losh
5509c1a7444SWarner Losh20000821:
5519c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
5529c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
5539c1a7444SWarner Losh	/boot/loader.conf.
554fdb9f54dSWarner Losh
5558f250aa7SWarner Losh20000812:
5565da0d091SWarner Losh	suidperl is now always built and installed on the system, but
5575da0d091SWarner Losh	with permissions of 511.  If you have applications that use
5585da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
5595da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
5605da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
5615da0d091SWarner Losh	will fix this until the next build.
5625da0d091SWarner Losh
5635da0d091SWarner Losh20000812:
5648f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
5658f250aa7SWarner Losh	visible changes that may immediately affect your configuration
5668f250aa7SWarner Losh	include:
5678f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
5688f250aa7SWarner Losh	- newaliases limited to root and trusted users
5698f250aa7SWarner Losh	- MSA port (587) turned on by default
5708f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
5718f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
5728f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
5738f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
5748f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
5758f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
5768f250aa7SWarner Losh
57771c38472SWarner Losh20000810:
57871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
57971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
58071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
58171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
58271c38472SWarner Losh	specific use for it.
58371c38472SWarner Losh
58471c38472SWarner Losh20000729:
58571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
58671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
58771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
58871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
58971c38472SWarner Losh		# Enable network daemons for user convenience.
59071c38472SWarner Losh		inetd_enable="YES"
59171c38472SWarner Losh		portmap_enable="YES"
59271c38472SWarner Losh		sendmail_enable="YES"
59371c38472SWarner Losh
59471c38472SWarner Losh20000728:
59571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
59671c38472SWarner Losh	will need to change that to nullfs_load="YES".
59771c38472SWarner Losh
5981dece4a9SWarner Losh20000728:
5991dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
6001dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
6011dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
6021dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
6031dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
6041dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
6051dece4a9SWarner Losh	to /MYKERNEL.
6061dece4a9SWarner Losh
607409e887cSWarner Losh20000711:
608409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
609409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
610409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
611409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
612409e887cSWarner Losh	for details on potential problems that you might have and how
613409e887cSWarner Losh	to get around them.
614409e887cSWarner Losh
615409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
616409e887cSWarner Losh	clauses above, you needn't worry.
617409e887cSWarner Losh
618409e887cSWarner Losh20000711:
619409e887cSWarner Losh	/etc/security has been updated to print the inode number of
620409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
621409e887cSWarner Losh	in the number of changed programs the first time when you run
622409e887cSWarner Losh	mergemaster to get a new /etc/security.
623409e887cSWarner Losh
624673d13f2SWarner Losh20000710:
625673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
626673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
627673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
628673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
629673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
630673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
631673d13f2SWarner Losh	errors. (see below, 20000624).
632673d13f2SWarner Losh
633bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
6341dece4a9SWarner Losh
635673d13f2SWarner Losh20000709:
636c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
637c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
638c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
639673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
640673d13f2SWarner Losh
641e98e26cdSWarner Losh20000706:
642e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
643e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
644e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
645f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
646e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
6472c021c6cSMark Ovens	interim if needed.
648e98e26cdSWarner Losh
649e98e26cdSWarner Losh20000705:
650e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
651e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
652e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
653e98e26cdSWarner Losh	details.
654e98e26cdSWarner Losh
655c373950eSWarner Losh20000704:
6562f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
6572f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
6582f961bc8SWarner Losh
6592f961bc8SWarner Losh20000704:
660c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
661c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
662c373950eSWarner Losh	rc.d scripts that haven't been updated.
663c373950eSWarner Losh
66427dc3a2bSWarner Losh20000630:
66527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
66627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
66727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
66827dc3a2bSWarner Losh
669b8c215acSWarner Losh20000625:
670b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
67127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
67227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
67327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
67427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
67527dc3a2bSWarner Losh	were required.  You should check with the latest collections
67627dc3a2bSWarner Losh	to make sure that these haven't changed.
677b8c215acSWarner Losh
6787b990719SWarner Losh20000624:
6797b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
6807b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
6817b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
6827b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
6837b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
6847b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
6857b990719SWarner Losh	date to the completion of the work.
6867b990719SWarner Losh
68727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
68827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
68927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
69027dc3a2bSWarner Losh	recreate the random and urandom devices.
69127dc3a2bSWarner Losh
69281e54c50SWarner Losh20000622:
69381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
69481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
69581e54c50SWarner Losh	that used to be required when updating.
69681e54c50SWarner Losh
69739943833SWarner Losh20000621:
6982c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
6992a2f33fbSDaniel Baker	the config file update procedure.
7002a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
701c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
702a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
70339943833SWarner Losh
704290f9ad8SWarner Losh20000620:
705290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
706290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
707290f9ad8SWarner Losh	that workaround will no longer be required.
708290f9ad8SWarner Losh
70990fb6346SWarner Losh20000615:
71090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
71190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
71290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
71390fb6346SWarner Losh	devices.
71490fb6346SWarner Losh
715f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
716f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
717f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
718f75f65bbSWarner Losh	may work).
719f75f65bbSWarner Losh
720ba26da8eSWarner Losh20000612:
721ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
722290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
723c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
724290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
725f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
726f54a3542SWarner Losh	NEWCARD for examples of the new format.
727290f9ad8SWarner Losh
728d65850ebSWarner Losh20000522:
729ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
730d65850ebSWarner Losh	building a kernel after this point is advised that they need
731d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
732d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
733d65850ebSWarner Losh
734d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
735d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
736d9583a00SWarner Losh	is recommended that you don't set this option until the problem
737d9583a00SWarner Losh	is resolved.
738d9583a00SWarner Losh
7398039cedeSWarner Losh20000513:
7408039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
7418039cedeSWarner Losh
742d65850ebSWarner Losh20000510:
7438039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
7448039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
7458039cedeSWarner Losh	is requires for the boot blocks to build properly.
7468039cedeSWarner Losh
7478039cedeSWarner Losh20000503:
7488039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
7498039cedeSWarner Losh	is now available.
7508039cedeSWarner Losh
751d65850ebSWarner Losh20000502:
752d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
753d65850ebSWarner Losh	connected to the kernel building instead.
754d65850ebSWarner Losh
755be149406SNik Clayton20000427:
7568039cedeSWarner Losh	You may need to build gperf
7578039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
7588039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
7598039cedeSWarner Losh	an option only in -current.
7608039cedeSWarner Losh
7612b8dd5f4SWarner Losh20000417:
7622b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
763f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
7642b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
7652b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
7662c021c6cSMark Ovens	before you reboot, you'll need to issue:
7672b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
7682b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
7692b8dd5f4SWarner Losh
7708d9f1945SWarner Losh20000320:
7712b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
7722b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
7732b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
7748d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
7752b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
7768d9f1945SWarner Losh
777f8ab1dd6SWarner Losh20000319:
778f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
779f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
780f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
781f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
782f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
783f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
784f8ab1dd6SWarner Losh
78519cada77SWarner Losh20000318:
786f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
78719cada77SWarner Losh	Large kernel changes are being committed and are in the
78819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
78919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
79019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
79119cada77SWarner Losh	that you are loading are up to date.
792ba228352SWarner Losh
79319cada77SWarner Losh20000315:
7946d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
7956d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
7966d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
7976d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
7986d23c382SWarner Losh	boot.
7996d23c382SWarner Losh
8006d23c382SWarner Losh20000315:
80119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
80219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
80357199806SWarner Losh
804dc0dbf5cSWarner LoshCOMMON ITEMS:
805dc0dbf5cSWarner Losh
806a24eff53SWarner Losh	General Notes
807a24eff53SWarner Losh	-------------
808a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
809a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
810a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
811a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
812a24eff53SWarner Losh	or several minor releases, or when several months have passed
813a24eff53SWarner Losh	on the -current branch).
814a24eff53SWarner Losh
8155780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
8165780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
8175780f3baSWarner Losh	environment when searching for values for global variables.
8185780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
8195780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
8205780f3baSWarner Losh	page for more details.
8215780f3baSWarner Losh
822dc0dbf5cSWarner Losh	To build a kernel
823dc0dbf5cSWarner Losh	-----------------
824ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
825f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
826ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
8271e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8281e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
829dc0dbf5cSWarner Losh
830ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
831ba01eb20SWarner Losh	--------------------------------------------------------------
832ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
83347d0d01fSWarner Losh	config KERNEL_NAME_HERE
834ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
835ba01eb20SWarner Losh	make depend
836ba01eb20SWarner Losh	make
837ba01eb20SWarner Losh	make install
838ba01eb20SWarner Losh
839ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
840ba01eb20SWarner Losh
841ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
842ba01eb20SWarner Losh	-----------------------------------------------------------
843759f0aefSWarner Losh	make world
844fdb9f54dSWarner Losh	Build a new kernel, see above.
845759f0aefSWarner Losh
8461dece4a9SWarner Losh	To upgrade from 4.x-stable to current
847ba26da8eSWarner Losh	-------------------------------------
848ba26da8eSWarner Losh	make buildworld
8491e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
8507595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
8511e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
852ee6e1fc3SWarner Losh	reboot in single user [3]
853ba26da8eSWarner Losh	make installworld
854a6cd4f9dSWarner Losh	mergemaster		[4]
855134d2e86SWarner Losh	[1]
856ba26da8eSWarner Losh	<reboot>
857ba26da8eSWarner Losh
858fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
859fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
860fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
861fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
862fdb9f54dSWarner Losh	the UPDATING entries.
863ba26da8eSWarner Losh
8641dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
8651dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
8661dece4a9SWarner Losh	your sources that you have read and understood all the recent
8671dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
8681dece4a9SWarner Losh	much fewer pitfalls.
8691dece4a9SWarner Losh
870134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
871134d2e86SWarner Losh	should disable them at this point so they don't crash your
872134d2e86SWarner Losh	system on reboot.
873134d2e86SWarner Losh
8749c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
8759c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
8769c1a7444SWarner Losh	configuration.
8779c1a7444SWarner Losh
878ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
879ee6e1fc3SWarner Losh		fsck -p
880ee6e1fc3SWarner Losh		mount -u /
881ee6e1fc3SWarner Losh		mount -a
882ee6e1fc3SWarner Losh		cd /usr/src
88347d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
884ee6e1fc3SWarner Losh
885a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
886a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
887a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
888a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
889a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
890a6cd4f9dSWarner Losh	for potential gotchas.
891a6cd4f9dSWarner Losh
892dc0dbf5cSWarner LoshFORMAT:
893dc0dbf5cSWarner Losh
894f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
8951fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
896f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
897f8ab1dd6SWarner Loshprevious releases if your system is older than this.
8981fc1a0dcSWarner Losh
8993645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
9003645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
901f8c77507SWarner Losh
902e72fd46aSWarner LoshCopyright information:
903e72fd46aSWarner Losh
904e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
905e72fd46aSWarner Losh
906772730c7SWarner LoshRedistribution, publication, translation and use, with or without
907772730c7SWarner Loshmodification, in full or in part, in any form or format of this
908772730c7SWarner Loshdocument are permitted.
909e72fd46aSWarner Losh
910e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
911e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
912e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
913e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
914e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
915e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
916e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
917e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
918e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
919e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
920e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
921e72fd46aSWarner Losh
922e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
923e72fd46aSWarner Loshauthor a beer.
924e72fd46aSWarner Losh
92522306abcSWarner LoshContact Warner Losh if you have any questions about your use of
926772730c7SWarner Loshthis document.
927772730c7SWarner Losh
92897d92980SPeter Wemm$FreeBSD$
929