xref: /freebsd/UPDATING (revision a45f2d05ec583f1599467456f0d3a34057457838)
157199806SWarner LoshUpdating Information for FreeBSD current users
253dfde79SWarner Losh
3f8c77507SWarner LoshThis file is maintained by imp@village.org.  Please send new entries
4dc0dbf5cSWarner Loshdirectly to him.  See end of file for further details.  For commonly
516de1a07SWarner Loshdone items, please see the end of the file.  Search for 'COMMON
616de1a07SWarner LoshITEMS:'
716de1a07SWarner Losh
8*a45f2d05SWarner Losh20010517:
9*a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
10*a45f2d05SWarner Losh	userland at the same time.
11*a45f2d05SWarner Losh
12*a45f2d05SWarner Losh20010517:
13*a45f2d05SWarner Losh	New ncurses imported.
14*a45f2d05SWarner Losh
152988afcaSWarner Losh20010512:
162988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
172988afcaSWarner Losh	will be the only way to go starting July 1.
182988afcaSWarner Losh
1909946a51SWarner Losh20010502:
2009946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
2109946a51SWarner Losh
2209946a51SWarner Losh20010501:
2309946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
2409946a51SWarner Losh
2509946a51SWarner Losh20010430:
26a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
2709946a51SWarner Losh	go back in the water.
2809946a51SWarner Losh
2909946a51SWarner Losh20010429:
3009946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
3109946a51SWarner Losh	this date, but before the correction date.
3209946a51SWarner Losh
3391dd3b53SWarner Losh20010423:
3491dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
3591dd3b53SWarner Losh
3691dd3b53SWarner Losh20010411:
3791dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
3891dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
3991dd3b53SWarner Losh	Update only if you understand that you must not use the old
4091dd3b53SWarner Losh	fsck with the new kernel ever.
4191dd3b53SWarner Losh
42933b3269SWarner Losh20010330:
43933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
44933b3269SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page fora
45933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
46933b3269SWarner Losh
47933b3269SWarner Losh20010319:
48933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
49933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
50933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
5109946a51SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
5209946a51SWarner Losh
5309946a51SWarner Losh20010315:
5409946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
5509946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
5609946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
57933b3269SWarner Losh
58933b3269SWarner Losh20010312:
59933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
60933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
61933b3269SWarner Losh
62933b3269SWarner Losh20010312:
63933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
64933b3269SWarner Losh	instead of ad-hoc.
65933b3269SWarner Losh
66933b3269SWarner Losh20010310:
67933b3269SWarner Losh	/dev/urandmon should be a sumbolic link to /dev/random now.
68933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
69933b3269SWarner Losh	ssh might not work if you don't.
70933b3269SWarner Losh
71d325cf65SWarner Losh20010220:
72d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
73d325cf65SWarner Losh	safe to go back into the water.
74d325cf65SWarner Losh
75024daae6SWarner Losh20010211:
76024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
77024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
78024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
79024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
80024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
81024daae6SWarner Losh
82024daae6SWarner Losh	To get to the new system, you'll need to use the following
83024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
84024daae6SWarner Losh	don't have to move this to the updating section.
85024daae6SWarner Losh
86024daae6SWarner Losh	To get around the installworld problem, do:
87024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
88024daae6SWarner Losh		# make install
89024daae6SWarner Losh		# cd /usr/src
90024daae6SWarner Losh		# make installworld
91024daae6SWarner Losh	If that doesn't work, then try:
92024daae6SWarner Losh		# make -k installworld
93024daae6SWarner Losh		# make installworld
94024daae6SWarner Losh
95024daae6SWarner Losh20010207:
96024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
97024daae6SWarner Losh	do not include devfs in your kernel as problems result.
98024daae6SWarner Losh
99024daae6SWarner Losh20010205:
1007595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
101024daae6SWarner Losh	Remove them from your config.
102024daae6SWarner Losh
1031e159248SWarner Losh20010122:
1041e159248SWarner Losh	****************************** WARNING ******************************
1051e159248SWarner Losh			buildkernel has been changed slightly
1061e159248SWarner Losh	****************************** WARNING ******************************
1071e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
1081e159248SWarner Losh	should update your scripts and make.conf accordingly.
1091e159248SWarner Losh
1101e159248SWarner Losh20010119:
1111e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
1121e159248SWarner Losh	This requires a new config to build correctly.
1131e159248SWarner Losh
114aac7dfeaSWarner Losh20010116:
115aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
116aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
117aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
118aac7dfeaSWarner Losh
119aac7dfeaSWarner Losh20010110:
120aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
121aac7dfeaSWarner Losh
122aac7dfeaSWarner Losh20010102:
123aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
124aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
125aac7dfeaSWarner Losh
12663c90c9eSWarner Losh20010101:
12763c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
12863c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
1295fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
13063c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
13163c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
13263c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
13363c90c9eSWarner Losh	might have been ignored by the -k option.
13463c90c9eSWarner Losh
1355fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
1365fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
1375fd2a895SWarner Losh	of this working.
1385fd2a895SWarner Losh
139aac7dfeaSWarner Losh20001228:
140aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
141aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
142aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
143aac7dfeaSWarner Losh
144de2bcc63SWarner Losh20001218:
145de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
146de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
147de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
148de2bcc63SWarner Losh	cards will not be recognized without it.
149de2bcc63SWarner Losh
150960773f7SWarner Losh20001205:
151960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
152960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
153960773f7SWarner Losh	adding the following in pam.conf:
154960773f7SWarner Losh
155960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
156960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
157960773f7SWarner Losh	sshd    session required        pam_permit.so
158960773f7SWarner Losh
1590acc635eSWarner Losh20001031:
1600acc635eSWarner Losh	cvs updated to 1.11.
1610acc635eSWarner Losh
1620acc635eSWarner Losh20001020:
1630acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
1640acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
1650acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
1660acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
1670acc635eSWarner Losh	workaround.
1680acc635eSWarner Losh
1690acc635eSWarner Losh20001010:
1700acc635eSWarner Losh	****************************** WARNING ******************************
1710acc635eSWarner Losh				Sendmail has been updated.
1720acc635eSWarner Losh	****************************** WARNING ******************************
1730acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
1740acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1750acc635eSWarner Losh	  is set.
1760acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1770acc635eSWarner Losh	  commands.
1780acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
1790acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
1800acc635eSWarner Losh	  in /usr/share/sendmail/cf.
1810acc635eSWarner Losh	o sendmail.cw changed to local-host-names
1820acc635eSWarner Losh
1830acc635eSWarner Losh	More details can be found at
1840acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1850acc635eSWarner Losh
1866e98a146SWarner Losh20001009:
1876e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
1886e98a146SWarner Losh	your entire ports tree, or you will have problems.
1896e98a146SWarner Losh
1906e98a146SWarner Losh20001006:
191685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
1926e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
1936e98a146SWarner Losh	/usr/bin/miniperl.
1946e98a146SWarner Losh
195073113a4SWarner Losh20001005:
196073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
197685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
198073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
199073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
200073113a4SWarner Losh	tree for anything to work.
201073113a4SWarner Losh
2020acc635eSWarner Losh20000928:
2030acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
2040acc635eSWarner Losh
205be3885b3SWarner Losh20000916:
206be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
207be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
208be3885b3SWarner Losh	same time as your kernel.
209be3885b3SWarner Losh
21076ec9675SWarner Losh20000914:
21176ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
21276ec9675SWarner Losh	include the device will cause suspended laptops losing time
21376ec9675SWarner Losh	when they resume.  Include
21476ec9675SWarner Losh		device		pmtimer
21576ec9675SWarner Losh	in your config file and
21601b9a434SWarner Losh		hint.pmtimer.0.at="isa"
21776ec9675SWarner Losh	to your /boot/device.hints file.
21876ec9675SWarner Losh
219f4865386SMark Murray20000911:
220f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
221f4865386SMark Murray	rather than an option. The supplied kernel config files have
222f4865386SMark Murray	been updated. You will need to do something similar in your
223f4865386SMark Murray	own kernel config file.
224f4865386SMark Murray	Remove:
225f4865386SMark Murray		options		RANDOMDEV
226f4865386SMark Murray	Add:
227f4865386SMark Murray		device		random
228f4865386SMark Murray	If you prefer to load the loadable module, you need to do
229f4865386SMark Murray	nothing.
230f4865386SMark Murray
231d594498fSWarner Losh20000909:
232d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
233d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
234d594498fSWarner Losh	reflect this if you load this module at boot time.
235d594498fSWarner Losh	The line should read:
236d594498fSWarner Losh		random_load="YES"
237d594498fSWarner Losh
2380deb7ddcSWarner Losh20000907:
2390deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
24016eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
24116eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
24216eb772dSWarner Losh	sure you don't have model loading problems which might at
24316eb772dSWarner Losh	first blush appear related to SMP.
24452bf24e7SWarner Losh
2455a01880bSWarner Losh20000906:
2465a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
2475a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
2485a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
2495a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
2505a01880bSWarner Losh	don't have one, and you have host.conf.
2515a01880bSWarner Losh
2522b41163cSWarner Losh20000905:
25338d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
25438d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
25538d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
25638d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
25738d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
25838d6ecd2SWarner Losh
25938d6ecd2SWarner Losh20000905:
2608aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
2618aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
2628aab4bc7SWarner Losh	is /boot/kernel.
2638aab4bc7SWarner Losh
2648aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
26538d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
26638d6ecd2SWarner Losh	installkernel/installworld dance.
2672b41163cSWarner Losh
268d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
269d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
270d594498fSWarner Losh	modules in that directory instead of finding them in the correct
271d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
272d594498fSWarner Losh	is that the linux module crashes your machine after the update.
273d594498fSWarner Losh
274d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
275d594498fSWarner Losh		mv /modules.old /boot/kernel.old
276d594498fSWarner Losh		chflags noschg /kernel.old
277d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
278d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
279d594498fSWarner Losh	fi
280d594498fSWarner Losh
281c22a309cSWarner Losh20000904:
282c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
283c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
284c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
285c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
286c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
287c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
288c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
289c22a309cSWarner Losh	is not likely to be generated.
290c22a309cSWarner Losh
291fdb9f54dSWarner Losh20000825:
292fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
2939c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
2949c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
2959c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
2969c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
2979c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
2989c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
2999c1a7444SWarner Losh	kernel.
3009c1a7444SWarner Losh
3019c1a7444SWarner Losh20000821:
3029c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
3039c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
3049c1a7444SWarner Losh	/boot/loader.conf.
305fdb9f54dSWarner Losh
3068f250aa7SWarner Losh20000812:
3075da0d091SWarner Losh	suidperl is now always built and installed on the system, but
3085da0d091SWarner Losh	with permissions of 511.  If you have applications that use
3095da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
3105da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
3115da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
3125da0d091SWarner Losh	will fix this until the next build.
3135da0d091SWarner Losh
3145da0d091SWarner Losh20000812:
3158f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
3168f250aa7SWarner Losh	visible changes that may immediately affect your configuration
3178f250aa7SWarner Losh	include:
3188f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
3198f250aa7SWarner Losh	- newaliases limited to root and trusted users
3208f250aa7SWarner Losh	- MSA port (587) turned on by default
3218f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
3228f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
3238f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
3248f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
3258f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
3268f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
3278f250aa7SWarner Losh
32871c38472SWarner Losh20000810:
32971c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
33071c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
33171c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
33271c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
33371c38472SWarner Losh	specific use for it.
33471c38472SWarner Losh
33571c38472SWarner Losh20000729:
33671c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
33771c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
33871c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
33971c38472SWarner Losh	afterwards (unless the variables already are set, of course):
34071c38472SWarner Losh		# Enable network daemons for user convenience.
34171c38472SWarner Losh		inetd_enable="YES"
34271c38472SWarner Losh		portmap_enable="YES"
34371c38472SWarner Losh		sendmail_enable="YES"
34471c38472SWarner Losh
34571c38472SWarner Losh20000728:
34671c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
34771c38472SWarner Losh	will need to change that to nullfs_load="YES".
34871c38472SWarner Losh
3491dece4a9SWarner Losh20000728:
3501dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
3511dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
3521dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
3531dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
3541dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
3551dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
3561dece4a9SWarner Losh	to /MYKERNEL.
3571dece4a9SWarner Losh
358409e887cSWarner Losh20000711:
359409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
360409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
361409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
362409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
363409e887cSWarner Losh	for details on potential problems that you might have and how
364409e887cSWarner Losh	to get around them.
365409e887cSWarner Losh
366409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
367409e887cSWarner Losh	clauses above, you needn't worry.
368409e887cSWarner Losh
369409e887cSWarner Losh20000711:
370409e887cSWarner Losh	/etc/security has been updated to print the inode number of
371409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
372409e887cSWarner Losh	in the number of changed programs the first time when you run
373409e887cSWarner Losh	mergemaster to get a new /etc/security.
374409e887cSWarner Losh
375673d13f2SWarner Losh20000710:
376673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
377673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
378673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
379673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
380673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
381673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
382673d13f2SWarner Losh	errors. (see below, 20000624).
383673d13f2SWarner Losh
384bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
3851dece4a9SWarner Losh
386673d13f2SWarner Losh20000709:
387c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
388c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
389c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
390673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
391673d13f2SWarner Losh
392e98e26cdSWarner Losh20000706:
393e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
394e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
395e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
396f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
397e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
3982c021c6cSMark Ovens	interim if needed.
399e98e26cdSWarner Losh
400e98e26cdSWarner Losh20000705:
401e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
402e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
403e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
404e98e26cdSWarner Losh	details.
405e98e26cdSWarner Losh
406c373950eSWarner Losh20000704:
4072f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
4082f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
4092f961bc8SWarner Losh
4102f961bc8SWarner Losh20000704:
411c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
412c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
413c373950eSWarner Losh	rc.d scripts that haven't been updated.
414c373950eSWarner Losh
41527dc3a2bSWarner Losh20000630:
41627dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
41727dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
41827dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
41927dc3a2bSWarner Losh
420b8c215acSWarner Losh20000625:
421b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
42227dc3a2bSWarner Losh	system installed in order to build the system and kernel.
42327dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
42427dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
42527dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
42627dc3a2bSWarner Losh	were required.  You should check with the latest collections
42727dc3a2bSWarner Losh	to make sure that these haven't changed.
428b8c215acSWarner Losh
4297b990719SWarner Losh20000624:
4307b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
4317b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
4327b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
4337b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
4347b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
4357b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
4367b990719SWarner Losh	date to the completion of the work.
4377b990719SWarner Losh
43827dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
43927dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
44027dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
44127dc3a2bSWarner Losh	recreate the random and urandom devices.
44227dc3a2bSWarner Losh
44381e54c50SWarner Losh20000622:
44481e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
44581e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
44681e54c50SWarner Losh	that used to be required when updating.
44781e54c50SWarner Losh
44839943833SWarner Losh20000621:
4492c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
4502a2f33fbSDaniel Baker	the config file update procedure.
4512a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
452c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
453a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
45439943833SWarner Losh
455290f9ad8SWarner Losh20000620:
456290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
457290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
458290f9ad8SWarner Losh	that workaround will no longer be required.
459290f9ad8SWarner Losh
46090fb6346SWarner Losh20000615:
46190fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
46290fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
46390fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
46490fb6346SWarner Losh	devices.
46590fb6346SWarner Losh
466f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
467f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
468f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
469f75f65bbSWarner Losh	may work).
470f75f65bbSWarner Losh
471ba26da8eSWarner Losh20000612:
472ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
473290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
474c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
475290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
476f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
477f54a3542SWarner Losh	NEWCARD for examples of the new format.
478290f9ad8SWarner Losh
479d65850ebSWarner Losh20000522:
480ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
481d65850ebSWarner Losh	building a kernel after this point is advised that they need
482d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
483d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
484d65850ebSWarner Losh
485d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
486d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
487d9583a00SWarner Losh	is recommended that you don't set this option until the problem
488d9583a00SWarner Losh	is resolved.
489d9583a00SWarner Losh
4908039cedeSWarner Losh20000513:
4918039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
4928039cedeSWarner Losh
493d65850ebSWarner Losh20000510:
4948039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
4958039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
4968039cedeSWarner Losh	is requires for the boot blocks to build properly.
4978039cedeSWarner Losh
4988039cedeSWarner Losh20000503:
4998039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
5008039cedeSWarner Losh	is now available.
5018039cedeSWarner Losh
502d65850ebSWarner Losh20000502:
503d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
504d65850ebSWarner Losh	connected to the kernel building instead.
505d65850ebSWarner Losh
506be149406SNik Clayton20000427:
5078039cedeSWarner Losh	You may need to build gperf
5088039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
5098039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
5108039cedeSWarner Losh	an option only in -current.
5118039cedeSWarner Losh
5122b8dd5f4SWarner Losh20000417:
5132b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
514f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
5152b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
5162b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
5172c021c6cSMark Ovens	before you reboot, you'll need to issue:
5182b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
5192b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
5202b8dd5f4SWarner Losh
5218d9f1945SWarner Losh20000320:
5222b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
5232b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
5242b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
5258d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
5262b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
5278d9f1945SWarner Losh
528f8ab1dd6SWarner Losh20000319:
529f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
530f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
531f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
532f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
533f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
534f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
535f8ab1dd6SWarner Losh
53619cada77SWarner Losh20000318:
537f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
53819cada77SWarner Losh	Large kernel changes are being committed and are in the
53919cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
54019cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
54119cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
54219cada77SWarner Losh	that you are loading are up to date.
543ba228352SWarner Losh
54419cada77SWarner Losh20000315:
5456d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
5466d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
5476d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
5486d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
5496d23c382SWarner Losh	boot.
5506d23c382SWarner Losh
5516d23c382SWarner Losh20000315:
55219cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
55319cada77SWarner Losh	to upgrade to 4.0 from 3.x.
55457199806SWarner Losh
555dc0dbf5cSWarner LoshCOMMON ITEMS:
556dc0dbf5cSWarner Losh
557a24eff53SWarner Losh	General Notes
558a24eff53SWarner Losh	-------------
559a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
560a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
561a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
562a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
563a24eff53SWarner Losh	or several minor releases, or when several months have passed
564a24eff53SWarner Losh	on the -current branch).
565a24eff53SWarner Losh
566dc0dbf5cSWarner Losh	To build a kernel
567dc0dbf5cSWarner Losh	-----------------
568ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
569f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
570ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
5711e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
5721e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
573dc0dbf5cSWarner Losh
574ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
575ba01eb20SWarner Losh	--------------------------------------------------------------
576ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
577ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
578ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
579ba01eb20SWarner Losh	make depend
580ba01eb20SWarner Losh	make
581ba01eb20SWarner Losh	make install
582ba01eb20SWarner Losh
583ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
584ba01eb20SWarner Losh
585ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
586ba01eb20SWarner Losh
587ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
588ba01eb20SWarner Losh	-----------------------------------------------------------
589759f0aefSWarner Losh	make world
590fdb9f54dSWarner Losh	Build a new kernel, see above.
591759f0aefSWarner Losh
5921dece4a9SWarner Losh	To upgrade from 4.x-stable to current
593ba26da8eSWarner Losh	-------------------------------------
594ba26da8eSWarner Losh	make buildworld
5951e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
5967595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
5971e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
598ba26da8eSWarner Losh	make installworld
5997595222aSWarner Losh	mergemaster
600134d2e86SWarner Losh	[1]
601ba26da8eSWarner Losh	<reboot>
602ba26da8eSWarner Losh
603fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
604fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
605fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
606fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
607fdb9f54dSWarner Losh	the UPDATING entries.
608ba26da8eSWarner Losh
6091dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
6101dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
6111dece4a9SWarner Losh	your sources that you have read and understood all the recent
6121dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
6131dece4a9SWarner Losh	much fewer pitfalls.
6141dece4a9SWarner Losh
615134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
616134d2e86SWarner Losh	should disable them at this point so they don't crash your
617134d2e86SWarner Losh	system on reboot.
618134d2e86SWarner Losh
6199c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
6209c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
6219c1a7444SWarner Losh	configuration.
6229c1a7444SWarner Losh
623dc0dbf5cSWarner LoshFORMAT:
624dc0dbf5cSWarner Losh
625f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
6261fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
627f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
628f8ab1dd6SWarner Loshprevious releases if your system is older than this.
6291fc1a0dcSWarner Losh
6303645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
6313645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
632f8c77507SWarner Losh
63397d92980SPeter Wemm$FreeBSD$
634