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