xref: /freebsd/UPDATING (revision 06596d3769b094b7f594d7e1c924733b43acdab2)
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
2506596d37SWarner Losh20020701:
2606596d37SWarner Losh	Now would be a bad time to upgrade.  Something in or near the
2706596d37SWarner Losh	KSE commit totally broke programs using libc_r like KDE and
2806596d37SWarner Losh	GNOME.
2906596d37SWarner Losh
3095ba4330SJacques Vidrine20020511:
3195ba4330SJacques Vidrine	The k5su utility installed as part of Kerberos 5 is no longer
3295ba4330SJacques Vidrine	installed with the set-user-ID bit set by default.  Add
3395ba4330SJacques Vidrine	ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
3495ba4330SJacques Vidrine	with the set-user-ID bit set.
3595ba4330SJacques Vidrine
36a81da3c9SDavid E. O'Brien20020510:
37f50caf6fSDavid E. O'Brien	Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
38f50caf6fSDavid E. O'Brien	Unfortunately our native GDB (at version 4.18) does not understand
394b683fb2SRobert Watson	the DWARF2 debugging format.  Thus you must use `gcc -gstabs+' to
40f50caf6fSDavid E. O'Brien	generated debugging information for our native GDB.
41f50caf6fSDavid E. O'Brien
42f50caf6fSDavid E. O'Brien20020510:
43a81da3c9SDavid E. O'Brien	Due to the way CVS works, it may not properly update src/contrib/gcc
44a81da3c9SDavid E. O'Brien	to the 3.1 sources.  The easiest fix is to `rm -rf' src/contrib/gcc
45a81da3c9SDavid E. O'Brien	and then do a cvs update.
46a81da3c9SDavid E. O'Brien
47528a0ef5SJacques Vidrine20020421:
48528a0ef5SJacques Vidrine	When exec'ing set[ug]id executables, the kernel now ensures that the
49528a0ef5SJacques Vidrine	stdio file descriptors (0..2) are open.  See FreeBSD-SA-02:23.stdio.
50528a0ef5SJacques Vidrine
5185aa5a2eSGregory Neil Shapiro20020404:
5285aa5a2eSGregory Neil Shapiro	New sendmail startup scripts have been installed to make it
5385aa5a2eSGregory Neil Shapiro	easier to use alternative MTAs with FreeBSD.  Setting the rc.conf
5485aa5a2eSGregory Neil Shapiro	variable sendmail_enable to "NO" no longer prevents any sendmail
5585aa5a2eSGregory Neil Shapiro	daemons from starting.  Instead, either set sendmail_enable to
5685aa5a2eSGregory Neil Shapiro	"NONE" or change mta_start_script to a script for starting
5785aa5a2eSGregory Neil Shapiro	an alternative MTA.  Setting mta_start_script to "" will
5885aa5a2eSGregory Neil Shapiro	also prevent any MTA from being started at boot.
5985aa5a2eSGregory Neil Shapiro
608f1e4358SRuslan Ermilov20020403:
618f1e4358SRuslan Ermilov	UCONSOLE is no longer a valid kernel option.
628f1e4358SRuslan Ermilov
632292c02eSWarner Losh20020315:
642292c02eSWarner Losh	FreeBSD 5.0 DP-1 was basically branched today.
652292c02eSWarner Losh
6669f7bcf3SWarner Losh20020225:
6769f7bcf3SWarner Losh	Warnings are now errors in the kernel.  Unless you are a developer,
6869f7bcf3SWarner Losh	you should add -DNO_WERROR to your make line.
6969f7bcf3SWarner Losh
708f35c493SWarner Losh20020217:
718f35c493SWarner Losh	sendmail 8.12.2 has been imported.  The sendmail binary is no
728f35c493SWarner Losh	longer a set-user-ID root binary and the infrastructure to support
738f35c493SWarner Losh	command line mail submission has changed.  Be sure to run
748f35c493SWarner Losh	mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
758f35c493SWarner Losh	and /etc/mail) and read /etc/mail/README for more details.
768f35c493SWarner Losh
77835284beSWarner Losh	Due to the import of sendmail 8.12.2, a new user and group are
78835284beSWarner Losh	required in order for sendmail to run as a set-group-ID
79835284beSWarner Losh	binary.  A 'make installworld' will use the new user and group
80835284beSWarner Losh	to set the owner and group of /var/spool/clientmqueue and will
81835284beSWarner Losh	fail if the new user and group do not exist.  The 'smmsp' user
82835284beSWarner Losh	and group must be merged from src/etc/group and
83835284beSWarner Losh	src/etc/master.passwd before using 'make installworld'.
84835284beSWarner Losh	'mergemaster -p' will do this.  You may need to install
85835284beSWarner Losh	mergemaster before this will work if you are updating from a
86835284beSWarner Losh	very old version of current.  The updating recipe has changed
87835284beSWarner Losh	as of this date.
88835284beSWarner Losh
89fa9401c1SWarner Losh20020112:
90fa9401c1SWarner Losh	The preferred configuration method for PAM is now /etc/pam.d/
91fa9401c1SWarner Losh	rather than /etc/pam.conf.  If you have an unmodified
92fa9401c1SWarner Losh	pam.conf, just delete it after your next mergemaster run.  If
93fa9401c1SWarner Losh	you have local modifications, you can use
94fa9401c1SWarner Losh	/usr/src/etc/pam.d/convert.pl to incorporate them into your
95fa9401c1SWarner Losh	/etc/pam.d.
96fa9401c1SWarner Losh
97fa9401c1SWarner Losh	Please see the following url for more details:
98fa9401c1SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
9947d0d01fSWarner Losh20011229:
10047d0d01fSWarner Losh	If anyone here is already using the new rc.conf(5) variable
10147d0d01fSWarner Losh	networkfs_types, please note that it has changed
10247d0d01fSWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
10347d0d01fSWarner Losh
104514318a8SWarner Losh20011220:
105514318a8SWarner Losh	sys/i4b/driver/i4b_ispppsubr.c has been retired.  This file
106514318a8SWarner Losh	started out its life in the ISDN4BSD project as an offspring
107514318a8SWarner Losh	from sys/net/if_spppsubr.c, which eventually got a life of its
108514318a8SWarner Losh	own.  All the accumulated features and bugfixes of the i4b
109514318a8SWarner Losh	version have now been merged back into the base system's
110514318a8SWarner Losh	version now.  The only user-visible change resulting from this
111514318a8SWarner Losh	is that i4b's sppp(4) interfaces are to be managed with
112514318a8SWarner Losh	spppcontrol(8) again, since ispppcontrol(8) has been retired
113514318a8SWarner Losh	as well.  (There has never been rc file support for
114514318a8SWarner Losh	ispppcontrol in -current, but only in -stable.  That will be
115514318a8SWarner Losh	reverted by the time the changes are MFCed.)
116514318a8SWarner Losh
117514318a8SWarner Losh20011215:
118514318a8SWarner Losh	The fdc(4) driver has been updated and now automatically
119514318a8SWarner Losh	recognizes media in `standard' formats (like 1440 KB and
120514318a8SWarner Losh	720 KB for a 3.5" high-density drive) when accessing the
121514318a8SWarner Losh	default device node (e. g. /dev/fd0).  The old variety of
122514318a8SWarner Losh	floppy device nodes /dev/fd*.* is no longer present by
123514318a8SWarner Losh	default, devices can be created (in DEVFS) on demand.  They
124514318a8SWarner Losh	will need to be customized then for `odd' densities using
125514318a8SWarner Losh	fdcontrol(8).
126514318a8SWarner Losh
1272d22e2bfSWarner Losh20011209:
1282d22e2bfSWarner Losh	The bugs in procfs' debugging support code have been fixed,
1292d22e2bfSWarner Losh	and truss(1) now works again.
1302d22e2bfSWarner Losh
1319e0428e2SWarner Losh20011207:
1329e0428e2SWarner Losh	Daily security checks have been split out to use the periodic(8)
1339e0428e2SWarner Losh	scripts.  Some change in configuration may be necessary.  Please
1349e0428e2SWarner Losh	see
1359e0428e2SWarner Loshhttp://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
1369e0428e2SWarner Losh	for details.
1379e0428e2SWarner Losh
1389bab8c59SWarner Losh20011204:
1399bab8c59SWarner Losh	sos added VCD/SVCD support to ata driver and that needs the
1409bab8c59SWarner Losh	kernel and burncd to be in sync.
1419bab8c59SWarner Losh
142e57d8b01SWarner Losh20011203:
143e57d8b01SWarner Losh	The procfs pseudo-filesystem has now been converted to use the
144e57d8b01SWarner Losh	pseudofs framework.  If you have 'options PROCFS' in your
145e57d8b01SWarner Losh	kernel config, you'll need to add 'options PSEUDOFS' if it's
146e57d8b01SWarner Losh	not there already.
147e57d8b01SWarner Losh
148e57d8b01SWarner Losh	This change temporarily breaks truss(1); use ktrace(1) instead
149e57d8b01SWarner Losh	until the issue has been resolved.
150e57d8b01SWarner Losh
151b001d36fSJacques Vidrine20011202:
152b001d36fSJacques Vidrine	A security hole in OpenSSH involving `UseLogin yes' has been
153b001d36fSJacques Vidrine	patched.
154b001d36fSJacques Vidrine
1554b676ec1SWarner Losh20011126:
1564b676ec1SWarner Losh	You need to remove /usr/obj/.../usr.bin/tip before rebuilding
1575ebbf43eSWarner Losh	after this date.  You need to do this only once.
1584b676ec1SWarner Losh
159d961e462SWarner Losh20011103:
160d961e462SWarner Losh	Most of the awk issues have been resolved.  Some rough
161d961e462SWarner Losh	edges may be left, but for the most part things should be
1624b676ec1SWarner Losh	back to "normal." For CURRENT's usual definition of "normal."
163d961e462SWarner Losh
164d961e462SWarner Losh20011030:
165d961e462SWarner Losh	Awk has been upgraded to the one true awk from bell labs.  Expect
166d961e462SWarner Losh	choppy waves in the upgrade process.
167d961e462SWarner Losh
1681fe003b6SWarner Losh20011030:
169a4b6fda0SWarner Losh	The asr driver problem has been resolved.
1701fe003b6SWarner Losh
1711fe003b6SWarner Losh20011027:
1721fe003b6SWarner Losh	Due to changes in other parts of the system, the asr driver
1731fe003b6SWarner Losh	now causes the system to panic on boot.  Do not use it pending
1741fe003b6SWarner Losh	correction.  Comment it out of any kernel config file that you
1751fe003b6SWarner Losh	try to use from this date forward.
1761fe003b6SWarner Losh
1771fe003b6SWarner Losh20011025:
1781fe003b6SWarner Losh	When crossbuilding, use TARGET=xxx where you used to use
1791fe003b6SWarner Losh	MACHINE=xxx.  You don't need to set TARGET_ARCH and TARGET,
1801fe003b6SWarner Losh	unless you are changing both of them.  To cross build pc98 on
1811fe003b6SWarner Losh	an alpha, for example, you need to set TARGET=pc98 and
1821fe003b6SWarner Losh	TARGET_ARCH=i386.
1831fe003b6SWarner Losh
184d05f9643SWarner Losh20011001:
185d05f9643SWarner Losh	The kernel interface that burncd depends on has changed.
186d05f9643SWarner Losh	You must recompile both the kernel and userland applications
187d05f9643SWarner Losh	at the same time.
188d05f9643SWarner Losh
18958970f85SWarner Losh20010929:
19058970f85SWarner Losh	When crossbuilding, please set TARGET_ARCH rather than
19158970f85SWarner Losh	MACHINE_ARCH to indicate the target.  In the future, one will
19258970f85SWarner Losh	set TARGET_MACHINE where you set MACHINE now.  At the moment,
19358970f85SWarner Losh	setting MACHINE alone for same MACHINE_ARCH machines works
19458970f85SWarner Losh	(eg, you can build pc98 on a i386 machine and vice versa).
19558970f85SWarner Losh
19658970f85SWarner Losh20010927:
19758970f85SWarner Losh	Some weird problems result from using ACPI on some machines.
19858970f85SWarner Losh	To disable ACPI you can add
199378f4486SAlfred Perlstein		hint.acpi.0.disable="1"
20058970f85SWarner Losh	to /boot/loader.conf (or by putting set X=Y at the boot
20158970f85SWarner Losh	loader "ok" prompt).
20258970f85SWarner Losh
20358970f85SWarner Losh	Alternatively, you can remove it from /boot/kernel/acpi.ko
20458970f85SWarner Losh	or use the MODULES_OVERRIDE function in your kernel config
20558970f85SWarner Losh	file and not list acpi in that list.
206378f4486SAlfred Perlstein
2075119d237SWarner Losh20010924:
2085119d237SWarner Losh	The buildworld has been fixed.  You may need to install
2095119d237SWarner Losh	the 4.x compatibility libraries for some old binaries
2108b039fffSWarner Losh	to work.  Add COMPAT4X=true to your /etc/make.conf to
2118b039fffSWarner Losh	get them installed on every installworld, or execute the
2128b039fffSWarner Losh	following to get them installed only once:
2138b039fffSWarner Losh		cd src/lib/compat/compat4x.<arch>
21458970f85SWarner Losh		make all install
2158b039fffSWarner Losh	You will see ``__stdoutp undefined'' until you do this.
2165119d237SWarner Losh
2173c293725SWarner Losh20010919:
2183c293725SWarner Losh	There's a bug in the world build process.  The cross-tools
2193c293725SWarner Losh	are build with the NEW headers, but the OLD libc.a.  This
2203c293725SWarner Losh	leads to all kinds of problems with the new libc.  A temporary
221772730c7SWarner Losh	workaround is to add
2223c293725SWarner Losh		CFLAGS="-O -pipe -D_OLD_STDIO"
2233c293725SWarner Losh	before building world when upgrading from 4.x to current.  This
2243c293725SWarner Losh	can be removed afterwards.
2253c293725SWarner Losh
2263c293725SWarner Losh	A proper fix to the buildworld target is needed.
2273c293725SWarner Losh
2283c293725SWarner Losh20010918:
2293c293725SWarner Losh	Peter has committed his new kthread nfs client/server code.
2303c293725SWarner Losh	NFS may be unstable after this date.
2313c293725SWarner Losh
2323c293725SWarner Losh20010912:
2333c293725SWarner Losh	KSE has hit the tree.  Lots of things are now different in
2343c293725SWarner Losh	the kernel.  While a few problems were introduced in the
2353c293725SWarner Losh	initial commit, most of the major ones have been found and
2363c293725SWarner Losh	corrected.
2373c293725SWarner Losh
2383c293725SWarner Losh20010901:
2393c293725SWarner Losh	In OLDCARD, CardBus bridges appear to be stable.  The work
2403c293725SWarner Losh	arounds described in the 20010604 entry are now no longer
2413c293725SWarner Losh	necessary and will be ignored.  Most insert/remove problems
2423c293725SWarner Losh	have been rectified around this date.
2433c293725SWarner Losh
24498b17b95SWarner Losh20010823:
24598b17b95SWarner Losh 	named now runs as user bind and group bind rather than as
24698b17b95SWarner Losh 	root.  If named_enable is set to YES in /etc/rc.conf, ensure
24798b17b95SWarner Losh 	that user bind is available in /etc/passwd (using vipw(8))
24898b17b95SWarner Losh 	and that group bind is available in /etc/group.  Also make
24998b17b95SWarner Losh 	sure that user or group bind has read (and not write)
25098b17b95SWarner Losh 	permission for your name server configuration and that it
25198b17b95SWarner Losh 	has read and write permission for your slave zone files and
25298b17b95SWarner Losh 	directory.
25398b17b95SWarner Losh
25498b17b95SWarner Losh 	If you wish to continue to run named as root (a less secure
25598b17b95SWarner Losh 	alternative), add a line to /etc/rc.conf saying
25698b17b95SWarner Losh
25798b17b95SWarner Losh 		named_flags=
25898b17b95SWarner Losh
2597b9786edSMark Murray20010709:
2607b9786edSMark Murray	The PAM libraries have had an API upgrade that is beyond
2617b9786edSMark Murray	the ability of the shared library major number to handle.
2627b9786edSMark Murray	It is manifested by PAM-using ports dumping core. The
2637b9786edSMark Murray	solution is to rebuild those ports.
2647b9786edSMark Murray
2651d28950eSWarner Losh20010628:
2661d28950eSWarner Losh	The kernel compile module has moved from src/sys/compile/FOO
2671d28950eSWarner Losh	to src/sys/${MACHINE}/compile/FOO.
2681d28950eSWarner Losh
269e72fd46aSWarner Losh20010625:
27098b17b95SWarner Losh	The pccard modem issue from 20010613 has been corrected.
27198b17b95SWarner Losh	OLDCARD support is still a little weak in -current.  slot 1 is
27298b17b95SWarner Losh	known not to work on some TI based cardbus bridges.  Some
27398b17b95SWarner Losh	cardbus bridges do not properly detect insert/removal events.
27498b17b95SWarner Losh	IRQ configuration needs more safety belts.
27516de1a07SWarner Losh
2760d415dffSWarner Losh20010617:
277e72fd46aSWarner Losh	Softupdates problems have been corrected.
2780d415dffSWarner Losh
2790d415dffSWarner Losh20010614:
2800d415dffSWarner Losh	Peter ripped out the linkerset support.  You must, as always,
2810d415dffSWarner Losh	rerun config after you cvsup if you are using the traditional
2820d415dffSWarner Losh	kernel building methods.
2830d415dffSWarner Losh
2848b9959adSWarner Losh20010613:
2858b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
2868b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
287e72fd46aSWarner Losh	config and /etc/rc.conf ala the 20010604 entry, or you will have
288e72fd46aSWarner Losh	problems (this issue will be fixed, it just hasn't been yet).
2898b9959adSWarner Losh
290e72fd46aSWarner Losh20010613:
2918b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
292e72fd46aSWarner Losh	use them in current.  You can disable softupdates on all mounted
293e72fd46aSWarner Losh	partitions, or remove SOFTUPDATES the kernel config file.
2948b9959adSWarner Losh
2950d415dffSWarner Losh20010612:
2960d415dffSWarner Losh	After Peter's commits to the hints code, people have been noticing
2970d415dffSWarner Losh	that certain devices are attached (or try to) twice.  This is due
2980d415dffSWarner Losh	to having both static hints as well as a /boot/device.hints.  To
2990d415dffSWarner Losh	work around this issue, please use only one or the other mechanism
3000d415dffSWarner Losh	until this bug is fixed.
3010d415dffSWarner Losh
302e72fd46aSWarner Losh	Please note that a feature of config is that if you have config
303e72fd46aSWarner Losh	file FOO and FOO.hints, it automatically adds FOO.hints to the
304e72fd46aSWarner Losh	hints.c file, wheather you want it to or not.
305e72fd46aSWarner Losh
3060d415dffSWarner Losh20010610:
3070d415dffSWarner Losh	Locale names have changed to match other systems better.
3080d415dffSWarner Losh
3096ccdb5e4SWarner Losh20010604:
3106ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
3116ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
3126ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
3133590182eSWarner Losh	Interrupt storms look a lot like a hang.
3143590182eSWarner Losh
3153590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
3163590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
3173590182eSWarner Losh	it is).
3183590182eSWarner Losh
3193590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
3203590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
3213590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
3223590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
3236ccdb5e4SWarner Losh
3240bc62786SWarner Losh20010530:
3250bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
3260bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
3270bc62786SWarner Losh	a limited time.  If you see
3280bc62786SWarner Losh
3290bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
3300bc62786SWarner Losh
3310bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
3320bc62786SWarner Losh	COPY=-C.
3330bc62786SWarner Losh
33468a38c6cSWarner Losh20010525:
335b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
336c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
337c4f4a728SWarner Losh	definitely is in bad shape.
33868a38c6cSWarner Losh
339ed0f29caSWarner Losh20010521:
340f10d3145SWarner Losh	Minor repo damange has happened.  This may cause problems
341ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
342ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
343ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
344ed0f29caSWarner Losh	is
345ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
346ed0f29caSWarner Losh
34780c16af9SWarner Losh20010520:
34868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
34980c16af9SWarner Losh
35080c16af9SWarner Losh20010519:
35180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
35280c16af9SWarner Losh	the past few days.  Everything should still work, but if
35380c16af9SWarner Losh	not, please contact imp@freebsd.org.
35480c16af9SWarner Losh
355a45f2d05SWarner Losh20010517:
356a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
357a45f2d05SWarner Losh	userland at the same time.
358a45f2d05SWarner Losh
359a45f2d05SWarner Losh20010517:
360a45f2d05SWarner Losh	New ncurses imported.
361a45f2d05SWarner Losh
3622988afcaSWarner Losh20010512:
3632988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
3642988afcaSWarner Losh	will be the only way to go starting July 1.
3652988afcaSWarner Losh
3661a33dba7SWarner Losh20010504:
3671a33dba7SWarner Losh	OpenSSH has been updated to 2.9.  Some defaults are different,
3681a33dba7SWarner Losh	including RhostsRSAAuthentication, which changes from yes to no.
3691a33dba7SWarner Losh
37009946a51SWarner Losh20010502:
37109946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
37209946a51SWarner Losh
37309946a51SWarner Losh20010501:
37409946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
37509946a51SWarner Losh
37609946a51SWarner Losh20010430:
377a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
37809946a51SWarner Losh	go back in the water.
37909946a51SWarner Losh
38009946a51SWarner Losh20010429:
38109946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
38209946a51SWarner Losh	this date, but before the correction date.
38309946a51SWarner Losh
38491dd3b53SWarner Losh20010423:
38591dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
38691dd3b53SWarner Losh
38791dd3b53SWarner Losh20010411:
38891dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
38991dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
39091dd3b53SWarner Losh	Update only if you understand that you must not use the old
39191dd3b53SWarner Losh	fsck with the new kernel ever.
39291dd3b53SWarner Losh
393933b3269SWarner Losh20010330:
394933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
395c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
396933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
397933b3269SWarner Losh
398933b3269SWarner Losh20010319:
399933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
400933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
401933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
402f34a9421SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
40309946a51SWarner Losh
40409946a51SWarner Losh20010315:
40509946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
40609946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
40709946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
408933b3269SWarner Losh
409933b3269SWarner Losh20010312:
410933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
411933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
412933b3269SWarner Losh
413933b3269SWarner Losh20010312:
414933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
415933b3269SWarner Losh	instead of ad-hoc.
416933b3269SWarner Losh
417933b3269SWarner Losh20010310:
418f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
419933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
420933b3269SWarner Losh	ssh might not work if you don't.
421933b3269SWarner Losh
42262353691SWarner Losh20010303:
42362353691SWarner Losh	The ed driver has been updated.  It now allows mii attachments,
42462353691SWarner Losh	which means that you must include the miibus in your kernel if
42562353691SWarner Losh	you use the ed driver.
42662353691SWarner Losh
427d325cf65SWarner Losh20010220:
428d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
429d325cf65SWarner Losh	safe to go back into the water.
430d325cf65SWarner Losh
431024daae6SWarner Losh20010211:
432024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
433024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
434024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
435024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
436024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
437024daae6SWarner Losh
438024daae6SWarner Losh	To get to the new system, you'll need to use the following
439024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
440024daae6SWarner Losh	don't have to move this to the updating section.
441024daae6SWarner Losh
442024daae6SWarner Losh	To get around the installworld problem, do:
443024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
444024daae6SWarner Losh		# make install
445024daae6SWarner Losh		# cd /usr/src
446024daae6SWarner Losh		# make installworld
447024daae6SWarner Losh	If that doesn't work, then try:
448024daae6SWarner Losh		# make -k installworld
449024daae6SWarner Losh		# make installworld
450024daae6SWarner Losh
451024daae6SWarner Losh20010207:
452024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
453024daae6SWarner Losh	do not include devfs in your kernel as problems result.
454024daae6SWarner Losh
455024daae6SWarner Losh20010205:
4567595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
457024daae6SWarner Losh	Remove them from your config.
458024daae6SWarner Losh
4591e159248SWarner Losh20010122:
4601e159248SWarner Losh	****************************** WARNING ******************************
4611e159248SWarner Losh			buildkernel has been changed slightly
4621e159248SWarner Losh	****************************** WARNING ******************************
4631e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
4641e159248SWarner Losh	should update your scripts and make.conf accordingly.
4651e159248SWarner Losh
4661e159248SWarner Losh20010119:
4671e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
4681e159248SWarner Losh	This requires a new config to build correctly.
4691e159248SWarner Losh
470aac7dfeaSWarner Losh20010116:
471aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
472aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
473aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
474aac7dfeaSWarner Losh
475aac7dfeaSWarner Losh20010110:
476aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
477aac7dfeaSWarner Losh
478aac7dfeaSWarner Losh20010102:
479aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
480aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
481aac7dfeaSWarner Losh
48263c90c9eSWarner Losh20010101:
48363c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
48463c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
4855fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
48663c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
48763c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
48863c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
48963c90c9eSWarner Losh	might have been ignored by the -k option.
49063c90c9eSWarner Losh
4915fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
4925fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
4935fd2a895SWarner Losh	of this working.
4945fd2a895SWarner Losh
495aac7dfeaSWarner Losh20001228:
496aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
497aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
498aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
499aac7dfeaSWarner Losh
500de2bcc63SWarner Losh20001218:
501de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
502de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
503de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
504de2bcc63SWarner Losh	cards will not be recognized without it.
505de2bcc63SWarner Losh
506960773f7SWarner Losh20001205:
507960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
508960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
509960773f7SWarner Losh	adding the following in pam.conf:
510960773f7SWarner Losh
511960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
512960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
513960773f7SWarner Losh	sshd    session required        pam_permit.so
514960773f7SWarner Losh
5150acc635eSWarner Losh20001031:
5160acc635eSWarner Losh	cvs updated to 1.11.
5170acc635eSWarner Losh
5180acc635eSWarner Losh20001020:
5190acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
5200acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
5210acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
5220acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
5230acc635eSWarner Losh	workaround.
5240acc635eSWarner Losh
5250acc635eSWarner Losh20001010:
5260acc635eSWarner Losh	****************************** WARNING ******************************
5270acc635eSWarner Losh				Sendmail has been updated.
5280acc635eSWarner Losh	****************************** WARNING ******************************
5290acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
5300acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
5310acc635eSWarner Losh	  is set.
5320acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
5330acc635eSWarner Losh	  commands.
5340acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
5350acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
5360acc635eSWarner Losh	  in /usr/share/sendmail/cf.
5370acc635eSWarner Losh	o sendmail.cw changed to local-host-names
5380acc635eSWarner Losh
5390acc635eSWarner Losh	More details can be found at
5400acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
5410acc635eSWarner Losh
5426e98a146SWarner Losh20001009:
5436e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
5446e98a146SWarner Losh	your entire ports tree, or you will have problems.
5456e98a146SWarner Losh
5466e98a146SWarner Losh20001006:
547685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
5486e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
5496e98a146SWarner Losh	/usr/bin/miniperl.
5506e98a146SWarner Losh
551073113a4SWarner Losh20001005:
552073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
553685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
554073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
555073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
556073113a4SWarner Losh	tree for anything to work.
557073113a4SWarner Losh
5580acc635eSWarner Losh20000928:
5590acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
5600acc635eSWarner Losh
561be3885b3SWarner Losh20000916:
562be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
563be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
564be3885b3SWarner Losh	same time as your kernel.
565be3885b3SWarner Losh
56676ec9675SWarner Losh20000914:
56776ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
56876ec9675SWarner Losh	include the device will cause suspended laptops losing time
56976ec9675SWarner Losh	when they resume.  Include
57076ec9675SWarner Losh		device		pmtimer
57176ec9675SWarner Losh	in your config file and
57201b9a434SWarner Losh		hint.pmtimer.0.at="isa"
57376ec9675SWarner Losh	to your /boot/device.hints file.
57476ec9675SWarner Losh
575f4865386SMark Murray20000911:
576f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
577f4865386SMark Murray	rather than an option. The supplied kernel config files have
578f4865386SMark Murray	been updated. You will need to do something similar in your
579f4865386SMark Murray	own kernel config file.
580f4865386SMark Murray	Remove:
581f4865386SMark Murray		options		RANDOMDEV
582f4865386SMark Murray	Add:
583f4865386SMark Murray		device		random
584f4865386SMark Murray	If you prefer to load the loadable module, you need to do
585f4865386SMark Murray	nothing.
586f4865386SMark Murray
587d594498fSWarner Losh20000909:
588d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
589d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
590d594498fSWarner Losh	reflect this if you load this module at boot time.
591d594498fSWarner Losh	The line should read:
592d594498fSWarner Losh		random_load="YES"
593d594498fSWarner Losh
5940deb7ddcSWarner Losh20000907:
5950deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
59616eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
59716eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
59816eb772dSWarner Losh	sure you don't have model loading problems which might at
59916eb772dSWarner Losh	first blush appear related to SMP.
60052bf24e7SWarner Losh
6015a01880bSWarner Losh20000906:
6025a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
6035a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
6045a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
6055a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
6065a01880bSWarner Losh	don't have one, and you have host.conf.
6075a01880bSWarner Losh
6082b41163cSWarner Losh20000905:
60938d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
61038d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
61138d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
61238d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
61338d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
61438d6ecd2SWarner Losh
61538d6ecd2SWarner Losh20000905:
6168aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
6178aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
6188aab4bc7SWarner Losh	is /boot/kernel.
6198aab4bc7SWarner Losh
6208aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
62138d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
62238d6ecd2SWarner Losh	installkernel/installworld dance.
6232b41163cSWarner Losh
624d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
625d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
626d594498fSWarner Losh	modules in that directory instead of finding them in the correct
627d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
628d594498fSWarner Losh	is that the linux module crashes your machine after the update.
629d594498fSWarner Losh
630d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
631d594498fSWarner Losh		mv /modules.old /boot/kernel.old
632d594498fSWarner Losh		chflags noschg /kernel.old
633d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
634d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
635d594498fSWarner Losh	fi
636d594498fSWarner Losh
637c22a309cSWarner Losh20000904:
638c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
639c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
640c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
641c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
642c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
643c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
644c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
645c22a309cSWarner Losh	is not likely to be generated.
646c22a309cSWarner Losh
647fdb9f54dSWarner Losh20000825:
648fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
6499c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
6509c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
6519c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
6529c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
6539c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
6549c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
6559c1a7444SWarner Losh	kernel.
6569c1a7444SWarner Losh
6579c1a7444SWarner Losh20000821:
6589c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
6599c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
6609c1a7444SWarner Losh	/boot/loader.conf.
661fdb9f54dSWarner Losh
6628f250aa7SWarner Losh20000812:
6635da0d091SWarner Losh	suidperl is now always built and installed on the system, but
6645da0d091SWarner Losh	with permissions of 511.  If you have applications that use
6655da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
6665da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
6675da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
6685da0d091SWarner Losh	will fix this until the next build.
6695da0d091SWarner Losh
6705da0d091SWarner Losh20000812:
6718f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
6728f250aa7SWarner Losh	visible changes that may immediately affect your configuration
6738f250aa7SWarner Losh	include:
6748f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
6758f250aa7SWarner Losh	- newaliases limited to root and trusted users
6768f250aa7SWarner Losh	- MSA port (587) turned on by default
6778f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
6788f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
6798f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
6808f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
6818f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
6828f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
6838f250aa7SWarner Losh
68471c38472SWarner Losh20000810:
68571c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
68671c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
68771c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
68871c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
68971c38472SWarner Losh	specific use for it.
69071c38472SWarner Losh
69171c38472SWarner Losh20000729:
69271c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
69371c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
69471c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
69571c38472SWarner Losh	afterwards (unless the variables already are set, of course):
69671c38472SWarner Losh		# Enable network daemons for user convenience.
69771c38472SWarner Losh		inetd_enable="YES"
69871c38472SWarner Losh		portmap_enable="YES"
69971c38472SWarner Losh		sendmail_enable="YES"
70071c38472SWarner Losh
70171c38472SWarner Losh20000728:
70271c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
70371c38472SWarner Losh	will need to change that to nullfs_load="YES".
70471c38472SWarner Losh
7051dece4a9SWarner Losh20000728:
7061dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
7071dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
7081dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
7091dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
7101dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
7111dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
7121dece4a9SWarner Losh	to /MYKERNEL.
7131dece4a9SWarner Losh
714409e887cSWarner Losh20000711:
715409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
716409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
717409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
718409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
719409e887cSWarner Losh	for details on potential problems that you might have and how
720409e887cSWarner Losh	to get around them.
721409e887cSWarner Losh
722409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
723409e887cSWarner Losh	clauses above, you needn't worry.
724409e887cSWarner Losh
725409e887cSWarner Losh20000711:
726409e887cSWarner Losh	/etc/security has been updated to print the inode number of
727409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
728409e887cSWarner Losh	in the number of changed programs the first time when you run
729409e887cSWarner Losh	mergemaster to get a new /etc/security.
730409e887cSWarner Losh
731673d13f2SWarner Losh20000710:
732673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
733673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
734673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
735673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
736673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
737673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
738673d13f2SWarner Losh	errors. (see below, 20000624).
739673d13f2SWarner Losh
740bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
7411dece4a9SWarner Losh
742673d13f2SWarner Losh20000709:
743c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
744c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
745c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
746673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
747673d13f2SWarner Losh
748e98e26cdSWarner Losh20000706:
749e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
750e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
751e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
752f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
753e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
7542c021c6cSMark Ovens	interim if needed.
755e98e26cdSWarner Losh
756e98e26cdSWarner Losh20000705:
757e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
758e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
759e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
760e98e26cdSWarner Losh	details.
761e98e26cdSWarner Losh
762c373950eSWarner Losh20000704:
7632f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
7642f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
7652f961bc8SWarner Losh
7662f961bc8SWarner Losh20000704:
767c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
768c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
769c373950eSWarner Losh	rc.d scripts that haven't been updated.
770c373950eSWarner Losh
77127dc3a2bSWarner Losh20000630:
77227dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
77327dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
77427dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
77527dc3a2bSWarner Losh
776b8c215acSWarner Losh20000625:
777b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
77827dc3a2bSWarner Losh	system installed in order to build the system and kernel.
77927dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
78027dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
78127dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
78227dc3a2bSWarner Losh	were required.  You should check with the latest collections
78327dc3a2bSWarner Losh	to make sure that these haven't changed.
784b8c215acSWarner Losh
7857b990719SWarner Losh20000624:
7867b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
7877b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
7887b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
7891a33dba7SWarner Losh	-CURRENT FROM THIS POINT to 2000710 for cryptographic services
7907b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
7917b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
7927b990719SWarner Losh	date to the completion of the work.
7937b990719SWarner Losh
79427dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
79527dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
79627dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
79727dc3a2bSWarner Losh	recreate the random and urandom devices.
79827dc3a2bSWarner Losh
79981e54c50SWarner Losh20000622:
80081e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
80181e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
80281e54c50SWarner Losh	that used to be required when updating.
80381e54c50SWarner Losh
80439943833SWarner Losh20000621:
8052c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
8062a2f33fbSDaniel Baker	the config file update procedure.
8072a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
808c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
809a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
81039943833SWarner Losh
811290f9ad8SWarner Losh20000620:
812290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
813290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
814290f9ad8SWarner Losh	that workaround will no longer be required.
815290f9ad8SWarner Losh
81690fb6346SWarner Losh20000615:
81790fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
81890fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
81990fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
82090fb6346SWarner Losh	devices.
82190fb6346SWarner Losh
822f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
823f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
824f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
825f75f65bbSWarner Losh	may work).
826f75f65bbSWarner Losh
827ba26da8eSWarner Losh20000612:
828ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
829290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
830c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
831290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
832f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
833f54a3542SWarner Losh	NEWCARD for examples of the new format.
834290f9ad8SWarner Losh
8359698f2c0SWarner Losh	Indirectly, this also breaks USERCONFIG.  Unless a newer entry
8369698f2c0SWarner Losh	says that it has been fixed, assume that must use the hints mechanism
8379698f2c0SWarner Losh	in the loader if you need to use a machine with very old ISA cards
8389698f2c0SWarner Losh	in it.
839bbcc5149SWarner Losh
840d65850ebSWarner Losh20000522:
841ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
842d65850ebSWarner Losh	building a kernel after this point is advised that they need
843d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
844d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
845d65850ebSWarner Losh
846d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
847d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
848d9583a00SWarner Losh	is recommended that you don't set this option until the problem
849d9583a00SWarner Losh	is resolved.
850d9583a00SWarner Losh
8518039cedeSWarner Losh20000513:
8528039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
8538039cedeSWarner Losh
854d65850ebSWarner Losh20000510:
8558039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
8568039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
8578039cedeSWarner Losh	is requires for the boot blocks to build properly.
8588039cedeSWarner Losh
8598039cedeSWarner Losh20000503:
8608039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
8618039cedeSWarner Losh	is now available.
8628039cedeSWarner Losh
863d65850ebSWarner Losh20000502:
864d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
865d65850ebSWarner Losh	connected to the kernel building instead.
866d65850ebSWarner Losh
867be149406SNik Clayton20000427:
8688039cedeSWarner Losh	You may need to build gperf
8698039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
8708039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
8718039cedeSWarner Losh	an option only in -current.
8728039cedeSWarner Losh
8732b8dd5f4SWarner Losh20000417:
8742b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
875f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
8762b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
8772b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
8782c021c6cSMark Ovens	before you reboot, you'll need to issue:
8792b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
8802b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
8812b8dd5f4SWarner Losh
8828d9f1945SWarner Losh20000320:
8832b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
8842b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
8852b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
886ae20a1b8SDima Dorfman		/sbin/sysctl hw.ata.ata_dma=0
8872b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
8888d9f1945SWarner Losh
889f8ab1dd6SWarner Losh20000319:
890f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
891f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
892f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
893f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
894f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
895f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
896f8ab1dd6SWarner Losh
89719cada77SWarner Losh20000318:
898f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
89919cada77SWarner Losh	Large kernel changes are being committed and are in the
90019cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
90119cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
90219cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
90319cada77SWarner Losh	that you are loading are up to date.
904ba228352SWarner Losh
90519cada77SWarner Losh20000315:
9066d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
9076d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
9086d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
9096d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
9106d23c382SWarner Losh	boot.
9116d23c382SWarner Losh
9126d23c382SWarner Losh20000315:
91319cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
91419cada77SWarner Losh	to upgrade to 4.0 from 3.x.
91557199806SWarner Losh
916dc0dbf5cSWarner LoshCOMMON ITEMS:
917dc0dbf5cSWarner Losh
918a24eff53SWarner Losh	General Notes
919a24eff53SWarner Losh	-------------
920a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
921a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
922a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
923a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
924a24eff53SWarner Losh	or several minor releases, or when several months have passed
925a24eff53SWarner Losh	on the -current branch).
926a24eff53SWarner Losh
9275780f3baSWarner Losh	Sometimes, obscure build problems are the result of environment
9285780f3baSWarner Losh	poisoning.  This can happen because the make utility reads its
9295780f3baSWarner Losh	environment when searching for values for global variables.
9305780f3baSWarner Losh	To run your build attempts in an "environmental clean room",
9315780f3baSWarner Losh	prefix all make commands with 'env -i '.  See the env(1) manual
9325780f3baSWarner Losh	page for more details.
9335780f3baSWarner Losh
934dc0dbf5cSWarner Losh	To build a kernel
935dc0dbf5cSWarner Losh	-----------------
936ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
937f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
938ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
9391e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9401e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
941dc0dbf5cSWarner Losh
942ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
943ba01eb20SWarner Losh	--------------------------------------------------------------
944ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
94547d0d01fSWarner Losh	config KERNEL_NAME_HERE
946ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
947ba01eb20SWarner Losh	make depend
948ba01eb20SWarner Losh	make
949ba01eb20SWarner Losh	make install
950ba01eb20SWarner Losh
951ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
952ba01eb20SWarner Losh
953ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
954ba01eb20SWarner Losh	-----------------------------------------------------------
955759f0aefSWarner Losh	make world
956fdb9f54dSWarner Losh	Build a new kernel, see above.
957759f0aefSWarner Losh
9581dece4a9SWarner Losh	To upgrade from 4.x-stable to current
959ba26da8eSWarner Losh	-------------------------------------
960ba26da8eSWarner Losh	make buildworld
9611e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
9627595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
963be1d673dSRuslan Ermilov	make installkernel KERNCONF=YOUR_KERNEL_HERE
964ee6e1fc3SWarner Losh	reboot in single user [3]
965835284beSWarner Losh	mergemaster -p		[5]
966ba26da8eSWarner Losh	make installworld
967a6cd4f9dSWarner Losh	mergemaster		[4]
968134d2e86SWarner Losh	[1]
969ba26da8eSWarner Losh	<reboot>
970ba26da8eSWarner Losh
971fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
972fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
973fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
974fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
975fdb9f54dSWarner Losh	the UPDATING entries.
976ba26da8eSWarner Losh
9771dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
9781dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
9791dece4a9SWarner Losh	your sources that you have read and understood all the recent
9801dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
9811dece4a9SWarner Losh	much fewer pitfalls.
9821dece4a9SWarner Losh
983134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
984134d2e86SWarner Losh	should disable them at this point so they don't crash your
985134d2e86SWarner Losh	system on reboot.
986134d2e86SWarner Losh
9879c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
9889c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
9899c1a7444SWarner Losh	configuration.
9909c1a7444SWarner Losh
991ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
992ee6e1fc3SWarner Losh		fsck -p
993ee6e1fc3SWarner Losh		mount -u /
994ee6e1fc3SWarner Losh		mount -a
995ee6e1fc3SWarner Losh		cd /usr/src
99647d0d01fSWarner Losh		adjkerntz -i		# if CMOS is wall time
997f6a0ef01SWarner Losh	Also, when doing a major release upgrade, it is required that
998f6a0ef01SWarner Losh	you boot into single user mode to do the installworld.
999ee6e1fc3SWarner Losh
1000a6cd4f9dSWarner Losh	[4] Note: This step is non-optional.  Failure to do this step
1001a6cd4f9dSWarner Losh	can result in a significant reduction in the functionality of the
1002a6cd4f9dSWarner Losh	system.  Attempting to do it by hand is not recommended and those
1003a6cd4f9dSWarner Losh	that pursue this avenue should read this file carefully, as well
1004a6cd4f9dSWarner Losh	as the archives of freebsd-current and freebsd-hackers mailing lists
1005a6cd4f9dSWarner Losh	for potential gotchas.
1006a6cd4f9dSWarner Losh
1007835284beSWarner Losh	[5] Usually this step is a noop.  However, from time to time
1008835284beSWarner Losh	you may need to do this if you get unknown user in the following
1009835284beSWarner Losh	step.  It never hurts to do it all the time.  You may need to
1010835284beSWarner Losh	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1011835284beSWarner Losh	install) after the buildworld before this step if you last updated
1012835284beSWarner Losh	from current before 20020224 or from -stable before 20020408.
1013835284beSWarner Losh
1014dc0dbf5cSWarner LoshFORMAT:
1015dc0dbf5cSWarner Losh
1016f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
10171fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
1018f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
1019f8ab1dd6SWarner Loshprevious releases if your system is older than this.
10201fc1a0dcSWarner Losh
1021e72fd46aSWarner LoshCopyright information:
1022e72fd46aSWarner Losh
10239698f2c0SWarner LoshCopyright 1998, 2002 M. Warner Losh.  All Rights Reserved.
1024e72fd46aSWarner Losh
1025772730c7SWarner LoshRedistribution, publication, translation and use, with or without
1026772730c7SWarner Loshmodification, in full or in part, in any form or format of this
10279698f2c0SWarner Loshdocument are permitted without further permission from the author.
1028e72fd46aSWarner Losh
1029e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1030e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1031e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1032e72fd46aSWarner LoshDISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1033e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1034e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1035e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1036e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1037e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1038e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1039e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE.
1040e72fd46aSWarner Losh
1041e72fd46aSWarner LoshIf you find this document useful, and you want to, you may buy the
1042e72fd46aSWarner Loshauthor a beer.
1043e72fd46aSWarner Losh
104422306abcSWarner LoshContact Warner Losh if you have any questions about your use of
1045772730c7SWarner Loshthis document.
1046772730c7SWarner Losh
104797d92980SPeter Wemm$FreeBSD$
1048