xref: /freebsd/UPDATING (revision 0d533e437d5ab3149e9380d9b0b7819221869d9f)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3e72fd46aSWarner LoshThis file is maintained and copyrighted by M. Warner Losh
49698f2c0SWarner Losh<imp@village.org>.  See end of file for further details.  For commonly
59698f2c0SWarner Loshdone items, please see the COMMON ITEMS: section later in the file.
6e72fd46aSWarner Losh
769f7bcf3SWarner LoshNOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
869f7bcf3SWarner Losh	FreeBSD 5.0-CURRENT has many debugging features turned on, in
969f7bcf3SWarner Losh	both the kernel and userland.  These features attempt to detect
1069f7bcf3SWarner Losh	incorrect use of system primitives, and encourage loud failure
1169f7bcf3SWarner Losh	through extra sanity checking and fail stop semantics.  They
1269f7bcf3SWarner Losh	also substantially impact system performance.  If you want to
1369f7bcf3SWarner Losh	do performance measurement, benchmarking, and optimization,
1469f7bcf3SWarner Losh	you'll want to turn them off.  This includes various WITNESS-
1569f7bcf3SWarner Losh	related kernel options, INVARIANTS, malloc debugging flags
1669f7bcf3SWarner Losh	in userland, and various verbose features in the kernel.  Many
1769f7bcf3SWarner Losh	developers choose to disable these features on build machines
1869f7bcf3SWarner Losh	to maximize performance.
1969f7bcf3SWarner Losh
2069f7bcf3SWarner Losh	In addition, IDE write caching is currently disabled by default
2169f7bcf3SWarner Losh	due to on-going concerns about disk write order and file system
2269f7bcf3SWarner Losh	integrity.  Re-enabling write caching can substantially improve
2369f7bcf3SWarner Losh	performance.
2469f7bcf3SWarner Losh
250d533e43SRuslan Ermilov20020815:
260d533e43SRuslan Ermilov	A "bug" in gcc(1) that was hiding warning in system headers was
270d533e43SRuslan Ermilov	fixed.  It's probably time to add -DNO_WERROR to your make line
280d533e43SRuslan Ermilov	again.
290d533e43SRuslan Ermilov
3033c1de7dSRuslan Ermilov20020729:
3133c1de7dSRuslan Ermilov	COPY is being deprecated.  The 20010530 change was reverted, as
3233c1de7dSRuslan Ermilov	it causes far more pain than was expected, and to always compare
3333c1de7dSRuslan Ermilov	before installing, please use INSTALL="install -C" again.  The
3433c1de7dSRuslan Ermilov	-C option is now silently ignored when used with the -d option.
3533c1de7dSRuslan Ermilov
362b877facSJulian Elischer20020702:
372b877facSJulian Elischer	Problems with libc_r clients like KDE and GNOME have been resolved.
382b877facSJulian Elischer	There are still some minor problems with some signals but the
392b877facSJulian Elischer	system is stable enough for general use again. SMP is less so than UP
402b877facSJulian Elischer	but each can successfully complete multiple buildworlds.
412b877facSJulian Elischer	Libkvm needs to be recompiled due to KSE.
422b877facSJulian Elischer
4306596d37SWarner Losh20020701:
4406596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
4506596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
4606596d37SWarner Losh	GNOME.
4706596d37SWarner Losh
4895ba4330SJacques Vidrine20020511:
4995ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
5095ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
5195ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
5295ba4330SJacques Vidrine	with the set-user-ID bit set.
5395ba4330SJacques Vidrine
54a81da3c9SDavid E. O'Brien20020510:
55f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
56f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
574b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
58f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
59f50caf6fSDavid E. O'Brien
60f50caf6fSDavid E. O'Brien20020510:
61a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
62a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
63a81da3c9SDavid E. O'Brien	and then do a cvs update.
64a81da3c9SDavid E. O'Brien
65528a0ef5SJacques Vidrine20020421:
66528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
67528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
68528a0ef5SJacques Vidrine
6985aa5a2eSGregory Neil Shapiro20020404:
7085aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
7185aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
7285aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
7385aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
7485aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
7585aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
7685aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
7785aa5a2eSGregory Neil Shapiro
788f1e4358SRuslan Ermilov20020403:
798f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
808f1e4358SRuslan Ermilov
812292c02eSWarner Losh20020315:
822292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
832292c02eSWarner Losh
8469f7bcf3SWarner Losh20020225:
8569f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
8669f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
8769f7bcf3SWarner Losh
888f35c493SWarner Losh20020217:
898f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
908f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
918f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
928f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
938f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
948f35c493SWarner Losh
95835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
96835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
97835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
98835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
99835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
100835284beSWarner Losh	and group must be merged from src/etc/group and
101835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
102835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
103835284beSWarner Losh	mergemaster before this will work if you are updating from a
104835284beSWarner Losh	very old version of current.  The updating recipe has changed
105835284beSWarner Losh	as of this date.
106835284beSWarner Losh
107fa9401c1SWarner Losh20020112:
108fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
109fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
110fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
111fa9401c1SWarner Losh	you have local modifications, you can use
112fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
113fa9401c1SWarner Losh	/etc/pam.d.
114fa9401c1SWarner Losh
115fa9401c1SWarner Losh	Please see the following url for more details:
116fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
11747d0d01fSWarner Losh20011229:
11847d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
11947d0d01fSWarner Losh	networkfs_types, please note that it has changed
12047d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
12147d0d01fSWarner Losh
122514318a8SWarner Losh20011220:
123514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
124514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
125514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
126514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
127514318a8SWarner Losh	version have now been merged back into the base system's
128514318a8SWarner Losh	version now.  The only user-visible change resulting from this
129514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
130514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
131514318a8SWarner Losh	as well.  (There has never been rc file support for
132514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
133514318a8SWarner Losh	reverted by the time the changes are MFCed.)
134514318a8SWarner Losh
135514318a8SWarner Losh20011215:
136514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
137514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
138514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
139514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
140514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
141514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
142514318a8SWarner Losh	will need to be customized then for `odd' densities using
143514318a8SWarner Losh	fdcontrol(8).
144514318a8SWarner Losh
1452d22e2bfSWarner Losh20011209:
1462d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
1472d22e2bfSWarner Losh	and truss(1) now works again.
1482d22e2bfSWarner Losh
1499e0428e2SWarner Losh20011207:
1509e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
1519e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
1529e0428e2SWarner Losh	see
1539e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
1549e0428e2SWarner Losh	for details.
1559e0428e2SWarner Losh
1569bab8c59SWarner Losh20011204:
1579bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
1589bab8c59SWarner Losh	kernel and burncd to be in sync.
1599bab8c59SWarner Losh
160e57d8b01SWarner Losh20011203:
161e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
162e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
163e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
164e57d8b01SWarner Losh	not there already.
165e57d8b01SWarner Losh
166e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
167e57d8b01SWarner Losh	until the issue has been resolved.
168e57d8b01SWarner Losh
169b001d36fSJacques Vidrine20011202:
170b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
171b001d36fSJacques Vidrine	patched.
172b001d36fSJacques Vidrine
1734b676ec1SWarner Losh20011126:
1744b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
1755ebbf43eSWarner Losh	after this date.  You need to do this only once.
1764b676ec1SWarner Losh
177d961e462SWarner Losh20011103:
178d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
179d961e462SWarner Losh	edges may be left, but for the most part things should be
1804b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
181d961e462SWarner Losh
182d961e462SWarner Losh20011030:
183d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
184d961e462SWarner Losh	choppy waves in the upgrade process.
185d961e462SWarner Losh
1861fe003b6SWarner Losh20011030:
187a4b6fda0SWarner Losh	The asr driver problem has been resolved.
1881fe003b6SWarner Losh
1891fe003b6SWarner Losh20011027:
1901fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
1911fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
1921fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
1931fe003b6SWarner Losh	try to use from this date forward.
1941fe003b6SWarner Losh
1951fe003b6SWarner Losh20011025:
1961fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
1971fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1981fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1991fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
2001fe003b6SWarner Losh	TARGET_ARCH=i386.
2011fe003b6SWarner Losh
202d05f9643SWarner Losh20011001:
203d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
204d05f9643SWarner Losh	You must recompile both the kernel and userland applications
205d05f9643SWarner Losh	at the same time.
206d05f9643SWarner Losh
20758970f85SWarner Losh20010929:
20858970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
20958970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
21058970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
21158970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
21258970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
21358970f85SWarner Losh
21458970f85SWarner Losh20010927:
21558970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
21658970f85SWarner Losh	To disable ACPI you can add
217378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
21858970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
21958970f85SWarner Losh	loader "ok" prompt).
22058970f85SWarner Losh
22158970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
22258970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
22358970f85SWarner Losh	file and not list acpi in that list.
224378f4486SAlfred Perlstein
2255119d237SWarner Losh20010924:
2265119d237SWarner Losh	The buildworld has been fixed.  You may need to install
2275119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
2288b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
2298b039fffSWarner Losh	get them installed on every installworld, or execute the
2308b039fffSWarner Losh	following to get them installed only once:
2318b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
23258970f85SWarner Losh		make all install
2338b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
2345119d237SWarner Losh
2353c293725SWarner Losh20010919:
2363c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
2373c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
2383c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
239772730c7SWarner Losh	workaround is to add
2403c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
2413c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
2423c293725SWarner Losh	can be removed afterwards.
2433c293725SWarner Losh
2443c293725SWarner Losh	A proper fix to the buildworld target is needed.
2453c293725SWarner Losh
2463c293725SWarner Losh20010918:
2473c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
2483c293725SWarner Losh	NFS may be unstable after this date.
2493c293725SWarner Losh
2503c293725SWarner Losh20010912:
2513c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
2523c293725SWarner Losh	the kernel.  While a few problems were introduced in the
2533c293725SWarner Losh	initial commit, most of the major ones have been found and
2543c293725SWarner Losh	corrected.
2553c293725SWarner Losh
2563c293725SWarner Losh20010901:
2573c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
2583c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
2593c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
2603c293725SWarner Losh	have been rectified around this date.
2613c293725SWarner Losh
26298b17b95SWarner Losh20010823:
26398b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
26498b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
26598b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
26698b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
26798b17b95SWarner Losh 	sure that user or group bind has read (and not write)
26898b17b95SWarner Losh 	permission for your name server configuration and that it
26998b17b95SWarner Losh 	has read and write permission for your slave zone files and
27098b17b95SWarner Losh 	directory.
27198b17b95SWarner Losh
27298b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
27398b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
27498b17b95SWarner Losh
27598b17b95SWarner Losh 		named_flags=
27698b17b95SWarner Losh
2777b9786edSMark Murray20010709:
2787b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
2797b9786edSMark Murray	the ability of the shared library major number to handle.
2807b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
2817b9786edSMark Murray	solution is to rebuild those ports.
2827b9786edSMark Murray
2831d28950eSWarner Losh20010628:
2841d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
2851d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
2861d28950eSWarner Losh
287e72fd46aSWarner Losh20010625:
28898b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
28998b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
29098b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
29198b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
29298b17b95SWarner Losh	IRQ configuration needs more safety belts.
29316de1a07SWarner Losh
2940d415dffSWarner Losh20010617:
295e72fd46aSWarner Losh	Softupdates problems have been corrected.
2960d415dffSWarner Losh
2970d415dffSWarner Losh20010614:
2980d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2990d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
3000d415dffSWarner Losh	kernel building methods.
3010d415dffSWarner Losh
3028b9959adSWarner Losh20010613:
3038b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
3048b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
305e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
306e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
3078b9959adSWarner Losh
308e72fd46aSWarner Losh20010613:
3098b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
310e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
311e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
3128b9959adSWarner Losh
3130d415dffSWarner Losh20010612:
3140d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
3150d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
3160d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
3170d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
3180d415dffSWarner Losh	until this bug is fixed.
3190d415dffSWarner Losh
320e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
321e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
322e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
323e72fd46aSWarner Losh
3240d415dffSWarner Losh20010610:
3250d415dffSWarner Losh	Locale names have changed to match other systems better.
3260d415dffSWarner Losh
3276ccdb5e4SWarner Losh20010604:
3286ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
3296ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
3306ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
3313590182eSWarner Losh	Interrupt storms look a lot like a hang.
3323590182eSWarner Losh
3333590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
3343590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
3353590182eSWarner Losh	it is).
3363590182eSWarner Losh
3373590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
3383590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
3393590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
3403590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
3416ccdb5e4SWarner Losh
3420bc62786SWarner Losh20010530:
3430bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
3440bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
3450bc62786SWarner Losh	a limited time.  If you see
3460bc62786SWarner Losh
3470bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
3480bc62786SWarner Losh
3490bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
3500bc62786SWarner Losh	COPY=-C.
3510bc62786SWarner Losh
35268a38c6cSWarner Losh20010525:
353b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
354c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
355c4f4a728SWarner Losh	definitely is in bad shape.
35668a38c6cSWarner Losh
357ed0f29caSWarner Losh20010521:
358f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
359ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
360ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
361ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
362ed0f29caSWarner Losh	is
363ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
364ed0f29caSWarner Losh
36580c16af9SWarner Losh20010520:
36668a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
36780c16af9SWarner Losh
36880c16af9SWarner Losh20010519:
36980c16af9SWarner Losh	pccard has had much reorganizational work done to it over
37080c16af9SWarner Losh	the past few days.  Everything should still work, but if
37180c16af9SWarner Losh	not, please contact imp@freebsd.org.
37280c16af9SWarner Losh
373a45f2d05SWarner Losh20010517:
374a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
375a45f2d05SWarner Losh	userland at the same time.
376a45f2d05SWarner Losh
377a45f2d05SWarner Losh20010517:
378a45f2d05SWarner Losh	New ncurses imported.
379a45f2d05SWarner Losh
3802988afcaSWarner Losh20010512:
3812988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
3822988afcaSWarner Losh	will be the only way to go starting July 1.
3832988afcaSWarner Losh
3841a33dba7SWarner Losh20010504:
3851a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
3861a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
3871a33dba7SWarner Losh
38809946a51SWarner Losh20010502:
38909946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
39009946a51SWarner Losh
39109946a51SWarner Losh20010501:
39209946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
39309946a51SWarner Losh
39409946a51SWarner Losh20010430:
395a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
39609946a51SWarner Losh	go back in the water.
39709946a51SWarner Losh
39809946a51SWarner Losh20010429:
39909946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
40009946a51SWarner Losh	this date, but before the correction date.
40109946a51SWarner Losh
40291dd3b53SWarner Losh20010423:
40391dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
40491dd3b53SWarner Losh
40591dd3b53SWarner Losh20010411:
40691dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
40791dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
40891dd3b53SWarner Losh	Update only if you understand that you must not use the old
40991dd3b53SWarner Losh	fsck with the new kernel ever.
41091dd3b53SWarner Losh
411933b3269SWarner Losh20010330:
412933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
413c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
414933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
415933b3269SWarner Losh
416933b3269SWarner Losh20010319:
417933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
418933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
419933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
420f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
42109946a51SWarner Losh
42209946a51SWarner Losh20010315:
42309946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
42409946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
42509946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
426933b3269SWarner Losh
427933b3269SWarner Losh20010312:
428933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
429933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
430933b3269SWarner Losh
431933b3269SWarner Losh20010312:
432933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
433933b3269SWarner Losh	instead of ad-hoc.
434933b3269SWarner Losh
435933b3269SWarner Losh20010310:
436f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
437933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
438933b3269SWarner Losh	ssh might not work if you don't.
439933b3269SWarner Losh
44062353691SWarner Losh20010303:
44162353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
44262353691SWarner Losh	which means that you must include the miibus in your kernel if
44362353691SWarner Losh	you use the ed driver.
44462353691SWarner Losh
445d325cf65SWarner Losh20010220:
446d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
447d325cf65SWarner Losh	safe to go back into the water.
448d325cf65SWarner Losh
449024daae6SWarner Losh20010211:
450024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
451024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
452024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
453024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
454024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
455024daae6SWarner Losh
456024daae6SWarner Losh	To get to the new system, you'll need to use the following
457024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
458024daae6SWarner Losh	don't have to move this to the updating section.
459024daae6SWarner Losh
460024daae6SWarner Losh	To get around the installworld problem, do:
461024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
462024daae6SWarner Losh		# make install
463024daae6SWarner Losh		# cd /usr/src
464024daae6SWarner Losh		# make installworld
465024daae6SWarner Losh	If that doesn't work, then try:
466024daae6SWarner Losh		# make -k installworld
467024daae6SWarner Losh		# make installworld
468024daae6SWarner Losh
469024daae6SWarner Losh20010207:
470024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
471024daae6SWarner Losh	do not include devfs in your kernel as problems result.
472024daae6SWarner Losh
473024daae6SWarner Losh20010205:
4747595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
475024daae6SWarner Losh	Remove them from your config.
476024daae6SWarner Losh
4771e159248SWarner Losh20010122:
4781e159248SWarner Losh	****************************** WARNING ******************************
4791e159248SWarner Losh			buildkernel has been changed slightly
4801e159248SWarner Losh	****************************** WARNING ******************************
4811e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
4821e159248SWarner Losh	should update your scripts and make.conf accordingly.
4831e159248SWarner Losh
4841e159248SWarner Losh20010119:
4851e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
4861e159248SWarner Losh	This requires a new config to build correctly.
4871e159248SWarner Losh
488aac7dfeaSWarner Losh20010116:
489aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
490aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
491aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
492aac7dfeaSWarner Losh
493aac7dfeaSWarner Losh20010110:
494aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
495aac7dfeaSWarner Losh
496aac7dfeaSWarner Losh20010102:
497aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
498aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
499aac7dfeaSWarner Losh
50063c90c9eSWarner Losh20010101:
50163c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
50263c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
5035fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
50463c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
50563c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
50663c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
50763c90c9eSWarner Losh	might have been ignored by the -k option.
50863c90c9eSWarner Losh
5095fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
5105fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
5115fd2a895SWarner Losh	of this working.
5125fd2a895SWarner Losh
513aac7dfeaSWarner Losh20001228:
514aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
515aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
516aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
517aac7dfeaSWarner Losh
518de2bcc63SWarner Losh20001218:
519de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
520de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
521de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
522de2bcc63SWarner Losh	cards will not be recognized without it.
523de2bcc63SWarner Losh
524960773f7SWarner Losh20001205:
525960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
526960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
527960773f7SWarner Losh	adding the following in pam.conf:
528960773f7SWarner Losh
529960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
530960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
531960773f7SWarner Losh	sshd    session required        pam_permit.so
532960773f7SWarner Losh
5330acc635eSWarner Losh20001031:
5340acc635eSWarner Losh	cvs updated to 1.11.
5350acc635eSWarner Losh
5360acc635eSWarner Losh20001020:
5370acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
5380acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
5390acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
5400acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
5410acc635eSWarner Losh	workaround.
5420acc635eSWarner Losh
5430acc635eSWarner Losh20001010:
5440acc635eSWarner Losh	****************************** WARNING ******************************
5450acc635eSWarner Losh				Sendmail has been updated.
5460acc635eSWarner Losh	****************************** WARNING ******************************
5470acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
5480acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
5490acc635eSWarner Losh	  is set.
5500acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
5510acc635eSWarner Losh	  commands.
5520acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
5530acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
5540acc635eSWarner Losh	  in /usr/share/sendmail/cf.
5550acc635eSWarner Losh	o sendmail.cw changed to local-host-names
5560acc635eSWarner Losh
5570acc635eSWarner Losh	More details can be found at
5580acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
5590acc635eSWarner Losh
5606e98a146SWarner Losh20001009:
5616e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
5626e98a146SWarner Losh	your entire ports tree, or you will have problems.
5636e98a146SWarner Losh
5646e98a146SWarner Losh20001006:
565685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
5666e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
5676e98a146SWarner Losh	/usr/bin/miniperl.
5686e98a146SWarner Losh
569073113a4SWarner Losh20001005:
570073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
571685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
572073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
573073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
574073113a4SWarner Losh	tree for anything to work.
575073113a4SWarner Losh
5760acc635eSWarner Losh20000928:
5770acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
5780acc635eSWarner Losh
579be3885b3SWarner Losh20000916:
580be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
581be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
582be3885b3SWarner Losh	same time as your kernel.
583be3885b3SWarner Losh
58476ec9675SWarner Losh20000914:
58576ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
58676ec9675SWarner Losh	include the device will cause suspended laptops losing time
58776ec9675SWarner Losh	when they resume.  Include
58876ec9675SWarner Losh		device		pmtimer
58976ec9675SWarner Losh	in your config file and
59001b9a434SWarner Losh		hint.pmtimer.0.at="isa"
59176ec9675SWarner Losh	to your /boot/device.hints file.
59276ec9675SWarner Losh
593f4865386SMark Murray20000911:
594f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
595f4865386SMark Murray	rather than an option. The supplied kernel config files have
596f4865386SMark Murray	been updated. You will need to do something similar in your
597f4865386SMark Murray	own kernel config file.
598f4865386SMark Murray	Remove:
599f4865386SMark Murray		options		RANDOMDEV
600f4865386SMark Murray	Add:
601f4865386SMark Murray		device		random
602f4865386SMark Murray	If you prefer to load the loadable module, you need to do
603f4865386SMark Murray	nothing.
604f4865386SMark Murray
605d594498fSWarner Losh20000909:
606d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
607d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
608d594498fSWarner Losh	reflect this if you load this module at boot time.
609d594498fSWarner Losh	The line should read:
610d594498fSWarner Losh		random_load="YES"
611d594498fSWarner Losh
6120deb7ddcSWarner Losh20000907:
6130deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
61416eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
61516eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
61616eb772dSWarner Losh	sure you don't have model loading problems which might at
61716eb772dSWarner Losh	first blush appear related to SMP.
61852bf24e7SWarner Losh
6195a01880bSWarner Losh20000906:
6205a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
6215a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
6225a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
6235a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
6245a01880bSWarner Losh	don't have one, and you have host.conf.
6255a01880bSWarner Losh
6262b41163cSWarner Losh20000905:
62738d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
62838d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
62938d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
63038d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
63138d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
63238d6ecd2SWarner Losh
63338d6ecd2SWarner Losh20000905:
6348aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
6358aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
6368aab4bc7SWarner Losh	is /boot/kernel.
6378aab4bc7SWarner Losh
6388aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
63938d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
64038d6ecd2SWarner Losh	installkernel/installworld dance.
6412b41163cSWarner Losh
642d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
643d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
644d594498fSWarner Losh	modules in that directory instead of finding them in the correct
645d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
646d594498fSWarner Losh	is that the linux module crashes your machine after the update.
647d594498fSWarner Losh
648d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
649d594498fSWarner Losh		mv /modules.old /boot/kernel.old
650d594498fSWarner Losh		chflags noschg /kernel.old
651d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
652d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
653d594498fSWarner Losh	fi
654d594498fSWarner Losh
655c22a309cSWarner Losh20000904:
656c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
657c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
658c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
659c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
660c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
661c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
662c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
663c22a309cSWarner Losh	is not likely to be generated.
664c22a309cSWarner Losh
665fdb9f54dSWarner Losh20000825:
666fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
6679c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
6689c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
6699c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
6709c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
6719c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
6729c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
6739c1a7444SWarner Losh	kernel.
6749c1a7444SWarner Losh
6759c1a7444SWarner Losh20000821:
6769c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
6779c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
6789c1a7444SWarner Losh	/boot/loader.conf.
679fdb9f54dSWarner Losh
6808f250aa7SWarner Losh20000812:
6815da0d091SWarner Losh	suidperl is now always built and installed on the system, but
6825da0d091SWarner Losh	with permissions of 511.  If you have applications that use
6835da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
6845da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
6855da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
6865da0d091SWarner Losh	will fix this until the next build.
6875da0d091SWarner Losh
6885da0d091SWarner Losh20000812:
6898f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
6908f250aa7SWarner Losh	visible changes that may immediately affect your configuration
6918f250aa7SWarner Losh	include:
6928f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
6938f250aa7SWarner Losh	- newaliases limited to root and trusted users
6948f250aa7SWarner Losh	- MSA port (587) turned on by default
6958f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
6968f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
6978f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6988f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6998f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
7008f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
7018f250aa7SWarner Losh
70271c38472SWarner Losh20000810:
70371c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
70471c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
70571c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
70671c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
70771c38472SWarner Losh	specific use for it.
70871c38472SWarner Losh
70971c38472SWarner Losh20000729:
71071c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
71171c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
71271c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
71371c38472SWarner Losh	afterwards (unless the variables already are set, of course):
71471c38472SWarner Losh		# Enable network daemons for user convenience.
71571c38472SWarner Losh		inetd_enable="YES"
71671c38472SWarner Losh		portmap_enable="YES"
71771c38472SWarner Losh		sendmail_enable="YES"
71871c38472SWarner Losh
71971c38472SWarner Losh20000728:
72071c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
72171c38472SWarner Losh	will need to change that to nullfs_load="YES".
72271c38472SWarner Losh
7231dece4a9SWarner Losh20000728:
7241dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
7251dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
7261dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
7271dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
7281dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
7291dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
7301dece4a9SWarner Losh	to /MYKERNEL.
7311dece4a9SWarner Losh
732409e887cSWarner Losh20000711:
733409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
734409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
735409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
736409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
737409e887cSWarner Losh	for details on potential problems that you might have and how
738409e887cSWarner Losh	to get around them.
739409e887cSWarner Losh
740409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
741409e887cSWarner Losh	clauses above, you needn't worry.
742409e887cSWarner Losh
743409e887cSWarner Losh20000711:
744409e887cSWarner Losh	/etc/security has been updated to print the inode number of
745409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
746409e887cSWarner Losh	in the number of changed programs the first time when you run
747409e887cSWarner Losh	mergemaster to get a new /etc/security.
748409e887cSWarner Losh
749673d13f2SWarner Losh20000710:
750673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
751673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
752673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
753673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
754673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
755673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
756673d13f2SWarner Losh	errors. (see below, 20000624).
757673d13f2SWarner Losh
758bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
7591dece4a9SWarner Losh
760673d13f2SWarner Losh20000709:
761c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
762c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
763c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
764673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
765673d13f2SWarner Losh
766e98e26cdSWarner Losh20000706:
767e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
768e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
769e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
770f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
771e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
7722c021c6cSMark Ovens	interim if needed.
773e98e26cdSWarner Losh
774e98e26cdSWarner Losh20000705:
775e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
776e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
777e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
778e98e26cdSWarner Losh	details.
779e98e26cdSWarner Losh
780c373950eSWarner Losh20000704:
7812f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
7822f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
7832f961bc8SWarner Losh
7842f961bc8SWarner Losh20000704:
785c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
786c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
787c373950eSWarner Losh	rc.d scripts that haven't been updated.
788c373950eSWarner Losh
78927dc3a2bSWarner Losh20000630:
79027dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
79127dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
79227dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
79327dc3a2bSWarner Losh
794b8c215acSWarner Losh20000625:
795b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
79627dc3a2bSWarner Losh	system installed in order to build the system and kernel.
79727dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
79827dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
79927dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
80027dc3a2bSWarner Losh	were required.  You should check with the latest collections
80127dc3a2bSWarner Losh	to make sure that these haven't changed.
802b8c215acSWarner Losh
8037b990719SWarner Losh20000624:
8047b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
8057b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
8067b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
8071a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
8087b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
8097b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
8107b990719SWarner Losh	date to the completion of the work.
8117b990719SWarner Losh
81227dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
81327dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
81427dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
81527dc3a2bSWarner Losh	recreate the random and urandom devices.
81627dc3a2bSWarner Losh
81781e54c50SWarner Losh20000622:
81881e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
81981e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
82081e54c50SWarner Losh	that used to be required when updating.
82181e54c50SWarner Losh
82239943833SWarner Losh20000621:
8232c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
8242a2f33fbSDaniel Baker	the config file update procedure.
8252a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
826c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
827a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
82839943833SWarner Losh
829290f9ad8SWarner Losh20000620:
830290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
831290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
832290f9ad8SWarner Losh	that workaround will no longer be required.
833290f9ad8SWarner Losh
83490fb6346SWarner Losh20000615:
83590fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
83690fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
83790fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
83890fb6346SWarner Losh	devices.
83990fb6346SWarner Losh
840f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
841f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
842f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
843f75f65bbSWarner Losh	may work).
844f75f65bbSWarner Losh
845ba26da8eSWarner Losh20000612:
846ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
847290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
848c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
849290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
850f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
851f54a3542SWarner Losh	NEWCARD for examples of the new format.
852290f9ad8SWarner Losh
8539698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
8549698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
8559698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
8569698f2c0SWarner Losh	in it.
857bbcc5149SWarner Losh
858d65850ebSWarner Losh20000522:
859ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
860d65850ebSWarner Losh	building a kernel after this point is advised that they need
861d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
862d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
863d65850ebSWarner Losh
864d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
865d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
866d9583a00SWarner Losh	is recommended that you don't set this option until the problem
867d9583a00SWarner Losh	is resolved.
868d9583a00SWarner Losh
8698039cedeSWarner Losh20000513:
8708039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
8718039cedeSWarner Losh
872d65850ebSWarner Losh20000510:
8738039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
8748039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
8758039cedeSWarner Losh	is requires for the boot blocks to build properly.
8768039cedeSWarner Losh
8778039cedeSWarner Losh20000503:
8788039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
8798039cedeSWarner Losh	is now available.
8808039cedeSWarner Losh
881d65850ebSWarner Losh20000502:
882d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
883d65850ebSWarner Losh	connected to the kernel building instead.
884d65850ebSWarner Losh
885be149406SNik Clayton20000427:
8868039cedeSWarner Losh	You may need to build gperf
8878039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
8888039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
8898039cedeSWarner Losh	an option only in -current.
8908039cedeSWarner Losh
8912b8dd5f4SWarner Losh20000417:
8922b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
893f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
8942b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
8952b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
8962c021c6cSMark Ovens	before you reboot, you'll need to issue:
8972b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
8982b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
8992b8dd5f4SWarner Losh
9008d9f1945SWarner Losh20000320:
9012b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
9022b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
9032b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
904ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
9052b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
9068d9f1945SWarner Losh
907f8ab1dd6SWarner Losh20000319:
908f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
909f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
910f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
911f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
912f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
913f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
914f8ab1dd6SWarner Losh
91519cada77SWarner Losh20000318:
916f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
91719cada77SWarner Losh	Large kernel changes are being committed and are in the
91819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
91919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
92019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
92119cada77SWarner Losh	that you are loading are up to date.
922ba228352SWarner Losh
92319cada77SWarner Losh20000315:
9246d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
9256d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
9266d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
9276d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
9286d23c382SWarner Losh	boot.
9296d23c382SWarner Losh
9306d23c382SWarner Losh20000315:
93119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
93219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
93357199806SWarner Losh
934dc0dbf5cSWarner LoshCOMMON ITEMS:
935dc0dbf5cSWarner Losh
936a24eff53SWarner Losh	General Notes
937a24eff53SWarner Losh	-------------
938a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
939a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
940a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
941a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
942a24eff53SWarner Losh	or several minor releases, or when several months have passed
943a24eff53SWarner Losh	on the -current branch).
944a24eff53SWarner Losh
9455780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
9465780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
9475780f3baSWarner Losh	environment when searching for values for global variables.
9485780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
9495780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
9505780f3baSWarner Losh	page for more details.
9515780f3baSWarner Losh
952dc0dbf5cSWarner Losh	To build a kernel
953dc0dbf5cSWarner Losh	-----------------
954ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
955f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
956ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
9571e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9581e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
959dc0dbf5cSWarner Losh
960ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
961ba01eb20SWarner Losh	--------------------------------------------------------------
962ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
96347d0d01fSWarner Losh	config KERNEL_NAME_HERE
964ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
965ba01eb20SWarner Losh	make depend
966ba01eb20SWarner Losh	make
967ba01eb20SWarner Losh	make install
968ba01eb20SWarner Losh
969ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
970ba01eb20SWarner Losh
971ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
972ba01eb20SWarner Losh	-----------------------------------------------------------
973759f0aefSWarner Losh	make world
974fdb9f54dSWarner Losh	Build a new kernel, see above.
975759f0aefSWarner Losh
9761dece4a9SWarner Losh	To upgrade from 4.x-stable to current
977ba26da8eSWarner Losh	-------------------------------------
978ba26da8eSWarner Losh	make buildworld
9791e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9807595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
981be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
982ee6e1fc3SWarner Losh	reboot in single user [3]
983835284beSWarner Losh	mergemaster -p		[5]
984ba26da8eSWarner Losh	make installworld
985a6cd4f9dSWarner Losh	mergemaster		[4]
986134d2e86SWarner Losh	[1]
987ba26da8eSWarner Losh	<reboot>
988ba26da8eSWarner Losh
989fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
990fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
991fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
992fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
993fdb9f54dSWarner Losh	the UPDATING entries.
994ba26da8eSWarner Losh
9951dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
9961dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
9971dece4a9SWarner Losh	your sources that you have read and understood all the recent
9981dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
9991dece4a9SWarner Losh	much fewer pitfalls.
10001dece4a9SWarner Losh
1001134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
1002134d2e86SWarner Losh	should disable them at this point so they don't crash your
1003134d2e86SWarner Losh	system on reboot.
1004134d2e86SWarner Losh
10059c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
10069c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
10079c1a7444SWarner Losh	configuration.
10089c1a7444SWarner Losh
1009ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
1010ee6e1fc3SWarner Losh		fsck -p
1011ee6e1fc3SWarner Losh		mount -u /
1012ee6e1fc3SWarner Losh		mount -a
1013ee6e1fc3SWarner Losh		cd /usr/src
101447d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
1015f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
1016f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
1017ee6e1fc3SWarner Losh
1018a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1019a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1020a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1021a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1022a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1023a6cd4f9dSWarner Losh	for potential gotchas.
1024a6cd4f9dSWarner Losh
1025835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1026835284beSWarner Losh	you may need to do this if you get unknown user in the following
1027835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1028835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1029835284beSWarner Losh	install) after the buildworld before this step if you last updated
1030835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1031835284beSWarner Losh
1032dc0dbf5cSWarner LoshFORMAT:
1033dc0dbf5cSWarner Losh
1034f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
10351fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1036f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1037f8ab1dd6SWarner Loshprevious releases if your system is older than this.
10381fc1a0dcSWarner Losh
1039e72fd46aSWarner LoshCopyright information:
1040e72fd46aSWarner Losh
10419698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1042e72fd46aSWarner Losh
1043772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1044772730c7SWarner Loshmodification, in full or in part, in any form or format of this
10459698f2c0SWarner Loshdocument are permitted without further permission from the author.
1046e72fd46aSWarner Losh
1047e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1048e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1049e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1050e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1051e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1052e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1053e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1054e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1055e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1056e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1057e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1058e72fd46aSWarner Losh
1059e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1060e72fd46aSWarner Loshauthor a beer.
1061e72fd46aSWarner Losh
106222306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1063772730c7SWarner Loshthis document.
1064772730c7SWarner Losh
106597d92980SPeter Wemm$FreeBSD$
1066