xref: /freebsd/UPDATING (revision 6e98a1467f95b3b4a4909283ffb31fa3d1edc929)
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
86e98a146SWarner Losh20001009:
96e98a146SWarner Losh	The ports tree's new layout is in place.  Be sure to update
106e98a146SWarner Losh	your entire ports tree, or you will have problems.
116e98a146SWarner Losh
126e98a146SWarner Losh20001006:
136e98a146SWarner Losh	The perl build proceedure no longer installs miniperl, nor uses
146e98a146SWarner Losh	the installed miniperl.  It is recommended that you delete
156e98a146SWarner Losh	/usr/bin/miniperl.
166e98a146SWarner Losh
17073113a4SWarner Losh20001005:
18073113a4SWarner Losh	This weekend the ports tree will be updated to a new layout.
19073113a4SWarner Losh	It will be in an inconsistant state until noted in the UPDATING
20073113a4SWarner Losh	file, or with asami-san's message to the relevant mailing
21073113a4SWarner Losh	lists.  With this new layout, you'll need to update the whole
22073113a4SWarner Losh	tree for anything to work.
23073113a4SWarner Losh
24be3885b3SWarner Losh20000916:
25be3885b3SWarner Losh	/boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
26be3885b3SWarner Losh	place.  Please update boot loader (not the boot blocks) at the
27be3885b3SWarner Losh	same time as your kernel.
28be3885b3SWarner Losh
2976ec9675SWarner Losh20000914:
3076ec9675SWarner Losh	The new pmtimer device is necessary for laptops.  Failure to
3176ec9675SWarner Losh	include the device will cause suspended laptops losing time
3276ec9675SWarner Losh	when they resume.  Include
3376ec9675SWarner Losh		device		pmtimer
3476ec9675SWarner Losh	in your config file and
3501b9a434SWarner Losh		hint.pmtimer.0.at="isa"
3676ec9675SWarner Losh	to your /boot/device.hints file.
3776ec9675SWarner Losh
38f4865386SMark Murray20000911:
39f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
40f4865386SMark Murray	rather than an option. The supplied kernel config files have
41f4865386SMark Murray	been updated. You will need to do something similar in your
42f4865386SMark Murray	own kernel config file.
43f4865386SMark Murray	Remove:
44f4865386SMark Murray		options		RANDOMDEV
45f4865386SMark Murray	Add:
46f4865386SMark Murray		device		random
47f4865386SMark Murray	If you prefer to load the loadable module, you need to do
48f4865386SMark Murray	nothing.
49f4865386SMark Murray
50d594498fSWarner Losh20000909:
51d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
52d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
53d594498fSWarner Losh	reflect this if you load this module at boot time.
54d594498fSWarner Losh	The line should read:
55d594498fSWarner Losh		random_load="YES"
56d594498fSWarner Losh
570deb7ddcSWarner Losh20000907:
580deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
5916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
6016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
6116eb772dSWarner Losh	sure you don't have model loading problems which might at
6216eb772dSWarner Losh	first blush appear related to SMP.
6352bf24e7SWarner Losh
645a01880bSWarner Losh20000906:
655a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
665a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
675a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
685a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
695a01880bSWarner Losh	don't have one, and you have host.conf.
705a01880bSWarner Losh
712b41163cSWarner Losh20000905:
7238d6ecd2SWarner Losh	The ucred structure changed size.  This breaks the interface
7338d6ecd2SWarner Losh	that mountd uses.  Trying to use an older mountd with a newer
7438d6ecd2SWarner Losh	kernel guarantees a panic.  This means that you need to use
7538d6ecd2SWarner Losh	kernels newer than today only with matching mountd, but you
7638d6ecd2SWarner Losh	needed to do that anyway with the boot loader changes.
7738d6ecd2SWarner Losh
7838d6ecd2SWarner Losh20000905:
798aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
808aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
818aab4bc7SWarner Losh	is /boot/kernel.
828aab4bc7SWarner Losh
838aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
8438d6ecd2SWarner Losh	The easiest way to do this is to do the buildworld/buildkernel/
8538d6ecd2SWarner Losh	installkernel/installworld dance.
862b41163cSWarner Losh
87d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
88d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
89d594498fSWarner Losh	modules in that directory instead of finding them in the correct
90d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
91d594498fSWarner Losh	is that the linux module crashes your machine after the update.
92d594498fSWarner Losh
93d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
94d594498fSWarner Losh		mv /modules.old /boot/kernel.old
95d594498fSWarner Losh		chflags noschg /kernel.old
96d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
97d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
98d594498fSWarner Losh	fi
99d594498fSWarner Losh
100c22a309cSWarner Losh20000904:
101c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
102c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
103c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
104c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
105c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
106c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
107c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
108c22a309cSWarner Losh	is not likely to be generated.
109c22a309cSWarner Losh
110fdb9f54dSWarner Losh20000825:
111fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
1129c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
1139c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
1149c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
1159c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
1169c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
1179c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
1189c1a7444SWarner Losh	kernel.
1199c1a7444SWarner Losh
1209c1a7444SWarner Losh20000821:
1219c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
1229c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
1239c1a7444SWarner Losh	/boot/loader.conf.
124fdb9f54dSWarner Losh
1258f250aa7SWarner Losh20000812:
1265da0d091SWarner Losh	suidperl is now always built and installed on the system, but
1275da0d091SWarner Losh	with permissions of 511.  If you have applications that use
1285da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
1295da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
1305da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
1315da0d091SWarner Losh	will fix this until the next build.
1325da0d091SWarner Losh
1335da0d091SWarner Losh20000812:
1348f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
1358f250aa7SWarner Losh	visible changes that may immediately affect your configuration
1368f250aa7SWarner Losh	include:
1378f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
1388f250aa7SWarner Losh	- newaliases limited to root and trusted users
1398f250aa7SWarner Losh	- MSA port (587) turned on by default
1408f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
1418f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1428f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
1438f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1448f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
1458f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
1468f250aa7SWarner Losh
14771c38472SWarner Losh20000810:
14871c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
14971c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
15071c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
15171c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
15271c38472SWarner Losh	specific use for it.
15371c38472SWarner Losh
15471c38472SWarner Losh20000729:
15571c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
15671c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
15771c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
15871c38472SWarner Losh	afterwards (unless the variables already are set, of course):
15971c38472SWarner Losh		# Enable network daemons for user convenience.
16071c38472SWarner Losh		inetd_enable="YES"
16171c38472SWarner Losh		portmap_enable="YES"
16271c38472SWarner Losh		sendmail_enable="YES"
16371c38472SWarner Losh
16471c38472SWarner Losh20000728:
16571c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
16671c38472SWarner Losh	will need to change that to nullfs_load="YES".
16771c38472SWarner Losh
1681dece4a9SWarner Losh20000728:
1691dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
1701dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1711dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
1721dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
1731dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
1741dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
1751dece4a9SWarner Losh	to /MYKERNEL.
1761dece4a9SWarner Losh
177409e887cSWarner Losh20000711:
178409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
179409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
180409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
181409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
182409e887cSWarner Losh	for details on potential problems that you might have and how
183409e887cSWarner Losh	to get around them.
184409e887cSWarner Losh
185409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
186409e887cSWarner Losh	clauses above, you needn't worry.
187409e887cSWarner Losh
188409e887cSWarner Losh20000711:
189409e887cSWarner Losh	/etc/security has been updated to print the inode number of
190409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
191409e887cSWarner Losh	in the number of changed programs the first time when you run
192409e887cSWarner Losh	mergemaster to get a new /etc/security.
193409e887cSWarner Losh
194673d13f2SWarner Losh20000710:
195673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
196673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
197673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
198673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
199673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
200673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
201673d13f2SWarner Losh	errors. (see below, 20000624).
202673d13f2SWarner Losh
203bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
2041dece4a9SWarner Losh
205673d13f2SWarner Losh20000709:
206c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
207c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
208c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
209673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
210673d13f2SWarner Losh
211e98e26cdSWarner Losh20000706:
212e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
213e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
214e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
215f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
216e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
2172c021c6cSMark Ovens	interim if needed.
218e98e26cdSWarner Losh
219e98e26cdSWarner Losh20000705:
220e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
221e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
222e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
223e98e26cdSWarner Losh	details.
224e98e26cdSWarner Losh
225c373950eSWarner Losh20000704:
2262f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
2272f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
2282f961bc8SWarner Losh
2292f961bc8SWarner Losh20000704:
230c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
231c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
232c373950eSWarner Losh	rc.d scripts that haven't been updated.
233c373950eSWarner Losh
23427dc3a2bSWarner Losh20000630:
23527dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
23627dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
23727dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
23827dc3a2bSWarner Losh
239b8c215acSWarner Losh20000625:
240b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
24127dc3a2bSWarner Losh	system installed in order to build the system and kernel.
24227dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
24327dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
24427dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
24527dc3a2bSWarner Losh	were required.  You should check with the latest collections
24627dc3a2bSWarner Losh	to make sure that these haven't changed.
247b8c215acSWarner Losh
2487b990719SWarner Losh20000624:
2497b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
2507b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
2517b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
2527b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
2537b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
2547b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
2557b990719SWarner Losh	date to the completion of the work.
2567b990719SWarner Losh
25727dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
25827dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
25927dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
26027dc3a2bSWarner Losh	recreate the random and urandom devices.
26127dc3a2bSWarner Losh
26281e54c50SWarner Losh20000622:
26381e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
26481e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
26581e54c50SWarner Losh	that used to be required when updating.
26681e54c50SWarner Losh
26739943833SWarner Losh20000621:
2682c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
2692a2f33fbSDaniel Baker	the config file update procedure.
2702a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
271c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
272a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
27339943833SWarner Losh
274290f9ad8SWarner Losh20000620:
275290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
276290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
277290f9ad8SWarner Losh	that workaround will no longer be required.
278290f9ad8SWarner Losh
27990fb6346SWarner Losh20000615:
28090fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
28190fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
28290fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
28390fb6346SWarner Losh	devices.
28490fb6346SWarner Losh
285f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
286f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
287f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
288f75f65bbSWarner Losh	may work).
289f75f65bbSWarner Losh
290ba26da8eSWarner Losh20000612:
291ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
292290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
293c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
294290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
295f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
296f54a3542SWarner Losh	NEWCARD for examples of the new format.
297290f9ad8SWarner Losh
298d65850ebSWarner Losh20000522:
299ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
300d65850ebSWarner Losh	building a kernel after this point is advised that they need
301d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
302d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
303d65850ebSWarner Losh
304d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
305d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
306d9583a00SWarner Losh	is recommended that you don't set this option until the problem
307d9583a00SWarner Losh	is resolved.
308d9583a00SWarner Losh
3098039cedeSWarner Losh20000513:
3108039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
3118039cedeSWarner Losh
312d65850ebSWarner Losh20000510:
3138039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
3148039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
3158039cedeSWarner Losh	is requires for the boot blocks to build properly.
3168039cedeSWarner Losh
3178039cedeSWarner Losh20000503:
3188039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
3198039cedeSWarner Losh	is now available.
3208039cedeSWarner Losh
321d65850ebSWarner Losh20000502:
322d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
323d65850ebSWarner Losh	connected to the kernel building instead.
324d65850ebSWarner Losh
3258039cedeSWarner Losh2000427:
3268039cedeSWarner Losh	You may need to build gperf
3278039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
3288039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
3298039cedeSWarner Losh	an option only in -current.
3308039cedeSWarner Losh
3312b8dd5f4SWarner Losh20000417:
3322b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
333f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
3342b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
3352b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
3362c021c6cSMark Ovens	before you reboot, you'll need to issue:
3372b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
3382b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
3392b8dd5f4SWarner Losh
3408d9f1945SWarner Losh20000320:
3412b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
3422b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
3432b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
3448d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
3452b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
3468d9f1945SWarner Losh
347f8ab1dd6SWarner Losh20000319:
348f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
349f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
350f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
351f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
352f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
353f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
354f8ab1dd6SWarner Losh
35519cada77SWarner Losh20000318:
356f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
35719cada77SWarner Losh	Large kernel changes are being committed and are in the
35819cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
35919cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
36019cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
36119cada77SWarner Losh	that you are loading are up to date.
362ba228352SWarner Losh
36319cada77SWarner Losh20000315:
3646d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
3656d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
3666d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
3676d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
3686d23c382SWarner Losh	boot.
3696d23c382SWarner Losh
3706d23c382SWarner Losh20000315:
37119cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
37219cada77SWarner Losh	to upgrade to 4.0 from 3.x.
37357199806SWarner Losh
374dc0dbf5cSWarner LoshCOMMON ITEMS:
375dc0dbf5cSWarner Losh
376a24eff53SWarner Losh	General Notes
377a24eff53SWarner Losh	-------------
378a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
379a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
380a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
381a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
382a24eff53SWarner Losh	or several minor releases, or when several months have passed
383a24eff53SWarner Losh	on the -current branch).
384a24eff53SWarner Losh
385dc0dbf5cSWarner Losh	To build a kernel
386dc0dbf5cSWarner Losh	-----------------
387ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
388f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
389ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
390ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
391ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
392dc0dbf5cSWarner Losh
393ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
394ba01eb20SWarner Losh	--------------------------------------------------------------
395ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
396ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
397ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
398ba01eb20SWarner Losh	make depend
399ba01eb20SWarner Losh	make
400ba01eb20SWarner Losh	make install
401ba01eb20SWarner Losh
402ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
403ba01eb20SWarner Losh
404ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
405ba01eb20SWarner Losh
406ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
407ba01eb20SWarner Losh	-----------------------------------------------------------
408759f0aefSWarner Losh	make world
409fdb9f54dSWarner Losh	Build a new kernel, see above.
410759f0aefSWarner Losh
4111dece4a9SWarner Losh	To upgrade from 4.x-stable to current
412ba26da8eSWarner Losh	-------------------------------------
413ba26da8eSWarner Losh	make buildworld
414ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
4159c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
416ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
417ba26da8eSWarner Losh	make installworld
418134d2e86SWarner Losh	[1]
419ba26da8eSWarner Losh	<reboot>
420ba26da8eSWarner Losh
421fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
422fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
423fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
424fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
425fdb9f54dSWarner Losh	the UPDATING entries.
426ba26da8eSWarner Losh
4271dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
4281dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
4291dece4a9SWarner Losh	your sources that you have read and understood all the recent
4301dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
4311dece4a9SWarner Losh	much fewer pitfalls.
4321dece4a9SWarner Losh
433134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
434134d2e86SWarner Losh	should disable them at this point so they don't crash your
435134d2e86SWarner Losh	system on reboot.
436134d2e86SWarner Losh
4379c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
4389c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
4399c1a7444SWarner Losh	configuration.
4409c1a7444SWarner Losh
441dc0dbf5cSWarner LoshFORMAT:
442dc0dbf5cSWarner Losh
443f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
4441fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
445f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
446f8ab1dd6SWarner Loshprevious releases if your system is older than this.
4471fc1a0dcSWarner Losh
4483645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
4493645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
450f8c77507SWarner Losh
45197d92980SPeter Wemm$FreeBSD$
452