1 Updating Information for FreeBSD current 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
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 8.x IS SLOW:
12 FreeBSD 8.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The 802.11 wireless support was redone to enable multi-bss
27 operation on devices that are capable. The underlying device
28 is no longer used directly but instead wlanX devices are
29 cloned with ifconfig. This requires changes to rc.conf files.
31 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
32 modules were merged into the base wlan module. All references
33 to these modules (e.g. in kernel config files) must be removed.
36 psm(4) has gained write(2) support in native operation level.
37 Arbitrary commands can be written to /dev/psm%d and status can
38 be read back from it. Therefore, an application is responsible
39 for status validation and error recovery. It is a no-op in
40 other operation levels.
43 Support for KSE threading has been removed from the kernel. To
44 run legacy applications linked against KSE libmap.conf may
45 be used. The following libmap.conf may be used to ensure
46 compatibility with any prior release:
48 libpthread.so.1 libthr.so.1
49 libpthread.so.2 libthr.so.2
50 libkse.so.3 libthr.so.3
53 The layout of struct vmspace has changed. This affects libkvm
54 and any executables that link against libkvm and use the
55 kvm_getprocs() function. In particular, but not exclusively,
56 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
57 The effects are minimal, but it's advisable to upgrade world
61 The latest em driver no longer has support in it for the
62 82575 adapter, this is now moved to the igb driver. The
63 split was done to make new features that are incompatible
64 with older hardware easier to do.
67 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
68 likewise the kernel option is now GEOM_LINUX_LVM.
71 The default NFS mount mode has changed from UDP to TCP for
72 increased reliability. If you rely on (insecurely) NFS
73 mounting across a firewall you may need to update your
77 Belatedly note the addition of m_collapse for compacting
81 The fts(3) structures have been changed to use adequate
82 integer types for their members and so to be able to cope
83 with huge file trees. The old fts(3) ABI is preserved
84 through symbol versioning in libc, so third-party binaries
85 using fts(3) should still work, although they will not take
86 advantage of the extended types. At the same time, some
87 third-party software might fail to build after this change
88 due to unportable assumptions made in its source code about
89 fts(3) structure members. Such software should be fixed
90 by its vendor or, in the worst case, in the ports tree.
91 FreeBSD_version 800015 marks this change for the unlikely
92 case that a portable fix is impossible.
95 To upgrade to -current after this date, you must be running
96 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
97 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
100 The ADAPTIVE_GIANT kernel option has been retired because its
101 functionality is the default now.
104 The AT keyboard emulation of sunkbd(4) has been turned on
105 by default. In order to make the special symbols of the Sun
106 keyboards driven by sunkbd(4) work under X these now have
107 to be configured the same way as Sun USB keyboards driven
108 by ukbd(4) (which also does AT keyboard emulation), f.e.:
110 Option "XkbLayout" "us"
111 Option "XkbRules" "xorg"
112 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
115 It has been decided that it is desirable to provide ABI
116 backwards compatibility to the FreeBSD 4/5/6 versions of the
117 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
118 broken with the introduction of PCI domain support (see the
119 20070930 entry). Unfortunately, this required the ABI of
120 PCIOCGETCONF to be broken again in order to be able to
121 provide backwards compatibility to the old version of that
122 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
123 again. As for prominent ports this affects neither pciutils
124 nor xorg-server this time, the hal port needs to be rebuilt
128 The misnamed kthread_create() and friends have been renamed
129 to kproc_create() etc. Many of the callers already
131 I will return kthread_create() and friends in a while
132 with implementations that actually create threads, not procs.
133 Renaming corresponds with version 800002.
139 Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and
140 WITHOUT_LIBTHR are set.
143 The PCI code has been made aware of PCI domains. This means that
144 the location strings as used by pciconf(8) etc are now in the
145 following format: pci<domain>:<bus>:<device>[:<function>]. It
146 also means that consumers of <sys/pciio.h> potentially need to
147 be recompiled; this includes the hal and xorg-server ports.
150 The caching daemon (cached) was renamed to nscd. nscd.conf
151 configuration file should be used instead of cached.conf and
152 nscd_enable, nscd_pidfile and nscd_flags options should be used
153 instead of cached_enable, cached_pidfile and cached_flags in
157 The getfacl(1) utility now prints owning user and group name
158 instead of owning uid and gid in the three line comment header.
159 This is the same behavior as getfacl(1) on Solaris and Linux.
162 The new IPsec code is now compiled in using the IPSEC option. The
163 IPSEC option now requires "device crypto" be defined in your kernel
164 configuration. The FAST_IPSEC kernel option is now deprecated.
167 The packet filter (pf) code has been updated to OpenBSD 4.1 Please
168 note the changed syntax - keep state is now on by default. Also
169 note the fact that ftp-proxy(8) has been changed from bottom up and
170 has been moved from libexec to usr/sbin. Changes in the ALTQ
171 handling also affect users of IPFW's ALTQ capabilities.
174 Remove KAME IPsec in favor of FAST_IPSEC, which is now the
175 only IPsec supported by FreeBSD. The new IPsec stack
176 supports both IPv4 and IPv6. The kernel option will change
177 after the code changes have settled in. For now the kernel
178 option IPSEC is deprecated and FAST_IPSEC is the only option, that
179 will change after some settling time.
182 The wicontrol(8) utility has been removed from the base system. wi(4)
183 cards should be configured using ifconfig(8), see the man page for more
187 The i386/amd64 GENERIC kernel now defaults to the nfe(4) driver
188 instead of the nve(4) driver. Please update your configuration
192 By default, /etc/rc.d/sendmail no longer rebuilds the aliases
193 database if it is missing or older than the aliases file. If
194 desired, set the new rc.conf option sendmail_rebuild_aliases
195 to "YES" to restore that functionality.
198 The IPv4 multicast socket code has been considerably modified, and
199 moved to the file sys/netinet/in_mcast.c. Initial support for the
200 RFC 3678 Source-Specific Multicast Socket API has been added to
201 the IPv4 network stack.
203 Strict multicast and broadcast reception is now the default for
204 UDP/IPv4 sockets; the net.inet.udp.strict_mcast_mship sysctl variable
205 has now been removed.
207 The RFC 1724 hack for interface selection has been removed; the use
208 of the Linux-derived ip_mreqn structure with IP_MULTICAST_IF has
209 been added to replace it. Consumers such as routed will soon be
210 updated to reflect this.
212 These changes affect users who are running routed(8) or rdisc(8)
213 from the FreeBSD base system on point-to-point or unnumbered
217 The net80211 layer has changed significantly and all wireless
218 drivers that depend on it need to be recompiled. Further these
219 changes require that any program that interacts with the wireless
220 support in the kernel be recompiled; this includes: ifconfig,
221 wpa_supplicant, hostapd, and wlanstats. Users must also, for
222 the moment, kldload the wlan_scan_sta and/or wlan_scan_ap modules
223 if they use modules for wireless support. These modules implement
224 scanning support for station and ap modes, respectively. Failure
225 to load the appropriate module before marking a wireless interface
226 up will result in a message to the console and the device not
230 The pam_nologin(8) module ceases to provide an authentication
231 function and starts providing an account management function.
232 Consequent changes to /etc/pam.d should be brought in using
233 mergemaster(8). Third-party files in /usr/local/etc/pam.d may
234 need manual editing as follows. Locate this line (or similar):
236 auth required pam_nologin.so no_warn
238 and change it according to this example:
240 account required pam_nologin.so no_warn
242 That is, the first word needs to be changed from "auth" to
243 "account". The new line can be moved to the account section
244 within the file for clarity. Not updating pam.conf(5) files
245 will result in nologin(5) ignored by the respective services.
248 The ether_ioctl() function has been synchronized with ioctl(2)
249 and ifnet.if_ioctl. Due to that, the size of one of its arguments
250 has changed on 64-bit architectures. All kernel modules using
251 ether_ioctl() need to be rebuilt on such architectures.
254 Improved INCLUDE_CONFIG_FILE support has been introduced to the
255 config(8) utility. In order to take advantage of this new
256 functionality, you are expected to recompile and install
257 src/usr.sbin/config. If you don't rebuild config(8), and your
258 kernel configuration depends on INCLUDE_CONFIG_FILE, the kernel
259 build will be broken because of a missing "kernconfstring"
263 Symbol versioning is enabled by default. To disable it, use
264 option WITHOUT_SYMVER. It is not advisable to attempt to
265 disable symbol versioning once it is enabled; your installworld
266 will break because a symbol version-less libc will get installed
267 before the install tools. As a result, the old install tools,
268 which previously had symbol dependencies to FBSD_1.0, will fail
269 because the freshly installed libc will not have them.
271 The default threading library (providing "libpthread") has been
272 changed to libthr. If you wish to have libkse as your default,
273 use option DEFAULT_THREAD_LIB=libkse for the buildworld.
276 The ABI breakage in sendmail(8)'s libmilter has been repaired
277 so it is no longer necessary to recompile mail filters (aka,
278 milters). If you recompiled mail filters after the 20070408
279 note, it is not necessary to recompile them again.
282 The new trunk(4) driver has been renamed to lagg(4) as it better
283 reflects its purpose. ifconfig will need to be recompiled.
286 sendmail(8) has been updated to version 8.14.1. Mail filters
287 (aka, milters) compiled against the libmilter included in the
288 base operating system should be recompiled.
291 Firmwares for ipw(4) and iwi(4) are now included in the base tree.
292 In order to use them one must agree to the respective LICENSE in
293 share/doc/legal and define legal.intel_<name>.license_ack=1 via
294 loader.conf(5) or kenv(1). Make sure to deinstall the now
295 deprecated modules from the respective firmware ports.
298 The name resolution/mapping functions addr2ascii(3) and ascii2addr(3)
299 were removed from FreeBSD's libc. These originally came from INRIA
300 IPv6. Nothing in FreeBSD ever used them. They may be regarded as
301 deprecated in previous releases.
302 The AF_LINK support for getnameinfo(3) was merged from NetBSD to
303 replace it as a more portable (and re-entrant) API.
306 To support interrupt filtering a modification to the newbus API
307 has occurred, ABI was broken and __FreeBSD_version was bumped
308 to 700031. Please make sure that your kernel and modules are in
310 http://docs.freebsd.org/cgi/mid.cgi?20070221233124.GA13941
313 The IPv6 multicast forwarding code may now be loaded into GENERIC
314 kernels by loading the ip_mroute.ko module. This is built into the
315 module unless WITHOUT_INET6 or WITHOUT_INET6_SUPPORT options are
316 set; see src.conf(5) for more information.
319 The output of netstat -r has changed. Without -n, we now only
320 print a "network name" without the prefix length if the network
321 address and mask exactly match a Class A/B/C network, and an entry
322 exists in the nsswitch "networks" map.
323 With -n, we print the full unabbreviated CIDR network prefix in
324 the form "a.b.c.d/p". 0.0.0.0/0 is always printed as "default".
325 This change is in preparation for changes such as equal-cost
326 multipath, and to more generally assist operational deployment
327 of FreeBSD as a modern IPv4 router.
330 PIM has been turned on by default in the IPv4 multicast
331 routing code. The kernel option 'PIM' has now been removed.
332 PIM is now built by default if option 'MROUTING' is specified.
333 It may now be loaded into GENERIC kernels by loading the
337 Support for IPIP tunnels (VIFF_TUNNEL) in IPv4 multicast routing
338 has been removed. Its functionality may be achieved by explicitly
339 configuring gif(4) interfaces and using the 'phyint' keyword in
341 XORP does not support source-routed IPv4 multicast tunnels nor the
342 integrated IPIP tunneling, therefore it is not affected by this
343 change. The __FreeBSD_version macro has been bumped to 700030.
346 Support for PCI Message Signalled Interrupts has been
347 re-enabled in the bge driver, only for those chips which are
348 believed to support it properly. If there are any problems,
349 MSI can be disabled completely by setting the
350 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
354 Support for PCI Message Signalled Interrupts has been
355 disabled again in the bge driver. Many revisions of the
356 hardware fail to support it properly. Support can be
357 re-enabled by removing the #define of BGE_DISABLE_MSI in
358 "src/sys/dev/bge/if_bge.c".
361 Support for PCI Message Signalled Interrupts has been added
362 to the bge driver. If there are any problems, MSI can be
363 disabled completely by setting the 'hw.pci.enable_msi' and
364 'hw.pci.enable_msix' tunables to 0 in the loader.
367 The removal of several facets of the experimental Threading
368 system from the kernel means that the proc and thread structures
369 have changed quite a bit. I suggest all kernel modules that might
370 reference these structures be recompiled.. Especially the
374 Sound infrastructure has been updated with various fixes and
375 improvements. Most of the changes are pretty much transparent,
376 with exceptions of followings:
377 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
378 moved to their own dev sysctl nodes, for example:
379 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
380 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
381 own chardev in the form of "dsp%d.<function>%d", where <function>
382 is p = playback, r = record and v = virtual, respectively. Users
383 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
384 This does not affect those who are using "/dev/dsp".
387 The following binaries have been disconnected from the build:
388 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
389 and mount_std. The functionality of these programs has been
390 moved into the mount program. For example, to mount a devfs
391 filesystem, instead of using mount_devfs, use: "mount -t devfs".
392 This does not affect entries in /etc/fstab, since entries in
393 /etc/fstab are always processed with "mount -t fstype".
396 Support for PCI Message Signalled Interrupts on i386 and amd64
397 has been added to the kernel and various drivers will soon be
398 updated to use MSI when it is available. If there are any problems,
399 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
400 and 'hw.pci.enable_msix' tunables to 0 in the loader.
403 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
404 The lockmgr object layout has been changed as a result of having
405 a lock_object embedded in it. As a consequence all file system
406 kernel modules must be re-compiled. The mutex profiling man page
407 has not yet been updated to reflect this change.
410 KSE in the kernel has now been made optional and turned on by
411 default. Use 'nooption KSE' in your kernel config to turn it
412 off. All kernel modules *must* be recompiled after this change.
413 There-after, modules from a KSE kernel should be compatible with
414 modules from a NOKSE kernel due to the temporary padding fields
415 added to 'struct proc'.
418 mrouted and its utilities have been removed from the base system.
421 Some ioctl(2) command codes have changed. Full backward ABI
422 compatibility is provided if the "options COMPAT_FREEBSD6" is
423 present in the kernel configuration file. Make sure to add
424 this option to your kernel config file, or recompile X.Org
425 and the rest of ports; otherwise they may refuse to work.
428 tcpslice has been removed from the base system.
431 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
432 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
433 systat needs to be rebuilt.
436 libpcap updated to v0.9.4 and tcpdump to v3.9.4
439 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
440 for IPFIREWALL_FORWARD is now as it was before when it was first
441 committed and for years after. The behaviour is now ON.
444 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
445 Now it can decrypt files created from different architectures.
446 Unfortunately, it is no longer able to decrypt a cipher text
447 generated with an older version on 64 bit architectures.
448 If you have such a file, you need old utility to decrypt it.
451 The interface version of the i4b kernel part has changed. So
452 after updating the kernel sources and compiling a new kernel,
453 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
454 be rebuilt, and vice versa.
457 The XBOX kernel now defaults to the nfe(4) driver instead of
458 the nve(4) driver. Please update your configuration
462 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
463 PCnet family of NICs has been removed. The new le(4) driver serves
464 as an equivalent but cross-platform replacement with the pcn(4)
465 driver still providing performance-optimized support for the subset
466 of AMD Am79C971 PCnet-FAST and greater chips as before.
469 The machdep.* sysctls and the adjkerntz utility have been
470 modified a bit. The new adjkerntz utility uses the new
471 sysctl names and sysctlbyname() calls, so it may be impossible
472 to run an old /sbin/adjkerntz utility in single-user mode
473 with a new kernel. Replace the `adjkerntz -i' step before
474 `make installworld' with:
476 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
478 and proceed as usual with the rest of the installworld-stage
479 steps. Otherwise, you risk installing binaries with their
480 timestamp set several hours in the future, especially if
481 you are running with local time set to GMT+X hours.
484 The ip6fw utility has been removed. The behavior provided by
485 ip6fw has been in ipfw2 for a good while and the rc.d scripts
486 have been updated to deal with it. There are some rules that
487 might not migrate cleanly. Use rc.firewall6 as a template to
491 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
492 attachments have been removed. Make sure to configure scc(4)
493 on sparc64. Note also that by default puc(4) will use uart(4)
494 and not sio(4) for serial ports because interrupt handling has
495 been optimized for multi-port serial cards and only uart(4)
496 implements the interface to support it.
499 The scc(4) driver replaces puc(4) for Serial Communications
500 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
501 Z8530. On sparc64, it is advised to add scc(4) to the kernel
502 configuration to make sure that the serial ports remain
506 Most world/kernel related NO_* build options changed names.
507 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
508 after FreeBSD ports) and should be set in /etc/src.conf
509 (the src.conf(5) manpage is provided). Full backwards
510 compatibility is maintained for the time being though it's
511 highly recommended to start moving old options out of the
512 system-wide /etc/make.conf file into the new /etc/src.conf
513 while also properly renaming them. More conversions will
514 likely follow. Posting to current@:
516 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
519 The NETSMBCRYPTO kernel option has been retired because its
520 functionality is always included in NETSMB and smbfs.ko now.
523 The TDFX_LINUX kernel option was retired and replaced by the
524 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
525 kernel module. Loading it alone should suffice to get 3dfx support
526 for Linux apps because it will pull in 3dfx.ko and linux.ko through
530 The 'audit' group was added to support the new auditing functionality
531 in the base system. Be sure to follow the directions for updating,
532 including the requirement to run mergemaster -p.
535 The kernel ABI to file system modules was changed on i386.
536 Please make sure that your kernel and modules are in sync.
539 This actually occured some time ago, but installing the kernel
540 now also installs a bunch of symbol files for the kernel modules.
541 This increases the size of /boot/kernel to about 67Mbytes. You
542 will need twice this if you will eventually back this up to kernel.old
543 on your next install.
544 If you have a shortage of room in your root partition, you should add
545 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
546 to your /etc/make.conf.
549 libc's malloc implementation has been replaced. This change has the
550 potential to uncover application bugs that previously went unnoticed.
551 See the malloc(3) manual page for more details.
554 The generic netgraph(4) cookie has been changed. If you upgrade
555 kernel passing this point, you also need to upgrade userland
556 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
559 si(4)'s device files now contain the unit number.
560 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
563 The kernel ABI was mostly destroyed due to a change in the size
564 of struct lock_object which is nested in other structures such
565 as mutexes which are nested in all sorts of other structures.
566 Make sure your kernel and modules are in sync.
569 The page coloring algorithm in the VM subsystem was converted
570 from tuning with kernel options to autotuning. Please remove
571 any PQ_* option except PQ_NOOPT from your kernel config.
574 The net80211-related tools in the tools/tools/ath directory
575 have been moved to tools/tools/net80211 and renamed with a
576 "wlan" prefix. Scripts that use them should be adjusted
580 Scripts in the local_startup directories (as defined in
581 /etc/defaults/rc.conf) that have the new rc.d semantics will
582 now be run as part of the base system rcorder. If there are
583 errors or problems with one of these local scripts, it could
584 cause boot problems. If you encounter such problems, boot in
585 single user mode, remove that script from the */rc.d directory.
586 Please report the problem to the port's maintainer, and the
587 freebsd-ports@freebsd.org mailing list.
590 The nodev mount option was deprecated in RELENG_6 (where it
591 was a no-op), and is now unsupported. If you have nodev or dev listed
592 in /etc/fstab, remove it, otherwise it will result in a mount error.
595 ABI between ipfw(4) and ipfw(8) has been changed. You need
596 to rebuild ipfw(8) when rebuilding kernel.
599 rp(4)'s device files now contain the unit number.
600 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
603 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
604 Its /etc/rc.conf.d configuration file has been `ppp' from
605 the beginning, and hence there is no need to touch it.
608 Now most modules get their build-time options from the kernel
609 configuration file. A few modules still have fixed options
610 due to their non-conformant implementation, but they will be
611 corrected eventually. You may need to review the options of
612 the modules in use, explicitly specify the non-default options
613 in the kernel configuration file, and rebuild the kernel and
617 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
618 to turn polling(4) on your interfaces.
621 The old bridge(4) implementation was retired. The new
622 if_bridge(4) serves as a full functional replacement.
625 The ai_addrlen of a struct addrinfo was changed to a socklen_t
626 to conform to POSIX-2001. This change broke an ABI
627 compatibility on 64 bit architecture. You have to recompile
628 userland programs that use getaddrinfo(3) on 64 bit
632 RELENG_6 branched here.
635 The pccard_ifconfig rc.conf variable has been removed and a new
636 variable, ifconfig_DEFAULT has been introduced. Unlike
637 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
638 do not have ifconfig_ifn entries rather than just those in
639 removable_interfaces.
642 Some previous versions of PAM have permitted the use of
643 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
644 to third party PAM modules in /usr/local/lib. A change has been
645 made to require the use of absolute paths in order to avoid
646 ambiguity and dependence on library path configuration, which may
647 affect existing configurations.
650 Major changes to network interface API. All drivers must be
651 recompiled. Drivers not in the base system will need to be
652 updated to the new APIs.
655 Changes were made to kinfo_proc in sys/user.h. Please recompile
656 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
657 will not behave correctly.
659 The API and ABI for hwpmc(4) have changed with the addition
660 of sampling support. Please recompile lib/libpmc(3) and
661 usr.sbin/{pmcstat,pmccontrol}.
664 The OpenBSD dhclient was imported in place of the ISC dhclient
665 and the network interface configuration scripts were updated
666 accordingly. If you use DHCP to configure your interfaces, you
667 must now run devd. Also, DNS updating was lost so you will need
668 to find a workaround if you use this feature.
670 The '_dhcp' user was added to support the OpenBSD dhclient. Be
671 sure to run mergemaster -p (like you are supposed to do every time
675 if_bridge was added to the tree. This has changed struct ifnet.
676 Please recompile userland and all network related modules.
679 The n_net of a struct netent was changed to an uint32_t, and
680 1st argument of getnetbyaddr() was changed to an uint32_t, to
681 conform to POSIX-2001. These changes broke an ABI
682 compatibility on 64 bit architecture. With these changes,
683 shlib major of libpcap was bumped. You have to recompile
684 userland programs that use getnetbyaddr(3), getnetbyname(3),
685 getnetent(3) and/or libpcap on 64 bit architecture.
688 Kernel parsing of extra options on '#!' first lines of shell
689 scripts has changed. Lines with multiple options likely will
690 fail after this date. For full details, please see
691 http://people.freebsd.org/~gad/Updating-20050528.txt
694 The packet filter (pf) code has been updated to OpenBSD 3.7
695 Please note the changed anchor syntax and the fact that
696 authpf(8) now needs a mounted fdescfs(5) to function.
699 The NO_MIXED_MODE kernel option has been removed from the i386
700 amd64 platforms as its use has been superceded by the new local
701 APIC timer code. Any kernel config files containing this option
705 The on-disk format of LC_CTYPE files was changed to be machine
706 independent. Please make sure NOT to use NO_CLEAN buildworld
707 when crossing this point. Crossing this point also requires
708 recompile or reinstall of all locale depended packages.
711 The ifi_epoch member of struct if_data has been changed to
712 contain the uptime at which the interface was created or the
713 statistics zeroed rather then the wall clock time because
714 wallclock time may go backwards. This should have no impact
715 unless an snmp implementation is using this value (I know of
719 The acpi_perf and acpi_throttle drivers are now part of the
720 acpi(4) main module. They are no longer built separately.
723 The layout of struct image_params has changed. You have to
724 recompile all compatibility modules (linux, svr4, etc) for use
728 The p4tcc driver has been merged into cpufreq(4). This makes
729 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
730 compile in "device cpufreq" to restore this functionality.
733 The responsibility of recomputing the file system summary of
734 a SoftUpdates-enabled dirty volume has been transferred to the
735 background fsck. A rebuild of fsck(8) utility is recommended
736 if you have updated the kernel.
738 To get the old behavior (recompute file system summary at mount
739 time), you can set vfs.ffs.compute_summary_at_mount=1 before
740 mounting the new volume.
743 The cpufreq import is complete. As part of this, the sysctls for
744 acpi(4) throttling have been removed. The power_profile script
745 has been updated, so you can use performance/economy_cpu_freq in
746 rc.conf(5) to set AC on/offline cpu frequencies.
749 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
750 requires recompiling libnetgraph and userland netgraph utilities.
753 Support for abbreviated forms of a number of ipfw options is
754 now deprecated. Warnings are printed to stderr indicating the
755 correct full form when a match occurs. Some abbreviations may
756 be supported at a later date based on user feedback. To be
757 considered for support, abbreviations must be in use prior to
758 this commit and unlikely to be confused with current key words.
761 By a popular demand, a lot of NOFOO options were renamed
762 to NO_FOO (see bsd.compat.mk for a full list). The old
763 spellings are still supported, but will cause annoying
764 warnings on stderr. Make sure you upgrade properly (see
765 the COMMON ITEMS: section later in this file).
768 Auto-loading of ancillary wlan modules such as wlan_wep has
769 been temporarily disabled; you need to statically configure
770 the modules you need into your kernel or explicitly load them
771 prior to use. Specifically, if you intend to use WEP encryption
772 with an 802.11 device load/configure wlan_wep; if you want to
773 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
774 and wlan_xauth as required.
777 The behaviour of ppp(8) has changed slightly. If lqr is enabled
778 (``enable lqr''), older versions would revert to LCP ECHO mode on
779 negotiation failure. Now, ``enable echo'' is required for this
780 behaviour. The ppp version number has been bumped to 3.4.2 to
784 The wlan support has been updated to split the crypto support
785 into separate modules. For static WEP you must configure the
786 wlan_wep module in your system or build and install the module
787 in place where it can be loaded (the kernel will auto-load
788 the module when a wep key is configured).
791 The ath driver has been updated to split the tx rate control
792 algorithm into a separate module. You need to include either
793 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
796 Support for systems with an 80386 CPU has been removed. Please
797 use FreeBSD 5.x or earlier on systems with an 80386.
800 We have had a hack which would mount the root filesystem
801 R/W if the device were named 'md*'. As part of the vnode
802 work I'm doing I have had to remove this hack. People
803 building systems which use preloaded MD root filesystems
804 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
805 their /etc/rc scripts.
808 FreeBSD 5.3 shipped here.
811 The size of struct tcpcb has changed again due to the removal
812 of RFC1644 T/TCP. You have to recompile userland programs that
813 read kmem for tcp sockets directly (netstat, sockstat, etc.)
816 The size of struct tcpcb has changed. You have to recompile
817 userland programs that read kmem for tcp sockets directly
818 (netstat, sockstat, etc.)
821 RELENG_5 branched here. For older entries, please see updating
822 in the RELENG_5 branch.
828 Avoid using make -j when upgrading. From time to time in the
829 past there have been problems using -j with buildworld and/or
830 installworld. This is especially true when upgrading between
831 "distant" versions (eg one that cross a major release boundary
832 or several minor releases, or when several months have passed
833 on the -current branch).
835 Sometimes, obscure build problems are the result of environment
836 poisoning. This can happen because the make utility reads its
837 environment when searching for values for global variables.
838 To run your build attempts in an "environmental clean room",
839 prefix all make commands with 'env -i '. See the env(1) manual
840 page for more details.
842 When upgrading from one major version to another it is generally
843 best to upgrade to the latest code in the currently installed branch
844 first, then do an upgrade to the new branch. This is the best-tested
845 upgrade path, and has the highest probability of being successful.
846 Please try this approach before reporting problems with a major
851 If you are updating from a prior version of FreeBSD (even one just
852 a few days old), you should follow this procedure. It is the most
853 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
855 make kernel-toolchain
856 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
857 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
859 To test a kernel once
860 ---------------------
861 If you just want to boot a kernel once (because you are not sure
862 if it works, or if you want to boot a known bad kernel to provide
863 debugging information) run
864 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
865 nextboot -k testkernel
867 To just build a kernel when you know that it won't mess you up
868 --------------------------------------------------------------
869 This assumes you are already running a 5.X system. Replace
870 ${arch} with the architecture of your machine (e.g. "i386",
871 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
873 cd src/sys/${arch}/conf
874 config KERNEL_NAME_HERE
875 cd ../compile/KERNEL_NAME_HERE
880 If this fails, go to the "To build a kernel" section.
882 To rebuild everything and install it on the current system.
883 -----------------------------------------------------------
884 # Note: sometimes if you are running current you gotta do more than
885 # is listed here if you are upgrading from a really old current.
887 <make sure you have good level 0 dumps>
889 make kernel KERNCONF=YOUR_KERNEL_HERE
891 <reboot in single user> [3]
899 To cross-install current onto a separate partition
900 --------------------------------------------------
901 # In this approach we use a separate partition to hold
902 # current's root, 'usr', and 'var' directories. A partition
903 # holding "/", "/usr" and "/var" should be about 2GB in
906 <make sure you have good level 0 dumps>
909 make buildkernel KERNCONF=YOUR_KERNEL_HERE
910 <maybe newfs current's root partition>
911 <mount current's root partition on directory ${CURRENT_ROOT}>
912 make installworld DESTDIR=${CURRENT_ROOT}
913 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
914 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
915 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
916 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
917 <reboot into current>
918 <do a "native" rebuild/install as described in the previous section>
919 <maybe install compatibility libraries from src/lib/compat>
923 To upgrade in-place from 5.x-stable to current
924 ----------------------------------------------
925 <make sure you have good level 0 dumps>
927 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
929 <reboot in single user> [3]
936 Make sure that you've read the UPDATING file to understand the
937 tweaks to various things you need. At this point in the life
938 cycle of current, things change often and you are on your own
939 to cope. The defaults can also change, so please read ALL of
940 the UPDATING entries.
942 Also, if you are tracking -current, you must be subscribed to
943 freebsd-current@freebsd.org. Make sure that before you update
944 your sources that you have read and understood all the recent
945 messages there. If in doubt, please track -stable which has
948 [1] If you have third party modules, such as vmware, you
949 should disable them at this point so they don't crash your
952 [3] From the bootblocks, boot -s, and then do
957 adjkerntz -i # if CMOS is wall time
958 Also, when doing a major release upgrade, it is required that
959 you boot into single user mode to do the installworld.
961 [4] Note: This step is non-optional. Failure to do this step
962 can result in a significant reduction in the functionality of the
963 system. Attempting to do it by hand is not recommended and those
964 that pursue this avenue should read this file carefully, as well
965 as the archives of freebsd-current and freebsd-hackers mailing lists
966 for potential gotchas.
968 [5] Usually this step is a noop. However, from time to time
969 you may need to do this if you get unknown user in the following
970 step. It never hurts to do it all the time. You may need to
971 install a new mergemaster (cd src/usr.sbin/mergemaster && make
972 install) after the buildworld before this step if you last updated
973 from current before 20020224 or from -stable before 20020408.
975 [8] In order to have a kernel that can run the 4.x binaries
976 needed to do an installworld, you must include the COMPAT_FREEBSD4
977 option in your kernel. Failure to do so may leave you with a system
978 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
979 is required to run the 5.x binaries on more recent kernels.
981 Make sure that you merge any new devices from GENERIC since the
982 last time you updated your kernel config file.
984 [9] When checking out sources, you must include the -P flag to have
985 cvs prune empty directories.
987 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
988 "?=" instead of the "=" assignment operator, so that buildworld can
989 override the CPUTYPE if it needs to.
991 MAKEOBJDIRPREFIX must be defined in an environment variable, and
992 not on the command line, or in /etc/make.conf. buildworld will
993 warn if it is improperly defined.
996 This file contains a list, in reverse chronological order, of major
997 breakages in tracking -current. Not all things will be listed here,
998 and it only starts on October 16, 2004. Updating files can found in
999 previous releases if your system is older than this.
1001 Copyright information:
1003 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
1005 Redistribution, publication, translation and use, with or without
1006 modification, in full or in part, in any form or format of this
1007 document are permitted without further permission from the author.
1009 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1010 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1011 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1012 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1013 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1014 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1015 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1016 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1017 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1018 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1019 POSSIBILITY OF SUCH DAMAGE.
1021 If you find this document useful, and you want to, you may buy the
1024 Contact Warner Losh if you have any questions about your use of