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 name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
26 were removed from FreeBSD's libc. These originally came from INRIA
27 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
28 deprecated in previous releases.
29 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
30 replace it as a more portable (and re-entrant) API.
33 To support interrupt filtering a modification to the newbus API
34 has occurred, ABI was broken and __FreeBSD_version was bumped
35 to 700031. Please make sure that your kernel and modules are in
37 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
40 The IPv6 multicast forwarding code may now be loaded into GENERIC
41 kernels by loading the ip_mroute.ko module. This is built into the
42 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
43 set; see src.conf(5) for more information.
46 The following build error may appear when upgrading from an old
47 -current (usr.sbin/bsnmpd/modules/snmp_bridge, depend stage):
48 line 31: '(' expected at begin of node
49 context: " TruthValue ENUM (
51 If so, run "make install" in usr.sbin/bsnmpd/gensnmptree. (It
52 should probably be a build tool). In the same module, you may
54 ...snmp_bridge/bridge_sys.c:39:27:
55 net/bridgestp.h: No such file or directory
56 If so, run "cp src/sys/net/bridgestp.h /usr/include/net".
59 The output of netstat -r has changed. Without -n, we now only
60 print a "network name" without the prefix length if the network
61 address and mask exactly match a Class A/B/C network, and an entry
62 exists in the nsswitch "networks" map.
63 With -n, we print the full unabbreviated CIDR network prefix in
64 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
65 This change is in preparation for changes such as equal-cost
66 multipath, and to more generally assist operational deployment
67 of FreeBSD as a modern IPv4 router.
70 PIM has been turned on by default in the IPv4 multicast
71 routing code. The kernel option 'PIM' has now been removed.
72 PIM is now built by default if option 'MROUTING' is specified.
73 It may now be loaded into GENERIC kernels by loading the
77 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
78 has been removed. Its functionality may be achieved by explicitly
79 configuring gif(4) interfaces and using the 'phyint' keyword in
81 XORP does not support source-routed IPv4 multicast tunnels nor the
82 integrated IPIP tunneling, therefore it is not affected by this
83 change. The __FreeBSD_version macro has been bumped to 700030.
86 Support for PCI Message Signalled Interrupts has been
87 re-enabled in the bge driver, only for those chips which are
88 believed to support it properly. If there are any problems,
89 MSI can be disabled completely by setting the
90 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
94 Support for PCI Message Signalled Interrupts has been
95 disabled again in the bge driver. Many revisions of the
96 hardware fail to support it properly. Support can be
97 re-enabled by removing the #define of BGE_DISABLE_MSI in
98 "src/sys/dev/bge/if_bge.c".
101 Support for PCI Message Signalled Interrupts has been added
102 to the bge driver. If there are any problems, MSI can be
103 disabled completely by setting the 'hw.pci.enable_msi' and
104 'hw.pci.enable_msix' tunables to 0 in the loader.
107 The removal of several facets of the experimental Threading
108 system from the kernel means that the proc and thread structures
109 have changed quite a bit. I suggest all kernel modules that might
110 reference these structures be recompiled.. Especially the
114 Sound infrastructure has been updated with various fixes and
115 improvements. Most of the changes are pretty much transparent,
116 with exceptions of followings:
117 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
118 moved to their own dev sysctl nodes, for example:
119 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
120 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
121 own chardev in the form of "dsp%d.<function>%d", where <function>
122 is p = playback, r = record and v = virtual, respectively. Users
123 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
124 This does not affect those who are using "/dev/dsp".
127 The following binaries have been disconnected from the build:
128 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
129 and mount_std. The functionality of these programs has been
130 moved into the mount program. For example, to mount a devfs
131 filesystem, instead of using mount_devfs, use: "mount -t devfs".
132 This does not affect entries in /etc/fstab, since entries in
133 /etc/fstab are always processed with "mount -t fstype".
136 Support for PCI Message Signalled Interrupts on i386 and amd64
137 has been added to the kernel and various drivers will soon be
138 updated to use MSI when it is available. If there are any problems,
139 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
140 and 'hw.pci.enable_msix' tunables to 0 in the loader.
143 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
144 The lockmgr object layout has been changed as a result of having
145 a lock_object embedded in it. As a consequence all file system
146 kernel modules must be re-compiled. The mutex profiling man page
147 has not yet been updated to reflect this change.
150 KSE in the kernel has now been made optional and turned on by
151 default. Use 'nooption KSE' in your kernel config to turn it
152 off. All kernel modules *must* be recompiled after this change.
153 There-after, modules from a KSE kernel should be compatible with
154 modules from a NOKSE kernel due to the temporary padding fields
155 added to 'struct proc'.
158 mrouted and its utilities have been removed from the base system.
161 Some ioctl(2) command codes have changed. Full backward ABI
162 compatibility is provided if the "options COMPAT_FREEBSD6" is
163 present in the kernel configuration file. Make sure to add
164 this option to your kernel config file, or recompile X.Org
165 and the rest of ports; otherwise they may refuse to work.
168 tcpslice has been removed from the base system.
171 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
172 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
173 systat needs to be rebuilt.
176 libpcap updated to v0.9.4 and tcpdump to v3.9.4
179 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
180 for IPFIREWALL_FORWARD is now as it was before when it was first
181 committed and for years after. The behaviour is now ON.
184 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
185 Now it can decrypt files created from different architectures.
186 Unfortunately, it is no longer able to decrypt a cipher text
187 generated with an older version on 64 bit architectures.
188 If you have such a file, you need old utility to decrypt it.
191 The interface version of the i4b kernel part has changed. So
192 after updating the kernel sources and compiling a new kernel,
193 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
194 be rebuilt, and vice versa.
197 The XBOX kernel now defaults to the nfe(4) driver instead of
198 the nve(4) driver. Please update your configuration
202 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
203 PCnet family of NICs has been removed. The new le(4) driver serves
204 as an equivalent but cross-platform replacement with the pcn(4)
205 driver still providing performance-optimized support for the subset
206 of AMD Am79C971 PCnet-FAST and greater chips as before.
209 The machdep.* sysctls and the adjkerntz utility have been
210 modified a bit. The new adjkerntz utility uses the new
211 sysctl names and sysctlbyname() calls, so it may be impossible
212 to run an old /sbin/adjkerntz utility in single-user mode
213 with a new kernel. Replace the `adjkerntz -i' step before
214 `make installworld' with:
216 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
218 and proceed as usual with the rest of the installworld-stage
219 steps. Otherwise, you risk installing binaries with their
220 timestamp set several hours in the future, especially if
221 you are running with local time set to GMT+X hours.
224 The ip6fw utility has been removed. The behavior provided by
225 ip6fw has been in ipfw2 for a good while and the rc.d scripts
226 have been updated to deal with it. There are some rules that
227 might not migrate cleanly. Use rc.firewall6 as a template to
231 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
232 attachments have been removed. Make sure to configure scc(4)
233 on sparc64. Note also that by default puc(4) will use uart(4)
234 and not sio(4) for serial ports because interrupt handling has
235 been optimized for multi-port serial cards and only uart(4)
236 implements the interface to support it.
239 The scc(4) driver replaces puc(4) for Serial Communications
240 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
241 Z8530. On sparc64, it is advised to add scc(4) to the kernel
242 configuration to make sure that the serial ports remain
246 Most world/kernel related NO_* build options changed names.
247 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
248 after FreeBSD ports) and should be set in /etc/src.conf
249 (the src.conf(5) manpage is provided). Full backwards
250 compatibility is maintained for the time being though it's
251 highly recommended to start moving old options out of the
252 system-wide /etc/make.conf file into the new /etc/src.conf
253 while also properly renaming them. More conversions will
254 likely follow. Posting to current@:
256 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
259 The NETSMBCRYPTO kernel option has been retired because its
260 functionality is always included in NETSMB and smbfs.ko now.
263 The TDFX_LINUX kernel option was retired and replaced by the
264 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
265 kernel module. Loading it alone should suffice to get 3dfx support
266 for Linux apps because it will pull in 3dfx.ko and linux.ko through
270 The 'audit' group was added to support the new auditing functionality
271 in the base system. Be sure to follow the directions for updating,
272 including the requirement to run mergemaster -p.
275 The kernel ABI to file system modules was changed on i386.
276 Please make sure that your kernel and modules are in sync.
279 This actually occured some time ago, but installing the kernel
280 now also installs a bunch of symbol files for the kernel modules.
281 This increases the size of /boot/kernel to about 67Mbytes. You
282 will need twice this if you will eventually back this up to kernel.old
283 on your next install.
284 If you have a shortage of room in your root partition, you should add
285 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
286 to your /etc/make.conf.
289 libc's malloc implementation has been replaced. This change has the
290 potential to uncover application bugs that previously went unnoticed.
291 See the malloc(3) manual page for more details.
294 The generic netgraph(4) cookie has been changed. If you upgrade
295 kernel passing this point, you also need to upgrade userland
296 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
299 si(4)'s device files now contain the unit number.
300 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
303 The kernel ABI was mostly destroyed due to a change in the size
304 of struct lock_object which is nested in other structures such
305 as mutexes which are nested in all sorts of other structures.
306 Make sure your kernel and modules are in sync.
309 The page coloring algorithm in the VM subsystem was converted
310 from tuning with kernel options to autotuning. Please remove
311 any PQ_* option except PQ_NOOPT from your kernel config.
314 The net80211-related tools in the tools/tools/ath directory
315 have been moved to tools/tools/net80211 and renamed with a
316 "wlan" prefix. Scripts that use them should be adjusted
320 Scripts in the local_startup directories (as defined in
321 /etc/defaults/rc.conf) that have the new rc.d semantics will
322 now be run as part of the base system rcorder. If there are
323 errors or problems with one of these local scripts, it could
324 cause boot problems. If you encounter such problems, boot in
325 single user mode, remove that script from the */rc.d directory.
326 Please report the problem to the port's maintainer, and the
327 freebsd-ports@freebsd.org mailing list.
330 The nodev mount option was deprecated in RELENG_6 (where it
331 was a no-op), and is now unsupported. If you have nodev or dev listed
332 in /etc/fstab, remove it, otherwise it will result in a mount error.
335 ABI between ipfw(4) and ipfw(8) has been changed. You need
336 to rebuild ipfw(8) when rebuilding kernel.
339 rp(4)'s device files now contain the unit number.
340 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
343 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
344 Its /etc/rc.conf.d configuration file has been `ppp' from
345 the beginning, and hence there is no need to touch it.
348 Now most modules get their build-time options from the kernel
349 configuration file. A few modules still have fixed options
350 due to their non-conformant implementation, but they will be
351 corrected eventually. You may need to review the options of
352 the modules in use, explicitly specify the non-default options
353 in the kernel configuration file, and rebuild the kernel and
357 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
358 to turn polling(4) on your interfaces.
361 The old bridge(4) implementation was retired. The new
362 if_bridge(4) serves as a full functional replacement.
365 The ai_addrlen of a struct addrinfo was changed to a socklen_t
366 to conform to POSIX-2001. This change broke an ABI
367 compatibility on 64 bit architecture. You have to recompile
368 userland programs that use getaddrinfo(3) on 64 bit
372 RELENG_6 branched here.
375 The pccard_ifconfig rc.conf variable has been removed and a new
376 variable, ifconfig_DEFAULT has been introduced. Unlike
377 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
378 do not have ifconfig_ifn entries rather than just those in
379 removable_interfaces.
382 Some previous versions of PAM have permitted the use of
383 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
384 to third party PAM modules in /usr/local/lib. A change has been
385 made to require the use of absolute paths in order to avoid
386 ambiguity and dependence on library path configuration, which may
387 affect existing configurations.
390 Major changes to network interface API. All drivers must be
391 recompiled. Drivers not in the base system will need to be
392 updated to the new APIs.
395 Changes were made to kinfo_proc in sys/user.h. Please recompile
396 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
397 will not behave correctly.
399 The API and ABI for hwpmc(4) have changed with the addition
400 of sampling support. Please recompile lib/libpmc(3) and
401 usr.sbin/{pmcstat,pmccontrol}.
404 The OpenBSD dhclient was imported in place of the ISC dhclient
405 and the network interface configuration scripts were updated
406 accordingly. If you use DHCP to configure your interfaces, you
407 must now run devd. Also, DNS updating was lost so you will need
408 to find a workaround if you use this feature.
410 The '_dhcp' user was added to support the OpenBSD dhclient. Be
411 sure to run mergemaster -p (like you are supposed to do every time
415 if_bridge was added to the tree. This has changed struct ifnet.
416 Please recompile userland and all network related modules.
419 The n_net of a struct netent was changed to an uint32_t, and
420 1st argument of getnetbyaddr() was changed to an uint32_t, to
421 conform to POSIX-2001. These changes broke an ABI
422 compatibility on 64 bit architecture. With these changes,
423 shlib major of libpcap was bumped. You have to recompile
424 userland programs that use getnetbyaddr(3), getnetbyname(3),
425 getnetent(3) and/or libpcap on 64 bit architecture.
428 Kernel parsing of extra options on '#!' first lines of shell
429 scripts has changed. Lines with multiple options likely will
430 fail after this date. For full details, please see
431 http://people.freebsd.org/~gad/Updating-20050528.txt
434 The packet filter (pf) code has been updated to OpenBSD 3.7
435 Please note the changed anchor syntax and the fact that
436 authpf(8) now needs a mounted fdescfs(5) to function.
439 The NO_MIXED_MODE kernel option has been removed from the i386
440 amd64 platforms as its use has been superceded by the new local
441 APIC timer code. Any kernel config files containing this option
445 The on-disk format of LC_CTYPE files was changed to be machine
446 independent. Please make sure NOT to use NO_CLEAN buildworld
447 when crossing this point. Crossing this point also requires
448 recompile or reinstall of all locale depended packages.
451 The ifi_epoch member of struct if_data has been changed to
452 contain the uptime at which the interface was created or the
453 statistics zeroed rather then the wall clock time because
454 wallclock time may go backwards. This should have no impact
455 unless an snmp implementation is using this value (I know of
459 The acpi_perf and acpi_throttle drivers are now part of the
460 acpi(4) main module. They are no longer built separately.
463 The layout of struct image_params has changed. You have to
464 recompile all compatibility modules (linux, svr4, etc) for use
468 The p4tcc driver has been merged into cpufreq(4). This makes
469 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
470 compile in "device cpufreq" to restore this functionality.
473 The responsibility of recomputing the file system summary of
474 a SoftUpdates-enabled dirty volume has been transferred to the
475 background fsck. A rebuild of fsck(8) utility is recommended
476 if you have updated the kernel.
478 To get the old behavior (recompute file system summary at mount
479 time), you can set vfs.ffs.compute_summary_at_mount=1 before
480 mounting the new volume.
483 The cpufreq import is complete. As part of this, the sysctls for
484 acpi(4) throttling have been removed. The power_profile script
485 has been updated, so you can use performance/economy_cpu_freq in
486 rc.conf(5) to set AC on/offline cpu frequencies.
489 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
490 requires recompiling libnetgraph and userland netgraph utilities.
493 Support for abbreviated forms of a number of ipfw options is
494 now deprecated. Warnings are printed to stderr indicating the
495 correct full form when a match occurs. Some abbreviations may
496 be supported at a later date based on user feedback. To be
497 considered for support, abbreviations must be in use prior to
498 this commit and unlikely to be confused with current key words.
501 By a popular demand, a lot of NOFOO options were renamed
502 to NO_FOO (see bsd.compat.mk for a full list). The old
503 spellings are still supported, but will cause annoying
504 warnings on stderr. Make sure you upgrade properly (see
505 the COMMON ITEMS: section later in this file).
508 Auto-loading of ancillary wlan modules such as wlan_wep has
509 been temporarily disabled; you need to statically configure
510 the modules you need into your kernel or explicitly load them
511 prior to use. Specifically, if you intend to use WEP encryption
512 with an 802.11 device load/configure wlan_wep; if you want to
513 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
514 and wlan_xauth as required.
517 The behaviour of ppp(8) has changed slightly. If lqr is enabled
518 (``enable lqr''), older versions would revert to LCP ECHO mode on
519 negotiation failure. Now, ``enable echo'' is required for this
520 behaviour. The ppp version number has been bumped to 3.4.2 to
524 The wlan support has been updated to split the crypto support
525 into separate modules. For static WEP you must configure the
526 wlan_wep module in your system or build and install the module
527 in place where it can be loaded (the kernel will auto-load
528 the module when a wep key is configured).
531 The ath driver has been updated to split the tx rate control
532 algorithm into a separate module. You need to include either
533 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
536 Support for systems with an 80386 CPU has been removed. Please
537 use FreeBSD 5.x or earlier on systems with an 80386.
540 We have had a hack which would mount the root filesystem
541 R/W if the device were named 'md*'. As part of the vnode
542 work I'm doing I have had to remove this hack. People
543 building systems which use preloaded MD root filesystems
544 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
545 their /etc/rc scripts.
548 FreeBSD 5.3 shipped here.
551 The size of struct tcpcb has changed again due to the removal
552 of RFC1644 T/TCP. You have to recompile userland programs that
553 read kmem for tcp sockets directly (netstat, sockstat, etc.)
556 The size of struct tcpcb has changed. You have to recompile
557 userland programs that read kmem for tcp sockets directly
558 (netstat, sockstat, etc.)
561 RELENG_5 branched here. For older entries, please see updating
562 in the RELENG_5 branch.
568 Avoid using make -j when upgrading. From time to time in the
569 past there have been problems using -j with buildworld and/or
570 installworld. This is especially true when upgrading between
571 "distant" versions (eg one that cross a major release boundary
572 or several minor releases, or when several months have passed
573 on the -current branch).
575 Sometimes, obscure build problems are the result of environment
576 poisoning. This can happen because the make utility reads its
577 environment when searching for values for global variables.
578 To run your build attempts in an "environmental clean room",
579 prefix all make commands with 'env -i '. See the env(1) manual
580 page for more details.
582 When upgrading from one major version to another it is generally
583 best to upgrade to the latest code in the currently installed branch
584 first, then do an upgrade to the new branch. This is the best-tested
585 upgrade path, and has the highest probability of being successful.
586 Please try this approach before reporting problems with a major
591 If you are updating from a prior version of FreeBSD (even one just
592 a few days old), you should follow this procedure. It is the most
593 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
595 make kernel-toolchain
596 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
597 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
599 To test a kernel once
600 ---------------------
601 If you just want to boot a kernel once (because you are not sure
602 if it works, or if you want to boot a known bad kernel to provide
603 debugging information) run
604 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
605 nextboot -k testkernel
607 To just build a kernel when you know that it won't mess you up
608 --------------------------------------------------------------
609 This assumes you are already running a 5.X system. Replace
610 ${arch} with the architecture of your machine (e.g. "i386",
611 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
613 cd src/sys/${arch}/conf
614 config KERNEL_NAME_HERE
615 cd ../compile/KERNEL_NAME_HERE
620 If this fails, go to the "To build a kernel" section.
622 To rebuild everything and install it on the current system.
623 -----------------------------------------------------------
624 # Note: sometimes if you are running current you gotta do more than
625 # is listed here if you are upgrading from a really old current.
627 <make sure you have good level 0 dumps>
629 make kernel KERNCONF=YOUR_KERNEL_HERE
631 <reboot in single user> [3]
639 To cross-install current onto a separate partition
640 --------------------------------------------------
641 # In this approach we use a separate partition to hold
642 # current's root, 'usr', and 'var' directories. A partition
643 # holding "/", "/usr" and "/var" should be about 2GB in
646 <make sure you have good level 0 dumps>
649 make buildkernel KERNCONF=YOUR_KERNEL_HERE
650 <maybe newfs current's root partition>
651 <mount current's root partition on directory ${CURRENT_ROOT}>
652 make installworld DESTDIR=${CURRENT_ROOT}
653 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
654 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
655 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
656 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
657 <reboot into current>
658 <do a "native" rebuild/install as described in the previous section>
659 <maybe install compatibility libraries from src/lib/compat>
663 To upgrade in-place from 5.x-stable to current
664 ----------------------------------------------
665 <make sure you have good level 0 dumps>
667 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
669 <reboot in single user> [3]
676 Make sure that you've read the UPDATING file to understand the
677 tweaks to various things you need. At this point in the life
678 cycle of current, things change often and you are on your own
679 to cope. The defaults can also change, so please read ALL of
680 the UPDATING entries.
682 Also, if you are tracking -current, you must be subscribed to
683 freebsd-current@freebsd.org. Make sure that before you update
684 your sources that you have read and understood all the recent
685 messages there. If in doubt, please track -stable which has
688 [1] If you have third party modules, such as vmware, you
689 should disable them at this point so they don't crash your
692 [3] From the bootblocks, boot -s, and then do
697 adjkerntz -i # if CMOS is wall time
698 Also, when doing a major release upgrade, it is required that
699 you boot into single user mode to do the installworld.
701 [4] Note: This step is non-optional. Failure to do this step
702 can result in a significant reduction in the functionality of the
703 system. Attempting to do it by hand is not recommended and those
704 that pursue this avenue should read this file carefully, as well
705 as the archives of freebsd-current and freebsd-hackers mailing lists
706 for potential gotchas.
708 [5] Usually this step is a noop. However, from time to time
709 you may need to do this if you get unknown user in the following
710 step. It never hurts to do it all the time. You may need to
711 install a new mergemaster (cd src/usr.sbin/mergemaster && make
712 install) after the buildworld before this step if you last updated
713 from current before 20020224 or from -stable before 20020408.
715 [8] In order to have a kernel that can run the 4.x binaries
716 needed to do an installworld, you must include the COMPAT_FREEBSD4
717 option in your kernel. Failure to do so may leave you with a system
718 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
719 is required to run the 5.x binaries on more recent kernels.
721 Make sure that you merge any new devices from GENERIC since the
722 last time you updated your kernel config file.
724 [9] When checking out sources, you must include the -P flag to have
725 cvs prune empty directories.
727 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
728 "?=" instead of the "=" assignment operator, so that buildworld can
729 override the CPUTYPE if it needs to.
731 MAKEOBJDIRPREFIX must be defined in an environment variable, and
732 not on the command line, or in /etc/make.conf. buildworld will
733 warn if it is improperly defined.
736 This file contains a list, in reverse chronological order, of major
737 breakages in tracking -current. Not all things will be listed here,
738 and it only starts on October 16, 2004. Updating files can found in
739 previous releases if your system is older than this.
741 Copyright information:
743 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
745 Redistribution, publication, translation and use, with or without
746 modification, in full or in part, in any form or format of this
747 document are permitted without further permission from the author.
749 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
750 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
751 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
752 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
753 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
754 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
755 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
756 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
757 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
758 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
759 POSSIBILITY OF SUCH DAMAGE.
761 If you find this document useful, and you want to, you may buy the
764 Contact Warner Losh if you have any questions about your use of