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