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 AT keyboard emulation of sunkbd(4) has been turned on
13 by default. In order to make the special symbols of the Sun
14 keyboards driven by sunkbd(4) work under X these now have
15 to be configured the same way as Sun USB keyboards driven
16 by ukbd(4) (which also does AT keyboard emulation), f.e.:
18 Option "XkbLayout" "us"
19 Option "XkbRules" "xorg"
20 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
23 A breakage was introduced in libc and fixed later. Make sure
24 you have lib/Makefile rev 1.205.2.4. If it already breaks your
25 world, you can recover it by
27 - reboot to single user mode, make sure you use /rescue/sh
29 - use /rescue/chflags to remove schg flag on /lib/libc.so.6
30 - use /rescue/cp to copy libc.so.6 from /usr/obj to /lib/libc.so.6
31 - continue installworld, you should be fine now
34 An incorrect field size in an ioctl struct for if_bridge(4) has been
35 corrected, ifconfig(8) will need to be recompilied.
38 The ABI breakage in sendmail(8)'s libmilter has been repaired
39 so it is no longer necessary to recompile mail filters (aka,
40 milters). If you recompiled mail filters after the 20070411
41 note, it is not necessary to recompile them again.
44 sendmail(8) has been updated to version 8.14.1. Mail filters
45 (aka, milters) compiled against the libmilter included in the
46 base operating system should be recompiled.
52 The IEEE80211_IOC_STA_INFO ioctl was updated to take a mac
53 address parameter. Binaries using the old ioctl number will
54 continue to work but user applications that use this must
55 be updated (none exist in the base system).
58 The NMBCLUSTERS kernel option has been removed because it is obsolete.
59 Use the kern.ipc.nmbclusters loader(8) tunable instead.
62 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
63 for IPFIREWALL_FORWARD is now as it was before when it was first
64 committed and for years thereafter. The behaviour is now ON.
67 The interface version of the i4b kernel part has changed. So
68 after updating the kernel sources and compiling a new kernel,
69 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
70 be rebuilt, and vice versa. This also applies to other tools
71 using the i4b kernel interface to userland.
74 The iwi(4) was updated to use the firmware(9) framework. In order
75 for it to work you need a port change from net/iwi-firmware to
76 net/iwi-firmware-kmod.
82 The support for Linux applications the 3dfx kernel module used
83 to provide is in a separate module named 3dfx_linux now. The
84 latter will pull in 3dfx.ko and linux.ko through its dependencies
88 An IPv6 support of ipfw was enabled by default. If you don't
89 want to filter an IPv6 by ipfw, please add following line into
92 pass ip6 from any to any
95 Now most modules get their build-time options from the kernel
96 configuration file. A few modules still have fixed options
97 due to their non-conformant implementation, but they will be
98 corrected eventually. You may need to review the options of
99 the modules in use, explicitly specify the non-default options
100 in the kernel configuration file, and rebuild the kernel and
104 The 'audit' group was added to support the new auditing functionality
105 in the base system. Be sure to follow the directions for updating,
106 including the requirement to run mergemaster -p.
109 The i386 loader(8) now defaults to the serial speed set by the
110 previous boot stage, if the comconsole is already in use. If
111 you've changed BOOT_COMCONSOLE_SPEED in make.conf(5) and
112 installed a new loader, but have not rebuilt and reinstalled the
113 boot blocks, then your loader will leave the console at 9600
114 baud. Either install the new boot blocks, or set
115 comconsole_speed in loader.conf(5). Note that the new boot
116 blocks also support a -S<speed> flag described in boot(8).
119 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
120 Its /etc/rc.conf.d configuration file has been `ppp' from
121 the beginning, and hence there is no need to touch it.
124 si(4)'s device files now contain the unit number.
125 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
128 A lot of fixes and new features in the soundsystem. To get all
129 benefits, you may want to recompile mplayer (if installed) after
130 booting the new world.
133 Bug fixes to the trimdomain(3) function in libutil may result in
134 slight changes to the host names appearing in log files under
135 relatively rare circumstances.
138 Scripts in the local_startup directories (as defined in
139 /etc/defaults/rc.conf) that have the new rc.d semantics will
140 now be run as part of the base system rcorder. If there are
141 errors or problems with one of these local scripts, it could
142 cause boot problems. If you encounter such problems, boot in
143 single user mode, remove that script from the */rc.d directory.
144 Please report the problem to the port's maintainer, and the
145 freebsd-ports@freebsd.org mailing list.
148 The setkey(8) utility was moved from /usr/sbin/setkey to /sbin/setkey.
149 You may want to update scripts which depend on its location.
152 rp(4)'s device files now contain the unit number.
153 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
159 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
160 to turn polling(4) on your interfaces.
163 The ai_addrlen of a struct addrinfo was changed to a socklen_t
164 to conform to POSIX-2001. This change broke an ABI
165 compatibility on 64 bit architecture. You have to recompile
166 userland programs that use getaddrinfo(3) on 64 bit
170 RELENG_6 branched here.
173 The pccard_ifconfig rc.conf variable has been removed and a new
174 variable, ifconfig_DEFAULT has been introduced. Unlike
175 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
176 do not have ifconfig_ifn entries rather than just those in
177 removable_interfaces.
180 Some previous versions of PAM have permitted the use of
181 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
182 to third party PAM modules in /usr/local/lib. A change has been
183 made to require the use of absolute paths in order to avoid
184 ambiguity and dependence on library path configuration, which may
185 affect existing configurations.
188 Major changes to network interface API. All drivers must be
189 recompiled. Drivers not in the base system will need to be
190 updated to the new APIs.
193 Changes were made to kinfo_proc in sys/user.h. Please recompile
194 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
195 will not behave correctly.
197 The API and ABI for hwpmc(4) have changed with the addition
198 of sampling support. Please recompile lib/libpmc(3) and
199 usr.sbin/{pmcstat,pmccontrol}.
202 The OpenBSD dhclient was imported in place of the ISC dhclient
203 and the network interface configuration scripts were updated
204 accordingly. If you use DHCP to configure your interfaces, you
205 must now run devd. Also, DNS updating was lost so you will need
206 to find a workaround if you use this feature.
209 if_bridge was added to the tree. This has changed struct ifnet.
210 Please recompile userland and all network related modules.
213 The n_net of a struct netent was changed to an uint32_t, and
214 1st argument of getnetbyaddr() was changed to an uint32_t, to
215 conform to POSIX-2001. These changes broke an ABI
216 compatibility on 64 bit architecture. With these changes,
217 shlib major of libpcap was bumped. You have to recompile
218 userland programs that use getnetbyaddr(3), getnetbyname(3),
219 getnetent(3) and/or libpcap on 64 bit architecture.
222 Kernel parsing of extra options on '#!' first lines of shell
223 scripts has changed. Lines with multiple options likely will
224 fail after this date. For full details, please see
225 http://people.freebsd.org/~gad/Updating-20050528.txt
228 The packet filter (pf) code has been updated to OpenBSD 3.7
229 Please note the changed anchor syntax and the fact that
230 authpf(8) now needs a mounted fdescfs(5) to function.
233 The NO_MIXED_MODE kernel option has been removed from the i386
234 amd64 platforms as its use has been superceded by the new local
235 APIC timer code. Any kernel config files containing this option
239 The on-disk format of LC_CTYPE files was changed to be machine
240 independent. Please make sure NOT to use NO_CLEAN buildworld
241 when crossing this point. Crossing this point also requires
242 recompile or reinstall of all locale depended packages.
245 The ifi_epoch member of struct if_data has been changed to
246 contain the uptime at which the interface was created or the
247 statistics zeroed rather then the wall clock time because
248 wallclock time may go backwards. This should have no impact
249 unless an snmp implementation is using this value (I know of
253 The acpi_perf and acpi_throttle drivers are now part of the
254 acpi(4) main module. They are no longer built separately.
257 The layout of struct image_params has changed. You have to
258 recompile all compatibility modules (linux, svr4, etc) for use
262 The p4tcc driver has been merged into cpufreq(4). This makes
263 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
264 compile in "device cpufreq" to restore this functionality.
267 The responsibility of recomputing the file system summary of
268 a SoftUpdates-enabled dirty volume has been transferred to the
269 background fsck. A rebuild of fsck(8) utility is recommended
270 if you have updated the kernel.
272 To get the old behavior (recompute file system summary at mount
273 time), you can set vfs.ffs.compute_summary_at_mount=1 before
274 mounting the new volume.
277 The cpufreq import is complete. As part of this, the sysctls for
278 acpi(4) throttling have been removed. The power_profile script
279 has been updated, so you can use performance/economy_cpu_freq in
280 rc.conf(5) to set AC on/offline cpu frequencies.
283 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
284 requires recompiling libnetgraph and userland netgraph utilities.
287 Support for abbreviated forms of a number of ipfw options is
288 now deprecated. Warnings are printed to stderr indicating the
289 correct full form when a match occurs. Some abbreviations may
290 be supported at a later date based on user feedback. To be
291 considered for support, abbreviations must be in use prior to
292 this commit and unlikely to be confused with current key words.
295 By a popular demand, a lot of NOFOO options were renamed
296 to NO_FOO (see bsd.compat.mk for a full list). The old
297 spellings are still supported, but will cause annoying
298 warnings on stderr. Make sure you upgrade properly (see
299 the COMMON ITEMS: section later in this file).
302 Auto-loading of ancillary wlan modules such as wlan_wep has
303 been temporarily disabled; you need to statically configure
304 the modules you need into your kernel or explicitly load them
305 prior to use. Specifically, if you intend to use WEP encryption
306 with an 802.11 device load/configure wlan_wep; if you want to
307 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
308 and wlan_xauth as required.
311 The behaviour of ppp(8) has changed slightly. If lqr is enabled
312 (``enable lqr''), older versions would revert to LCP ECHO mode on
313 negotiation failure. Now, ``enable echo'' is required for this
314 behaviour. The ppp version number has been bumped to 3.4.2 to
318 The wlan support has been updated to split the crypto support
319 into separate modules. For static WEP you must configure the
320 wlan_wep module in your system or build and install the module
321 in place where it can be loaded (the kernel will auto-load
322 the module when a wep key is configured).
325 The ath driver has been updated to split the tx rate control
326 algorithm into a separate module. You need to include either
327 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
330 Support for systems with an 80386 CPU has been removed. Please
331 use FreeBSD 5.x or earlier on systems with an 80386.
334 We have had a hack which would mount the root filesystem
335 R/W if the device were named 'md*'. As part of the vnode
336 work I'm doing I have had to remove this hack. People
337 building systems which use preloaded MD root filesystems
338 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
339 their /etc/rc scripts.
342 FreeBSD 5.3 shipped here.
345 The size of struct tcpcb has changed again due to the removal
346 of RFC1644 T/TCP. You have to recompile userland programs that
347 read kmem for tcp sockets directly (netstat, sockstat, etc.)
350 The size of struct tcpcb has changed. You have to recompile
351 userland programs that read kmem for tcp sockets directly
352 (netstat, sockstat, etc.)
355 RELENG_5 branched here. For older entries, please see updating
356 in the RELENG_5 branch.
362 Avoid using make -j when upgrading. From time to time in the
363 past there have been problems using -j with buildworld and/or
364 installworld. This is especially true when upgrading between
365 "distant" versions (eg one that cross a major release boundary
366 or several minor releases, or when several months have passed
367 on the -current branch).
369 Sometimes, obscure build problems are the result of environment
370 poisoning. This can happen because the make utility reads its
371 environment when searching for values for global variables.
372 To run your build attempts in an "environmental clean room",
373 prefix all make commands with 'env -i '. See the env(1) manual
374 page for more details.
376 Due to several updates to the build infrastructure, source
377 upgrades from versions prior to 5.3 no longer supported.
379 When upgrading from one major version to another it is generally
380 best to upgrade to the latest code in the currently installed branch
381 first, then do an upgrade to the new branch. This is the best-tested
382 upgrade path, and has the highest probability of being successful.
383 Please try this approach before reporting problems with a major
388 If you are updating from a prior version of FreeBSD (even one just
389 a few days old), you should follow this procedure. With a
390 /usr/obj tree with a fresh buildworld,
391 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
392 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
394 To test a kernel once
395 ---------------------
396 If you just want to boot a kernel once (because you are not sure
397 if it works, or if you want to boot a known bad kernel to provide
398 debugging information) run
399 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
400 nextboot -k testkernel
402 To just build a kernel when you know that it won't mess you up
403 --------------------------------------------------------------
404 This assumes you are already running a 6.X system. Replace
405 ${arch} with the architecture of your machine (e.g. "i386",
406 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
408 cd src/sys/${arch}/conf
409 config KERNEL_NAME_HERE
410 cd ../compile/KERNEL_NAME_HERE
415 If this fails, go to the "To build a kernel" section.
417 To rebuild everything and install it on the current system.
418 -----------------------------------------------------------
419 # Note: sometimes if you are running current you gotta do more than
420 # is listed here if you are upgrading from a really old current.
422 <make sure you have good level 0 dumps>
424 make kernel KERNCONF=YOUR_KERNEL_HERE
426 <reboot in single user> [3]
434 To cross-install current onto a separate partition
435 --------------------------------------------------
436 # In this approach we use a separate partition to hold
437 # current's root, 'usr', and 'var' directories. A partition
438 # holding "/", "/usr" and "/var" should be about 2GB in
441 <make sure you have good level 0 dumps>
444 make buildkernel KERNCONF=YOUR_KERNEL_HERE
445 <maybe newfs current's root partition>
446 <mount current's root partition on directory ${CURRENT_ROOT}>
447 make installworld DESTDIR=${CURRENT_ROOT}
448 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
449 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
450 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
451 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
452 <reboot into current>
453 <do a "native" rebuild/install as described in the previous section>
454 <maybe install compatibility libraries from src/lib/compat>
458 To upgrade in-place from 5.x-stable or higher to 6.x-stable
459 -----------------------------------------------------------
460 <make sure you have good level 0 dumps>
462 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
464 <reboot in single user> [3]
471 Make sure that you've read the UPDATING file to understand the
472 tweaks to various things you need. At this point in the life
473 cycle of current, things change often and you are on your own
474 to cope. The defaults can also change, so please read ALL of
475 the UPDATING entries.
477 Also, if you are tracking -current, you must be subscribed to
478 freebsd-current@freebsd.org. Make sure that before you update
479 your sources that you have read and understood all the recent
480 messages there. If in doubt, please track -stable which has
483 [1] If you have third party modules, such as vmware, you
484 should disable them at this point so they don't crash your
487 [3] From the bootblocks, boot -s, and then do
492 adjkerntz -i # if CMOS is wall time
493 Also, when doing a major release upgrade, it is required that
494 you boot into single user mode to do the installworld.
496 [4] Note: This step is non-optional. Failure to do this step
497 can result in a significant reduction in the functionality of the
498 system. Attempting to do it by hand is not recommended and those
499 that pursue this avenue should read this file carefully, as well
500 as the archives of freebsd-current and freebsd-hackers mailing lists
501 for potential gotchas.
503 [5] Usually this step is a noop. However, from time to time
504 you may need to do this if you get unknown user in the following
505 step. It never hurts to do it all the time.
507 [8] In order to have a kernel that can run the 5.x binaries
508 needed to do an installworld, you must include the COMPAT_FREEBSD5
509 option in your kernel. Failure to do so may leave you with a system
510 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
511 is required to run the 5.x binaries on more recent kernels.
513 Make sure that you merge any new devices from GENERIC since the
514 last time you updated your kernel config file.
516 [9] When checking out sources, you must include the -P flag to have
517 cvs prune empty directories.
519 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
520 "?=" instead of the "=" assignment operator, so that buildworld can
521 override the CPUTYPE if it needs to.
523 MAKEOBJDIRPREFIX must be defined in an environment variable, and
524 not on the command line, or in /etc/make.conf. buildworld will
525 warn if it is improperly defined.
528 This file contains a list, in reverse chronological order, of major
529 breakages in tracking -STABLE. Not all things will be listed here,
530 and it only starts on October 16, 2004. Updating files can found in
531 previous releases if your system is older than this.
533 Copyright information:
535 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
537 Redistribution, publication, translation and use, with or without
538 modification, in full or in part, in any form or format of this
539 document are permitted without further permission from the author.
541 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
542 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
543 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
544 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
545 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
546 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
547 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
548 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
549 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
550 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
551 POSSIBILITY OF SUCH DAMAGE.
553 If you find this document useful, and you want to, you may buy the
556 Contact Warner Losh if you have any questions about your use of