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 SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
27 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
28 for scalar sysctls is defined but disabled. Code that needs
29 UQUAD to pass the type checking that must compile on older
30 systems where the define is not present can check against
31 __FreeBSD_version >= 900030.
33 The system dialog(1) has been replaced with a new version previously
34 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
35 with the previous version, but the libdialog associated with it has
36 a largely incompatible API. As such, the original version of libdialog
37 will be kept temporarily as libodialog, until its base system consumers
38 are replaced or updated. Bump __FreeBSD_version to 900030.
41 If you are trying to run make universe on a -stable system, and you get
42 the following warning:
43 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
44 unknown. config(8) likely too old."
45 or something similar to it, then you must upgrade your -stable system
46 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
47 stable/8) or build the config from the latest stable/8 branch and
48 install it on your system.
50 Prior to this date, building a current universe on 8-stable system from
51 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
52 error in the first kernel build phase. A new config on those old
53 systems will fix that problem for older versions of -current.
56 The TCP stack has been modified to allow Khelp modules to interact with
57 it via helper hook points and store per-connection data in the TCP
58 control block. Bump __FreeBSD_version to 900029. User space tools that
59 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
63 Generic IEEE 802.3 annex 31B full duplex flow control support has been
64 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
65 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
66 to take advantage of it instead of using custom implementations. This
67 means that these drivers now no longer unconditionally advertise
68 support for flow control but only do so if flow control is a selected
69 media option. This was implemented in the generic support that way in
70 order to allow flow control to be switched on and off via ifconfig(8)
71 with the PHY specific default to typically off in order to protect
72 from unwanted effects. Consequently, if you used flow control with
73 one of the above mentioned drivers you now need to explicitly enable
75 ifconfig bge0 media auto mediaopt flowcontrol
77 Along with the above mentioned changes generic support for setting
78 1000baseT master mode also has been added and brgphy(4), ciphy(4),
79 e1000phy(4) as well as ip1000phy(4) have been converted to take
80 advantage of it. This means that these drivers now no longer take the
81 link0 parameter for selecting master mode but the master media option
82 has to be used instead, for example like in the following:
83 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
85 Selection of master mode now is also available with all other PHY
86 drivers supporting 1000baseT.
89 The TCP stack has received a significant update to add support for
90 modularised congestion control and generally improve the clarity of
91 congestion control decisions. Bump __FreeBSD_version to 900025. User
92 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
93 sockstat) need to be recompiled.
96 The man(1) utility has been replaced by a new version that no longer
97 uses /etc/manpath.config. Please consult man.conf(5) for how to
98 migrate local entries to the new format.
101 The copyright strings printed by login(1) and sshd(8) at the time of a
102 new connection have been removed to follow other operating systems and
106 A workaround for a fixed ld bug has been removed in kernel code,
107 so make sure that your system ld is built from sources after
108 revision 210245 from 2010-07-19 (r211583 if building head kernel
109 on stable/8, r211584 for stable/7; both from 2010-08-21).
110 A symptom of incorrect ld version is different addresses for
111 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
114 The $ipv6_prefer variable in rc.conf(5) has been split into
115 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
117 The $ip6addrctl_policy is a variable to choose a pre-defined
118 address selection policy set by ip6addrctl(8). A value
119 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
122 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
123 flag (see an entry of 20090926) is set on an interface with no
124 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
125 security reason. If you want IPv6 link-local address on all
126 interfaces by default, set this to "YES".
128 The old ipv6_prefer="YES" is equivalent to
129 ipv6_activate_all_interfaces="YES" and
130 ip6addrctl_policy="ipv6_prefer".
133 DTrace has grown support for userland tracing. Due to this, DTrace is
134 now i386 and amd64 only.
135 dtruss(1) is now installed by default on those systems and a new
136 kernel module is needed for userland tracing: fasttrap.
137 No changes to your kernel config file are necessary to enable
138 userland tracing, but you might consider adding 'STRIP=' and
139 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
140 to have informative userland stack traces in DTrace (ustack).
143 The acpi_aiboost(4) driver has been removed in favor of the new
144 aibs(4) driver. You should update your kernel configuration file.
147 BSD grep has been imported to the base system and it is built by
148 default. It is completely BSD licensed, highly GNU-compatible, uses
149 less memory than its GNU counterpart and has a small codebase.
150 However, it is slower than its GNU counterpart, which is mostly
151 noticeable for larger searches, for smaller ones it is measurable
152 but not significant. The reason is complex, the most important factor
153 is that we lack a modern and efficient regex library and GNU
154 overcomes this by optimizing the searches internally. Future work
155 on improving the regex performance is planned, for the meantime,
156 users that need better performance, can build GNU grep instead by
157 setting the WITH_GNU_GREP knob.
160 Due to the import of powerpc64 support, all existing powerpc kernel
161 configuration files must be updated with a machine directive like this:
162 machine powerpc powerpc
164 In addition, an updated config(8) is required to build powerpc kernels
168 A new version of ZFS (version 15) has been merged to -HEAD.
169 This version uses a python library for the following subcommands:
170 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
171 For full functionality of these commands the following port must
172 be installed: sysutils/py-zfs
175 'vm_page's are now hashed by physical address to an array of mutexes.
176 Currently this is only used to serialize access to hold_count. Over
177 time the page queue mutex will be peeled away. This changes the size
178 of pmap on every architecture. And requires all callers of vm_page_hold
179 and vm_page_unhold to be updated.
182 WITH_CTF can now be specified in src.conf (not recommended, there
183 are some problems with static executables), make.conf (would also
184 affect ports which do not use GNU make and do not override the
185 compile targets) or in the kernel config (via "makeoptions
187 When WITH_CTF was specified there before this was silently ignored,
188 so make sure that WITH_CTF is not used in places which could lead
189 to unwanted behavior.
192 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
193 to allow 32-bit compatibility on non-x86 platforms. All kernel
194 configurations on amd64 and ia64 platforms using these options must
195 be modified accordingly.
198 The utmp user accounting database has been replaced with utmpx,
199 the user accounting interface standardized by POSIX.
200 Unfortunately the semantics of utmp and utmpx don't match,
201 making it practically impossible to support both interfaces.
202 The user accounting database is used by tools like finger(1),
203 last(1), talk(1), w(1) and ac(8).
205 All applications in the base system use utmpx. This means only
206 local binaries (e.g. from the ports tree) may still use these
207 utmp database files. These applications must be rebuilt to make
210 After the system has been upgraded, it is safe to remove the old
211 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
212 assuming their contents is of no importance anymore. Old wtmp
213 databases can only be used by last(1) and ac(8) after they have
214 been converted to the new format using wtmpcvt(1).
217 Introduce the kernel thread "deadlock resolver" (which can be enabled
218 via the DEADLKRES option, see NOTES for more details) and the
219 sleepq_type() function for sleepqueues.
222 The rc.firewall and rc.firewall6 were unified, and
223 rc.firewall6 and rc.d/ip6fw were removed.
224 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
225 variables are obsoleted. Instead, the following new rc
226 variables are added to rc.d/ipfw:
228 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
229 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
230 firewall_simple_onet_ipv6, firewall_trusted_ipv6
232 The meanings correspond to the relevant IPv4 variables.
238 The default terminal emulation for syscons(4) has been changed
239 from cons25 to xterm on all platforms except pc98. This means
240 that the /etc/ttys file needs to be updated to ensure correct
241 operation of applications on the console.
243 The terminal emulation style can be toggled per window by using
244 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
245 options can be used to change the compile-time default back to
248 To prevent graphical artifacts, make sure the TERM environment
249 variable is set to match the terminal emulation that is being
250 performed by syscons(4).
253 The layout of the structure ieee80211req_scan_result has changed.
254 Applications that require wireless scan results (e.g. ifconfig(8))
255 from net80211 need to be recompiled.
257 Applications such as wpa_supplicant(8) may require a full world
258 build without using NO_CLEAN in order to get synchronized with the
262 The iwn(4) driver has been updated to support the 5000 and 5150 series.
263 There's one kernel module for each firmware. Adding "device iwnfw"
264 to the kernel configuration file means including all three firmware
265 images inside the kernel. If you want to include just the one for
266 your wireless card, use the the devices iwn4965fw, iwn5000fw or
270 The rc.d/network_ipv6, IPv6 configuration script has been integrated
271 into rc.d/netif. The changes are the following:
273 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
274 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
275 Note that both variables need the "inet6" keyword at the head.
277 Do not set $ipv6_network_interfaces manually if you do not
278 understand what you are doing. It is not needed in most cases.
280 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
283 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
284 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
286 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
287 all configured interfaces have "inet6 accept_rtadv" in the
288 $ifconfig_IF_ipv6. These are for backward compatibility.
290 3. A new variable $ipv6_prefer has been added. If NO, IPv6
291 functionality of interfaces with no corresponding
292 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
293 and the default address selection policy of ip6addrctl(8)
294 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
295 Note that if you want to configure IPv6 functionality on the
296 disabled interfaces after boot, first you need to clear the flag by
297 using ifconfig(8) like:
299 ifconfig em0 inet6 -ifdisabled
301 If YES, the default address selection policy is set as
304 The default value of $ipv6_prefer is NO.
306 4. If your system need to receive Router Advertisement messages,
307 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
308 scripts automatically invoke rtsol(8) when the interface becomes
309 UP. The Router Advertisement messages are used for SLAAC
310 (State-Less Address AutoConfiguration).
313 802.11s D3.03 support was committed. This is incompatible with the
314 previous code, which was based on D3.0.
317 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
318 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
319 control whether accepting Router Advertisement messages or not.
320 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
321 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
322 The ifconfig(8) utility now supports these flags.
325 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
326 mount(8) and -a option for df(1) to see them.
329 The old tunable hw.bus.devctl_disable has been superseded by
330 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
331 replaced by hw.bus.devctl_queue=0. The default for this new tunable
335 Remove the option STOP_NMI. The default action is now to use NMI only
336 for KDB via the newly introduced function stop_cpus_hard() and
337 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
340 The stable/8 branch created in subversion. This corresponds to the
341 RELENG_8 branch in CVS.
344 Bump the shared library version numbers for all libraries that do not
345 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
346 __FreeBSD_version to 800105.
349 Due to changes in the implementation of virtual network stack support,
350 all network-related kernel modules must be recompiled. As this change
351 breaks the ABI, bump __FreeBSD_version to 800104.
354 The TOE interface to the TCP syncache has been modified to remove
355 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
356 The cxgb driver is the only TOE consumer affected by this change, and
357 needs to be recompiled along with the kernel. As this change breaks
358 the ABI, bump __FreeBSD_version to 800103.
361 Padding has been added to struct tcpcb, sackhint and tcpstat in
362 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
363 maintaining the ABI. However, this change breaks the ABI, so bump
364 __FreeBSD_version to 800102. User space tools that rely on the size of
365 any of these structs (e.g. sockstat) need to be recompiled.
368 The NFS_LEGACYRPC option has been removed along with the old kernel
369 RPC implementation that this option selected. Kernel configurations
370 may need to be adjusted.
373 The network interface device nodes at /dev/net/<interface> have been
374 removed. All ioctl operations can be performed the normal way using
375 routing sockets. The kqueue functionality can generally be replaced
376 with routing sockets.
379 The documentation from the FreeBSD Documentation Project (Handbook,
380 FAQ, etc.) is now installed via packages by sysinstall(8) and under
381 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
384 The ABI of various structures related to the SYSV IPC API have been
385 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
386 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
390 Layout of struct vnet has changed as routing related variables were
391 moved to their own Vimage module. Modules need to be recompiled. Bump
392 __FreeBSD_version to 800099.
395 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
396 respectively. As long as no more than 16 groups per process are used,
397 no changes should be visible. When more than 16 groups are used, old
398 binaries may fail if they call getgroups() or getgrouplist() with
399 statically sized storage. Recompiling will work around this, but
400 applications should be modified to use dynamically allocated storage
401 for group arrays as POSIX.1-2008 does not cap an implementation's
402 number of supported groups at NGROUPS_MAX+1 as previous versions did.
404 NFS and portalfs mounts may also be affected as the list of groups is
405 truncated to 16. Users of NFS who use more than 16 groups, should
406 take care that negative group permissions are not used on the exported
407 file systems as they will not be reliable unless a GSSAPI based
408 authentication method is used.
411 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
412 option compiles in the support for adaptive spinning for lockmgrs
413 which want to enable it. The lockinit() function now accepts the flag
414 LK_ADAPTIVE in order to make the lock object subject to adaptive
415 spinning when both held in write and read mode.
418 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
419 changed. User applications that use this ioctl need to be rebuilt.
422 The layout of struct thread has changed. Kernel and modules need to
426 The layout of structs ifnet, domain, protosw and vnet_net has changed.
427 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
430 window(1) has been removed from the base system. It can now be
431 installed from ports. The port is called misc/window.
434 The way we are storing and accessing `routing table' entries has
435 changed. Programs reading the FIB, like netstat, need to be
439 A new netisr implementation has been added for FreeBSD 8. Network
440 file system modules, such as igmp, ipdivert, and others, should be
442 Bump __FreeBSD_version to 800096.
445 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
449 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
450 Bump __FreeBSD_version to 800094.
453 Add mnt_xflag field to 'struct mount'. File system modules need to be
455 Bump __FreeBSD_version to 800093.
458 The compiling option ADAPTIVE_SX has been retired while it has been
459 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
460 The KPI for sx_init_flags() changes as accepting flags:
461 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
462 been introduced in order to handle the reversed logic.
463 Bump __FreeBSD_version to 800092.
466 Add support for hierarchical jails. Remove global securelevel.
467 Bump __FreeBSD_version to 800091.
470 The layout of struct vnet_net has changed, therefore modules
472 Bump __FreeBSD_version to 800090.
475 The newly imported zic(8) produces a new format in the output. Please
476 run tzsetup(8) to install the newly created data to /etc/localtime.
479 The sysctl tree for the usb stack has renamed from hw.usb2.* to
480 hw.usb.* and is now consistent again with previous releases.
483 802.11 monitor mode support was revised and driver api's were changed.
484 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
485 of DLT_IEEE802_11. No user-visible data structures were changed but
486 applications that use DLT_IEEE802_11 may require changes.
487 Bump __FreeBSD_version to 800088.
490 The layout of the following structs has changed: sysctl_oid,
491 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
492 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
493 panics may be experienced. World rebuild is required for
494 correctly checking networking state from userland.
495 Bump __FreeBSD_version to 800085.
498 MLDv2 and Source-Specific Multicast (SSM) have been merged
499 to the IPv6 stack. VIMAGE hooks are in but not yet used.
500 The implementation of SSM within FreeBSD's IPv6 stack closely
501 follows the IPv4 implementation.
503 For kernel developers:
505 * The most important changes are that the ip6_output() and
506 ip6_input() paths no longer take the IN6_MULTI_LOCK,
507 and this lock has been downgraded to a non-recursive mutex.
509 * As with the changes to the IPv4 stack to support SSM, filtering
510 of inbound multicast traffic must now be performed by transport
511 protocols within the IPv6 stack. This does not apply to TCP and
512 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
514 * The KPIs used by IPv6 multicast are similar to those used by
515 the IPv4 stack, with the following differences:
516 * im6o_mc_filter() is analogous to imo_multicast_filter().
517 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
518 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
519 * IN6_LOOKUP_MULTI() has been deprecated and removed.
520 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
521 for MLDv1 have an additional 'timer' argument which is used to
522 jitter the initial membership report for the solicited-node
523 multicast membership on-link.
524 * This is not strictly needed for MLDv2, which already jitters
525 its report transmissions. However, the 'timer' argument is
526 preserved in case MLDv1 is active on the interface.
528 * The KAME linked-list based IPv6 membership implementation has
529 been refactored to use a vector similar to that used by the IPv4
531 Code which maintains a list of its own multicast memberships
532 internally, e.g. carp, has been updated to reflect the new
535 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
536 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
537 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
538 implementation constraint which needs to be addressed in HEAD.
540 For application developers:
542 * The changes are broadly similar to those made for the IPv4
545 * The use of IPv4 and IPv6 multicast socket options on the same
546 socket, using mapped addresses, HAS NOT been tested or supported.
548 * There are a number of issues with the implementation of various
549 IPv6 multicast APIs which need to be resolved in the API surface
550 before the implementation is fully compatible with KAME userland
551 use, and these are mostly to do with interface index treatment.
553 * The literature available discusses the use of either the delta / ASM
554 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
555 using setsourcefilter(3)/getsourcefilter(3). For more information
556 please refer to RFC 3768, 'Socket Interface Extensions for
557 Multicast Source Filters'.
559 * Applications which use the published RFC 3678 APIs should be fine.
561 For systems administrators:
563 * The mtest(8) utility has been refactored to support IPv6, in
564 addition to IPv4. Interface addresses are no longer accepted
565 as arguments, their names must be used instead. The utility
566 will map the interface name to its first IPv4 address as
567 returned by getifaddrs(3).
569 * The ifmcstat(8) utility has also been updated to print the MLDv2
570 endpoint state and source filter lists via sysctl(3).
572 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
573 loopback of IPv6 multicast datagrams by default; it defaults to 1
574 to preserve the existing behaviour. Disabling multicast loopback is
575 recommended for optimal system performance.
577 * The IPv6 MROUTING code has been changed to examine this sysctl
578 instead of attempting to perform a group lookup before looping
579 back forwarded datagrams.
581 Bump __FreeBSD_version to 800084.
584 Implement low-level Bluetooth HCI API.
585 Bump __FreeBSD_version to 800083.
588 The layout of struct malloc_type, used by modules to register new
589 memory allocation types, has changed. Most modules will need to
590 be rebuilt or panics may be experienced.
591 Bump __FreeBSD_version to 800081.
594 Anticipate overflowing inp_flags - add inp_flags2.
595 This changes most offsets in inpcb, so checking v4 connection
596 state will require a world rebuild.
597 Bump __FreeBSD_version to 800080.
600 Add an llentry to struct route and struct route_in6. Modules
601 embedding a struct route will need to be recompiled.
602 Bump __FreeBSD_version to 800079.
605 The size of rt_metrics_lite and by extension rtentry has changed.
606 Networking administration apps will need to be recompiled.
607 The route command now supports show as an alias for get, weighting
608 of routes, sticky and nostick flags to alter the behavior of stateful
610 Bump __FreeBSD_version to 800078.
613 Do not use Giant for kbdmux(4) locking. This is wrong and
614 apparently causing more problems than it solves. This will
615 re-open the issue where interrupt handlers may race with
616 kbdmux(4) in polling mode. Typical symptoms include (but
617 not limited to) duplicated and/or missing characters when
618 low level console functions (such as gets) are used while
619 interrupts are enabled (for example geli password prompt,
620 mountroot prompt etc.). Disabling kbdmux(4) may help.
623 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
624 kernel modules referencing any of the above need to be recompiled.
625 Bump __FreeBSD_version to 800075.
628 GEOM_PART has become the default partition slicer for storage devices,
629 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
630 introduces some changes:
632 MSDOS/EBR: the devices created from MSDOS extended partition entries
633 (EBR) can be named differently than with GEOM_MBR and are now symlinks
634 to devices with offset-based names. fstabs may need to be modified.
636 BSD: the "geometry does not match label" warning is harmless in most
637 cases but it points to problems in file system misalignment with
638 disk geometry. The "c" partition is now implicit, covers the whole
639 top-level drive and cannot be (mis)used by users.
641 General: Kernel dumps are now not allowed to be written to devices
642 whose partition types indicate they are meant to be used for file
643 systems (or, in case of MSDOS partitions, as something else than
646 Most of these changes date approximately from 200812.
649 The uscanner(4) driver has been removed from the kernel. This follows
650 Linux removing theirs in 2.6 and making libusb the default interface
654 The multicast forwarding code has been cleaned up. netstat(1)
655 only relies on KVM now for printing bandwidth upcall meters.
656 The IPv4 and IPv6 modules are split into ip_mroute_mod and
657 ip6_mroute_mod respectively. The config(5) options for statically
658 compiling this code remain the same, i.e. 'options MROUTING'.
661 Support for the IFF_NEEDSGIANT network interface flag has been
662 removed, which means that non-MPSAFE network device drivers are no
663 longer supported. In particular, if_ar, if_sr, and network device
664 drivers from the old (legacy) USB stack can no longer be built or
668 POSIX.1 Native Language Support (NLS) has been enabled in libc and
669 a bunch of new language catalog files have also been added.
670 This means that some common libc messages are now localized and
671 they depend on the LC_MESSAGES environmental variable.
674 The k8temp(4) driver has been renamed to amdtemp(4) since
675 support for Family 10 and Family 11 CPU families was added.
678 IGMPv3 and Source-Specific Multicast (SSM) have been merged
679 to the IPv4 stack. VIMAGE hooks are in but not yet used.
681 For kernel developers, the most important changes are that the
682 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
683 and this lock has been downgraded to a non-recursive mutex.
685 Transport protocols (UDP, Raw IP) are now responsible for filtering
686 inbound multicast traffic according to group membership and source
687 filters. The imo_multicast_filter() KPI exists for this purpose.
688 Transports which do not use multicast (SCTP, TCP) already reject
689 multicast by default. Forwarding and receive performance may improve
690 as a mutex acquisition is no longer needed in the ip_input()
691 low-level input path. in_addmulti() and in_delmulti() are shimmed
692 to new KPIs which exist to support SSM in-kernel.
694 For application developers, it is recommended that loopback of
695 multicast datagrams be disabled for best performance, as this
696 will still cause the lock to be taken for each looped-back
697 datagram transmission. The net.inet.ip.mcast.loop sysctl may
698 be tuned to 0 to disable loopback by default; it defaults to 1
699 to preserve the existing behaviour.
701 For systems administrators, to obtain best performance with
702 multicast reception and multiple groups, it is always recommended
703 that a card with a suitably precise hash filter is used. Hash
704 collisions will still result in the lock being taken within the
705 transport protocol input path to check group membership.
707 If deploying FreeBSD in an environment with IGMP snooping switches,
708 it is recommended that the net.inet.igmp.sendlocal sysctl remain
709 enabled; this forces 224.0.0.0/24 group membership to be announced
712 The size of 'struct igmpstat' has changed; netstat needs to be
713 recompiled to reflect this.
714 Bump __FreeBSD_version to 800070.
717 libusb20.so.1 is now installed as libusb.so.1 and the ports system
718 updated to use it. This requires a buildworld/installworld in order to
719 update the library and dependencies (usbconfig, etc). Its advisable to
720 rebuild all ports which uses libusb. More specific directions are given
721 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
722 libusb are no longer required and can be removed.
725 A workaround is committed to allow the creation of System V shared
726 memory segment of size > 2 GB on the 64-bit architectures.
727 Due to a limitation of the existing ABI, the shm_segsz member
728 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
729 wrong for large segments. Note that limits must be explicitly
730 raised to allow such segments to be created.
733 The layout of struct ifnet has changed, requiring a rebuild of all
734 network device driver modules.
737 The /dev handling for the new USB stack has changed, a
738 buildworld/installworld is required for libusb20.
741 The new USB2 stack has now been permanently moved in and all kernel and
742 module names reverted to their previous values (eg, usb, ehci, ohci,
743 ums, ...). The old usb stack can be compiled in by prefixing the name
744 with the letter 'o', the old usb modules have been removed.
745 Updating entry 20090216 for xorg and 20090215 for libmap may still
749 The rc.conf(5) option if_up_delay has been renamed to
750 defaultroute_delay to better reflect its purpose. If you have
751 customized this setting in /etc/rc.conf you need to update it to
755 xorg 7.4 wants to configure its input devices via hald which does not
756 yet work with USB2. If the keyboard/mouse does not work in xorg then
758 Option "AllowEmptyInput" "off"
759 to your ServerLayout section. This will cause X to use the configured
760 kbd and mouse sections from your xorg.conf.
763 The GENERIC kernels for all architectures now default to the new USB2
764 stack. No kernel config options or code have been removed so if a
765 problem arises please report it and optionally revert to the old USB
766 stack. If you are loading USB kernel modules or have a custom kernel
767 that includes GENERIC then ensure that usb names are also changed over,
768 eg uftdi -> usb2_serial_ftdi.
770 Older programs linked against the ports libusb 0.1 need to be
771 redirected to the new stack's libusb20. /etc/libmap.conf can
773 # Map old usb library to new one for usb2 stack
774 libusb-0.1.so.8 libusb20.so.1
777 All USB ethernet devices now attach as interfaces under the name ueN
778 (eg. ue0). This is to provide a predictable name as vendors often
779 change usb chipsets in a product without notice.
782 The ichsmb(4) driver has been changed to require SMBus slave
783 addresses be left-justified (xxxxxxx0b) rather than right-justified.
784 All of the other SMBus controller drivers require left-justified
785 slave addresses, so this change makes all the drivers provide the
789 INET6 statistics (struct ip6stat) was updated.
790 netstat(1) needs to be recompiled.
793 NTFS has been removed from GENERIC kernel on amd64 to match
794 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
795 will load ntfs.ko module automatically when NTFS support is
796 actually needed, unless ntfs.ko is not installed or security
797 level prohibits loading kernel modules. If either is the case,
798 "options NTFS" has to be added into kernel config.
801 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
802 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
803 800061. User space tools that rely on the size of struct tcpcb in
804 tcp_var.h (e.g. sockstat) need to be recompiled.
807 ng_tty(4) module updated to match the new TTY subsystem.
808 Due to API change, user-level applications must be updated.
809 New API support added to mpd5 CVS and expected to be present
810 in next mpd5.3 release.
813 With __FreeBSD_version 800060 the makefs tool is part of
814 the base system (it was a port).
817 The afdata and ifnet locks have been changed from mutexes to
818 rwlocks, network modules will need to be re-compiled.
821 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
822 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
823 The new code reduced struct rtentry{} by 16 bytes on 32-bit
824 architecture and 40 bytes on 64-bit architecture. The userland
825 applications "arp" and "ndp" have been updated accordingly.
826 The output from "netstat -r" shows only routing entries and
827 none of the L2 information.
830 __FreeBSD_version 800057 marks the switchover from the
831 binary ath hal to source code. Users must add the line:
833 options AH_SUPPORT_AR5416
835 to their kernel config files when specifying:
839 The ath_hal module no longer exists; the code is now compiled
840 together with the driver in the ath module. It is now
841 possible to tailor chip support (i.e. reduce the set of chips
842 and thereby the code size); consult ath_hal(4) for details.
845 __FreeBSD_version 800054 adds memory barriers to
846 <machine/atomic.h>, new interfaces to ifnet to facilitate
847 multiple hardware transmit queues for cards that support
848 them, and a lock-less ring-buffer implementation to
849 enable drivers to more efficiently manage queueing of
853 A new version of ZFS (version 13) has been merged to -HEAD.
854 This version has zpool attribute "listsnapshots" off by
855 default, which means "zfs list" does not show snapshots,
856 and is the same as Solaris behavior.
859 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
862 The uhci, ohci, ehci and slhci USB Host controller drivers have
863 been put into separate modules. If you load the usb module
864 separately through loader.conf you will need to load the
865 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
866 controller add the following to loader.conf:
872 The ABI used by the PMC toolset has changed. Please keep
873 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
877 atapci kernel module now includes only generic PCI ATA
878 driver. AHCI driver moved to ataahci kernel module.
879 All vendor-specific code moved into separate kernel modules:
880 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
881 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
882 atamarvell, atamicron, atanational, atanetcell, atanvidia,
883 atapromise, ataserverworks, atasiliconimage, atasis, atavia
886 The TTY subsystem of the kernel has been replaced by a new
887 implementation, which provides better scalability and an
888 improved driver model. Most common drivers have been migrated to
889 the new TTY subsystem, while others have not. The following
890 drivers have not yet been ported to the new TTY layer:
893 cy, digi, rc, rp, sio
899 ng_h4, ng_tty, ppp, sl, snp
901 Adding these drivers to your kernel configuration file shall
902 cause compilation to fail.
905 ntpd has been upgraded to 4.2.4p5.
908 OpenSSH has been upgraded to 5.1p1.
910 For many years, FreeBSD's version of OpenSSH preferred DSA
911 over RSA for host and user authentication keys. With this
912 upgrade, we've switched to the vendor's default of RSA over
913 DSA. This may cause upgraded clients to warn about unknown
914 host keys even for previously known hosts. Users should
915 follow the usual procedure for verifying host keys before
916 accepting the RSA key.
918 This can be circumvented by setting the "HostKeyAlgorithms"
919 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
922 Please note that the sequence of keys offered for
923 authentication has been changed as well. You may want to
924 specify IdentityFile in a different order to revert this
928 The sio(4) driver has been removed from the i386 and amd64
929 kernel configuration files. This means uart(4) is now the
930 default serial port driver on those platforms as well.
932 To prevent collisions with the sio(4) driver, the uart(4) driver
933 uses different names for its device nodes. This means the
934 onboard serial port will now most likely be called "ttyu0"
935 instead of "ttyd0". You may need to reconfigure applications to
936 use the new device names.
938 When using the serial port as a boot console, be sure to update
939 /boot/device.hints and /etc/ttys before booting the new kernel.
940 If you forget to do so, you can still manually specify the hints
941 at the loader prompt:
943 set hint.uart.0.at="isa"
944 set hint.uart.0.port="0x3F8"
945 set hint.uart.0.flags="0x10"
946 set hint.uart.0.irq="4"
950 The gpt(8) utility has been removed. Use gpart(8) to partition
954 The version that Linuxulator emulates was changed from 2.4.2
955 to 2.6.16. If you experience any problems with Linux binaries
956 please try to set sysctl compat.linux.osrelease to 2.4.2 and
957 if it fixes the problem contact emulation mailing list.
960 ISDN4BSD (I4B) was removed from the src tree. You may need to
961 update a your kernel configuration and remove relevant entries.
964 I have checked in code to support multiple routing tables.
965 See the man pages setfib(1) and setfib(2).
966 This is a hopefully backwards compatible version,
967 but to make use of it you need to compile your kernel
968 with options ROUTETABLES=2 (or more up to 16).
971 The 802.11 wireless support was redone to enable multi-bss
972 operation on devices that are capable. The underlying device
973 is no longer used directly but instead wlanX devices are
974 cloned with ifconfig. This requires changes to rc.conf files.
976 ifconfig_ath0="WPA DHCP"
979 ifconfig_wlan0="WPA DHCP"
980 see rc.conf(5) for more details. In addition, mergemaster of
981 /etc/rc.d is highly recommended. Simultaneous update of userland
982 and kernel wouldn't hurt either.
984 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
985 modules were merged into the base wlan module. All references
986 to these modules (e.g. in kernel config files) must be removed.
989 psm(4) has gained write(2) support in native operation level.
990 Arbitrary commands can be written to /dev/psm%d and status can
991 be read back from it. Therefore, an application is responsible
992 for status validation and error recovery. It is a no-op in
993 other operation levels.
996 Support for KSE threading has been removed from the kernel. To
997 run legacy applications linked against KSE libmap.conf may
998 be used. The following libmap.conf may be used to ensure
999 compatibility with any prior release:
1001 libpthread.so.1 libthr.so.1
1002 libpthread.so.2 libthr.so.2
1003 libkse.so.3 libthr.so.3
1006 The layout of struct vmspace has changed. This affects libkvm
1007 and any executables that link against libkvm and use the
1008 kvm_getprocs() function. In particular, but not exclusively,
1009 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1010 The effects are minimal, but it's advisable to upgrade world
1014 The latest em driver no longer has support in it for the
1015 82575 adapter, this is now moved to the igb driver. The
1016 split was done to make new features that are incompatible
1017 with older hardware easier to do.
1020 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1021 likewise the kernel option is now GEOM_LINUX_LVM.
1024 The default NFS mount mode has changed from UDP to TCP for
1025 increased reliability. If you rely on (insecurely) NFS
1026 mounting across a firewall you may need to update your
1030 Belatedly note the addition of m_collapse for compacting
1034 The fts(3) structures have been changed to use adequate
1035 integer types for their members and so to be able to cope
1036 with huge file trees. The old fts(3) ABI is preserved
1037 through symbol versioning in libc, so third-party binaries
1038 using fts(3) should still work, although they will not take
1039 advantage of the extended types. At the same time, some
1040 third-party software might fail to build after this change
1041 due to unportable assumptions made in its source code about
1042 fts(3) structure members. Such software should be fixed
1043 by its vendor or, in the worst case, in the ports tree.
1044 FreeBSD_version 800015 marks this change for the unlikely
1045 case that a portable fix is impossible.
1048 To upgrade to -current after this date, you must be running
1049 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1050 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1053 The ADAPTIVE_GIANT kernel option has been retired because its
1054 functionality is the default now.
1057 The AT keyboard emulation of sunkbd(4) has been turned on
1058 by default. In order to make the special symbols of the Sun
1059 keyboards driven by sunkbd(4) work under X these now have
1060 to be configured the same way as Sun USB keyboards driven
1061 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1063 Option "XkbLayout" "us"
1064 Option "XkbRules" "xorg"
1065 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1068 It has been decided that it is desirable to provide ABI
1069 backwards compatibility to the FreeBSD 4/5/6 versions of the
1070 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1071 broken with the introduction of PCI domain support (see the
1072 20070930 entry). Unfortunately, this required the ABI of
1073 PCIOCGETCONF to be broken again in order to be able to
1074 provide backwards compatibility to the old version of that
1075 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1076 again. As for prominent ports this affects neither pciutils
1077 nor xorg-server this time, the hal port needs to be rebuilt
1081 The misnamed kthread_create() and friends have been renamed
1082 to kproc_create() etc. Many of the callers already
1083 used kproc_start()..
1084 I will return kthread_create() and friends in a while
1085 with implementations that actually create threads, not procs.
1086 Renaming corresponds with version 800002.
1095 Avoid using make -j when upgrading. While generally safe, there are
1096 sometimes problems using -j to upgrade. If your upgrade fails with
1097 -j, please try again without -j. From time to time in the past there
1098 have been problems using -j with buildworld and/or installworld. This
1099 is especially true when upgrading between "distant" versions (eg one
1100 that cross a major release boundary or several minor releases, or when
1101 several months have passed on the -current branch).
1103 Sometimes, obscure build problems are the result of environment
1104 poisoning. This can happen because the make utility reads its
1105 environment when searching for values for global variables. To run
1106 your build attempts in an "environmental clean room", prefix all make
1107 commands with 'env -i '. See the env(1) manual page for more details.
1109 When upgrading from one major version to another it is generally best
1110 to upgrade to the latest code in the currently installed branch first,
1111 then do an upgrade to the new branch. This is the best-tested upgrade
1112 path, and has the highest probability of being successful. Please try
1113 this approach before reporting problems with a major version upgrade.
1117 When upgrading the boot ZFS pool to a new version, always follow
1120 1.) recompile and reinstall the ZFS boot loader and boot block
1121 (this is part of "make buildworld" and "make installworld")
1123 2.) update the ZFS boot block on your boot drive
1125 The following example updates the ZFS boot block on the first
1126 partition (freebsd-boot) of a GPT partitioned drive ad0:
1127 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1129 Non-boot pools do not need these updates.
1133 If you are updating from a prior version of FreeBSD (even one just
1134 a few days old), you should follow this procedure. It is the most
1135 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1137 make kernel-toolchain
1138 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1139 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1141 To test a kernel once
1142 ---------------------
1143 If you just want to boot a kernel once (because you are not sure
1144 if it works, or if you want to boot a known bad kernel to provide
1145 debugging information) run
1146 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1147 nextboot -k testkernel
1149 To just build a kernel when you know that it won't mess you up
1150 --------------------------------------------------------------
1151 This assumes you are already running a CURRENT system. Replace
1152 ${arch} with the architecture of your machine (e.g. "i386",
1153 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1155 cd src/sys/${arch}/conf
1156 config KERNEL_NAME_HERE
1157 cd ../compile/KERNEL_NAME_HERE
1162 If this fails, go to the "To build a kernel" section.
1164 To rebuild everything and install it on the current system.
1165 -----------------------------------------------------------
1166 # Note: sometimes if you are running current you gotta do more than
1167 # is listed here if you are upgrading from a really old current.
1169 <make sure you have good level 0 dumps>
1171 make kernel KERNCONF=YOUR_KERNEL_HERE
1173 <reboot in single user> [3]
1181 To cross-install current onto a separate partition
1182 --------------------------------------------------
1183 # In this approach we use a separate partition to hold
1184 # current's root, 'usr', and 'var' directories. A partition
1185 # holding "/", "/usr" and "/var" should be about 2GB in
1188 <make sure you have good level 0 dumps>
1191 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1192 <maybe newfs current's root partition>
1193 <mount current's root partition on directory ${CURRENT_ROOT}>
1194 make installworld DESTDIR=${CURRENT_ROOT}
1195 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1196 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1197 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1198 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1199 <reboot into current>
1200 <do a "native" rebuild/install as described in the previous section>
1201 <maybe install compatibility libraries from ports/misc/compat*>
1205 To upgrade in-place from 8.x-stable to current
1206 ----------------------------------------------
1207 <make sure you have good level 0 dumps>
1209 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1211 <reboot in single user> [3]
1218 Make sure that you've read the UPDATING file to understand the
1219 tweaks to various things you need. At this point in the life
1220 cycle of current, things change often and you are on your own
1221 to cope. The defaults can also change, so please read ALL of
1222 the UPDATING entries.
1224 Also, if you are tracking -current, you must be subscribed to
1225 freebsd-current@freebsd.org. Make sure that before you update
1226 your sources that you have read and understood all the recent
1227 messages there. If in doubt, please track -stable which has
1228 much fewer pitfalls.
1230 [1] If you have third party modules, such as vmware, you
1231 should disable them at this point so they don't crash your
1234 [3] From the bootblocks, boot -s, and then do
1239 adjkerntz -i # if CMOS is wall time
1240 Also, when doing a major release upgrade, it is required that
1241 you boot into single user mode to do the installworld.
1243 [4] Note: This step is non-optional. Failure to do this step
1244 can result in a significant reduction in the functionality of the
1245 system. Attempting to do it by hand is not recommended and those
1246 that pursue this avenue should read this file carefully, as well
1247 as the archives of freebsd-current and freebsd-hackers mailing lists
1248 for potential gotchas. The -U option is also useful to consider.
1249 See mergemaster(8) for more information.
1251 [5] Usually this step is a noop. However, from time to time
1252 you may need to do this if you get unknown user in the following
1253 step. It never hurts to do it all the time. You may need to
1254 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1255 install) after the buildworld before this step if you last updated
1256 from current before 20020224 or from -stable before 20020408.
1258 [6] This only deletes old files and directories. Old libraries
1259 can be deleted by "make delete-old-libs", but you have to make
1260 sure that no program is using those libraries anymore.
1262 [8] In order to have a kernel that can run the 4.x binaries needed to
1263 do an installworld, you must include the COMPAT_FREEBSD4 option in
1264 your kernel. Failure to do so may leave you with a system that is
1265 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1266 required to run the 5.x binaries on more recent kernels. And so on
1267 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1269 Make sure that you merge any new devices from GENERIC since the
1270 last time you updated your kernel config file.
1272 [9] When checking out sources, you must include the -P flag to have
1273 cvs prune empty directories.
1275 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1276 "?=" instead of the "=" assignment operator, so that buildworld can
1277 override the CPUTYPE if it needs to.
1279 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1280 not on the command line, or in /etc/make.conf. buildworld will
1281 warn if it is improperly defined.
1284 This file contains a list, in reverse chronological order, of major
1285 breakages in tracking -current. Not all things will be listed here,
1286 and it only starts on October 16, 2004. Updating files can found in
1287 previous releases if your system is older than this.
1289 Copyright information:
1291 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1293 Redistribution, publication, translation and use, with or without
1294 modification, in full or in part, in any form or format of this
1295 document are permitted without further permission from the author.
1297 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1298 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1299 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1300 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1301 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1302 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1303 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1304 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1305 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1306 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1307 POSSIBILITY OF SUCH DAMAGE.
1309 Contact Warner Losh if you have any questions about your use of