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