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
12 The ABI breakage in sendmail(8)'s libmilter has been repaired
13 so it is no longer necessary to recompile mail filters (aka,
14 milters). If you recompiled mail filters after the 20070411
15 note, it is not necessary to recompile them again.
18 sendmail(8) has been updated to version 8.14.1. Mail filters
19 (aka, milters) compiled against the libmilter included in the
20 base operating system should be recompiled.
26 The IEEE80211_IOC_STA_INFO ioctl was updated to take a mac
27 address parameter. Binaries using the old ioctl number will
28 continue to work but user applications that use this must
29 be updated (none exist in the base system).
32 The NMBCLUSTERS kernel option has been removed because it is obsolete.
33 Use the kern.ipc.nmbclusters loader(8) tunable instead.
36 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
37 for IPFIREWALL_FORWARD is now as it was before when it was first
38 committed and for years thereafter. The behaviour is now ON.
41 The interface version of the i4b kernel part has changed. So
42 after updating the kernel sources and compiling a new kernel,
43 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
44 be rebuilt, and vice versa. This also applies to other tools
45 using the i4b kernel interface to userland.
48 The iwi(4) was updated to use the firmware(9) framework. In order
49 for it to work you need a port change from net/iwi-firmware to
50 net/iwi-firmware-kmod.
56 The support for Linux applications the 3dfx kernel module used
57 to provide is in a separate module named 3dfx_linux now. The
58 latter will pull in 3dfx.ko and linux.ko through its dependencies
62 An IPv6 support of ipfw was enabled by default. If you don't
63 want to filter an IPv6 by ipfw, please add following line into
66 pass ip6 from any to any
69 Now most modules get their build-time options from the kernel
70 configuration file. A few modules still have fixed options
71 due to their non-conformant implementation, but they will be
72 corrected eventually. You may need to review the options of
73 the modules in use, explicitly specify the non-default options
74 in the kernel configuration file, and rebuild the kernel and
78 The 'audit' group was added to support the new auditing functionality
79 in the base system. Be sure to follow the directions for updating,
80 including the requirement to run mergemaster -p.
83 The i386 loader(8) now defaults to the serial speed set by the
84 previous boot stage, if the comconsole is already in use. If
85 you've changed BOOT_COMCONSOLE_SPEED in make.conf(5) and
86 installed a new loader, but have not rebuilt and reinstalled the
87 boot blocks, then your loader will leave the console at 9600
88 baud. Either install the new boot blocks, or set
89 comconsole_speed in loader.conf(5). Note that the new boot
90 blocks also support a -S<speed> flag described in boot(8).
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 si(4)'s device files now contain the unit number.
99 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
102 A lot of fixes and new features in the soundsystem. To get all
103 benefits, you may want to recompile mplayer (if installed) after
104 booting the new world.
107 Bug fixes to the trimdomain(3) function in libutil may result in
108 slight changes to the host names appearing in log files under
109 relatively rare circumstances.
112 Scripts in the local_startup directories (as defined in
113 /etc/defaults/rc.conf) that have the new rc.d semantics will
114 now be run as part of the base system rcorder. If there are
115 errors or problems with one of these local scripts, it could
116 cause boot problems. If you encounter such problems, boot in
117 single user mode, remove that script from the */rc.d directory.
118 Please report the problem to the port's maintainer, and the
119 freebsd-ports@freebsd.org mailing list.
122 The setkey(8) utility was moved from /usr/sbin/setkey to /sbin/setkey.
123 You may want to update scripts which depend on its location.
126 rp(4)'s device files now contain the unit number.
127 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
133 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
134 to turn polling(4) on your interfaces.
137 The ai_addrlen of a struct addrinfo was changed to a socklen_t
138 to conform to POSIX-2001. This change broke an ABI
139 compatibility on 64 bit architecture. You have to recompile
140 userland programs that use getaddrinfo(3) on 64 bit
144 RELENG_6 branched here.
147 The pccard_ifconfig rc.conf variable has been removed and a new
148 variable, ifconfig_DEFAULT has been introduced. Unlike
149 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
150 do not have ifconfig_ifn entries rather than just those in
151 removable_interfaces.
154 Some previous versions of PAM have permitted the use of
155 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
156 to third party PAM modules in /usr/local/lib. A change has been
157 made to require the use of absolute paths in order to avoid
158 ambiguity and dependence on library path configuration, which may
159 affect existing configurations.
162 Major changes to network interface API. All drivers must be
163 recompiled. Drivers not in the base system will need to be
164 updated to the new APIs.
167 Changes were made to kinfo_proc in sys/user.h. Please recompile
168 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
169 will not behave correctly.
171 The API and ABI for hwpmc(4) have changed with the addition
172 of sampling support. Please recompile lib/libpmc(3) and
173 usr.sbin/{pmcstat,pmccontrol}.
176 The OpenBSD dhclient was imported in place of the ISC dhclient
177 and the network interface configuration scripts were updated
178 accordingly. If you use DHCP to configure your interfaces, you
179 must now run devd. Also, DNS updating was lost so you will need
180 to find a workaround if you use this feature.
183 if_bridge was added to the tree. This has changed struct ifnet.
184 Please recompile userland and all network related modules.
187 The n_net of a struct netent was changed to an uint32_t, and
188 1st argument of getnetbyaddr() was changed to an uint32_t, to
189 conform to POSIX-2001. These changes broke an ABI
190 compatibility on 64 bit architecture. With these changes,
191 shlib major of libpcap was bumped. You have to recompile
192 userland programs that use getnetbyaddr(3), getnetbyname(3),
193 getnetent(3) and/or libpcap on 64 bit architecture.
196 Kernel parsing of extra options on '#!' first lines of shell
197 scripts has changed. Lines with multiple options likely will
198 fail after this date. For full details, please see
199 http://people.freebsd.org/~gad/Updating-20050528.txt
202 The packet filter (pf) code has been updated to OpenBSD 3.7
203 Please note the changed anchor syntax and the fact that
204 authpf(8) now needs a mounted fdescfs(5) to function.
207 The NO_MIXED_MODE kernel option has been removed from the i386
208 amd64 platforms as its use has been superceded by the new local
209 APIC timer code. Any kernel config files containing this option
213 The on-disk format of LC_CTYPE files was changed to be machine
214 independent. Please make sure NOT to use NO_CLEAN buildworld
215 when crossing this point. Crossing this point also requires
216 recompile or reinstall of all locale depended packages.
219 The ifi_epoch member of struct if_data has been changed to
220 contain the uptime at which the interface was created or the
221 statistics zeroed rather then the wall clock time because
222 wallclock time may go backwards. This should have no impact
223 unless an snmp implementation is using this value (I know of
227 The acpi_perf and acpi_throttle drivers are now part of the
228 acpi(4) main module. They are no longer built separately.
231 The layout of struct image_params has changed. You have to
232 recompile all compatibility modules (linux, svr4, etc) for use
236 The p4tcc driver has been merged into cpufreq(4). This makes
237 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
238 compile in "device cpufreq" to restore this functionality.
241 The responsibility of recomputing the file system summary of
242 a SoftUpdates-enabled dirty volume has been transferred to the
243 background fsck. A rebuild of fsck(8) utility is recommended
244 if you have updated the kernel.
246 To get the old behavior (recompute file system summary at mount
247 time), you can set vfs.ffs.compute_summary_at_mount=1 before
248 mounting the new volume.
251 The cpufreq import is complete. As part of this, the sysctls for
252 acpi(4) throttling have been removed. The power_profile script
253 has been updated, so you can use performance/economy_cpu_freq in
254 rc.conf(5) to set AC on/offline cpu frequencies.
257 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
258 requires recompiling libnetgraph and userland netgraph utilities.
261 Support for abbreviated forms of a number of ipfw options is
262 now deprecated. Warnings are printed to stderr indicating the
263 correct full form when a match occurs. Some abbreviations may
264 be supported at a later date based on user feedback. To be
265 considered for support, abbreviations must be in use prior to
266 this commit and unlikely to be confused with current key words.
269 By a popular demand, a lot of NOFOO options were renamed
270 to NO_FOO (see bsd.compat.mk for a full list). The old
271 spellings are still supported, but will cause annoying
272 warnings on stderr. Make sure you upgrade properly (see
273 the COMMON ITEMS: section later in this file).
276 Auto-loading of ancillary wlan modules such as wlan_wep has
277 been temporarily disabled; you need to statically configure
278 the modules you need into your kernel or explicitly load them
279 prior to use. Specifically, if you intend to use WEP encryption
280 with an 802.11 device load/configure wlan_wep; if you want to
281 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
282 and wlan_xauth as required.
285 The behaviour of ppp(8) has changed slightly. If lqr is enabled
286 (``enable lqr''), older versions would revert to LCP ECHO mode on
287 negotiation failure. Now, ``enable echo'' is required for this
288 behaviour. The ppp version number has been bumped to 3.4.2 to
292 The wlan support has been updated to split the crypto support
293 into separate modules. For static WEP you must configure the
294 wlan_wep module in your system or build and install the module
295 in place where it can be loaded (the kernel will auto-load
296 the module when a wep key is configured).
299 The ath driver has been updated to split the tx rate control
300 algorithm into a separate module. You need to include either
301 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
304 Support for systems with an 80386 CPU has been removed. Please
305 use FreeBSD 5.x or earlier on systems with an 80386.
308 We have had a hack which would mount the root filesystem
309 R/W if the device were named 'md*'. As part of the vnode
310 work I'm doing I have had to remove this hack. People
311 building systems which use preloaded MD root filesystems
312 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
313 their /etc/rc scripts.
316 FreeBSD 5.3 shipped here.
319 The size of struct tcpcb has changed again due to the removal
320 of RFC1644 T/TCP. You have to recompile userland programs that
321 read kmem for tcp sockets directly (netstat, sockstat, etc.)
324 The size of struct tcpcb has changed. You have to recompile
325 userland programs that read kmem for tcp sockets directly
326 (netstat, sockstat, etc.)
329 RELENG_5 branched here. For older entries, please see updating
330 in the RELENG_5 branch.
336 Avoid using make -j when upgrading. From time to time in the
337 past there have been problems using -j with buildworld and/or
338 installworld. This is especially true when upgrading between
339 "distant" versions (eg one that cross a major release boundary
340 or several minor releases, or when several months have passed
341 on the -current branch).
343 Sometimes, obscure build problems are the result of environment
344 poisoning. This can happen because the make utility reads its
345 environment when searching for values for global variables.
346 To run your build attempts in an "environmental clean room",
347 prefix all make commands with 'env -i '. See the env(1) manual
348 page for more details.
350 Due to several updates to the build infrastructure, source
351 upgrades from versions prior to 5.3 no longer supported.
353 When upgrading from one major version to another it is generally
354 best to upgrade to the latest code in the currently installed branch
355 first, then do an upgrade to the new branch. This is the best-tested
356 upgrade path, and has the highest probability of being successful.
357 Please try this approach before reporting problems with a major
362 If you are updating from a prior version of FreeBSD (even one just
363 a few days old), you should follow this procedure. With a
364 /usr/obj tree with a fresh buildworld,
365 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
366 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
368 To test a kernel once
369 ---------------------
370 If you just want to boot a kernel once (because you are not sure
371 if it works, or if you want to boot a known bad kernel to provide
372 debugging information) run
373 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
374 nextboot -k testkernel
376 To just build a kernel when you know that it won't mess you up
377 --------------------------------------------------------------
378 This assumes you are already running a 6.X system. Replace
379 ${arch} with the architecture of your machine (e.g. "i386",
380 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
382 cd src/sys/${arch}/conf
383 config KERNEL_NAME_HERE
384 cd ../compile/KERNEL_NAME_HERE
389 If this fails, go to the "To build a kernel" section.
391 To rebuild everything and install it on the current system.
392 -----------------------------------------------------------
393 # Note: sometimes if you are running current you gotta do more than
394 # is listed here if you are upgrading from a really old current.
396 <make sure you have good level 0 dumps>
398 make kernel KERNCONF=YOUR_KERNEL_HERE
400 <reboot in single user> [3]
408 To cross-install current onto a separate partition
409 --------------------------------------------------
410 # In this approach we use a separate partition to hold
411 # current's root, 'usr', and 'var' directories. A partition
412 # holding "/", "/usr" and "/var" should be about 2GB in
415 <make sure you have good level 0 dumps>
418 make buildkernel KERNCONF=YOUR_KERNEL_HERE
419 <maybe newfs current's root partition>
420 <mount current's root partition on directory ${CURRENT_ROOT}>
421 make installworld DESTDIR=${CURRENT_ROOT}
422 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
423 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
424 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
425 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
426 <reboot into current>
427 <do a "native" rebuild/install as described in the previous section>
428 <maybe install compatibility libraries from src/lib/compat>
432 To upgrade in-place from 5.x-stable or higher to 6.x-stable
433 -----------------------------------------------------------
434 <make sure you have good level 0 dumps>
436 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
438 <reboot in single user> [3]
445 Make sure that you've read the UPDATING file to understand the
446 tweaks to various things you need. At this point in the life
447 cycle of current, things change often and you are on your own
448 to cope. The defaults can also change, so please read ALL of
449 the UPDATING entries.
451 Also, if you are tracking -current, you must be subscribed to
452 freebsd-current@freebsd.org. Make sure that before you update
453 your sources that you have read and understood all the recent
454 messages there. If in doubt, please track -stable which has
457 [1] If you have third party modules, such as vmware, you
458 should disable them at this point so they don't crash your
461 [3] From the bootblocks, boot -s, and then do
466 adjkerntz -i # if CMOS is wall time
467 Also, when doing a major release upgrade, it is required that
468 you boot into single user mode to do the installworld.
470 [4] Note: This step is non-optional. Failure to do this step
471 can result in a significant reduction in the functionality of the
472 system. Attempting to do it by hand is not recommended and those
473 that pursue this avenue should read this file carefully, as well
474 as the archives of freebsd-current and freebsd-hackers mailing lists
475 for potential gotchas.
477 [5] Usually this step is a noop. However, from time to time
478 you may need to do this if you get unknown user in the following
479 step. It never hurts to do it all the time.
481 [8] In order to have a kernel that can run the 5.x binaries
482 needed to do an installworld, you must include the COMPAT_FREEBSD5
483 option in your kernel. Failure to do so may leave you with a system
484 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
485 is required to run the 5.x binaries on more recent kernels.
487 Make sure that you merge any new devices from GENERIC since the
488 last time you updated your kernel config file.
490 [9] When checking out sources, you must include the -P flag to have
491 cvs prune empty directories.
493 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
494 "?=" instead of the "=" assignment operator, so that buildworld can
495 override the CPUTYPE if it needs to.
497 MAKEOBJDIRPREFIX must be defined in an environment variable, and
498 not on the command line, or in /etc/make.conf. buildworld will
499 warn if it is improperly defined.
502 This file contains a list, in reverse chronological order, of major
503 breakages in tracking -STABLE. Not all things will be listed here,
504 and it only starts on October 16, 2004. Updating files can found in
505 previous releases if your system is older than this.
507 Copyright information:
509 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
511 Redistribution, publication, translation and use, with or without
512 modification, in full or in part, in any form or format of this
513 document are permitted without further permission from the author.
515 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
516 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
517 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
518 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
519 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
520 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
521 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
522 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
523 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
524 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
525 POSSIBILITY OF SUCH DAMAGE.
527 If you find this document useful, and you want to, you may buy the
530 Contact Warner Losh if you have any questions about your use of