xref: /freebsd/UPDATING (revision 63c90c9e57ec865af6b4306f2cfbfe6b185d6599)
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
1163c90c9eSWarner Losh	dump wile 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
17de2bcc63SWarner Losh20001218:
18de2bcc63SWarner Losh	Linksys Fast Ethernet PCCARD cards supported by the ed driver
19de2bcc63SWarner Losh	now require the addition of flag 0x80000 to their config line
20de2bcc63SWarner Losh	in pccard.conf(5).  This flag is not optional.  These Linksys
21de2bcc63SWarner Losh	cards will not be recognized without it.
22de2bcc63SWarner Losh
23960773f7SWarner Losh20001205:
24960773f7SWarner Losh	Important new FreeBSD-version stuff: PAM support has been worked
25960773f7SWarner Losh	in, partially from the "Unix" OpenSSH version.  This requires
26960773f7SWarner Losh	adding the following in pam.conf:
27960773f7SWarner Losh
28960773f7SWarner Losh	sshd    auth    sufficient      pam_skey.so
29960773f7SWarner Losh	sshd    auth    required        pam_unix.so         try_first_pass
30960773f7SWarner Losh	sshd    session required        pam_permit.so
31960773f7SWarner Losh
320acc635eSWarner Losh20001031:
330acc635eSWarner Losh	cvs updated to 1.11.
340acc635eSWarner Losh
350acc635eSWarner Losh20001020:
360acc635eSWarner Losh	The random device needs more entropy, so you need to make sure
370acc635eSWarner Losh	that you've run mergemaster to get a /etc/rc which will seed
380acc635eSWarner Losh	/dev/random.  If you don't and the system hangs after ldconfig,
390acc635eSWarner Losh	then banging on the keyboard randomly until it unhangs is one
400acc635eSWarner Losh	workaround.
410acc635eSWarner Losh
420acc635eSWarner Losh20001010:
430acc635eSWarner Losh	****************************** WARNING ******************************
440acc635eSWarner Losh				Sendmail has been updated.
450acc635eSWarner Losh	****************************** WARNING ******************************
460acc635eSWarner Losh	o mail.local(8) is no longer installed as a set-user-id binary.
470acc635eSWarner Losh	o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
480acc635eSWarner Losh	  is set.
490acc635eSWarner Losh	o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
500acc635eSWarner Losh	  commands.
510acc635eSWarner Losh	o Now using sendmail's version of vacation(1).
520acc635eSWarner Losh	o The sendmail cf building tools (contrib/sendmail/cf) are installed
530acc635eSWarner Losh	  in /usr/share/sendmail/cf.
540acc635eSWarner Losh	o sendmail.cw changed to local-host-names
550acc635eSWarner Losh
560acc635eSWarner Losh	More details can be found at
570acc635eSWarner Losh		http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
580acc635eSWarner Losh
596e98a146SWarner Losh20001009:
606e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
616e98a146SWarner Losh	your entire ports tree, or you will have problems.
626e98a146SWarner Losh
636e98a146SWarner Losh20001006:
64685294e7SMark Ovens	The perl build procedure no longer installs miniperl, nor uses
656e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
666e98a146SWarner Losh	/usr/bin/miniperl.
676e98a146SWarner Losh
68073113a4SWarner Losh20001005:
69073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
70685294e7SMark Ovens	It will be in an inconsistent state until noted in the UPDATING
71073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
72073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
73073113a4SWarner Losh	tree for anything to work.
74073113a4SWarner Losh
750acc635eSWarner Losh20000928:
760acc635eSWarner Losh	There was a change in the passwd format.  Need more information.
770acc635eSWarner Losh
78be3885b3SWarner Losh20000916:
79be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
80be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
81be3885b3SWarner Losh	same time as your kernel.
82be3885b3SWarner Losh
8376ec9675SWarner Losh20000914:
8476ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
8576ec9675SWarner Losh	include the device will cause suspended laptops losing time
8676ec9675SWarner Losh	when they resume.  Include
8776ec9675SWarner Losh		device		pmtimer
8876ec9675SWarner Losh	in your config file and
8901b9a434SWarner Losh		hint.pmtimer.0.at="isa"
9076ec9675SWarner Losh	to your /boot/device.hints file.
9176ec9675SWarner Losh
92f4865386SMark Murray20000911:
93f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
94f4865386SMark Murray	rather than an option. The supplied kernel config files have
95f4865386SMark Murray	been updated. You will need to do something similar in your
96f4865386SMark Murray	own kernel config file.
97f4865386SMark Murray	Remove:
98f4865386SMark Murray		options		RANDOMDEV
99f4865386SMark Murray	Add:
100f4865386SMark Murray		device		random
101f4865386SMark Murray	If you prefer to load the loadable module, you need to do
102f4865386SMark Murray	nothing.
103f4865386SMark Murray
104d594498fSWarner Losh20000909:
105d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
106d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
107d594498fSWarner Losh	reflect this if you load this module at boot time.
108d594498fSWarner Losh	The line should read:
109d594498fSWarner Losh		random_load="YES"
110d594498fSWarner Losh
1110deb7ddcSWarner Losh20000907:
1120deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
11316eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
11416eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
11516eb772dSWarner Losh	sure you don't have model loading problems which might at
11616eb772dSWarner Losh	first blush appear related to SMP.
11752bf24e7SWarner Losh
1185a01880bSWarner Losh20000906:
1195a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
1205a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
1215a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
1225a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
1235a01880bSWarner Losh	don't have one, and you have host.conf.
1245a01880bSWarner Losh
1252b41163cSWarner Losh20000905:
12638d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
12738d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
12838d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
12938d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
13038d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
13138d6ecd2SWarner Losh
13238d6ecd2SWarner Losh20000905:
1338aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
1348aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
1358aab4bc7SWarner Losh	is /boot/kernel.
1368aab4bc7SWarner Losh
1378aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
13838d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
13938d6ecd2SWarner Losh	installkernel/installworld dance.
1402b41163cSWarner Losh
141d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
142d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
143d594498fSWarner Losh	modules in that directory instead of finding them in the correct
144d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
145d594498fSWarner Losh	is that the linux module crashes your machine after the update.
146d594498fSWarner Losh
147d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
148d594498fSWarner Losh		mv /modules.old /boot/kernel.old
149d594498fSWarner Losh		chflags noschg /kernel.old
150d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
151d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
152d594498fSWarner Losh	fi
153d594498fSWarner Losh
154c22a309cSWarner Losh20000904:
155c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
156c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
157c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
158c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
159c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
160c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
161c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
162c22a309cSWarner Losh	is not likely to be generated.
163c22a309cSWarner Losh
164fdb9f54dSWarner Losh20000825:
165fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
1669c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
1679c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
1689c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
1699c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
1709c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
1719c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
1729c1a7444SWarner Losh	kernel.
1739c1a7444SWarner Losh
1749c1a7444SWarner Losh20000821:
1759c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
1769c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
1779c1a7444SWarner Losh	/boot/loader.conf.
178fdb9f54dSWarner Losh
1798f250aa7SWarner Losh20000812:
1805da0d091SWarner Losh	suidperl is now always built and installed on the system, but
1815da0d091SWarner Losh	with permissions of 511.  If you have applications that use
1825da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
1835da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
1845da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
1855da0d091SWarner Losh	will fix this until the next build.
1865da0d091SWarner Losh
1875da0d091SWarner Losh20000812:
1888f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
1898f250aa7SWarner Losh	visible changes that may immediately affect your configuration
1908f250aa7SWarner Losh	include:
1918f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
1928f250aa7SWarner Losh	- newaliases limited to root and trusted users
1938f250aa7SWarner Losh	- MSA port (587) turned on by default
1948f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
1958f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1968f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
1978f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1988f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
1998f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
2008f250aa7SWarner Losh
20171c38472SWarner Losh20000810:
20271c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
20371c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
20471c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
20571c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
20671c38472SWarner Losh	specific use for it.
20771c38472SWarner Losh
20871c38472SWarner Losh20000729:
20971c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
21071c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
21171c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
21271c38472SWarner Losh	afterwards (unless the variables already are set, of course):
21371c38472SWarner Losh		# Enable network daemons for user convenience.
21471c38472SWarner Losh		inetd_enable="YES"
21571c38472SWarner Losh		portmap_enable="YES"
21671c38472SWarner Losh		sendmail_enable="YES"
21771c38472SWarner Losh
21871c38472SWarner Losh20000728:
21971c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
22071c38472SWarner Losh	will need to change that to nullfs_load="YES".
22171c38472SWarner Losh
2221dece4a9SWarner Losh20000728:
2231dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
2241dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
2251dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
2261dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
2271dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
2281dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
2291dece4a9SWarner Losh	to /MYKERNEL.
2301dece4a9SWarner Losh
231409e887cSWarner Losh20000711:
232409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
233409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
234409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
235409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
236409e887cSWarner Losh	for details on potential problems that you might have and how
237409e887cSWarner Losh	to get around them.
238409e887cSWarner Losh
239409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
240409e887cSWarner Losh	clauses above, you needn't worry.
241409e887cSWarner Losh
242409e887cSWarner Losh20000711:
243409e887cSWarner Losh	/etc/security has been updated to print the inode number of
244409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
245409e887cSWarner Losh	in the number of changed programs the first time when you run
246409e887cSWarner Losh	mergemaster to get a new /etc/security.
247409e887cSWarner Losh
248673d13f2SWarner Losh20000710:
249673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
250673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
251673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
252673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
253673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
254673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
255673d13f2SWarner Losh	errors. (see below, 20000624).
256673d13f2SWarner Losh
257bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
2581dece4a9SWarner Losh
259673d13f2SWarner Losh20000709:
260c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
261c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
262c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
263673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
264673d13f2SWarner Losh
265e98e26cdSWarner Losh20000706:
266e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
267e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
268e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
269f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
270e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
2712c021c6cSMark Ovens	interim if needed.
272e98e26cdSWarner Losh
273e98e26cdSWarner Losh20000705:
274e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
275e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
276e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
277e98e26cdSWarner Losh	details.
278e98e26cdSWarner Losh
279c373950eSWarner Losh20000704:
2802f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
2812f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
2822f961bc8SWarner Losh
2832f961bc8SWarner Losh20000704:
284c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
285c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
286c373950eSWarner Losh	rc.d scripts that haven't been updated.
287c373950eSWarner Losh
28827dc3a2bSWarner Losh20000630:
28927dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
29027dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
29127dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
29227dc3a2bSWarner Losh
293b8c215acSWarner Losh20000625:
294b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
29527dc3a2bSWarner Losh	system installed in order to build the system and kernel.
29627dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
29727dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
29827dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
29927dc3a2bSWarner Losh	were required.  You should check with the latest collections
30027dc3a2bSWarner Losh	to make sure that these haven't changed.
301b8c215acSWarner Losh
3027b990719SWarner Losh20000624:
3037b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
3047b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
3057b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
3067b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
3077b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
3087b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
3097b990719SWarner Losh	date to the completion of the work.
3107b990719SWarner Losh
31127dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
31227dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
31327dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
31427dc3a2bSWarner Losh	recreate the random and urandom devices.
31527dc3a2bSWarner Losh
31681e54c50SWarner Losh20000622:
31781e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
31881e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
31981e54c50SWarner Losh	that used to be required when updating.
32081e54c50SWarner Losh
32139943833SWarner Losh20000621:
3222c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
3232a2f33fbSDaniel Baker	the config file update procedure.
3242a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
325c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
326a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
32739943833SWarner Losh
328290f9ad8SWarner Losh20000620:
329290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
330290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
331290f9ad8SWarner Losh	that workaround will no longer be required.
332290f9ad8SWarner Losh
33390fb6346SWarner Losh20000615:
33490fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
33590fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
33690fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
33790fb6346SWarner Losh	devices.
33890fb6346SWarner Losh
339f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
340f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
341f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
342f75f65bbSWarner Losh	may work).
343f75f65bbSWarner Losh
344ba26da8eSWarner Losh20000612:
345ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
346290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
347c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
348290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
349f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
350f54a3542SWarner Losh	NEWCARD for examples of the new format.
351290f9ad8SWarner Losh
352d65850ebSWarner Losh20000522:
353ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
354d65850ebSWarner Losh	building a kernel after this point is advised that they need
355d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
356d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
357d65850ebSWarner Losh
358d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
359d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
360d9583a00SWarner Losh	is recommended that you don't set this option until the problem
361d9583a00SWarner Losh	is resolved.
362d9583a00SWarner Losh
3638039cedeSWarner Losh20000513:
3648039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
3658039cedeSWarner Losh
366d65850ebSWarner Losh20000510:
3678039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
3688039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
3698039cedeSWarner Losh	is requires for the boot blocks to build properly.
3708039cedeSWarner Losh
3718039cedeSWarner Losh20000503:
3728039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
3738039cedeSWarner Losh	is now available.
3748039cedeSWarner Losh
375d65850ebSWarner Losh20000502:
376d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
377d65850ebSWarner Losh	connected to the kernel building instead.
378d65850ebSWarner Losh
379be149406SNik Clayton20000427:
3808039cedeSWarner Losh	You may need to build gperf
3818039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
3828039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
3838039cedeSWarner Losh	an option only in -current.
3848039cedeSWarner Losh
3852b8dd5f4SWarner Losh20000417:
3862b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
387f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
3882b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
3892b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
3902c021c6cSMark Ovens	before you reboot, you'll need to issue:
3912b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
3922b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
3932b8dd5f4SWarner Losh
3948d9f1945SWarner Losh20000320:
3952b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
3962b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
3972b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
3988d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
3992b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
4008d9f1945SWarner Losh
401f8ab1dd6SWarner Losh20000319:
402f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
403f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
404f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
405f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
406f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
407f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
408f8ab1dd6SWarner Losh
40919cada77SWarner Losh20000318:
410f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
41119cada77SWarner Losh	Large kernel changes are being committed and are in the
41219cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
41319cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
41419cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
41519cada77SWarner Losh	that you are loading are up to date.
416ba228352SWarner Losh
41719cada77SWarner Losh20000315:
4186d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
4196d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
4206d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
4216d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
4226d23c382SWarner Losh	boot.
4236d23c382SWarner Losh
4246d23c382SWarner Losh20000315:
42519cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
42619cada77SWarner Losh	to upgrade to 4.0 from 3.x.
42757199806SWarner Losh
428dc0dbf5cSWarner LoshCOMMON ITEMS:
429dc0dbf5cSWarner Losh
430a24eff53SWarner Losh	General Notes
431a24eff53SWarner Losh	-------------
432a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
433a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
434a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
435a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
436a24eff53SWarner Losh	or several minor releases, or when several months have passed
437a24eff53SWarner Losh	on the -current branch).
438a24eff53SWarner Losh
439dc0dbf5cSWarner Losh	To build a kernel
440dc0dbf5cSWarner Losh	-----------------
441ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
442f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
443ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
444ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
445ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
446dc0dbf5cSWarner Losh
447ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
448ba01eb20SWarner Losh	--------------------------------------------------------------
449ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
450ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
451ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
452ba01eb20SWarner Losh	make depend
453ba01eb20SWarner Losh	make
454ba01eb20SWarner Losh	make install
455ba01eb20SWarner Losh
456ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
457ba01eb20SWarner Losh
458ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
459ba01eb20SWarner Losh
460ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
461ba01eb20SWarner Losh	-----------------------------------------------------------
462759f0aefSWarner Losh	make world
463fdb9f54dSWarner Losh	Build a new kernel, see above.
464759f0aefSWarner Losh
4651dece4a9SWarner Losh	To upgrade from 4.x-stable to current
466ba26da8eSWarner Losh	-------------------------------------
467ba26da8eSWarner Losh	make buildworld
468ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
4699c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
470ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
471ba26da8eSWarner Losh	make installworld
472134d2e86SWarner Losh	[1]
473ba26da8eSWarner Losh	<reboot>
474ba26da8eSWarner Losh
475fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
476fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
477fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
478fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
479fdb9f54dSWarner Losh	the UPDATING entries.
480ba26da8eSWarner Losh
4811dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
4821dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
4831dece4a9SWarner Losh	your sources that you have read and understood all the recent
4841dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
4851dece4a9SWarner Losh	much fewer pitfalls.
4861dece4a9SWarner Losh
487134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
488134d2e86SWarner Losh	should disable them at this point so they don't crash your
489134d2e86SWarner Losh	system on reboot.
490134d2e86SWarner Losh
4919c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
4929c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
4939c1a7444SWarner Losh	configuration.
4949c1a7444SWarner Losh
495dc0dbf5cSWarner LoshFORMAT:
496dc0dbf5cSWarner Losh
497f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
4981fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
499f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
500f8ab1dd6SWarner Loshprevious releases if your system is older than this.
5011fc1a0dcSWarner Losh
5023645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
5033645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
504f8c77507SWarner Losh
50597d92980SPeter Wemm$FreeBSD$
506