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 6.x IS SLOW:
12 FreeBSD 6.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 packet filter (pf) code has been updated to OpenBSD 3.7
26 Please note the changed anchor syntax and the fact that
27 authpf(8) now needs a mounted fdescfs(5) to function.
30 The NO_MIXED_MODE kernel option has been removed from the i386
31 amd64 platforms as its use has been superceded by the new local
32 APIC timer code. Any kernel config files containing this option
36 The on-disk format of LC_CTYPE files was changed to be machine
37 independent. Please make sure NOT to use NO_CLEAN buildworld
38 when crossing this point.
41 The ifi_epoch member of struct if_data has been changed to
42 contain the uptime at which the interface was created or the
43 statistics zeroed rather then the wall clock time because
44 wallclock time may go backwards. This should have no impact
45 unless an snmp implementation is using this value (I know of
49 The acpi_perf and acpi_throttle drivers are now part of the
50 acpi(4) main module. They are no longer built separately.
53 The layout of struct image_params has changed. You have to
54 recompile all compatibility modules (linux, svr4, etc) for use
58 The p4tcc driver has been merged into cpufreq(4). This makes
59 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
60 compile in "device cpufreq" to restore this functionality.
63 The responsibility of recomputing the file system summary of
64 a SoftUpdates-enabled dirty volume has been transferred to the
65 background fsck. A rebuild of fsck(8) utility is recommended
66 if you have updated the kernel.
68 To get the old behavior (recompute file system summary at mount
69 time), you can set vfs.ffs.compute_summary_at_mount=1 before
70 mounting the new volume.
73 The cpufreq import is complete. As part of this, the sysctls for
74 acpi(4) throttling have been removed. The power_profile script
75 has been updated, so you can use performance/economy_cpu_freq in
76 rc.conf(5) to set AC on/offline cpu frequencies.
79 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
80 requires recompiling libnetgraph and userland netgraph utilities.
83 Support for abbreviated forms of a number of ipfw options is
84 now deprecated. Warnings are printed to stderr indicating the
85 correct full form when a match occurs. Some abbreviations may
86 be supported at a later date based on user feedback. To be
87 considered for support, abbreviations must be in use prior to
88 this commit and unlikely to be confused with current key words.
91 By a popular demand, a lot of NOFOO options were renamed
92 to NO_FOO (see bsd.compat.mk for a full list). The old
93 spellings are still supported, but will cause annoying
94 warnings on stderr. Make sure you upgrade properly (see
95 the COMMON ITEMS: section later in this file).
98 Auto-loading of ancillary wlan modules such as wlan_wep has
99 been temporarily disabled; you need to statically configure
100 the modules you need into your kernel or explicitly load them
101 prior to use. Specifically, if you intend to use WEP encryption
102 with an 802.11 device load/configure wlan_wep; if you want to
103 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
104 and wlan_xauth as required.
107 The behaviour of ppp(8) has changed slightly. If lqr is enabled
108 (``enable lqr''), older versions would revert to LCP ECHO mode on
109 negotiation failure. Now, ``enable echo'' is required for this
110 behaviour. The ppp version number has been bumped to 3.4.2 to
114 The wlan support has been updated to split the crypto support
115 into separate modules. For static WEP you must configure the
116 wlan_wep module in your system or build and install the module
117 in place where it can be loaded (the kernel will auto-load
118 the module when a wep key is configured).
121 The ath driver has been updated to split the tx rate control
122 algorithm into a separate module. You need to include either
123 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
126 Support for systems with an 80386 CPU has been removed. Please
127 use FreeBSD 5.x or earlier on systems with an 80386.
130 We have had a hack which would mount the root filesystem
131 R/W if the device were named 'md*'. As part of the vnode
132 work I'm doing I have had to remove this hack. People
133 building systems which use preloaded MD root filesystems
134 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
135 their /etc/rc scripts.
138 FreeBSD 5.3 shipped here.
141 The size of struct tcpcb has changed again due to the removal
142 of RFC1644 T/TCP. You have to recompile userland programs that
143 read kmem for tcp sockets directly (netstat, sockstat, etc.)
146 The size of struct tcpcb has changed. You have to recompile
147 userland programs that read kmem for tcp sockets directly
148 (netstat, sockstat, etc.)
151 RELENG_5 branched here. For older entries, please see updating
152 in the RELENG_5 branch.
158 Avoid using make -j when upgrading. From time to time in the
159 past there have been problems using -j with buildworld and/or
160 installworld. This is especially true when upgrading between
161 "distant" versions (eg one that cross a major release boundary
162 or several minor releases, or when several months have passed
163 on the -current branch).
165 Sometimes, obscure build problems are the result of environment
166 poisoning. This can happen because the make utility reads its
167 environment when searching for values for global variables.
168 To run your build attempts in an "environmental clean room",
169 prefix all make commands with 'env -i '. See the env(1) manual
170 page for more details.
174 If you are updating from a prior version of FreeBSD (even one just
175 a few days old), you should follow this procedure. With a
176 /usr/obj tree with a fresh buildworld,
177 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
178 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
180 To just build a kernel when you know that it won't mess you up
181 --------------------------------------------------------------
182 This assumes you are already running a 5.X system. Replace
183 ${arch} with the architecture of your machine (e.g. "i386",
184 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
186 cd src/sys/${arch}/conf
187 config KERNEL_NAME_HERE
188 cd ../compile/KERNEL_NAME_HERE
193 If this fails, go to the "To build a kernel" section.
195 To rebuild everything and install it on the current system.
196 -----------------------------------------------------------
197 # Note: sometimes if you are running current you gotta do more than
198 # is listed here if you are upgrading from a really old current.
200 <make sure you have good level 0 dumps>
202 make kernel KERNCONF=YOUR_KERNEL_HERE
204 <reboot in single user> [3]
211 To cross-install current onto a separate partition
212 --------------------------------------------------
213 # In this approach we use a separate partition to hold
214 # current's root, 'usr', and 'var' directories. A partition
215 # holding "/", "/usr" and "/var" should be about 2GB in
218 <make sure you have good level 0 dumps>
221 make buildkernel KERNCONF=YOUR_KERNEL_HERE
222 <maybe newfs current's root partition>
223 <mount current's root partition on directory ${CURRENT_ROOT}>
224 make installworld DESTDIR=${CURRENT_ROOT}
225 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
226 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
227 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
228 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
229 <reboot into current>
230 <do a "native" rebuild/install as described in the previous section>
231 <maybe install compatibility libraries from src/lib/compat>
235 To upgrade in-place from 5.x-stable to current
236 ----------------------------------------------
237 <make sure you have good level 0 dumps>
239 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
241 <reboot in single user> [3]
247 Make sure that you've read the UPDATING file to understand the
248 tweaks to various things you need. At this point in the life
249 cycle of current, things change often and you are on your own
250 to cope. The defaults can also change, so please read ALL of
251 the UPDATING entries.
253 Also, if you are tracking -current, you must be subscribed to
254 freebsd-current@freebsd.org. Make sure that before you update
255 your sources that you have read and understood all the recent
256 messages there. If in doubt, please track -stable which has
259 [1] If you have third party modules, such as vmware, you
260 should disable them at this point so they don't crash your
263 [3] From the bootblocks, boot -s, and then do
268 adjkerntz -i # if CMOS is wall time
269 Also, when doing a major release upgrade, it is required that
270 you boot into single user mode to do the installworld.
272 [4] Note: This step is non-optional. Failure to do this step
273 can result in a significant reduction in the functionality of the
274 system. Attempting to do it by hand is not recommended and those
275 that pursue this avenue should read this file carefully, as well
276 as the archives of freebsd-current and freebsd-hackers mailing lists
277 for potential gotchas.
279 [5] Usually this step is a noop. However, from time to time
280 you may need to do this if you get unknown user in the following
281 step. It never hurts to do it all the time. You may need to
282 install a new mergemaster (cd src/usr.sbin/mergemaster && make
283 install) after the buildworld before this step if you last updated
284 from current before 20020224 or from -stable before 20020408.
286 [8] In order to have a kernel that can run the 4.x binaries
287 needed to do an installworld, you must include the COMPAT_FREEBSD4
288 option in your kernel. Failure to do so may leave you with a system
289 that is hard to boot to recover.
291 Make sure that you merge any new devices from GENERIC since the
292 last time you updated your kernel config file.
294 [9] When checking out sources, you must include the -P flag to have
295 cvs prune empty directories.
297 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
298 "?=" instead of the "=" assignment operator, so that buildworld can
299 override the CPUTYPE if it needs to.
301 MAKEOBJDIRPREFIX must be defined in an environment variable, and
302 not on the command line, or in /etc/make.conf. buildworld will
303 warn if it is improperly defined.
306 This file contains a list, in reverse chronological order, of major
307 breakages in tracking -current. Not all things will be listed here,
308 and it only starts on October 16, 2004. Updating files can found in
309 previous releases if your system is older than this.
311 Copyright information:
313 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
315 Redistribution, publication, translation and use, with or without
316 modification, in full or in part, in any form or format of this
317 document are permitted without further permission from the author.
319 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
320 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
321 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
322 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
323 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
324 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
325 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
326 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
327 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
328 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
329 POSSIBILITY OF SUCH DAMAGE.
331 If you find this document useful, and you want to, you may buy the
334 Contact Warner Losh if you have any questions about your use of