1 Updating Information for FreeBSD STABLE 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
15 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
16 to turn polling(4) on your interfaces.
19 The ai_addrlen of a struct addrinfo was changed to a socklen_t
20 to conform to POSIX-2001. This change broke an ABI
21 compatibility on 64 bit architecture. You have to recompile
22 userland programs that use getaddrinfo(3) on 64 bit
26 RELENG_6 branched here.
29 The pccard_ifconfig rc.conf variable has been removed and a new
30 variable, ifconfig_DEFAULT has been introduced. Unlike
31 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
32 do not have ifconfig_ifn entries rather than just those in
36 Some previous versions of PAM have permitted the use of
37 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
38 to third party PAM modules in /usr/local/lib. A change has been
39 made to require the use of absolute paths in order to avoid
40 ambiguity and dependence on library path configuration, which may
41 affect existing configurations.
44 Major changes to network interface API. All drivers must be
45 recompiled. Drivers not in the base system will need to be
46 updated to the new APIs.
49 Changes were made to kinfo_proc in sys/user.h. Please recompile
50 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
51 will not behave correctly.
53 The API and ABI for hwpmc(4) have changed with the addition
54 of sampling support. Please recompile lib/libpmc(3) and
55 usr.sbin/{pmcstat,pmccontrol}.
58 The OpenBSD dhclient was imported in place of the ISC dhclient
59 and the network interface configuration scripts were updated
60 accordingly. If you use DHCP to configure your interfaces, you
61 must now run devd. Also, DNS updating was lost so you will need
62 to find a workaround if you use this feature.
65 if_bridge was added to the tree. This has changed struct ifnet.
66 Please recompile userland and all network related modules.
69 The n_net of a struct netent was changed to an uint32_t, and
70 1st argument of getnetbyaddr() was changed to an uint32_t, to
71 conform to POSIX-2001. These changes broke an ABI
72 compatibility on 64 bit architecture. With these changes,
73 shlib major of libpcap was bumped. You have to recompile
74 userland programs that use getnetbyaddr(3), getnetbyname(3),
75 getnetent(3) and/or libpcap on 64 bit architecture.
78 Kernel parsing of extra options on '#!' first lines of shell
79 scripts has changed. Lines with multiple options likely will
80 fail after this date. For full details, please see
81 http://people.freebsd.org/~gad/Updating-20050528.txt
84 The packet filter (pf) code has been updated to OpenBSD 3.7
85 Please note the changed anchor syntax and the fact that
86 authpf(8) now needs a mounted fdescfs(5) to function.
89 The NO_MIXED_MODE kernel option has been removed from the i386
90 amd64 platforms as its use has been superceded by the new local
91 APIC timer code. Any kernel config files containing this option
95 The on-disk format of LC_CTYPE files was changed to be machine
96 independent. Please make sure NOT to use NO_CLEAN buildworld
97 when crossing this point.
100 The ifi_epoch member of struct if_data has been changed to
101 contain the uptime at which the interface was created or the
102 statistics zeroed rather then the wall clock time because
103 wallclock time may go backwards. This should have no impact
104 unless an snmp implementation is using this value (I know of
108 The acpi_perf and acpi_throttle drivers are now part of the
109 acpi(4) main module. They are no longer built separately.
112 The layout of struct image_params has changed. You have to
113 recompile all compatibility modules (linux, svr4, etc) for use
117 The p4tcc driver has been merged into cpufreq(4). This makes
118 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
119 compile in "device cpufreq" to restore this functionality.
122 The responsibility of recomputing the file system summary of
123 a SoftUpdates-enabled dirty volume has been transferred to the
124 background fsck. A rebuild of fsck(8) utility is recommended
125 if you have updated the kernel.
127 To get the old behavior (recompute file system summary at mount
128 time), you can set vfs.ffs.compute_summary_at_mount=1 before
129 mounting the new volume.
132 The cpufreq import is complete. As part of this, the sysctls for
133 acpi(4) throttling have been removed. The power_profile script
134 has been updated, so you can use performance/economy_cpu_freq in
135 rc.conf(5) to set AC on/offline cpu frequencies.
138 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
139 requires recompiling libnetgraph and userland netgraph utilities.
142 Support for abbreviated forms of a number of ipfw options is
143 now deprecated. Warnings are printed to stderr indicating the
144 correct full form when a match occurs. Some abbreviations may
145 be supported at a later date based on user feedback. To be
146 considered for support, abbreviations must be in use prior to
147 this commit and unlikely to be confused with current key words.
150 By a popular demand, a lot of NOFOO options were renamed
151 to NO_FOO (see bsd.compat.mk for a full list). The old
152 spellings are still supported, but will cause annoying
153 warnings on stderr. Make sure you upgrade properly (see
154 the COMMON ITEMS: section later in this file).
157 Auto-loading of ancillary wlan modules such as wlan_wep has
158 been temporarily disabled; you need to statically configure
159 the modules you need into your kernel or explicitly load them
160 prior to use. Specifically, if you intend to use WEP encryption
161 with an 802.11 device load/configure wlan_wep; if you want to
162 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
163 and wlan_xauth as required.
166 The behaviour of ppp(8) has changed slightly. If lqr is enabled
167 (``enable lqr''), older versions would revert to LCP ECHO mode on
168 negotiation failure. Now, ``enable echo'' is required for this
169 behaviour. The ppp version number has been bumped to 3.4.2 to
173 The wlan support has been updated to split the crypto support
174 into separate modules. For static WEP you must configure the
175 wlan_wep module in your system or build and install the module
176 in place where it can be loaded (the kernel will auto-load
177 the module when a wep key is configured).
180 The ath driver has been updated to split the tx rate control
181 algorithm into a separate module. You need to include either
182 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
185 Support for systems with an 80386 CPU has been removed. Please
186 use FreeBSD 5.x or earlier on systems with an 80386.
189 We have had a hack which would mount the root filesystem
190 R/W if the device were named 'md*'. As part of the vnode
191 work I'm doing I have had to remove this hack. People
192 building systems which use preloaded MD root filesystems
193 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
194 their /etc/rc scripts.
197 FreeBSD 5.3 shipped here.
200 The size of struct tcpcb has changed again due to the removal
201 of RFC1644 T/TCP. You have to recompile userland programs that
202 read kmem for tcp sockets directly (netstat, sockstat, etc.)
205 The size of struct tcpcb has changed. You have to recompile
206 userland programs that read kmem for tcp sockets directly
207 (netstat, sockstat, etc.)
210 RELENG_5 branched here. For older entries, please see updating
211 in the RELENG_5 branch.
217 Avoid using make -j when upgrading. From time to time in the
218 past there have been problems using -j with buildworld and/or
219 installworld. This is especially true when upgrading between
220 "distant" versions (eg one that cross a major release boundary
221 or several minor releases, or when several months have passed
222 on the -current branch).
224 Sometimes, obscure build problems are the result of environment
225 poisoning. This can happen because the make utility reads its
226 environment when searching for values for global variables.
227 To run your build attempts in an "environmental clean room",
228 prefix all make commands with 'env -i '. See the env(1) manual
229 page for more details.
231 Due to several updates to the build infrastructure, source
232 upgrades from versions prior to 5.3 no longer supported.
236 If you are updating from a prior version of FreeBSD (even one just
237 a few days old), you should follow this procedure. With a
238 /usr/obj tree with a fresh buildworld,
239 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
240 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
242 To test a kernel once
243 ---------------------
244 If you just want to boot a kernel once (because you are not sure
245 if it works, or if you want to boot a known bad kernel to provide
246 debugging information) run
247 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
248 nextboot -k testkernel
250 To just build a kernel when you know that it won't mess you up
251 --------------------------------------------------------------
252 This assumes you are already running a 6.X system. Replace
253 ${arch} with the architecture of your machine (e.g. "i386",
254 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
256 cd src/sys/${arch}/conf
257 config KERNEL_NAME_HERE
258 cd ../compile/KERNEL_NAME_HERE
263 If this fails, go to the "To build a kernel" section.
265 To rebuild everything and install it on the current system.
266 -----------------------------------------------------------
267 # Note: sometimes if you are running current you gotta do more than
268 # is listed here if you are upgrading from a really old current.
270 <make sure you have good level 0 dumps>
272 make kernel KERNCONF=YOUR_KERNEL_HERE
274 <reboot in single user> [3]
281 To cross-install current onto a separate partition
282 --------------------------------------------------
283 # In this approach we use a separate partition to hold
284 # current's root, 'usr', and 'var' directories. A partition
285 # holding "/", "/usr" and "/var" should be about 2GB in
288 <make sure you have good level 0 dumps>
291 make buildkernel KERNCONF=YOUR_KERNEL_HERE
292 <maybe newfs current's root partition>
293 <mount current's root partition on directory ${CURRENT_ROOT}>
294 make installworld DESTDIR=${CURRENT_ROOT}
295 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
296 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
297 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
298 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
299 <reboot into current>
300 <do a "native" rebuild/install as described in the previous section>
301 <maybe install compatibility libraries from src/lib/compat>
305 To upgrade in-place from 5.x-stable or higher to 6.x-stable
306 -----------------------------------------------------------
307 <make sure you have good level 0 dumps>
309 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
311 <reboot in single user> [3]
317 Make sure that you've read the UPDATING file to understand the
318 tweaks to various things you need. At this point in the life
319 cycle of current, things change often and you are on your own
320 to cope. The defaults can also change, so please read ALL of
321 the UPDATING entries.
323 Also, if you are tracking -current, you must be subscribed to
324 freebsd-current@freebsd.org. Make sure that before you update
325 your sources that you have read and understood all the recent
326 messages there. If in doubt, please track -stable which has
329 [1] If you have third party modules, such as vmware, you
330 should disable them at this point so they don't crash your
333 [3] From the bootblocks, boot -s, and then do
338 adjkerntz -i # if CMOS is wall time
339 Also, when doing a major release upgrade, it is required that
340 you boot into single user mode to do the installworld.
342 [4] Note: This step is non-optional. Failure to do this step
343 can result in a significant reduction in the functionality of the
344 system. Attempting to do it by hand is not recommended and those
345 that pursue this avenue should read this file carefully, as well
346 as the archives of freebsd-current and freebsd-hackers mailing lists
347 for potential gotchas.
349 [5] Usually this step is a noop. However, from time to time
350 you may need to do this if you get unknown user in the following
351 step. It never hurts to do it all the time.
353 [8] In order to have a kernel that can run the 5.x binaries
354 needed to do an installworld, you must include the COMPAT_FREEBSD5
355 option in your kernel. Failure to do so may leave you with a system
356 that is hard to boot to recover.
358 Make sure that you merge any new devices from GENERIC since the
359 last time you updated your kernel config file.
361 [9] When checking out sources, you must include the -P flag to have
362 cvs prune empty directories.
364 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
365 "?=" instead of the "=" assignment operator, so that buildworld can
366 override the CPUTYPE if it needs to.
368 MAKEOBJDIRPREFIX must be defined in an environment variable, and
369 not on the command line, or in /etc/make.conf. buildworld will
370 warn if it is improperly defined.
373 This file contains a list, in reverse chronological order, of major
374 breakages in tracking -STABLE. Not all things will be listed here,
375 and it only starts on October 16, 2004. Updating files can found in
376 previous releases if your system is older than this.
378 Copyright information:
380 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
382 Redistribution, publication, translation and use, with or without
383 modification, in full or in part, in any form or format of this
384 document are permitted without further permission from the author.
386 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
387 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
388 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
389 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
390 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
391 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
392 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
393 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
394 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
395 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
396 POSSIBILITY OF SUCH DAMAGE.
398 If you find this document useful, and you want to, you may buy the
401 Contact Warner Losh if you have any questions about your use of