xref: /freebsd/UPDATING (revision 5fd2a895baacde4ea52a6ad9a2e9cf5c1bcc8846)
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
863c90c9eSWarner Losh20010101:
963c90c9eSWarner Losh	ex and vi were broken by some changes to sys/queue.h.  If you
1063c90c9eSWarner Losh	have a bad vi, you will see make buildworld fail with a core
115fd2a895SWarner Losh	dump while building termcap.  You can work around this problem
1263c90c9eSWarner Losh	by adding -k to your make buildworld.  This will cause the
1363c90c9eSWarner Losh	build to complete and install a new vi.  Once that's done, you
1463c90c9eSWarner Losh	can rebuild again without the -k to pick up anything that
1563c90c9eSWarner Losh	might have been ignored by the -k option.
1663c90c9eSWarner Losh
175fd2a895SWarner Losh	Others have suggested that you can just rebuild libc if your
185fd2a895SWarner Losh	vi/ex is dynamically linked, but I've not received any reports
195fd2a895SWarner Losh	of this working.
205fd2a895SWarner Losh
21de2bcc63SWarner Losh20001218:
22de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
23de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
24de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
25de2bcc63SWarner Losh	cards will not be recognized without it.
26de2bcc63SWarner Losh
27960773f7SWarner Losh20001205:
28960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
29960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
30960773f7SWarner Losh	adding the following in pam.conf:
31960773f7SWarner Losh
32960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
33960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
34960773f7SWarner Losh	sshd    session required        pam_permit.so
35960773f7SWarner Losh
360acc635eSWarner Losh20001031:
370acc635eSWarner Losh	cvs updated to 1.11.
380acc635eSWarner Losh
390acc635eSWarner Losh20001020:
400acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
410acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
420acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
430acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
440acc635eSWarner Losh	workaround.
450acc635eSWarner Losh
460acc635eSWarner Losh20001010:
470acc635eSWarner Losh	****************************** WARNING ******************************
480acc635eSWarner Losh				Sendmail has been updated.
490acc635eSWarner Losh	****************************** WARNING ******************************
500acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
510acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
520acc635eSWarner Losh	  is set.
530acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
540acc635eSWarner Losh	  commands.
550acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
560acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
570acc635eSWarner Losh	  in /usr/share/sendmail/cf.
580acc635eSWarner Losh	o sendmail.cw changed to local-host-names
590acc635eSWarner Losh
600acc635eSWarner Losh	More details can be found at
610acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
620acc635eSWarner Losh
636e98a146SWarner Losh20001009:
646e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
656e98a146SWarner Losh	your entire ports tree, or you will have problems.
666e98a146SWarner Losh
676e98a146SWarner Losh20001006:
68685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
696e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
706e98a146SWarner Losh	/usr/bin/miniperl.
716e98a146SWarner Losh
72073113a4SWarner Losh20001005:
73073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
74685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
75073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
76073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
77073113a4SWarner Losh	tree for anything to work.
78073113a4SWarner Losh
790acc635eSWarner Losh20000928:
800acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
810acc635eSWarner Losh
82be3885b3SWarner Losh20000916:
83be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
84be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
85be3885b3SWarner Losh	same time as your kernel.
86be3885b3SWarner Losh
8776ec9675SWarner Losh20000914:
8876ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
8976ec9675SWarner Losh	include the device will cause suspended laptops losing time
9076ec9675SWarner Losh	when they resume.  Include
9176ec9675SWarner Losh		device		pmtimer
9276ec9675SWarner Losh	in your config file and
9301b9a434SWarner Losh		hint.pmtimer.0.at="isa"
9476ec9675SWarner Losh	to your /boot/device.hints file.
9576ec9675SWarner Losh
96f4865386SMark Murray20000911:
97f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
98f4865386SMark Murray	rather than an option. The supplied kernel config files have
99f4865386SMark Murray	been updated. You will need to do something similar in your
100f4865386SMark Murray	own kernel config file.
101f4865386SMark Murray	Remove:
102f4865386SMark Murray		options		RANDOMDEV
103f4865386SMark Murray	Add:
104f4865386SMark Murray		device		random
105f4865386SMark Murray	If you prefer to load the loadable module, you need to do
106f4865386SMark Murray	nothing.
107f4865386SMark Murray
108d594498fSWarner Losh20000909:
109d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
110d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
111d594498fSWarner Losh	reflect this if you load this module at boot time.
112d594498fSWarner Losh	The line should read:
113d594498fSWarner Losh		random_load="YES"
114d594498fSWarner Losh
1150deb7ddcSWarner Losh20000907:
1160deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
11716eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
11816eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
11916eb772dSWarner Losh	sure you don't have model loading problems which might at
12016eb772dSWarner Losh	first blush appear related to SMP.
12152bf24e7SWarner Losh
1225a01880bSWarner Losh20000906:
1235a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
1245a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
1255a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
1265a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
1275a01880bSWarner Losh	don't have one, and you have host.conf.
1285a01880bSWarner Losh
1292b41163cSWarner Losh20000905:
13038d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
13138d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
13238d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
13338d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
13438d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
13538d6ecd2SWarner Losh
13638d6ecd2SWarner Losh20000905:
1378aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
1388aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
1398aab4bc7SWarner Losh	is /boot/kernel.
1408aab4bc7SWarner Losh
1418aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
14238d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
14338d6ecd2SWarner Losh	installkernel/installworld dance.
1442b41163cSWarner Losh
145d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
146d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
147d594498fSWarner Losh	modules in that directory instead of finding them in the correct
148d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
149d594498fSWarner Losh	is that the linux module crashes your machine after the update.
150d594498fSWarner Losh
151d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
152d594498fSWarner Losh		mv /modules.old /boot/kernel.old
153d594498fSWarner Losh		chflags noschg /kernel.old
154d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
155d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
156d594498fSWarner Losh	fi
157d594498fSWarner Losh
158c22a309cSWarner Losh20000904:
159c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
160c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
161c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
162c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
163c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
164c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
165c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
166c22a309cSWarner Losh	is not likely to be generated.
167c22a309cSWarner Losh
168fdb9f54dSWarner Losh20000825:
169fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
1709c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
1719c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
1729c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
1739c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
1749c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
1759c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
1769c1a7444SWarner Losh	kernel.
1779c1a7444SWarner Losh
1789c1a7444SWarner Losh20000821:
1799c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
1809c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
1819c1a7444SWarner Losh	/boot/loader.conf.
182fdb9f54dSWarner Losh
1838f250aa7SWarner Losh20000812:
1845da0d091SWarner Losh	suidperl is now always built and installed on the system, but
1855da0d091SWarner Losh	with permissions of 511.  If you have applications that use
1865da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
1875da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
1885da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
1895da0d091SWarner Losh	will fix this until the next build.
1905da0d091SWarner Losh
1915da0d091SWarner Losh20000812:
1928f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
1938f250aa7SWarner Losh	visible changes that may immediately affect your configuration
1948f250aa7SWarner Losh	include:
1958f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
1968f250aa7SWarner Losh	- newaliases limited to root and trusted users
1978f250aa7SWarner Losh	- MSA port (587) turned on by default
1988f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
1998f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
2008f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
2018f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
2028f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
2038f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
2048f250aa7SWarner Losh
20571c38472SWarner Losh20000810:
20671c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
20771c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
20871c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
20971c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
21071c38472SWarner Losh	specific use for it.
21171c38472SWarner Losh
21271c38472SWarner Losh20000729:
21371c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
21471c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
21571c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
21671c38472SWarner Losh	afterwards (unless the variables already are set, of course):
21771c38472SWarner Losh		# Enable network daemons for user convenience.
21871c38472SWarner Losh		inetd_enable="YES"
21971c38472SWarner Losh		portmap_enable="YES"
22071c38472SWarner Losh		sendmail_enable="YES"
22171c38472SWarner Losh
22271c38472SWarner Losh20000728:
22371c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
22471c38472SWarner Losh	will need to change that to nullfs_load="YES".
22571c38472SWarner Losh
2261dece4a9SWarner Losh20000728:
2271dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
2281dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
2291dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
2301dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
2311dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
2321dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
2331dece4a9SWarner Losh	to /MYKERNEL.
2341dece4a9SWarner Losh
235409e887cSWarner Losh20000711:
236409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
237409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
238409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
239409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
240409e887cSWarner Losh	for details on potential problems that you might have and how
241409e887cSWarner Losh	to get around them.
242409e887cSWarner Losh
243409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
244409e887cSWarner Losh	clauses above, you needn't worry.
245409e887cSWarner Losh
246409e887cSWarner Losh20000711:
247409e887cSWarner Losh	/etc/security has been updated to print the inode number of
248409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
249409e887cSWarner Losh	in the number of changed programs the first time when you run
250409e887cSWarner Losh	mergemaster to get a new /etc/security.
251409e887cSWarner Losh
252673d13f2SWarner Losh20000710:
253673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
254673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
255673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
256673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
257673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
258673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
259673d13f2SWarner Losh	errors. (see below, 20000624).
260673d13f2SWarner Losh
261bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
2621dece4a9SWarner Losh
263673d13f2SWarner Losh20000709:
264c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
265c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
266c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
267673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
268673d13f2SWarner Losh
269e98e26cdSWarner Losh20000706:
270e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
271e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
272e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
273f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
274e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
2752c021c6cSMark Ovens	interim if needed.
276e98e26cdSWarner Losh
277e98e26cdSWarner Losh20000705:
278e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
279e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
280e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
281e98e26cdSWarner Losh	details.
282e98e26cdSWarner Losh
283c373950eSWarner Losh20000704:
2842f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
2852f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
2862f961bc8SWarner Losh
2872f961bc8SWarner Losh20000704:
288c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
289c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
290c373950eSWarner Losh	rc.d scripts that haven't been updated.
291c373950eSWarner Losh
29227dc3a2bSWarner Losh20000630:
29327dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
29427dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
29527dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
29627dc3a2bSWarner Losh
297b8c215acSWarner Losh20000625:
298b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
29927dc3a2bSWarner Losh	system installed in order to build the system and kernel.
30027dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
30127dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
30227dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
30327dc3a2bSWarner Losh	were required.  You should check with the latest collections
30427dc3a2bSWarner Losh	to make sure that these haven't changed.
305b8c215acSWarner Losh
3067b990719SWarner Losh20000624:
3077b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
3087b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
3097b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
3107b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
3117b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
3127b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
3137b990719SWarner Losh	date to the completion of the work.
3147b990719SWarner Losh
31527dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
31627dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
31727dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
31827dc3a2bSWarner Losh	recreate the random and urandom devices.
31927dc3a2bSWarner Losh
32081e54c50SWarner Losh20000622:
32181e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
32281e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
32381e54c50SWarner Losh	that used to be required when updating.
32481e54c50SWarner Losh
32539943833SWarner Losh20000621:
3262c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
3272a2f33fbSDaniel Baker	the config file update procedure.
3282a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
329c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
330a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
33139943833SWarner Losh
332290f9ad8SWarner Losh20000620:
333290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
334290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
335290f9ad8SWarner Losh	that workaround will no longer be required.
336290f9ad8SWarner Losh
33790fb6346SWarner Losh20000615:
33890fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
33990fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
34090fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
34190fb6346SWarner Losh	devices.
34290fb6346SWarner Losh
343f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
344f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
345f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
346f75f65bbSWarner Losh	may work).
347f75f65bbSWarner Losh
348ba26da8eSWarner Losh20000612:
349ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
350290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
351c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
352290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
353f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
354f54a3542SWarner Losh	NEWCARD for examples of the new format.
355290f9ad8SWarner Losh
356d65850ebSWarner Losh20000522:
357ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
358d65850ebSWarner Losh	building a kernel after this point is advised that they need
359d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
360d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
361d65850ebSWarner Losh
362d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
363d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
364d9583a00SWarner Losh	is recommended that you don't set this option until the problem
365d9583a00SWarner Losh	is resolved.
366d9583a00SWarner Losh
3678039cedeSWarner Losh20000513:
3688039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
3698039cedeSWarner Losh
370d65850ebSWarner Losh20000510:
3718039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
3728039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
3738039cedeSWarner Losh	is requires for the boot blocks to build properly.
3748039cedeSWarner Losh
3758039cedeSWarner Losh20000503:
3768039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
3778039cedeSWarner Losh	is now available.
3788039cedeSWarner Losh
379d65850ebSWarner Losh20000502:
380d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
381d65850ebSWarner Losh	connected to the kernel building instead.
382d65850ebSWarner Losh
383be149406SNik Clayton20000427:
3848039cedeSWarner Losh	You may need to build gperf
3858039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
3868039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
3878039cedeSWarner Losh	an option only in -current.
3888039cedeSWarner Losh
3892b8dd5f4SWarner Losh20000417:
3902b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
391f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
3922b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
3932b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
3942c021c6cSMark Ovens	before you reboot, you'll need to issue:
3952b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
3962b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
3972b8dd5f4SWarner Losh
3988d9f1945SWarner Losh20000320:
3992b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
4002b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
4012b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
4028d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
4032b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
4048d9f1945SWarner Losh
405f8ab1dd6SWarner Losh20000319:
406f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
407f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
408f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
409f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
410f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
411f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
412f8ab1dd6SWarner Losh
41319cada77SWarner Losh20000318:
414f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
41519cada77SWarner Losh	Large kernel changes are being committed and are in the
41619cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
41719cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
41819cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
41919cada77SWarner Losh	that you are loading are up to date.
420ba228352SWarner Losh
42119cada77SWarner Losh20000315:
4226d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
4236d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
4246d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
4256d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
4266d23c382SWarner Losh	boot.
4276d23c382SWarner Losh
4286d23c382SWarner Losh20000315:
42919cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
43019cada77SWarner Losh	to upgrade to 4.0 from 3.x.
43157199806SWarner Losh
432dc0dbf5cSWarner LoshCOMMON ITEMS:
433dc0dbf5cSWarner Losh
434a24eff53SWarner Losh	General Notes
435a24eff53SWarner Losh	-------------
436a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
437a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
438a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
439a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
440a24eff53SWarner Losh	or several minor releases, or when several months have passed
441a24eff53SWarner Losh	on the -current branch).
442a24eff53SWarner Losh
443dc0dbf5cSWarner Losh	To build a kernel
444dc0dbf5cSWarner Losh	-----------------
445ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
446f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
447ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
448ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
449ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
450dc0dbf5cSWarner Losh
451ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
452ba01eb20SWarner Losh	--------------------------------------------------------------
453ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
454ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
455ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
456ba01eb20SWarner Losh	make depend
457ba01eb20SWarner Losh	make
458ba01eb20SWarner Losh	make install
459ba01eb20SWarner Losh
460ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
461ba01eb20SWarner Losh
462ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
463ba01eb20SWarner Losh
464ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
465ba01eb20SWarner Losh	-----------------------------------------------------------
466759f0aefSWarner Losh	make world
467fdb9f54dSWarner Losh	Build a new kernel, see above.
468759f0aefSWarner Losh
4691dece4a9SWarner Losh	To upgrade from 4.x-stable to current
470ba26da8eSWarner Losh	-------------------------------------
471ba26da8eSWarner Losh	make buildworld
472ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
4739c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
474ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
475ba26da8eSWarner Losh	make installworld
476134d2e86SWarner Losh	[1]
477ba26da8eSWarner Losh	<reboot>
478ba26da8eSWarner Losh
479fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
480fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
481fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
482fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
483fdb9f54dSWarner Losh	the UPDATING entries.
484ba26da8eSWarner Losh
4851dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
4861dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
4871dece4a9SWarner Losh	your sources that you have read and understood all the recent
4881dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
4891dece4a9SWarner Losh	much fewer pitfalls.
4901dece4a9SWarner Losh
491134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
492134d2e86SWarner Losh	should disable them at this point so they don't crash your
493134d2e86SWarner Losh	system on reboot.
494134d2e86SWarner Losh
4959c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
4969c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
4979c1a7444SWarner Losh	configuration.
4989c1a7444SWarner Losh
499dc0dbf5cSWarner LoshFORMAT:
500dc0dbf5cSWarner Losh
501f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
5021fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
503f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
504f8ab1dd6SWarner Loshprevious releases if your system is older than this.
5051fc1a0dcSWarner Losh
5063645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
5073645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
508f8c77507SWarner Losh
50997d92980SPeter Wemm$FreeBSD$
510