xref: /freebsd/UPDATING (revision f4865386bcae4c0d910d76b5dcd0e94ceca559dc)
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
8f4865386SMark Murray20000911:
9f4865386SMark Murray	The random device has been turned into a (pseudo-)device,
10f4865386SMark Murray	rather than an option. The supplied kernel config files have
11f4865386SMark Murray	been updated. You will need to do something similar in your
12f4865386SMark Murray	own kernel config file.
13f4865386SMark Murray	Remove:
14f4865386SMark Murray		options		RANDOMDEV
15f4865386SMark Murray	Add:
16f4865386SMark Murray		device		random
17f4865386SMark Murray	If you prefer to load the loadable module, you need to do
18f4865386SMark Murray	nothing.
19f4865386SMark Murray
20d594498fSWarner Losh20000909:
21d594498fSWarner Losh	The random device module has been renamed from randomdev.ko to
22d594498fSWarner Losh	random.ko. You will need to edit your /boot/loader.conf to
23d594498fSWarner Losh	reflect this if you load this module at boot time.
24d594498fSWarner Losh	The line should read:
25d594498fSWarner Losh		random_load="YES"
26d594498fSWarner Losh
270deb7ddcSWarner Losh20000907:
280deb7ddcSWarner Losh	The SMPNG commit has happened.  It should work, but if it
2916eb772dSWarner Losh	doesn't, fallback to the PRE_SMPNG CVS tag.  There are likely
3016eb772dSWarner Losh	to be a variety of minor issues.  Please see 20000905 to make
3116eb772dSWarner Losh	sure you don't have model loading problems which might at
3216eb772dSWarner Losh	first blush appear related to SMP.
3352bf24e7SWarner Losh
345a01880bSWarner Losh20000906:
355a01880bSWarner Losh	nsswitch has been imported from NetBSD.  Among other things,
365a01880bSWarner Losh	this means that /etc/host.conf is no longer used.  See
375a01880bSWarner Losh	nsswitch.conf(5) instead.  Note that at boot time rc.network
385a01880bSWarner Losh	will attempt to produce a new nsswitch.conf file for you if you
395a01880bSWarner Losh	don't have one, and you have host.conf.
405a01880bSWarner Losh
412b41163cSWarner Losh20000905:
428aab4bc7SWarner Losh	The boot loader has been updated.  The new default kernel is
438aab4bc7SWarner Losh	now /boot/kernel/kernel.ko.  The new default module location
448aab4bc7SWarner Losh	is /boot/kernel.
458aab4bc7SWarner Losh
468aab4bc7SWarner Losh	You *MUST* upgrade your boot loader and kernel at the same time.
472b41163cSWarner Losh
48d594498fSWarner Losh	Furthermore, you are urged to delete your old /modules directory
49d594498fSWarner Losh	before booting the new kernel, since kldload will find stale
50d594498fSWarner Losh	modules in that directory instead of finding them in the correct
51d594498fSWarner Losh	path, /boot/kernel.  The most common complaint that this cures
52d594498fSWarner Losh	is that the linux module crashes your machine after the update.
53d594498fSWarner Losh
54d594498fSWarner Losh	if [ ! -d /boot/kernel.old ]; then
55d594498fSWarner Losh		mv /modules.old /boot/kernel.old
56d594498fSWarner Losh		chflags noschg /kernel.old
57d594498fSWarner Losh		mv /kernel.old /boot/kernel.old/kernel.ko
58d594498fSWarner Losh		chflags schg /boot/kernel.old/kernel.ko
59d594498fSWarner Losh	fi
60d594498fSWarner Losh
61c22a309cSWarner Losh20000904:
62c22a309cSWarner Losh	A new issue with the sendmail upgrade has come to light.
63c22a309cSWarner Losh	/etc/aliases has moved to /etc/mail/aliases.  Mergemaster will
64c22a309cSWarner Losh	incorrectly install the default aliases in /etc/mail rather than
65c22a309cSWarner Losh	move the old one from /etc.  So you'll need to manually move the
66c22a309cSWarner Losh	file, create a symbolic link, remove the old /etc/aliases.db and
67c22a309cSWarner Losh	run newaliases.  For safety sake, you should stop sendmail
68c22a309cSWarner Losh	while doing this and run the upgrade when locally sourced email
69c22a309cSWarner Losh	is not likely to be generated.
70c22a309cSWarner Losh
71fdb9f54dSWarner Losh20000825:
72fdb9f54dSWarner Losh	/boot/device.hints is now required for installkernel to
739c1a7444SWarner Losh	succeed.  You should copy GENERIC.hints for your architecture
749c1a7444SWarner Losh	into /boot/device.hints.  If and only if you compile hints
759c1a7444SWarner Losh	into your kernel, then this file may be empty.  Please note,
769c1a7444SWarner Losh	if you have an empty or missing /boot/device.hints file and
779c1a7444SWarner Losh	you neglected to compile hints into your kernel, no boot
789c1a7444SWarner Losh	messages will appear after the boot loader tries to start the
799c1a7444SWarner Losh	kernel.
809c1a7444SWarner Losh
819c1a7444SWarner Losh20000821:
829c1a7444SWarner Losh	If you do NOT have ``options RANDOMDEV'' in your kernel and
839c1a7444SWarner Losh	you DO want the random device then add randomdev_load="YES" to
849c1a7444SWarner Losh	/boot/loader.conf.
85fdb9f54dSWarner Losh
868f250aa7SWarner Losh20000812:
875da0d091SWarner Losh	suidperl is now always built and installed on the system, but
885da0d091SWarner Losh	with permissions of 511.  If you have applications that use
895da0d091SWarner Losh	this program, you are now required to add ENABLE_SUIDPERL=true
905da0d091SWarner Losh	to /etc/make.conf.  If you forget to do this,
915da0d091SWarner Losh		chmod 4511 /usr/bin/suidperl
925da0d091SWarner Losh	will fix this until the next build.
935da0d091SWarner Losh
945da0d091SWarner Losh20000812:
958f250aa7SWarner Losh	sendmail has been updated from 8.9.3 to 8.11.0.  Some of the more
968f250aa7SWarner Losh	visible changes that may immediately affect your configuration
978f250aa7SWarner Losh	include:
988f250aa7SWarner Losh	- New default file locations from src/contrib/sendmail/cf/README
998f250aa7SWarner Losh	- newaliases limited to root and trusted users
1008f250aa7SWarner Losh	- MSA port (587) turned on by default
1018f250aa7SWarner Losh	- New queue file naming system so can't go from 8.11 -> 8.9
1028f250aa7SWarner Losh	- FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1038f250aa7SWarner Losh	- FEATURE(`nullclient') is more full featured
1048f250aa7SWarner Losh	- FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1058f250aa7SWarner Losh	- mail.local FreeBSD-only -b option changed to -B
1068f250aa7SWarner Losh	- See src/contrib/sendmail/RELEASE_NOTES for more info
1078f250aa7SWarner Losh
10871c38472SWarner Losh20000810:
10971c38472SWarner Losh	suidperl (aka sperl) is no longer build by default.  You must
11071c38472SWarner Losh	specifically define BUILD_SUIDPERL to "true" for it to be build.
11171c38472SWarner Losh	Furthermore, we recommend that you remove /usr/bin/sperl* and
11271c38472SWarner Losh	/usr/bin/suidperl files from your system unless you have a
11371c38472SWarner Losh	specific use for it.
11471c38472SWarner Losh
11571c38472SWarner Losh20000729:
11671c38472SWarner Losh	Networking defaults have been tightened.  Anybody upgrading
11771c38472SWarner Losh	/etc/defaults/rc.conf needs to add the following lines to
11871c38472SWarner Losh	/etc/rc.conf if they want to have the same setup
11971c38472SWarner Losh	afterwards (unless the variables already are set, of course):
12071c38472SWarner Losh		# Enable network daemons for user convenience.
12171c38472SWarner Losh		inetd_enable="YES"
12271c38472SWarner Losh		portmap_enable="YES"
12371c38472SWarner Losh		sendmail_enable="YES"
12471c38472SWarner Losh
12571c38472SWarner Losh20000728:
12671c38472SWarner Losh	If you have null_load="YES" in your /boot/loader.conf, you
12771c38472SWarner Losh	will need to change that to nullfs_load="YES".
12871c38472SWarner Losh
1291dece4a9SWarner Losh20000728:
1301dece4a9SWarner Losh	The "installkernel" target has changed slightly. Now even if
1311dece4a9SWarner Losh	you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1321dece4a9SWarner Losh	it will install the MYKERNEL file (built with the buildkernel
1331dece4a9SWarner Losh	target) as /kernel rather than /MYKERNEL. Those who have
1341dece4a9SWarner Losh	updated their /boot/loader.conf files to point to /MYKERNEL
1351dece4a9SWarner Losh	should remove that entry or perform manual rename of /kernel
1361dece4a9SWarner Losh	to /MYKERNEL.
1371dece4a9SWarner Losh
138409e887cSWarner Losh20000711:
139409e887cSWarner Losh	If you use CVSUP or CTM to get CVS trees, AND you used to get
140409e887cSWarner Losh	the old crypto files from internat.freebsd.org AND you check
141409e887cSWarner Losh	out files from the CVS tree with the cvs command, please read
142409e887cSWarner Losh		http://people.freebsd.org/~imp/internat.txt
143409e887cSWarner Losh	for details on potential problems that you might have and how
144409e887cSWarner Losh	to get around them.
145409e887cSWarner Losh
146409e887cSWarner Losh	If you are merely a mirror, or don't answer yes to each of the
147409e887cSWarner Losh	clauses above, you needn't worry.
148409e887cSWarner Losh
149409e887cSWarner Losh20000711:
150409e887cSWarner Losh	/etc/security has been updated to print the inode number of
151409e887cSWarner Losh	setuid programs that have changed.  You will see a large spike
152409e887cSWarner Losh	in the number of changed programs the first time when you run
153409e887cSWarner Losh	mergemaster to get a new /etc/security.
154409e887cSWarner Losh
155673d13f2SWarner Losh20000710:
156673d13f2SWarner Losh	/dev/random now has good entropy collection (from the keyboard
157673d13f2SWarner Losh	and sysmouse drivers). Please ensure that either `options
158673d13f2SWarner Losh	RANDOMDEV' is present in your kernel config file or that
159673d13f2SWarner Losh	`randomdev_load="YES"' is in your /boot/loader.conf. If you do
160673d13f2SWarner Losh	not have the /dev/random driver, OpenSSL (and consequently
161673d13f2SWarner Losh	lots of crypto tools (like SSH)) will fail with strange
162673d13f2SWarner Losh	errors. (see below, 20000624).
163673d13f2SWarner Losh
164bed5c5ffSWarner Losh	FreeBSD-current is safe again to run Crypto.
1651dece4a9SWarner Losh
166673d13f2SWarner Losh20000709:
167c6dd1430SWarner Losh	phk made the malloc default options AJ.  This may slow things
168c6dd1430SWarner Losh	down and uncover other latent bugs in the code.  If you need to
169c6dd1430SWarner Losh	run at full speed, you can disable this by doing the following:
170673d13f2SWarner Losh		ln -s aj /etc/malloc.conf
171673d13f2SWarner Losh
172e98e26cdSWarner Losh20000706:
173e98e26cdSWarner Losh	libftpio's version was accidentally bumped a few days ago.  This
174e98e26cdSWarner Losh	has been corrected.  You may need to remove /usr/lib/libftpio.so.6
175e98e26cdSWarner Losh	before doing your next buildworld/installworld pair.  It certainly
176f699bbbbSMark Ovens	won't hurt to remove it before the update procedure.  It will
177e98e26cdSWarner Losh	break fetch until a new one is built, but ftp can be used in the
1782c021c6cSMark Ovens	interim if needed.
179e98e26cdSWarner Losh
180e98e26cdSWarner Losh20000705:
181e98e26cdSWarner Losh	The crypto packages have changed for the cvsup.  This has been done
182e98e26cdSWarner Losh	in a backward compatible way, but the old packages will go away at
183e98e26cdSWarner Losh	some point in the future.  Look at /usr/share/examples/cvsup for
184e98e26cdSWarner Losh	details.
185e98e26cdSWarner Losh
186c373950eSWarner Losh20000704:
1872f961bc8SWarner Losh	With the new sys/modules/sound/drivers/*, you will need to
1882f961bc8SWarner Losh	set SYSDIR until you do an installworld after July 7th.
1892f961bc8SWarner Losh
1902f961bc8SWarner Losh20000704:
191c373950eSWarner Losh	rc.shutdown and rc will now call the rc.d scripts with start
192c373950eSWarner Losh	or stop.  This may cause some harmless warnings from older
193c373950eSWarner Losh	rc.d scripts that haven't been updated.
194c373950eSWarner Losh
19527dc3a2bSWarner Losh20000630:
19627dc3a2bSWarner Losh	The libfetch based version of fetch has gone into the tree.
19727dc3a2bSWarner Losh	Minor problems may result on some of the less popular sites,
19827dc3a2bSWarner Losh	which should be reported to des@freebsd.org.
19927dc3a2bSWarner Losh
200b8c215acSWarner Losh20000625:
201b8c215acSWarner Losh	From approximately this date forward, one must have the crypto
20227dc3a2bSWarner Losh	system installed in order to build the system and kernel.
20327dc3a2bSWarner Losh	While not technically strictly true, one should treat it as
20427dc3a2bSWarner Losh	required and grab the crypto bits.  If you are grabbing CVS
20527dc3a2bSWarner Losh	trees, src-all and cvs-crypto should be treated as if they
20627dc3a2bSWarner Losh	were required.  You should check with the latest collections
20727dc3a2bSWarner Losh	to make sure that these haven't changed.
208b8c215acSWarner Losh
2097b990719SWarner Losh20000624:
2107b990719SWarner Losh	Mark Murray just committed the first parts of a cleanup of
2117b990719SWarner Losh	/dev/zero, et al.  This is also cleaning up /dev/random.
2127b990719SWarner Losh	The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
2137b990719SWarner Losh	-CURRENT FROM THIS POINT FORWARD for cryptographic services
2147b990719SWarner Losh	until Mark can merge in the fixes to this work in progress.
2157b990719SWarner Losh	openssh and openssl should not be used to generate keys from this
2167b990719SWarner Losh	date to the completion of the work.
2177b990719SWarner Losh
21827dc3a2bSWarner Losh	If you must operate at this reduced level of security, add '
21927dc3a2bSWarner Losh	options RANDOMDEV' to your kernel or modload the randomdev
22027dc3a2bSWarner Losh	module.  You may also need to copy a new MAKEDEV to /dev and
22127dc3a2bSWarner Losh	recreate the random and urandom devices.
22227dc3a2bSWarner Losh
22381e54c50SWarner Losh20000622:
22481e54c50SWarner Losh	The license on the softupdates is now a standard 2 clause
22581e54c50SWarner Losh	BSD license.  You may need to remove your symbolic links
22681e54c50SWarner Losh	that used to be required when updating.
22781e54c50SWarner Losh
22839943833SWarner Losh20000621:
2292c021c6cSMark Ovens	Scott Flatman <sf@aracnet.com> sent in a decent write-up on
2302a2f33fbSDaniel Baker	the config file update procedure.
2312a2f33fbSDaniel Baker		http://people.freebsd.org/~imp/config-upd.html
232c373950eSWarner Losh	NOTE: LINT is gone.  It has been replaced with NOTES.  NOTES
233a24eff53SWarner Losh	isn't buildable.  However, you can generate a LINT file.
23439943833SWarner Losh
235290f9ad8SWarner Losh20000620:
236290f9ad8SWarner Losh	Binutils 2.10 have hit the tree, or will shortly.  As soon
237290f9ad8SWarner Losh	as they do, the problem noted in 20000522 will be resolved and
238290f9ad8SWarner Losh	that workaround will no longer be required.
239290f9ad8SWarner Losh
24090fb6346SWarner Losh20000615:
24190fb6346SWarner Losh	phk removed the compatibility creation of wd devices in the
24290fb6346SWarner Losh	ad driver.  If you haven't done so already, you must update
24390fb6346SWarner Losh	your fstab, etc to use the ad devices instead of the wd
24490fb6346SWarner Losh	devices.
24590fb6346SWarner Losh
246f75f65bbSWarner Losh	In addition, you'll need to update your boot blocks to a
247f75f65bbSWarner Losh	more modern version, if you haven't already done so.  Modern
248f75f65bbSWarner Losh	here means 4.0 release or newer (although older releases
249f75f65bbSWarner Losh	may work).
250f75f65bbSWarner Losh
251ba26da8eSWarner Losh20000612:
252ba26da8eSWarner Losh	Peter took an axe to config(8).  Be sure that you read his mail
253290f9ad8SWarner Losh	on the topic before even thinking about updating.  You will
254c6dd1430SWarner Losh	need to create a /boot/device.hints or add a hints directive
255290f9ad8SWarner Losh	to your config file to compile them in statically.  The format
256f54a3542SWarner Losh	of the config file has changed as well.  Please see GENERIC or
257f54a3542SWarner Losh	NEWCARD for examples of the new format.
258290f9ad8SWarner Losh
259d65850ebSWarner Losh20000522:
260ba26da8eSWarner Losh	A new set of binutils went into the tree today.  Anybody
261d65850ebSWarner Losh	building a kernel after this point is advised that they need
262d65850ebSWarner Losh	to rebuild their binutils (or better yet do a
263d65850ebSWarner Losh	buildworld/installworld) before building a new kernel.
264d65850ebSWarner Losh
265d9583a00SWarner Losh	Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
266d9583a00SWarner Losh	or MALLOC_OPTIONS env var) J will cause ld to dump core.  It
267d9583a00SWarner Losh	is recommended that you don't set this option until the problem
268d9583a00SWarner Losh	is resolved.
269d9583a00SWarner Losh
2708039cedeSWarner Losh20000513:
2718039cedeSWarner Losh	The ethernet drivers were all updated to clean up the BPF handling.
2728039cedeSWarner Losh
273d65850ebSWarner Losh20000510:
2748039cedeSWarner Losh	The problems with boot blocks on the alphas have been corrected.
2758039cedeSWarner Losh	This will require some care in updating alphas.  A new libstand
2768039cedeSWarner Losh	is requires for the boot blocks to build properly.
2778039cedeSWarner Losh
2788039cedeSWarner Losh20000503:
2798039cedeSWarner Losh	Recompile all kld modules.  Proper version dependency info
2808039cedeSWarner Losh	is now available.
2818039cedeSWarner Losh
282d65850ebSWarner Losh20000502:
283d65850ebSWarner Losh	Modules have been disconnected from the buildworld tree and
284d65850ebSWarner Losh	connected to the kernel building instead.
285d65850ebSWarner Losh
2868039cedeSWarner Losh2000427:
2878039cedeSWarner Losh	You may need to build gperf
2888039cedeSWarner Losh		cd /usr/src/gnu/usr.bin/gperf && make depend all install
2898039cedeSWarner Losh	when upgrading from 4.0 -> current.  The build system now uses
2908039cedeSWarner Losh	an option only in -current.
2918039cedeSWarner Losh
2922b8dd5f4SWarner Losh20000417:
2932b8dd5f4SWarner Losh	The method that we brand ELF binaries has changed to be more
294f699bbbbSMark Ovens	acceptable to the binutils maintainers.  You will need to
2952b8dd5f4SWarner Losh	rebrand your ELF binaries that aren't native.  One problem
2962b8dd5f4SWarner Losh	binary is the Linux ldconfig.  After your make world, but
2972c021c6cSMark Ovens	before you reboot, you'll need to issue:
2982b8dd5f4SWarner Losh		brandelf -t Linux /compat/linux/sbin/ldconfig
2992b8dd5f4SWarner Losh	if you have Linux compatibility enabled on your machine.
3002b8dd5f4SWarner Losh
3018d9f1945SWarner Losh20000320:
3022b8dd5f4SWarner Losh	If you have really bad/marginal IDE drives, you may find they
3032b8dd5f4SWarner Losh	don't work well.  Use pio mode instead.  The easiest way to
3042b8dd5f4SWarner Losh	cope if you have a problem combination is to add:
3058d9f1945SWarner Losh		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
3062b8dd5f4SWarner Losh	to the start of /etc/rc.conf.
3078d9f1945SWarner Losh
308f8ab1dd6SWarner Losh20000319:
309f699bbbbSMark Ovens	The ISA and PCI compatibility shims have been connected to the
310f8ab1dd6SWarner Losh	options COMPAT_OLDISA and COMPAT_OLDPCI.  If you are using old
311f8ab1dd6SWarner Losh	style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
312f8ab1dd6SWarner Losh	include the appropriate option in your kernel config.  Drivers
313f8ab1dd6SWarner Losh	using the shims should be updated or they won't ship with
314f8ab1dd6SWarner Losh	5.0-RELEASE, targeted for 2001.
315f8ab1dd6SWarner Losh
31619cada77SWarner Losh20000318:
317f699bbbbSMark Ovens	We've entered the traditional post release dumping party.
31819cada77SWarner Losh	Large kernel changes are being committed and are in the
31919cada77SWarner Losh	works.  It is important to keep the systems' klds and kernel
32019cada77SWarner Losh	in sync as kernel interfaces and structures are changing.
32119cada77SWarner Losh	Before reporting kernel panics, make sure that all modules
32219cada77SWarner Losh	that you are loading are up to date.
323ba228352SWarner Losh
32419cada77SWarner Losh20000315:
3256d23c382SWarner Losh	If you are upgrading from an older version of FreeBSD, you
3266d23c382SWarner Losh	need to update your boot blocks as well.  'disklabel -B ad0'
3276d23c382SWarner Losh	will do the trick.  This isn't critical until you remove your
3286d23c382SWarner Losh	wd device entries in /dev, at which point your system will not
3296d23c382SWarner Losh	boot.
3306d23c382SWarner Losh
3316d23c382SWarner Losh20000315:
33219cada77SWarner Losh	4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
33319cada77SWarner Losh	to upgrade to 4.0 from 3.x.
33457199806SWarner Losh
335dc0dbf5cSWarner LoshCOMMON ITEMS:
336dc0dbf5cSWarner Losh
337a24eff53SWarner Losh	General Notes
338a24eff53SWarner Losh	-------------
339a24eff53SWarner Losh	Avoid using make -j when upgrading.  From time to time in the
340a24eff53SWarner Losh	past there have been problems using -j with buildworld and/or
341a24eff53SWarner Losh	installworld.  This is especially true when upgrading between
342a24eff53SWarner Losh	"distant" versions (eg one that cross a major release boundary
343a24eff53SWarner Losh	or several minor releases, or when several months have passed
344a24eff53SWarner Losh	on the -current branch).
345a24eff53SWarner Losh
346dc0dbf5cSWarner Losh	To build a kernel
347dc0dbf5cSWarner Losh	-----------------
348ba01eb20SWarner Losh	If you are updating from a prior version of FreeBSD (even one just
349f699bbbbSMark Ovens	a few days old), you should follow this procedure. With a
350ba01eb20SWarner Losh	/usr/obj tree with a fresh buildworld,
351ba01eb20SWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
352ba01eb20SWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
353dc0dbf5cSWarner Losh
354ba01eb20SWarner Losh	To just build a kernel when you know that it won't mess you up
355ba01eb20SWarner Losh	--------------------------------------------------------------
356ba01eb20SWarner Losh	cd src/sys/{i386,alpha}/conf
357ba01eb20SWarner Losh	config KERNEL_NAME_HERE			[1]
358ba01eb20SWarner Losh	cd ../../compile/KERNEL_NAME_HERE
359ba01eb20SWarner Losh	make depend
360ba01eb20SWarner Losh	make
361ba01eb20SWarner Losh	make install
362ba01eb20SWarner Losh
363ba01eb20SWarner Losh	[1] If in doubt, -r might help here.
364ba01eb20SWarner Losh
365ba01eb20SWarner Losh	If this fails, go to the "To build a kernel" section.
366ba01eb20SWarner Losh
367ba01eb20SWarner Losh	To rebuild everything and install it on the current system.
368ba01eb20SWarner Losh	-----------------------------------------------------------
369759f0aefSWarner Losh	make world
370fdb9f54dSWarner Losh	Build a new kernel, see above.
371759f0aefSWarner Losh
3721dece4a9SWarner Losh	To upgrade from 4.x-stable to current
373ba26da8eSWarner Losh	-------------------------------------
374ba26da8eSWarner Losh	make buildworld
375ba26da8eSWarner Losh	make buildkernel KERNEL=YOUR_KERNEL_HERE
3769c1a7444SWarner Losh	cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
377ba26da8eSWarner Losh	make installkernel KERNEL=YOUR_KERNEL_HERE
378ba26da8eSWarner Losh	make installworld
379134d2e86SWarner Losh	[1]
380ba26da8eSWarner Losh	<reboot>
381ba26da8eSWarner Losh
382fdb9f54dSWarner Losh	Make sure that you've read the UPDATING file to understand the
383fdb9f54dSWarner Losh	tweaks to various things you need.  At this point in the life
384fdb9f54dSWarner Losh	cycle of current, things change often and you are on your own
385fdb9f54dSWarner Losh	to cope.  The defaults can also change, so please read ALL of
386fdb9f54dSWarner Losh	the UPDATING entries.
387ba26da8eSWarner Losh
3881dece4a9SWarner Losh	Also, if you are tracking -current, you must be subscribed to
3891dece4a9SWarner Losh	freebsd-current@freebsd.org.  Make sure that before you update
3901dece4a9SWarner Losh	your sources that you have read and understood all the recent
3911dece4a9SWarner Losh	messages there.  If in doubt, please track -stable which has
3921dece4a9SWarner Losh	much fewer pitfalls.
3931dece4a9SWarner Losh
394134d2e86SWarner Losh	[1] If you have third party modules, such as vmware, you
395134d2e86SWarner Losh	should disable them at this point so they don't crash your
396134d2e86SWarner Losh	system on reboot.
397134d2e86SWarner Losh
3989c1a7444SWarner Losh	[2] If you have legacy ISA devices, you may need to create
3999c1a7444SWarner Losh	your own device.hints to reflect your unique hardware
4009c1a7444SWarner Losh	configuration.
4019c1a7444SWarner Losh
402dc0dbf5cSWarner LoshFORMAT:
403dc0dbf5cSWarner Losh
404f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major
4051fc1a0dcSWarner Loshbreakages in tracking -current.  Not all things will be listed here,
406f8ab1dd6SWarner Loshand it only starts on March 15, 2000.  Updating files can found in
407f8ab1dd6SWarner Loshprevious releases if your system is older than this.
4081fc1a0dcSWarner Losh
4093645fc1cSWarner LoshPlease filter your entries through Warner Losh (imp@village.org) so
4103645fc1cSWarner Loshthat the style, formatting, etc of this file can be maintained.
411f8c77507SWarner Losh
41297d92980SPeter Wemm$FreeBSD$
413