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