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 net80211-related tools in the tools/tools/ath directory
26 have been moved to tools/tools/net80211 and renamed with a
27 "wlan" prefix. Scripts that use them should be adjusted
31 Scripts in the local_startup directories (as defined in
32 /etc/defaults/rc.conf) that have the new rc.d semantics will
33 now be run as part of the base system rcorder. If there are
34 errors or problems with one of these local scripts, it could
35 cause boot problems. If you encounter such problems, boot in
36 single user mode, remove that script from the */rc.d directory.
37 Please report the problem to the port's maintainer, and the
38 freebsd-ports@freebsd.org mailing list.
41 The nodev mount option was deprecated in RELENG_6 (where it
42 was a no-op), and is now unsupported. If you have nodev or dev listed
43 in /etc/fstab, remove it, otherwise it will result in a mount error.
46 ABI between ipfw(4) and ipfw(8) has been changed. You need
47 to rebuild ipfw(8) when rebuilding kernel.
50 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
51 Its /etc/rc.conf.d configuration file has been `ppp' from
52 the beginning, and hence there is no need to touch it.
55 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
56 to turn polling(4) on your interfaces.
59 The old bridge(4) implementation was retired. The new
60 if_bridge(4) serves as a full functional replacement.
63 The ai_addrlen of a struct addrinfo was changed to a socklen_t
64 to conform to POSIX-2001. This change broke an ABI
65 compatibility on 64 bit architecture. You have to recompile
66 userland programs that use getaddrinfo(3) on 64 bit
70 RELENG_6 branched here.
73 The pccard_ifconfig rc.conf variable has been removed and a new
74 variable, ifconfig_DEFAULT has been introduced. Unlike
75 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
76 do not have ifconfig_ifn entries rather than just those in
80 Some previous versions of PAM have permitted the use of
81 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
82 to third party PAM modules in /usr/local/lib. A change has been
83 made to require the use of absolute paths in order to avoid
84 ambiguity and dependence on library path configuration, which may
85 affect existing configurations.
88 Major changes to network interface API. All drivers must be
89 recompiled. Drivers not in the base system will need to be
90 updated to the new APIs.
93 Changes were made to kinfo_proc in sys/user.h. Please recompile
94 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
95 will not behave correctly.
97 The API and ABI for hwpmc(4) have changed with the addition
98 of sampling support. Please recompile lib/libpmc(3) and
99 usr.sbin/{pmcstat,pmccontrol}.
102 The OpenBSD dhclient was imported in place of the ISC dhclient
103 and the network interface configuration scripts were updated
104 accordingly. If you use DHCP to configure your interfaces, you
105 must now run devd. Also, DNS updating was lost so you will need
106 to find a workaround if you use this feature.
109 if_bridge was added to the tree. This has changed struct ifnet.
110 Please recompile userland and all network related modules.
113 The n_net of a struct netent was changed to an uint32_t, and
114 1st argument of getnetbyaddr() was changed to an uint32_t, to
115 conform to POSIX-2001. These changes broke an ABI
116 compatibility on 64 bit architecture. With these changes,
117 shlib major of libpcap was bumped. You have to recompile
118 userland programs that use getnetbyaddr(3), getnetbyname(3),
119 getnetent(3) and/or libpcap on 64 bit architecture.
122 Kernel parsing of extra options on '#!' first lines of shell
123 scripts has changed. Lines with multiple options likely will
124 fail after this date. For full details, please see
125 http://people.freebsd.org/~gad/Updating-20050528.txt
128 The packet filter (pf) code has been updated to OpenBSD 3.7
129 Please note the changed anchor syntax and the fact that
130 authpf(8) now needs a mounted fdescfs(5) to function.
133 The NO_MIXED_MODE kernel option has been removed from the i386
134 amd64 platforms as its use has been superceded by the new local
135 APIC timer code. Any kernel config files containing this option
139 The on-disk format of LC_CTYPE files was changed to be machine
140 independent. Please make sure NOT to use NO_CLEAN buildworld
141 when crossing this point. Crossing this point also requires
142 recompile or reinstall of all locale depended packages.
145 The ifi_epoch member of struct if_data has been changed to
146 contain the uptime at which the interface was created or the
147 statistics zeroed rather then the wall clock time because
148 wallclock time may go backwards. This should have no impact
149 unless an snmp implementation is using this value (I know of
153 The acpi_perf and acpi_throttle drivers are now part of the
154 acpi(4) main module. They are no longer built separately.
157 The layout of struct image_params has changed. You have to
158 recompile all compatibility modules (linux, svr4, etc) for use
162 The p4tcc driver has been merged into cpufreq(4). This makes
163 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
164 compile in "device cpufreq" to restore this functionality.
167 The responsibility of recomputing the file system summary of
168 a SoftUpdates-enabled dirty volume has been transferred to the
169 background fsck. A rebuild of fsck(8) utility is recommended
170 if you have updated the kernel.
172 To get the old behavior (recompute file system summary at mount
173 time), you can set vfs.ffs.compute_summary_at_mount=1 before
174 mounting the new volume.
177 The cpufreq import is complete. As part of this, the sysctls for
178 acpi(4) throttling have been removed. The power_profile script
179 has been updated, so you can use performance/economy_cpu_freq in
180 rc.conf(5) to set AC on/offline cpu frequencies.
183 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
184 requires recompiling libnetgraph and userland netgraph utilities.
187 Support for abbreviated forms of a number of ipfw options is
188 now deprecated. Warnings are printed to stderr indicating the
189 correct full form when a match occurs. Some abbreviations may
190 be supported at a later date based on user feedback. To be
191 considered for support, abbreviations must be in use prior to
192 this commit and unlikely to be confused with current key words.
195 By a popular demand, a lot of NOFOO options were renamed
196 to NO_FOO (see bsd.compat.mk for a full list). The old
197 spellings are still supported, but will cause annoying
198 warnings on stderr. Make sure you upgrade properly (see
199 the COMMON ITEMS: section later in this file).
202 Auto-loading of ancillary wlan modules such as wlan_wep has
203 been temporarily disabled; you need to statically configure
204 the modules you need into your kernel or explicitly load them
205 prior to use. Specifically, if you intend to use WEP encryption
206 with an 802.11 device load/configure wlan_wep; if you want to
207 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
208 and wlan_xauth as required.
211 The behaviour of ppp(8) has changed slightly. If lqr is enabled
212 (``enable lqr''), older versions would revert to LCP ECHO mode on
213 negotiation failure. Now, ``enable echo'' is required for this
214 behaviour. The ppp version number has been bumped to 3.4.2 to
218 The wlan support has been updated to split the crypto support
219 into separate modules. For static WEP you must configure the
220 wlan_wep module in your system or build and install the module
221 in place where it can be loaded (the kernel will auto-load
222 the module when a wep key is configured).
225 The ath driver has been updated to split the tx rate control
226 algorithm into a separate module. You need to include either
227 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
230 Support for systems with an 80386 CPU has been removed. Please
231 use FreeBSD 5.x or earlier on systems with an 80386.
234 We have had a hack which would mount the root filesystem
235 R/W if the device were named 'md*'. As part of the vnode
236 work I'm doing I have had to remove this hack. People
237 building systems which use preloaded MD root filesystems
238 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
239 their /etc/rc scripts.
242 FreeBSD 5.3 shipped here.
245 The size of struct tcpcb has changed again due to the removal
246 of RFC1644 T/TCP. You have to recompile userland programs that
247 read kmem for tcp sockets directly (netstat, sockstat, etc.)
250 The size of struct tcpcb has changed. You have to recompile
251 userland programs that read kmem for tcp sockets directly
252 (netstat, sockstat, etc.)
255 RELENG_5 branched here. For older entries, please see updating
256 in the RELENG_5 branch.
262 Avoid using make -j when upgrading. From time to time in the
263 past there have been problems using -j with buildworld and/or
264 installworld. This is especially true when upgrading between
265 "distant" versions (eg one that cross a major release boundary
266 or several minor releases, or when several months have passed
267 on the -current branch).
269 Sometimes, obscure build problems are the result of environment
270 poisoning. This can happen because the make utility reads its
271 environment when searching for values for global variables.
272 To run your build attempts in an "environmental clean room",
273 prefix all make commands with 'env -i '. See the env(1) manual
274 page for more details.
276 When upgrading from one major version to another it is generally
277 best to upgrade to the latest code in the currently installed branch
278 first, then do an upgrade to the new branch. This is the best-tested
279 upgrade path, and has the highest probability of being successful.
280 Please try this approach before reporting problems with a major
285 If you are updating from a prior version of FreeBSD (even one just
286 a few days old), you should follow this procedure. It is the most
287 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
289 make kernel-toolchain
290 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
291 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
293 To test a kernel once
294 ---------------------
295 If you just want to boot a kernel once (because you are not sure
296 if it works, or if you want to boot a known bad kernel to provide
297 debugging information) run
298 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
299 nextboot -k testkernel
301 To just build a kernel when you know that it won't mess you up
302 --------------------------------------------------------------
303 This assumes you are already running a 5.X system. Replace
304 ${arch} with the architecture of your machine (e.g. "i386",
305 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
307 cd src/sys/${arch}/conf
308 config KERNEL_NAME_HERE
309 cd ../compile/KERNEL_NAME_HERE
314 If this fails, go to the "To build a kernel" section.
316 To rebuild everything and install it on the current system.
317 -----------------------------------------------------------
318 # Note: sometimes if you are running current you gotta do more than
319 # is listed here if you are upgrading from a really old current.
321 <make sure you have good level 0 dumps>
323 make kernel KERNCONF=YOUR_KERNEL_HERE
325 <reboot in single user> [3]
333 To cross-install current onto a separate partition
334 --------------------------------------------------
335 # In this approach we use a separate partition to hold
336 # current's root, 'usr', and 'var' directories. A partition
337 # holding "/", "/usr" and "/var" should be about 2GB in
340 <make sure you have good level 0 dumps>
343 make buildkernel KERNCONF=YOUR_KERNEL_HERE
344 <maybe newfs current's root partition>
345 <mount current's root partition on directory ${CURRENT_ROOT}>
346 make installworld DESTDIR=${CURRENT_ROOT}
347 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
348 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
349 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
350 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
351 <reboot into current>
352 <do a "native" rebuild/install as described in the previous section>
353 <maybe install compatibility libraries from src/lib/compat>
357 To upgrade in-place from 5.x-stable to current
358 ----------------------------------------------
359 <make sure you have good level 0 dumps>
361 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
363 <reboot in single user> [3]
370 Make sure that you've read the UPDATING file to understand the
371 tweaks to various things you need. At this point in the life
372 cycle of current, things change often and you are on your own
373 to cope. The defaults can also change, so please read ALL of
374 the UPDATING entries.
376 Also, if you are tracking -current, you must be subscribed to
377 freebsd-current@freebsd.org. Make sure that before you update
378 your sources that you have read and understood all the recent
379 messages there. If in doubt, please track -stable which has
382 [1] If you have third party modules, such as vmware, you
383 should disable them at this point so they don't crash your
386 [3] From the bootblocks, boot -s, and then do
391 adjkerntz -i # if CMOS is wall time
392 Also, when doing a major release upgrade, it is required that
393 you boot into single user mode to do the installworld.
395 [4] Note: This step is non-optional. Failure to do this step
396 can result in a significant reduction in the functionality of the
397 system. Attempting to do it by hand is not recommended and those
398 that pursue this avenue should read this file carefully, as well
399 as the archives of freebsd-current and freebsd-hackers mailing lists
400 for potential gotchas.
402 [5] Usually this step is a noop. However, from time to time
403 you may need to do this if you get unknown user in the following
404 step. It never hurts to do it all the time. You may need to
405 install a new mergemaster (cd src/usr.sbin/mergemaster && make
406 install) after the buildworld before this step if you last updated
407 from current before 20020224 or from -stable before 20020408.
409 [8] In order to have a kernel that can run the 4.x binaries
410 needed to do an installworld, you must include the COMPAT_FREEBSD4
411 option in your kernel. Failure to do so may leave you with a system
412 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
413 is required to run the 5.x binaries on more recent kernels.
415 Make sure that you merge any new devices from GENERIC since the
416 last time you updated your kernel config file.
418 [9] When checking out sources, you must include the -P flag to have
419 cvs prune empty directories.
421 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
422 "?=" instead of the "=" assignment operator, so that buildworld can
423 override the CPUTYPE if it needs to.
425 MAKEOBJDIRPREFIX must be defined in an environment variable, and
426 not on the command line, or in /etc/make.conf. buildworld will
427 warn if it is improperly defined.
430 This file contains a list, in reverse chronological order, of major
431 breakages in tracking -current. Not all things will be listed here,
432 and it only starts on October 16, 2004. Updating files can found in
433 previous releases if your system is older than this.
435 Copyright information:
437 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
439 Redistribution, publication, translation and use, with or without
440 modification, in full or in part, in any form or format of this
441 document are permitted without further permission from the author.
443 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
444 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
445 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
446 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
447 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
448 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
449 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
450 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
451 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
452 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
453 POSSIBILITY OF SUCH DAMAGE.
455 If you find this document useful, and you want to, you may buy the
458 Contact Warner Losh if you have any questions about your use of