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 mrouted and its utilities have been removed from the base system.
28 Some ioctl(2) command codes have changed. Full backward ABI
29 compatibility is provided if the "options COMPAT_FREEBSD6" is
30 present in the kernel configuration file. Make sure to add
31 this option to your kernel config file, or recompile X.Org
32 and the rest of ports; otherwise they may refuse to work.
35 tcpslice has been removed from the base system.
38 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
39 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
40 systat needs to be rebuilt.
43 libpcap updated to v0.9.4 and tcpdump to v3.9.4
46 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
47 for IPFIREWALL_FORWARD is now as it was before when it was first
48 committed and for years after. The behaviour is now ON.
51 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
52 Now it can decrypt files created from different architectures.
53 Unfortunately, it is no longer able to decrypt a cipher text
54 generated with an older version on 64 bit architectures.
55 If you have such a file, you need old utility to decrypt it.
58 The interface version of the i4b kernel part has changed. So
59 after updating the kernel sources and compiling a new kernel,
60 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
61 be rebuilt, and vice versa.
64 The XBOX kernel now defaults to the nfe(4) driver instead of
65 the nve(4) driver. Please update your configuration
69 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
70 PCnet family of NICs has been removed. The new le(4) driver serves
71 as an equivalent but cross-platform replacement with the pcn(4)
72 driver still providing performance-optimized support for the subset
73 of AMD Am79C971 PCnet-FAST and greater chips as before.
76 The machdep.* sysctls and the adjkerntz utility have been
77 modified a bit. The new adjkerntz utility uses the new
78 sysctl names and sysctlbyname() calls, so it may be impossible
79 to run an old /sbin/adjkerntz utility in single-user mode
80 with a new kernel. Replace the `adjkerntz -i' step before
81 `make installworld' with:
83 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
85 and proceed as usual with the rest of the installworld-stage
86 steps. Otherwise, you risk installing binaries with their
87 timestamp set several hours in the future, especially if
88 you are running with local time set to GMT+X hours.
91 The ip6fw utility has been removed. The behavior provided by
92 ip6fw has been in ipfw2 for a good while and the rc.d scripts
93 have been updated to deal with it. There are some rules that
94 might not migrate cleanly. Use rc.firewall6 as a template to
98 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
99 attachments have been removed. Make sure to configure scc(4)
100 on sparc64. Note also that by default puc(4) will use uart(4)
101 and not sio(4) for serial ports because interrupt handling has
102 been optimized for multi-port serial cards and only uart(4)
103 implements the interface to support it.
106 The scc(4) driver replaces puc(4) for Serial Communications
107 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
108 Z8530. On sparc64, it is advised to add scc(4) to the kernel
109 configuration to make sure that the serial ports remain
113 Most world/kernel related NO_* build options changed names.
114 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
115 after FreeBSD ports) and should be set in /etc/src.conf
116 (the src.conf(5) manpage is provided). Full backwards
117 compatibility is maintained for the time being though it's
118 highly recommended to start moving old options out of the
119 system-wide /etc/make.conf file into the new /etc/src.conf
120 while also properly renaming them. More conversions will
121 likely follow. Posting to current@:
123 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
126 The NETSMBCRYPTO kernel option has been retired because its
127 functionality is always included in NETSMB and smbfs.ko now.
130 The TDFX_LINUX kernel option was retired and replaced by the
131 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
132 kernel module. Loading it alone should suffice to get 3dfx support
133 for Linux apps because it will pull in 3dfx.ko and linux.ko through
137 The 'audit' group was added to support the new auditing functionality
138 in the base system. Be sure to follow the directions for updating,
139 including the requirement to run mergemaster -p.
142 The kernel ABI to file system modules was changed on i386.
143 Please make sure that your kernel and modules are in sync.
146 This actually occured some time ago, but installing the kernel
147 now also installs a bunch of symbol files for the kernel modules.
148 This increases the size of /boot/kernel to about 67Mbytes. You
149 will need twice this if you will eventually back this up to kernel.old
150 on your next install.
151 If you have a shortage of room in your root partition, you should add
152 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
153 to your /etc/make.conf.
156 libc's malloc implementation has been replaced. This change has the
157 potential to uncover application bugs that previously went unnoticed.
158 See the malloc(3) manual page for more details.
161 The generic netgraph(4) cookie has been changed. If you upgrade
162 kernel passing this point, you also need to upgrade userland
163 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
166 si(4)'s device files now contain the unit number.
167 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
170 The kernel ABI was mostly destroyed due to a change in the size
171 of struct lock_object which is nested in other structures such
172 as mutexes which are nested in all sorts of other structures.
173 Make sure your kernel and modules are in sync.
176 The page coloring algorithm in the VM subsystem was converted
177 from tuning with kernel options to autotuning. Please remove
178 any PQ_* option except PQ_NOOPT from your kernel config.
181 The net80211-related tools in the tools/tools/ath directory
182 have been moved to tools/tools/net80211 and renamed with a
183 "wlan" prefix. Scripts that use them should be adjusted
187 Scripts in the local_startup directories (as defined in
188 /etc/defaults/rc.conf) that have the new rc.d semantics will
189 now be run as part of the base system rcorder. If there are
190 errors or problems with one of these local scripts, it could
191 cause boot problems. If you encounter such problems, boot in
192 single user mode, remove that script from the */rc.d directory.
193 Please report the problem to the port's maintainer, and the
194 freebsd-ports@freebsd.org mailing list.
197 The nodev mount option was deprecated in RELENG_6 (where it
198 was a no-op), and is now unsupported. If you have nodev or dev listed
199 in /etc/fstab, remove it, otherwise it will result in a mount error.
202 ABI between ipfw(4) and ipfw(8) has been changed. You need
203 to rebuild ipfw(8) when rebuilding kernel.
206 rp(4)'s device files now contain the unit number.
207 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
210 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
211 Its /etc/rc.conf.d configuration file has been `ppp' from
212 the beginning, and hence there is no need to touch it.
215 Now most modules get their build-time options from the kernel
216 configuration file. A few modules still have fixed options
217 due to their non-conformant implementation, but they will be
218 corrected eventually. You may need to review the options of
219 the modules in use, explicitly specify the non-default options
220 in the kernel configuration file, and rebuild the kernel and
224 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
225 to turn polling(4) on your interfaces.
228 The old bridge(4) implementation was retired. The new
229 if_bridge(4) serves as a full functional replacement.
232 The ai_addrlen of a struct addrinfo was changed to a socklen_t
233 to conform to POSIX-2001. This change broke an ABI
234 compatibility on 64 bit architecture. You have to recompile
235 userland programs that use getaddrinfo(3) on 64 bit
239 RELENG_6 branched here.
242 The pccard_ifconfig rc.conf variable has been removed and a new
243 variable, ifconfig_DEFAULT has been introduced. Unlike
244 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
245 do not have ifconfig_ifn entries rather than just those in
246 removable_interfaces.
249 Some previous versions of PAM have permitted the use of
250 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
251 to third party PAM modules in /usr/local/lib. A change has been
252 made to require the use of absolute paths in order to avoid
253 ambiguity and dependence on library path configuration, which may
254 affect existing configurations.
257 Major changes to network interface API. All drivers must be
258 recompiled. Drivers not in the base system will need to be
259 updated to the new APIs.
262 Changes were made to kinfo_proc in sys/user.h. Please recompile
263 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
264 will not behave correctly.
266 The API and ABI for hwpmc(4) have changed with the addition
267 of sampling support. Please recompile lib/libpmc(3) and
268 usr.sbin/{pmcstat,pmccontrol}.
271 The OpenBSD dhclient was imported in place of the ISC dhclient
272 and the network interface configuration scripts were updated
273 accordingly. If you use DHCP to configure your interfaces, you
274 must now run devd. Also, DNS updating was lost so you will need
275 to find a workaround if you use this feature.
277 The '_dhcp' user was added to support the OpenBSD dhclient. Be
278 sure to run mergemaster -p (like you are supposed to do every time
282 if_bridge was added to the tree. This has changed struct ifnet.
283 Please recompile userland and all network related modules.
286 The n_net of a struct netent was changed to an uint32_t, and
287 1st argument of getnetbyaddr() was changed to an uint32_t, to
288 conform to POSIX-2001. These changes broke an ABI
289 compatibility on 64 bit architecture. With these changes,
290 shlib major of libpcap was bumped. You have to recompile
291 userland programs that use getnetbyaddr(3), getnetbyname(3),
292 getnetent(3) and/or libpcap on 64 bit architecture.
295 Kernel parsing of extra options on '#!' first lines of shell
296 scripts has changed. Lines with multiple options likely will
297 fail after this date. For full details, please see
298 http://people.freebsd.org/~gad/Updating-20050528.txt
301 The packet filter (pf) code has been updated to OpenBSD 3.7
302 Please note the changed anchor syntax and the fact that
303 authpf(8) now needs a mounted fdescfs(5) to function.
306 The NO_MIXED_MODE kernel option has been removed from the i386
307 amd64 platforms as its use has been superceded by the new local
308 APIC timer code. Any kernel config files containing this option
312 The on-disk format of LC_CTYPE files was changed to be machine
313 independent. Please make sure NOT to use NO_CLEAN buildworld
314 when crossing this point. Crossing this point also requires
315 recompile or reinstall of all locale depended packages.
318 The ifi_epoch member of struct if_data has been changed to
319 contain the uptime at which the interface was created or the
320 statistics zeroed rather then the wall clock time because
321 wallclock time may go backwards. This should have no impact
322 unless an snmp implementation is using this value (I know of
326 The acpi_perf and acpi_throttle drivers are now part of the
327 acpi(4) main module. They are no longer built separately.
330 The layout of struct image_params has changed. You have to
331 recompile all compatibility modules (linux, svr4, etc) for use
335 The p4tcc driver has been merged into cpufreq(4). This makes
336 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
337 compile in "device cpufreq" to restore this functionality.
340 The responsibility of recomputing the file system summary of
341 a SoftUpdates-enabled dirty volume has been transferred to the
342 background fsck. A rebuild of fsck(8) utility is recommended
343 if you have updated the kernel.
345 To get the old behavior (recompute file system summary at mount
346 time), you can set vfs.ffs.compute_summary_at_mount=1 before
347 mounting the new volume.
350 The cpufreq import is complete. As part of this, the sysctls for
351 acpi(4) throttling have been removed. The power_profile script
352 has been updated, so you can use performance/economy_cpu_freq in
353 rc.conf(5) to set AC on/offline cpu frequencies.
356 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
357 requires recompiling libnetgraph and userland netgraph utilities.
360 Support for abbreviated forms of a number of ipfw options is
361 now deprecated. Warnings are printed to stderr indicating the
362 correct full form when a match occurs. Some abbreviations may
363 be supported at a later date based on user feedback. To be
364 considered for support, abbreviations must be in use prior to
365 this commit and unlikely to be confused with current key words.
368 By a popular demand, a lot of NOFOO options were renamed
369 to NO_FOO (see bsd.compat.mk for a full list). The old
370 spellings are still supported, but will cause annoying
371 warnings on stderr. Make sure you upgrade properly (see
372 the COMMON ITEMS: section later in this file).
375 Auto-loading of ancillary wlan modules such as wlan_wep has
376 been temporarily disabled; you need to statically configure
377 the modules you need into your kernel or explicitly load them
378 prior to use. Specifically, if you intend to use WEP encryption
379 with an 802.11 device load/configure wlan_wep; if you want to
380 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
381 and wlan_xauth as required.
384 The behaviour of ppp(8) has changed slightly. If lqr is enabled
385 (``enable lqr''), older versions would revert to LCP ECHO mode on
386 negotiation failure. Now, ``enable echo'' is required for this
387 behaviour. The ppp version number has been bumped to 3.4.2 to
391 The wlan support has been updated to split the crypto support
392 into separate modules. For static WEP you must configure the
393 wlan_wep module in your system or build and install the module
394 in place where it can be loaded (the kernel will auto-load
395 the module when a wep key is configured).
398 The ath driver has been updated to split the tx rate control
399 algorithm into a separate module. You need to include either
400 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
403 Support for systems with an 80386 CPU has been removed. Please
404 use FreeBSD 5.x or earlier on systems with an 80386.
407 We have had a hack which would mount the root filesystem
408 R/W if the device were named 'md*'. As part of the vnode
409 work I'm doing I have had to remove this hack. People
410 building systems which use preloaded MD root filesystems
411 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
412 their /etc/rc scripts.
415 FreeBSD 5.3 shipped here.
418 The size of struct tcpcb has changed again due to the removal
419 of RFC1644 T/TCP. You have to recompile userland programs that
420 read kmem for tcp sockets directly (netstat, sockstat, etc.)
423 The size of struct tcpcb has changed. You have to recompile
424 userland programs that read kmem for tcp sockets directly
425 (netstat, sockstat, etc.)
428 RELENG_5 branched here. For older entries, please see updating
429 in the RELENG_5 branch.
435 Avoid using make -j when upgrading. From time to time in the
436 past there have been problems using -j with buildworld and/or
437 installworld. This is especially true when upgrading between
438 "distant" versions (eg one that cross a major release boundary
439 or several minor releases, or when several months have passed
440 on the -current branch).
442 Sometimes, obscure build problems are the result of environment
443 poisoning. This can happen because the make utility reads its
444 environment when searching for values for global variables.
445 To run your build attempts in an "environmental clean room",
446 prefix all make commands with 'env -i '. See the env(1) manual
447 page for more details.
449 When upgrading from one major version to another it is generally
450 best to upgrade to the latest code in the currently installed branch
451 first, then do an upgrade to the new branch. This is the best-tested
452 upgrade path, and has the highest probability of being successful.
453 Please try this approach before reporting problems with a major
458 If you are updating from a prior version of FreeBSD (even one just
459 a few days old), you should follow this procedure. It is the most
460 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
462 make kernel-toolchain
463 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
464 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
466 To test a kernel once
467 ---------------------
468 If you just want to boot a kernel once (because you are not sure
469 if it works, or if you want to boot a known bad kernel to provide
470 debugging information) run
471 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
472 nextboot -k testkernel
474 To just build a kernel when you know that it won't mess you up
475 --------------------------------------------------------------
476 This assumes you are already running a 5.X system. Replace
477 ${arch} with the architecture of your machine (e.g. "i386",
478 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
480 cd src/sys/${arch}/conf
481 config KERNEL_NAME_HERE
482 cd ../compile/KERNEL_NAME_HERE
487 If this fails, go to the "To build a kernel" section.
489 To rebuild everything and install it on the current system.
490 -----------------------------------------------------------
491 # Note: sometimes if you are running current you gotta do more than
492 # is listed here if you are upgrading from a really old current.
494 <make sure you have good level 0 dumps>
496 make kernel KERNCONF=YOUR_KERNEL_HERE
498 <reboot in single user> [3]
506 To cross-install current onto a separate partition
507 --------------------------------------------------
508 # In this approach we use a separate partition to hold
509 # current's root, 'usr', and 'var' directories. A partition
510 # holding "/", "/usr" and "/var" should be about 2GB in
513 <make sure you have good level 0 dumps>
516 make buildkernel KERNCONF=YOUR_KERNEL_HERE
517 <maybe newfs current's root partition>
518 <mount current's root partition on directory ${CURRENT_ROOT}>
519 make installworld DESTDIR=${CURRENT_ROOT}
520 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
521 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
522 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
523 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
524 <reboot into current>
525 <do a "native" rebuild/install as described in the previous section>
526 <maybe install compatibility libraries from src/lib/compat>
530 To upgrade in-place from 5.x-stable to current
531 ----------------------------------------------
532 <make sure you have good level 0 dumps>
534 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
536 <reboot in single user> [3]
543 Make sure that you've read the UPDATING file to understand the
544 tweaks to various things you need. At this point in the life
545 cycle of current, things change often and you are on your own
546 to cope. The defaults can also change, so please read ALL of
547 the UPDATING entries.
549 Also, if you are tracking -current, you must be subscribed to
550 freebsd-current@freebsd.org. Make sure that before you update
551 your sources that you have read and understood all the recent
552 messages there. If in doubt, please track -stable which has
555 [1] If you have third party modules, such as vmware, you
556 should disable them at this point so they don't crash your
559 [3] From the bootblocks, boot -s, and then do
564 adjkerntz -i # if CMOS is wall time
565 Also, when doing a major release upgrade, it is required that
566 you boot into single user mode to do the installworld.
568 [4] Note: This step is non-optional. Failure to do this step
569 can result in a significant reduction in the functionality of the
570 system. Attempting to do it by hand is not recommended and those
571 that pursue this avenue should read this file carefully, as well
572 as the archives of freebsd-current and freebsd-hackers mailing lists
573 for potential gotchas.
575 [5] Usually this step is a noop. However, from time to time
576 you may need to do this if you get unknown user in the following
577 step. It never hurts to do it all the time. You may need to
578 install a new mergemaster (cd src/usr.sbin/mergemaster && make
579 install) after the buildworld before this step if you last updated
580 from current before 20020224 or from -stable before 20020408.
582 [8] In order to have a kernel that can run the 4.x binaries
583 needed to do an installworld, you must include the COMPAT_FREEBSD4
584 option in your kernel. Failure to do so may leave you with a system
585 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
586 is required to run the 5.x binaries on more recent kernels.
588 Make sure that you merge any new devices from GENERIC since the
589 last time you updated your kernel config file.
591 [9] When checking out sources, you must include the -P flag to have
592 cvs prune empty directories.
594 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
595 "?=" instead of the "=" assignment operator, so that buildworld can
596 override the CPUTYPE if it needs to.
598 MAKEOBJDIRPREFIX must be defined in an environment variable, and
599 not on the command line, or in /etc/make.conf. buildworld will
600 warn if it is improperly defined.
603 This file contains a list, in reverse chronological order, of major
604 breakages in tracking -current. Not all things will be listed here,
605 and it only starts on October 16, 2004. Updating files can found in
606 previous releases if your system is older than this.
608 Copyright information:
610 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
612 Redistribution, publication, translation and use, with or without
613 modification, in full or in part, in any form or format of this
614 document are permitted without further permission from the author.
616 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
617 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
618 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
619 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
620 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
621 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
622 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
623 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
624 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
625 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
626 POSSIBILITY OF SUCH DAMAGE.
628 If you find this document useful, and you want to, you may buy the
631 Contact Warner Losh if you have any questions about your use of