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