xref: /freebsd/UPDATING (revision 8b9959ada826de46460ce68966626fe7f55690dc)
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
88b9959adSWarner Losh20010613:
98b9959adSWarner Losh	Two items that have been biting people:
108b9959adSWarner Losh
118b9959adSWarner Losh	pccard modems may not work with current after 20010604 date.  Some
128b9959adSWarner Losh	do, others result in panics.  *MAKE*SURE* that you update your
138b9959adSWarner Losh	config ala the 20010604 entry, or you will have problems (this issue
148b9959adSWarner Losh	will be fixed, it just hasn't been yet).
158b9959adSWarner Losh
168b9959adSWarner Losh	SOFTUPDATES seem to be broken since the middle of May or so.  Do not
178b9959adSWarner Losh	use them in current.  Resolution unknown.
188b9959adSWarner Losh
196ccdb5e4SWarner Losh20010604:
206ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
216ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
226ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
233590182eSWarner Losh	Interrupt storms look a lot like a hang.
243590182eSWarner Losh
253590182eSWarner Losh	You must also install a new pccardd, otherwise you will get an
263590182eSWarner Losh	interrupt storm at card reset time (just after it tells you what
273590182eSWarner Losh	it is).
283590182eSWarner Losh
293590182eSWarner Losh	pccardd_flags="-I" is necessary for the time being.  It tells pccardd
303590182eSWarner Losh	not to ask the kernel if the interrupt is really free or not before
313590182eSWarner Losh	using it.  You can either change the /etc/pccard.conf irq lines to
323590182eSWarner Losh	match pcic, or add "-i X" to the pccardd_flags.
336ccdb5e4SWarner Losh
340bc62786SWarner Losh20010530:
350bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
360bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
370bc62786SWarner Losh	a limited time.  If you see
380bc62786SWarner Losh
390bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
400bc62786SWarner Losh
410bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
420bc62786SWarner Losh	COPY=-C.
430bc62786SWarner Losh
4468a38c6cSWarner Losh20010525:
45b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
46c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
47c4f4a728SWarner Losh	definitely is in bad shape.
4868a38c6cSWarner Losh
49ed0f29caSWarner Losh20010521:
50ed0f29caSWarner Losh	Minor repo damanged has happened.  This may cause problems
51ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
52ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
53ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
54ed0f29caSWarner Losh	is
55ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
56ed0f29caSWarner Losh
5780c16af9SWarner Losh20010520:
5868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
5980c16af9SWarner Losh
6080c16af9SWarner Losh20010519:
6180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
6280c16af9SWarner Losh	the past few days.  Everything should still work, but if
6380c16af9SWarner Losh	not, please contact imp@freebsd.org.
6480c16af9SWarner Losh
65a45f2d05SWarner Losh20010517:
66a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
67a45f2d05SWarner Losh	userland at the same time.
68a45f2d05SWarner Losh
69a45f2d05SWarner Losh20010517:
70a45f2d05SWarner Losh	New ncurses imported.
71a45f2d05SWarner Losh
722988afcaSWarner Losh20010512:
732988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
742988afcaSWarner Losh	will be the only way to go starting July 1.
752988afcaSWarner Losh
7609946a51SWarner Losh20010502:
7709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
7809946a51SWarner Losh
7909946a51SWarner Losh20010501:
8009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
8109946a51SWarner Losh
8209946a51SWarner Losh20010430:
83a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
8409946a51SWarner Losh	go back in the water.
8509946a51SWarner Losh
8609946a51SWarner Losh20010429:
8709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
8809946a51SWarner Losh	this date, but before the correction date.
8909946a51SWarner Losh
9091dd3b53SWarner Losh20010423:
9191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
9291dd3b53SWarner Losh
9391dd3b53SWarner Losh20010411:
9491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
9591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
9691dd3b53SWarner Losh	Update only if you understand that you must not use the old
9791dd3b53SWarner Losh	fsck with the new kernel ever.
9891dd3b53SWarner Losh
99933b3269SWarner Losh20010330:
100933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
101c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
102933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
103933b3269SWarner Losh
104933b3269SWarner Losh20010319:
105933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
106933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
107933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
10809946a51SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
10909946a51SWarner Losh
11009946a51SWarner Losh20010315:
11109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
11209946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
11309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
114933b3269SWarner Losh
115933b3269SWarner Losh20010312:
116933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
117933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
118933b3269SWarner Losh
119933b3269SWarner Losh20010312:
120933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
121933b3269SWarner Losh	instead of ad-hoc.
122933b3269SWarner Losh
123933b3269SWarner Losh20010310:
124f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
125933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
126933b3269SWarner Losh	ssh might not work if you don't.
127933b3269SWarner Losh
128d325cf65SWarner Losh20010220:
129d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
130d325cf65SWarner Losh	safe to go back into the water.
131d325cf65SWarner Losh
132024daae6SWarner Losh20010211:
133024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
134024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
135024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
136024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
137024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
138024daae6SWarner Losh
139024daae6SWarner Losh	To get to the new system, you'll need to use the following
140024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
141024daae6SWarner Losh	don't have to move this to the updating section.
142024daae6SWarner Losh
143024daae6SWarner Losh	To get around the installworld problem, do:
144024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
145024daae6SWarner Losh		# make install
146024daae6SWarner Losh		# cd /usr/src
147024daae6SWarner Losh		# make installworld
148024daae6SWarner Losh	If that doesn't work, then try:
149024daae6SWarner Losh		# make -k installworld
150024daae6SWarner Losh		# make installworld
151024daae6SWarner Losh
152024daae6SWarner Losh20010207:
153024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
154024daae6SWarner Losh	do not include devfs in your kernel as problems result.
155024daae6SWarner Losh
156024daae6SWarner Losh20010205:
1577595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
158024daae6SWarner Losh	Remove them from your config.
159024daae6SWarner Losh
1601e159248SWarner Losh20010122:
1611e159248SWarner Losh	****************************** WARNING ******************************
1621e159248SWarner Losh			buildkernel has been changed slightly
1631e159248SWarner Losh	****************************** WARNING ******************************
1641e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
1651e159248SWarner Losh	should update your scripts and make.conf accordingly.
1661e159248SWarner Losh
1671e159248SWarner Losh20010119:
1681e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
1691e159248SWarner Losh	This requires a new config to build correctly.
1701e159248SWarner Losh
171aac7dfeaSWarner Losh20010116:
172aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
173aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
174aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
175aac7dfeaSWarner Losh
176aac7dfeaSWarner Losh20010110:
177aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
178aac7dfeaSWarner Losh
179aac7dfeaSWarner Losh20010102:
180aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
181aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
182aac7dfeaSWarner Losh
18363c90c9eSWarner Losh20010101:
18463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
18563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
1865fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
18763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
18863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
18963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
19063c90c9eSWarner Losh	might have been ignored by the -k option.
19163c90c9eSWarner Losh
1925fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
1935fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
1945fd2a895SWarner Losh	of this working.
1955fd2a895SWarner Losh
196aac7dfeaSWarner Losh20001228:
197aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
198aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
199aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
200aac7dfeaSWarner Losh
201de2bcc63SWarner Losh20001218:
202de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
203de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
204de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
205de2bcc63SWarner Losh	cards will not be recognized without it.
206de2bcc63SWarner Losh
207960773f7SWarner Losh20001205:
208960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
209960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
210960773f7SWarner Losh	adding the following in pam.conf:
211960773f7SWarner Losh
212960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
213960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
214960773f7SWarner Losh	sshd    session required        pam_permit.so
215960773f7SWarner Losh
2160acc635eSWarner Losh20001031:
2170acc635eSWarner Losh	cvs updated to 1.11.
2180acc635eSWarner Losh
2190acc635eSWarner Losh20001020:
2200acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
2210acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
2220acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
2230acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
2240acc635eSWarner Losh	workaround.
2250acc635eSWarner Losh
2260acc635eSWarner Losh20001010:
2270acc635eSWarner Losh	****************************** WARNING ******************************
2280acc635eSWarner Losh				Sendmail has been updated.
2290acc635eSWarner Losh	****************************** WARNING ******************************
2300acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
2310acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
2320acc635eSWarner Losh	  is set.
2330acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
2340acc635eSWarner Losh	  commands.
2350acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
2360acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
2370acc635eSWarner Losh	  in /usr/share/sendmail/cf.
2380acc635eSWarner Losh	o sendmail.cw changed to local-host-names
2390acc635eSWarner Losh
2400acc635eSWarner Losh	More details can be found at
2410acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
2420acc635eSWarner Losh
2436e98a146SWarner Losh20001009:
2446e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
2456e98a146SWarner Losh	your entire ports tree, or you will have problems.
2466e98a146SWarner Losh
2476e98a146SWarner Losh20001006:
248685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
2496e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
2506e98a146SWarner Losh	/usr/bin/miniperl.
2516e98a146SWarner Losh
252073113a4SWarner Losh20001005:
253073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
254685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
255073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
256073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
257073113a4SWarner Losh	tree for anything to work.
258073113a4SWarner Losh
2590acc635eSWarner Losh20000928:
2600acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
2610acc635eSWarner Losh
262be3885b3SWarner Losh20000916:
263be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
264be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
265be3885b3SWarner Losh	same time as your kernel.
266be3885b3SWarner Losh
26776ec9675SWarner Losh20000914:
26876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
26976ec9675SWarner Losh	include the device will cause suspended laptops losing time
27076ec9675SWarner Losh	when they resume.  Include
27176ec9675SWarner Losh		device		pmtimer
27276ec9675SWarner Losh	in your config file and
27301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
27476ec9675SWarner Losh	to your /boot/device.hints file.
27576ec9675SWarner Losh
276f4865386SMark Murray20000911:
277f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
278f4865386SMark Murray	rather than an option. The supplied kernel config files have
279f4865386SMark Murray	been updated. You will need to do something similar in your
280f4865386SMark Murray	own kernel config file.
281f4865386SMark Murray	Remove:
282f4865386SMark Murray		options		RANDOMDEV
283f4865386SMark Murray	Add:
284f4865386SMark Murray		device		random
285f4865386SMark Murray	If you prefer to load the loadable module, you need to do
286f4865386SMark Murray	nothing.
287f4865386SMark Murray
288d594498fSWarner Losh20000909:
289d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
290d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
291d594498fSWarner Losh	reflect this if you load this module at boot time.
292d594498fSWarner Losh	The line should read:
293d594498fSWarner Losh		random_load="YES"
294d594498fSWarner Losh
2950deb7ddcSWarner Losh20000907:
2960deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
29716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
29816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
29916eb772dSWarner Losh	sure you don't have model loading problems which might at
30016eb772dSWarner Losh	first blush appear related to SMP.
30152bf24e7SWarner Losh
3025a01880bSWarner Losh20000906:
3035a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
3045a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
3055a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
3065a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
3075a01880bSWarner Losh	don't have one, and you have host.conf.
3085a01880bSWarner Losh
3092b41163cSWarner Losh20000905:
31038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
31138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
31238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
31338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
31438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
31538d6ecd2SWarner Losh
31638d6ecd2SWarner Losh20000905:
3178aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
3188aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
3198aab4bc7SWarner Losh	is /boot/kernel.
3208aab4bc7SWarner Losh
3218aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
32238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
32338d6ecd2SWarner Losh	installkernel/installworld dance.
3242b41163cSWarner Losh
325d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
326d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
327d594498fSWarner Losh	modules in that directory instead of finding them in the correct
328d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
329d594498fSWarner Losh	is that the linux module crashes your machine after the update.
330d594498fSWarner Losh
331d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
332d594498fSWarner Losh		mv /modules.old /boot/kernel.old
333d594498fSWarner Losh		chflags noschg /kernel.old
334d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
335d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
336d594498fSWarner Losh	fi
337d594498fSWarner Losh
338c22a309cSWarner Losh20000904:
339c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
340c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
341c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
342c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
343c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
344c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
345c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
346c22a309cSWarner Losh	is not likely to be generated.
347c22a309cSWarner Losh
348fdb9f54dSWarner Losh20000825:
349fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
3509c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
3519c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
3529c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
3539c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
3549c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
3559c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
3569c1a7444SWarner Losh	kernel.
3579c1a7444SWarner Losh
3589c1a7444SWarner Losh20000821:
3599c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
3609c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
3619c1a7444SWarner Losh	/boot/loader.conf.
362fdb9f54dSWarner Losh
3638f250aa7SWarner Losh20000812:
3645da0d091SWarner Losh	suidperl is now always built and installed on the system, but
3655da0d091SWarner Losh	with permissions of 511.  If you have applications that use
3665da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
3675da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
3685da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
3695da0d091SWarner Losh	will fix this until the next build.
3705da0d091SWarner Losh
3715da0d091SWarner Losh20000812:
3728f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
3738f250aa7SWarner Losh	visible changes that may immediately affect your configuration
3748f250aa7SWarner Losh	include:
3758f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
3768f250aa7SWarner Losh	- newaliases limited to root and trusted users
3778f250aa7SWarner Losh	- MSA port (587) turned on by default
3788f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
3798f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
3808f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
3818f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
3828f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
3838f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
3848f250aa7SWarner Losh
38571c38472SWarner Losh20000810:
38671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
38771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
38871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
38971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
39071c38472SWarner Losh	specific use for it.
39171c38472SWarner Losh
39271c38472SWarner Losh20000729:
39371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
39471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
39571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
39671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
39771c38472SWarner Losh		# Enable network daemons for user convenience.
39871c38472SWarner Losh		inetd_enable="YES"
39971c38472SWarner Losh		portmap_enable="YES"
40071c38472SWarner Losh		sendmail_enable="YES"
40171c38472SWarner Losh
40271c38472SWarner Losh20000728:
40371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
40471c38472SWarner Losh	will need to change that to nullfs_load="YES".
40571c38472SWarner Losh
4061dece4a9SWarner Losh20000728:
4071dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
4081dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
4091dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
4101dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
4111dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
4121dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
4131dece4a9SWarner Losh	to /MYKERNEL.
4141dece4a9SWarner Losh
415409e887cSWarner Losh20000711:
416409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
417409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
418409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
419409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
420409e887cSWarner Losh	for details on potential problems that you might have and how
421409e887cSWarner Losh	to get around them.
422409e887cSWarner Losh
423409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
424409e887cSWarner Losh	clauses above, you needn't worry.
425409e887cSWarner Losh
426409e887cSWarner Losh20000711:
427409e887cSWarner Losh	/etc/security has been updated to print the inode number of
428409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
429409e887cSWarner Losh	in the number of changed programs the first time when you run
430409e887cSWarner Losh	mergemaster to get a new /etc/security.
431409e887cSWarner Losh
432673d13f2SWarner Losh20000710:
433673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
434673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
435673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
436673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
437673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
438673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
439673d13f2SWarner Losh	errors. (see below, 20000624).
440673d13f2SWarner Losh
441bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
4421dece4a9SWarner Losh
443673d13f2SWarner Losh20000709:
444c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
445c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
446c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
447673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
448673d13f2SWarner Losh
449e98e26cdSWarner Losh20000706:
450e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
451e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
452e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
453f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
454e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
4552c021c6cSMark Ovens	interim if needed.
456e98e26cdSWarner Losh
457e98e26cdSWarner Losh20000705:
458e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
459e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
460e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
461e98e26cdSWarner Losh	details.
462e98e26cdSWarner Losh
463c373950eSWarner Losh20000704:
4642f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
4652f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
4662f961bc8SWarner Losh
4672f961bc8SWarner Losh20000704:
468c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
469c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
470c373950eSWarner Losh	rc.d scripts that haven't been updated.
471c373950eSWarner Losh
47227dc3a2bSWarner Losh20000630:
47327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
47427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
47527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
47627dc3a2bSWarner Losh
477b8c215acSWarner Losh20000625:
478b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
47927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
48027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
48127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
48227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
48327dc3a2bSWarner Losh	were required.  You should check with the latest collections
48427dc3a2bSWarner Losh	to make sure that these haven't changed.
485b8c215acSWarner Losh
4867b990719SWarner Losh20000624:
4877b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
4887b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
4897b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
4907b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
4917b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
4927b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
4937b990719SWarner Losh	date to the completion of the work.
4947b990719SWarner Losh
49527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
49627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
49727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
49827dc3a2bSWarner Losh	recreate the random and urandom devices.
49927dc3a2bSWarner Losh
50081e54c50SWarner Losh20000622:
50181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
50281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
50381e54c50SWarner Losh	that used to be required when updating.
50481e54c50SWarner Losh
50539943833SWarner Losh20000621:
5062c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
5072a2f33fbSDaniel Baker	the config file update procedure.
5082a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
509c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
510a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
51139943833SWarner Losh
512290f9ad8SWarner Losh20000620:
513290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
514290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
515290f9ad8SWarner Losh	that workaround will no longer be required.
516290f9ad8SWarner Losh
51790fb6346SWarner Losh20000615:
51890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
51990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
52090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
52190fb6346SWarner Losh	devices.
52290fb6346SWarner Losh
523f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
524f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
525f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
526f75f65bbSWarner Losh	may work).
527f75f65bbSWarner Losh
528ba26da8eSWarner Losh20000612:
529ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
530290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
531c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
532290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
533f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
534f54a3542SWarner Losh	NEWCARD for examples of the new format.
535290f9ad8SWarner Losh
536d65850ebSWarner Losh20000522:
537ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
538d65850ebSWarner Losh	building a kernel after this point is advised that they need
539d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
540d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
541d65850ebSWarner Losh
542d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
543d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
544d9583a00SWarner Losh	is recommended that you don't set this option until the problem
545d9583a00SWarner Losh	is resolved.
546d9583a00SWarner Losh
5478039cedeSWarner Losh20000513:
5488039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
5498039cedeSWarner Losh
550d65850ebSWarner Losh20000510:
5518039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
5528039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
5538039cedeSWarner Losh	is requires for the boot blocks to build properly.
5548039cedeSWarner Losh
5558039cedeSWarner Losh20000503:
5568039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
5578039cedeSWarner Losh	is now available.
5588039cedeSWarner Losh
559d65850ebSWarner Losh20000502:
560d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
561d65850ebSWarner Losh	connected to the kernel building instead.
562d65850ebSWarner Losh
563be149406SNik Clayton20000427:
5648039cedeSWarner Losh	You may need to build gperf
5658039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
5668039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
5678039cedeSWarner Losh	an option only in -current.
5688039cedeSWarner Losh
5692b8dd5f4SWarner Losh20000417:
5702b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
571f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
5722b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
5732b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
5742c021c6cSMark Ovens	before you reboot, you'll need to issue:
5752b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
5762b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
5772b8dd5f4SWarner Losh
5788d9f1945SWarner Losh20000320:
5792b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
5802b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
5812b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
5828d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
5832b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
5848d9f1945SWarner Losh
585f8ab1dd6SWarner Losh20000319:
586f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
587f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
588f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
589f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
590f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
591f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
592f8ab1dd6SWarner Losh
59319cada77SWarner Losh20000318:
594f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
59519cada77SWarner Losh	Large kernel changes are being committed and are in the
59619cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
59719cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
59819cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
59919cada77SWarner Losh	that you are loading are up to date.
600ba228352SWarner Losh
60119cada77SWarner Losh20000315:
6026d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
6036d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
6046d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
6056d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
6066d23c382SWarner Losh	boot.
6076d23c382SWarner Losh
6086d23c382SWarner Losh20000315:
60919cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
61019cada77SWarner Losh	to upgrade to 4.0 from 3.x.
61157199806SWarner Losh
612dc0dbf5cSWarner LoshCOMMON ITEMS:
613dc0dbf5cSWarner Losh
614a24eff53SWarner Losh	General Notes
615a24eff53SWarner Losh	-------------
616a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
617a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
618a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
619a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
620a24eff53SWarner Losh	or several minor releases, or when several months have passed
621a24eff53SWarner Losh	on the -current branch).
622a24eff53SWarner Losh
623dc0dbf5cSWarner Losh	To build a kernel
624dc0dbf5cSWarner Losh	-----------------
625ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
626f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
627ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
6281e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
6291e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
630dc0dbf5cSWarner Losh
631ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
632ba01eb20SWarner Losh	--------------------------------------------------------------
633ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
634ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
635ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
636ba01eb20SWarner Losh	make depend
637ba01eb20SWarner Losh	make
638ba01eb20SWarner Losh	make install
639ba01eb20SWarner Losh
640ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
641ba01eb20SWarner Losh
642ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
643ba01eb20SWarner Losh
644ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
645ba01eb20SWarner Losh	-----------------------------------------------------------
646759f0aefSWarner Losh	make world
647fdb9f54dSWarner Losh	Build a new kernel, see above.
648759f0aefSWarner Losh
6491dece4a9SWarner Losh	To upgrade from 4.x-stable to current
650ba26da8eSWarner Losh	-------------------------------------
651ba26da8eSWarner Losh	make buildworld
6521e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
6537595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
6541e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
655ee6e1fc3SWarner Losh	reboot in single user [3]
656ba26da8eSWarner Losh	make installworld
6577595222aSWarner Losh	mergemaster
658134d2e86SWarner Losh	[1]
659ba26da8eSWarner Losh	<reboot>
660ba26da8eSWarner Losh
661fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
662fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
663fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
664fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
665fdb9f54dSWarner Losh	the UPDATING entries.
666ba26da8eSWarner Losh
6671dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
6681dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
6691dece4a9SWarner Losh	your sources that you have read and understood all the recent
6701dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
6711dece4a9SWarner Losh	much fewer pitfalls.
6721dece4a9SWarner Losh
673134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
674134d2e86SWarner Losh	should disable them at this point so they don't crash your
675134d2e86SWarner Losh	system on reboot.
676134d2e86SWarner Losh
6779c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
6789c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
6799c1a7444SWarner Losh	configuration.
6809c1a7444SWarner Losh
681ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
682ee6e1fc3SWarner Losh		fsck -p
683ee6e1fc3SWarner Losh		mount -u /
684ee6e1fc3SWarner Losh		mount -a
685ee6e1fc3SWarner Losh		cd /usr/src
686ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
687ee6e1fc3SWarner Losh
688dc0dbf5cSWarner LoshFORMAT:
689dc0dbf5cSWarner Losh
690f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
6911fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
692f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
693f8ab1dd6SWarner Loshprevious releases if your system is older than this.
6941fc1a0dcSWarner Losh
6953645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
6963645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
697f8c77507SWarner Losh
69897d92980SPeter Wemm$FreeBSD$
699