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