1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 Items affecting the ports and packages system can be found in
10 /usr/ports/UPDATING. Please read that file before running portupgrade.
12 NOTE TO PEOPLE WHO THINK THAT FreeBSD 9.x IS SLOW:
13 FreeBSD 9.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
26 The man(1) utility has been replaced by a new version that no longer
27 uses /etc/manpath.config. Please consult man.conf(5) for how to
28 migrate local entries to the new format.
31 The copyright strings printed by login(1) and sshd(8) at the time of a
32 new connection have been removed to follow other operating systems and
36 A workaround for a fixed ld bug has been removed in kernel code,
37 so make sure that your system ld is built from sources after
38 revision 210245 (r211583 if building head kernel on stable/8,
39 r211584 for stable/7). A symptom of incorrect ld version is
40 different addresses for set_pcpu section and __start_set_pcpu
41 symbol in kernel and/or modules.
44 The $ipv6_prefer variable in rc.conf(5) has been split into
45 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
47 The $ip6addrctl_policy is a variable to choose a pre-defined
48 address selection policy set by ip6addrctl(8). A value
49 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
52 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
53 flag (see an entry of 20090926) is set on an interface with no
54 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
55 security reason. If you want IPv6 link-local address on all
56 interfaces by default, set this to "YES".
58 The old ipv6_prefer="YES" is equivalent to
59 ipv6_activate_all_interfaces="YES" and
60 ip6addrctl_policy="ipv6_prefer".
63 DTrace has grown support for userland tracing. Due to this, DTrace is
64 now i386 and amd64 only.
65 dtruss(1) is now installed by default on those systems and a new
66 kernel module is needed for userland tracing: fasttrap.
67 No changes to your kernel config file are necessary to enable
68 userland tracing, but you might consider adding 'STRIP=' and
69 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
70 to have informative userland stack traces in DTrace (ustack).
73 The acpi_aiboost(4) driver has been removed in favor of the new
74 aibs(4) driver. You should update your kernel configuration file.
77 BSD grep has been imported to the base system and it is built by
78 default. It is completely BSD licensed, highly GNU-compatible, uses
79 less memory than its GNU counterpart and has a small codebase.
80 However, it is slower than its GNU counterpart, which is mostly
81 noticeable for larger searches, for smaller ones it is measurable
82 but not significant. The reason is complex, the most important factor
83 is that we lack a modern and efficient regex library and GNU
84 overcomes this by optimizing the searches internally. Future work
85 on improving the regex performance is planned, for the meantime,
86 users that need better performance, can build GNU grep instead by
87 setting the WITH_GNU_GREP knob.
90 Due to the import of powerpc64 support, all existing powerpc kernel
91 configuration files must be updated with a machine directive like this:
92 machine powerpc powerpc
94 In addition, an updated config(8) is required to build powerpc kernels
98 A new version of ZFS (version 15) has been merged to -HEAD.
99 This version uses a python library for the following subcommands:
100 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
101 For full functionality of these commands the following port must
102 be installed: sysutils/py-zfs
105 'vm_page's are now hashed by physical address to an array of mutexes.
106 Currently this is only used to serialize access to hold_count. Over
107 time the page queue mutex will be peeled away. This changes the size
108 of pmap on every architecture. And requires all callers of vm_page_hold
109 and vm_page_unhold to be updated.
112 WITH_CTF can now be specified in src.conf (not recommended, there
113 are some problems with static executables), make.conf (would also
114 affect ports which do not use GNU make and do not override the
115 compile targets) or in the kernel config (via "makeoptions
117 When WITH_CTF was specified there before this was silently ignored,
118 so make sure that WITH_CTF is not used in places which could lead
119 to unwanted behavior.
122 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
123 to allow 32-bit compatibility on non-x86 platforms. All kernel
124 configurations on amd64 and ia64 platforms using these options must
125 be modified accordingly.
128 The utmp user accounting database has been replaced with utmpx,
129 the user accounting interface standardized by POSIX.
130 Unfortunately the semantics of utmp and utmpx don't match,
131 making it practically impossible to support both interfaces.
132 The user accounting database is used by tools like finger(1),
133 last(1), talk(1), w(1) and ac(8).
135 All applications in the base system use utmpx. This means only
136 local binaries (e.g. from the ports tree) may still use these
137 utmp database files. These applications must be rebuilt to make
140 After the system has been upgraded, it is safe to remove the old
141 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
142 assuming their contents is of no importance anymore. Old wtmp
143 databases can only be used by last(1) and ac(8) after they have
144 been converted to the new format using wtmpcvt(1).
147 Introduce the kernel thread "deadlock resolver" (which can be enabled
148 via the DEADLKRES option, see NOTES for more details) and the
149 sleepq_type() function for sleepqueues.
152 The rc.firewall and rc.firewall6 were unified, and
153 rc.firewall6 and rc.d/ip6fw were removed.
154 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
155 variables are obsoleted. Instead, the following new rc
156 variables are added to rc.d/ipfw:
158 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
159 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
160 firewall_simple_onet_ipv6, firewall_trusted_ipv6
162 The meanings correspond to the relevant IPv4 variables.
168 The default terminal emulation for syscons(4) has been changed
169 from cons25 to xterm on all platforms except pc98. This means
170 that the /etc/ttys file needs to be updated to ensure correct
171 operation of applications on the console.
173 The terminal emulation style can be toggled per window by using
174 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
175 options can be used to change the compile-time default back to
178 To prevent graphical artifacts, make sure the TERM environment
179 variable is set to match the terminal emulation that is being
180 performed by syscons(4).
183 The layout of the structure ieee80211req_scan_result has changed.
184 Applications that require wireless scan results (e.g. ifconfig(8))
185 from net80211 need to be recompiled.
187 Applications such as wpa_supplicant(8) may require a full world
188 build without using NO_CLEAN in order to get synchronized with the
192 The iwn(4) driver has been updated to support the 5000 and 5150 series.
193 There's one kernel module for each firmware. Adding "device iwnfw"
194 to the kernel configuration file means including all three firmware
195 images inside the kernel. If you want to include just the one for
196 your wireless card, use the the devices iwn4965fw, iwn5000fw or
200 The rc.d/network_ipv6, IPv6 configuration script has been integrated
201 into rc.d/netif. The changes are the following:
203 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
204 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
205 Note that both variables need the "inet6" keyword at the head.
207 Do not set $ipv6_network_interfaces manually if you do not
208 understand what you are doing. It is not needed in most cases.
210 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
213 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
214 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
216 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
217 all configured interfaces have "inet6 accept_rtadv" in the
218 $ifconfig_IF_ipv6. These are for backward compatibility.
220 3. A new variable $ipv6_prefer has been added. If NO, IPv6
221 functionality of interfaces with no corresponding
222 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
223 and the default address selection policy of ip6addrctl(8)
224 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
225 Note that if you want to configure IPv6 functionality on the
226 disabled interfaces after boot, first you need to clear the flag by
227 using ifconfig(8) like:
229 ifconfig em0 inet6 -ifdisabled
231 If YES, the default address selection policy is set as
234 The default value of $ipv6_prefer is NO.
236 4. If your system need to receive Router Advertisement messages,
237 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
238 scripts automatically invoke rtsol(8) when the interface becomes
239 UP. The Router Advertisement messages are used for SLAAC
240 (State-Less Address AutoConfiguration).
243 802.11s D3.03 support was committed. This is incompatible with the
244 previous code, which was based on D3.0.
247 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
248 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
249 control whether accepting Router Advertisement messages or not.
250 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
251 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
252 The ifconfig(8) utility now supports these flags.
255 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
256 mount(8) and -a option for df(1) to see them.
259 The old tunable hw.bus.devctl_disable has been superseded by
260 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
261 replaced by hw.bus.devctl_queue=0. The default for this new tunable
265 Remove the option STOP_NMI. The default action is now to use NMI only
266 for KDB via the newly introduced function stop_cpus_hard() and
267 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
270 The stable/8 branch created in subversion. This corresponds to the
271 RELENG_8 branch in CVS.
274 Bump the shared library version numbers for all libraries that do not
275 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
276 __FreeBSD_version to 800105.
279 Due to changes in the implementation of virtual network stack support,
280 all network-related kernel modules must be recompiled. As this change
281 breaks the ABI, bump __FreeBSD_version to 800104.
284 The TOE interface to the TCP syncache has been modified to remove
285 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
286 The cxgb driver is the only TOE consumer affected by this change, and
287 needs to be recompiled along with the kernel. As this change breaks
288 the ABI, bump __FreeBSD_version to 800103.
291 Padding has been added to struct tcpcb, sackhint and tcpstat in
292 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
293 maintaining the ABI. However, this change breaks the ABI, so bump
294 __FreeBSD_version to 800102. User space tools that rely on the size of
295 any of these structs (e.g. sockstat) need to be recompiled.
298 The NFS_LEGACYRPC option has been removed along with the old kernel
299 RPC implementation that this option selected. Kernel configurations
300 may need to be adjusted.
303 The network interface device nodes at /dev/net/<interface> have been
304 removed. All ioctl operations can be performed the normal way using
305 routing sockets. The kqueue functionality can generally be replaced
306 with routing sockets.
309 The documentation from the FreeBSD Documentation Project (Handbook,
310 FAQ, etc.) is now installed via packages by sysinstall(8) and under
311 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
314 The ABI of various structures related to the SYSV IPC API have been
315 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
316 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
320 Layout of struct vnet has changed as routing related variables were
321 moved to their own Vimage module. Modules need to be recompiled. Bump
322 __FreeBSD_version to 800099.
325 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
326 respectively. As long as no more than 16 groups per process are used,
327 no changes should be visible. When more than 16 groups are used, old
328 binaries may fail if they call getgroups() or getgrouplist() with
329 statically sized storage. Recompiling will work around this, but
330 applications should be modified to use dynamically allocated storage
331 for group arrays as POSIX.1-2008 does not cap an implementation's
332 number of supported groups at NGROUPS_MAX+1 as previous versions did.
334 NFS and portalfs mounts may also be affected as the list of groups is
335 truncated to 16. Users of NFS who use more than 16 groups, should
336 take care that negative group permissions are not used on the exported
337 file systems as they will not be reliable unless a GSSAPI based
338 authentication method is used.
341 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
342 option compiles in the support for adaptive spinning for lockmgrs
343 which want to enable it. The lockinit() function now accepts the flag
344 LK_ADAPTIVE in order to make the lock object subject to adaptive
345 spinning when both held in write and read mode.
348 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
349 changed. User applications that use this ioctl need to be rebuilt.
352 The layout of struct thread has changed. Kernel and modules need to
356 The layout of structs ifnet, domain, protosw and vnet_net has changed.
357 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
360 window(1) has been removed from the base system. It can now be
361 installed from ports. The port is called misc/window.
364 The way we are storing and accessing `routing table' entries has
365 changed. Programs reading the FIB, like netstat, need to be
369 A new netisr implementation has been added for FreeBSD 8. Network
370 file system modules, such as igmp, ipdivert, and others, should be
372 Bump __FreeBSD_version to 800096.
375 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
379 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
380 Bump __FreeBSD_version to 800094.
383 Add mnt_xflag field to 'struct mount'. File system modules need to be
385 Bump __FreeBSD_version to 800093.
388 The compiling option ADAPTIVE_SX has been retired while it has been
389 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
390 The KPI for sx_init_flags() changes as accepting flags:
391 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
392 been introduced in order to handle the reversed logic.
393 Bump __FreeBSD_version to 800092.
396 Add support for hierarchical jails. Remove global securelevel.
397 Bump __FreeBSD_version to 800091.
400 The layout of struct vnet_net has changed, therefore modules
402 Bump __FreeBSD_version to 800090.
405 The newly imported zic(8) produces a new format in the output. Please
406 run tzsetup(8) to install the newly created data to /etc/localtime.
409 The sysctl tree for the usb stack has renamed from hw.usb2.* to
410 hw.usb.* and is now consistent again with previous releases.
413 802.11 monitor mode support was revised and driver api's were changed.
414 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
415 of DLT_IEEE802_11. No user-visible data structures were changed but
416 applications that use DLT_IEEE802_11 may require changes.
417 Bump __FreeBSD_version to 800088.
420 The layout of the following structs has changed: sysctl_oid,
421 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
422 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
423 panics may be experienced. World rebuild is required for
424 correctly checking networking state from userland.
425 Bump __FreeBSD_version to 800085.
428 MLDv2 and Source-Specific Multicast (SSM) have been merged
429 to the IPv6 stack. VIMAGE hooks are in but not yet used.
430 The implementation of SSM within FreeBSD's IPv6 stack closely
431 follows the IPv4 implementation.
433 For kernel developers:
435 * The most important changes are that the ip6_output() and
436 ip6_input() paths no longer take the IN6_MULTI_LOCK,
437 and this lock has been downgraded to a non-recursive mutex.
439 * As with the changes to the IPv4 stack to support SSM, filtering
440 of inbound multicast traffic must now be performed by transport
441 protocols within the IPv6 stack. This does not apply to TCP and
442 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
444 * The KPIs used by IPv6 multicast are similar to those used by
445 the IPv4 stack, with the following differences:
446 * im6o_mc_filter() is analogous to imo_multicast_filter().
447 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
448 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
449 * IN6_LOOKUP_MULTI() has been deprecated and removed.
450 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
451 for MLDv1 have an additional 'timer' argument which is used to
452 jitter the initial membership report for the solicited-node
453 multicast membership on-link.
454 * This is not strictly needed for MLDv2, which already jitters
455 its report transmissions. However, the 'timer' argument is
456 preserved in case MLDv1 is active on the interface.
458 * The KAME linked-list based IPv6 membership implementation has
459 been refactored to use a vector similar to that used by the IPv4
461 Code which maintains a list of its own multicast memberships
462 internally, e.g. carp, has been updated to reflect the new
465 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
466 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
467 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
468 implementation constraint which needs to be addressed in HEAD.
470 For application developers:
472 * The changes are broadly similar to those made for the IPv4
475 * The use of IPv4 and IPv6 multicast socket options on the same
476 socket, using mapped addresses, HAS NOT been tested or supported.
478 * There are a number of issues with the implementation of various
479 IPv6 multicast APIs which need to be resolved in the API surface
480 before the implementation is fully compatible with KAME userland
481 use, and these are mostly to do with interface index treatment.
483 * The literature available discusses the use of either the delta / ASM
484 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
485 using setsourcefilter(3)/getsourcefilter(3). For more information
486 please refer to RFC 3768, 'Socket Interface Extensions for
487 Multicast Source Filters'.
489 * Applications which use the published RFC 3678 APIs should be fine.
491 For systems administrators:
493 * The mtest(8) utility has been refactored to support IPv6, in
494 addition to IPv4. Interface addresses are no longer accepted
495 as arguments, their names must be used instead. The utility
496 will map the interface name to its first IPv4 address as
497 returned by getifaddrs(3).
499 * The ifmcstat(8) utility has also been updated to print the MLDv2
500 endpoint state and source filter lists via sysctl(3).
502 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
503 loopback of IPv6 multicast datagrams by default; it defaults to 1
504 to preserve the existing behaviour. Disabling multicast loopback is
505 recommended for optimal system performance.
507 * The IPv6 MROUTING code has been changed to examine this sysctl
508 instead of attempting to perform a group lookup before looping
509 back forwarded datagrams.
511 Bump __FreeBSD_version to 800084.
514 Implement low-level Bluetooth HCI API.
515 Bump __FreeBSD_version to 800083.
518 The layout of struct malloc_type, used by modules to register new
519 memory allocation types, has changed. Most modules will need to
520 be rebuilt or panics may be experienced.
521 Bump __FreeBSD_version to 800081.
524 Anticipate overflowing inp_flags - add inp_flags2.
525 This changes most offsets in inpcb, so checking v4 connection
526 state will require a world rebuild.
527 Bump __FreeBSD_version to 800080.
530 Add an llentry to struct route and struct route_in6. Modules
531 embedding a struct route will need to be recompiled.
532 Bump __FreeBSD_version to 800079.
535 The size of rt_metrics_lite and by extension rtentry has changed.
536 Networking administration apps will need to be recompiled.
537 The route command now supports show as an alias for get, weighting
538 of routes, sticky and nostick flags to alter the behavior of stateful
540 Bump __FreeBSD_version to 800078.
543 Do not use Giant for kbdmux(4) locking. This is wrong and
544 apparently causing more problems than it solves. This will
545 re-open the issue where interrupt handlers may race with
546 kbdmux(4) in polling mode. Typical symptoms include (but
547 not limited to) duplicated and/or missing characters when
548 low level console functions (such as gets) are used while
549 interrupts are enabled (for example geli password prompt,
550 mountroot prompt etc.). Disabling kbdmux(4) may help.
553 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
554 kernel modules referencing any of the above need to be recompiled.
555 Bump __FreeBSD_version to 800075.
558 GEOM_PART has become the default partition slicer for storage devices,
559 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
560 introduces some changes:
562 MSDOS/EBR: the devices created from MSDOS extended partition entries
563 (EBR) can be named differently than with GEOM_MBR and are now symlinks
564 to devices with offset-based names. fstabs may need to be modified.
566 BSD: the "geometry does not match label" warning is harmless in most
567 cases but it points to problems in file system misalignment with
568 disk geometry. The "c" partition is now implicit, covers the whole
569 top-level drive and cannot be (mis)used by users.
571 General: Kernel dumps are now not allowed to be written to devices
572 whose partition types indicate they are meant to be used for file
573 systems (or, in case of MSDOS partitions, as something else than
576 Most of these changes date approximately from 200812.
579 The uscanner(4) driver has been removed from the kernel. This follows
580 Linux removing theirs in 2.6 and making libusb the default interface
584 The multicast forwarding code has been cleaned up. netstat(1)
585 only relies on KVM now for printing bandwidth upcall meters.
586 The IPv4 and IPv6 modules are split into ip_mroute_mod and
587 ip6_mroute_mod respectively. The config(5) options for statically
588 compiling this code remain the same, i.e. 'options MROUTING'.
591 Support for the IFF_NEEDSGIANT network interface flag has been
592 removed, which means that non-MPSAFE network device drivers are no
593 longer supported. In particular, if_ar, if_sr, and network device
594 drivers from the old (legacy) USB stack can no longer be built or
598 POSIX.1 Native Language Support (NLS) has been enabled in libc and
599 a bunch of new language catalog files have also been added.
600 This means that some common libc messages are now localized and
601 they depend on the LC_MESSAGES environmental variable.
604 The k8temp(4) driver has been renamed to amdtemp(4) since
605 support for Family 10 and Family 11 CPU families was added.
608 IGMPv3 and Source-Specific Multicast (SSM) have been merged
609 to the IPv4 stack. VIMAGE hooks are in but not yet used.
611 For kernel developers, the most important changes are that the
612 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
613 and this lock has been downgraded to a non-recursive mutex.
615 Transport protocols (UDP, Raw IP) are now responsible for filtering
616 inbound multicast traffic according to group membership and source
617 filters. The imo_multicast_filter() KPI exists for this purpose.
618 Transports which do not use multicast (SCTP, TCP) already reject
619 multicast by default. Forwarding and receive performance may improve
620 as a mutex acquisition is no longer needed in the ip_input()
621 low-level input path. in_addmulti() and in_delmulti() are shimmed
622 to new KPIs which exist to support SSM in-kernel.
624 For application developers, it is recommended that loopback of
625 multicast datagrams be disabled for best performance, as this
626 will still cause the lock to be taken for each looped-back
627 datagram transmission. The net.inet.ip.mcast.loop sysctl may
628 be tuned to 0 to disable loopback by default; it defaults to 1
629 to preserve the existing behaviour.
631 For systems administrators, to obtain best performance with
632 multicast reception and multiple groups, it is always recommended
633 that a card with a suitably precise hash filter is used. Hash
634 collisions will still result in the lock being taken within the
635 transport protocol input path to check group membership.
637 If deploying FreeBSD in an environment with IGMP snooping switches,
638 it is recommended that the net.inet.igmp.sendlocal sysctl remain
639 enabled; this forces 224.0.0.0/24 group membership to be announced
642 The size of 'struct igmpstat' has changed; netstat needs to be
643 recompiled to reflect this.
644 Bump __FreeBSD_version to 800070.
647 libusb20.so.1 is now installed as libusb.so.1 and the ports system
648 updated to use it. This requires a buildworld/installworld in order to
649 update the library and dependencies (usbconfig, etc). Its advisable to
650 rebuild all ports which uses libusb. More specific directions are given
651 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
652 libusb are no longer required and can be removed.
655 A workaround is committed to allow the creation of System V shared
656 memory segment of size > 2 GB on the 64-bit architectures.
657 Due to a limitation of the existing ABI, the shm_segsz member
658 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
659 wrong for large segments. Note that limits must be explicitly
660 raised to allow such segments to be created.
663 The layout of struct ifnet has changed, requiring a rebuild of all
664 network device driver modules.
667 The /dev handling for the new USB stack has changed, a
668 buildworld/installworld is required for libusb20.
671 The new USB2 stack has now been permanently moved in and all kernel and
672 module names reverted to their previous values (eg, usb, ehci, ohci,
673 ums, ...). The old usb stack can be compiled in by prefixing the name
674 with the letter 'o', the old usb modules have been removed.
675 Updating entry 20090216 for xorg and 20090215 for libmap may still
679 The rc.conf(5) option if_up_delay has been renamed to
680 defaultroute_delay to better reflect its purpose. If you have
681 customized this setting in /etc/rc.conf you need to update it to
685 xorg 7.4 wants to configure its input devices via hald which does not
686 yet work with USB2. If the keyboard/mouse does not work in xorg then
688 Option "AllowEmptyInput" "off"
689 to your ServerLayout section. This will cause X to use the configured
690 kbd and mouse sections from your xorg.conf.
693 The GENERIC kernels for all architectures now default to the new USB2
694 stack. No kernel config options or code have been removed so if a
695 problem arises please report it and optionally revert to the old USB
696 stack. If you are loading USB kernel modules or have a custom kernel
697 that includes GENERIC then ensure that usb names are also changed over,
698 eg uftdi -> usb2_serial_ftdi.
700 Older programs linked against the ports libusb 0.1 need to be
701 redirected to the new stack's libusb20. /etc/libmap.conf can
703 # Map old usb library to new one for usb2 stack
704 libusb-0.1.so.8 libusb20.so.1
707 All USB ethernet devices now attach as interfaces under the name ueN
708 (eg. ue0). This is to provide a predictable name as vendors often
709 change usb chipsets in a product without notice.
712 The ichsmb(4) driver has been changed to require SMBus slave
713 addresses be left-justified (xxxxxxx0b) rather than right-justified.
714 All of the other SMBus controller drivers require left-justified
715 slave addresses, so this change makes all the drivers provide the
719 INET6 statistics (struct ip6stat) was updated.
720 netstat(1) needs to be recompiled.
723 NTFS has been removed from GENERIC kernel on amd64 to match
724 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
725 will load ntfs.ko module automatically when NTFS support is
726 actually needed, unless ntfs.ko is not installed or security
727 level prohibits loading kernel modules. If either is the case,
728 "options NTFS" has to be added into kernel config.
731 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
732 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
733 800061. User space tools that rely on the size of struct tcpcb in
734 tcp_var.h (e.g. sockstat) need to be recompiled.
737 ng_tty(4) module updated to match the new TTY subsystem.
738 Due to API change, user-level applications must be updated.
739 New API support added to mpd5 CVS and expected to be present
740 in next mpd5.3 release.
743 With __FreeBSD_version 800060 the makefs tool is part of
744 the base system (it was a port).
747 The afdata and ifnet locks have been changed from mutexes to
748 rwlocks, network modules will need to be re-compiled.
751 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
752 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
753 The new code reduced struct rtentry{} by 16 bytes on 32-bit
754 architecture and 40 bytes on 64-bit architecture. The userland
755 applications "arp" and "ndp" have been updated accordingly.
756 The output from "netstat -r" shows only routing entries and
757 none of the L2 information.
760 __FreeBSD_version 800057 marks the switchover from the
761 binary ath hal to source code. Users must add the line:
763 options AH_SUPPORT_AR5416
765 to their kernel config files when specifying:
769 The ath_hal module no longer exists; the code is now compiled
770 together with the driver in the ath module. It is now
771 possible to tailor chip support (i.e. reduce the set of chips
772 and thereby the code size); consult ath_hal(4) for details.
775 __FreeBSD_version 800054 adds memory barriers to
776 <machine/atomic.h>, new interfaces to ifnet to facilitate
777 multiple hardware transmit queues for cards that support
778 them, and a lock-less ring-buffer implementation to
779 enable drivers to more efficiently manage queueing of
783 A new version of ZFS (version 13) has been merged to -HEAD.
784 This version has zpool attribute "listsnapshots" off by
785 default, which means "zfs list" does not show snapshots,
786 and is the same as Solaris behavior.
789 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
792 The uhci, ohci, ehci and slhci USB Host controller drivers have
793 been put into separate modules. If you load the usb module
794 separately through loader.conf you will need to load the
795 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
796 controller add the following to loader.conf:
802 The ABI used by the PMC toolset has changed. Please keep
803 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
807 atapci kernel module now includes only generic PCI ATA
808 driver. AHCI driver moved to ataahci kernel module.
809 All vendor-specific code moved into separate kernel modules:
810 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
811 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
812 atamarvell, atamicron, atanational, atanetcell, atanvidia,
813 atapromise, ataserverworks, atasiliconimage, atasis, atavia
816 The TTY subsystem of the kernel has been replaced by a new
817 implementation, which provides better scalability and an
818 improved driver model. Most common drivers have been migrated to
819 the new TTY subsystem, while others have not. The following
820 drivers have not yet been ported to the new TTY layer:
823 cy, digi, rc, rp, sio
829 ng_h4, ng_tty, ppp, sl, snp
831 Adding these drivers to your kernel configuration file shall
832 cause compilation to fail.
835 ntpd has been upgraded to 4.2.4p5.
838 OpenSSH has been upgraded to 5.1p1.
840 For many years, FreeBSD's version of OpenSSH preferred DSA
841 over RSA for host and user authentication keys. With this
842 upgrade, we've switched to the vendor's default of RSA over
843 DSA. This may cause upgraded clients to warn about unknown
844 host keys even for previously known hosts. Users should
845 follow the usual procedure for verifying host keys before
846 accepting the RSA key.
848 This can be circumvented by setting the "HostKeyAlgorithms"
849 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
852 Please note that the sequence of keys offered for
853 authentication has been changed as well. You may want to
854 specify IdentityFile in a different order to revert this
858 The sio(4) driver has been removed from the i386 and amd64
859 kernel configuration files. This means uart(4) is now the
860 default serial port driver on those platforms as well.
862 To prevent collisions with the sio(4) driver, the uart(4) driver
863 uses different names for its device nodes. This means the
864 onboard serial port will now most likely be called "ttyu0"
865 instead of "ttyd0". You may need to reconfigure applications to
866 use the new device names.
868 When using the serial port as a boot console, be sure to update
869 /boot/device.hints and /etc/ttys before booting the new kernel.
870 If you forget to do so, you can still manually specify the hints
871 at the loader prompt:
873 set hint.uart.0.at="isa"
874 set hint.uart.0.port="0x3F8"
875 set hint.uart.0.flags="0x10"
876 set hint.uart.0.irq="4"
880 The gpt(8) utility has been removed. Use gpart(8) to partition
884 The version that Linuxulator emulates was changed from 2.4.2
885 to 2.6.16. If you experience any problems with Linux binaries
886 please try to set sysctl compat.linux.osrelease to 2.4.2 and
887 if it fixes the problem contact emulation mailing list.
890 ISDN4BSD (I4B) was removed from the src tree. You may need to
891 update a your kernel configuration and remove relevant entries.
894 I have checked in code to support multiple routing tables.
895 See the man pages setfib(1) and setfib(2).
896 This is a hopefully backwards compatible version,
897 but to make use of it you need to compile your kernel
898 with options ROUTETABLES=2 (or more up to 16).
901 The 802.11 wireless support was redone to enable multi-bss
902 operation on devices that are capable. The underlying device
903 is no longer used directly but instead wlanX devices are
904 cloned with ifconfig. This requires changes to rc.conf files.
906 ifconfig_ath0="WPA DHCP"
909 ifconfig_wlan0="WPA DHCP"
910 see rc.conf(5) for more details. In addition, mergemaster of
911 /etc/rc.d is highly recommended. Simultaneous update of userland
912 and kernel wouldn't hurt either.
914 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
915 modules were merged into the base wlan module. All references
916 to these modules (e.g. in kernel config files) must be removed.
919 psm(4) has gained write(2) support in native operation level.
920 Arbitrary commands can be written to /dev/psm%d and status can
921 be read back from it. Therefore, an application is responsible
922 for status validation and error recovery. It is a no-op in
923 other operation levels.
926 Support for KSE threading has been removed from the kernel. To
927 run legacy applications linked against KSE libmap.conf may
928 be used. The following libmap.conf may be used to ensure
929 compatibility with any prior release:
931 libpthread.so.1 libthr.so.1
932 libpthread.so.2 libthr.so.2
933 libkse.so.3 libthr.so.3
936 The layout of struct vmspace has changed. This affects libkvm
937 and any executables that link against libkvm and use the
938 kvm_getprocs() function. In particular, but not exclusively,
939 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
940 The effects are minimal, but it's advisable to upgrade world
944 The latest em driver no longer has support in it for the
945 82575 adapter, this is now moved to the igb driver. The
946 split was done to make new features that are incompatible
947 with older hardware easier to do.
950 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
951 likewise the kernel option is now GEOM_LINUX_LVM.
954 The default NFS mount mode has changed from UDP to TCP for
955 increased reliability. If you rely on (insecurely) NFS
956 mounting across a firewall you may need to update your
960 Belatedly note the addition of m_collapse for compacting
964 The fts(3) structures have been changed to use adequate
965 integer types for their members and so to be able to cope
966 with huge file trees. The old fts(3) ABI is preserved
967 through symbol versioning in libc, so third-party binaries
968 using fts(3) should still work, although they will not take
969 advantage of the extended types. At the same time, some
970 third-party software might fail to build after this change
971 due to unportable assumptions made in its source code about
972 fts(3) structure members. Such software should be fixed
973 by its vendor or, in the worst case, in the ports tree.
974 FreeBSD_version 800015 marks this change for the unlikely
975 case that a portable fix is impossible.
978 To upgrade to -current after this date, you must be running
979 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
980 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
983 The ADAPTIVE_GIANT kernel option has been retired because its
984 functionality is the default now.
987 The AT keyboard emulation of sunkbd(4) has been turned on
988 by default. In order to make the special symbols of the Sun
989 keyboards driven by sunkbd(4) work under X these now have
990 to be configured the same way as Sun USB keyboards driven
991 by ukbd(4) (which also does AT keyboard emulation), f.e.:
993 Option "XkbLayout" "us"
994 Option "XkbRules" "xorg"
995 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
998 It has been decided that it is desirable to provide ABI
999 backwards compatibility to the FreeBSD 4/5/6 versions of the
1000 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1001 broken with the introduction of PCI domain support (see the
1002 20070930 entry). Unfortunately, this required the ABI of
1003 PCIOCGETCONF to be broken again in order to be able to
1004 provide backwards compatibility to the old version of that
1005 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1006 again. As for prominent ports this affects neither pciutils
1007 nor xorg-server this time, the hal port needs to be rebuilt
1011 The misnamed kthread_create() and friends have been renamed
1012 to kproc_create() etc. Many of the callers already
1013 used kproc_start()..
1014 I will return kthread_create() and friends in a while
1015 with implementations that actually create threads, not procs.
1016 Renaming corresponds with version 800002.
1025 Avoid using make -j when upgrading. While generally safe, there are
1026 sometimes problems using -j to upgrade. If your upgrade fails with
1027 -j, please try again without -j. From time to time in the past there
1028 have been problems using -j with buildworld and/or installworld. This
1029 is especially true when upgrading between "distant" versions (eg one
1030 that cross a major release boundary or several minor releases, or when
1031 several months have passed on the -current branch).
1033 Sometimes, obscure build problems are the result of environment
1034 poisoning. This can happen because the make utility reads its
1035 environment when searching for values for global variables. To run
1036 your build attempts in an "environmental clean room", prefix all make
1037 commands with 'env -i '. See the env(1) manual page for more details.
1039 When upgrading from one major version to another it is generally best
1040 to upgrade to the latest code in the currently installed branch first,
1041 then do an upgrade to the new branch. This is the best-tested upgrade
1042 path, and has the highest probability of being successful. Please try
1043 this approach before reporting problems with a major version upgrade.
1047 When upgrading the boot ZFS pool to a new version, always follow
1050 1.) recompile and reinstall the ZFS boot loader and boot block
1051 (this is part of "make buildworld" and "make installworld")
1053 2.) update the ZFS boot block on your boot drive
1055 The following example updates the ZFS boot block on the first
1056 partition (freebsd-boot) of a GPT partitioned drive ad0:
1057 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1059 Non-boot pools do not need these updates.
1063 If you are updating from a prior version of FreeBSD (even one just
1064 a few days old), you should follow this procedure. It is the most
1065 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1067 make kernel-toolchain
1068 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1069 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1071 To test a kernel once
1072 ---------------------
1073 If you just want to boot a kernel once (because you are not sure
1074 if it works, or if you want to boot a known bad kernel to provide
1075 debugging information) run
1076 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1077 nextboot -k testkernel
1079 To just build a kernel when you know that it won't mess you up
1080 --------------------------------------------------------------
1081 This assumes you are already running a CURRENT system. Replace
1082 ${arch} with the architecture of your machine (e.g. "i386",
1083 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1085 cd src/sys/${arch}/conf
1086 config KERNEL_NAME_HERE
1087 cd ../compile/KERNEL_NAME_HERE
1092 If this fails, go to the "To build a kernel" section.
1094 To rebuild everything and install it on the current system.
1095 -----------------------------------------------------------
1096 # Note: sometimes if you are running current you gotta do more than
1097 # is listed here if you are upgrading from a really old current.
1099 <make sure you have good level 0 dumps>
1101 make kernel KERNCONF=YOUR_KERNEL_HERE
1103 <reboot in single user> [3]
1111 To cross-install current onto a separate partition
1112 --------------------------------------------------
1113 # In this approach we use a separate partition to hold
1114 # current's root, 'usr', and 'var' directories. A partition
1115 # holding "/", "/usr" and "/var" should be about 2GB in
1118 <make sure you have good level 0 dumps>
1121 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1122 <maybe newfs current's root partition>
1123 <mount current's root partition on directory ${CURRENT_ROOT}>
1124 make installworld DESTDIR=${CURRENT_ROOT}
1125 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1126 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1127 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1128 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1129 <reboot into current>
1130 <do a "native" rebuild/install as described in the previous section>
1131 <maybe install compatibility libraries from ports/misc/compat*>
1135 To upgrade in-place from 8.x-stable to current
1136 ----------------------------------------------
1137 <make sure you have good level 0 dumps>
1139 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1141 <reboot in single user> [3]
1148 Make sure that you've read the UPDATING file to understand the
1149 tweaks to various things you need. At this point in the life
1150 cycle of current, things change often and you are on your own
1151 to cope. The defaults can also change, so please read ALL of
1152 the UPDATING entries.
1154 Also, if you are tracking -current, you must be subscribed to
1155 freebsd-current@freebsd.org. Make sure that before you update
1156 your sources that you have read and understood all the recent
1157 messages there. If in doubt, please track -stable which has
1158 much fewer pitfalls.
1160 [1] If you have third party modules, such as vmware, you
1161 should disable them at this point so they don't crash your
1164 [3] From the bootblocks, boot -s, and then do
1169 adjkerntz -i # if CMOS is wall time
1170 Also, when doing a major release upgrade, it is required that
1171 you boot into single user mode to do the installworld.
1173 [4] Note: This step is non-optional. Failure to do this step
1174 can result in a significant reduction in the functionality of the
1175 system. Attempting to do it by hand is not recommended and those
1176 that pursue this avenue should read this file carefully, as well
1177 as the archives of freebsd-current and freebsd-hackers mailing lists
1178 for potential gotchas. The -U option is also useful to consider.
1179 See mergemaster(8) for more information.
1181 [5] Usually this step is a noop. However, from time to time
1182 you may need to do this if you get unknown user in the following
1183 step. It never hurts to do it all the time. You may need to
1184 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1185 install) after the buildworld before this step if you last updated
1186 from current before 20020224 or from -stable before 20020408.
1188 [8] In order to have a kernel that can run the 4.x binaries needed to
1189 do an installworld, you must include the COMPAT_FREEBSD4 option in
1190 your kernel. Failure to do so may leave you with a system that is
1191 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1192 required to run the 5.x binaries on more recent kernels. And so on
1193 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1195 Make sure that you merge any new devices from GENERIC since the
1196 last time you updated your kernel config file.
1198 [9] When checking out sources, you must include the -P flag to have
1199 cvs prune empty directories.
1201 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1202 "?=" instead of the "=" assignment operator, so that buildworld can
1203 override the CPUTYPE if it needs to.
1205 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1206 not on the command line, or in /etc/make.conf. buildworld will
1207 warn if it is improperly defined.
1210 This file contains a list, in reverse chronological order, of major
1211 breakages in tracking -current. Not all things will be listed here,
1212 and it only starts on October 16, 2004. Updating files can found in
1213 previous releases if your system is older than this.
1215 Copyright information:
1217 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1219 Redistribution, publication, translation and use, with or without
1220 modification, in full or in part, in any form or format of this
1221 document are permitted without further permission from the author.
1223 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1224 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1225 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1226 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1227 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1228 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1229 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1230 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1231 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1232 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1233 POSSIBILITY OF SUCH DAMAGE.
1235 Contact Warner Losh if you have any questions about your use of