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