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 Support for PCI Message Signalled Interrupts has been
26 re-enabled in the bge driver, only for those chips which are
27 believed to support it properly. If there are any problems,
28 MSI can be disabled completely by setting the
29 'hw.pci.enable_msi' and 'hw.pci.enable_msix' tunables to 0
33 Support for PCI Message Signalled Interrupts has been
34 disabled again in the bge driver. Many revisions of the
35 hardware fail to support it properly. Support can be
36 re-enabled by removing the #define of BGE_DISABLE_MSI in
37 "src/sys/dev/bge/if_bge.c".
40 Support for PCI Message Signalled Interrupts has been added
41 to the bge driver. If there are any problems, MSI can be
42 disabled completely by setting the 'hw.pci.enable_msi' and
43 'hw.pci.enable_msix' tunables to 0 in the loader.
46 The removal of several facets of the experimental Threading
47 system from the kernel means that the proc and thread structures
48 have changed quite a bit. I suggest all kernel modules that might
49 reference these structures be recompiled.. Especially the
53 Sound infrastructure has been updated with various fixes and
54 improvements. Most of the changes are pretty much transparent,
55 with exceptions of followings:
56 1) All sound driver specific sysctls (hw.snd.pcm%d.*) have been
57 moved to their own dev sysctl nodes, for example:
58 hw.snd.pcm0.vchans -> dev.pcm.0.vchans
59 2) /dev/dspr%d.%d has been deprecated. Each channel now has its
60 own chardev in the form of "dsp%d.<function>%d", where <function>
61 is p = playback, r = record and v = virtual, respectively. Users
62 are encouraged to use these devs instead of (old) "/dev/dsp%d.%d".
63 This does not affect those who are using "/dev/dsp".
66 The following binaries have been disconnected from the build:
67 mount_devfs, mount_ext2fs, mount_fdescfs, mount_procfs, mount_linprocfs,
68 and mount_std. The functionality of these programs has been
69 moved into the mount program. For example, to mount a devfs
70 filesystem, instead of using mount_devfs, use: "mount -t devfs".
71 This does not affect entries in /etc/fstab, since entries in
72 /etc/fstab are always processed with "mount -t fstype".
75 Support for PCI Message Signalled Interrupts on i386 and amd64
76 has been added to the kernel and various drivers will soon be
77 updated to use MSI when it is available. If there are any problems,
78 MSI can be disabled completely by setting the 'hw.pci.enable_msi'
79 and 'hw.pci.enable_msix' tunables to 0 in the loader.
82 The MUTEX_PROFILING option has been renamed to LOCK_PROFILING.
83 The lockmgr object layout has been changed as a result of having
84 a lock_object embedded in it. As a consequence all file system
85 kernel modules must be re-compiled. The mutex profiling man page
86 has not yet been updated to reflect this change.
89 KSE in the kernel has now been made optional and turned on by
90 default. Use 'nooption KSE' in your kernel config to turn it
91 off. All kernel modules *must* be recompiled after this change.
92 There-after, modules from a KSE kernel should be compatible with
93 modules from a NOKSE kernel due to the temporary padding fields
94 added to 'struct proc'.
97 mrouted and its utilities have been removed from the base system.
100 Some ioctl(2) command codes have changed. Full backward ABI
101 compatibility is provided if the "options COMPAT_FREEBSD6" is
102 present in the kernel configuration file. Make sure to add
103 this option to your kernel config file, or recompile X.Org
104 and the rest of ports; otherwise they may refuse to work.
107 tcpslice has been removed from the base system.
110 The sizes of struct tcpcb (and struct xtcpcb) have changed due to
111 the rewrite of TCP syncookies. Tools like netstat, sockstat, and
112 systat needs to be rebuilt.
115 libpcap updated to v0.9.4 and tcpdump to v3.9.4
118 The IPFIREWALL_FORWARD_EXTENDED option is gone and the behaviour
119 for IPFIREWALL_FORWARD is now as it was before when it was first
120 committed and for years after. The behaviour is now ON.
123 enigma(1)/crypt(1) utility has been changed on 64 bit architectures.
124 Now it can decrypt files created from different architectures.
125 Unfortunately, it is no longer able to decrypt a cipher text
126 generated with an older version on 64 bit architectures.
127 If you have such a file, you need old utility to decrypt it.
130 The interface version of the i4b kernel part has changed. So
131 after updating the kernel sources and compiling a new kernel,
132 the i4b user space tools in "/usr/src/usr.sbin/i4b" must also
133 be rebuilt, and vice versa.
136 The XBOX kernel now defaults to the nfe(4) driver instead of
137 the nve(4) driver. Please update your configuration
141 The i386-only lnc(4) driver for the AMD Am7900 LANCE and Am79C9xx
142 PCnet family of NICs has been removed. The new le(4) driver serves
143 as an equivalent but cross-platform replacement with the pcn(4)
144 driver still providing performance-optimized support for the subset
145 of AMD Am79C971 PCnet-FAST and greater chips as before.
148 The machdep.* sysctls and the adjkerntz utility have been
149 modified a bit. The new adjkerntz utility uses the new
150 sysctl names and sysctlbyname() calls, so it may be impossible
151 to run an old /sbin/adjkerntz utility in single-user mode
152 with a new kernel. Replace the `adjkerntz -i' step before
153 `make installworld' with:
155 /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
157 and proceed as usual with the rest of the installworld-stage
158 steps. Otherwise, you risk installing binaries with their
159 timestamp set several hours in the future, especially if
160 you are running with local time set to GMT+X hours.
163 The ip6fw utility has been removed. The behavior provided by
164 ip6fw has been in ipfw2 for a good while and the rc.d scripts
165 have been updated to deal with it. There are some rules that
166 might not migrate cleanly. Use rc.firewall6 as a template to
170 The puc(4) driver has been overhauled. The ebus(4) and sbus(4)
171 attachments have been removed. Make sure to configure scc(4)
172 on sparc64. Note also that by default puc(4) will use uart(4)
173 and not sio(4) for serial ports because interrupt handling has
174 been optimized for multi-port serial cards and only uart(4)
175 implements the interface to support it.
178 The scc(4) driver replaces puc(4) for Serial Communications
179 Controllers (SCCs) like the Siemens SAB82532 and the Zilog
180 Z8530. On sparc64, it is advised to add scc(4) to the kernel
181 configuration to make sure that the serial ports remain
185 Most world/kernel related NO_* build options changed names.
186 New knobs have common prefixes WITHOUT_*/WITH_* (modelled
187 after FreeBSD ports) and should be set in /etc/src.conf
188 (the src.conf(5) manpage is provided). Full backwards
189 compatibility is maintained for the time being though it's
190 highly recommended to start moving old options out of the
191 system-wide /etc/make.conf file into the new /etc/src.conf
192 while also properly renaming them. More conversions will
193 likely follow. Posting to current@:
195 http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
198 The NETSMBCRYPTO kernel option has been retired because its
199 functionality is always included in NETSMB and smbfs.ko now.
202 The TDFX_LINUX kernel option was retired and replaced by the
203 tdfx_linux device. The latter can be loaded as the 3dfx_linux.ko
204 kernel module. Loading it alone should suffice to get 3dfx support
205 for Linux apps because it will pull in 3dfx.ko and linux.ko through
209 The 'audit' group was added to support the new auditing functionality
210 in the base system. Be sure to follow the directions for updating,
211 including the requirement to run mergemaster -p.
214 The kernel ABI to file system modules was changed on i386.
215 Please make sure that your kernel and modules are in sync.
218 This actually occured some time ago, but installing the kernel
219 now also installs a bunch of symbol files for the kernel modules.
220 This increases the size of /boot/kernel to about 67Mbytes. You
221 will need twice this if you will eventually back this up to kernel.old
222 on your next install.
223 If you have a shortage of room in your root partition, you should add
224 -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes"
225 to your /etc/make.conf.
228 libc's malloc implementation has been replaced. This change has the
229 potential to uncover application bugs that previously went unnoticed.
230 See the malloc(3) manual page for more details.
233 The generic netgraph(4) cookie has been changed. If you upgrade
234 kernel passing this point, you also need to upgrade userland
235 and netgraph(4) utilities like ports/net/mpd or ports/net/mpd4.
238 si(4)'s device files now contain the unit number.
239 Uses of {cua,tty}A[0-9a-f] should be replaced by {cua,tty}A0[0-9a-f].
242 The kernel ABI was mostly destroyed due to a change in the size
243 of struct lock_object which is nested in other structures such
244 as mutexes which are nested in all sorts of other structures.
245 Make sure your kernel and modules are in sync.
248 The page coloring algorithm in the VM subsystem was converted
249 from tuning with kernel options to autotuning. Please remove
250 any PQ_* option except PQ_NOOPT from your kernel config.
253 The net80211-related tools in the tools/tools/ath directory
254 have been moved to tools/tools/net80211 and renamed with a
255 "wlan" prefix. Scripts that use them should be adjusted
259 Scripts in the local_startup directories (as defined in
260 /etc/defaults/rc.conf) that have the new rc.d semantics will
261 now be run as part of the base system rcorder. If there are
262 errors or problems with one of these local scripts, it could
263 cause boot problems. If you encounter such problems, boot in
264 single user mode, remove that script from the */rc.d directory.
265 Please report the problem to the port's maintainer, and the
266 freebsd-ports@freebsd.org mailing list.
269 The nodev mount option was deprecated in RELENG_6 (where it
270 was a no-op), and is now unsupported. If you have nodev or dev listed
271 in /etc/fstab, remove it, otherwise it will result in a mount error.
274 ABI between ipfw(4) and ipfw(8) has been changed. You need
275 to rebuild ipfw(8) when rebuilding kernel.
278 rp(4)'s device files now contain the unit number.
279 Uses of {cua,tty}R[0-9a-f] should be replaced by {cua,tty}R0[0-9a-f].
282 /etc/rc.d/ppp-user has been renamed to /etc/rc.d/ppp.
283 Its /etc/rc.conf.d configuration file has been `ppp' from
284 the beginning, and hence there is no need to touch it.
287 Now most modules get their build-time options from the kernel
288 configuration file. A few modules still have fixed options
289 due to their non-conformant implementation, but they will be
290 corrected eventually. You may need to review the options of
291 the modules in use, explicitly specify the non-default options
292 in the kernel configuration file, and rebuild the kernel and
296 kern.polling.enable sysctl MIB is now deprecated. Use ifconfig(8)
297 to turn polling(4) on your interfaces.
300 The old bridge(4) implementation was retired. The new
301 if_bridge(4) serves as a full functional replacement.
304 The ai_addrlen of a struct addrinfo was changed to a socklen_t
305 to conform to POSIX-2001. This change broke an ABI
306 compatibility on 64 bit architecture. You have to recompile
307 userland programs that use getaddrinfo(3) on 64 bit
311 RELENG_6 branched here.
314 The pccard_ifconfig rc.conf variable has been removed and a new
315 variable, ifconfig_DEFAULT has been introduced. Unlike
316 pccard_ifconfig, ifconfig_DEFAULT applies to ALL interfaces that
317 do not have ifconfig_ifn entries rather than just those in
318 removable_interfaces.
321 Some previous versions of PAM have permitted the use of
322 non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
323 to third party PAM modules in /usr/local/lib. A change has been
324 made to require the use of absolute paths in order to avoid
325 ambiguity and dependence on library path configuration, which may
326 affect existing configurations.
329 Major changes to network interface API. All drivers must be
330 recompiled. Drivers not in the base system will need to be
331 updated to the new APIs.
334 Changes were made to kinfo_proc in sys/user.h. Please recompile
335 userland, or commands like `fstat', `pkill', `ps', `top' and `w'
336 will not behave correctly.
338 The API and ABI for hwpmc(4) have changed with the addition
339 of sampling support. Please recompile lib/libpmc(3) and
340 usr.sbin/{pmcstat,pmccontrol}.
343 The OpenBSD dhclient was imported in place of the ISC dhclient
344 and the network interface configuration scripts were updated
345 accordingly. If you use DHCP to configure your interfaces, you
346 must now run devd. Also, DNS updating was lost so you will need
347 to find a workaround if you use this feature.
349 The '_dhcp' user was added to support the OpenBSD dhclient. Be
350 sure to run mergemaster -p (like you are supposed to do every time
354 if_bridge was added to the tree. This has changed struct ifnet.
355 Please recompile userland and all network related modules.
358 The n_net of a struct netent was changed to an uint32_t, and
359 1st argument of getnetbyaddr() was changed to an uint32_t, to
360 conform to POSIX-2001. These changes broke an ABI
361 compatibility on 64 bit architecture. With these changes,
362 shlib major of libpcap was bumped. You have to recompile
363 userland programs that use getnetbyaddr(3), getnetbyname(3),
364 getnetent(3) and/or libpcap on 64 bit architecture.
367 Kernel parsing of extra options on '#!' first lines of shell
368 scripts has changed. Lines with multiple options likely will
369 fail after this date. For full details, please see
370 http://people.freebsd.org/~gad/Updating-20050528.txt
373 The packet filter (pf) code has been updated to OpenBSD 3.7
374 Please note the changed anchor syntax and the fact that
375 authpf(8) now needs a mounted fdescfs(5) to function.
378 The NO_MIXED_MODE kernel option has been removed from the i386
379 amd64 platforms as its use has been superceded by the new local
380 APIC timer code. Any kernel config files containing this option
384 The on-disk format of LC_CTYPE files was changed to be machine
385 independent. Please make sure NOT to use NO_CLEAN buildworld
386 when crossing this point. Crossing this point also requires
387 recompile or reinstall of all locale depended packages.
390 The ifi_epoch member of struct if_data has been changed to
391 contain the uptime at which the interface was created or the
392 statistics zeroed rather then the wall clock time because
393 wallclock time may go backwards. This should have no impact
394 unless an snmp implementation is using this value (I know of
398 The acpi_perf and acpi_throttle drivers are now part of the
399 acpi(4) main module. They are no longer built separately.
402 The layout of struct image_params has changed. You have to
403 recompile all compatibility modules (linux, svr4, etc) for use
407 The p4tcc driver has been merged into cpufreq(4). This makes
408 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or
409 compile in "device cpufreq" to restore this functionality.
412 The responsibility of recomputing the file system summary of
413 a SoftUpdates-enabled dirty volume has been transferred to the
414 background fsck. A rebuild of fsck(8) utility is recommended
415 if you have updated the kernel.
417 To get the old behavior (recompute file system summary at mount
418 time), you can set vfs.ffs.compute_summary_at_mount=1 before
419 mounting the new volume.
422 The cpufreq import is complete. As part of this, the sysctls for
423 acpi(4) throttling have been removed. The power_profile script
424 has been updated, so you can use performance/economy_cpu_freq in
425 rc.conf(5) to set AC on/offline cpu frequencies.
428 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko)
429 requires recompiling libnetgraph and userland netgraph utilities.
432 Support for abbreviated forms of a number of ipfw options is
433 now deprecated. Warnings are printed to stderr indicating the
434 correct full form when a match occurs. Some abbreviations may
435 be supported at a later date based on user feedback. To be
436 considered for support, abbreviations must be in use prior to
437 this commit and unlikely to be confused with current key words.
440 By a popular demand, a lot of NOFOO options were renamed
441 to NO_FOO (see bsd.compat.mk for a full list). The old
442 spellings are still supported, but will cause annoying
443 warnings on stderr. Make sure you upgrade properly (see
444 the COMMON ITEMS: section later in this file).
447 Auto-loading of ancillary wlan modules such as wlan_wep has
448 been temporarily disabled; you need to statically configure
449 the modules you need into your kernel or explicitly load them
450 prior to use. Specifically, if you intend to use WEP encryption
451 with an 802.11 device load/configure wlan_wep; if you want to
452 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp,
453 and wlan_xauth as required.
456 The behaviour of ppp(8) has changed slightly. If lqr is enabled
457 (``enable lqr''), older versions would revert to LCP ECHO mode on
458 negotiation failure. Now, ``enable echo'' is required for this
459 behaviour. The ppp version number has been bumped to 3.4.2 to
463 The wlan support has been updated to split the crypto support
464 into separate modules. For static WEP you must configure the
465 wlan_wep module in your system or build and install the module
466 in place where it can be loaded (the kernel will auto-load
467 the module when a wep key is configured).
470 The ath driver has been updated to split the tx rate control
471 algorithm into a separate module. You need to include either
472 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
475 Support for systems with an 80386 CPU has been removed. Please
476 use FreeBSD 5.x or earlier on systems with an 80386.
479 We have had a hack which would mount the root filesystem
480 R/W if the device were named 'md*'. As part of the vnode
481 work I'm doing I have had to remove this hack. People
482 building systems which use preloaded MD root filesystems
483 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
484 their /etc/rc scripts.
487 FreeBSD 5.3 shipped here.
490 The size of struct tcpcb has changed again due to the removal
491 of RFC1644 T/TCP. You have to recompile userland programs that
492 read kmem for tcp sockets directly (netstat, sockstat, etc.)
495 The size of struct tcpcb has changed. You have to recompile
496 userland programs that read kmem for tcp sockets directly
497 (netstat, sockstat, etc.)
500 RELENG_5 branched here. For older entries, please see updating
501 in the RELENG_5 branch.
507 Avoid using make -j when upgrading. From time to time in the
508 past there have been problems using -j with buildworld and/or
509 installworld. This is especially true when upgrading between
510 "distant" versions (eg one that cross a major release boundary
511 or several minor releases, or when several months have passed
512 on the -current branch).
514 Sometimes, obscure build problems are the result of environment
515 poisoning. This can happen because the make utility reads its
516 environment when searching for values for global variables.
517 To run your build attempts in an "environmental clean room",
518 prefix all make commands with 'env -i '. See the env(1) manual
519 page for more details.
521 When upgrading from one major version to another it is generally
522 best to upgrade to the latest code in the currently installed branch
523 first, then do an upgrade to the new branch. This is the best-tested
524 upgrade path, and has the highest probability of being successful.
525 Please try this approach before reporting problems with a major
530 If you are updating from a prior version of FreeBSD (even one just
531 a few days old), you should follow this procedure. It is the most
532 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
534 make kernel-toolchain
535 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
536 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
538 To test a kernel once
539 ---------------------
540 If you just want to boot a kernel once (because you are not sure
541 if it works, or if you want to boot a known bad kernel to provide
542 debugging information) run
543 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
544 nextboot -k testkernel
546 To just build a kernel when you know that it won't mess you up
547 --------------------------------------------------------------
548 This assumes you are already running a 5.X system. Replace
549 ${arch} with the architecture of your machine (e.g. "i386",
550 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
552 cd src/sys/${arch}/conf
553 config KERNEL_NAME_HERE
554 cd ../compile/KERNEL_NAME_HERE
559 If this fails, go to the "To build a kernel" section.
561 To rebuild everything and install it on the current system.
562 -----------------------------------------------------------
563 # Note: sometimes if you are running current you gotta do more than
564 # is listed here if you are upgrading from a really old current.
566 <make sure you have good level 0 dumps>
568 make kernel KERNCONF=YOUR_KERNEL_HERE
570 <reboot in single user> [3]
578 To cross-install current onto a separate partition
579 --------------------------------------------------
580 # In this approach we use a separate partition to hold
581 # current's root, 'usr', and 'var' directories. A partition
582 # holding "/", "/usr" and "/var" should be about 2GB in
585 <make sure you have good level 0 dumps>
588 make buildkernel KERNCONF=YOUR_KERNEL_HERE
589 <maybe newfs current's root partition>
590 <mount current's root partition on directory ${CURRENT_ROOT}>
591 make installworld DESTDIR=${CURRENT_ROOT}
592 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
593 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
594 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
595 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
596 <reboot into current>
597 <do a "native" rebuild/install as described in the previous section>
598 <maybe install compatibility libraries from src/lib/compat>
602 To upgrade in-place from 5.x-stable to current
603 ----------------------------------------------
604 <make sure you have good level 0 dumps>
606 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
608 <reboot in single user> [3]
615 Make sure that you've read the UPDATING file to understand the
616 tweaks to various things you need. At this point in the life
617 cycle of current, things change often and you are on your own
618 to cope. The defaults can also change, so please read ALL of
619 the UPDATING entries.
621 Also, if you are tracking -current, you must be subscribed to
622 freebsd-current@freebsd.org. Make sure that before you update
623 your sources that you have read and understood all the recent
624 messages there. If in doubt, please track -stable which has
627 [1] If you have third party modules, such as vmware, you
628 should disable them at this point so they don't crash your
631 [3] From the bootblocks, boot -s, and then do
636 adjkerntz -i # if CMOS is wall time
637 Also, when doing a major release upgrade, it is required that
638 you boot into single user mode to do the installworld.
640 [4] Note: This step is non-optional. Failure to do this step
641 can result in a significant reduction in the functionality of the
642 system. Attempting to do it by hand is not recommended and those
643 that pursue this avenue should read this file carefully, as well
644 as the archives of freebsd-current and freebsd-hackers mailing lists
645 for potential gotchas.
647 [5] Usually this step is a noop. However, from time to time
648 you may need to do this if you get unknown user in the following
649 step. It never hurts to do it all the time. You may need to
650 install a new mergemaster (cd src/usr.sbin/mergemaster && make
651 install) after the buildworld before this step if you last updated
652 from current before 20020224 or from -stable before 20020408.
654 [8] In order to have a kernel that can run the 4.x binaries
655 needed to do an installworld, you must include the COMPAT_FREEBSD4
656 option in your kernel. Failure to do so may leave you with a system
657 that is hard to boot to recover. A similar kernel option COMPAT_FREEBSD5
658 is required to run the 5.x binaries on more recent kernels.
660 Make sure that you merge any new devices from GENERIC since the
661 last time you updated your kernel config file.
663 [9] When checking out sources, you must include the -P flag to have
664 cvs prune empty directories.
666 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
667 "?=" instead of the "=" assignment operator, so that buildworld can
668 override the CPUTYPE if it needs to.
670 MAKEOBJDIRPREFIX must be defined in an environment variable, and
671 not on the command line, or in /etc/make.conf. buildworld will
672 warn if it is improperly defined.
675 This file contains a list, in reverse chronological order, of major
676 breakages in tracking -current. Not all things will be listed here,
677 and it only starts on October 16, 2004. Updating files can found in
678 previous releases if your system is older than this.
680 Copyright information:
682 Copyright 1998-2005 M. Warner Losh. All Rights Reserved.
684 Redistribution, publication, translation and use, with or without
685 modification, in full or in part, in any form or format of this
686 document are permitted without further permission from the author.
688 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
689 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
690 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
691 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
692 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
693 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
694 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
695 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
696 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
697 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
698 POSSIBILITY OF SUCH DAMAGE.
700 If you find this document useful, and you want to, you may buy the
703 Contact Warner Losh if you have any questions about your use of