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 kernel ABI to file system modules was changed on i386.
26 Please make sure that your kernel and modules are in sync.
29 This actually occured some time ago, but installing the kernel
30 now also installs a bunch of symbol files for the kernel modules.
31 This increases the size of /boot/kernel to about 67Mbytes. You
32 will need twice this if you will eventually back this up to kernel.old
34 If you have a shortage of room in your root partition, you should add
35 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
36 to your /etc/make.conf.
39 libc's malloc implementation has been replaced. This change has the
40 potential to uncover application bugs that previously went unnoticed.
41 See the malloc(3) manual page for more details.
44 The generic netgraph(4) cookie has been changed. If you upgrade
45 kernel passing this point, you also need to upgrade userland
46 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
49 si(4)'s device files now contain the unit number.
50 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
53 The kernel ABI was mostly destroyed due to a change in the size
54 of struct lock_object which is nested in other structures such
55 as mutexes which are nested in all sorts of other structures.
56 Make sure your kernel and modules are in sync.
59 The page coloring algorithm in the VM subsystem was converted
60 from tuning with kernel options to autotuning. Please remove
61 any PQ_* option except PQ_NOOPT from your kernel config.
64 The net80211-related tools in the tools/tools/ath directory
65 have been moved to tools/tools/net80211 and renamed with a
66 "wlan" prefix. Scripts that use them should be adjusted
70 Scripts in the local_startup directories (as defined in
71 /etc/defaults/rc.conf) that have the new rc.d semantics will
72 now be run as part of the base system rcorder. If there are
73 errors or problems with one of these local scripts, it could
74 cause boot problems. If you encounter such problems, boot in
75 single user mode, remove that script from the */rc.d directory.
76 Please report the problem to the port's maintainer, and the
77 freebsd-ports@freebsd.org mailing list.
80 The nodev mount option was deprecated in RELENG_6 (where it
81 was a no-op), and is now unsupported. If you have nodev or dev listed
82 in /etc/fstab, remove it, otherwise it will result in a mount error.
85 ABI between ipfw(4) and ipfw(8) has been changed. You need
86 to rebuild ipfw(8) when rebuilding kernel.
89 rp(4)'s device files now contain the unit number.
90 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
93 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
94 Its /etc/rc.conf.d configuration file has been `ppp' from
95 the beginning, and hence there is no need to touch it.
98 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
99 to turn polling(4) on your interfaces.
102 The old bridge(4) implementation was retired. The new
103 if_bridge(4) serves as a full functional replacement.
106 The ai_addrlen of a struct addrinfo was changed to a socklen_t
107 to conform to POSIX-2001. This change broke an ABI
108 compatibility on 64 bit architecture. You have to recompile
109 userland programs that use getaddrinfo(3) on 64 bit
113 RELENG_6 branched here.
116 The pccard_ifconfig rc.conf variable has been removed and a new
117 variable, ifconfig_DEFAULT has been introduced. Unlike
118 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
119 do not have ifconfig_ifn entries rather than just those in
120 removable_interfaces.
123 Some previous versions of PAM have permitted the use of
124 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
125 to third party PAM modules in /usr/local/lib. A change has been
126 made to require the use of absolute paths in order to avoid
127 ambiguity and dependence on library path configuration, which may
128 affect existing configurations.
131 Major changes to network interface API. All drivers must be
132 recompiled. Drivers not in the base system will need to be
133 updated to the new APIs.
136 Changes were made to kinfo_proc in sys/user.h. Please recompile
137 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
138 will not behave correctly.
140 The API and ABI for hwpmc(4) have changed with the addition
141 of sampling support. Please recompile lib/libpmc(3) and
142 usr.sbin/{pmcstat,pmccontrol}.
145 The OpenBSD dhclient was imported in place of the ISC dhclient
146 and the network interface configuration scripts were updated
147 accordingly. If you use DHCP to configure your interfaces, you
148 must now run devd. Also, DNS updating was lost so you will need
149 to find a workaround if you use this feature.
152 if_bridge was added to the tree. This has changed struct ifnet.
153 Please recompile userland and all network related modules.
156 The n_net of a struct netent was changed to an uint32_t, and
157 1st argument of getnetbyaddr() was changed to an uint32_t, to
158 conform to POSIX-2001. These changes broke an ABI
159 compatibility on 64 bit architecture. With these changes,
160 shlib major of libpcap was bumped. You have to recompile
161 userland programs that use getnetbyaddr(3), getnetbyname(3),
162 getnetent(3) and/or libpcap on 64 bit architecture.
165 Kernel parsing of extra options on '#!' first lines of shell
166 scripts has changed. Lines with multiple options likely will
167 fail after this date. For full details, please see
168 http://people.freebsd.org/~gad/Updating-20050528.txt
171 The packet filter (pf) code has been updated to OpenBSD 3.7
172 Please note the changed anchor syntax and the fact that
173 authpf(8) now needs a mounted fdescfs(5) to function.
176 The NO_MIXED_MODE kernel option has been removed from the i386
177 amd64 platforms as its use has been superceded by the new local
178 APIC timer code. Any kernel config files containing this option
182 The on-disk format of LC_CTYPE files was changed to be machine
183 independent. Please make sure NOT to use NO_CLEAN buildworld
184 when crossing this point. Crossing this point also requires
185 recompile or reinstall of all locale depended packages.
188 The ifi_epoch member of struct if_data has been changed to
189 contain the uptime at which the interface was created or the
190 statistics zeroed rather then the wall clock time because
191 wallclock time may go backwards. This should have no impact
192 unless an snmp implementation is using this value (I know of
196 The acpi_perf and acpi_throttle drivers are now part of the
197 acpi(4) main module. They are no longer built separately.
200 The layout of struct image_params has changed. You have to
201 recompile all compatibility modules (linux, svr4, etc) for use
205 The p4tcc driver has been merged into cpufreq(4). This makes
206 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
207 compile in "device cpufreq" to restore this functionality.
210 The responsibility of recomputing the file system summary of
211 a SoftUpdates-enabled dirty volume has been transferred to the
212 background fsck. A rebuild of fsck(8) utility is recommended
213 if you have updated the kernel.
215 To get the old behavior (recompute file system summary at mount
216 time), you can set vfs.ffs.compute_summary_at_mount=1 before
217 mounting the new volume.
220 The cpufreq import is complete. As part of this, the sysctls for
221 acpi(4) throttling have been removed. The power_profile script
222 has been updated, so you can use performance/economy_cpu_freq in
223 rc.conf(5) to set AC on/offline cpu frequencies.
226 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
227 requires recompiling libnetgraph and userland netgraph utilities.
230 Support for abbreviated forms of a number of ipfw options is
231 now deprecated. Warnings are printed to stderr indicating the
232 correct full form when a match occurs. Some abbreviations may
233 be supported at a later date based on user feedback. To be
234 considered for support, abbreviations must be in use prior to
235 this commit and unlikely to be confused with current key words.
238 By a popular demand, a lot of NOFOO options were renamed
239 to NO_FOO (see bsd.compat.mk for a full list). The old
240 spellings are still supported, but will cause annoying
241 warnings on stderr. Make sure you upgrade properly (see
242 the COMMON ITEMS: section later in this file).
245 Auto-loading of ancillary wlan modules such as wlan_wep has
246 been temporarily disabled; you need to statically configure
247 the modules you need into your kernel or explicitly load them
248 prior to use. Specifically, if you intend to use WEP encryption
249 with an 802.11 device load/configure wlan_wep; if you want to
250 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
251 and wlan_xauth as required.
254 The behaviour of ppp(8) has changed slightly. If lqr is enabled
255 (``enable lqr''), older versions would revert to LCP ECHO mode on
256 negotiation failure. Now, ``enable echo'' is required for this
257 behaviour. The ppp version number has been bumped to 3.4.2 to
261 The wlan support has been updated to split the crypto support
262 into separate modules. For static WEP you must configure the
263 wlan_wep module in your system or build and install the module
264 in place where it can be loaded (the kernel will auto-load
265 the module when a wep key is configured).
268 The ath driver has been updated to split the tx rate control
269 algorithm into a separate module. You need to include either
270 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
273 Support for systems with an 80386 CPU has been removed. Please
274 use FreeBSD 5.x or earlier on systems with an 80386.
277 We have had a hack which would mount the root filesystem
278 R/W if the device were named 'md*'. As part of the vnode
279 work I'm doing I have had to remove this hack. People
280 building systems which use preloaded MD root filesystems
281 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
282 their /etc/rc scripts.
285 FreeBSD 5.3 shipped here.
288 The size of struct tcpcb has changed again due to the removal
289 of RFC1644 T/TCP. You have to recompile userland programs that
290 read kmem for tcp sockets directly (netstat, sockstat, etc.)
293 The size of struct tcpcb has changed. You have to recompile
294 userland programs that read kmem for tcp sockets directly
295 (netstat, sockstat, etc.)
298 RELENG_5 branched here. For older entries, please see updating
299 in the RELENG_5 branch.
305 Avoid using make -j when upgrading. From time to time in the
306 past there have been problems using -j with buildworld and/or
307 installworld. This is especially true when upgrading between
308 "distant" versions (eg one that cross a major release boundary
309 or several minor releases, or when several months have passed
310 on the -current branch).
312 Sometimes, obscure build problems are the result of environment
313 poisoning. This can happen because the make utility reads its
314 environment when searching for values for global variables.
315 To run your build attempts in an "environmental clean room",
316 prefix all make commands with 'env -i '. See the env(1) manual
317 page for more details.
319 When upgrading from one major version to another it is generally
320 best to upgrade to the latest code in the currently installed branch
321 first, then do an upgrade to the new branch. This is the best-tested
322 upgrade path, and has the highest probability of being successful.
323 Please try this approach before reporting problems with a major
328 If you are updating from a prior version of FreeBSD (even one just
329 a few days old), you should follow this procedure. It is the most
330 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
332 make kernel-toolchain
333 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
334 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
336 To test a kernel once
337 ---------------------
338 If you just want to boot a kernel once (because you are not sure
339 if it works, or if you want to boot a known bad kernel to provide
340 debugging information) run
341 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
342 nextboot -k testkernel
344 To just build a kernel when you know that it won't mess you up
345 --------------------------------------------------------------
346 This assumes you are already running a 5.X system. Replace
347 ${arch} with the architecture of your machine (e.g. "i386",
348 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
350 cd src/sys/${arch}/conf
351 config KERNEL_NAME_HERE
352 cd ../compile/KERNEL_NAME_HERE
357 If this fails, go to the "To build a kernel" section.
359 To rebuild everything and install it on the current system.
360 -----------------------------------------------------------
361 # Note: sometimes if you are running current you gotta do more than
362 # is listed here if you are upgrading from a really old current.
364 <make sure you have good level 0 dumps>
366 make kernel KERNCONF=YOUR_KERNEL_HERE
368 <reboot in single user> [3]
376 To cross-install current onto a separate partition
377 --------------------------------------------------
378 # In this approach we use a separate partition to hold
379 # current's root, 'usr', and 'var' directories. A partition
380 # holding "/", "/usr" and "/var" should be about 2GB in
383 <make sure you have good level 0 dumps>
386 make buildkernel KERNCONF=YOUR_KERNEL_HERE
387 <maybe newfs current's root partition>
388 <mount current's root partition on directory ${CURRENT_ROOT}>
389 make installworld DESTDIR=${CURRENT_ROOT}
390 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
391 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
392 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
393 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
394 <reboot into current>
395 <do a "native" rebuild/install as described in the previous section>
396 <maybe install compatibility libraries from src/lib/compat>
400 To upgrade in-place from 5.x-stable to current
401 ----------------------------------------------
402 <make sure you have good level 0 dumps>
404 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
406 <reboot in single user> [3]
413 Make sure that you've read the UPDATING file to understand the
414 tweaks to various things you need. At this point in the life
415 cycle of current, things change often and you are on your own
416 to cope. The defaults can also change, so please read ALL of
417 the UPDATING entries.
419 Also, if you are tracking -current, you must be subscribed to
420 freebsd-current@freebsd.org. Make sure that before you update
421 your sources that you have read and understood all the recent
422 messages there. If in doubt, please track -stable which has
425 [1] If you have third party modules, such as vmware, you
426 should disable them at this point so they don't crash your
429 [3] From the bootblocks, boot -s, and then do
434 adjkerntz -i # if CMOS is wall time
435 Also, when doing a major release upgrade, it is required that
436 you boot into single user mode to do the installworld.
438 [4] Note: This step is non-optional. Failure to do this step
439 can result in a significant reduction in the functionality of the
440 system. Attempting to do it by hand is not recommended and those
441 that pursue this avenue should read this file carefully, as well
442 as the archives of freebsd-current and freebsd-hackers mailing lists
443 for potential gotchas.
445 [5] Usually this step is a noop. However, from time to time
446 you may need to do this if you get unknown user in the following
447 step. It never hurts to do it all the time. You may need to
448 install a new mergemaster (cd src/usr.sbin/mergemaster && make
449 install) after the buildworld before this step if you last updated
450 from current before 20020224 or from -stable before 20020408.
452 [8] In order to have a kernel that can run the 4.x binaries
453 needed to do an installworld, you must include the COMPAT_FREEBSD4
454 option in your kernel. Failure to do so may leave you with a system
455 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
456 is required to run the 5.x binaries on more recent kernels.
458 Make sure that you merge any new devices from GENERIC since the
459 last time you updated your kernel config file.
461 [9] When checking out sources, you must include the -P flag to have
462 cvs prune empty directories.
464 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
465 "?=" instead of the "=" assignment operator, so that buildworld can
466 override the CPUTYPE if it needs to.
468 MAKEOBJDIRPREFIX must be defined in an environment variable, and
469 not on the command line, or in /etc/make.conf. buildworld will
470 warn if it is improperly defined.
473 This file contains a list, in reverse chronological order, of major
474 breakages in tracking -current. Not all things will be listed here,
475 and it only starts on October 16, 2004. Updating files can found in
476 previous releases if your system is older than this.
478 Copyright information:
480 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
482 Redistribution, publication, translation and use, with or without
483 modification, in full or in part, in any form or format of this
484 document are permitted without further permission from the author.
486 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
487 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
488 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
489 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
490 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
491 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
492 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
493 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
494 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
495 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
496 POSSIBILITY OF SUCH DAMAGE.
498 If you find this document useful, and you want to, you may buy the
501 Contact Warner Losh if you have any questions about your use of