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 Generic IEEE 802.3 annex 31B full duplex flow control support has been
27 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
28 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
29 to take advantage of it instead of using custom implementations. This
30 means that these drivers now no longer unconditionally advertise
31 support for flow control but only do so if flow control is a selected
32 media option. This was implemented in the generic support that way in
33 order to allow flow control to be switched on and off via ifconfig(8)
34 with the PHY specific default to typically off in order to protect
35 from unwanted effects. Consequently, if you used flow control with
36 one of the above mentioned drivers you now need to explicitly enable
38 ifconfig bge0 media auto mediaopt flowcontrol
40 Along with the above mentioned changes generic support for setting
41 1000baseT master mode also has been added and brgphy(4), ciphy(4),
42 e1000phy(4) as well as ip1000phy(4) have been converted to take
43 advantage of it. This means that these drivers now no longer take the
44 link0 parameter for selecting master mode but the master media option
45 has to be used instead, for example like in the following:
46 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
48 Selection of master mode now is also available with all other PHY
49 drivers supporting 1000baseT.
52 The TCP stack has received a significant update to add support for
53 modularised congestion control and generally improve the clarity of
54 congestion control decisions. Bump __FreeBSD_version to 900025. User
55 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
56 sockstat) need to be recompiled.
59 The man(1) utility has been replaced by a new version that no longer
60 uses /etc/manpath.config. Please consult man.conf(5) for how to
61 migrate local entries to the new format.
64 The copyright strings printed by login(1) and sshd(8) at the time of a
65 new connection have been removed to follow other operating systems and
69 A workaround for a fixed ld bug has been removed in kernel code,
70 so make sure that your system ld is built from sources after
71 revision 210245 from 2010-07-19 (r211583 if building head kernel
72 on stable/8, r211584 for stable/7; both from 2010-08-21).
73 A symptom of incorrect ld version is different addresses for
74 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
77 The $ipv6_prefer variable in rc.conf(5) has been split into
78 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
80 The $ip6addrctl_policy is a variable to choose a pre-defined
81 address selection policy set by ip6addrctl(8). A value
82 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
85 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
86 flag (see an entry of 20090926) is set on an interface with no
87 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
88 security reason. If you want IPv6 link-local address on all
89 interfaces by default, set this to "YES".
91 The old ipv6_prefer="YES" is equivalent to
92 ipv6_activate_all_interfaces="YES" and
93 ip6addrctl_policy="ipv6_prefer".
96 DTrace has grown support for userland tracing. Due to this, DTrace is
97 now i386 and amd64 only.
98 dtruss(1) is now installed by default on those systems and a new
99 kernel module is needed for userland tracing: fasttrap.
100 No changes to your kernel config file are necessary to enable
101 userland tracing, but you might consider adding 'STRIP=' and
102 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
103 to have informative userland stack traces in DTrace (ustack).
106 The acpi_aiboost(4) driver has been removed in favor of the new
107 aibs(4) driver. You should update your kernel configuration file.
110 BSD grep has been imported to the base system and it is built by
111 default. It is completely BSD licensed, highly GNU-compatible, uses
112 less memory than its GNU counterpart and has a small codebase.
113 However, it is slower than its GNU counterpart, which is mostly
114 noticeable for larger searches, for smaller ones it is measurable
115 but not significant. The reason is complex, the most important factor
116 is that we lack a modern and efficient regex library and GNU
117 overcomes this by optimizing the searches internally. Future work
118 on improving the regex performance is planned, for the meantime,
119 users that need better performance, can build GNU grep instead by
120 setting the WITH_GNU_GREP knob.
123 Due to the import of powerpc64 support, all existing powerpc kernel
124 configuration files must be updated with a machine directive like this:
125 machine powerpc powerpc
127 In addition, an updated config(8) is required to build powerpc kernels
131 A new version of ZFS (version 15) has been merged to -HEAD.
132 This version uses a python library for the following subcommands:
133 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
134 For full functionality of these commands the following port must
135 be installed: sysutils/py-zfs
138 'vm_page's are now hashed by physical address to an array of mutexes.
139 Currently this is only used to serialize access to hold_count. Over
140 time the page queue mutex will be peeled away. This changes the size
141 of pmap on every architecture. And requires all callers of vm_page_hold
142 and vm_page_unhold to be updated.
145 WITH_CTF can now be specified in src.conf (not recommended, there
146 are some problems with static executables), make.conf (would also
147 affect ports which do not use GNU make and do not override the
148 compile targets) or in the kernel config (via "makeoptions
150 When WITH_CTF was specified there before this was silently ignored,
151 so make sure that WITH_CTF is not used in places which could lead
152 to unwanted behavior.
155 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
156 to allow 32-bit compatibility on non-x86 platforms. All kernel
157 configurations on amd64 and ia64 platforms using these options must
158 be modified accordingly.
161 The utmp user accounting database has been replaced with utmpx,
162 the user accounting interface standardized by POSIX.
163 Unfortunately the semantics of utmp and utmpx don't match,
164 making it practically impossible to support both interfaces.
165 The user accounting database is used by tools like finger(1),
166 last(1), talk(1), w(1) and ac(8).
168 All applications in the base system use utmpx. This means only
169 local binaries (e.g. from the ports tree) may still use these
170 utmp database files. These applications must be rebuilt to make
173 After the system has been upgraded, it is safe to remove the old
174 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
175 assuming their contents is of no importance anymore. Old wtmp
176 databases can only be used by last(1) and ac(8) after they have
177 been converted to the new format using wtmpcvt(1).
180 Introduce the kernel thread "deadlock resolver" (which can be enabled
181 via the DEADLKRES option, see NOTES for more details) and the
182 sleepq_type() function for sleepqueues.
185 The rc.firewall and rc.firewall6 were unified, and
186 rc.firewall6 and rc.d/ip6fw were removed.
187 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
188 variables are obsoleted. Instead, the following new rc
189 variables are added to rc.d/ipfw:
191 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
192 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
193 firewall_simple_onet_ipv6, firewall_trusted_ipv6
195 The meanings correspond to the relevant IPv4 variables.
201 The default terminal emulation for syscons(4) has been changed
202 from cons25 to xterm on all platforms except pc98. This means
203 that the /etc/ttys file needs to be updated to ensure correct
204 operation of applications on the console.
206 The terminal emulation style can be toggled per window by using
207 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
208 options can be used to change the compile-time default back to
211 To prevent graphical artifacts, make sure the TERM environment
212 variable is set to match the terminal emulation that is being
213 performed by syscons(4).
216 The layout of the structure ieee80211req_scan_result has changed.
217 Applications that require wireless scan results (e.g. ifconfig(8))
218 from net80211 need to be recompiled.
220 Applications such as wpa_supplicant(8) may require a full world
221 build without using NO_CLEAN in order to get synchronized with the
225 The iwn(4) driver has been updated to support the 5000 and 5150 series.
226 There's one kernel module for each firmware. Adding "device iwnfw"
227 to the kernel configuration file means including all three firmware
228 images inside the kernel. If you want to include just the one for
229 your wireless card, use the the devices iwn4965fw, iwn5000fw or
233 The rc.d/network_ipv6, IPv6 configuration script has been integrated
234 into rc.d/netif. The changes are the following:
236 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
237 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
238 Note that both variables need the "inet6" keyword at the head.
240 Do not set $ipv6_network_interfaces manually if you do not
241 understand what you are doing. It is not needed in most cases.
243 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
246 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
247 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
249 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
250 all configured interfaces have "inet6 accept_rtadv" in the
251 $ifconfig_IF_ipv6. These are for backward compatibility.
253 3. A new variable $ipv6_prefer has been added. If NO, IPv6
254 functionality of interfaces with no corresponding
255 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
256 and the default address selection policy of ip6addrctl(8)
257 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
258 Note that if you want to configure IPv6 functionality on the
259 disabled interfaces after boot, first you need to clear the flag by
260 using ifconfig(8) like:
262 ifconfig em0 inet6 -ifdisabled
264 If YES, the default address selection policy is set as
267 The default value of $ipv6_prefer is NO.
269 4. If your system need to receive Router Advertisement messages,
270 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
271 scripts automatically invoke rtsol(8) when the interface becomes
272 UP. The Router Advertisement messages are used for SLAAC
273 (State-Less Address AutoConfiguration).
276 802.11s D3.03 support was committed. This is incompatible with the
277 previous code, which was based on D3.0.
280 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
281 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
282 control whether accepting Router Advertisement messages or not.
283 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
284 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
285 The ifconfig(8) utility now supports these flags.
288 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
289 mount(8) and -a option for df(1) to see them.
292 The old tunable hw.bus.devctl_disable has been superseded by
293 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
294 replaced by hw.bus.devctl_queue=0. The default for this new tunable
298 Remove the option STOP_NMI. The default action is now to use NMI only
299 for KDB via the newly introduced function stop_cpus_hard() and
300 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
303 The stable/8 branch created in subversion. This corresponds to the
304 RELENG_8 branch in CVS.
307 Bump the shared library version numbers for all libraries that do not
308 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
309 __FreeBSD_version to 800105.
312 Due to changes in the implementation of virtual network stack support,
313 all network-related kernel modules must be recompiled. As this change
314 breaks the ABI, bump __FreeBSD_version to 800104.
317 The TOE interface to the TCP syncache has been modified to remove
318 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
319 The cxgb driver is the only TOE consumer affected by this change, and
320 needs to be recompiled along with the kernel. As this change breaks
321 the ABI, bump __FreeBSD_version to 800103.
324 Padding has been added to struct tcpcb, sackhint and tcpstat in
325 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
326 maintaining the ABI. However, this change breaks the ABI, so bump
327 __FreeBSD_version to 800102. User space tools that rely on the size of
328 any of these structs (e.g. sockstat) need to be recompiled.
331 The NFS_LEGACYRPC option has been removed along with the old kernel
332 RPC implementation that this option selected. Kernel configurations
333 may need to be adjusted.
336 The network interface device nodes at /dev/net/<interface> have been
337 removed. All ioctl operations can be performed the normal way using
338 routing sockets. The kqueue functionality can generally be replaced
339 with routing sockets.
342 The documentation from the FreeBSD Documentation Project (Handbook,
343 FAQ, etc.) is now installed via packages by sysinstall(8) and under
344 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
347 The ABI of various structures related to the SYSV IPC API have been
348 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
349 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
353 Layout of struct vnet has changed as routing related variables were
354 moved to their own Vimage module. Modules need to be recompiled. Bump
355 __FreeBSD_version to 800099.
358 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
359 respectively. As long as no more than 16 groups per process are used,
360 no changes should be visible. When more than 16 groups are used, old
361 binaries may fail if they call getgroups() or getgrouplist() with
362 statically sized storage. Recompiling will work around this, but
363 applications should be modified to use dynamically allocated storage
364 for group arrays as POSIX.1-2008 does not cap an implementation's
365 number of supported groups at NGROUPS_MAX+1 as previous versions did.
367 NFS and portalfs mounts may also be affected as the list of groups is
368 truncated to 16. Users of NFS who use more than 16 groups, should
369 take care that negative group permissions are not used on the exported
370 file systems as they will not be reliable unless a GSSAPI based
371 authentication method is used.
374 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
375 option compiles in the support for adaptive spinning for lockmgrs
376 which want to enable it. The lockinit() function now accepts the flag
377 LK_ADAPTIVE in order to make the lock object subject to adaptive
378 spinning when both held in write and read mode.
381 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
382 changed. User applications that use this ioctl need to be rebuilt.
385 The layout of struct thread has changed. Kernel and modules need to
389 The layout of structs ifnet, domain, protosw and vnet_net has changed.
390 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
393 window(1) has been removed from the base system. It can now be
394 installed from ports. The port is called misc/window.
397 The way we are storing and accessing `routing table' entries has
398 changed. Programs reading the FIB, like netstat, need to be
402 A new netisr implementation has been added for FreeBSD 8. Network
403 file system modules, such as igmp, ipdivert, and others, should be
405 Bump __FreeBSD_version to 800096.
408 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
412 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
413 Bump __FreeBSD_version to 800094.
416 Add mnt_xflag field to 'struct mount'. File system modules need to be
418 Bump __FreeBSD_version to 800093.
421 The compiling option ADAPTIVE_SX has been retired while it has been
422 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
423 The KPI for sx_init_flags() changes as accepting flags:
424 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
425 been introduced in order to handle the reversed logic.
426 Bump __FreeBSD_version to 800092.
429 Add support for hierarchical jails. Remove global securelevel.
430 Bump __FreeBSD_version to 800091.
433 The layout of struct vnet_net has changed, therefore modules
435 Bump __FreeBSD_version to 800090.
438 The newly imported zic(8) produces a new format in the output. Please
439 run tzsetup(8) to install the newly created data to /etc/localtime.
442 The sysctl tree for the usb stack has renamed from hw.usb2.* to
443 hw.usb.* and is now consistent again with previous releases.
446 802.11 monitor mode support was revised and driver api's were changed.
447 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
448 of DLT_IEEE802_11. No user-visible data structures were changed but
449 applications that use DLT_IEEE802_11 may require changes.
450 Bump __FreeBSD_version to 800088.
453 The layout of the following structs has changed: sysctl_oid,
454 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
455 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
456 panics may be experienced. World rebuild is required for
457 correctly checking networking state from userland.
458 Bump __FreeBSD_version to 800085.
461 MLDv2 and Source-Specific Multicast (SSM) have been merged
462 to the IPv6 stack. VIMAGE hooks are in but not yet used.
463 The implementation of SSM within FreeBSD's IPv6 stack closely
464 follows the IPv4 implementation.
466 For kernel developers:
468 * The most important changes are that the ip6_output() and
469 ip6_input() paths no longer take the IN6_MULTI_LOCK,
470 and this lock has been downgraded to a non-recursive mutex.
472 * As with the changes to the IPv4 stack to support SSM, filtering
473 of inbound multicast traffic must now be performed by transport
474 protocols within the IPv6 stack. This does not apply to TCP and
475 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
477 * The KPIs used by IPv6 multicast are similar to those used by
478 the IPv4 stack, with the following differences:
479 * im6o_mc_filter() is analogous to imo_multicast_filter().
480 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
481 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
482 * IN6_LOOKUP_MULTI() has been deprecated and removed.
483 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
484 for MLDv1 have an additional 'timer' argument which is used to
485 jitter the initial membership report for the solicited-node
486 multicast membership on-link.
487 * This is not strictly needed for MLDv2, which already jitters
488 its report transmissions. However, the 'timer' argument is
489 preserved in case MLDv1 is active on the interface.
491 * The KAME linked-list based IPv6 membership implementation has
492 been refactored to use a vector similar to that used by the IPv4
494 Code which maintains a list of its own multicast memberships
495 internally, e.g. carp, has been updated to reflect the new
498 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
499 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
500 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
501 implementation constraint which needs to be addressed in HEAD.
503 For application developers:
505 * The changes are broadly similar to those made for the IPv4
508 * The use of IPv4 and IPv6 multicast socket options on the same
509 socket, using mapped addresses, HAS NOT been tested or supported.
511 * There are a number of issues with the implementation of various
512 IPv6 multicast APIs which need to be resolved in the API surface
513 before the implementation is fully compatible with KAME userland
514 use, and these are mostly to do with interface index treatment.
516 * The literature available discusses the use of either the delta / ASM
517 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
518 using setsourcefilter(3)/getsourcefilter(3). For more information
519 please refer to RFC 3768, 'Socket Interface Extensions for
520 Multicast Source Filters'.
522 * Applications which use the published RFC 3678 APIs should be fine.
524 For systems administrators:
526 * The mtest(8) utility has been refactored to support IPv6, in
527 addition to IPv4. Interface addresses are no longer accepted
528 as arguments, their names must be used instead. The utility
529 will map the interface name to its first IPv4 address as
530 returned by getifaddrs(3).
532 * The ifmcstat(8) utility has also been updated to print the MLDv2
533 endpoint state and source filter lists via sysctl(3).
535 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
536 loopback of IPv6 multicast datagrams by default; it defaults to 1
537 to preserve the existing behaviour. Disabling multicast loopback is
538 recommended for optimal system performance.
540 * The IPv6 MROUTING code has been changed to examine this sysctl
541 instead of attempting to perform a group lookup before looping
542 back forwarded datagrams.
544 Bump __FreeBSD_version to 800084.
547 Implement low-level Bluetooth HCI API.
548 Bump __FreeBSD_version to 800083.
551 The layout of struct malloc_type, used by modules to register new
552 memory allocation types, has changed. Most modules will need to
553 be rebuilt or panics may be experienced.
554 Bump __FreeBSD_version to 800081.
557 Anticipate overflowing inp_flags - add inp_flags2.
558 This changes most offsets in inpcb, so checking v4 connection
559 state will require a world rebuild.
560 Bump __FreeBSD_version to 800080.
563 Add an llentry to struct route and struct route_in6. Modules
564 embedding a struct route will need to be recompiled.
565 Bump __FreeBSD_version to 800079.
568 The size of rt_metrics_lite and by extension rtentry has changed.
569 Networking administration apps will need to be recompiled.
570 The route command now supports show as an alias for get, weighting
571 of routes, sticky and nostick flags to alter the behavior of stateful
573 Bump __FreeBSD_version to 800078.
576 Do not use Giant for kbdmux(4) locking. This is wrong and
577 apparently causing more problems than it solves. This will
578 re-open the issue where interrupt handlers may race with
579 kbdmux(4) in polling mode. Typical symptoms include (but
580 not limited to) duplicated and/or missing characters when
581 low level console functions (such as gets) are used while
582 interrupts are enabled (for example geli password prompt,
583 mountroot prompt etc.). Disabling kbdmux(4) may help.
586 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
587 kernel modules referencing any of the above need to be recompiled.
588 Bump __FreeBSD_version to 800075.
591 GEOM_PART has become the default partition slicer for storage devices,
592 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
593 introduces some changes:
595 MSDOS/EBR: the devices created from MSDOS extended partition entries
596 (EBR) can be named differently than with GEOM_MBR and are now symlinks
597 to devices with offset-based names. fstabs may need to be modified.
599 BSD: the "geometry does not match label" warning is harmless in most
600 cases but it points to problems in file system misalignment with
601 disk geometry. The "c" partition is now implicit, covers the whole
602 top-level drive and cannot be (mis)used by users.
604 General: Kernel dumps are now not allowed to be written to devices
605 whose partition types indicate they are meant to be used for file
606 systems (or, in case of MSDOS partitions, as something else than
609 Most of these changes date approximately from 200812.
612 The uscanner(4) driver has been removed from the kernel. This follows
613 Linux removing theirs in 2.6 and making libusb the default interface
617 The multicast forwarding code has been cleaned up. netstat(1)
618 only relies on KVM now for printing bandwidth upcall meters.
619 The IPv4 and IPv6 modules are split into ip_mroute_mod and
620 ip6_mroute_mod respectively. The config(5) options for statically
621 compiling this code remain the same, i.e. 'options MROUTING'.
624 Support for the IFF_NEEDSGIANT network interface flag has been
625 removed, which means that non-MPSAFE network device drivers are no
626 longer supported. In particular, if_ar, if_sr, and network device
627 drivers from the old (legacy) USB stack can no longer be built or
631 POSIX.1 Native Language Support (NLS) has been enabled in libc and
632 a bunch of new language catalog files have also been added.
633 This means that some common libc messages are now localized and
634 they depend on the LC_MESSAGES environmental variable.
637 The k8temp(4) driver has been renamed to amdtemp(4) since
638 support for Family 10 and Family 11 CPU families was added.
641 IGMPv3 and Source-Specific Multicast (SSM) have been merged
642 to the IPv4 stack. VIMAGE hooks are in but not yet used.
644 For kernel developers, the most important changes are that the
645 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
646 and this lock has been downgraded to a non-recursive mutex.
648 Transport protocols (UDP, Raw IP) are now responsible for filtering
649 inbound multicast traffic according to group membership and source
650 filters. The imo_multicast_filter() KPI exists for this purpose.
651 Transports which do not use multicast (SCTP, TCP) already reject
652 multicast by default. Forwarding and receive performance may improve
653 as a mutex acquisition is no longer needed in the ip_input()
654 low-level input path. in_addmulti() and in_delmulti() are shimmed
655 to new KPIs which exist to support SSM in-kernel.
657 For application developers, it is recommended that loopback of
658 multicast datagrams be disabled for best performance, as this
659 will still cause the lock to be taken for each looped-back
660 datagram transmission. The net.inet.ip.mcast.loop sysctl may
661 be tuned to 0 to disable loopback by default; it defaults to 1
662 to preserve the existing behaviour.
664 For systems administrators, to obtain best performance with
665 multicast reception and multiple groups, it is always recommended
666 that a card with a suitably precise hash filter is used. Hash
667 collisions will still result in the lock being taken within the
668 transport protocol input path to check group membership.
670 If deploying FreeBSD in an environment with IGMP snooping switches,
671 it is recommended that the net.inet.igmp.sendlocal sysctl remain
672 enabled; this forces 224.0.0.0/24 group membership to be announced
675 The size of 'struct igmpstat' has changed; netstat needs to be
676 recompiled to reflect this.
677 Bump __FreeBSD_version to 800070.
680 libusb20.so.1 is now installed as libusb.so.1 and the ports system
681 updated to use it. This requires a buildworld/installworld in order to
682 update the library and dependencies (usbconfig, etc). Its advisable to
683 rebuild all ports which uses libusb. More specific directions are given
684 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
685 libusb are no longer required and can be removed.
688 A workaround is committed to allow the creation of System V shared
689 memory segment of size > 2 GB on the 64-bit architectures.
690 Due to a limitation of the existing ABI, the shm_segsz member
691 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
692 wrong for large segments. Note that limits must be explicitly
693 raised to allow such segments to be created.
696 The layout of struct ifnet has changed, requiring a rebuild of all
697 network device driver modules.
700 The /dev handling for the new USB stack has changed, a
701 buildworld/installworld is required for libusb20.
704 The new USB2 stack has now been permanently moved in and all kernel and
705 module names reverted to their previous values (eg, usb, ehci, ohci,
706 ums, ...). The old usb stack can be compiled in by prefixing the name
707 with the letter 'o', the old usb modules have been removed.
708 Updating entry 20090216 for xorg and 20090215 for libmap may still
712 The rc.conf(5) option if_up_delay has been renamed to
713 defaultroute_delay to better reflect its purpose. If you have
714 customized this setting in /etc/rc.conf you need to update it to
718 xorg 7.4 wants to configure its input devices via hald which does not
719 yet work with USB2. If the keyboard/mouse does not work in xorg then
721 Option "AllowEmptyInput" "off"
722 to your ServerLayout section. This will cause X to use the configured
723 kbd and mouse sections from your xorg.conf.
726 The GENERIC kernels for all architectures now default to the new USB2
727 stack. No kernel config options or code have been removed so if a
728 problem arises please report it and optionally revert to the old USB
729 stack. If you are loading USB kernel modules or have a custom kernel
730 that includes GENERIC then ensure that usb names are also changed over,
731 eg uftdi -> usb2_serial_ftdi.
733 Older programs linked against the ports libusb 0.1 need to be
734 redirected to the new stack's libusb20. /etc/libmap.conf can
736 # Map old usb library to new one for usb2 stack
737 libusb-0.1.so.8 libusb20.so.1
740 All USB ethernet devices now attach as interfaces under the name ueN
741 (eg. ue0). This is to provide a predictable name as vendors often
742 change usb chipsets in a product without notice.
745 The ichsmb(4) driver has been changed to require SMBus slave
746 addresses be left-justified (xxxxxxx0b) rather than right-justified.
747 All of the other SMBus controller drivers require left-justified
748 slave addresses, so this change makes all the drivers provide the
752 INET6 statistics (struct ip6stat) was updated.
753 netstat(1) needs to be recompiled.
756 NTFS has been removed from GENERIC kernel on amd64 to match
757 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
758 will load ntfs.ko module automatically when NTFS support is
759 actually needed, unless ntfs.ko is not installed or security
760 level prohibits loading kernel modules. If either is the case,
761 "options NTFS" has to be added into kernel config.
764 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
765 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
766 800061. User space tools that rely on the size of struct tcpcb in
767 tcp_var.h (e.g. sockstat) need to be recompiled.
770 ng_tty(4) module updated to match the new TTY subsystem.
771 Due to API change, user-level applications must be updated.
772 New API support added to mpd5 CVS and expected to be present
773 in next mpd5.3 release.
776 With __FreeBSD_version 800060 the makefs tool is part of
777 the base system (it was a port).
780 The afdata and ifnet locks have been changed from mutexes to
781 rwlocks, network modules will need to be re-compiled.
784 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
785 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
786 The new code reduced struct rtentry{} by 16 bytes on 32-bit
787 architecture and 40 bytes on 64-bit architecture. The userland
788 applications "arp" and "ndp" have been updated accordingly.
789 The output from "netstat -r" shows only routing entries and
790 none of the L2 information.
793 __FreeBSD_version 800057 marks the switchover from the
794 binary ath hal to source code. Users must add the line:
796 options AH_SUPPORT_AR5416
798 to their kernel config files when specifying:
802 The ath_hal module no longer exists; the code is now compiled
803 together with the driver in the ath module. It is now
804 possible to tailor chip support (i.e. reduce the set of chips
805 and thereby the code size); consult ath_hal(4) for details.
808 __FreeBSD_version 800054 adds memory barriers to
809 <machine/atomic.h>, new interfaces to ifnet to facilitate
810 multiple hardware transmit queues for cards that support
811 them, and a lock-less ring-buffer implementation to
812 enable drivers to more efficiently manage queueing of
816 A new version of ZFS (version 13) has been merged to -HEAD.
817 This version has zpool attribute "listsnapshots" off by
818 default, which means "zfs list" does not show snapshots,
819 and is the same as Solaris behavior.
822 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
825 The uhci, ohci, ehci and slhci USB Host controller drivers have
826 been put into separate modules. If you load the usb module
827 separately through loader.conf you will need to load the
828 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
829 controller add the following to loader.conf:
835 The ABI used by the PMC toolset has changed. Please keep
836 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
840 atapci kernel module now includes only generic PCI ATA
841 driver. AHCI driver moved to ataahci kernel module.
842 All vendor-specific code moved into separate kernel modules:
843 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
844 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
845 atamarvell, atamicron, atanational, atanetcell, atanvidia,
846 atapromise, ataserverworks, atasiliconimage, atasis, atavia
849 The TTY subsystem of the kernel has been replaced by a new
850 implementation, which provides better scalability and an
851 improved driver model. Most common drivers have been migrated to
852 the new TTY subsystem, while others have not. The following
853 drivers have not yet been ported to the new TTY layer:
856 cy, digi, rc, rp, sio
862 ng_h4, ng_tty, ppp, sl, snp
864 Adding these drivers to your kernel configuration file shall
865 cause compilation to fail.
868 ntpd has been upgraded to 4.2.4p5.
871 OpenSSH has been upgraded to 5.1p1.
873 For many years, FreeBSD's version of OpenSSH preferred DSA
874 over RSA for host and user authentication keys. With this
875 upgrade, we've switched to the vendor's default of RSA over
876 DSA. This may cause upgraded clients to warn about unknown
877 host keys even for previously known hosts. Users should
878 follow the usual procedure for verifying host keys before
879 accepting the RSA key.
881 This can be circumvented by setting the "HostKeyAlgorithms"
882 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
885 Please note that the sequence of keys offered for
886 authentication has been changed as well. You may want to
887 specify IdentityFile in a different order to revert this
891 The sio(4) driver has been removed from the i386 and amd64
892 kernel configuration files. This means uart(4) is now the
893 default serial port driver on those platforms as well.
895 To prevent collisions with the sio(4) driver, the uart(4) driver
896 uses different names for its device nodes. This means the
897 onboard serial port will now most likely be called "ttyu0"
898 instead of "ttyd0". You may need to reconfigure applications to
899 use the new device names.
901 When using the serial port as a boot console, be sure to update
902 /boot/device.hints and /etc/ttys before booting the new kernel.
903 If you forget to do so, you can still manually specify the hints
904 at the loader prompt:
906 set hint.uart.0.at="isa"
907 set hint.uart.0.port="0x3F8"
908 set hint.uart.0.flags="0x10"
909 set hint.uart.0.irq="4"
913 The gpt(8) utility has been removed. Use gpart(8) to partition
917 The version that Linuxulator emulates was changed from 2.4.2
918 to 2.6.16. If you experience any problems with Linux binaries
919 please try to set sysctl compat.linux.osrelease to 2.4.2 and
920 if it fixes the problem contact emulation mailing list.
923 ISDN4BSD (I4B) was removed from the src tree. You may need to
924 update a your kernel configuration and remove relevant entries.
927 I have checked in code to support multiple routing tables.
928 See the man pages setfib(1) and setfib(2).
929 This is a hopefully backwards compatible version,
930 but to make use of it you need to compile your kernel
931 with options ROUTETABLES=2 (or more up to 16).
934 The 802.11 wireless support was redone to enable multi-bss
935 operation on devices that are capable. The underlying device
936 is no longer used directly but instead wlanX devices are
937 cloned with ifconfig. This requires changes to rc.conf files.
939 ifconfig_ath0="WPA DHCP"
942 ifconfig_wlan0="WPA DHCP"
943 see rc.conf(5) for more details. In addition, mergemaster of
944 /etc/rc.d is highly recommended. Simultaneous update of userland
945 and kernel wouldn't hurt either.
947 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
948 modules were merged into the base wlan module. All references
949 to these modules (e.g. in kernel config files) must be removed.
952 psm(4) has gained write(2) support in native operation level.
953 Arbitrary commands can be written to /dev/psm%d and status can
954 be read back from it. Therefore, an application is responsible
955 for status validation and error recovery. It is a no-op in
956 other operation levels.
959 Support for KSE threading has been removed from the kernel. To
960 run legacy applications linked against KSE libmap.conf may
961 be used. The following libmap.conf may be used to ensure
962 compatibility with any prior release:
964 libpthread.so.1 libthr.so.1
965 libpthread.so.2 libthr.so.2
966 libkse.so.3 libthr.so.3
969 The layout of struct vmspace has changed. This affects libkvm
970 and any executables that link against libkvm and use the
971 kvm_getprocs() function. In particular, but not exclusively,
972 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
973 The effects are minimal, but it's advisable to upgrade world
977 The latest em driver no longer has support in it for the
978 82575 adapter, this is now moved to the igb driver. The
979 split was done to make new features that are incompatible
980 with older hardware easier to do.
983 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
984 likewise the kernel option is now GEOM_LINUX_LVM.
987 The default NFS mount mode has changed from UDP to TCP for
988 increased reliability. If you rely on (insecurely) NFS
989 mounting across a firewall you may need to update your
993 Belatedly note the addition of m_collapse for compacting
997 The fts(3) structures have been changed to use adequate
998 integer types for their members and so to be able to cope
999 with huge file trees. The old fts(3) ABI is preserved
1000 through symbol versioning in libc, so third-party binaries
1001 using fts(3) should still work, although they will not take
1002 advantage of the extended types. At the same time, some
1003 third-party software might fail to build after this change
1004 due to unportable assumptions made in its source code about
1005 fts(3) structure members. Such software should be fixed
1006 by its vendor or, in the worst case, in the ports tree.
1007 FreeBSD_version 800015 marks this change for the unlikely
1008 case that a portable fix is impossible.
1011 To upgrade to -current after this date, you must be running
1012 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1013 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1016 The ADAPTIVE_GIANT kernel option has been retired because its
1017 functionality is the default now.
1020 The AT keyboard emulation of sunkbd(4) has been turned on
1021 by default. In order to make the special symbols of the Sun
1022 keyboards driven by sunkbd(4) work under X these now have
1023 to be configured the same way as Sun USB keyboards driven
1024 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1026 Option "XkbLayout" "us"
1027 Option "XkbRules" "xorg"
1028 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1031 It has been decided that it is desirable to provide ABI
1032 backwards compatibility to the FreeBSD 4/5/6 versions of the
1033 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1034 broken with the introduction of PCI domain support (see the
1035 20070930 entry). Unfortunately, this required the ABI of
1036 PCIOCGETCONF to be broken again in order to be able to
1037 provide backwards compatibility to the old version of that
1038 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1039 again. As for prominent ports this affects neither pciutils
1040 nor xorg-server this time, the hal port needs to be rebuilt
1044 The misnamed kthread_create() and friends have been renamed
1045 to kproc_create() etc. Many of the callers already
1046 used kproc_start()..
1047 I will return kthread_create() and friends in a while
1048 with implementations that actually create threads, not procs.
1049 Renaming corresponds with version 800002.
1058 Avoid using make -j when upgrading. While generally safe, there are
1059 sometimes problems using -j to upgrade. If your upgrade fails with
1060 -j, please try again without -j. From time to time in the past there
1061 have been problems using -j with buildworld and/or installworld. This
1062 is especially true when upgrading between "distant" versions (eg one
1063 that cross a major release boundary or several minor releases, or when
1064 several months have passed on the -current branch).
1066 Sometimes, obscure build problems are the result of environment
1067 poisoning. This can happen because the make utility reads its
1068 environment when searching for values for global variables. To run
1069 your build attempts in an "environmental clean room", prefix all make
1070 commands with 'env -i '. See the env(1) manual page for more details.
1072 When upgrading from one major version to another it is generally best
1073 to upgrade to the latest code in the currently installed branch first,
1074 then do an upgrade to the new branch. This is the best-tested upgrade
1075 path, and has the highest probability of being successful. Please try
1076 this approach before reporting problems with a major version upgrade.
1080 When upgrading the boot ZFS pool to a new version, always follow
1083 1.) recompile and reinstall the ZFS boot loader and boot block
1084 (this is part of "make buildworld" and "make installworld")
1086 2.) update the ZFS boot block on your boot drive
1088 The following example updates the ZFS boot block on the first
1089 partition (freebsd-boot) of a GPT partitioned drive ad0:
1090 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1092 Non-boot pools do not need these updates.
1096 If you are updating from a prior version of FreeBSD (even one just
1097 a few days old), you should follow this procedure. It is the most
1098 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1100 make kernel-toolchain
1101 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1102 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1104 To test a kernel once
1105 ---------------------
1106 If you just want to boot a kernel once (because you are not sure
1107 if it works, or if you want to boot a known bad kernel to provide
1108 debugging information) run
1109 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1110 nextboot -k testkernel
1112 To just build a kernel when you know that it won't mess you up
1113 --------------------------------------------------------------
1114 This assumes you are already running a CURRENT system. Replace
1115 ${arch} with the architecture of your machine (e.g. "i386",
1116 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1118 cd src/sys/${arch}/conf
1119 config KERNEL_NAME_HERE
1120 cd ../compile/KERNEL_NAME_HERE
1125 If this fails, go to the "To build a kernel" section.
1127 To rebuild everything and install it on the current system.
1128 -----------------------------------------------------------
1129 # Note: sometimes if you are running current you gotta do more than
1130 # is listed here if you are upgrading from a really old current.
1132 <make sure you have good level 0 dumps>
1134 make kernel KERNCONF=YOUR_KERNEL_HERE
1136 <reboot in single user> [3]
1144 To cross-install current onto a separate partition
1145 --------------------------------------------------
1146 # In this approach we use a separate partition to hold
1147 # current's root, 'usr', and 'var' directories. A partition
1148 # holding "/", "/usr" and "/var" should be about 2GB in
1151 <make sure you have good level 0 dumps>
1154 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1155 <maybe newfs current's root partition>
1156 <mount current's root partition on directory ${CURRENT_ROOT}>
1157 make installworld DESTDIR=${CURRENT_ROOT}
1158 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1159 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1160 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1161 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1162 <reboot into current>
1163 <do a "native" rebuild/install as described in the previous section>
1164 <maybe install compatibility libraries from ports/misc/compat*>
1168 To upgrade in-place from 8.x-stable to current
1169 ----------------------------------------------
1170 <make sure you have good level 0 dumps>
1172 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1174 <reboot in single user> [3]
1181 Make sure that you've read the UPDATING file to understand the
1182 tweaks to various things you need. At this point in the life
1183 cycle of current, things change often and you are on your own
1184 to cope. The defaults can also change, so please read ALL of
1185 the UPDATING entries.
1187 Also, if you are tracking -current, you must be subscribed to
1188 freebsd-current@freebsd.org. Make sure that before you update
1189 your sources that you have read and understood all the recent
1190 messages there. If in doubt, please track -stable which has
1191 much fewer pitfalls.
1193 [1] If you have third party modules, such as vmware, you
1194 should disable them at this point so they don't crash your
1197 [3] From the bootblocks, boot -s, and then do
1202 adjkerntz -i # if CMOS is wall time
1203 Also, when doing a major release upgrade, it is required that
1204 you boot into single user mode to do the installworld.
1206 [4] Note: This step is non-optional. Failure to do this step
1207 can result in a significant reduction in the functionality of the
1208 system. Attempting to do it by hand is not recommended and those
1209 that pursue this avenue should read this file carefully, as well
1210 as the archives of freebsd-current and freebsd-hackers mailing lists
1211 for potential gotchas. The -U option is also useful to consider.
1212 See mergemaster(8) for more information.
1214 [5] Usually this step is a noop. However, from time to time
1215 you may need to do this if you get unknown user in the following
1216 step. It never hurts to do it all the time. You may need to
1217 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1218 install) after the buildworld before this step if you last updated
1219 from current before 20020224 or from -stable before 20020408.
1221 [8] In order to have a kernel that can run the 4.x binaries needed to
1222 do an installworld, you must include the COMPAT_FREEBSD4 option in
1223 your kernel. Failure to do so may leave you with a system that is
1224 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1225 required to run the 5.x binaries on more recent kernels. And so on
1226 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1228 Make sure that you merge any new devices from GENERIC since the
1229 last time you updated your kernel config file.
1231 [9] When checking out sources, you must include the -P flag to have
1232 cvs prune empty directories.
1234 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1235 "?=" instead of the "=" assignment operator, so that buildworld can
1236 override the CPUTYPE if it needs to.
1238 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1239 not on the command line, or in /etc/make.conf. buildworld will
1240 warn if it is improperly defined.
1243 This file contains a list, in reverse chronological order, of major
1244 breakages in tracking -current. Not all things will be listed here,
1245 and it only starts on October 16, 2004. Updating files can found in
1246 previous releases if your system is older than this.
1248 Copyright information:
1250 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1252 Redistribution, publication, translation and use, with or without
1253 modification, in full or in part, in any form or format of this
1254 document are permitted without further permission from the author.
1256 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1257 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1258 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1259 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1260 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1261 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1262 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1263 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1264 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1265 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1266 POSSIBILITY OF SUCH DAMAGE.
1268 Contact Warner Losh if you have any questions about your use of