xref: /freebsd/UPDATING (revision ee6e1fc3808fd9eb80d43c374586c257bf3c5a45)
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
86ccdb5e4SWarner Losh20010604:
96ccdb5e4SWarner Losh	pccard support for pci cards has been committed.  You must change
106ccdb5e4SWarner Losh	your /etc/pccard.conf irq lines.  It must match the irq used by
116ccdb5e4SWarner Losh	pcic device.  Interrupt storms may result if you fail to do this.
126ccdb5e4SWarner Losh	Interrupt storms look a lot like a hang.
136ccdb5e4SWarner Losh
140bc62786SWarner Losh20010530:
150bc62786SWarner Losh	INSTALL=install -C is being deprecated.  If you want to do this,
160bc62786SWarner Losh	use COPY=-C instead.  The former method will be supported for only
170bc62786SWarner Losh	a limited time.  If you see
180bc62786SWarner Losh
190bc62786SWarner Loshinstall: warning: the -d and -C options may not be specified together
200bc62786SWarner Losh
210bc62786SWarner Losh	in your makeworld, then you need to migrate towards using
220bc62786SWarner Losh	COPY=-C.
230bc62786SWarner Losh
2468a38c6cSWarner Losh20010525:
25b6609bbbSWarner Losh	It appears that vm is now stable enough to use again.  However,
26c4f4a728SWarner Losh	there may be other problems, so caution is still urged.  alpha
27c4f4a728SWarner Losh	definitely is in bad shape.
2868a38c6cSWarner Losh
29ed0f29caSWarner Losh20010521:
30ed0f29caSWarner Losh	Minor repo damanged has happened.  This may cause problems
31ed0f29caSWarner Losh	with cvsup of ports.  If you get errors, please see
32ed0f29caSWarner Losh	http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
33ed0f29caSWarner Losh	at the bottom for details on a workaround.  The error message
34ed0f29caSWarner Losh	is
35ed0f29caSWarner LoshUpdater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
36ed0f29caSWarner Losh
3780c16af9SWarner Losh20010520:
3868a38c6cSWarner Losh	Vm and/or swapping are busted on -current.  Please be patient.
3980c16af9SWarner Losh
4080c16af9SWarner Losh20010519:
4180c16af9SWarner Losh	pccard has had much reorganizational work done to it over
4280c16af9SWarner Losh	the past few days.  Everything should still work, but if
4380c16af9SWarner Losh	not, please contact imp@freebsd.org.
4480c16af9SWarner Losh
45a45f2d05SWarner Losh20010517:
46a45f2d05SWarner Losh	ata ioctl changed.  Make sure to recompile both kernel and
47a45f2d05SWarner Losh	userland at the same time.
48a45f2d05SWarner Losh
49a45f2d05SWarner Losh20010517:
50a45f2d05SWarner Losh	New ncurses imported.
51a45f2d05SWarner Losh
522988afcaSWarner Losh20010512:
532988afcaSWarner Losh	DEVFS is now opt out, not opt in.  Barring major problems, this
542988afcaSWarner Losh	will be the only way to go starting July 1.
552988afcaSWarner Losh
5609946a51SWarner Losh20010502:
5709946a51SWarner Losh	Perl breakage in 20010501 was corrected at 14:18:33 PDT.
5809946a51SWarner Losh
5909946a51SWarner Losh20010501:
6009946a51SWarner Losh	Building perl was broken at 02:25:25 PDT.
6109946a51SWarner Losh
6209946a51SWarner Losh20010430:
63a70a79adSWarner Losh	The bug in 20010429 was corrected at 07:35:37 PDT.  It is safe to
6409946a51SWarner Losh	go back in the water.
6509946a51SWarner Losh
6609946a51SWarner Losh20010429:
6709946a51SWarner Losh	A bad bug was committed at 04:48:42 PDT.  Don't use kernels after
6809946a51SWarner Losh	this date, but before the correction date.
6909946a51SWarner Losh
7091dd3b53SWarner Losh20010423:
7191dd3b53SWarner Losh	old fsck and new kernel interactions appear to have been fixed.
7291dd3b53SWarner Losh
7391dd3b53SWarner Losh20010411:
7491dd3b53SWarner Losh	fsck and the kernel were changed to handle some optimizations
7591dd3b53SWarner Losh	to directory layout.  This breaks backward compatibility.
7691dd3b53SWarner Losh	Update only if you understand that you must not use the old
7791dd3b53SWarner Losh	fsck with the new kernel ever.
7891dd3b53SWarner Losh
79933b3269SWarner Losh20010330:
80933b3269SWarner Losh	fsck has changed the meaning of the pass column in /etc/fstab.
81c4e215d3SWarner Losh	Please see the cvs commit to fsck.8 or the fsck.8 man page for
82933b3269SWarner Losh	details.  It is unclear if changes to /etc/fstab are necessary.
83933b3269SWarner Losh
84933b3269SWarner Losh20010319:
85933b3269SWarner Losh	portmap had changed name to rpcbind for maximum POLA in your
86933b3269SWarner Losh	current world.  /etc/hosts.{allow,deny} needs changes.  nfs and
87933b3269SWarner Losh	other rpc based programs that rely on portmapper will not work
8809946a51SWarner Losh	without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
8909946a51SWarner Losh
9009946a51SWarner Losh20010315:
9109946a51SWarner Losh	ata subsystem changes.  ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
9209946a51SWarner Losh	and ATA_ENABEL_TAGS are no longer kernel options.  They have
9309946a51SWarner Losh	been replaced by tunables.  See ata.4 for details.
94933b3269SWarner Losh
95933b3269SWarner Losh20010312:
96933b3269SWarner Losh	The fxp driver was converted to use miibus.  If you compile
97933b3269SWarner Losh	fxp into your kernel statically, you will need to add miibus.
98933b3269SWarner Losh
99933b3269SWarner Losh20010312:
100933b3269SWarner Losh	The wi device now defaults to BSS (infrastructure) mode
101933b3269SWarner Losh	instead of ad-hoc.
102933b3269SWarner Losh
103933b3269SWarner Losh20010310:
104f5260d32SWarner Losh	/dev/urandom should be a symbolic link to /dev/random now.
105933b3269SWarner Losh	Users of current not using DEVFS need to run MAKEDEV std.
106933b3269SWarner Losh	ssh might not work if you don't.
107933b3269SWarner Losh
108d325cf65SWarner Losh20010220:
109d325cf65SWarner Losh	The problems with libc have been corrected.  It is now mostly
110d325cf65SWarner Losh	safe to go back into the water.
111d325cf65SWarner Losh
112024daae6SWarner Losh20010211:
113024daae6SWarner Losh	The size of FILE was changed.  This breaks upgrading.  If
114024daae6SWarner Losh	you must upgrade, be prepared for pain.  It also breaks almost
115024daae6SWarner Losh	all binaries that you've compiled on -current.  You are warned
116024daae6SWarner Losh	that before upgrading would be a good time to do a level 0
117024daae6SWarner Losh	dump of your system.  No, really, I mean it this time.
118024daae6SWarner Losh
119024daae6SWarner Losh	To get to the new system, you'll need to use the following
120024daae6SWarner Losh	workaround.  Hopefully this can be sorted out so that we
121024daae6SWarner Losh	don't have to move this to the updating section.
122024daae6SWarner Losh
123024daae6SWarner Losh	To get around the installworld problem, do:
124024daae6SWarner Losh		# cd /usr/src/usr.bin/sed
125024daae6SWarner Losh		# make install
126024daae6SWarner Losh		# cd /usr/src
127024daae6SWarner Losh		# make installworld
128024daae6SWarner Losh	If that doesn't work, then try:
129024daae6SWarner Losh		# make -k installworld
130024daae6SWarner Losh		# make installworld
131024daae6SWarner Losh
132024daae6SWarner Losh20010207:
133024daae6SWarner Losh	DEVFS is now the default.  If you use vinum, make sure that you
134024daae6SWarner Losh	do not include devfs in your kernel as problems result.
135024daae6SWarner Losh
136024daae6SWarner Losh20010205:
1377595222aSWarner Losh	FFS_ROOT and CD9660_ROOT have been removed or deprecated.
138024daae6SWarner Losh	Remove them from your config.
139024daae6SWarner Losh
1401e159248SWarner Losh20010122:
1411e159248SWarner Losh	****************************** WARNING ******************************
1421e159248SWarner Losh			buildkernel has been changed slightly
1431e159248SWarner Losh	****************************** WARNING ******************************
1441e159248SWarner Losh	KERNCONF replaces the variable KERNEL for buildkernel.  You
1451e159248SWarner Losh	should update your scripts and make.conf accordingly.
1461e159248SWarner Losh
1471e159248SWarner Losh20010119:
1481e159248SWarner Losh	config has changed to allow DEV_FOO as a replacement for NFOO.
1491e159248SWarner Losh	This requires a new config to build correctly.
1501e159248SWarner Losh
151aac7dfeaSWarner Losh20010116:
152aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
153aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
154aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
155aac7dfeaSWarner Losh
156aac7dfeaSWarner Losh20010110:
157aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
158aac7dfeaSWarner Losh
159aac7dfeaSWarner Losh20010102:
160aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
161aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
162aac7dfeaSWarner Losh
16363c90c9eSWarner Losh20010101:
16463c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
16563c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
1665fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
16763c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
16863c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
16963c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
17063c90c9eSWarner Losh	might have been ignored by the -k option.
17163c90c9eSWarner Losh
1725fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
1735fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
1745fd2a895SWarner Losh	of this working.
1755fd2a895SWarner Losh
176aac7dfeaSWarner Losh20001228:
177aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
178aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
179aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
180aac7dfeaSWarner Losh
181de2bcc63SWarner Losh20001218:
182de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
183de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
184de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
185de2bcc63SWarner Losh	cards will not be recognized without it.
186de2bcc63SWarner Losh
187960773f7SWarner Losh20001205:
188960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
189960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
190960773f7SWarner Losh	adding the following in pam.conf:
191960773f7SWarner Losh
192960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
193960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
194960773f7SWarner Losh	sshd    session required        pam_permit.so
195960773f7SWarner Losh
1960acc635eSWarner Losh20001031:
1970acc635eSWarner Losh	cvs updated to 1.11.
1980acc635eSWarner Losh
1990acc635eSWarner Losh20001020:
2000acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
2010acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
2020acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
2030acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
2040acc635eSWarner Losh	workaround.
2050acc635eSWarner Losh
2060acc635eSWarner Losh20001010:
2070acc635eSWarner Losh	****************************** WARNING ******************************
2080acc635eSWarner Losh				Sendmail has been updated.
2090acc635eSWarner Losh	****************************** WARNING ******************************
2100acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
2110acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
2120acc635eSWarner Losh	  is set.
2130acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
2140acc635eSWarner Losh	  commands.
2150acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
2160acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
2170acc635eSWarner Losh	  in /usr/share/sendmail/cf.
2180acc635eSWarner Losh	o sendmail.cw changed to local-host-names
2190acc635eSWarner Losh
2200acc635eSWarner Losh	More details can be found at
2210acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
2220acc635eSWarner Losh
2236e98a146SWarner Losh20001009:
2246e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
2256e98a146SWarner Losh	your entire ports tree, or you will have problems.
2266e98a146SWarner Losh
2276e98a146SWarner Losh20001006:
228685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
2296e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
2306e98a146SWarner Losh	/usr/bin/miniperl.
2316e98a146SWarner Losh
232073113a4SWarner Losh20001005:
233073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
234685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
235073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
236073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
237073113a4SWarner Losh	tree for anything to work.
238073113a4SWarner Losh
2390acc635eSWarner Losh20000928:
2400acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
2410acc635eSWarner Losh
242be3885b3SWarner Losh20000916:
243be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
244be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
245be3885b3SWarner Losh	same time as your kernel.
246be3885b3SWarner Losh
24776ec9675SWarner Losh20000914:
24876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
24976ec9675SWarner Losh	include the device will cause suspended laptops losing time
25076ec9675SWarner Losh	when they resume.  Include
25176ec9675SWarner Losh		device		pmtimer
25276ec9675SWarner Losh	in your config file and
25301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
25476ec9675SWarner Losh	to your /boot/device.hints file.
25576ec9675SWarner Losh
256f4865386SMark Murray20000911:
257f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
258f4865386SMark Murray	rather than an option. The supplied kernel config files have
259f4865386SMark Murray	been updated. You will need to do something similar in your
260f4865386SMark Murray	own kernel config file.
261f4865386SMark Murray	Remove:
262f4865386SMark Murray		options		RANDOMDEV
263f4865386SMark Murray	Add:
264f4865386SMark Murray		device		random
265f4865386SMark Murray	If you prefer to load the loadable module, you need to do
266f4865386SMark Murray	nothing.
267f4865386SMark Murray
268d594498fSWarner Losh20000909:
269d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
270d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
271d594498fSWarner Losh	reflect this if you load this module at boot time.
272d594498fSWarner Losh	The line should read:
273d594498fSWarner Losh		random_load="YES"
274d594498fSWarner Losh
2750deb7ddcSWarner Losh20000907:
2760deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
27716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
27816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
27916eb772dSWarner Losh	sure you don't have model loading problems which might at
28016eb772dSWarner Losh	first blush appear related to SMP.
28152bf24e7SWarner Losh
2825a01880bSWarner Losh20000906:
2835a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
2845a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
2855a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
2865a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
2875a01880bSWarner Losh	don't have one, and you have host.conf.
2885a01880bSWarner Losh
2892b41163cSWarner Losh20000905:
29038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
29138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
29238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
29338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
29438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
29538d6ecd2SWarner Losh
29638d6ecd2SWarner Losh20000905:
2978aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
2988aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
2998aab4bc7SWarner Losh	is /boot/kernel.
3008aab4bc7SWarner Losh
3018aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
30238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
30338d6ecd2SWarner Losh	installkernel/installworld dance.
3042b41163cSWarner Losh
305d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
306d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
307d594498fSWarner Losh	modules in that directory instead of finding them in the correct
308d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
309d594498fSWarner Losh	is that the linux module crashes your machine after the update.
310d594498fSWarner Losh
311d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
312d594498fSWarner Losh		mv /modules.old /boot/kernel.old
313d594498fSWarner Losh		chflags noschg /kernel.old
314d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
315d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
316d594498fSWarner Losh	fi
317d594498fSWarner Losh
318c22a309cSWarner Losh20000904:
319c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
320c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
321c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
322c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
323c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
324c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
325c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
326c22a309cSWarner Losh	is not likely to be generated.
327c22a309cSWarner Losh
328fdb9f54dSWarner Losh20000825:
329fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
3309c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
3319c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
3329c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
3339c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
3349c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
3359c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
3369c1a7444SWarner Losh	kernel.
3379c1a7444SWarner Losh
3389c1a7444SWarner Losh20000821:
3399c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
3409c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
3419c1a7444SWarner Losh	/boot/loader.conf.
342fdb9f54dSWarner Losh
3438f250aa7SWarner Losh20000812:
3445da0d091SWarner Losh	suidperl is now always built and installed on the system, but
3455da0d091SWarner Losh	with permissions of 511.  If you have applications that use
3465da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
3475da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
3485da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
3495da0d091SWarner Losh	will fix this until the next build.
3505da0d091SWarner Losh
3515da0d091SWarner Losh20000812:
3528f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
3538f250aa7SWarner Losh	visible changes that may immediately affect your configuration
3548f250aa7SWarner Losh	include:
3558f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
3568f250aa7SWarner Losh	- newaliases limited to root and trusted users
3578f250aa7SWarner Losh	- MSA port (587) turned on by default
3588f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
3598f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
3608f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
3618f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
3628f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
3638f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
3648f250aa7SWarner Losh
36571c38472SWarner Losh20000810:
36671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
36771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
36871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
36971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
37071c38472SWarner Losh	specific use for it.
37171c38472SWarner Losh
37271c38472SWarner Losh20000729:
37371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
37471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
37571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
37671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
37771c38472SWarner Losh		# Enable network daemons for user convenience.
37871c38472SWarner Losh		inetd_enable="YES"
37971c38472SWarner Losh		portmap_enable="YES"
38071c38472SWarner Losh		sendmail_enable="YES"
38171c38472SWarner Losh
38271c38472SWarner Losh20000728:
38371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
38471c38472SWarner Losh	will need to change that to nullfs_load="YES".
38571c38472SWarner Losh
3861dece4a9SWarner Losh20000728:
3871dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
3881dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
3891dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
3901dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
3911dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
3921dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
3931dece4a9SWarner Losh	to /MYKERNEL.
3941dece4a9SWarner Losh
395409e887cSWarner Losh20000711:
396409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
397409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
398409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
399409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
400409e887cSWarner Losh	for details on potential problems that you might have and how
401409e887cSWarner Losh	to get around them.
402409e887cSWarner Losh
403409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
404409e887cSWarner Losh	clauses above, you needn't worry.
405409e887cSWarner Losh
406409e887cSWarner Losh20000711:
407409e887cSWarner Losh	/etc/security has been updated to print the inode number of
408409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
409409e887cSWarner Losh	in the number of changed programs the first time when you run
410409e887cSWarner Losh	mergemaster to get a new /etc/security.
411409e887cSWarner Losh
412673d13f2SWarner Losh20000710:
413673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
414673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
415673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
416673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
417673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
418673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
419673d13f2SWarner Losh	errors. (see below, 20000624).
420673d13f2SWarner Losh
421bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
4221dece4a9SWarner Losh
423673d13f2SWarner Losh20000709:
424c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
425c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
426c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
427673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
428673d13f2SWarner Losh
429e98e26cdSWarner Losh20000706:
430e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
431e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
432e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
433f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
434e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
4352c021c6cSMark Ovens	interim if needed.
436e98e26cdSWarner Losh
437e98e26cdSWarner Losh20000705:
438e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
439e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
440e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
441e98e26cdSWarner Losh	details.
442e98e26cdSWarner Losh
443c373950eSWarner Losh20000704:
4442f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
4452f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
4462f961bc8SWarner Losh
4472f961bc8SWarner Losh20000704:
448c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
449c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
450c373950eSWarner Losh	rc.d scripts that haven't been updated.
451c373950eSWarner Losh
45227dc3a2bSWarner Losh20000630:
45327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
45427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
45527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
45627dc3a2bSWarner Losh
457b8c215acSWarner Losh20000625:
458b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
45927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
46027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
46127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
46227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
46327dc3a2bSWarner Losh	were required.  You should check with the latest collections
46427dc3a2bSWarner Losh	to make sure that these haven't changed.
465b8c215acSWarner Losh
4667b990719SWarner Losh20000624:
4677b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
4687b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
4697b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
4707b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
4717b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
4727b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
4737b990719SWarner Losh	date to the completion of the work.
4747b990719SWarner Losh
47527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
47627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
47727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
47827dc3a2bSWarner Losh	recreate the random and urandom devices.
47927dc3a2bSWarner Losh
48081e54c50SWarner Losh20000622:
48181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
48281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
48381e54c50SWarner Losh	that used to be required when updating.
48481e54c50SWarner Losh
48539943833SWarner Losh20000621:
4862c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
4872a2f33fbSDaniel Baker	the config file update procedure.
4882a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
489c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
490a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
49139943833SWarner Losh
492290f9ad8SWarner Losh20000620:
493290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
494290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
495290f9ad8SWarner Losh	that workaround will no longer be required.
496290f9ad8SWarner Losh
49790fb6346SWarner Losh20000615:
49890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
49990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
50090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
50190fb6346SWarner Losh	devices.
50290fb6346SWarner Losh
503f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
504f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
505f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
506f75f65bbSWarner Losh	may work).
507f75f65bbSWarner Losh
508ba26da8eSWarner Losh20000612:
509ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
510290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
511c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
512290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
513f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
514f54a3542SWarner Losh	NEWCARD for examples of the new format.
515290f9ad8SWarner Losh
516d65850ebSWarner Losh20000522:
517ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
518d65850ebSWarner Losh	building a kernel after this point is advised that they need
519d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
520d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
521d65850ebSWarner Losh
522d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
523d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
524d9583a00SWarner Losh	is recommended that you don't set this option until the problem
525d9583a00SWarner Losh	is resolved.
526d9583a00SWarner Losh
5278039cedeSWarner Losh20000513:
5288039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
5298039cedeSWarner Losh
530d65850ebSWarner Losh20000510:
5318039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
5328039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
5338039cedeSWarner Losh	is requires for the boot blocks to build properly.
5348039cedeSWarner Losh
5358039cedeSWarner Losh20000503:
5368039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
5378039cedeSWarner Losh	is now available.
5388039cedeSWarner Losh
539d65850ebSWarner Losh20000502:
540d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
541d65850ebSWarner Losh	connected to the kernel building instead.
542d65850ebSWarner Losh
543be149406SNik Clayton20000427:
5448039cedeSWarner Losh	You may need to build gperf
5458039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
5468039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
5478039cedeSWarner Losh	an option only in -current.
5488039cedeSWarner Losh
5492b8dd5f4SWarner Losh20000417:
5502b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
551f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
5522b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
5532b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
5542c021c6cSMark Ovens	before you reboot, you'll need to issue:
5552b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
5562b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
5572b8dd5f4SWarner Losh
5588d9f1945SWarner Losh20000320:
5592b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
5602b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
5612b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
5628d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
5632b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
5648d9f1945SWarner Losh
565f8ab1dd6SWarner Losh20000319:
566f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
567f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
568f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
569f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
570f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
571f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
572f8ab1dd6SWarner Losh
57319cada77SWarner Losh20000318:
574f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
57519cada77SWarner Losh	Large kernel changes are being committed and are in the
57619cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
57719cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
57819cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
57919cada77SWarner Losh	that you are loading are up to date.
580ba228352SWarner Losh
58119cada77SWarner Losh20000315:
5826d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
5836d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
5846d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
5856d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
5866d23c382SWarner Losh	boot.
5876d23c382SWarner Losh
5886d23c382SWarner Losh20000315:
58919cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
59019cada77SWarner Losh	to upgrade to 4.0 from 3.x.
59157199806SWarner Losh
592dc0dbf5cSWarner LoshCOMMON ITEMS:
593dc0dbf5cSWarner Losh
594a24eff53SWarner Losh	General Notes
595a24eff53SWarner Losh	-------------
596a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
597a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
598a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
599a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
600a24eff53SWarner Losh	or several minor releases, or when several months have passed
601a24eff53SWarner Losh	on the -current branch).
602a24eff53SWarner Losh
603dc0dbf5cSWarner Losh	To build a kernel
604dc0dbf5cSWarner Losh	-----------------
605ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
606f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
607ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
6081e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
6091e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
610dc0dbf5cSWarner Losh
611ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
612ba01eb20SWarner Losh	--------------------------------------------------------------
613ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
614ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
615ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
616ba01eb20SWarner Losh	make depend
617ba01eb20SWarner Losh	make
618ba01eb20SWarner Losh	make install
619ba01eb20SWarner Losh
620ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
621ba01eb20SWarner Losh
622ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
623ba01eb20SWarner Losh
624ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
625ba01eb20SWarner Losh	-----------------------------------------------------------
626759f0aefSWarner Losh	make world
627fdb9f54dSWarner Losh	Build a new kernel, see above.
628759f0aefSWarner Losh
6291dece4a9SWarner Losh	To upgrade from 4.x-stable to current
630ba26da8eSWarner Losh	-------------------------------------
631ba26da8eSWarner Losh	make buildworld
6321e159248SWarner Losh	make buildkernel KERNCONF=YOUR_KERNEL_HERE
6337595222aSWarner Losh	cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
6341e159248SWarner Losh	make installkernel KERNCONF=YOUR_KERNEL_HERE
635ee6e1fc3SWarner Losh	reboot in single user [3]
636ba26da8eSWarner Losh	make installworld
6377595222aSWarner Losh	mergemaster
638134d2e86SWarner Losh	[1]
639ba26da8eSWarner Losh	<reboot>
640ba26da8eSWarner Losh
641fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
642fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
643fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
644fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
645fdb9f54dSWarner Losh	the UPDATING entries.
646ba26da8eSWarner Losh
6471dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
6481dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
6491dece4a9SWarner Losh	your sources that you have read and understood all the recent
6501dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
6511dece4a9SWarner Losh	much fewer pitfalls.
6521dece4a9SWarner Losh
653134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
654134d2e86SWarner Losh	should disable them at this point so they don't crash your
655134d2e86SWarner Losh	system on reboot.
656134d2e86SWarner Losh
6579c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
6589c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
6599c1a7444SWarner Losh	configuration.
6609c1a7444SWarner Losh
661ee6e1fc3SWarner Losh	[3] From the bootblocks, boot -s, and then do
662ee6e1fc3SWarner Losh		fsck -p
663ee6e1fc3SWarner Losh		mount -u /
664ee6e1fc3SWarner Losh		mount -a
665ee6e1fc3SWarner Losh		cd /usr/src
666ee6e1fc3SWarner Losh		adjkerntz -i		# if COMS is wall time
667ee6e1fc3SWarner Losh
668dc0dbf5cSWarner LoshFORMAT:
669dc0dbf5cSWarner Losh
670f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
6711fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
672f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
673f8ab1dd6SWarner Loshprevious releases if your system is older than this.
6741fc1a0dcSWarner Losh
6753645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
6763645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
677f8c77507SWarner Losh
67897d92980SPeter Wemm$FreeBSD$
679