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 A workaround for a fixed ld bug has been removed in kernel code,
27 so make sure that your system ld is built from sources after
28 revision 210245 (r211583 if building head kernel on stable/8,
29 r211584 for stable/7). A symptom of incorrect ld version is
30 different addresses for set_pcpu section and __start_set_pcpu
31 symbol in kernel and/or modules.
34 The $ipv6_prefer variable in rc.conf(5) has been split into
35 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
37 The $ip6addrctl_policy is a variable to choose a pre-defined
38 address selection policy set by ip6addrctl(8). A value
39 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
42 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
43 flag (see an entry of 20090926) is set on an interface with no
44 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
45 security reason. If you want IPv6 link-local address on all
46 interfaces by default, set this to "YES".
48 The old ipv6_prefer="YES" is equivalent to
49 ipv6_activate_all_interfaces="YES" and
50 ip6addrctl_policy="ipv6_prefer".
53 DTrace has grown support for userland tracing. Due to this, DTrace is
54 now i386 and amd64 only.
55 dtruss(1) is now installed by default on those systems and a new
56 kernel module is needed for userland tracing: fasttrap.
57 No changes to your kernel config file are necessary to enable
58 userland tracing, but you might consider adding 'STRIP=' and
59 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
60 to have informative userland stack traces in DTrace (ustack).
63 The acpi_aiboost(4) driver has been removed in favor of the new
64 aibs(4) driver. You should update your kernel configuration file.
67 BSD grep has been imported to the base system and it is built by
68 default. It is completely BSD licensed, highly GNU-compatible, uses
69 less memory than its GNU counterpart and has a small codebase.
70 However, it is slower than its GNU counterpart, which is mostly
71 noticeable for larger searches, for smaller ones it is measurable
72 but not significant. The reason is complex, the most important factor
73 is that we lack a modern and efficient regex library and GNU
74 overcomes this by optimizing the searches internally. Future work
75 on improving the regex performance is planned, for the meantime,
76 users that need better performance, can build GNU grep instead by
77 setting the WITH_GNU_GREP knob.
80 Due to the import of powerpc64 support, all existing powerpc kernel
81 configuration files must be updated with a machine directive like this:
82 machine powerpc powerpc
84 In addition, an updated config(8) is required to build powerpc kernels
88 A new version of ZFS (version 15) has been merged to -HEAD.
89 This version uses a python library for the following subcommands:
90 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
91 For full functionality of these commands the following port must
92 be installed: sysutils/py-zfs
95 'vm_page's are now hashed by physical address to an array of mutexes.
96 Currently this is only used to serialize access to hold_count. Over
97 time the page queue mutex will be peeled away. This changes the size
98 of pmap on every architecture. And requires all callers of vm_page_hold
99 and vm_page_unhold to be updated.
102 WITH_CTF can now be specified in src.conf (not recommended, there
103 are some problems with static executables), make.conf (would also
104 affect ports which do not use GNU make and do not override the
105 compile targets) or in the kernel config (via "makeoptions
107 When WITH_CTF was specified there before this was silently ignored,
108 so make sure that WITH_CTF is not used in places which could lead
109 to unwanted behavior.
112 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
113 to allow 32-bit compatibility on non-x86 platforms. All kernel
114 configurations on amd64 and ia64 platforms using these options must
115 be modified accordingly.
118 The utmp user accounting database has been replaced with utmpx,
119 the user accounting interface standardized by POSIX.
120 Unfortunately the semantics of utmp and utmpx don't match,
121 making it practically impossible to support both interfaces.
122 The user accounting database is used by tools like finger(1),
123 last(1), talk(1), w(1) and ac(8).
125 All applications in the base system use utmpx. This means only
126 local binaries (e.g. from the ports tree) may still use these
127 utmp database files. These applications must be rebuilt to make
130 After the system has been upgraded, it is safe to remove the old
131 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
132 assuming their contents is of no importance anymore. Old wtmp
133 databases can only be used by last(1) and ac(8) after they have
134 been converted to the new format using wtmpcvt(1).
137 Introduce the kernel thread "deadlock resolver" (which can be enabled
138 via the DEADLKRES option, see NOTES for more details) and the
139 sleepq_type() function for sleepqueues.
142 The rc.firewall and rc.firewall6 were unified, and
143 rc.firewall6 and rc.d/ip6fw were removed.
144 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
145 variables are obsoleted. Instead, the following new rc
146 variables are added to rc.d/ipfw:
148 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
149 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
150 firewall_simple_onet_ipv6, firewall_trusted_ipv6
152 The meanings correspond to the relevant IPv4 variables.
158 The default terminal emulation for syscons(4) has been changed
159 from cons25 to xterm on all platforms except pc98. This means
160 that the /etc/ttys file needs to be updated to ensure correct
161 operation of applications on the console.
163 The terminal emulation style can be toggled per window by using
164 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
165 options can be used to change the compile-time default back to
168 To prevent graphical artifacts, make sure the TERM environment
169 variable is set to match the terminal emulation that is being
170 performed by syscons(4).
173 The layout of the structure ieee80211req_scan_result has changed.
174 Applications that require wireless scan results (e.g. ifconfig(8))
175 from net80211 need to be recompiled.
177 Applications such as wpa_supplicant(8) may require a full world
178 build without using NO_CLEAN in order to get synchronized with the
182 The iwn(4) driver has been updated to support the 5000 and 5150 series.
183 There's one kernel module for each firmware. Adding "device iwnfw"
184 to the kernel configuration file means including all three firmware
185 images inside the kernel. If you want to include just the one for
186 your wireless card, use the the devices iwn4965fw, iwn5000fw or
190 The rc.d/network_ipv6, IPv6 configuration script has been integrated
191 into rc.d/netif. The changes are the following:
193 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
194 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
195 Note that both variables need the "inet6" keyword at the head.
197 Do not set $ipv6_network_interfaces manually if you do not
198 understand what you are doing. It is not needed in most cases.
200 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
203 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
204 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
206 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
207 all configured interfaces have "inet6 accept_rtadv" in the
208 $ifconfig_IF_ipv6. These are for backward compatibility.
210 3. A new variable $ipv6_prefer has been added. If NO, IPv6
211 functionality of interfaces with no corresponding
212 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
213 and the default address selection policy of ip6addrctl(8)
214 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
215 Note that if you want to configure IPv6 functionality on the
216 disabled interfaces after boot, first you need to clear the flag by
217 using ifconfig(8) like:
219 ifconfig em0 inet6 -ifdisabled
221 If YES, the default address selection policy is set as
224 The default value of $ipv6_prefer is NO.
226 4. If your system need to receive Router Advertisement messages,
227 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
228 scripts automatically invoke rtsol(8) when the interface becomes
229 UP. The Router Advertisement messages are used for SLAAC
230 (State-Less Address AutoConfiguration).
233 802.11s D3.03 support was committed. This is incompatible with the
234 previous code, which was based on D3.0.
237 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
238 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
239 control whether accepting Router Advertisement messages or not.
240 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
241 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
242 The ifconfig(8) utility now supports these flags.
245 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
246 mount(8) and -a option for df(1) to see them.
249 The old tunable hw.bus.devctl_disable has been superseded by
250 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
251 replaced by hw.bus.devctl_queue=0. The default for this new tunable
255 Remove the option STOP_NMI. The default action is now to use NMI only
256 for KDB via the newly introduced function stop_cpus_hard() and
257 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
260 The stable/8 branch created in subversion. This corresponds to the
261 RELENG_8 branch in CVS.
264 Bump the shared library version numbers for all libraries that do not
265 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
266 __FreeBSD_version to 800105.
269 Due to changes in the implementation of virtual network stack support,
270 all network-related kernel modules must be recompiled. As this change
271 breaks the ABI, bump __FreeBSD_version to 800104.
274 The TOE interface to the TCP syncache has been modified to remove
275 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
276 The cxgb driver is the only TOE consumer affected by this change, and
277 needs to be recompiled along with the kernel. As this change breaks
278 the ABI, bump __FreeBSD_version to 800103.
281 Padding has been added to struct tcpcb, sackhint and tcpstat in
282 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
283 maintaining the ABI. However, this change breaks the ABI, so bump
284 __FreeBSD_version to 800102. User space tools that rely on the size of
285 any of these structs (e.g. sockstat) need to be recompiled.
288 The NFS_LEGACYRPC option has been removed along with the old kernel
289 RPC implementation that this option selected. Kernel configurations
290 may need to be adjusted.
293 The network interface device nodes at /dev/net/<interface> have been
294 removed. All ioctl operations can be performed the normal way using
295 routing sockets. The kqueue functionality can generally be replaced
296 with routing sockets.
299 The documentation from the FreeBSD Documentation Project (Handbook,
300 FAQ, etc.) is now installed via packages by sysinstall(8) and under
301 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
304 The ABI of various structures related to the SYSV IPC API have been
305 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
306 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
310 Layout of struct vnet has changed as routing related variables were
311 moved to their own Vimage module. Modules need to be recompiled. Bump
312 __FreeBSD_version to 800099.
315 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
316 respectively. As long as no more than 16 groups per process are used,
317 no changes should be visible. When more than 16 groups are used, old
318 binaries may fail if they call getgroups() or getgrouplist() with
319 statically sized storage. Recompiling will work around this, but
320 applications should be modified to use dynamically allocated storage
321 for group arrays as POSIX.1-2008 does not cap an implementation's
322 number of supported groups at NGROUPS_MAX+1 as previous versions did.
324 NFS and portalfs mounts may also be affected as the list of groups is
325 truncated to 16. Users of NFS who use more than 16 groups, should
326 take care that negative group permissions are not used on the exported
327 file systems as they will not be reliable unless a GSSAPI based
328 authentication method is used.
331 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
332 option compiles in the support for adaptive spinning for lockmgrs
333 which want to enable it. The lockinit() function now accepts the flag
334 LK_ADAPTIVE in order to make the lock object subject to adaptive
335 spinning when both held in write and read mode.
338 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
339 changed. User applications that use this ioctl need to be rebuilt.
342 The layout of struct thread has changed. Kernel and modules need to
346 The layout of structs ifnet, domain, protosw and vnet_net has changed.
347 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
350 window(1) has been removed from the base system. It can now be
351 installed from ports. The port is called misc/window.
354 The way we are storing and accessing `routing table' entries has
355 changed. Programs reading the FIB, like netstat, need to be
359 A new netisr implementation has been added for FreeBSD 8. Network
360 file system modules, such as igmp, ipdivert, and others, should be
362 Bump __FreeBSD_version to 800096.
365 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
369 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
370 Bump __FreeBSD_version to 800094.
373 Add mnt_xflag field to 'struct mount'. File system modules need to be
375 Bump __FreeBSD_version to 800093.
378 The compiling option ADAPTIVE_SX has been retired while it has been
379 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
380 The KPI for sx_init_flags() changes as accepting flags:
381 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
382 been introduced in order to handle the reversed logic.
383 Bump __FreeBSD_version to 800092.
386 Add support for hierarchical jails. Remove global securelevel.
387 Bump __FreeBSD_version to 800091.
390 The layout of struct vnet_net has changed, therefore modules
392 Bump __FreeBSD_version to 800090.
395 The newly imported zic(8) produces a new format in the output. Please
396 run tzsetup(8) to install the newly created data to /etc/localtime.
399 The sysctl tree for the usb stack has renamed from hw.usb2.* to
400 hw.usb.* and is now consistent again with previous releases.
403 802.11 monitor mode support was revised and driver api's were changed.
404 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
405 of DLT_IEEE802_11. No user-visible data structures were changed but
406 applications that use DLT_IEEE802_11 may require changes.
407 Bump __FreeBSD_version to 800088.
410 The layout of the following structs has changed: sysctl_oid,
411 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
412 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
413 panics may be experienced. World rebuild is required for
414 correctly checking networking state from userland.
415 Bump __FreeBSD_version to 800085.
418 MLDv2 and Source-Specific Multicast (SSM) have been merged
419 to the IPv6 stack. VIMAGE hooks are in but not yet used.
420 The implementation of SSM within FreeBSD's IPv6 stack closely
421 follows the IPv4 implementation.
423 For kernel developers:
425 * The most important changes are that the ip6_output() and
426 ip6_input() paths no longer take the IN6_MULTI_LOCK,
427 and this lock has been downgraded to a non-recursive mutex.
429 * As with the changes to the IPv4 stack to support SSM, filtering
430 of inbound multicast traffic must now be performed by transport
431 protocols within the IPv6 stack. This does not apply to TCP and
432 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
434 * The KPIs used by IPv6 multicast are similar to those used by
435 the IPv4 stack, with the following differences:
436 * im6o_mc_filter() is analogous to imo_multicast_filter().
437 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
438 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
439 * IN6_LOOKUP_MULTI() has been deprecated and removed.
440 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
441 for MLDv1 have an additional 'timer' argument which is used to
442 jitter the initial membership report for the solicited-node
443 multicast membership on-link.
444 * This is not strictly needed for MLDv2, which already jitters
445 its report transmissions. However, the 'timer' argument is
446 preserved in case MLDv1 is active on the interface.
448 * The KAME linked-list based IPv6 membership implementation has
449 been refactored to use a vector similar to that used by the IPv4
451 Code which maintains a list of its own multicast memberships
452 internally, e.g. carp, has been updated to reflect the new
455 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
456 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
457 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
458 implementation constraint which needs to be addressed in HEAD.
460 For application developers:
462 * The changes are broadly similar to those made for the IPv4
465 * The use of IPv4 and IPv6 multicast socket options on the same
466 socket, using mapped addresses, HAS NOT been tested or supported.
468 * There are a number of issues with the implementation of various
469 IPv6 multicast APIs which need to be resolved in the API surface
470 before the implementation is fully compatible with KAME userland
471 use, and these are mostly to do with interface index treatment.
473 * The literature available discusses the use of either the delta / ASM
474 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
475 using setsourcefilter(3)/getsourcefilter(3). For more information
476 please refer to RFC 3768, 'Socket Interface Extensions for
477 Multicast Source Filters'.
479 * Applications which use the published RFC 3678 APIs should be fine.
481 For systems administrators:
483 * The mtest(8) utility has been refactored to support IPv6, in
484 addition to IPv4. Interface addresses are no longer accepted
485 as arguments, their names must be used instead. The utility
486 will map the interface name to its first IPv4 address as
487 returned by getifaddrs(3).
489 * The ifmcstat(8) utility has also been updated to print the MLDv2
490 endpoint state and source filter lists via sysctl(3).
492 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
493 loopback of IPv6 multicast datagrams by default; it defaults to 1
494 to preserve the existing behaviour. Disabling multicast loopback is
495 recommended for optimal system performance.
497 * The IPv6 MROUTING code has been changed to examine this sysctl
498 instead of attempting to perform a group lookup before looping
499 back forwarded datagrams.
501 Bump __FreeBSD_version to 800084.
504 Implement low-level Bluetooth HCI API.
505 Bump __FreeBSD_version to 800083.
508 The layout of struct malloc_type, used by modules to register new
509 memory allocation types, has changed. Most modules will need to
510 be rebuilt or panics may be experienced.
511 Bump __FreeBSD_version to 800081.
514 Anticipate overflowing inp_flags - add inp_flags2.
515 This changes most offsets in inpcb, so checking v4 connection
516 state will require a world rebuild.
517 Bump __FreeBSD_version to 800080.
520 Add an llentry to struct route and struct route_in6. Modules
521 embedding a struct route will need to be recompiled.
522 Bump __FreeBSD_version to 800079.
525 The size of rt_metrics_lite and by extension rtentry has changed.
526 Networking administration apps will need to be recompiled.
527 The route command now supports show as an alias for get, weighting
528 of routes, sticky and nostick flags to alter the behavior of stateful
530 Bump __FreeBSD_version to 800078.
533 Do not use Giant for kbdmux(4) locking. This is wrong and
534 apparently causing more problems than it solves. This will
535 re-open the issue where interrupt handlers may race with
536 kbdmux(4) in polling mode. Typical symptoms include (but
537 not limited to) duplicated and/or missing characters when
538 low level console functions (such as gets) are used while
539 interrupts are enabled (for example geli password prompt,
540 mountroot prompt etc.). Disabling kbdmux(4) may help.
543 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
544 kernel modules referencing any of the above need to be recompiled.
545 Bump __FreeBSD_version to 800075.
548 GEOM_PART has become the default partition slicer for storage devices,
549 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
550 introduces some changes:
552 MSDOS/EBR: the devices created from MSDOS extended partition entries
553 (EBR) can be named differently than with GEOM_MBR and are now symlinks
554 to devices with offset-based names. fstabs may need to be modified.
556 BSD: the "geometry does not match label" warning is harmless in most
557 cases but it points to problems in file system misalignment with
558 disk geometry. The "c" partition is now implicit, covers the whole
559 top-level drive and cannot be (mis)used by users.
561 General: Kernel dumps are now not allowed to be written to devices
562 whose partition types indicate they are meant to be used for file
563 systems (or, in case of MSDOS partitions, as something else than
566 Most of these changes date approximately from 200812.
569 The uscanner(4) driver has been removed from the kernel. This follows
570 Linux removing theirs in 2.6 and making libusb the default interface
574 The multicast forwarding code has been cleaned up. netstat(1)
575 only relies on KVM now for printing bandwidth upcall meters.
576 The IPv4 and IPv6 modules are split into ip_mroute_mod and
577 ip6_mroute_mod respectively. The config(5) options for statically
578 compiling this code remain the same, i.e. 'options MROUTING'.
581 Support for the IFF_NEEDSGIANT network interface flag has been
582 removed, which means that non-MPSAFE network device drivers are no
583 longer supported. In particular, if_ar, if_sr, and network device
584 drivers from the old (legacy) USB stack can no longer be built or
588 POSIX.1 Native Language Support (NLS) has been enabled in libc and
589 a bunch of new language catalog files have also been added.
590 This means that some common libc messages are now localized and
591 they depend on the LC_MESSAGES environmental variable.
594 The k8temp(4) driver has been renamed to amdtemp(4) since
595 support for Family 10 and Family 11 CPU families was added.
598 IGMPv3 and Source-Specific Multicast (SSM) have been merged
599 to the IPv4 stack. VIMAGE hooks are in but not yet used.
601 For kernel developers, the most important changes are that the
602 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
603 and this lock has been downgraded to a non-recursive mutex.
605 Transport protocols (UDP, Raw IP) are now responsible for filtering
606 inbound multicast traffic according to group membership and source
607 filters. The imo_multicast_filter() KPI exists for this purpose.
608 Transports which do not use multicast (SCTP, TCP) already reject
609 multicast by default. Forwarding and receive performance may improve
610 as a mutex acquisition is no longer needed in the ip_input()
611 low-level input path. in_addmulti() and in_delmulti() are shimmed
612 to new KPIs which exist to support SSM in-kernel.
614 For application developers, it is recommended that loopback of
615 multicast datagrams be disabled for best performance, as this
616 will still cause the lock to be taken for each looped-back
617 datagram transmission. The net.inet.ip.mcast.loop sysctl may
618 be tuned to 0 to disable loopback by default; it defaults to 1
619 to preserve the existing behaviour.
621 For systems administrators, to obtain best performance with
622 multicast reception and multiple groups, it is always recommended
623 that a card with a suitably precise hash filter is used. Hash
624 collisions will still result in the lock being taken within the
625 transport protocol input path to check group membership.
627 If deploying FreeBSD in an environment with IGMP snooping switches,
628 it is recommended that the net.inet.igmp.sendlocal sysctl remain
629 enabled; this forces 224.0.0.0/24 group membership to be announced
632 The size of 'struct igmpstat' has changed; netstat needs to be
633 recompiled to reflect this.
634 Bump __FreeBSD_version to 800070.
637 libusb20.so.1 is now installed as libusb.so.1 and the ports system
638 updated to use it. This requires a buildworld/installworld in order to
639 update the library and dependencies (usbconfig, etc). Its advisable to
640 rebuild all ports which uses libusb. More specific directions are given
641 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
642 libusb are no longer required and can be removed.
645 A workaround is committed to allow the creation of System V shared
646 memory segment of size > 2 GB on the 64-bit architectures.
647 Due to a limitation of the existing ABI, the shm_segsz member
648 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
649 wrong for large segments. Note that limits must be explicitly
650 raised to allow such segments to be created.
653 The layout of struct ifnet has changed, requiring a rebuild of all
654 network device driver modules.
657 The /dev handling for the new USB stack has changed, a
658 buildworld/installworld is required for libusb20.
661 The new USB2 stack has now been permanently moved in and all kernel and
662 module names reverted to their previous values (eg, usb, ehci, ohci,
663 ums, ...). The old usb stack can be compiled in by prefixing the name
664 with the letter 'o', the old usb modules have been removed.
665 Updating entry 20090216 for xorg and 20090215 for libmap may still
669 The rc.conf(5) option if_up_delay has been renamed to
670 defaultroute_delay to better reflect its purpose. If you have
671 customized this setting in /etc/rc.conf you need to update it to
675 xorg 7.4 wants to configure its input devices via hald which does not
676 yet work with USB2. If the keyboard/mouse does not work in xorg then
678 Option "AllowEmptyInput" "off"
679 to your ServerLayout section. This will cause X to use the configured
680 kbd and mouse sections from your xorg.conf.
683 The GENERIC kernels for all architectures now default to the new USB2
684 stack. No kernel config options or code have been removed so if a
685 problem arises please report it and optionally revert to the old USB
686 stack. If you are loading USB kernel modules or have a custom kernel
687 that includes GENERIC then ensure that usb names are also changed over,
688 eg uftdi -> usb2_serial_ftdi.
690 Older programs linked against the ports libusb 0.1 need to be
691 redirected to the new stack's libusb20. /etc/libmap.conf can
693 # Map old usb library to new one for usb2 stack
694 libusb-0.1.so.8 libusb20.so.1
697 All USB ethernet devices now attach as interfaces under the name ueN
698 (eg. ue0). This is to provide a predictable name as vendors often
699 change usb chipsets in a product without notice.
702 The ichsmb(4) driver has been changed to require SMBus slave
703 addresses be left-justified (xxxxxxx0b) rather than right-justified.
704 All of the other SMBus controller drivers require left-justified
705 slave addresses, so this change makes all the drivers provide the
709 INET6 statistics (struct ip6stat) was updated.
710 netstat(1) needs to be recompiled.
713 NTFS has been removed from GENERIC kernel on amd64 to match
714 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
715 will load ntfs.ko module automatically when NTFS support is
716 actually needed, unless ntfs.ko is not installed or security
717 level prohibits loading kernel modules. If either is the case,
718 "options NTFS" has to be added into kernel config.
721 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
722 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
723 800061. User space tools that rely on the size of struct tcpcb in
724 tcp_var.h (e.g. sockstat) need to be recompiled.
727 ng_tty(4) module updated to match the new TTY subsystem.
728 Due to API change, user-level applications must be updated.
729 New API support added to mpd5 CVS and expected to be present
730 in next mpd5.3 release.
733 With __FreeBSD_version 800060 the makefs tool is part of
734 the base system (it was a port).
737 The afdata and ifnet locks have been changed from mutexes to
738 rwlocks, network modules will need to be re-compiled.
741 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
742 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
743 The new code reduced struct rtentry{} by 16 bytes on 32-bit
744 architecture and 40 bytes on 64-bit architecture. The userland
745 applications "arp" and "ndp" have been updated accordingly.
746 The output from "netstat -r" shows only routing entries and
747 none of the L2 information.
750 __FreeBSD_version 800057 marks the switchover from the
751 binary ath hal to source code. Users must add the line:
753 options AH_SUPPORT_AR5416
755 to their kernel config files when specifying:
759 The ath_hal module no longer exists; the code is now compiled
760 together with the driver in the ath module. It is now
761 possible to tailor chip support (i.e. reduce the set of chips
762 and thereby the code size); consult ath_hal(4) for details.
765 __FreeBSD_version 800054 adds memory barriers to
766 <machine/atomic.h>, new interfaces to ifnet to facilitate
767 multiple hardware transmit queues for cards that support
768 them, and a lock-less ring-buffer implementation to
769 enable drivers to more efficiently manage queueing of
773 A new version of ZFS (version 13) has been merged to -HEAD.
774 This version has zpool attribute "listsnapshots" off by
775 default, which means "zfs list" does not show snapshots,
776 and is the same as Solaris behavior.
779 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
782 The uhci, ohci, ehci and slhci USB Host controller drivers have
783 been put into separate modules. If you load the usb module
784 separately through loader.conf you will need to load the
785 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
786 controller add the following to loader.conf:
792 The ABI used by the PMC toolset has changed. Please keep
793 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
797 atapci kernel module now includes only generic PCI ATA
798 driver. AHCI driver moved to ataahci kernel module.
799 All vendor-specific code moved into separate kernel modules:
800 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
801 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
802 atamarvell, atamicron, atanational, atanetcell, atanvidia,
803 atapromise, ataserverworks, atasiliconimage, atasis, atavia
806 The TTY subsystem of the kernel has been replaced by a new
807 implementation, which provides better scalability and an
808 improved driver model. Most common drivers have been migrated to
809 the new TTY subsystem, while others have not. The following
810 drivers have not yet been ported to the new TTY layer:
813 cy, digi, rc, rp, sio
819 ng_h4, ng_tty, ppp, sl, snp
821 Adding these drivers to your kernel configuration file shall
822 cause compilation to fail.
825 ntpd has been upgraded to 4.2.4p5.
828 OpenSSH has been upgraded to 5.1p1.
830 For many years, FreeBSD's version of OpenSSH preferred DSA
831 over RSA for host and user authentication keys. With this
832 upgrade, we've switched to the vendor's default of RSA over
833 DSA. This may cause upgraded clients to warn about unknown
834 host keys even for previously known hosts. Users should
835 follow the usual procedure for verifying host keys before
836 accepting the RSA key.
838 This can be circumvented by setting the "HostKeyAlgorithms"
839 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
842 Please note that the sequence of keys offered for
843 authentication has been changed as well. You may want to
844 specify IdentityFile in a different order to revert this
848 The sio(4) driver has been removed from the i386 and amd64
849 kernel configuration files. This means uart(4) is now the
850 default serial port driver on those platforms as well.
852 To prevent collisions with the sio(4) driver, the uart(4) driver
853 uses different names for its device nodes. This means the
854 onboard serial port will now most likely be called "ttyu0"
855 instead of "ttyd0". You may need to reconfigure applications to
856 use the new device names.
858 When using the serial port as a boot console, be sure to update
859 /boot/device.hints and /etc/ttys before booting the new kernel.
860 If you forget to do so, you can still manually specify the hints
861 at the loader prompt:
863 set hint.uart.0.at="isa"
864 set hint.uart.0.port="0x3F8"
865 set hint.uart.0.flags="0x10"
866 set hint.uart.0.irq="4"
870 The gpt(8) utility has been removed. Use gpart(8) to partition
874 The version that Linuxulator emulates was changed from 2.4.2
875 to 2.6.16. If you experience any problems with Linux binaries
876 please try to set sysctl compat.linux.osrelease to 2.4.2 and
877 if it fixes the problem contact emulation mailing list.
880 ISDN4BSD (I4B) was removed from the src tree. You may need to
881 update a your kernel configuration and remove relevant entries.
884 I have checked in code to support multiple routing tables.
885 See the man pages setfib(1) and setfib(2).
886 This is a hopefully backwards compatible version,
887 but to make use of it you need to compile your kernel
888 with options ROUTETABLES=2 (or more up to 16).
891 The 802.11 wireless support was redone to enable multi-bss
892 operation on devices that are capable. The underlying device
893 is no longer used directly but instead wlanX devices are
894 cloned with ifconfig. This requires changes to rc.conf files.
896 ifconfig_ath0="WPA DHCP"
899 ifconfig_wlan0="WPA DHCP"
900 see rc.conf(5) for more details. In addition, mergemaster of
901 /etc/rc.d is highly recommended. Simultaneous update of userland
902 and kernel wouldn't hurt either.
904 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
905 modules were merged into the base wlan module. All references
906 to these modules (e.g. in kernel config files) must be removed.
909 psm(4) has gained write(2) support in native operation level.
910 Arbitrary commands can be written to /dev/psm%d and status can
911 be read back from it. Therefore, an application is responsible
912 for status validation and error recovery. It is a no-op in
913 other operation levels.
916 Support for KSE threading has been removed from the kernel. To
917 run legacy applications linked against KSE libmap.conf may
918 be used. The following libmap.conf may be used to ensure
919 compatibility with any prior release:
921 libpthread.so.1 libthr.so.1
922 libpthread.so.2 libthr.so.2
923 libkse.so.3 libthr.so.3
926 The layout of struct vmspace has changed. This affects libkvm
927 and any executables that link against libkvm and use the
928 kvm_getprocs() function. In particular, but not exclusively,
929 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
930 The effects are minimal, but it's advisable to upgrade world
934 The latest em driver no longer has support in it for the
935 82575 adapter, this is now moved to the igb driver. The
936 split was done to make new features that are incompatible
937 with older hardware easier to do.
940 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
941 likewise the kernel option is now GEOM_LINUX_LVM.
944 The default NFS mount mode has changed from UDP to TCP for
945 increased reliability. If you rely on (insecurely) NFS
946 mounting across a firewall you may need to update your
950 Belatedly note the addition of m_collapse for compacting
954 The fts(3) structures have been changed to use adequate
955 integer types for their members and so to be able to cope
956 with huge file trees. The old fts(3) ABI is preserved
957 through symbol versioning in libc, so third-party binaries
958 using fts(3) should still work, although they will not take
959 advantage of the extended types. At the same time, some
960 third-party software might fail to build after this change
961 due to unportable assumptions made in its source code about
962 fts(3) structure members. Such software should be fixed
963 by its vendor or, in the worst case, in the ports tree.
964 FreeBSD_version 800015 marks this change for the unlikely
965 case that a portable fix is impossible.
968 To upgrade to -current after this date, you must be running
969 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
970 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
973 The ADAPTIVE_GIANT kernel option has been retired because its
974 functionality is the default now.
977 The AT keyboard emulation of sunkbd(4) has been turned on
978 by default. In order to make the special symbols of the Sun
979 keyboards driven by sunkbd(4) work under X these now have
980 to be configured the same way as Sun USB keyboards driven
981 by ukbd(4) (which also does AT keyboard emulation), f.e.:
983 Option "XkbLayout" "us"
984 Option "XkbRules" "xorg"
985 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
988 It has been decided that it is desirable to provide ABI
989 backwards compatibility to the FreeBSD 4/5/6 versions of the
990 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
991 broken with the introduction of PCI domain support (see the
992 20070930 entry). Unfortunately, this required the ABI of
993 PCIOCGETCONF to be broken again in order to be able to
994 provide backwards compatibility to the old version of that
995 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
996 again. As for prominent ports this affects neither pciutils
997 nor xorg-server this time, the hal port needs to be rebuilt
1001 The misnamed kthread_create() and friends have been renamed
1002 to kproc_create() etc. Many of the callers already
1003 used kproc_start()..
1004 I will return kthread_create() and friends in a while
1005 with implementations that actually create threads, not procs.
1006 Renaming corresponds with version 800002.
1015 Avoid using make -j when upgrading. While generally safe, there are
1016 sometimes problems using -j to upgrade. If your upgrade fails with
1017 -j, please try again without -j. From time to time in the past there
1018 have been problems using -j with buildworld and/or installworld. This
1019 is especially true when upgrading between "distant" versions (eg one
1020 that cross a major release boundary or several minor releases, or when
1021 several months have passed on the -current branch).
1023 Sometimes, obscure build problems are the result of environment
1024 poisoning. This can happen because the make utility reads its
1025 environment when searching for values for global variables. To run
1026 your build attempts in an "environmental clean room", prefix all make
1027 commands with 'env -i '. See the env(1) manual page for more details.
1029 When upgrading from one major version to another it is generally best
1030 to upgrade to the latest code in the currently installed branch first,
1031 then do an upgrade to the new branch. This is the best-tested upgrade
1032 path, and has the highest probability of being successful. Please try
1033 this approach before reporting problems with a major version upgrade.
1037 When upgrading the boot ZFS pool to a new version, always follow
1040 1.) recompile and reinstall the ZFS boot loader and boot block
1041 (this is part of "make buildworld" and "make installworld")
1043 2.) update the ZFS boot block on your boot drive
1045 The following example updates the ZFS boot block on the first
1046 partition (freebsd-boot) of a GPT partitioned drive ad0:
1047 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1049 Non-boot pools do not need these updates.
1053 If you are updating from a prior version of FreeBSD (even one just
1054 a few days old), you should follow this procedure. It is the most
1055 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1057 make kernel-toolchain
1058 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1059 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1061 To test a kernel once
1062 ---------------------
1063 If you just want to boot a kernel once (because you are not sure
1064 if it works, or if you want to boot a known bad kernel to provide
1065 debugging information) run
1066 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1067 nextboot -k testkernel
1069 To just build a kernel when you know that it won't mess you up
1070 --------------------------------------------------------------
1071 This assumes you are already running a CURRENT system. Replace
1072 ${arch} with the architecture of your machine (e.g. "i386",
1073 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1075 cd src/sys/${arch}/conf
1076 config KERNEL_NAME_HERE
1077 cd ../compile/KERNEL_NAME_HERE
1082 If this fails, go to the "To build a kernel" section.
1084 To rebuild everything and install it on the current system.
1085 -----------------------------------------------------------
1086 # Note: sometimes if you are running current you gotta do more than
1087 # is listed here if you are upgrading from a really old current.
1089 <make sure you have good level 0 dumps>
1091 make kernel KERNCONF=YOUR_KERNEL_HERE
1093 <reboot in single user> [3]
1101 To cross-install current onto a separate partition
1102 --------------------------------------------------
1103 # In this approach we use a separate partition to hold
1104 # current's root, 'usr', and 'var' directories. A partition
1105 # holding "/", "/usr" and "/var" should be about 2GB in
1108 <make sure you have good level 0 dumps>
1111 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1112 <maybe newfs current's root partition>
1113 <mount current's root partition on directory ${CURRENT_ROOT}>
1114 make installworld DESTDIR=${CURRENT_ROOT}
1115 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1116 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1117 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1118 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1119 <reboot into current>
1120 <do a "native" rebuild/install as described in the previous section>
1121 <maybe install compatibility libraries from ports/misc/compat*>
1125 To upgrade in-place from 8.x-stable to current
1126 ----------------------------------------------
1127 <make sure you have good level 0 dumps>
1129 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1131 <reboot in single user> [3]
1138 Make sure that you've read the UPDATING file to understand the
1139 tweaks to various things you need. At this point in the life
1140 cycle of current, things change often and you are on your own
1141 to cope. The defaults can also change, so please read ALL of
1142 the UPDATING entries.
1144 Also, if you are tracking -current, you must be subscribed to
1145 freebsd-current@freebsd.org. Make sure that before you update
1146 your sources that you have read and understood all the recent
1147 messages there. If in doubt, please track -stable which has
1148 much fewer pitfalls.
1150 [1] If you have third party modules, such as vmware, you
1151 should disable them at this point so they don't crash your
1154 [3] From the bootblocks, boot -s, and then do
1159 adjkerntz -i # if CMOS is wall time
1160 Also, when doing a major release upgrade, it is required that
1161 you boot into single user mode to do the installworld.
1163 [4] Note: This step is non-optional. Failure to do this step
1164 can result in a significant reduction in the functionality of the
1165 system. Attempting to do it by hand is not recommended and those
1166 that pursue this avenue should read this file carefully, as well
1167 as the archives of freebsd-current and freebsd-hackers mailing lists
1168 for potential gotchas. The -U option is also useful to consider.
1169 See mergemaster(8) for more information.
1171 [5] Usually this step is a noop. However, from time to time
1172 you may need to do this if you get unknown user in the following
1173 step. It never hurts to do it all the time. You may need to
1174 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1175 install) after the buildworld before this step if you last updated
1176 from current before 20020224 or from -stable before 20020408.
1178 [8] In order to have a kernel that can run the 4.x binaries needed to
1179 do an installworld, you must include the COMPAT_FREEBSD4 option in
1180 your kernel. Failure to do so may leave you with a system that is
1181 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1182 required to run the 5.x binaries on more recent kernels. And so on
1183 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1185 Make sure that you merge any new devices from GENERIC since the
1186 last time you updated your kernel config file.
1188 [9] When checking out sources, you must include the -P flag to have
1189 cvs prune empty directories.
1191 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1192 "?=" instead of the "=" assignment operator, so that buildworld can
1193 override the CPUTYPE if it needs to.
1195 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1196 not on the command line, or in /etc/make.conf. buildworld will
1197 warn if it is improperly defined.
1200 This file contains a list, in reverse chronological order, of major
1201 breakages in tracking -current. Not all things will be listed here,
1202 and it only starts on October 16, 2004. Updating files can found in
1203 previous releases if your system is older than this.
1205 Copyright information:
1207 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1209 Redistribution, publication, translation and use, with or without
1210 modification, in full or in part, in any form or format of this
1211 document are permitted without further permission from the author.
1213 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1214 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1215 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1216 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1217 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1218 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1219 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1220 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1221 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1222 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1223 POSSIBILITY OF SUCH DAMAGE.
1225 Contact Warner Losh if you have any questions about your use of