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 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process from
17 older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang and llvm have been upgraded to 3.7.0. Please see the
36 20141231 entry below for information about prerequisites and upgrading,
37 if you are not already using 3.5.0 or higher.
40 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
41 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
42 default, i.e., they will not contain "::". For example, instead
43 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
44 to have a more specific match, such as different map entries for
45 IPv6:0:0 vs IPv6:0. This change requires that configuration
46 data (including maps, files, classes, custom ruleset, etc.) must
47 use the same format, so make certain such configuration data is
48 upgrading. As a very simple check search for patterns like
49 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
50 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
51 the cf option UseCompressedIPv6Addresses.
54 The default kernel entropy-processing algorithm is now
55 Fortuna, replacing Yarrow.
57 Assuming you have 'device random' in your kernel config
58 file, the configurations allow a kernel option to override
59 this default. You may choose *ONE* of:
61 options RANDOM_YARROW # Legacy /dev/random algorithm.
62 options RANDOM_DUMMY # Blocking-only driver.
64 If you have neither, you get Fortuna. For most people,
65 read no further, Fortuna will give a /dev/random that works
66 like it always used to, and the difference will be irrelevant.
68 If you remove 'device random', you get *NO* kernel-processed
69 entopy at all. This may be acceptable to folks building
70 embedded systems, but has complications. Carry on reading,
71 and it is assumed you know what you need.
73 *PLEASE* read random(4) and random(9) if you are in the
74 habit of tweeking kernel configs, and/or if you are a member
75 of the embedded community, wanting specific and not-usual
76 behaviour from your security subsystems.
78 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
79 random', you will NOT have a functioning /dev/random, and
80 many cryptographic features will not work, including SSH.
81 You may also find strange behaviour from the random(3) set
82 of library functions, in particular sranddev(3), srandomdev(3)
83 and arc4random(3). The reason for this is that the KERN_ARND
84 sysctl only returns entropy if it thinks it has some to
85 share, and with RANDOM_DUMMY or no 'device random' this
89 An additional fix for the issue described in the 20150614 sendmail
90 entry below has been been committed in revision 284717.
93 FreeBSD's old make (fmake) has been removed from the system. It is
94 available as the devel/fmake port or via pkg install fmake.
97 The fix for the issue described in the 20150614 sendmail entry
98 below has been been committed in revision 284436. The work
99 around described in that entry is no longer needed unless the
100 default setting is overridden by a confDH_PARAMETERS configuration
101 setting of '5' or pointing to a 512 bit DH parameter file.
104 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
105 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
106 and devel/kyua to version 0.20+ and adjust any calling code to work
107 with Kyuafile and kyua.
110 The import of openssl to address the FreeBSD-SA-15:10.openssl
111 security advisory includes a change which rejects handshakes
112 with DH parameters below 768 bits. sendmail releases prior
113 to 8.15.2 (not yet released), defaulted to a 512 bit
114 DH parameter setting for client connections. To work around
115 this interoperability, sendmail can be configured to use a
116 2048 bit DH parameter by:
118 1. Edit /etc/mail/`hostname`.mc
119 2. If a setting for confDH_PARAMETERS does not exist or
120 exists and is set to a string beginning with '5',
122 3. If a setting for confDH_PARAMETERS exists and is set to
123 a file path, create a new file with:
124 openssl dhparam -out /path/to/file 2048
125 4. Rebuild the .cf file:
126 cd /etc/mail/; make; make install
128 cd /etc/mail/; make restart
130 A sendmail patch is coming, at which time this file will be
134 Generation of legacy formatted entries have been disabled by default
135 in pwd_mkdb(8), as all base system consumers of the legacy formatted
136 entries were converted to use the new format by default when the new,
137 machine independent format have been added and supported since FreeBSD
140 Please see the pwd_mkdb(8) manual page for further details.
143 Clang and llvm have been upgraded to 3.6.1 release. Please see the
144 20141231 entry below for information about prerequisites and upgrading,
145 if you are not already using 3.5.0 or higher.
148 TI platform code switched to using vendor DTS files and this update
149 may break existing systems running on Beaglebone, Beaglebone Black,
152 - dtb files should be regenerated/reinstalled. Filenames are the
153 same but content is different now
154 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
155 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
156 addressing scheme is now pin 25 on /dev/gpioc3.
157 - Pandaboard: /etc/ttys should be updated, serial console device is
158 now /dev/ttyu2, not /dev/ttyu0
161 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
162 If you need the GNU extension from groff soelim(1), install groff
163 from package: pkg install groff, or via ports: textproc/groff.
166 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
167 defined in symlink(7); previously symlinks were silently ignored.
170 The const qualifier has been removed from iconv(3) to comply with
171 POSIX. The ports tree is aware of this from r384038 onwards.
174 Libraries specified by LIBADD in Makefiles must have a corresponding
175 DPADD_<lib> variable to ensure correct dependencies. This is now
176 enforced in src.libnames.mk.
179 From legacy ata(4) driver was removed support for SATA controllers
180 supported by more functional drivers ahci(4), siis(4) and mvs(4).
181 Kernel modules ataahci and ataadaptec were removed completely,
182 replaced by ahci and mvs modules respectively.
185 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
186 the 20141231 entry below for information about prerequisites and
187 upgrading, if you are not already using 3.5.0 or higher.
190 The 32-bit PowerPC kernel has been changed to a position-independent
191 executable. This can only be booted with a version of loader(8)
192 newer than January 31, 2015, so make sure to update both world and
193 kernel before rebooting.
196 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
197 but before r278950, the RNG was not seeded properly. Immediately
198 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
199 ssh keys or openssl keys) that were generated w/ a kernel from that
200 range. This does not affect programs that directly used /dev/random
201 or /dev/urandom. All userland uses of arc4random(3) are affected.
204 The autofs(4) ABI was changed in order to restore binary compatibility
205 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
209 The powerpc64 kernel has been changed to a position-independent
210 executable. This can only be booted with a new version of loader(8),
211 so make sure to update both world and kernel before rebooting.
214 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
215 only release, no new features have been added. Please see the 20141231
216 entry below for information about prerequisites and upgrading, if you
217 are not already using 3.5.0.
220 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
221 taken from the ELF Tool Chain project rather than GNU binutils. They
222 should be drop-in replacements, with the addition of arm64 support.
223 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
224 binutils tools, if necessary.
227 The default Unbound configuration now enables remote control
228 using a local socket. Users who have already enabled the
229 local_unbound service should regenerate their configuration
230 by running "service local_unbound setup" as root.
233 The GNU texinfo and GNU info pages have been removed.
234 To be able to view GNU info pages please install texinfo from ports.
237 Clang, llvm and lldb have been upgraded to 3.5.0 release.
239 As of this release, a prerequisite for building clang, llvm and lldb is
240 a C++11 capable compiler and C++11 standard library. This means that to
241 be able to successfully build the cross-tools stage of buildworld, with
242 clang as the bootstrap compiler, your system compiler or cross compiler
243 should either be clang 3.3 or later, or gcc 4.8 or later, and your
244 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
247 On any standard FreeBSD 10.x or 11.x installation, where clang and
248 libc++ are on by default (that is, on x86 or arm), this should work out
251 On 9.x installations where clang is enabled by default, e.g. on x86 and
252 powerpc, libc++ will not be enabled by default, so libc++ should be
253 built (with clang) and installed first. If both clang and libc++ are
254 missing, build clang first, then use it to build libc++.
256 On 8.x and earlier installations, upgrade to 9.x first, and then follow
257 the instructions for 9.x above.
259 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
260 default, and do not build clang.
262 Many embedded systems are resource constrained, and will not be able to
263 build clang in a reasonable time, or in some cases at all. In those
264 cases, cross building bootable systems on amd64 is a workaround.
266 This new version of clang introduces a number of new warnings, of which
267 the following are most likely to appear:
271 This warns in two cases, for both C and C++:
272 * When the code is trying to take the absolute value of an unsigned
273 quantity, which is effectively a no-op, and almost never what was
274 intended. The code should be fixed, if at all possible. If you are
275 sure that the unsigned quantity can be safely cast to signed, without
276 loss of information or undefined behavior, you can add an explicit
277 cast, or disable the warning.
279 * When the code is trying to take an absolute value, but the called
280 abs() variant is for the wrong type, which can lead to truncation.
281 If you want to disable the warning instead of fixing the code, please
282 make sure that truncation will not occur, or it might lead to unwanted
285 -Wtautological-undefined-compare and
286 -Wundefined-bool-conversion
288 These warn when C++ code is trying to compare 'this' against NULL, while
289 'this' should never be NULL in well-defined C++ code. However, there is
290 some legacy (pre C++11) code out there, which actively abuses this
291 feature, which was less strictly defined in previous C++ versions.
293 Squid and openjdk do this, for example. The warning can be turned off
294 for C++98 and earlier, but compiling the code in C++11 mode might result
295 in unexpected behavior; for example, the parts of the program that are
296 unreachable could be optimized away.
299 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
300 kernel sources have been removed. The .h files remain, since some
301 utilities include them. This will need to be fixed later.
302 If "mount -t oldnfs ..." is attempted, it will fail.
303 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
304 the utilities will report errors.
307 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
308 directories to top level SUBDIR variable when their parent
309 directory is included in LOCAL_DIRS. Users with build systems with
310 such hierarchies and without SUBDIR entries in the parent
311 directory Makefiles should add them or add the directories to
315 faith(4) and faithd(8) have been removed from the base system. Faith
316 has been obsolete for a very long time.
319 vt(4), the new console driver, is enabled by default. It brings
320 support for Unicode and double-width characters, as well as
321 support for UEFI and integration with the KMS kernel video
324 You may need to update your console settings in /etc/rc.conf,
325 most probably the keymap. During boot, /etc/rc.d/syscons will
326 indicate what you need to do.
328 vt(4) still has issues and lacks some features compared to
329 syscons(4). See the wiki for up-to-date information:
330 https://wiki.freebsd.org/Newcons
332 If you want to keep using syscons(4), you can do so by adding
333 the following line to /boot/loader.conf:
337 pjdfstest has been integrated into kyua as an opt-in test suite.
338 Please see share/doc/pjdfstest/README for more details on how to
342 gperf has been removed from the base system for architectures
343 that use clang. Ports that require gperf will obtain it from the
347 pjdfstest has been moved from tools/regression/pjdfstest to
351 At svn r271982, The default linux compat kernel ABI has been adjusted
352 to 2.6.18 in support of the linux-c6 compat ports infrastructure
353 update. If you wish to continue using the linux-f10 compat ports,
354 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
355 encouraged to update their linux-compat packages to linux-c6 during
356 their next update cycle.
359 The ofwfb driver, used to provide a graphics console on PowerPC when
360 using vt(4), no longer allows mmap() of all physical memory. This
361 will prevent Xorg on PowerPC with some ATI graphics cards from
362 initializing properly unless x11-servers/xorg-server is updated to
366 The xdev targets have been converted to using TARGET and
367 TARGET_ARCH instead of XDEV and XDEV_ARCH.
370 The default unbound configuration has been modified to address
371 issues with reverse lookups on networks that use private
372 address ranges. If you use the local_unbound service, run
373 "service local_unbound setup" as root to regenerate your
374 configuration, then "service local_unbound reload" to load the
378 The GNU texinfo and GNU info pages are not built and installed
379 anymore, WITH_INFO knob has been added to allow to built and install
381 UPDATE: see 20150102 entry on texinfo's removal
384 The GNU readline library is now an INTERNALLIB - that is, it is
385 statically linked into consumers (GDB and variants) in the base
386 system, and the shared library is no longer installed. The
387 devel/readline port is available for third party software that
391 The Itanium architecture (ia64) has been removed from the list of
392 known architectures. This is the first step in the removal of the
396 Commit r268115 has added NFSv4.1 server support, merged from
397 projects/nfsv4.1-server. Since this includes changes to the
398 internal interfaces between the NFS related modules, a full
399 build of the kernel and modules will be necessary.
400 __FreeBSD_version has been bumped.
403 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
404 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
405 which differs from the behaviour controlled by this knob.)
408 Maximal length of the serial number in CTL was increased from 16 to
409 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
410 and ctld, need to be rebuilt to work with a new kernel.
413 The libatf-c and libatf-c++ major versions were downgraded to 0 and
414 1 respectively to match the upstream numbers. They were out of
415 sync because, when they were originally added to FreeBSD, the
416 upstream versions were not respected. These libraries are private
417 and not yet built by default, so renumbering them should be a
418 non-issue. However, unclean source trees will yield broken test
419 programs once the operator executes "make delete-old-libs" after a
422 Additionally, the atf-sh binary was made private by moving it into
423 /usr/libexec/. Already-built shell test programs will keep the
424 path to the old binary so they will break after "make delete-old"
427 If you are using WITH_TESTS=yes (not the default), wipe the object
428 tree and rebuild from scratch to prevent spurious test failures.
429 This is only needed once: the misnumbered libraries and misplaced
430 binaries have been added to OptionalObsoleteFiles.inc so they will
431 be removed during a clean upgrade.
434 Clang and llvm have been upgraded to 3.4.1 release.
437 We bogusly installed src.opts.mk in /usr/share/mk. This file should
438 be removed to avoid issues in the future (and has been added to
442 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
443 past, it affected all builds that used the bsd.*.mk files. The old
444 behavior was a bug, but people may have relied upon it. To get this
445 behavior back, you can .include /etc/src.conf from /etc/make.conf
446 (which is still global and isn't changed). This also changes the
447 behavior of incremental builds inside the tree of individual
448 directories. Set MAKESYSPATH to ".../share/mk" to do that.
449 Although this has survived make universe and some upgrade scenarios,
450 other upgrade scenarios may have broken. At least one form of
451 temporary breakage was fixed with MAKESYSPATH settings for buildworld
452 as well... In cases where MAKESYSPATH isn't working with this
453 setting, you'll need to set it to the full path to your tree.
455 One side effect of all this cleaning up is that bsd.compiler.mk
456 is no longer implicitly included by bsd.own.mk. If you wish to
457 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
461 The lindev device has been removed since /dev/full has been made a
462 standard device. __FreeBSD_version has been bumped.
465 The knob WITHOUT_VI was added to the base system, which controls
466 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
467 in order to reorder files share/termcap and didn't build ex(1) as a
468 build tool, so building/installing with WITH_VI is highly advised for
469 build hosts for older releases.
471 This issue has been fixed in stable/9 and stable/10 in r277022 and
472 r276991, respectively.
475 The YES_HESIOD knob has been removed. It has been obsolete for
476 a decade. Please move to using WITH_HESIOD instead or your builds
477 will silently lack HESIOD.
480 The uart(4) driver has been changed with respect to its handling
481 of the low-level console. Previously the uart(4) driver prevented
482 any process from changing the baudrate or the CLOCAL and HUPCL
483 control flags. By removing the restrictions, operators can make
484 changes to the serial console port without having to reboot.
485 However, when getty(8) is started on the serial device that is
486 associated with the low-level console, a misconfigured terminal
487 line in /etc/ttys will now have a real impact.
488 Before upgrading the kernel, make sure that /etc/ttys has the
489 serial console device configured as 3wire without baudrate to
490 preserve the previous behaviour. E.g:
491 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
494 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
495 to improve performance. To re-enable it, if needed, run rpcbind
496 with command line option -W.
499 Switched back to the GPL dtc compiler due to updates in the upstream
500 dts files not being supported by the BSDL dtc compiler. You will need
501 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
502 may result while building dtb files during a kernel build if you fail
503 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
506 Clang and llvm have been upgraded to 3.4 release.
509 The nve(4) driver has been removed. Please use the nfe(4) driver
510 for NVIDIA nForce MCP Ethernet adapters instead.
513 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
514 This could cause certain C++ applications using shared libraries built
515 against the previous version of libc++ to crash. The incompatibility
516 has now been fixed, but any C++ applications or shared libraries built
517 between r261283 and r261801 should be recompiled.
520 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
521 capability mode support. Please note that enabling the feature in
522 kernel is still highly recommended.
525 OpenSSH is now built with sandbox support, and will use sandbox as
526 the default privilege separation method. This requires Capsicum
527 capability mode support in kernel.
530 The libelf and libdwarf libraries have been updated to newer
531 versions from upstream. Shared library version numbers for
532 these two libraries were bumped. Any ports or binaries
533 requiring these two libraries should be recompiled.
534 __FreeBSD_version is bumped to 1100006.
537 If a Makefile in a tests/ directory was auto-generating a Kyuafile
538 instead of providing an explicit one, this would prevent such
539 Makefile from providing its own Kyuafile in the future during
540 NO_CLEAN builds. This has been fixed in the Makefiles but manual
541 intervention is needed to clean an objdir if you use NO_CLEAN:
542 # find /usr/obj -name Kyuafile | xargs rm -f
545 The behavior of gss_pseudo_random() for the krb5 mechanism
546 has changed, for applications requesting a longer random string
547 than produced by the underlying enctype's pseudo-random() function.
548 In particular, the random string produced from a session key of
549 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
550 be different at the 17th octet and later, after this change.
551 The counter used in the PRF+ construction is now encoded as a
552 big-endian integer in accordance with RFC 4402.
553 __FreeBSD_version is bumped to 1100004.
556 The WITHOUT_ATF build knob has been removed and its functionality
557 has been subsumed into the more generic WITHOUT_TESTS. If you were
558 using the former to disable the build of the ATF libraries, you
559 should change your settings to use the latter.
562 The default version of mtree is nmtree which is obtained from
563 NetBSD. The output is generally the same, but may vary
564 slightly. If you found you need identical output adding
565 "-F freebsd9" to the command line should do the trick. For the
566 time being, the old mtree is available as fmtree.
569 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
570 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
571 1.1.4_8 and verify bsdyml not linked in, before running "make
573 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
575 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
578 The rc.d/jail script has been updated to support jail(8)
579 configuration file. The "jail_<jname>_*" rc.conf(5) variables
580 for per-jail configuration are automatically converted to
581 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
582 This is transparently backward compatible. See below about some
583 incompatibilities and rc.conf(5) manual page for more details.
585 These variables are now deprecated in favor of jail(8) configuration
586 file. One can use "rc.d/jail config <jname>" command to generate
587 a jail(8) configuration file in /var/run/jail.<jname>.conf without
588 running the jail(8) utility. The default pathname of the
589 configuration file is /etc/jail.conf and can be specified by
590 using $jail_conf or $jail_<jname>_conf variables.
592 Please note that jail_devfs_ruleset accepts an integer at
593 this moment. Please consider to rewrite the ruleset name
597 BIND has been removed from the base system. If all you need
598 is a local resolver, simply enable and start the local_unbound
599 service instead. Otherwise, several versions of BIND are
600 available in the ports tree. The dns/bind99 port is one example.
602 With this change, nslookup(1) and dig(1) are no longer in the base
603 system. Users should instead use host(1) and drill(1) which are
604 in the base system. Alternatively, nslookup and dig can
605 be obtained by installing the dns/bind-tools port.
608 With the addition of unbound(8), a new unbound user is now
609 required during installworld. "mergemaster -p" can be used to
610 add the user prior to installworld, as documented in the handbook.
613 OpenSSH is now built with DNSSEC support, and will by default
614 silently trust signed SSHFP records. This can be controlled with
615 the VerifyHostKeyDNS client configuration setting. DNSSEC support
616 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
619 The GNU Compiler Collection and C++ standard library (libstdc++)
620 are no longer built by default on platforms where clang is the system
621 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
625 The PROCDESC kernel option is now part of the GENERIC kernel
626 configuration and is required for the rwhod(8) to work.
627 If you are using custom kernel configuration, you should include
631 The API and ABI related to the Capsicum framework was modified
632 in backward incompatible way. The userland libraries and programs
633 have to be recompiled to work with the new kernel. This includes the
634 following libraries and programs, but the whole buildworld is
635 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
636 kdump, procstat, rwho, rwhod, uniq.
639 AES-NI intrinsic support has been added to gcc. The AES-NI module
640 has been updated to use this support. A new gcc is required to build
641 the aesni module on both i386 and amd64.
644 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
645 Thus "device padlock_rng" and "device rdrand_rng" should be
646 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
649 WITH_ICONV has been split into two feature sets. WITH_ICONV now
650 enables just the iconv* functionality and is now on by default.
651 WITH_LIBICONV_COMPAT enables the libiconv api and link time
652 compatability. Set WITHOUT_ICONV to build the old way.
653 If you have been using WITH_ICONV before, you will very likely
654 need to turn on WITH_LIBICONV_COMPAT.
657 INVARIANTS option now enables DEBUG for code with OpenSolaris and
658 Illumos origin, including ZFS. If you have INVARIANTS in your
659 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
661 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
662 locks if WITNESS option was set. Because that generated a lot of
663 witness(9) reports and all of them were believed to be false
664 positives, this is no longer done. New option OPENSOLARIS_WITNESS
665 can be used to achieve the previous behavior.
668 Timer values in IPv6 data structures now use time_uptime instead
669 of time_second. Although this is not a user-visible functional
670 change, userland utilities which directly use them---ndp(8),
671 rtadvd(8), and rtsold(8) in the base system---need to be updated
675 find -delete can now delete the pathnames given as arguments,
676 instead of only files found below them or if the pathname did
677 not contain any slashes. Formerly, the following error message
680 find: -delete: <path>: relative path potentially not safe
682 Deleting the pathnames given as arguments can be prevented
683 without error messages using -mindepth 1 or by changing
684 directory and passing "." as argument to find. This works in the
685 old as well as the new version of find.
688 Behavior of devfs rules path matching has been changed.
689 Pattern is now always matched against fully qualified devfs
690 path and slash characters must be explicitly matched by
691 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
692 subdirectories must be reviewed.
695 The default ARM ABI has changed to the ARM EABI. The old ABI is
696 incompatible with the ARM EABI and all programs and modules will
697 need to be rebuilt to work with a new kernel.
699 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
701 NOTE: Support for the old ABI will be removed in the future and
702 users are advised to upgrade.
705 pkg_install has been disconnected from the build if you really need it
706 you should add WITH_PKGTOOLS in your src.conf(5).
709 Most of network statistics structures were changed to be able
710 keep 64-bits counters. Thus all tools, that work with networking
711 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
714 Fix targets that run multiple make's to use && rather than ;
715 so that subsequent steps depend on success of previous.
717 NOTE: if building 'universe' with -j* on stable/8 or stable/9
718 it would be better to start the build using bmake, to avoid
719 overloading the machine.
722 Fix a bug that allowed a tracing process (e.g. gdb) to write
723 to a memory-mapped file in the traced process's address space
724 even if neither the traced process nor the tracing process had
725 write access to that file.
728 CVS has been removed from the base system. An exact copy
729 of the code is available from the devel/cvs port.
732 Some people report the following error after the switch to bmake:
734 make: illegal option -- J
735 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
737 *** [buildworld] Error code 2
739 this likely due to an old instance of make in
740 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
741 which src/Makefile will use that blindly, if it exists, so if
742 you see the above error:
744 rm -rf `make -V MAKEPATH`
749 Use bmake by default.
750 Whereas before one could choose to build with bmake via
751 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
752 make. The goal is to remove these knobs for 10-RELEASE.
754 It is worth noting that bmake (like gmake) treats the command
755 line as the unit of failure, rather than statements within the
756 command line. Thus '(cd some/where && dosomething)' is safer
757 than 'cd some/where; dosomething'. The '()' allows consistent
758 behavior in parallel build.
761 Fix a bug that allows NFS clients to issue READDIR on files.
764 The WITHOUT_IDEA option has been removed because
765 the IDEA patent expired.
768 The sysctl which controls TRIM support under ZFS has been renamed
769 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
773 The mergemaster command now uses the default MAKEOBJDIRPREFIX
774 rather than creating it's own in the temporary directory in
775 order allow access to bootstrapped versions of tools such as
776 install and mtree. When upgrading from version of FreeBSD where
777 the install command does not support -l, you will need to
778 install a new mergemaster command if mergemaster -p is required.
779 This can be accomplished with the command (cd src/usr.sbin/mergemaster
783 Legacy ATA stack, disabled and replaced by new CAM-based one since
784 FreeBSD 9.0, completely removed from the sources. Kernel modules
785 atadisk and atapi*, user-level tools atacontrol and burncd are
786 removed. Kernel option `options ATA_CAM` is now permanently enabled
790 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
791 and socketpair(2). Software, in particular Kerberos, may
792 automatically detect and use these during building. The resulting
793 binaries will not work on older kernels.
796 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
797 information, see the respective 20130304 entry).
800 Recent commits to callout(9) changed the size of struct callout,
801 so the KBI is probably heavily disturbed. Also, some functions
802 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
803 by macros. Every kernel module using it won't load, so rebuild
806 The ctl device has been re-enabled in GENERIC for i386 and amd64,
807 but does not initialize by default (because of the new CTL_DISABLE
808 option) to save memory. To re-enable it, remove the CTL_DISABLE
809 option from the kernel config file or set kern.cam.ctl.disable=0
810 in /boot/loader.conf.
813 The ctl device has been disabled in GENERIC for i386 and amd64.
814 This was done due to the extra memory being allocated at system
815 initialisation time by the ctl driver which was only used if
816 a CAM target device was created. This makes a FreeBSD system
817 unusable on 128MB or less of RAM.
820 A new compression method (lz4) has been merged to -HEAD. Please
821 refer to zpool-features(7) for more information.
823 Please refer to the "ZFS notes" section of this file for information
824 on upgrading boot ZFS pools.
827 A BSD-licensed patch(1) variant has been added and is installed
828 as bsdpatch, being the GNU version the default patch.
829 To inverse the logic and use the BSD-licensed one as default,
830 while having the GNU version installed as gnupatch, rebuild
831 and install world with the WITH_BSD_PATCH knob set.
834 Due to the use of the new -l option to install(1) during build
835 and install, you must take care not to directly set the INSTALL
836 make variable in your /etc/make.conf, /etc/src.conf, or on the
837 command line. If you wish to use the -C flag for all installs
838 you may be able to add INSTALL+=-C to /etc/make.conf or
842 The install(1) option -M has changed meaning and now takes an
843 argument that is a file or path to append logs to. In the
844 unlikely event that -M was the last option on the command line
845 and the command line contained at least two files and a target
846 directory the first file will have logs appended to it. The -M
847 option served little practical purpose in the last decade so its
848 use is expected to be extremely rare.
851 After switching to Clang as the default compiler some users of ZFS
852 on i386 systems started to experience stack overflow kernel panics.
853 Please consider using 'options KSTACK_PAGES=4' in such configurations.
856 GEOM_LABEL now mangles label names read from file system metadata.
857 Mangling affect labels containing spaces, non-printable characters,
858 '%' or '"'. Device names in /etc/fstab and other places may need to
862 By default, only the 10 most recent kernel dumps will be saved. To
863 restore the previous behaviour (no limit on the number of kernel dumps
864 stored in the dump directory) add the following line to /etc/rc.conf:
869 With the addition of auditdistd(8), a new auditdistd user is now
870 required during installworld. "mergemaster -p" can be used to
871 add the user prior to installworld, as documented in the handbook.
874 The sin6_scope_id member variable in struct sockaddr_in6 is now
875 filled by the kernel before passing the structure to the userland via
876 sysctl or routing socket. This means the KAME-specific embedded scope
877 id in sin6_addr.s6_addr[2] is always cleared in userland application.
878 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
879 __FreeBSD_version is bumped to 1000025.
882 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
883 This means that the world and kernel will be compiled with clang
884 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
885 and /usr/bin/cpp. To disable this behavior and revert to building
886 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
887 of current may need to bootstrap WITHOUT_CLANG first if the clang
888 build fails (its compatibility window doesn't extend to the 9 stable
892 The IPFIREWALL_FORWARD kernel option has been removed. Its
893 functionality now turned on by default.
896 The ZERO_COPY_SOCKET kernel option has been removed and
897 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
898 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
899 mechanism which is not safe and may result in kernel crashes.
900 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
901 driver supports disposeable external page sized mbuf storage.
902 Proper replacements for both zero-copy mechanisms are under
903 consideration and will eventually lead to complete removal
904 of the two kernel options.
907 The IPv4 network stack has been converted to network byte
908 order. The following modules need to be recompiled together
909 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
910 pf(4), ipfw(4), ng_ipfw(4), stf(4).
913 Support for non-MPSAFE filesystems was removed from VFS. The
914 VFS_VERSION was bumped, all filesystem modules shall be
918 All the non-MPSAFE filesystems have been disconnected from
919 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
920 portalfs, smbfs, xfs.
923 The interface cloning API and ABI has changed. The following
924 modules need to be recompiled together with kernel:
925 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
926 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
927 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
930 The sdhci driver was split in two parts: sdhci (generic SD Host
931 Controller logic) and sdhci_pci (actual hardware driver).
932 No kernel config modifications are required, but if you
933 load sdhc as a module you must switch to sdhci_pci instead.
936 Import the FUSE kernel and userland support into base system.
939 The GNU sort(1) program has been removed since the BSD-licensed
940 sort(1) has been the default for quite some time and no serious
941 problems have been reported. The corresponding WITH_GNU_SORT
945 The pfil(9) API/ABI for AF_INET family has been changed. Packet
946 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
950 The net80211(4) ABI has been changed to allow for improved driver
951 PS-POLL and power-save support. All wireless drivers need to be
952 recompiled to work with the new kernel.
955 The random(4) support for the VIA hardware random number
956 generator (`PADLOCK') is no longer enabled unconditionally.
957 Add the padlock_rng device in the custom kernel config if
958 needed. The GENERIC kernels on i386 and amd64 do include the
959 device, so the change only affects the custom kernel
963 The pf(4) packet filter ABI has been changed. pfctl(8) and
964 snmp_pf module need to be recompiled to work with new kernel.
967 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
968 to -HEAD. Pools that have empty_bpobj in active state can not be
969 imported read-write with ZFS implementations that do not support
970 this feature. For more information read the zpool-features(5)
974 The sparc64 ZFS loader has been changed to no longer try to auto-
975 detect ZFS providers based on diskN aliases but now requires these
976 to be explicitly listed in the OFW boot-device environment variable.
979 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
980 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
981 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
984 The following sysctls and tunables have been renamed for consistency
985 with other variables:
986 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
987 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
990 The sort utility has been replaced with BSD sort. For now, GNU sort
991 is also available as "gnusort" or the default can be set back to
992 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
993 installed as "bsdsort".
996 A new version of ZFS (pool version 5000) has been merged to -HEAD.
997 Starting with this version the old system of ZFS pool versioning
998 is superseded by "feature flags". This concept enables forward
999 compatibility against certain future changes in functionality of ZFS
1000 pools. The first read-only compatible "feature flag" for ZFS pools
1001 is named "com.delphix:async_destroy". For more information
1002 read the new zpool-features(5) manual page.
1003 Please refer to the "ZFS notes" section of this file for information
1004 on upgrading boot ZFS pools.
1007 The malloc(3) implementation embedded in libc now uses sources imported
1008 as contrib/jemalloc. The most disruptive API change is to
1009 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1010 delete it prior to installworld, and optionally re-create it using the
1011 new format after rebooting. See malloc.conf(5) for details
1012 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1016 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1017 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1018 now spelled mips. This is to aid compatibility with third-party
1019 software that expects this naming scheme in uname(3). Little-endian
1020 settings are unchanged. If you are updating a big-endian mips64 machine
1021 from before this change, you may need to set MACHINE_ARCH=mips64 in
1022 your environment before the new build system will recognize your machine.
1025 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1029 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1030 nullfs(5) did not pass through all behaviours to the underlying layer,
1031 as a result if we bound to a socket on the lower layer we could connect
1032 only to the lower path; if we bound to the upper layer we could connect
1033 only to the upper path. The new behavior is one can connect to both the
1034 lower and the upper paths regardless what layer path one binds to.
1037 The getifaddrs upgrade path broken with 20111215 has been restored.
1038 If you have upgraded in between 20111215 and 20120209 you need to
1039 recompile libc again with your kernel. You still need to recompile
1040 world to be able to configure CARP but this restriction already
1041 comes from 20111215.
1044 The set_rcvar() function has been removed from /etc/rc.subr. All
1045 base and ports rc.d scripts have been updated, so if you have a
1046 port installed with a script in /usr/local/etc/rc.d you can either
1047 hand-edit the rcvar= line, or reinstall the port.
1049 An easy way to handle the mass-update of /etc/rc.d:
1050 rm /etc/rc.d/* && mergemaster -i
1053 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1054 on the current CPU and prevents other threads from running.
1055 This behavior can be reverted using the kern.stop_scheduler_on_panic
1057 The new behavior can be incompatible with kern.sync_on_panic.
1060 The carp(4) facility has been changed significantly. Configuration
1061 of the CARP protocol via ifconfig(8) has changed, as well as format
1062 of CARP events submitted to devd(8) has changed. See manual pages
1063 for more information. The arpbalance feature of carp(4) is currently
1064 not supported anymore.
1066 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1067 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1068 need to be recompiled.
1071 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1075 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1076 explicitely support non-MPSAFE filesystems.
1077 It is on by default for all supported platform at this present
1081 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1082 i386 and pc98 GENERIC kernel configuration files.
1085 sysinstall has been removed
1088 The stable/9 branch created in subversion. This corresponds to the
1089 RELENG_9 branch in CVS.
1095 Avoid using make -j when upgrading. While generally safe, there are
1096 sometimes problems using -j to upgrade. If your upgrade fails with
1097 -j, please try again without -j. From time to time in the past there
1098 have been problems using -j with buildworld and/or installworld. This
1099 is especially true when upgrading between "distant" versions (eg one
1100 that cross a major release boundary or several minor releases, or when
1101 several months have passed on the -current branch).
1103 Sometimes, obscure build problems are the result of environment
1104 poisoning. This can happen because the make utility reads its
1105 environment when searching for values for global variables. To run
1106 your build attempts in an "environmental clean room", prefix all make
1107 commands with 'env -i '. See the env(1) manual page for more details.
1109 When upgrading from one major version to another it is generally best
1110 to upgrade to the latest code in the currently installed branch first,
1111 then do an upgrade to the new branch. This is the best-tested upgrade
1112 path, and has the highest probability of being successful. Please try
1113 this approach before reporting problems with a major version upgrade.
1115 When upgrading a live system, having a root shell around before
1116 installing anything can help undo problems. Not having a root shell
1117 around can lead to problems if pam has changed too much from your
1118 starting point to allow continued authentication after the upgrade.
1122 When upgrading the boot ZFS pool to a new version, always follow
1125 1.) recompile and reinstall the ZFS boot loader and boot block
1126 (this is part of "make buildworld" and "make installworld")
1128 2.) update the ZFS boot block on your boot drive
1130 The following example updates the ZFS boot block on the first
1131 partition (freebsd-boot) of a GPT partitioned drive ada0:
1132 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1134 Non-boot pools do not need these updates.
1138 If you are updating from a prior version of FreeBSD (even one just
1139 a few days old), you should follow this procedure. It is the most
1140 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1142 make kernel-toolchain
1143 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1144 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1146 To test a kernel once
1147 ---------------------
1148 If you just want to boot a kernel once (because you are not sure
1149 if it works, or if you want to boot a known bad kernel to provide
1150 debugging information) run
1151 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1152 nextboot -k testkernel
1154 To just build a kernel when you know that it won't mess you up
1155 --------------------------------------------------------------
1156 This assumes you are already running a CURRENT system. Replace
1157 ${arch} with the architecture of your machine (e.g. "i386",
1158 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1160 cd src/sys/${arch}/conf
1161 config KERNEL_NAME_HERE
1162 cd ../compile/KERNEL_NAME_HERE
1167 If this fails, go to the "To build a kernel" section.
1169 To rebuild everything and install it on the current system.
1170 -----------------------------------------------------------
1171 # Note: sometimes if you are running current you gotta do more than
1172 # is listed here if you are upgrading from a really old current.
1174 <make sure you have good level 0 dumps>
1176 make kernel KERNCONF=YOUR_KERNEL_HERE
1178 <reboot in single user> [3]
1185 To cross-install current onto a separate partition
1186 --------------------------------------------------
1187 # In this approach we use a separate partition to hold
1188 # current's root, 'usr', and 'var' directories. A partition
1189 # holding "/", "/usr" and "/var" should be about 2GB in
1192 <make sure you have good level 0 dumps>
1195 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1196 <maybe newfs current's root partition>
1197 <mount current's root partition on directory ${CURRENT_ROOT}>
1198 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1199 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1200 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1201 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1202 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1203 <reboot into current>
1204 <do a "native" rebuild/install as described in the previous section>
1205 <maybe install compatibility libraries from ports/misc/compat*>
1209 To upgrade in-place from stable to current
1210 ----------------------------------------------
1211 <make sure you have good level 0 dumps>
1213 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1215 <reboot in single user> [3]
1222 Make sure that you've read the UPDATING file to understand the
1223 tweaks to various things you need. At this point in the life
1224 cycle of current, things change often and you are on your own
1225 to cope. The defaults can also change, so please read ALL of
1226 the UPDATING entries.
1228 Also, if you are tracking -current, you must be subscribed to
1229 freebsd-current@freebsd.org. Make sure that before you update
1230 your sources that you have read and understood all the recent
1231 messages there. If in doubt, please track -stable which has
1232 much fewer pitfalls.
1234 [1] If you have third party modules, such as vmware, you
1235 should disable them at this point so they don't crash your
1238 [3] From the bootblocks, boot -s, and then do
1243 adjkerntz -i # if CMOS is wall time
1244 Also, when doing a major release upgrade, it is required that
1245 you boot into single user mode to do the installworld.
1247 [4] Note: This step is non-optional. Failure to do this step
1248 can result in a significant reduction in the functionality of the
1249 system. Attempting to do it by hand is not recommended and those
1250 that pursue this avenue should read this file carefully, as well
1251 as the archives of freebsd-current and freebsd-hackers mailing lists
1252 for potential gotchas. The -U option is also useful to consider.
1253 See mergemaster(8) for more information.
1255 [5] Usually this step is a noop. However, from time to time
1256 you may need to do this if you get unknown user in the following
1257 step. It never hurts to do it all the time. You may need to
1258 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1259 install) after the buildworld before this step if you last updated
1260 from current before 20130425 or from -stable before 20130430.
1262 [6] This only deletes old files and directories. Old libraries
1263 can be deleted by "make delete-old-libs", but you have to make
1264 sure that no program is using those libraries anymore.
1266 [8] In order to have a kernel that can run the 4.x binaries needed to
1267 do an installworld, you must include the COMPAT_FREEBSD4 option in
1268 your kernel. Failure to do so may leave you with a system that is
1269 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1270 required to run the 5.x binaries on more recent kernels. And so on
1271 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1273 Make sure that you merge any new devices from GENERIC since the
1274 last time you updated your kernel config file.
1276 [9] When checking out sources, you must include the -P flag to have
1277 cvs prune empty directories.
1279 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1280 "?=" instead of the "=" assignment operator, so that buildworld can
1281 override the CPUTYPE if it needs to.
1283 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1284 not on the command line, or in /etc/make.conf. buildworld will
1285 warn if it is improperly defined.
1288 This file contains a list, in reverse chronological order, of major
1289 breakages in tracking -current. It is not guaranteed to be a complete
1290 list of such breakages, and only contains entries since October 10, 2007.
1291 If you need to see UPDATING entries from before that date, you will need
1292 to fetch an UPDATING file from an older FreeBSD release.
1294 Copyright information:
1296 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1298 Redistribution, publication, translation and use, with or without
1299 modification, in full or in part, in any form or format of this
1300 document are permitted without further permission from the author.
1302 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1303 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1304 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1305 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1306 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1307 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1308 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1309 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1310 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1311 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1312 POSSIBILITY OF SUCH DAMAGE.
1314 Contact Warner Losh if you have any questions about your use of