xref: /freebsd/UPDATING (revision 85aa5a2e0a9ad52d96d796900075f68c7f18743c)
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
869f7bcf3SWarner LoshNOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
969f7bcf3SWarner Losh	FreeBSD 5.0-CURRENT has many debugging features turned on, in
1069f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1169f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1269f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1369f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1469f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1569f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1669f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1769f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1869f7bcf3SWarner Losh	developers choose to disable these features on build machines
1969f7bcf3SWarner Losh	to maximize performance.
2069f7bcf3SWarner Losh
2169f7bcf3SWarner Losh	In addition, IDE write caching is currently disabled by default
2269f7bcf3SWarner Losh	due to on-going concerns about disk write order and file system
2369f7bcf3SWarner Losh	integrity.  Re-enabling write caching can substantially improve
2469f7bcf3SWarner Losh	performance.
2569f7bcf3SWarner Losh
2685aa5a2eSGregory Neil Shapiro20020404:
2785aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
2885aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
2985aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
3085aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
3185aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
3285aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
3385aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
3485aa5a2eSGregory Neil Shapiro
3585aa5a2eSGregory Neil Shapiro20020404:
3685aa5a2eSGregory Neil Shapiro	Due to the import of sendmail 8.12.2 (see 20020217 entry), a new
3785aa5a2eSGregory Neil Shapiro	user and group are required in order for sendmail to run as a
3885aa5a2eSGregory Neil Shapiro	set-group-ID binary.  A 'make installworld' will use the new user
3985aa5a2eSGregory Neil Shapiro	and group to set the owner and group of /var/spool/clientmqueue
4085aa5a2eSGregory Neil Shapiro	and will fail if the new user and group do not exist.  The 'smmsp'
4185aa5a2eSGregory Neil Shapiro	user and group must be merged from src/etc/group and
4285aa5a2eSGregory Neil Shapiro	src/etc/master.passwd before using 'make installworld'.
4385aa5a2eSGregory Neil Shapiro
442292c02eSWarner Losh20020315:
452292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
462292c02eSWarner Losh
4769f7bcf3SWarner Losh20020225:
4869f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
4969f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
5069f7bcf3SWarner Losh
518f35c493SWarner Losh20020217:
528f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
538f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
548f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
558f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
568f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
578f35c493SWarner Losh
58fa9401c1SWarner Losh20020112:
59fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
60fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
61fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
62fa9401c1SWarner Losh	you have local modifications, you can use
63fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
64fa9401c1SWarner Losh	/etc/pam.d.
65fa9401c1SWarner Losh
66fa9401c1SWarner Losh	Please see the following url for more details:
67fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
68fa9401c1SWarner Losh
6947d0d01fSWarner Losh20011229:
7047d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
7147d0d01fSWarner Losh	networkfs_types, please note that it has changed
7247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
7347d0d01fSWarner Losh
74514318a8SWarner Losh20011220:
75514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
76514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
77514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
78514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
79514318a8SWarner Losh	version have now been merged back into the base system's
80514318a8SWarner Losh	version now.  The only user-visible change resulting from this
81514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
82514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
83514318a8SWarner Losh	as well.  (There has never been rc file support for
84514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
85514318a8SWarner Losh	reverted by the time the changes are MFCed.)
86514318a8SWarner Losh
87514318a8SWarner Losh20011215:
88514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
89514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
90514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
91514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
92514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
93514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
94514318a8SWarner Losh	will need to be customized then for `odd' densities using
95514318a8SWarner Losh	fdcontrol(8).
96514318a8SWarner Losh
972d22e2bfSWarner Losh20011209:
982d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
992d22e2bfSWarner Losh	and truss(1) now works again.
1002d22e2bfSWarner Losh
1019e0428e2SWarner Losh20011207:
1029e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
1039e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
1049e0428e2SWarner Losh	see
1059e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
1069e0428e2SWarner Losh	for details.
1079e0428e2SWarner Losh
1089bab8c59SWarner Losh20011204:
1099bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
1109bab8c59SWarner Losh	kernel and burncd to be in sync.
1119bab8c59SWarner Losh
112e57d8b01SWarner Losh20011203:
113e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
114e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
115e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
116e57d8b01SWarner Losh	not there already.
117e57d8b01SWarner Losh
118e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
119e57d8b01SWarner Losh	until the issue has been resolved.
120e57d8b01SWarner Losh
121b001d36fSJacques Vidrine20011202:
122b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
123b001d36fSJacques Vidrine	patched.
124b001d36fSJacques Vidrine
1254b676ec1SWarner Losh20011126:
1264b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
1275ebbf43eSWarner Losh	after this date.  You need to do this only once.
1284b676ec1SWarner Losh
129d961e462SWarner Losh20011103:
130d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
131d961e462SWarner Losh	edges may be left, but for the most part things should be
1324b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
133d961e462SWarner Losh
134d961e462SWarner Losh20011030:
135d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
136d961e462SWarner Losh	choppy waves in the upgrade process.
137d961e462SWarner Losh
1381fe003b6SWarner Losh20011030:
139a4b6fda0SWarner Losh	The asr driver problem has been resolved.
1401fe003b6SWarner Losh
1411fe003b6SWarner Losh20011027:
1421fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
1431fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
1441fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
1451fe003b6SWarner Losh	try to use from this date forward.
1461fe003b6SWarner Losh
1471fe003b6SWarner Losh20011025:
1481fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
1491fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1501fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1511fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
1521fe003b6SWarner Losh	TARGET_ARCH=i386.
1531fe003b6SWarner Losh
154d05f9643SWarner Losh20011001:
155d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
156d05f9643SWarner Losh	You must recompile both the kernel and userland applications
157d05f9643SWarner Losh	at the same time.
158d05f9643SWarner Losh
15958970f85SWarner Losh20010929:
16058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
16158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
16258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
16358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
16458970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
16558970f85SWarner Losh
16658970f85SWarner Losh20010927:
16758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
16858970f85SWarner Losh	To disable ACPI you can add
169378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
17058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
17158970f85SWarner Losh	loader "ok" prompt).
17258970f85SWarner Losh
17358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
17458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
17558970f85SWarner Losh	file and not list acpi in that list.
176378f4486SAlfred Perlstein
1775119d237SWarner Losh20010924:
1785119d237SWarner Losh	The buildworld has been fixed.  You may need to install
1795119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
1808b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
1818b039fffSWarner Losh	get them installed on every installworld, or execute the
1828b039fffSWarner Losh	following to get them installed only once:
1838b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
18458970f85SWarner Losh		make all install
1858b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
1865119d237SWarner Losh
1873c293725SWarner Losh20010919:
1883c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
1893c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
1903c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
191772730c7SWarner Losh	workaround is to add
1923c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
1933c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
1943c293725SWarner Losh	can be removed afterwards.
1953c293725SWarner Losh
1963c293725SWarner Losh	A proper fix to the buildworld target is needed.
1973c293725SWarner Losh
1983c293725SWarner Losh20010918:
1993c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
2003c293725SWarner Losh	NFS may be unstable after this date.
2013c293725SWarner Losh
2023c293725SWarner Losh20010912:
2033c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
2043c293725SWarner Losh	the kernel.  While a few problems were introduced in the
2053c293725SWarner Losh	initial commit, most of the major ones have been found and
2063c293725SWarner Losh	corrected.
2073c293725SWarner Losh
2083c293725SWarner Losh20010901:
2093c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
2103c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
2113c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
2123c293725SWarner Losh	have been rectified around this date.
2133c293725SWarner Losh
21498b17b95SWarner Losh20010823:
21598b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
21698b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
21798b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
21898b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
21998b17b95SWarner Losh 	sure that user or group bind has read (and not write)
22098b17b95SWarner Losh 	permission for your name server configuration and that it
22198b17b95SWarner Losh 	has read and write permission for your slave zone files and
22298b17b95SWarner Losh 	directory.
22398b17b95SWarner Losh
22498b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
22598b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
22698b17b95SWarner Losh
22798b17b95SWarner Losh 		named_flags=
22898b17b95SWarner Losh
2297b9786edSMark Murray20010709:
2307b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
2317b9786edSMark Murray	the ability of the shared library major number to handle.
2327b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
2337b9786edSMark Murray	solution is to rebuild those ports.
2347b9786edSMark Murray
2351d28950eSWarner Losh20010628:
2361d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
2371d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
2381d28950eSWarner Losh
239e72fd46aSWarner Losh20010625:
24098b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
24198b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
24298b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
24398b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
24498b17b95SWarner Losh	IRQ configuration needs more safety belts.
24516de1a07SWarner Losh
2460d415dffSWarner Losh20010617:
247e72fd46aSWarner Losh	Softupdates problems have been corrected.
2480d415dffSWarner Losh
2490d415dffSWarner Losh20010614:
2500d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2510d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
2520d415dffSWarner Losh	kernel building methods.
2530d415dffSWarner Losh
2548b9959adSWarner Losh20010613:
2558b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
2568b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
257e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
258e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
2598b9959adSWarner Losh
260e72fd46aSWarner Losh20010613:
2618b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
262e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
263e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
2648b9959adSWarner Losh
2650d415dffSWarner Losh20010612:
2660d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
2670d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
2680d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
2690d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
2700d415dffSWarner Losh	until this bug is fixed.
2710d415dffSWarner Losh
272e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
273e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
274e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
275e72fd46aSWarner Losh
2760d415dffSWarner Losh20010610:
2770d415dffSWarner Losh	Locale names have changed to match other systems better.
2780d415dffSWarner Losh
2796ccdb5e4SWarner Losh20010604:
2806ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
2816ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
2826ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
2833590182eSWarner Losh	Interrupt storms look a lot like a hang.
2843590182eSWarner Losh
2853590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
2863590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
2873590182eSWarner Losh	it is).
2883590182eSWarner Losh
2893590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
2903590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
2913590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
2923590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
2936ccdb5e4SWarner Losh
2940bc62786SWarner Losh20010530:
2950bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
2960bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
2970bc62786SWarner Losh	a limited time.  If you see
2980bc62786SWarner Losh
2990bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
3000bc62786SWarner Losh
3010bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
3020bc62786SWarner Losh	COPY=-C.
3030bc62786SWarner Losh
30468a38c6cSWarner Losh20010525:
305b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
306c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
307c4f4a728SWarner Losh	definitely is in bad shape.
30868a38c6cSWarner Losh
309ed0f29caSWarner Losh20010521:
310f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
311ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
312ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
313ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
314ed0f29caSWarner Losh	is
315ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
316ed0f29caSWarner Losh
31780c16af9SWarner Losh20010520:
31868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
31980c16af9SWarner Losh
32080c16af9SWarner Losh20010519:
32180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
32280c16af9SWarner Losh	the past few days.  Everything should still work, but if
32380c16af9SWarner Losh	not, please contact imp@freebsd.org.
32480c16af9SWarner Losh
325a45f2d05SWarner Losh20010517:
326a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
327a45f2d05SWarner Losh	userland at the same time.
328a45f2d05SWarner Losh
329a45f2d05SWarner Losh20010517:
330a45f2d05SWarner Losh	New ncurses imported.
331a45f2d05SWarner Losh
3322988afcaSWarner Losh20010512:
3332988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
3342988afcaSWarner Losh	will be the only way to go starting July 1.
3352988afcaSWarner Losh
3361a33dba7SWarner Losh20010504:
3371a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
3381a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
3391a33dba7SWarner Losh
34009946a51SWarner Losh20010502:
34109946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
34209946a51SWarner Losh
34309946a51SWarner Losh20010501:
34409946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
34509946a51SWarner Losh
34609946a51SWarner Losh20010430:
347a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
34809946a51SWarner Losh	go back in the water.
34909946a51SWarner Losh
35009946a51SWarner Losh20010429:
35109946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
35209946a51SWarner Losh	this date, but before the correction date.
35309946a51SWarner Losh
35491dd3b53SWarner Losh20010423:
35591dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
35691dd3b53SWarner Losh
35791dd3b53SWarner Losh20010411:
35891dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
35991dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
36091dd3b53SWarner Losh	Update only if you understand that you must not use the old
36191dd3b53SWarner Losh	fsck with the new kernel ever.
36291dd3b53SWarner Losh
363933b3269SWarner Losh20010330:
364933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
365c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
366933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
367933b3269SWarner Losh
368933b3269SWarner Losh20010319:
369933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
370933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
371933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
372f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
37309946a51SWarner Losh
37409946a51SWarner Losh20010315:
37509946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
37609946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
37709946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
378933b3269SWarner Losh
379933b3269SWarner Losh20010312:
380933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
381933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
382933b3269SWarner Losh
383933b3269SWarner Losh20010312:
384933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
385933b3269SWarner Losh	instead of ad-hoc.
386933b3269SWarner Losh
387933b3269SWarner Losh20010310:
388f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
389933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
390933b3269SWarner Losh	ssh might not work if you don't.
391933b3269SWarner Losh
39262353691SWarner Losh20010303:
39362353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
39462353691SWarner Losh	which means that you must include the miibus in your kernel if
39562353691SWarner Losh	you use the ed driver.
39662353691SWarner Losh
397d325cf65SWarner Losh20010220:
398d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
399d325cf65SWarner Losh	safe to go back into the water.
400d325cf65SWarner Losh
401024daae6SWarner Losh20010211:
402024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
403024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
404024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
405024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
406024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
407024daae6SWarner Losh
408024daae6SWarner Losh	To get to the new system, you'll need to use the following
409024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
410024daae6SWarner Losh	don't have to move this to the updating section.
411024daae6SWarner Losh
412024daae6SWarner Losh	To get around the installworld problem, do:
413024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
414024daae6SWarner Losh		# make install
415024daae6SWarner Losh		# cd /usr/src
416024daae6SWarner Losh		# make installworld
417024daae6SWarner Losh	If that doesn't work, then try:
418024daae6SWarner Losh		# make -k installworld
419024daae6SWarner Losh		# make installworld
420024daae6SWarner Losh
421024daae6SWarner Losh20010207:
422024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
423024daae6SWarner Losh	do not include devfs in your kernel as problems result.
424024daae6SWarner Losh
425024daae6SWarner Losh20010205:
4267595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
427024daae6SWarner Losh	Remove them from your config.
428024daae6SWarner Losh
4291e159248SWarner Losh20010122:
4301e159248SWarner Losh	****************************** WARNING ******************************
4311e159248SWarner Losh			buildkernel has been changed slightly
4321e159248SWarner Losh	****************************** WARNING ******************************
4331e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
4341e159248SWarner Losh	should update your scripts and make.conf accordingly.
4351e159248SWarner Losh
4361e159248SWarner Losh20010119:
4371e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
4381e159248SWarner Losh	This requires a new config to build correctly.
4391e159248SWarner Losh
440aac7dfeaSWarner Losh20010116:
441aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
442aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
443aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
444aac7dfeaSWarner Losh
445aac7dfeaSWarner Losh20010110:
446aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
447aac7dfeaSWarner Losh
448aac7dfeaSWarner Losh20010102:
449aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
450aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
451aac7dfeaSWarner Losh
45263c90c9eSWarner Losh20010101:
45363c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
45463c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
4555fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
45663c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
45763c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
45863c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
45963c90c9eSWarner Losh	might have been ignored by the -k option.
46063c90c9eSWarner Losh
4615fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
4625fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
4635fd2a895SWarner Losh	of this working.
4645fd2a895SWarner Losh
465aac7dfeaSWarner Losh20001228:
466aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
467aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
468aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
469aac7dfeaSWarner Losh
470de2bcc63SWarner Losh20001218:
471de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
472de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
473de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
474de2bcc63SWarner Losh	cards will not be recognized without it.
475de2bcc63SWarner Losh
476960773f7SWarner Losh20001205:
477960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
478960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
479960773f7SWarner Losh	adding the following in pam.conf:
480960773f7SWarner Losh
481960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
482960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
483960773f7SWarner Losh	sshd    session required        pam_permit.so
484960773f7SWarner Losh
4850acc635eSWarner Losh20001031:
4860acc635eSWarner Losh	cvs updated to 1.11.
4870acc635eSWarner Losh
4880acc635eSWarner Losh20001020:
4890acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
4900acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
4910acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
4920acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
4930acc635eSWarner Losh	workaround.
4940acc635eSWarner Losh
4950acc635eSWarner Losh20001010:
4960acc635eSWarner Losh	****************************** WARNING ******************************
4970acc635eSWarner Losh				Sendmail has been updated.
4980acc635eSWarner Losh	****************************** WARNING ******************************
4990acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
5000acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
5010acc635eSWarner Losh	  is set.
5020acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
5030acc635eSWarner Losh	  commands.
5040acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
5050acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
5060acc635eSWarner Losh	  in /usr/share/sendmail/cf.
5070acc635eSWarner Losh	o sendmail.cw changed to local-host-names
5080acc635eSWarner Losh
5090acc635eSWarner Losh	More details can be found at
5100acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
5110acc635eSWarner Losh
5126e98a146SWarner Losh20001009:
5136e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
5146e98a146SWarner Losh	your entire ports tree, or you will have problems.
5156e98a146SWarner Losh
5166e98a146SWarner Losh20001006:
517685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
5186e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
5196e98a146SWarner Losh	/usr/bin/miniperl.
5206e98a146SWarner Losh
521073113a4SWarner Losh20001005:
522073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
523685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
524073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
525073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
526073113a4SWarner Losh	tree for anything to work.
527073113a4SWarner Losh
5280acc635eSWarner Losh20000928:
5290acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
5300acc635eSWarner Losh
531be3885b3SWarner Losh20000916:
532be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
533be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
534be3885b3SWarner Losh	same time as your kernel.
535be3885b3SWarner Losh
53676ec9675SWarner Losh20000914:
53776ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
53876ec9675SWarner Losh	include the device will cause suspended laptops losing time
53976ec9675SWarner Losh	when they resume.  Include
54076ec9675SWarner Losh		device		pmtimer
54176ec9675SWarner Losh	in your config file and
54201b9a434SWarner Losh		hint.pmtimer.0.at="isa"
54376ec9675SWarner Losh	to your /boot/device.hints file.
54476ec9675SWarner Losh
545f4865386SMark Murray20000911:
546f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
547f4865386SMark Murray	rather than an option. The supplied kernel config files have
548f4865386SMark Murray	been updated. You will need to do something similar in your
549f4865386SMark Murray	own kernel config file.
550f4865386SMark Murray	Remove:
551f4865386SMark Murray		options		RANDOMDEV
552f4865386SMark Murray	Add:
553f4865386SMark Murray		device		random
554f4865386SMark Murray	If you prefer to load the loadable module, you need to do
555f4865386SMark Murray	nothing.
556f4865386SMark Murray
557d594498fSWarner Losh20000909:
558d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
559d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
560d594498fSWarner Losh	reflect this if you load this module at boot time.
561d594498fSWarner Losh	The line should read:
562d594498fSWarner Losh		random_load="YES"
563d594498fSWarner Losh
5640deb7ddcSWarner Losh20000907:
5650deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
56616eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
56716eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
56816eb772dSWarner Losh	sure you don't have model loading problems which might at
56916eb772dSWarner Losh	first blush appear related to SMP.
57052bf24e7SWarner Losh
5715a01880bSWarner Losh20000906:
5725a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
5735a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
5745a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
5755a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
5765a01880bSWarner Losh	don't have one, and you have host.conf.
5775a01880bSWarner Losh
5782b41163cSWarner Losh20000905:
57938d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
58038d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
58138d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
58238d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
58338d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
58438d6ecd2SWarner Losh
58538d6ecd2SWarner Losh20000905:
5868aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
5878aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
5888aab4bc7SWarner Losh	is /boot/kernel.
5898aab4bc7SWarner Losh
5908aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
59138d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
59238d6ecd2SWarner Losh	installkernel/installworld dance.
5932b41163cSWarner Losh
594d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
595d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
596d594498fSWarner Losh	modules in that directory instead of finding them in the correct
597d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
598d594498fSWarner Losh	is that the linux module crashes your machine after the update.
599d594498fSWarner Losh
600d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
601d594498fSWarner Losh		mv /modules.old /boot/kernel.old
602d594498fSWarner Losh		chflags noschg /kernel.old
603d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
604d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
605d594498fSWarner Losh	fi
606d594498fSWarner Losh
607c22a309cSWarner Losh20000904:
608c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
609c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
610c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
611c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
612c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
613c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
614c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
615c22a309cSWarner Losh	is not likely to be generated.
616c22a309cSWarner Losh
617fdb9f54dSWarner Losh20000825:
618fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
6199c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
6209c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
6219c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
6229c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
6239c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
6249c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
6259c1a7444SWarner Losh	kernel.
6269c1a7444SWarner Losh
6279c1a7444SWarner Losh20000821:
6289c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
6299c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
6309c1a7444SWarner Losh	/boot/loader.conf.
631fdb9f54dSWarner Losh
6328f250aa7SWarner Losh20000812:
6335da0d091SWarner Losh	suidperl is now always built and installed on the system, but
6345da0d091SWarner Losh	with permissions of 511.  If you have applications that use
6355da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
6365da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
6375da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
6385da0d091SWarner Losh	will fix this until the next build.
6395da0d091SWarner Losh
6405da0d091SWarner Losh20000812:
6418f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
6428f250aa7SWarner Losh	visible changes that may immediately affect your configuration
6438f250aa7SWarner Losh	include:
6448f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
6458f250aa7SWarner Losh	- newaliases limited to root and trusted users
6468f250aa7SWarner Losh	- MSA port (587) turned on by default
6478f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
6488f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
6498f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6508f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6518f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
6528f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
6538f250aa7SWarner Losh
65471c38472SWarner Losh20000810:
65571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
65671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
65771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
65871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
65971c38472SWarner Losh	specific use for it.
66071c38472SWarner Losh
66171c38472SWarner Losh20000729:
66271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
66371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
66471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
66571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
66671c38472SWarner Losh		# Enable network daemons for user convenience.
66771c38472SWarner Losh		inetd_enable="YES"
66871c38472SWarner Losh		portmap_enable="YES"
66971c38472SWarner Losh		sendmail_enable="YES"
67071c38472SWarner Losh
67171c38472SWarner Losh20000728:
67271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
67371c38472SWarner Losh	will need to change that to nullfs_load="YES".
67471c38472SWarner Losh
6751dece4a9SWarner Losh20000728:
6761dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
6771dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
6781dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
6791dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
6801dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
6811dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
6821dece4a9SWarner Losh	to /MYKERNEL.
6831dece4a9SWarner Losh
684409e887cSWarner Losh20000711:
685409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
686409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
687409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
688409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
689409e887cSWarner Losh	for details on potential problems that you might have and how
690409e887cSWarner Losh	to get around them.
691409e887cSWarner Losh
692409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
693409e887cSWarner Losh	clauses above, you needn't worry.
694409e887cSWarner Losh
695409e887cSWarner Losh20000711:
696409e887cSWarner Losh	/etc/security has been updated to print the inode number of
697409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
698409e887cSWarner Losh	in the number of changed programs the first time when you run
699409e887cSWarner Losh	mergemaster to get a new /etc/security.
700409e887cSWarner Losh
701673d13f2SWarner Losh20000710:
702673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
703673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
704673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
705673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
706673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
707673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
708673d13f2SWarner Losh	errors. (see below, 20000624).
709673d13f2SWarner Losh
710bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
7111dece4a9SWarner Losh
712673d13f2SWarner Losh20000709:
713c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
714c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
715c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
716673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
717673d13f2SWarner Losh
718e98e26cdSWarner Losh20000706:
719e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
720e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
721e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
722f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
723e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
7242c021c6cSMark Ovens	interim if needed.
725e98e26cdSWarner Losh
726e98e26cdSWarner Losh20000705:
727e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
728e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
729e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
730e98e26cdSWarner Losh	details.
731e98e26cdSWarner Losh
732c373950eSWarner Losh20000704:
7332f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
7342f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
7352f961bc8SWarner Losh
7362f961bc8SWarner Losh20000704:
737c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
738c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
739c373950eSWarner Losh	rc.d scripts that haven't been updated.
740c373950eSWarner Losh
74127dc3a2bSWarner Losh20000630:
74227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
74327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
74427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
74527dc3a2bSWarner Losh
746b8c215acSWarner Losh20000625:
747b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
74827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
74927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
75027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
75127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
75227dc3a2bSWarner Losh	were required.  You should check with the latest collections
75327dc3a2bSWarner Losh	to make sure that these haven't changed.
754b8c215acSWarner Losh
7557b990719SWarner Losh20000624:
7567b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
7577b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
7587b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
7591a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
7607b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
7617b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
7627b990719SWarner Losh	date to the completion of the work.
7637b990719SWarner Losh
76427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
76527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
76627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
76727dc3a2bSWarner Losh	recreate the random and urandom devices.
76827dc3a2bSWarner Losh
76981e54c50SWarner Losh20000622:
77081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
77181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
77281e54c50SWarner Losh	that used to be required when updating.
77381e54c50SWarner Losh
77439943833SWarner Losh20000621:
7752c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
7762a2f33fbSDaniel Baker	the config file update procedure.
7772a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
778c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
779a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
78039943833SWarner Losh
781290f9ad8SWarner Losh20000620:
782290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
783290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
784290f9ad8SWarner Losh	that workaround will no longer be required.
785290f9ad8SWarner Losh
78690fb6346SWarner Losh20000615:
78790fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
78890fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
78990fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
79090fb6346SWarner Losh	devices.
79190fb6346SWarner Losh
792f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
793f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
794f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
795f75f65bbSWarner Losh	may work).
796f75f65bbSWarner Losh
797ba26da8eSWarner Losh20000612:
798ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
799290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
800c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
801290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
802f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
803f54a3542SWarner Losh	NEWCARD for examples of the new format.
804290f9ad8SWarner Losh
805d65850ebSWarner Losh20000522:
806ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
807d65850ebSWarner Losh	building a kernel after this point is advised that they need
808d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
809d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
810d65850ebSWarner Losh
811d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
812d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
813d9583a00SWarner Losh	is recommended that you don't set this option until the problem
814d9583a00SWarner Losh	is resolved.
815d9583a00SWarner Losh
8168039cedeSWarner Losh20000513:
8178039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
8188039cedeSWarner Losh
819d65850ebSWarner Losh20000510:
8208039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
8218039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
8228039cedeSWarner Losh	is requires for the boot blocks to build properly.
8238039cedeSWarner Losh
8248039cedeSWarner Losh20000503:
8258039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
8268039cedeSWarner Losh	is now available.
8278039cedeSWarner Losh
828d65850ebSWarner Losh20000502:
829d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
830d65850ebSWarner Losh	connected to the kernel building instead.
831d65850ebSWarner Losh
832be149406SNik Clayton20000427:
8338039cedeSWarner Losh	You may need to build gperf
8348039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
8358039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
8368039cedeSWarner Losh	an option only in -current.
8378039cedeSWarner Losh
8382b8dd5f4SWarner Losh20000417:
8392b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
840f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
8412b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
8422b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
8432c021c6cSMark Ovens	before you reboot, you'll need to issue:
8442b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
8452b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
8462b8dd5f4SWarner Losh
8478d9f1945SWarner Losh20000320:
8482b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
8492b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
8502b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
8518d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
8522b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
8538d9f1945SWarner Losh
854f8ab1dd6SWarner Losh20000319:
855f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
856f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
857f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
858f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
859f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
860f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
861f8ab1dd6SWarner Losh
86219cada77SWarner Losh20000318:
863f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
86419cada77SWarner Losh	Large kernel changes are being committed and are in the
86519cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
86619cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
86719cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
86819cada77SWarner Losh	that you are loading are up to date.
869ba228352SWarner Losh
87019cada77SWarner Losh20000315:
8716d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
8726d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
8736d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
8746d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
8756d23c382SWarner Losh	boot.
8766d23c382SWarner Losh
8776d23c382SWarner Losh20000315:
87819cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
87919cada77SWarner Losh	to upgrade to 4.0 from 3.x.
88057199806SWarner Losh
881dc0dbf5cSWarner LoshCOMMON ITEMS:
882dc0dbf5cSWarner Losh
883a24eff53SWarner Losh	General Notes
884a24eff53SWarner Losh	-------------
885a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
886a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
887a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
888a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
889a24eff53SWarner Losh	or several minor releases, or when several months have passed
890a24eff53SWarner Losh	on the -current branch).
891a24eff53SWarner Losh
8925780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
8935780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
8945780f3baSWarner Losh	environment when searching for values for global variables.
8955780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
8965780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
8975780f3baSWarner Losh	page for more details.
8985780f3baSWarner Losh
899dc0dbf5cSWarner Losh	To build a kernel
900dc0dbf5cSWarner Losh	-----------------
901ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
902f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
903ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
9041e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9051e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
906dc0dbf5cSWarner Losh
907ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
908ba01eb20SWarner Losh	--------------------------------------------------------------
909ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
91047d0d01fSWarner Losh	config KERNEL_NAME_HERE
911ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
912ba01eb20SWarner Losh	make depend
913ba01eb20SWarner Losh	make
914ba01eb20SWarner Losh	make install
915ba01eb20SWarner Losh
916ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
917ba01eb20SWarner Losh
918ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
919ba01eb20SWarner Losh	-----------------------------------------------------------
920759f0aefSWarner Losh	make world
921fdb9f54dSWarner Losh	Build a new kernel, see above.
922759f0aefSWarner Losh
9231dece4a9SWarner Losh	To upgrade from 4.x-stable to current
924ba26da8eSWarner Losh	-------------------------------------
925ba26da8eSWarner Losh	make buildworld
9261e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9277595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
9281e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
929ee6e1fc3SWarner Losh	reboot in single user [3]
930ba26da8eSWarner Losh	make installworld
931a6cd4f9dSWarner Losh	mergemaster		[4]
932134d2e86SWarner Losh	[1]
933ba26da8eSWarner Losh	<reboot>
934ba26da8eSWarner Losh
935fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
936fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
937fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
938fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
939fdb9f54dSWarner Losh	the UPDATING entries.
940ba26da8eSWarner Losh
9411dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
9421dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
9431dece4a9SWarner Losh	your sources that you have read and understood all the recent
9441dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
9451dece4a9SWarner Losh	much fewer pitfalls.
9461dece4a9SWarner Losh
947134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
948134d2e86SWarner Losh	should disable them at this point so they don't crash your
949134d2e86SWarner Losh	system on reboot.
950134d2e86SWarner Losh
9519c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
9529c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
9539c1a7444SWarner Losh	configuration.
9549c1a7444SWarner Losh
955ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
956ee6e1fc3SWarner Losh		fsck -p
957ee6e1fc3SWarner Losh		mount -u /
958ee6e1fc3SWarner Losh		mount -a
959ee6e1fc3SWarner Losh		cd /usr/src
96047d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
961ee6e1fc3SWarner Losh
962a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
963a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
964a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
965a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
966a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
967a6cd4f9dSWarner Losh	for potential gotchas.
968a6cd4f9dSWarner Losh
969dc0dbf5cSWarner LoshFORMAT:
970dc0dbf5cSWarner Losh
971f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
9721fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
973f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
974f8ab1dd6SWarner Loshprevious releases if your system is older than this.
9751fc1a0dcSWarner Losh
9763645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
9773645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
978f8c77507SWarner Losh
979e72fd46aSWarner LoshCopyright information:
980e72fd46aSWarner Losh
981e72fd46aSWarner LoshCopyright 1998, 2001 M. Warner Losh.  All Rights Reserved.
982e72fd46aSWarner Losh
983772730c7SWarner LoshRedistribution, publication, translation and use, with or without
984772730c7SWarner Loshmodification, in full or in part, in any form or format of this
985772730c7SWarner Loshdocument are permitted.
986e72fd46aSWarner Losh
987e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
988e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
989e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
990e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
991e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
992e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
993e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
994e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
995e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
996e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
997e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
998e72fd46aSWarner Losh
999e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1000e72fd46aSWarner Loshauthor a beer.
1001e72fd46aSWarner Losh
100222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1003772730c7SWarner Loshthis document.
1004772730c7SWarner Losh
100597d92980SPeter Wemm$FreeBSD$
1006