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 The support for Linux applications the 3dfx kernel module used
16 to provide is in a separate module named 3dfx_linux now. The
17 latter will pull in 3dfx.ko and linux.ko through its dependencies
21 An IPv6 support of ipfw was enabled by default. If you don't
22 want to filter an IPv6 by ipfw, please add following line into
25 pass ip6 from any to any
28 Now most modules get their build-time options from the kernel
29 configuration file. A few modules still have fixed options
30 due to their non-conformant implementation, but they will be
31 corrected eventually. You may need to review the options of
32 the modules in use, explicitly specify the non-default options
33 in the kernel configuration file, and rebuild the kernel and
37 The 'audit' group was added to support the new auditing functionality
38 in the base system. Be sure to follow the directions for updating,
39 including the requirement to run mergemaster -p.
42 The i386 loader(8) now defaults to the serial speed set by the
43 previous boot stage, if the comconsole is already in use. If
44 you've changed BOOT_COMCONSOLE_SPEED in make.conf(5) and
45 installed a new loader, but have not rebuilt and reinstalled the
46 boot blocks, then your loader will leave the console at 9600
47 baud. Either install the new boot blocks, or set
48 comconsole_speed in loader.conf(5). Note that the new boot
49 blocks also support a -S<speed> flag described in boot(8).
52 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
53 Its /etc/rc.conf.d configuration file has been `ppp' from
54 the beginning, and hence there is no need to touch it.
57 si(4)'s device files now contain the unit number.
58 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
61 A lot of fixes and new features in the soundsystem. To get all
62 benefits, you may want to recompile mplayer (if installed) after
63 booting the new world.
66 Bug fixes to the trimdomain(3) function in libutil may result in
67 slight changes to the host names appearing in log files under
68 relatively rare circumstances.
71 Scripts in the local_startup directories (as defined in
72 /etc/defaults/rc.conf) that have the new rc.d semantics will
73 now be run as part of the base system rcorder. If there are
74 errors or problems with one of these local scripts, it could
75 cause boot problems. If you encounter such problems, boot in
76 single user mode, remove that script from the */rc.d directory.
77 Please report the problem to the port's maintainer, and the
78 freebsd-ports@freebsd.org mailing list.
81 The setkey(8) utility was moved from /usr/sbin/setkey to /sbin/setkey.
82 You may want to update scripts which depend on its location.
85 rp(4)'s device files now contain the unit number.
86 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
92 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
93 to turn polling(4) on your interfaces.
96 The ai_addrlen of a struct addrinfo was changed to a socklen_t
97 to conform to POSIX-2001. This change broke an ABI
98 compatibility on 64 bit architecture. You have to recompile
99 userland programs that use getaddrinfo(3) on 64 bit
103 RELENG_6 branched here.
106 The pccard_ifconfig rc.conf variable has been removed and a new
107 variable, ifconfig_DEFAULT has been introduced. Unlike
108 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
109 do not have ifconfig_ifn entries rather than just those in
110 removable_interfaces.
113 Some previous versions of PAM have permitted the use of
114 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
115 to third party PAM modules in /usr/local/lib. A change has been
116 made to require the use of absolute paths in order to avoid
117 ambiguity and dependence on library path configuration, which may
118 affect existing configurations.
121 Major changes to network interface API. All drivers must be
122 recompiled. Drivers not in the base system will need to be
123 updated to the new APIs.
126 Changes were made to kinfo_proc in sys/user.h. Please recompile
127 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
128 will not behave correctly.
130 The API and ABI for hwpmc(4) have changed with the addition
131 of sampling support. Please recompile lib/libpmc(3) and
132 usr.sbin/{pmcstat,pmccontrol}.
135 The OpenBSD dhclient was imported in place of the ISC dhclient
136 and the network interface configuration scripts were updated
137 accordingly. If you use DHCP to configure your interfaces, you
138 must now run devd. Also, DNS updating was lost so you will need
139 to find a workaround if you use this feature.
142 if_bridge was added to the tree. This has changed struct ifnet.
143 Please recompile userland and all network related modules.
146 The n_net of a struct netent was changed to an uint32_t, and
147 1st argument of getnetbyaddr() was changed to an uint32_t, to
148 conform to POSIX-2001. These changes broke an ABI
149 compatibility on 64 bit architecture. With these changes,
150 shlib major of libpcap was bumped. You have to recompile
151 userland programs that use getnetbyaddr(3), getnetbyname(3),
152 getnetent(3) and/or libpcap on 64 bit architecture.
155 Kernel parsing of extra options on '#!' first lines of shell
156 scripts has changed. Lines with multiple options likely will
157 fail after this date. For full details, please see
158 http://people.freebsd.org/~gad/Updating-20050528.txt
161 The packet filter (pf) code has been updated to OpenBSD 3.7
162 Please note the changed anchor syntax and the fact that
163 authpf(8) now needs a mounted fdescfs(5) to function.
166 The NO_MIXED_MODE kernel option has been removed from the i386
167 amd64 platforms as its use has been superceded by the new local
168 APIC timer code. Any kernel config files containing this option
172 The on-disk format of LC_CTYPE files was changed to be machine
173 independent. Please make sure NOT to use NO_CLEAN buildworld
174 when crossing this point. Crossing this point also requires
175 recompile or reinstall of all locale depended packages.
178 The ifi_epoch member of struct if_data has been changed to
179 contain the uptime at which the interface was created or the
180 statistics zeroed rather then the wall clock time because
181 wallclock time may go backwards. This should have no impact
182 unless an snmp implementation is using this value (I know of
186 The acpi_perf and acpi_throttle drivers are now part of the
187 acpi(4) main module. They are no longer built separately.
190 The layout of struct image_params has changed. You have to
191 recompile all compatibility modules (linux, svr4, etc) for use
195 The p4tcc driver has been merged into cpufreq(4). This makes
196 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
197 compile in "device cpufreq" to restore this functionality.
200 The responsibility of recomputing the file system summary of
201 a SoftUpdates-enabled dirty volume has been transferred to the
202 background fsck. A rebuild of fsck(8) utility is recommended
203 if you have updated the kernel.
205 To get the old behavior (recompute file system summary at mount
206 time), you can set vfs.ffs.compute_summary_at_mount=1 before
207 mounting the new volume.
210 The cpufreq import is complete. As part of this, the sysctls for
211 acpi(4) throttling have been removed. The power_profile script
212 has been updated, so you can use performance/economy_cpu_freq in
213 rc.conf(5) to set AC on/offline cpu frequencies.
216 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
217 requires recompiling libnetgraph and userland netgraph utilities.
220 Support for abbreviated forms of a number of ipfw options is
221 now deprecated. Warnings are printed to stderr indicating the
222 correct full form when a match occurs. Some abbreviations may
223 be supported at a later date based on user feedback. To be
224 considered for support, abbreviations must be in use prior to
225 this commit and unlikely to be confused with current key words.
228 By a popular demand, a lot of NOFOO options were renamed
229 to NO_FOO (see bsd.compat.mk for a full list). The old
230 spellings are still supported, but will cause annoying
231 warnings on stderr. Make sure you upgrade properly (see
232 the COMMON ITEMS: section later in this file).
235 Auto-loading of ancillary wlan modules such as wlan_wep has
236 been temporarily disabled; you need to statically configure
237 the modules you need into your kernel or explicitly load them
238 prior to use. Specifically, if you intend to use WEP encryption
239 with an 802.11 device load/configure wlan_wep; if you want to
240 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
241 and wlan_xauth as required.
244 The behaviour of ppp(8) has changed slightly. If lqr is enabled
245 (``enable lqr''), older versions would revert to LCP ECHO mode on
246 negotiation failure. Now, ``enable echo'' is required for this
247 behaviour. The ppp version number has been bumped to 3.4.2 to
251 The wlan support has been updated to split the crypto support
252 into separate modules. For static WEP you must configure the
253 wlan_wep module in your system or build and install the module
254 in place where it can be loaded (the kernel will auto-load
255 the module when a wep key is configured).
258 The ath driver has been updated to split the tx rate control
259 algorithm into a separate module. You need to include either
260 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
263 Support for systems with an 80386 CPU has been removed. Please
264 use FreeBSD 5.x or earlier on systems with an 80386.
267 We have had a hack which would mount the root filesystem
268 R/W if the device were named 'md*'. As part of the vnode
269 work I'm doing I have had to remove this hack. People
270 building systems which use preloaded MD root filesystems
271 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
272 their /etc/rc scripts.
275 FreeBSD 5.3 shipped here.
278 The size of struct tcpcb has changed again due to the removal
279 of RFC1644 T/TCP. You have to recompile userland programs that
280 read kmem for tcp sockets directly (netstat, sockstat, etc.)
283 The size of struct tcpcb has changed. You have to recompile
284 userland programs that read kmem for tcp sockets directly
285 (netstat, sockstat, etc.)
288 RELENG_5 branched here. For older entries, please see updating
289 in the RELENG_5 branch.
295 Avoid using make -j when upgrading. From time to time in the
296 past there have been problems using -j with buildworld and/or
297 installworld. This is especially true when upgrading between
298 "distant" versions (eg one that cross a major release boundary
299 or several minor releases, or when several months have passed
300 on the -current branch).
302 Sometimes, obscure build problems are the result of environment
303 poisoning. This can happen because the make utility reads its
304 environment when searching for values for global variables.
305 To run your build attempts in an "environmental clean room",
306 prefix all make commands with 'env -i '. See the env(1) manual
307 page for more details.
309 Due to several updates to the build infrastructure, source
310 upgrades from versions prior to 5.3 no longer supported.
312 When upgrading from one major version to another it is generally
313 best to upgrade to the latest code in the currently installed branch
314 first, then do an upgrade to the new branch. This is the best-tested
315 upgrade path, and has the highest probability of being successful.
316 Please try this approach before reporting problems with a major
321 If you are updating from a prior version of FreeBSD (even one just
322 a few days old), you should follow this procedure. With a
323 /usr/obj tree with a fresh buildworld,
324 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
325 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
327 To test a kernel once
328 ---------------------
329 If you just want to boot a kernel once (because you are not sure
330 if it works, or if you want to boot a known bad kernel to provide
331 debugging information) run
332 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
333 nextboot -k testkernel
335 To just build a kernel when you know that it won't mess you up
336 --------------------------------------------------------------
337 This assumes you are already running a 6.X system. Replace
338 ${arch} with the architecture of your machine (e.g. "i386",
339 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
341 cd src/sys/${arch}/conf
342 config KERNEL_NAME_HERE
343 cd ../compile/KERNEL_NAME_HERE
348 If this fails, go to the "To build a kernel" section.
350 To rebuild everything and install it on the current system.
351 -----------------------------------------------------------
352 # Note: sometimes if you are running current you gotta do more than
353 # is listed here if you are upgrading from a really old current.
355 <make sure you have good level 0 dumps>
357 make kernel KERNCONF=YOUR_KERNEL_HERE
359 <reboot in single user> [3]
367 To cross-install current onto a separate partition
368 --------------------------------------------------
369 # In this approach we use a separate partition to hold
370 # current's root, 'usr', and 'var' directories. A partition
371 # holding "/", "/usr" and "/var" should be about 2GB in
374 <make sure you have good level 0 dumps>
377 make buildkernel KERNCONF=YOUR_KERNEL_HERE
378 <maybe newfs current's root partition>
379 <mount current's root partition on directory ${CURRENT_ROOT}>
380 make installworld DESTDIR=${CURRENT_ROOT}
381 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
382 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
383 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
384 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
385 <reboot into current>
386 <do a "native" rebuild/install as described in the previous section>
387 <maybe install compatibility libraries from src/lib/compat>
391 To upgrade in-place from 5.x-stable or higher to 6.x-stable
392 -----------------------------------------------------------
393 <make sure you have good level 0 dumps>
395 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
397 <reboot in single user> [3]
404 Make sure that you've read the UPDATING file to understand the
405 tweaks to various things you need. At this point in the life
406 cycle of current, things change often and you are on your own
407 to cope. The defaults can also change, so please read ALL of
408 the UPDATING entries.
410 Also, if you are tracking -current, you must be subscribed to
411 freebsd-current@freebsd.org. Make sure that before you update
412 your sources that you have read and understood all the recent
413 messages there. If in doubt, please track -stable which has
416 [1] If you have third party modules, such as vmware, you
417 should disable them at this point so they don't crash your
420 [3] From the bootblocks, boot -s, and then do
425 adjkerntz -i # if CMOS is wall time
426 Also, when doing a major release upgrade, it is required that
427 you boot into single user mode to do the installworld.
429 [4] Note: This step is non-optional. Failure to do this step
430 can result in a significant reduction in the functionality of the
431 system. Attempting to do it by hand is not recommended and those
432 that pursue this avenue should read this file carefully, as well
433 as the archives of freebsd-current and freebsd-hackers mailing lists
434 for potential gotchas.
436 [5] Usually this step is a noop. However, from time to time
437 you may need to do this if you get unknown user in the following
438 step. It never hurts to do it all the time.
440 [8] In order to have a kernel that can run the 5.x binaries
441 needed to do an installworld, you must include the COMPAT_FREEBSD5
442 option in your kernel. Failure to do so may leave you with a system
443 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
444 is required to run the 5.x binaries on more recent kernels.
446 Make sure that you merge any new devices from GENERIC since the
447 last time you updated your kernel config file.
449 [9] When checking out sources, you must include the -P flag to have
450 cvs prune empty directories.
452 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
453 "?=" instead of the "=" assignment operator, so that buildworld can
454 override the CPUTYPE if it needs to.
456 MAKEOBJDIRPREFIX must be defined in an environment variable, and
457 not on the command line, or in /etc/make.conf. buildworld will
458 warn if it is improperly defined.
461 This file contains a list, in reverse chronological order, of major
462 breakages in tracking -STABLE. Not all things will be listed here,
463 and it only starts on October 16, 2004. Updating files can found in
464 previous releases if your system is older than this.
466 Copyright information:
468 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
470 Redistribution, publication, translation and use, with or without
471 modification, in full or in part, in any form or format of this
472 document are permitted without further permission from the author.
474 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
475 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
476 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
477 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
478 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
479 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
480 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
481 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
482 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
483 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
484 POSSIBILITY OF SUCH DAMAGE.
486 If you find this document useful, and you want to, you may buy the
489 Contact Warner Losh if you have any questions about your use of