1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 7.x IS SLOW:
12 FreeBSD 7.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance.
25 The new trunk(4) driver has been renamed to lagg(4) as it better
26 reflects its purpose. ifconfig will need to be recompiled.
29 sendmail(8) has been updated to version 8.14.1. Mail filters
30 (aka, milters) compiled against the libmilter included in the
31 base operating system should be recompiled.
34 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
35 In order to use them one must agree to the respective LICENSE in
36 share/doc/legal and define legal.intel_<name>.license_ack=1 via
37 loader.conf(5) or kenv(1). Make sure to deinstall the now
38 deprecated modules from the respective firmware ports.
41 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
42 were removed from FreeBSD's libc. These originally came from INRIA
43 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
44 deprecated in previous releases.
45 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
46 replace it as a more portable (and re-entrant) API.
49 To support interrupt filtering a modification to the newbus API
50 has occurred, ABI was broken and __FreeBSD_version was bumped
51 to 700031. Please make sure that your kernel and modules are in
53 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
56 The IPv6 multicast forwarding code may now be loaded into GENERIC
57 kernels by loading the ip_mroute.ko module. This is built into the
58 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
59 set; see src.conf(5) for more information.
62 The output of netstat -r has changed. Without -n, we now only
63 print a "network name" without the prefix length if the network
64 address and mask exactly match a Class A/B/C network, and an entry
65 exists in the nsswitch "networks" map.
66 With -n, we print the full unabbreviated CIDR network prefix in
67 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
68 This change is in preparation for changes such as equal-cost
69 multipath, and to more generally assist operational deployment
70 of FreeBSD as a modern IPv4 router.
73 PIM has been turned on by default in the IPv4 multicast
74 routing code. The kernel option 'PIM' has now been removed.
75 PIM is now built by default if option 'MROUTING' is specified.
76 It may now be loaded into GENERIC kernels by loading the
80 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
81 has been removed. Its functionality may be achieved by explicitly
82 configuring gif(4) interfaces and using the 'phyint' keyword in
84 XORP does not support source-routed IPv4 multicast tunnels nor the
85 integrated IPIP tunneling, therefore it is not affected by this
86 change. The __FreeBSD_version macro has been bumped to 700030.
89 Support for PCI Message Signalled Interrupts has been
90 re-enabled in the bge driver, only for those chips which are
91 believed to support it properly. If there are any problems,
92 MSI can be disabled completely by setting the
93 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
97 Support for PCI Message Signalled Interrupts has been
98 disabled again in the bge driver. Many revisions of the
99 hardware fail to support it properly. Support can be
100 re-enabled by removing the #define of BGE_DISABLE_MSI in
101 "src/sys/dev/bge/if_bge.c".
104 Support for PCI Message Signalled Interrupts has been added
105 to the bge driver. If there are any problems, MSI can be
106 disabled completely by setting the 'hw.pci.enable_msi' and
107 'hw.pci.enable_msix' tunables to 0 in the loader.
110 The removal of several facets of the experimental Threading
111 system from the kernel means that the proc and thread structures
112 have changed quite a bit. I suggest all kernel modules that might
113 reference these structures be recompiled.. Especially the
117 Sound infrastructure has been updated with various fixes and
118 improvements. Most of the changes are pretty much transparent,
119 with exceptions of followings:
120 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
121 moved to their own dev sysctl nodes, for example:
122 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
123 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
124 own chardev in the form of "dsp%d.<function>%d", where <function>
125 is p = playback, r = record and v = virtual, respectively. Users
126 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
127 This does not affect those who are using "/dev/dsp".
130 The following binaries have been disconnected from the build:
131 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
132 and mount_std. The functionality of these programs has been
133 moved into the mount program. For example, to mount a devfs
134 filesystem, instead of using mount_devfs, use: "mount -t devfs".
135 This does not affect entries in /etc/fstab, since entries in
136 /etc/fstab are always processed with "mount -t fstype".
139 Support for PCI Message Signalled Interrupts on i386 and amd64
140 has been added to the kernel and various drivers will soon be
141 updated to use MSI when it is available. If there are any problems,
142 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
143 and 'hw.pci.enable_msix' tunables to 0 in the loader.
146 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
147 The lockmgr object layout has been changed as a result of having
148 a lock_object embedded in it. As a consequence all file system
149 kernel modules must be re-compiled. The mutex profiling man page
150 has not yet been updated to reflect this change.
153 KSE in the kernel has now been made optional and turned on by
154 default. Use 'nooption KSE' in your kernel config to turn it
155 off. All kernel modules *must* be recompiled after this change.
156 There-after, modules from a KSE kernel should be compatible with
157 modules from a NOKSE kernel due to the temporary padding fields
158 added to 'struct proc'.
161 mrouted and its utilities have been removed from the base system.
164 Some ioctl(2) command codes have changed. Full backward ABI
165 compatibility is provided if the "options COMPAT_FREEBSD6" is
166 present in the kernel configuration file. Make sure to add
167 this option to your kernel config file, or recompile X.Org
168 and the rest of ports; otherwise they may refuse to work.
171 tcpslice has been removed from the base system.
174 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
175 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
176 systat needs to be rebuilt.
179 libpcap updated to v0.9.4 and tcpdump to v3.9.4
182 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
183 for IPFIREWALL_FORWARD is now as it was before when it was first
184 committed and for years after. The behaviour is now ON.
187 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
188 Now it can decrypt files created from different architectures.
189 Unfortunately, it is no longer able to decrypt a cipher text
190 generated with an older version on 64 bit architectures.
191 If you have such a file, you need old utility to decrypt it.
194 The interface version of the i4b kernel part has changed. So
195 after updating the kernel sources and compiling a new kernel,
196 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
197 be rebuilt, and vice versa.
200 The XBOX kernel now defaults to the nfe(4) driver instead of
201 the nve(4) driver. Please update your configuration
205 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
206 PCnet family of NICs has been removed. The new le(4) driver serves
207 as an equivalent but cross-platform replacement with the pcn(4)
208 driver still providing performance-optimized support for the subset
209 of AMD Am79C971 PCnet-FAST and greater chips as before.
212 The machdep.* sysctls and the adjkerntz utility have been
213 modified a bit. The new adjkerntz utility uses the new
214 sysctl names and sysctlbyname() calls, so it may be impossible
215 to run an old /sbin/adjkerntz utility in single-user mode
216 with a new kernel. Replace the `adjkerntz -i' step before
217 `make installworld' with:
219 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
221 and proceed as usual with the rest of the installworld-stage
222 steps. Otherwise, you risk installing binaries with their
223 timestamp set several hours in the future, especially if
224 you are running with local time set to GMT+X hours.
227 The ip6fw utility has been removed. The behavior provided by
228 ip6fw has been in ipfw2 for a good while and the rc.d scripts
229 have been updated to deal with it. There are some rules that
230 might not migrate cleanly. Use rc.firewall6 as a template to
234 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
235 attachments have been removed. Make sure to configure scc(4)
236 on sparc64. Note also that by default puc(4) will use uart(4)
237 and not sio(4) for serial ports because interrupt handling has
238 been optimized for multi-port serial cards and only uart(4)
239 implements the interface to support it.
242 The scc(4) driver replaces puc(4) for Serial Communications
243 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
244 Z8530. On sparc64, it is advised to add scc(4) to the kernel
245 configuration to make sure that the serial ports remain
249 Most world/kernel related NO_* build options changed names.
250 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
251 after FreeBSD ports) and should be set in /etc/src.conf
252 (the src.conf(5) manpage is provided). Full backwards
253 compatibility is maintained for the time being though it's
254 highly recommended to start moving old options out of the
255 system-wide /etc/make.conf file into the new /etc/src.conf
256 while also properly renaming them. More conversions will
257 likely follow. Posting to current@:
259 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
262 The NETSMBCRYPTO kernel option has been retired because its
263 functionality is always included in NETSMB and smbfs.ko now.
266 The TDFX_LINUX kernel option was retired and replaced by the
267 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
268 kernel module. Loading it alone should suffice to get 3dfx support
269 for Linux apps because it will pull in 3dfx.ko and linux.ko through
273 The 'audit' group was added to support the new auditing functionality
274 in the base system. Be sure to follow the directions for updating,
275 including the requirement to run mergemaster -p.
278 The kernel ABI to file system modules was changed on i386.
279 Please make sure that your kernel and modules are in sync.
282 This actually occured some time ago, but installing the kernel
283 now also installs a bunch of symbol files for the kernel modules.
284 This increases the size of /boot/kernel to about 67Mbytes. You
285 will need twice this if you will eventually back this up to kernel.old
286 on your next install.
287 If you have a shortage of room in your root partition, you should add
288 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
289 to your /etc/make.conf.
292 libc's malloc implementation has been replaced. This change has the
293 potential to uncover application bugs that previously went unnoticed.
294 See the malloc(3) manual page for more details.
297 The generic netgraph(4) cookie has been changed. If you upgrade
298 kernel passing this point, you also need to upgrade userland
299 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
302 si(4)'s device files now contain the unit number.
303 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
306 The kernel ABI was mostly destroyed due to a change in the size
307 of struct lock_object which is nested in other structures such
308 as mutexes which are nested in all sorts of other structures.
309 Make sure your kernel and modules are in sync.
312 The page coloring algorithm in the VM subsystem was converted
313 from tuning with kernel options to autotuning. Please remove
314 any PQ_* option except PQ_NOOPT from your kernel config.
317 The net80211-related tools in the tools/tools/ath directory
318 have been moved to tools/tools/net80211 and renamed with a
319 "wlan" prefix. Scripts that use them should be adjusted
323 Scripts in the local_startup directories (as defined in
324 /etc/defaults/rc.conf) that have the new rc.d semantics will
325 now be run as part of the base system rcorder. If there are
326 errors or problems with one of these local scripts, it could
327 cause boot problems. If you encounter such problems, boot in
328 single user mode, remove that script from the */rc.d directory.
329 Please report the problem to the port's maintainer, and the
330 freebsd-ports@freebsd.org mailing list.
333 The nodev mount option was deprecated in RELENG_6 (where it
334 was a no-op), and is now unsupported. If you have nodev or dev listed
335 in /etc/fstab, remove it, otherwise it will result in a mount error.
338 ABI between ipfw(4) and ipfw(8) has been changed. You need
339 to rebuild ipfw(8) when rebuilding kernel.
342 rp(4)'s device files now contain the unit number.
343 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
346 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
347 Its /etc/rc.conf.d configuration file has been `ppp' from
348 the beginning, and hence there is no need to touch it.
351 Now most modules get their build-time options from the kernel
352 configuration file. A few modules still have fixed options
353 due to their non-conformant implementation, but they will be
354 corrected eventually. You may need to review the options of
355 the modules in use, explicitly specify the non-default options
356 in the kernel configuration file, and rebuild the kernel and
360 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
361 to turn polling(4) on your interfaces.
364 The old bridge(4) implementation was retired. The new
365 if_bridge(4) serves as a full functional replacement.
368 The ai_addrlen of a struct addrinfo was changed to a socklen_t
369 to conform to POSIX-2001. This change broke an ABI
370 compatibility on 64 bit architecture. You have to recompile
371 userland programs that use getaddrinfo(3) on 64 bit
375 RELENG_6 branched here.
378 The pccard_ifconfig rc.conf variable has been removed and a new
379 variable, ifconfig_DEFAULT has been introduced. Unlike
380 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
381 do not have ifconfig_ifn entries rather than just those in
382 removable_interfaces.
385 Some previous versions of PAM have permitted the use of
386 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
387 to third party PAM modules in /usr/local/lib. A change has been
388 made to require the use of absolute paths in order to avoid
389 ambiguity and dependence on library path configuration, which may
390 affect existing configurations.
393 Major changes to network interface API. All drivers must be
394 recompiled. Drivers not in the base system will need to be
395 updated to the new APIs.
398 Changes were made to kinfo_proc in sys/user.h. Please recompile
399 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
400 will not behave correctly.
402 The API and ABI for hwpmc(4) have changed with the addition
403 of sampling support. Please recompile lib/libpmc(3) and
404 usr.sbin/{pmcstat,pmccontrol}.
407 The OpenBSD dhclient was imported in place of the ISC dhclient
408 and the network interface configuration scripts were updated
409 accordingly. If you use DHCP to configure your interfaces, you
410 must now run devd. Also, DNS updating was lost so you will need
411 to find a workaround if you use this feature.
413 The '_dhcp' user was added to support the OpenBSD dhclient. Be
414 sure to run mergemaster -p (like you are supposed to do every time
418 if_bridge was added to the tree. This has changed struct ifnet.
419 Please recompile userland and all network related modules.
422 The n_net of a struct netent was changed to an uint32_t, and
423 1st argument of getnetbyaddr() was changed to an uint32_t, to
424 conform to POSIX-2001. These changes broke an ABI
425 compatibility on 64 bit architecture. With these changes,
426 shlib major of libpcap was bumped. You have to recompile
427 userland programs that use getnetbyaddr(3), getnetbyname(3),
428 getnetent(3) and/or libpcap on 64 bit architecture.
431 Kernel parsing of extra options on '#!' first lines of shell
432 scripts has changed. Lines with multiple options likely will
433 fail after this date. For full details, please see
434 http://people.freebsd.org/~gad/Updating-20050528.txt
437 The packet filter (pf) code has been updated to OpenBSD 3.7
438 Please note the changed anchor syntax and the fact that
439 authpf(8) now needs a mounted fdescfs(5) to function.
442 The NO_MIXED_MODE kernel option has been removed from the i386
443 amd64 platforms as its use has been superceded by the new local
444 APIC timer code. Any kernel config files containing this option
448 The on-disk format of LC_CTYPE files was changed to be machine
449 independent. Please make sure NOT to use NO_CLEAN buildworld
450 when crossing this point. Crossing this point also requires
451 recompile or reinstall of all locale depended packages.
454 The ifi_epoch member of struct if_data has been changed to
455 contain the uptime at which the interface was created or the
456 statistics zeroed rather then the wall clock time because
457 wallclock time may go backwards. This should have no impact
458 unless an snmp implementation is using this value (I know of
462 The acpi_perf and acpi_throttle drivers are now part of the
463 acpi(4) main module. They are no longer built separately.
466 The layout of struct image_params has changed. You have to
467 recompile all compatibility modules (linux, svr4, etc) for use
471 The p4tcc driver has been merged into cpufreq(4). This makes
472 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
473 compile in "device cpufreq" to restore this functionality.
476 The responsibility of recomputing the file system summary of
477 a SoftUpdates-enabled dirty volume has been transferred to the
478 background fsck. A rebuild of fsck(8) utility is recommended
479 if you have updated the kernel.
481 To get the old behavior (recompute file system summary at mount
482 time), you can set vfs.ffs.compute_summary_at_mount=1 before
483 mounting the new volume.
486 The cpufreq import is complete. As part of this, the sysctls for
487 acpi(4) throttling have been removed. The power_profile script
488 has been updated, so you can use performance/economy_cpu_freq in
489 rc.conf(5) to set AC on/offline cpu frequencies.
492 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
493 requires recompiling libnetgraph and userland netgraph utilities.
496 Support for abbreviated forms of a number of ipfw options is
497 now deprecated. Warnings are printed to stderr indicating the
498 correct full form when a match occurs. Some abbreviations may
499 be supported at a later date based on user feedback. To be
500 considered for support, abbreviations must be in use prior to
501 this commit and unlikely to be confused with current key words.
504 By a popular demand, a lot of NOFOO options were renamed
505 to NO_FOO (see bsd.compat.mk for a full list). The old
506 spellings are still supported, but will cause annoying
507 warnings on stderr. Make sure you upgrade properly (see
508 the COMMON ITEMS: section later in this file).
511 Auto-loading of ancillary wlan modules such as wlan_wep has
512 been temporarily disabled; you need to statically configure
513 the modules you need into your kernel or explicitly load them
514 prior to use. Specifically, if you intend to use WEP encryption
515 with an 802.11 device load/configure wlan_wep; if you want to
516 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
517 and wlan_xauth as required.
520 The behaviour of ppp(8) has changed slightly. If lqr is enabled
521 (``enable lqr''), older versions would revert to LCP ECHO mode on
522 negotiation failure. Now, ``enable echo'' is required for this
523 behaviour. The ppp version number has been bumped to 3.4.2 to
527 The wlan support has been updated to split the crypto support
528 into separate modules. For static WEP you must configure the
529 wlan_wep module in your system or build and install the module
530 in place where it can be loaded (the kernel will auto-load
531 the module when a wep key is configured).
534 The ath driver has been updated to split the tx rate control
535 algorithm into a separate module. You need to include either
536 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
539 Support for systems with an 80386 CPU has been removed. Please
540 use FreeBSD 5.x or earlier on systems with an 80386.
543 We have had a hack which would mount the root filesystem
544 R/W if the device were named 'md*'. As part of the vnode
545 work I'm doing I have had to remove this hack. People
546 building systems which use preloaded MD root filesystems
547 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
548 their /etc/rc scripts.
551 FreeBSD 5.3 shipped here.
554 The size of struct tcpcb has changed again due to the removal
555 of RFC1644 T/TCP. You have to recompile userland programs that
556 read kmem for tcp sockets directly (netstat, sockstat, etc.)
559 The size of struct tcpcb has changed. You have to recompile
560 userland programs that read kmem for tcp sockets directly
561 (netstat, sockstat, etc.)
564 RELENG_5 branched here. For older entries, please see updating
565 in the RELENG_5 branch.
571 Avoid using make -j when upgrading. From time to time in the
572 past there have been problems using -j with buildworld and/or
573 installworld. This is especially true when upgrading between
574 "distant" versions (eg one that cross a major release boundary
575 or several minor releases, or when several months have passed
576 on the -current branch).
578 Sometimes, obscure build problems are the result of environment
579 poisoning. This can happen because the make utility reads its
580 environment when searching for values for global variables.
581 To run your build attempts in an "environmental clean room",
582 prefix all make commands with 'env -i '. See the env(1) manual
583 page for more details.
585 When upgrading from one major version to another it is generally
586 best to upgrade to the latest code in the currently installed branch
587 first, then do an upgrade to the new branch. This is the best-tested
588 upgrade path, and has the highest probability of being successful.
589 Please try this approach before reporting problems with a major
594 If you are updating from a prior version of FreeBSD (even one just
595 a few days old), you should follow this procedure. It is the most
596 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
598 make kernel-toolchain
599 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
600 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
602 To test a kernel once
603 ---------------------
604 If you just want to boot a kernel once (because you are not sure
605 if it works, or if you want to boot a known bad kernel to provide
606 debugging information) run
607 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
608 nextboot -k testkernel
610 To just build a kernel when you know that it won't mess you up
611 --------------------------------------------------------------
612 This assumes you are already running a 5.X system. Replace
613 ${arch} with the architecture of your machine (e.g. "i386",
614 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
616 cd src/sys/${arch}/conf
617 config KERNEL_NAME_HERE
618 cd ../compile/KERNEL_NAME_HERE
623 If this fails, go to the "To build a kernel" section.
625 To rebuild everything and install it on the current system.
626 -----------------------------------------------------------
627 # Note: sometimes if you are running current you gotta do more than
628 # is listed here if you are upgrading from a really old current.
630 <make sure you have good level 0 dumps>
632 make kernel KERNCONF=YOUR_KERNEL_HERE
634 <reboot in single user> [3]
642 To cross-install current onto a separate partition
643 --------------------------------------------------
644 # In this approach we use a separate partition to hold
645 # current's root, 'usr', and 'var' directories. A partition
646 # holding "/", "/usr" and "/var" should be about 2GB in
649 <make sure you have good level 0 dumps>
652 make buildkernel KERNCONF=YOUR_KERNEL_HERE
653 <maybe newfs current's root partition>
654 <mount current's root partition on directory ${CURRENT_ROOT}>
655 make installworld DESTDIR=${CURRENT_ROOT}
656 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
657 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
658 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
659 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
660 <reboot into current>
661 <do a "native" rebuild/install as described in the previous section>
662 <maybe install compatibility libraries from src/lib/compat>
666 To upgrade in-place from 5.x-stable to current
667 ----------------------------------------------
668 <make sure you have good level 0 dumps>
670 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
672 <reboot in single user> [3]
679 Make sure that you've read the UPDATING file to understand the
680 tweaks to various things you need. At this point in the life
681 cycle of current, things change often and you are on your own
682 to cope. The defaults can also change, so please read ALL of
683 the UPDATING entries.
685 Also, if you are tracking -current, you must be subscribed to
686 freebsd-current@freebsd.org. Make sure that before you update
687 your sources that you have read and understood all the recent
688 messages there. If in doubt, please track -stable which has
691 [1] If you have third party modules, such as vmware, you
692 should disable them at this point so they don't crash your
695 [3] From the bootblocks, boot -s, and then do
700 adjkerntz -i # if CMOS is wall time
701 Also, when doing a major release upgrade, it is required that
702 you boot into single user mode to do the installworld.
704 [4] Note: This step is non-optional. Failure to do this step
705 can result in a significant reduction in the functionality of the
706 system. Attempting to do it by hand is not recommended and those
707 that pursue this avenue should read this file carefully, as well
708 as the archives of freebsd-current and freebsd-hackers mailing lists
709 for potential gotchas.
711 [5] Usually this step is a noop. However, from time to time
712 you may need to do this if you get unknown user in the following
713 step. It never hurts to do it all the time. You may need to
714 install a new mergemaster (cd src/usr.sbin/mergemaster && make
715 install) after the buildworld before this step if you last updated
716 from current before 20020224 or from -stable before 20020408.
718 [8] In order to have a kernel that can run the 4.x binaries
719 needed to do an installworld, you must include the COMPAT_FREEBSD4
720 option in your kernel. Failure to do so may leave you with a system
721 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
722 is required to run the 5.x binaries on more recent kernels.
724 Make sure that you merge any new devices from GENERIC since the
725 last time you updated your kernel config file.
727 [9] When checking out sources, you must include the -P flag to have
728 cvs prune empty directories.
730 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
731 "?=" instead of the "=" assignment operator, so that buildworld can
732 override the CPUTYPE if it needs to.
734 MAKEOBJDIRPREFIX must be defined in an environment variable, and
735 not on the command line, or in /etc/make.conf. buildworld will
736 warn if it is improperly defined.
739 This file contains a list, in reverse chronological order, of major
740 breakages in tracking -current. Not all things will be listed here,
741 and it only starts on October 16, 2004. Updating files can found in
742 previous releases if your system is older than this.
744 Copyright information:
746 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
748 Redistribution, publication, translation and use, with or without
749 modification, in full or in part, in any form or format of this
750 document are permitted without further permission from the author.
752 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
753 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
754 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
755 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
756 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
757 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
758 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
759 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
760 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
761 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
762 POSSIBILITY OF SUCH DAMAGE.
764 If you find this document useful, and you want to, you may buy the
767 Contact Warner Losh if you have any questions about your use of