xref: /freebsd/UPDATING (revision a70a79ad2d5e33ae1d7badb02edc4f73f4c7c6f3)
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
82988afcaSWarner Losh20010512:
92988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
102988afcaSWarner Losh	will be the only way to go starting July 1.
112988afcaSWarner Losh
1209946a51SWarner Losh20010502:
1309946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1409946a51SWarner Losh
1509946a51SWarner Losh20010501:
1609946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
1709946a51SWarner Losh
1809946a51SWarner Losh20010430:
19a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
2009946a51SWarner Losh	go back in the water.
2109946a51SWarner Losh
2209946a51SWarner Losh20010429:
2309946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
2409946a51SWarner Losh	this date, but before the correction date.
2509946a51SWarner Losh
2691dd3b53SWarner Losh20010423:
2791dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
2891dd3b53SWarner Losh
2991dd3b53SWarner Losh20010411:
3091dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
3191dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
3291dd3b53SWarner Losh	Update only if you understand that you must not use the old
3391dd3b53SWarner Losh	fsck with the new kernel ever.
3491dd3b53SWarner Losh
35933b3269SWarner Losh20010330:
36933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
37933b3269SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page fora
38933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
39933b3269SWarner Losh
40933b3269SWarner Losh20010319:
41933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
42933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
43933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
4409946a51SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
4509946a51SWarner Losh
4609946a51SWarner Losh20010315:
4709946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
4809946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
4909946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
50933b3269SWarner Losh
51933b3269SWarner Losh20010312:
52933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
53933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
54933b3269SWarner Losh
55933b3269SWarner Losh20010312:
56933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
57933b3269SWarner Losh	instead of ad-hoc.
58933b3269SWarner Losh
59933b3269SWarner Losh20010310:
60933b3269SWarner Losh	/dev/urandmon should be a sumbolic link to /dev/random now.
61933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
62933b3269SWarner Losh	ssh might not work if you don't.
63933b3269SWarner Losh
64d325cf65SWarner Losh20010220:
65d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
66d325cf65SWarner Losh	safe to go back into the water.
67d325cf65SWarner Losh
68024daae6SWarner Losh20010211:
69024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
70024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
71024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
72024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
73024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
74024daae6SWarner Losh
75024daae6SWarner Losh	To get to the new system, you'll need to use the following
76024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
77024daae6SWarner Losh	don't have to move this to the updating section.
78024daae6SWarner Losh
79024daae6SWarner Losh	To get around the installworld problem, do:
80024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
81024daae6SWarner Losh		# make install
82024daae6SWarner Losh		# cd /usr/src
83024daae6SWarner Losh		# make installworld
84024daae6SWarner Losh	If that doesn't work, then try:
85024daae6SWarner Losh		# make -k installworld
86024daae6SWarner Losh		# make installworld
87024daae6SWarner Losh
88024daae6SWarner Losh20010207:
89024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
90024daae6SWarner Losh	do not include devfs in your kernel as problems result.
91024daae6SWarner Losh
92024daae6SWarner Losh20010205:
937595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
94024daae6SWarner Losh	Remove them from your config.
95024daae6SWarner Losh
961e159248SWarner Losh20010122:
971e159248SWarner Losh	****************************** WARNING ******************************
981e159248SWarner Losh			buildkernel has been changed slightly
991e159248SWarner Losh	****************************** WARNING ******************************
1001e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
1011e159248SWarner Losh	should update your scripts and make.conf accordingly.
1021e159248SWarner Losh
1031e159248SWarner Losh20010119:
1041e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
1051e159248SWarner Losh	This requires a new config to build correctly.
1061e159248SWarner Losh
107aac7dfeaSWarner Losh20010116:
108aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
109aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
110aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
111aac7dfeaSWarner Losh
112aac7dfeaSWarner Losh20010110:
113aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
114aac7dfeaSWarner Losh
115aac7dfeaSWarner Losh20010102:
116aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
117aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
118aac7dfeaSWarner Losh
11963c90c9eSWarner Losh20010101:
12063c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
12163c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
1225fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
12363c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
12463c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
12563c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
12663c90c9eSWarner Losh	might have been ignored by the -k option.
12763c90c9eSWarner Losh
1285fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
1295fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
1305fd2a895SWarner Losh	of this working.
1315fd2a895SWarner Losh
132aac7dfeaSWarner Losh20001228:
133aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
134aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
135aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
136aac7dfeaSWarner Losh
137de2bcc63SWarner Losh20001218:
138de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
139de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
140de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
141de2bcc63SWarner Losh	cards will not be recognized without it.
142de2bcc63SWarner Losh
143960773f7SWarner Losh20001205:
144960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
145960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
146960773f7SWarner Losh	adding the following in pam.conf:
147960773f7SWarner Losh
148960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
149960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
150960773f7SWarner Losh	sshd    session required        pam_permit.so
151960773f7SWarner Losh
1520acc635eSWarner Losh20001031:
1530acc635eSWarner Losh	cvs updated to 1.11.
1540acc635eSWarner Losh
1550acc635eSWarner Losh20001020:
1560acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
1570acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
1580acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
1590acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
1600acc635eSWarner Losh	workaround.
1610acc635eSWarner Losh
1620acc635eSWarner Losh20001010:
1630acc635eSWarner Losh	****************************** WARNING ******************************
1640acc635eSWarner Losh				Sendmail has been updated.
1650acc635eSWarner Losh	****************************** WARNING ******************************
1660acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
1670acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1680acc635eSWarner Losh	  is set.
1690acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1700acc635eSWarner Losh	  commands.
1710acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
1720acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
1730acc635eSWarner Losh	  in /usr/share/sendmail/cf.
1740acc635eSWarner Losh	o sendmail.cw changed to local-host-names
1750acc635eSWarner Losh
1760acc635eSWarner Losh	More details can be found at
1770acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1780acc635eSWarner Losh
1796e98a146SWarner Losh20001009:
1806e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
1816e98a146SWarner Losh	your entire ports tree, or you will have problems.
1826e98a146SWarner Losh
1836e98a146SWarner Losh20001006:
184685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
1856e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
1866e98a146SWarner Losh	/usr/bin/miniperl.
1876e98a146SWarner Losh
188073113a4SWarner Losh20001005:
189073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
190685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
191073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
192073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
193073113a4SWarner Losh	tree for anything to work.
194073113a4SWarner Losh
1950acc635eSWarner Losh20000928:
1960acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
1970acc635eSWarner Losh
198be3885b3SWarner Losh20000916:
199be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
200be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
201be3885b3SWarner Losh	same time as your kernel.
202be3885b3SWarner Losh
20376ec9675SWarner Losh20000914:
20476ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
20576ec9675SWarner Losh	include the device will cause suspended laptops losing time
20676ec9675SWarner Losh	when they resume.  Include
20776ec9675SWarner Losh		device		pmtimer
20876ec9675SWarner Losh	in your config file and
20901b9a434SWarner Losh		hint.pmtimer.0.at="isa"
21076ec9675SWarner Losh	to your /boot/device.hints file.
21176ec9675SWarner Losh
212f4865386SMark Murray20000911:
213f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
214f4865386SMark Murray	rather than an option. The supplied kernel config files have
215f4865386SMark Murray	been updated. You will need to do something similar in your
216f4865386SMark Murray	own kernel config file.
217f4865386SMark Murray	Remove:
218f4865386SMark Murray		options		RANDOMDEV
219f4865386SMark Murray	Add:
220f4865386SMark Murray		device		random
221f4865386SMark Murray	If you prefer to load the loadable module, you need to do
222f4865386SMark Murray	nothing.
223f4865386SMark Murray
224d594498fSWarner Losh20000909:
225d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
226d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
227d594498fSWarner Losh	reflect this if you load this module at boot time.
228d594498fSWarner Losh	The line should read:
229d594498fSWarner Losh		random_load="YES"
230d594498fSWarner Losh
2310deb7ddcSWarner Losh20000907:
2320deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
23316eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
23416eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
23516eb772dSWarner Losh	sure you don't have model loading problems which might at
23616eb772dSWarner Losh	first blush appear related to SMP.
23752bf24e7SWarner Losh
2385a01880bSWarner Losh20000906:
2395a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
2405a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
2415a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
2425a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
2435a01880bSWarner Losh	don't have one, and you have host.conf.
2445a01880bSWarner Losh
2452b41163cSWarner Losh20000905:
24638d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
24738d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
24838d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
24938d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
25038d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
25138d6ecd2SWarner Losh
25238d6ecd2SWarner Losh20000905:
2538aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
2548aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
2558aab4bc7SWarner Losh	is /boot/kernel.
2568aab4bc7SWarner Losh
2578aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
25838d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
25938d6ecd2SWarner Losh	installkernel/installworld dance.
2602b41163cSWarner Losh
261d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
262d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
263d594498fSWarner Losh	modules in that directory instead of finding them in the correct
264d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
265d594498fSWarner Losh	is that the linux module crashes your machine after the update.
266d594498fSWarner Losh
267d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
268d594498fSWarner Losh		mv /modules.old /boot/kernel.old
269d594498fSWarner Losh		chflags noschg /kernel.old
270d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
271d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
272d594498fSWarner Losh	fi
273d594498fSWarner Losh
274c22a309cSWarner Losh20000904:
275c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
276c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
277c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
278c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
279c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
280c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
281c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
282c22a309cSWarner Losh	is not likely to be generated.
283c22a309cSWarner Losh
284fdb9f54dSWarner Losh20000825:
285fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
2869c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
2879c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
2889c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
2899c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
2909c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
2919c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
2929c1a7444SWarner Losh	kernel.
2939c1a7444SWarner Losh
2949c1a7444SWarner Losh20000821:
2959c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
2969c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
2979c1a7444SWarner Losh	/boot/loader.conf.
298fdb9f54dSWarner Losh
2998f250aa7SWarner Losh20000812:
3005da0d091SWarner Losh	suidperl is now always built and installed on the system, but
3015da0d091SWarner Losh	with permissions of 511.  If you have applications that use
3025da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
3035da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
3045da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
3055da0d091SWarner Losh	will fix this until the next build.
3065da0d091SWarner Losh
3075da0d091SWarner Losh20000812:
3088f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
3098f250aa7SWarner Losh	visible changes that may immediately affect your configuration
3108f250aa7SWarner Losh	include:
3118f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
3128f250aa7SWarner Losh	- newaliases limited to root and trusted users
3138f250aa7SWarner Losh	- MSA port (587) turned on by default
3148f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
3158f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
3168f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
3178f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
3188f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
3198f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
3208f250aa7SWarner Losh
32171c38472SWarner Losh20000810:
32271c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
32371c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
32471c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
32571c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
32671c38472SWarner Losh	specific use for it.
32771c38472SWarner Losh
32871c38472SWarner Losh20000729:
32971c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
33071c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
33171c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
33271c38472SWarner Losh	afterwards (unless the variables already are set, of course):
33371c38472SWarner Losh		# Enable network daemons for user convenience.
33471c38472SWarner Losh		inetd_enable="YES"
33571c38472SWarner Losh		portmap_enable="YES"
33671c38472SWarner Losh		sendmail_enable="YES"
33771c38472SWarner Losh
33871c38472SWarner Losh20000728:
33971c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
34071c38472SWarner Losh	will need to change that to nullfs_load="YES".
34171c38472SWarner Losh
3421dece4a9SWarner Losh20000728:
3431dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
3441dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
3451dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
3461dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
3471dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
3481dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
3491dece4a9SWarner Losh	to /MYKERNEL.
3501dece4a9SWarner Losh
351409e887cSWarner Losh20000711:
352409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
353409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
354409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
355409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
356409e887cSWarner Losh	for details on potential problems that you might have and how
357409e887cSWarner Losh	to get around them.
358409e887cSWarner Losh
359409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
360409e887cSWarner Losh	clauses above, you needn't worry.
361409e887cSWarner Losh
362409e887cSWarner Losh20000711:
363409e887cSWarner Losh	/etc/security has been updated to print the inode number of
364409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
365409e887cSWarner Losh	in the number of changed programs the first time when you run
366409e887cSWarner Losh	mergemaster to get a new /etc/security.
367409e887cSWarner Losh
368673d13f2SWarner Losh20000710:
369673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
370673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
371673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
372673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
373673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
374673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
375673d13f2SWarner Losh	errors. (see below, 20000624).
376673d13f2SWarner Losh
377bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
3781dece4a9SWarner Losh
379673d13f2SWarner Losh20000709:
380c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
381c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
382c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
383673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
384673d13f2SWarner Losh
385e98e26cdSWarner Losh20000706:
386e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
387e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
388e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
389f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
390e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
3912c021c6cSMark Ovens	interim if needed.
392e98e26cdSWarner Losh
393e98e26cdSWarner Losh20000705:
394e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
395e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
396e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
397e98e26cdSWarner Losh	details.
398e98e26cdSWarner Losh
399c373950eSWarner Losh20000704:
4002f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
4012f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
4022f961bc8SWarner Losh
4032f961bc8SWarner Losh20000704:
404c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
405c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
406c373950eSWarner Losh	rc.d scripts that haven't been updated.
407c373950eSWarner Losh
40827dc3a2bSWarner Losh20000630:
40927dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
41027dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
41127dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
41227dc3a2bSWarner Losh
413b8c215acSWarner Losh20000625:
414b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
41527dc3a2bSWarner Losh	system installed in order to build the system and kernel.
41627dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
41727dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
41827dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
41927dc3a2bSWarner Losh	were required.  You should check with the latest collections
42027dc3a2bSWarner Losh	to make sure that these haven't changed.
421b8c215acSWarner Losh
4227b990719SWarner Losh20000624:
4237b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
4247b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
4257b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
4267b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
4277b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
4287b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
4297b990719SWarner Losh	date to the completion of the work.
4307b990719SWarner Losh
43127dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
43227dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
43327dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
43427dc3a2bSWarner Losh	recreate the random and urandom devices.
43527dc3a2bSWarner Losh
43681e54c50SWarner Losh20000622:
43781e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
43881e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
43981e54c50SWarner Losh	that used to be required when updating.
44081e54c50SWarner Losh
44139943833SWarner Losh20000621:
4422c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
4432a2f33fbSDaniel Baker	the config file update procedure.
4442a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
445c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
446a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
44739943833SWarner Losh
448290f9ad8SWarner Losh20000620:
449290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
450290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
451290f9ad8SWarner Losh	that workaround will no longer be required.
452290f9ad8SWarner Losh
45390fb6346SWarner Losh20000615:
45490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
45590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
45690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
45790fb6346SWarner Losh	devices.
45890fb6346SWarner Losh
459f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
460f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
461f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
462f75f65bbSWarner Losh	may work).
463f75f65bbSWarner Losh
464ba26da8eSWarner Losh20000612:
465ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
466290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
467c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
468290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
469f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
470f54a3542SWarner Losh	NEWCARD for examples of the new format.
471290f9ad8SWarner Losh
472d65850ebSWarner Losh20000522:
473ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
474d65850ebSWarner Losh	building a kernel after this point is advised that they need
475d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
476d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
477d65850ebSWarner Losh
478d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
479d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
480d9583a00SWarner Losh	is recommended that you don't set this option until the problem
481d9583a00SWarner Losh	is resolved.
482d9583a00SWarner Losh
4838039cedeSWarner Losh20000513:
4848039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
4858039cedeSWarner Losh
486d65850ebSWarner Losh20000510:
4878039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
4888039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
4898039cedeSWarner Losh	is requires for the boot blocks to build properly.
4908039cedeSWarner Losh
4918039cedeSWarner Losh20000503:
4928039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
4938039cedeSWarner Losh	is now available.
4948039cedeSWarner Losh
495d65850ebSWarner Losh20000502:
496d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
497d65850ebSWarner Losh	connected to the kernel building instead.
498d65850ebSWarner Losh
499be149406SNik Clayton20000427:
5008039cedeSWarner Losh	You may need to build gperf
5018039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
5028039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
5038039cedeSWarner Losh	an option only in -current.
5048039cedeSWarner Losh
5052b8dd5f4SWarner Losh20000417:
5062b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
507f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
5082b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
5092b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
5102c021c6cSMark Ovens	before you reboot, you'll need to issue:
5112b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
5122b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
5132b8dd5f4SWarner Losh
5148d9f1945SWarner Losh20000320:
5152b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
5162b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
5172b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
5188d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
5192b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
5208d9f1945SWarner Losh
521f8ab1dd6SWarner Losh20000319:
522f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
523f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
524f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
525f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
526f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
527f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
528f8ab1dd6SWarner Losh
52919cada77SWarner Losh20000318:
530f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
53119cada77SWarner Losh	Large kernel changes are being committed and are in the
53219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
53319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
53419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
53519cada77SWarner Losh	that you are loading are up to date.
536ba228352SWarner Losh
53719cada77SWarner Losh20000315:
5386d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
5396d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
5406d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
5416d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
5426d23c382SWarner Losh	boot.
5436d23c382SWarner Losh
5446d23c382SWarner Losh20000315:
54519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
54619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
54757199806SWarner Losh
548dc0dbf5cSWarner LoshCOMMON ITEMS:
549dc0dbf5cSWarner Losh
550a24eff53SWarner Losh	General Notes
551a24eff53SWarner Losh	-------------
552a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
553a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
554a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
555a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
556a24eff53SWarner Losh	or several minor releases, or when several months have passed
557a24eff53SWarner Losh	on the -current branch).
558a24eff53SWarner Losh
559dc0dbf5cSWarner Losh	To build a kernel
560dc0dbf5cSWarner Losh	-----------------
561ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
562f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
563ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
5641e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
5651e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
566dc0dbf5cSWarner Losh
567ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
568ba01eb20SWarner Losh	--------------------------------------------------------------
569ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
570ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
571ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
572ba01eb20SWarner Losh	make depend
573ba01eb20SWarner Losh	make
574ba01eb20SWarner Losh	make install
575ba01eb20SWarner Losh
576ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
577ba01eb20SWarner Losh
578ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
579ba01eb20SWarner Losh
580ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
581ba01eb20SWarner Losh	-----------------------------------------------------------
582759f0aefSWarner Losh	make world
583fdb9f54dSWarner Losh	Build a new kernel, see above.
584759f0aefSWarner Losh
5851dece4a9SWarner Losh	To upgrade from 4.x-stable to current
586ba26da8eSWarner Losh	-------------------------------------
587ba26da8eSWarner Losh	make buildworld
5881e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
5897595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
5901e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
591ba26da8eSWarner Losh	make installworld
5927595222aSWarner Losh	mergemaster
593134d2e86SWarner Losh	[1]
594ba26da8eSWarner Losh	<reboot>
595ba26da8eSWarner Losh
596fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
597fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
598fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
599fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
600fdb9f54dSWarner Losh	the UPDATING entries.
601ba26da8eSWarner Losh
6021dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
6031dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
6041dece4a9SWarner Losh	your sources that you have read and understood all the recent
6051dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
6061dece4a9SWarner Losh	much fewer pitfalls.
6071dece4a9SWarner Losh
608134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
609134d2e86SWarner Losh	should disable them at this point so they don't crash your
610134d2e86SWarner Losh	system on reboot.
611134d2e86SWarner Losh
6129c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
6139c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
6149c1a7444SWarner Losh	configuration.
6159c1a7444SWarner Losh
616dc0dbf5cSWarner LoshFORMAT:
617dc0dbf5cSWarner Losh
618f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
6191fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
620f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
621f8ab1dd6SWarner Loshprevious releases if your system is older than this.
6221fc1a0dcSWarner Losh
6233645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
6243645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
625f8c77507SWarner Losh
62697d92980SPeter Wemm$FreeBSD$
627