1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 7.x IS SLOW:
12 FreeBSD 7.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance.
25 Sound infrastructure has been updated with various fixes and
26 improvements. Most of the changes are pretty much transparent,
27 with exceptions of followings:
28 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
29 moved to their own dev sysctl nodes, for example:
30 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
31 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
32 own chardev in the form of "dsp%d.<function>%d", where <function>
33 is p = playback, r = record and v = virtual, respectively. Users
34 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
35 This does not affect those who are using "/dev/dsp".
38 The following binaries have been disconnected from the build:
39 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
40 and mount_std. The functionality of these programs has been
41 moved into the mount program. For example, to mount a devfs
42 filesystem, instead of using mount_devfs, use: "mount -t devfs".
43 This does not affect entries in /etc/fstab, since entries in
44 /etc/fstab are always processed with "mount -t fstype".
47 Support for PCI Message Signalled Interrupts on i386 and amd64
48 has been added to the kernel and various drivers will soon be
49 updated to use MSI when it is available. If there are any problems,
50 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
51 and 'hw.pci.enable_msix' tunables to 0 in the loader.
54 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
55 The lockmgr object layout has been changed as a result of having
56 a lock_object embedded in it. As a consequence all file system
57 kernel modules must be re-compiled. The mutex profiling man page
58 has not yet been updated to reflect this change.
61 KSE in the kernel has now been made optional and turned on by
62 default. Use 'nooption KSE' in your kernel config to turn it
63 off. All kernel modules *must* be recompiled after this change.
64 There-after, modules from a KSE kernel should be compatible with
65 modules from a NOKSE kernel due to the temporary padding fields
66 added to 'struct proc'.
69 mrouted and its utilities have been removed from the base system.
72 Some ioctl(2) command codes have changed. Full backward ABI
73 compatibility is provided if the "options COMPAT_FREEBSD6" is
74 present in the kernel configuration file. Make sure to add
75 this option to your kernel config file, or recompile X.Org
76 and the rest of ports; otherwise they may refuse to work.
79 tcpslice has been removed from the base system.
82 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
83 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
84 systat needs to be rebuilt.
87 libpcap updated to v0.9.4 and tcpdump to v3.9.4
90 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
91 for IPFIREWALL_FORWARD is now as it was before when it was first
92 committed and for years after. The behaviour is now ON.
95 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
96 Now it can decrypt files created from different architectures.
97 Unfortunately, it is no longer able to decrypt a cipher text
98 generated with an older version on 64 bit architectures.
99 If you have such a file, you need old utility to decrypt it.
102 The interface version of the i4b kernel part has changed. So
103 after updating the kernel sources and compiling a new kernel,
104 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
105 be rebuilt, and vice versa.
108 The XBOX kernel now defaults to the nfe(4) driver instead of
109 the nve(4) driver. Please update your configuration
113 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
114 PCnet family of NICs has been removed. The new le(4) driver serves
115 as an equivalent but cross-platform replacement with the pcn(4)
116 driver still providing performance-optimized support for the subset
117 of AMD Am79C971 PCnet-FAST and greater chips as before.
120 The machdep.* sysctls and the adjkerntz utility have been
121 modified a bit. The new adjkerntz utility uses the new
122 sysctl names and sysctlbyname() calls, so it may be impossible
123 to run an old /sbin/adjkerntz utility in single-user mode
124 with a new kernel. Replace the `adjkerntz -i' step before
125 `make installworld' with:
127 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
129 and proceed as usual with the rest of the installworld-stage
130 steps. Otherwise, you risk installing binaries with their
131 timestamp set several hours in the future, especially if
132 you are running with local time set to GMT+X hours.
135 The ip6fw utility has been removed. The behavior provided by
136 ip6fw has been in ipfw2 for a good while and the rc.d scripts
137 have been updated to deal with it. There are some rules that
138 might not migrate cleanly. Use rc.firewall6 as a template to
142 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
143 attachments have been removed. Make sure to configure scc(4)
144 on sparc64. Note also that by default puc(4) will use uart(4)
145 and not sio(4) for serial ports because interrupt handling has
146 been optimized for multi-port serial cards and only uart(4)
147 implements the interface to support it.
150 The scc(4) driver replaces puc(4) for Serial Communications
151 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
152 Z8530. On sparc64, it is advised to add scc(4) to the kernel
153 configuration to make sure that the serial ports remain
157 Most world/kernel related NO_* build options changed names.
158 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
159 after FreeBSD ports) and should be set in /etc/src.conf
160 (the src.conf(5) manpage is provided). Full backwards
161 compatibility is maintained for the time being though it's
162 highly recommended to start moving old options out of the
163 system-wide /etc/make.conf file into the new /etc/src.conf
164 while also properly renaming them. More conversions will
165 likely follow. Posting to current@:
167 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
170 The NETSMBCRYPTO kernel option has been retired because its
171 functionality is always included in NETSMB and smbfs.ko now.
174 The TDFX_LINUX kernel option was retired and replaced by the
175 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
176 kernel module. Loading it alone should suffice to get 3dfx support
177 for Linux apps because it will pull in 3dfx.ko and linux.ko through
181 The 'audit' group was added to support the new auditing functionality
182 in the base system. Be sure to follow the directions for updating,
183 including the requirement to run mergemaster -p.
186 The kernel ABI to file system modules was changed on i386.
187 Please make sure that your kernel and modules are in sync.
190 This actually occured some time ago, but installing the kernel
191 now also installs a bunch of symbol files for the kernel modules.
192 This increases the size of /boot/kernel to about 67Mbytes. You
193 will need twice this if you will eventually back this up to kernel.old
194 on your next install.
195 If you have a shortage of room in your root partition, you should add
196 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
197 to your /etc/make.conf.
200 libc's malloc implementation has been replaced. This change has the
201 potential to uncover application bugs that previously went unnoticed.
202 See the malloc(3) manual page for more details.
205 The generic netgraph(4) cookie has been changed. If you upgrade
206 kernel passing this point, you also need to upgrade userland
207 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
210 si(4)'s device files now contain the unit number.
211 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
214 The kernel ABI was mostly destroyed due to a change in the size
215 of struct lock_object which is nested in other structures such
216 as mutexes which are nested in all sorts of other structures.
217 Make sure your kernel and modules are in sync.
220 The page coloring algorithm in the VM subsystem was converted
221 from tuning with kernel options to autotuning. Please remove
222 any PQ_* option except PQ_NOOPT from your kernel config.
225 The net80211-related tools in the tools/tools/ath directory
226 have been moved to tools/tools/net80211 and renamed with a
227 "wlan" prefix. Scripts that use them should be adjusted
231 Scripts in the local_startup directories (as defined in
232 /etc/defaults/rc.conf) that have the new rc.d semantics will
233 now be run as part of the base system rcorder. If there are
234 errors or problems with one of these local scripts, it could
235 cause boot problems. If you encounter such problems, boot in
236 single user mode, remove that script from the */rc.d directory.
237 Please report the problem to the port's maintainer, and the
238 freebsd-ports@freebsd.org mailing list.
241 The nodev mount option was deprecated in RELENG_6 (where it
242 was a no-op), and is now unsupported. If you have nodev or dev listed
243 in /etc/fstab, remove it, otherwise it will result in a mount error.
246 ABI between ipfw(4) and ipfw(8) has been changed. You need
247 to rebuild ipfw(8) when rebuilding kernel.
250 rp(4)'s device files now contain the unit number.
251 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
254 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
255 Its /etc/rc.conf.d configuration file has been `ppp' from
256 the beginning, and hence there is no need to touch it.
259 Now most modules get their build-time options from the kernel
260 configuration file. A few modules still have fixed options
261 due to their non-conformant implementation, but they will be
262 corrected eventually. You may need to review the options of
263 the modules in use, explicitly specify the non-default options
264 in the kernel configuration file, and rebuild the kernel and
268 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
269 to turn polling(4) on your interfaces.
272 The old bridge(4) implementation was retired. The new
273 if_bridge(4) serves as a full functional replacement.
276 The ai_addrlen of a struct addrinfo was changed to a socklen_t
277 to conform to POSIX-2001. This change broke an ABI
278 compatibility on 64 bit architecture. You have to recompile
279 userland programs that use getaddrinfo(3) on 64 bit
283 RELENG_6 branched here.
286 The pccard_ifconfig rc.conf variable has been removed and a new
287 variable, ifconfig_DEFAULT has been introduced. Unlike
288 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
289 do not have ifconfig_ifn entries rather than just those in
290 removable_interfaces.
293 Some previous versions of PAM have permitted the use of
294 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
295 to third party PAM modules in /usr/local/lib. A change has been
296 made to require the use of absolute paths in order to avoid
297 ambiguity and dependence on library path configuration, which may
298 affect existing configurations.
301 Major changes to network interface API. All drivers must be
302 recompiled. Drivers not in the base system will need to be
303 updated to the new APIs.
306 Changes were made to kinfo_proc in sys/user.h. Please recompile
307 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
308 will not behave correctly.
310 The API and ABI for hwpmc(4) have changed with the addition
311 of sampling support. Please recompile lib/libpmc(3) and
312 usr.sbin/{pmcstat,pmccontrol}.
315 The OpenBSD dhclient was imported in place of the ISC dhclient
316 and the network interface configuration scripts were updated
317 accordingly. If you use DHCP to configure your interfaces, you
318 must now run devd. Also, DNS updating was lost so you will need
319 to find a workaround if you use this feature.
321 The '_dhcp' user was added to support the OpenBSD dhclient. Be
322 sure to run mergemaster -p (like you are supposed to do every time
326 if_bridge was added to the tree. This has changed struct ifnet.
327 Please recompile userland and all network related modules.
330 The n_net of a struct netent was changed to an uint32_t, and
331 1st argument of getnetbyaddr() was changed to an uint32_t, to
332 conform to POSIX-2001. These changes broke an ABI
333 compatibility on 64 bit architecture. With these changes,
334 shlib major of libpcap was bumped. You have to recompile
335 userland programs that use getnetbyaddr(3), getnetbyname(3),
336 getnetent(3) and/or libpcap on 64 bit architecture.
339 Kernel parsing of extra options on '#!' first lines of shell
340 scripts has changed. Lines with multiple options likely will
341 fail after this date. For full details, please see
342 http://people.freebsd.org/~gad/Updating-20050528.txt
345 The packet filter (pf) code has been updated to OpenBSD 3.7
346 Please note the changed anchor syntax and the fact that
347 authpf(8) now needs a mounted fdescfs(5) to function.
350 The NO_MIXED_MODE kernel option has been removed from the i386
351 amd64 platforms as its use has been superceded by the new local
352 APIC timer code. Any kernel config files containing this option
356 The on-disk format of LC_CTYPE files was changed to be machine
357 independent. Please make sure NOT to use NO_CLEAN buildworld
358 when crossing this point. Crossing this point also requires
359 recompile or reinstall of all locale depended packages.
362 The ifi_epoch member of struct if_data has been changed to
363 contain the uptime at which the interface was created or the
364 statistics zeroed rather then the wall clock time because
365 wallclock time may go backwards. This should have no impact
366 unless an snmp implementation is using this value (I know of
370 The acpi_perf and acpi_throttle drivers are now part of the
371 acpi(4) main module. They are no longer built separately.
374 The layout of struct image_params has changed. You have to
375 recompile all compatibility modules (linux, svr4, etc) for use
379 The p4tcc driver has been merged into cpufreq(4). This makes
380 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
381 compile in "device cpufreq" to restore this functionality.
384 The responsibility of recomputing the file system summary of
385 a SoftUpdates-enabled dirty volume has been transferred to the
386 background fsck. A rebuild of fsck(8) utility is recommended
387 if you have updated the kernel.
389 To get the old behavior (recompute file system summary at mount
390 time), you can set vfs.ffs.compute_summary_at_mount=1 before
391 mounting the new volume.
394 The cpufreq import is complete. As part of this, the sysctls for
395 acpi(4) throttling have been removed. The power_profile script
396 has been updated, so you can use performance/economy_cpu_freq in
397 rc.conf(5) to set AC on/offline cpu frequencies.
400 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
401 requires recompiling libnetgraph and userland netgraph utilities.
404 Support for abbreviated forms of a number of ipfw options is
405 now deprecated. Warnings are printed to stderr indicating the
406 correct full form when a match occurs. Some abbreviations may
407 be supported at a later date based on user feedback. To be
408 considered for support, abbreviations must be in use prior to
409 this commit and unlikely to be confused with current key words.
412 By a popular demand, a lot of NOFOO options were renamed
413 to NO_FOO (see bsd.compat.mk for a full list). The old
414 spellings are still supported, but will cause annoying
415 warnings on stderr. Make sure you upgrade properly (see
416 the COMMON ITEMS: section later in this file).
419 Auto-loading of ancillary wlan modules such as wlan_wep has
420 been temporarily disabled; you need to statically configure
421 the modules you need into your kernel or explicitly load them
422 prior to use. Specifically, if you intend to use WEP encryption
423 with an 802.11 device load/configure wlan_wep; if you want to
424 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
425 and wlan_xauth as required.
428 The behaviour of ppp(8) has changed slightly. If lqr is enabled
429 (``enable lqr''), older versions would revert to LCP ECHO mode on
430 negotiation failure. Now, ``enable echo'' is required for this
431 behaviour. The ppp version number has been bumped to 3.4.2 to
435 The wlan support has been updated to split the crypto support
436 into separate modules. For static WEP you must configure the
437 wlan_wep module in your system or build and install the module
438 in place where it can be loaded (the kernel will auto-load
439 the module when a wep key is configured).
442 The ath driver has been updated to split the tx rate control
443 algorithm into a separate module. You need to include either
444 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
447 Support for systems with an 80386 CPU has been removed. Please
448 use FreeBSD 5.x or earlier on systems with an 80386.
451 We have had a hack which would mount the root filesystem
452 R/W if the device were named 'md*'. As part of the vnode
453 work I'm doing I have had to remove this hack. People
454 building systems which use preloaded MD root filesystems
455 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
456 their /etc/rc scripts.
459 FreeBSD 5.3 shipped here.
462 The size of struct tcpcb has changed again due to the removal
463 of RFC1644 T/TCP. You have to recompile userland programs that
464 read kmem for tcp sockets directly (netstat, sockstat, etc.)
467 The size of struct tcpcb has changed. You have to recompile
468 userland programs that read kmem for tcp sockets directly
469 (netstat, sockstat, etc.)
472 RELENG_5 branched here. For older entries, please see updating
473 in the RELENG_5 branch.
479 Avoid using make -j when upgrading. From time to time in the
480 past there have been problems using -j with buildworld and/or
481 installworld. This is especially true when upgrading between
482 "distant" versions (eg one that cross a major release boundary
483 or several minor releases, or when several months have passed
484 on the -current branch).
486 Sometimes, obscure build problems are the result of environment
487 poisoning. This can happen because the make utility reads its
488 environment when searching for values for global variables.
489 To run your build attempts in an "environmental clean room",
490 prefix all make commands with 'env -i '. See the env(1) manual
491 page for more details.
493 When upgrading from one major version to another it is generally
494 best to upgrade to the latest code in the currently installed branch
495 first, then do an upgrade to the new branch. This is the best-tested
496 upgrade path, and has the highest probability of being successful.
497 Please try this approach before reporting problems with a major
502 If you are updating from a prior version of FreeBSD (even one just
503 a few days old), you should follow this procedure. It is the most
504 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
506 make kernel-toolchain
507 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
508 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
510 To test a kernel once
511 ---------------------
512 If you just want to boot a kernel once (because you are not sure
513 if it works, or if you want to boot a known bad kernel to provide
514 debugging information) run
515 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
516 nextboot -k testkernel
518 To just build a kernel when you know that it won't mess you up
519 --------------------------------------------------------------
520 This assumes you are already running a 5.X system. Replace
521 ${arch} with the architecture of your machine (e.g. "i386",
522 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
524 cd src/sys/${arch}/conf
525 config KERNEL_NAME_HERE
526 cd ../compile/KERNEL_NAME_HERE
531 If this fails, go to the "To build a kernel" section.
533 To rebuild everything and install it on the current system.
534 -----------------------------------------------------------
535 # Note: sometimes if you are running current you gotta do more than
536 # is listed here if you are upgrading from a really old current.
538 <make sure you have good level 0 dumps>
540 make kernel KERNCONF=YOUR_KERNEL_HERE
542 <reboot in single user> [3]
550 To cross-install current onto a separate partition
551 --------------------------------------------------
552 # In this approach we use a separate partition to hold
553 # current's root, 'usr', and 'var' directories. A partition
554 # holding "/", "/usr" and "/var" should be about 2GB in
557 <make sure you have good level 0 dumps>
560 make buildkernel KERNCONF=YOUR_KERNEL_HERE
561 <maybe newfs current's root partition>
562 <mount current's root partition on directory ${CURRENT_ROOT}>
563 make installworld DESTDIR=${CURRENT_ROOT}
564 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
565 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
566 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
567 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
568 <reboot into current>
569 <do a "native" rebuild/install as described in the previous section>
570 <maybe install compatibility libraries from src/lib/compat>
574 To upgrade in-place from 5.x-stable to current
575 ----------------------------------------------
576 <make sure you have good level 0 dumps>
578 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
580 <reboot in single user> [3]
587 Make sure that you've read the UPDATING file to understand the
588 tweaks to various things you need. At this point in the life
589 cycle of current, things change often and you are on your own
590 to cope. The defaults can also change, so please read ALL of
591 the UPDATING entries.
593 Also, if you are tracking -current, you must be subscribed to
594 freebsd-current@freebsd.org. Make sure that before you update
595 your sources that you have read and understood all the recent
596 messages there. If in doubt, please track -stable which has
599 [1] If you have third party modules, such as vmware, you
600 should disable them at this point so they don't crash your
603 [3] From the bootblocks, boot -s, and then do
608 adjkerntz -i # if CMOS is wall time
609 Also, when doing a major release upgrade, it is required that
610 you boot into single user mode to do the installworld.
612 [4] Note: This step is non-optional. Failure to do this step
613 can result in a significant reduction in the functionality of the
614 system. Attempting to do it by hand is not recommended and those
615 that pursue this avenue should read this file carefully, as well
616 as the archives of freebsd-current and freebsd-hackers mailing lists
617 for potential gotchas.
619 [5] Usually this step is a noop. However, from time to time
620 you may need to do this if you get unknown user in the following
621 step. It never hurts to do it all the time. You may need to
622 install a new mergemaster (cd src/usr.sbin/mergemaster && make
623 install) after the buildworld before this step if you last updated
624 from current before 20020224 or from -stable before 20020408.
626 [8] In order to have a kernel that can run the 4.x binaries
627 needed to do an installworld, you must include the COMPAT_FREEBSD4
628 option in your kernel. Failure to do so may leave you with a system
629 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
630 is required to run the 5.x binaries on more recent kernels.
632 Make sure that you merge any new devices from GENERIC since the
633 last time you updated your kernel config file.
635 [9] When checking out sources, you must include the -P flag to have
636 cvs prune empty directories.
638 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
639 "?=" instead of the "=" assignment operator, so that buildworld can
640 override the CPUTYPE if it needs to.
642 MAKEOBJDIRPREFIX must be defined in an environment variable, and
643 not on the command line, or in /etc/make.conf. buildworld will
644 warn if it is improperly defined.
647 This file contains a list, in reverse chronological order, of major
648 breakages in tracking -current. Not all things will be listed here,
649 and it only starts on October 16, 2004. Updating files can found in
650 previous releases if your system is older than this.
652 Copyright information:
654 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
656 Redistribution, publication, translation and use, with or without
657 modification, in full or in part, in any form or format of this
658 document are permitted without further permission from the author.
660 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
661 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
662 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
663 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
664 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
665 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
666 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
667 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
668 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
669 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
670 POSSIBILITY OF SUCH DAMAGE.
672 If you find this document useful, and you want to, you may buy the
675 Contact Warner Losh if you have any questions about your use of