xref: /freebsd/UPDATING (revision aac7dfeae8a517843cf113621d272c8531214aa9)
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
8aac7dfeaSWarner Losh20010116:
9aac7dfeaSWarner Losh	The kerrnel option I386_CPU is now mutually exclusive with the
10aac7dfeaSWarner Losh	other cpu types. If you have an i386 system, be sure that it
11aac7dfeaSWarner Losh	only had this line.  Remove it for all other configurations.
12aac7dfeaSWarner Losh
13aac7dfeaSWarner Losh20010110:
14aac7dfeaSWarner Losh	Changes to the kernel require it and burncd be in sync.
15aac7dfeaSWarner Losh
16aac7dfeaSWarner Losh20010102:
17aac7dfeaSWarner Losh	Everyone who has hw.sndunit set to something in
18aac7dfeaSWarner Losh	/etc/sysctl.conf, it is now hw.snd.unit.
19aac7dfeaSWarner Losh
2063c90c9eSWarner Losh20010101:
2163c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
2263c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
235fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
2463c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
2563c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
2663c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
2763c90c9eSWarner Losh	might have been ignored by the -k option.
2863c90c9eSWarner Losh
295fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
305fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
315fd2a895SWarner Losh	of this working.
325fd2a895SWarner Losh
33aac7dfeaSWarner Losh20001228:
34aac7dfeaSWarner Losh	There have been some changes to libcrypt in -current.  The
35aac7dfeaSWarner Losh	libscrypt/libdescrypt symlink sillyness is gone and the installed
36aac7dfeaSWarner Losh	libcrypt is fully functional.  Be aware of this.
37aac7dfeaSWarner Losh
38de2bcc63SWarner Losh20001218:
39de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
40de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
41de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
42de2bcc63SWarner Losh	cards will not be recognized without it.
43de2bcc63SWarner Losh
44960773f7SWarner Losh20001205:
45960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
46960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
47960773f7SWarner Losh	adding the following in pam.conf:
48960773f7SWarner Losh
49960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
50960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
51960773f7SWarner Losh	sshd    session required        pam_permit.so
52960773f7SWarner Losh
530acc635eSWarner Losh20001031:
540acc635eSWarner Losh	cvs updated to 1.11.
550acc635eSWarner Losh
560acc635eSWarner Losh20001020:
570acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
580acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
590acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
600acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
610acc635eSWarner Losh	workaround.
620acc635eSWarner Losh
630acc635eSWarner Losh20001010:
640acc635eSWarner Losh	****************************** WARNING ******************************
650acc635eSWarner Losh				Sendmail has been updated.
660acc635eSWarner Losh	****************************** WARNING ******************************
670acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
680acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
690acc635eSWarner Losh	  is set.
700acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
710acc635eSWarner Losh	  commands.
720acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
730acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
740acc635eSWarner Losh	  in /usr/share/sendmail/cf.
750acc635eSWarner Losh	o sendmail.cw changed to local-host-names
760acc635eSWarner Losh
770acc635eSWarner Losh	More details can be found at
780acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
790acc635eSWarner Losh
806e98a146SWarner Losh20001009:
816e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
826e98a146SWarner Losh	your entire ports tree, or you will have problems.
836e98a146SWarner Losh
846e98a146SWarner Losh20001006:
85685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
866e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
876e98a146SWarner Losh	/usr/bin/miniperl.
886e98a146SWarner Losh
89073113a4SWarner Losh20001005:
90073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
91685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
92073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
93073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
94073113a4SWarner Losh	tree for anything to work.
95073113a4SWarner Losh
960acc635eSWarner Losh20000928:
970acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
980acc635eSWarner Losh
99be3885b3SWarner Losh20000916:
100be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
101be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
102be3885b3SWarner Losh	same time as your kernel.
103be3885b3SWarner Losh
10476ec9675SWarner Losh20000914:
10576ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
10676ec9675SWarner Losh	include the device will cause suspended laptops losing time
10776ec9675SWarner Losh	when they resume.  Include
10876ec9675SWarner Losh		device		pmtimer
10976ec9675SWarner Losh	in your config file and
11001b9a434SWarner Losh		hint.pmtimer.0.at="isa"
11176ec9675SWarner Losh	to your /boot/device.hints file.
11276ec9675SWarner Losh
113f4865386SMark Murray20000911:
114f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
115f4865386SMark Murray	rather than an option. The supplied kernel config files have
116f4865386SMark Murray	been updated. You will need to do something similar in your
117f4865386SMark Murray	own kernel config file.
118f4865386SMark Murray	Remove:
119f4865386SMark Murray		options		RANDOMDEV
120f4865386SMark Murray	Add:
121f4865386SMark Murray		device		random
122f4865386SMark Murray	If you prefer to load the loadable module, you need to do
123f4865386SMark Murray	nothing.
124f4865386SMark Murray
125d594498fSWarner Losh20000909:
126d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
127d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
128d594498fSWarner Losh	reflect this if you load this module at boot time.
129d594498fSWarner Losh	The line should read:
130d594498fSWarner Losh		random_load="YES"
131d594498fSWarner Losh
1320deb7ddcSWarner Losh20000907:
1330deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
13416eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
13516eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
13616eb772dSWarner Losh	sure you don't have model loading problems which might at
13716eb772dSWarner Losh	first blush appear related to SMP.
13852bf24e7SWarner Losh
1395a01880bSWarner Losh20000906:
1405a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
1415a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
1425a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
1435a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
1445a01880bSWarner Losh	don't have one, and you have host.conf.
1455a01880bSWarner Losh
1462b41163cSWarner Losh20000905:
14738d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
14838d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
14938d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
15038d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
15138d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
15238d6ecd2SWarner Losh
15338d6ecd2SWarner Losh20000905:
1548aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
1558aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
1568aab4bc7SWarner Losh	is /boot/kernel.
1578aab4bc7SWarner Losh
1588aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
15938d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
16038d6ecd2SWarner Losh	installkernel/installworld dance.
1612b41163cSWarner Losh
162d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
163d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
164d594498fSWarner Losh	modules in that directory instead of finding them in the correct
165d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
166d594498fSWarner Losh	is that the linux module crashes your machine after the update.
167d594498fSWarner Losh
168d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
169d594498fSWarner Losh		mv /modules.old /boot/kernel.old
170d594498fSWarner Losh		chflags noschg /kernel.old
171d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
172d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
173d594498fSWarner Losh	fi
174d594498fSWarner Losh
175c22a309cSWarner Losh20000904:
176c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
177c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
178c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
179c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
180c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
181c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
182c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
183c22a309cSWarner Losh	is not likely to be generated.
184c22a309cSWarner Losh
185fdb9f54dSWarner Losh20000825:
186fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
1879c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
1889c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
1899c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
1909c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
1919c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
1929c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
1939c1a7444SWarner Losh	kernel.
1949c1a7444SWarner Losh
1959c1a7444SWarner Losh20000821:
1969c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
1979c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
1989c1a7444SWarner Losh	/boot/loader.conf.
199fdb9f54dSWarner Losh
2008f250aa7SWarner Losh20000812:
2015da0d091SWarner Losh	suidperl is now always built and installed on the system, but
2025da0d091SWarner Losh	with permissions of 511.  If you have applications that use
2035da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
2045da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
2055da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
2065da0d091SWarner Losh	will fix this until the next build.
2075da0d091SWarner Losh
2085da0d091SWarner Losh20000812:
2098f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
2108f250aa7SWarner Losh	visible changes that may immediately affect your configuration
2118f250aa7SWarner Losh	include:
2128f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
2138f250aa7SWarner Losh	- newaliases limited to root and trusted users
2148f250aa7SWarner Losh	- MSA port (587) turned on by default
2158f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
2168f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
2178f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
2188f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
2198f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
2208f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
2218f250aa7SWarner Losh
22271c38472SWarner Losh20000810:
22371c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
22471c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
22571c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
22671c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
22771c38472SWarner Losh	specific use for it.
22871c38472SWarner Losh
22971c38472SWarner Losh20000729:
23071c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
23171c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
23271c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
23371c38472SWarner Losh	afterwards (unless the variables already are set, of course):
23471c38472SWarner Losh		# Enable network daemons for user convenience.
23571c38472SWarner Losh		inetd_enable="YES"
23671c38472SWarner Losh		portmap_enable="YES"
23771c38472SWarner Losh		sendmail_enable="YES"
23871c38472SWarner Losh
23971c38472SWarner Losh20000728:
24071c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
24171c38472SWarner Losh	will need to change that to nullfs_load="YES".
24271c38472SWarner Losh
2431dece4a9SWarner Losh20000728:
2441dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
2451dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
2461dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
2471dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
2481dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
2491dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
2501dece4a9SWarner Losh	to /MYKERNEL.
2511dece4a9SWarner Losh
252409e887cSWarner Losh20000711:
253409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
254409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
255409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
256409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
257409e887cSWarner Losh	for details on potential problems that you might have and how
258409e887cSWarner Losh	to get around them.
259409e887cSWarner Losh
260409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
261409e887cSWarner Losh	clauses above, you needn't worry.
262409e887cSWarner Losh
263409e887cSWarner Losh20000711:
264409e887cSWarner Losh	/etc/security has been updated to print the inode number of
265409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
266409e887cSWarner Losh	in the number of changed programs the first time when you run
267409e887cSWarner Losh	mergemaster to get a new /etc/security.
268409e887cSWarner Losh
269673d13f2SWarner Losh20000710:
270673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
271673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
272673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
273673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
274673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
275673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
276673d13f2SWarner Losh	errors. (see below, 20000624).
277673d13f2SWarner Losh
278bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
2791dece4a9SWarner Losh
280673d13f2SWarner Losh20000709:
281c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
282c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
283c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
284673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
285673d13f2SWarner Losh
286e98e26cdSWarner Losh20000706:
287e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
288e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
289e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
290f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
291e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
2922c021c6cSMark Ovens	interim if needed.
293e98e26cdSWarner Losh
294e98e26cdSWarner Losh20000705:
295e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
296e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
297e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
298e98e26cdSWarner Losh	details.
299e98e26cdSWarner Losh
300c373950eSWarner Losh20000704:
3012f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
3022f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
3032f961bc8SWarner Losh
3042f961bc8SWarner Losh20000704:
305c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
306c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
307c373950eSWarner Losh	rc.d scripts that haven't been updated.
308c373950eSWarner Losh
30927dc3a2bSWarner Losh20000630:
31027dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
31127dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
31227dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
31327dc3a2bSWarner Losh
314b8c215acSWarner Losh20000625:
315b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
31627dc3a2bSWarner Losh	system installed in order to build the system and kernel.
31727dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
31827dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
31927dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
32027dc3a2bSWarner Losh	were required.  You should check with the latest collections
32127dc3a2bSWarner Losh	to make sure that these haven't changed.
322b8c215acSWarner Losh
3237b990719SWarner Losh20000624:
3247b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
3257b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
3267b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
3277b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
3287b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
3297b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
3307b990719SWarner Losh	date to the completion of the work.
3317b990719SWarner Losh
33227dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
33327dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
33427dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
33527dc3a2bSWarner Losh	recreate the random and urandom devices.
33627dc3a2bSWarner Losh
33781e54c50SWarner Losh20000622:
33881e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
33981e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
34081e54c50SWarner Losh	that used to be required when updating.
34181e54c50SWarner Losh
34239943833SWarner Losh20000621:
3432c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
3442a2f33fbSDaniel Baker	the config file update procedure.
3452a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
346c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
347a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
34839943833SWarner Losh
349290f9ad8SWarner Losh20000620:
350290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
351290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
352290f9ad8SWarner Losh	that workaround will no longer be required.
353290f9ad8SWarner Losh
35490fb6346SWarner Losh20000615:
35590fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
35690fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
35790fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
35890fb6346SWarner Losh	devices.
35990fb6346SWarner Losh
360f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
361f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
362f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
363f75f65bbSWarner Losh	may work).
364f75f65bbSWarner Losh
365ba26da8eSWarner Losh20000612:
366ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
367290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
368c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
369290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
370f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
371f54a3542SWarner Losh	NEWCARD for examples of the new format.
372290f9ad8SWarner Losh
373d65850ebSWarner Losh20000522:
374ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
375d65850ebSWarner Losh	building a kernel after this point is advised that they need
376d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
377d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
378d65850ebSWarner Losh
379d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
380d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
381d9583a00SWarner Losh	is recommended that you don't set this option until the problem
382d9583a00SWarner Losh	is resolved.
383d9583a00SWarner Losh
3848039cedeSWarner Losh20000513:
3858039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
3868039cedeSWarner Losh
387d65850ebSWarner Losh20000510:
3888039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
3898039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
3908039cedeSWarner Losh	is requires for the boot blocks to build properly.
3918039cedeSWarner Losh
3928039cedeSWarner Losh20000503:
3938039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
3948039cedeSWarner Losh	is now available.
3958039cedeSWarner Losh
396d65850ebSWarner Losh20000502:
397d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
398d65850ebSWarner Losh	connected to the kernel building instead.
399d65850ebSWarner Losh
400be149406SNik Clayton20000427:
4018039cedeSWarner Losh	You may need to build gperf
4028039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
4038039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
4048039cedeSWarner Losh	an option only in -current.
4058039cedeSWarner Losh
4062b8dd5f4SWarner Losh20000417:
4072b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
408f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
4092b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
4102b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
4112c021c6cSMark Ovens	before you reboot, you'll need to issue:
4122b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
4132b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
4142b8dd5f4SWarner Losh
4158d9f1945SWarner Losh20000320:
4162b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
4172b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
4182b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
4198d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
4202b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
4218d9f1945SWarner Losh
422f8ab1dd6SWarner Losh20000319:
423f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
424f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
425f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
426f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
427f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
428f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
429f8ab1dd6SWarner Losh
43019cada77SWarner Losh20000318:
431f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
43219cada77SWarner Losh	Large kernel changes are being committed and are in the
43319cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
43419cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
43519cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
43619cada77SWarner Losh	that you are loading are up to date.
437ba228352SWarner Losh
43819cada77SWarner Losh20000315:
4396d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
4406d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
4416d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
4426d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
4436d23c382SWarner Losh	boot.
4446d23c382SWarner Losh
4456d23c382SWarner Losh20000315:
44619cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
44719cada77SWarner Losh	to upgrade to 4.0 from 3.x.
44857199806SWarner Losh
449dc0dbf5cSWarner LoshCOMMON ITEMS:
450dc0dbf5cSWarner Losh
451a24eff53SWarner Losh	General Notes
452a24eff53SWarner Losh	-------------
453a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
454a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
455a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
456a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
457a24eff53SWarner Losh	or several minor releases, or when several months have passed
458a24eff53SWarner Losh	on the -current branch).
459a24eff53SWarner Losh
460dc0dbf5cSWarner Losh	To build a kernel
461dc0dbf5cSWarner Losh	-----------------
462ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
463f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
464ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
465ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
466ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
467dc0dbf5cSWarner Losh
468ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
469ba01eb20SWarner Losh	--------------------------------------------------------------
470ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
471ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
472ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
473ba01eb20SWarner Losh	make depend
474ba01eb20SWarner Losh	make
475ba01eb20SWarner Losh	make install
476ba01eb20SWarner Losh
477ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
478ba01eb20SWarner Losh
479ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
480ba01eb20SWarner Losh
481ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
482ba01eb20SWarner Losh	-----------------------------------------------------------
483759f0aefSWarner Losh	make world
484fdb9f54dSWarner Losh	Build a new kernel, see above.
485759f0aefSWarner Losh
4861dece4a9SWarner Losh	To upgrade from 4.x-stable to current
487ba26da8eSWarner Losh	-------------------------------------
488ba26da8eSWarner Losh	make buildworld
489ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
4909c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
491ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
492ba26da8eSWarner Losh	make installworld
493134d2e86SWarner Losh	[1]
494ba26da8eSWarner Losh	<reboot>
495ba26da8eSWarner Losh
496fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
497fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
498fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
499fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
500fdb9f54dSWarner Losh	the UPDATING entries.
501ba26da8eSWarner Losh
5021dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
5031dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
5041dece4a9SWarner Losh	your sources that you have read and understood all the recent
5051dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
5061dece4a9SWarner Losh	much fewer pitfalls.
5071dece4a9SWarner Losh
508134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
509134d2e86SWarner Losh	should disable them at this point so they don't crash your
510134d2e86SWarner Losh	system on reboot.
511134d2e86SWarner Losh
5129c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
5139c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
5149c1a7444SWarner Losh	configuration.
5159c1a7444SWarner Losh
516dc0dbf5cSWarner LoshFORMAT:
517dc0dbf5cSWarner Losh
518f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
5191fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
520f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
521f8ab1dd6SWarner Loshprevious releases if your system is older than this.
5221fc1a0dcSWarner Losh
5233645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
5243645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
525f8c77507SWarner Losh
52697d92980SPeter Wemm$FreeBSD$
527