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 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.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
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.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 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 Since the switch to GPT disk labels, fsck for UFS/FFS has been
56 unable to automatically find alternate superblocks. As of r322297,
57 the information needed to find alternate superblocks has been
58 moved to the end of the area reserved for the boot block.
59 Filesystems created with a newfs of this vintage or later
60 will create the recovery information. If you have a filesystem
61 created prior to this change and wish to have a recovery block
62 created for your filesystem, you can do so by running fsck in
63 forground mode (i.e., do not use the -p or -y options). As it
64 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
65 to which you should answer yes.
68 As of r321665, an NFSv4 server configuration that services
69 Kerberos mounts or clients that do not support the uid/gid in
70 owner/owner_group string capability, must explicitly enable
71 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
72 machine's /etc/rc.conf file.
75 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
76 Please see the 20141231 entry below for information about prerequisites
77 and upgrading, if you are not already using clang 3.5.0 or higher.
80 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
81 r-commands (rlogin, rsh, etc.) to be built with the base system.
84 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
85 a very major ABI incompatible change, so users of FreeBSD/powerpc must
86 be careful when performing source upgrades. It is best to run
87 'make installworld' from an alternate root system, either a live
88 CD/memory stick, or a temporary root partition. Additionally, all ports
89 must be recompiled. powerpc64 is largely unaffected, except in the case
90 of 32-bit compatibility. All 32-bit binaries will be affected.
93 Forward compatibility for the "ino64" project have been committed. This
94 will allow most new binaries to run on older kernels in a limited
95 fashion. This prevents many of the common foot-shooting actions in the
96 upgrade as well as the limited ability to roll back the kernel across
97 the ino64 upgrade. Complicated use cases may not work properly, though
98 enough simpler ones work to allow recovery in most situations.
101 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
102 if you require the GPL compiler.
105 The internal ABI used for communication between the NFS kernel modules
106 was changed by r320085, so __FreeBSD_version was bumped to
107 ensure all the NFS related modules are updated together.
110 The ABI of struct event was changed by extending the data
111 member to 64bit and adding ext fields. For upgrade, same
112 precautions as for the entry 20170523 "ino64" must be
116 The GNU roff toolchain has been removed from base. To render manpages
117 which are not supported by mandoc(1), man(1) can fallback on GNU roff
118 from ports (and recommends to install it).
119 To render roff(7) documents, consider using GNU roff from ports or the
120 heirloom doctools roff toolchain from ports via pkg install groff or
121 via pkg install heirloom-doctools.
124 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
125 smaller runtime footprint builds. This is useful for embedded systems
126 which only require one chipset support.
128 If you load it as a module, make sure this is in /boot/loader.conf:
132 This will load the HAL, all chip/RF backends and if_ath_pci.
133 If you have if_ath_pci in /boot/loader.conf, ensure it is after
134 if_ath or it will not load any HAL chipset support.
136 If you want to selectively load things (eg on ye cheape ARM/MIPS
137 platforms where RAM is at a premium) you should:
140 * load the chip modules in question
141 * load ath_rate, ath_dfs
143 * load if_ath_pci and/or if_ath_ahb depending upon your particular
144 bus bind type - this is where probe/attach is done.
146 For further comments/feedback, poke adrian@ .
149 The "ino64" 64-bit inode project has been committed, which extends
150 a number of types to 64 bits. Upgrading in place requires care and
151 adherence to the documented upgrade procedure.
153 If using a custom kernel configuration ensure that the
154 COMPAT_FREEBSD11 option is included (as during the upgrade the
155 system will be running the ino64 kernel with the existing world).
157 For the safest in-place upgrade begin by removing previous build
158 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
159 full procedure documented below under the heading "To rebuild
160 everything and install it on the current system." Specifically,
161 a reboot is required after installing the new kernel before
165 The NATM framework including the en(4), fatm(4), hatm(4), and
166 patm(4) devices has been removed. Consumers should plan a
167 migration before the end-of-life date for FreeBSD 11.
170 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
171 diff has not been implemented, if those are needed a newer version of
172 GNU diff is available via the diffutils package under the gdiff name.
175 As of r316810 for ipfilter, keep frags is no longer assumed when
176 keep state is specified in a rule. r316810 aligns ipfilter with
177 documentation in man pages separating keep frags from keep state.
178 This allows keep state to be specified without forcing keep frags
179 and allows keep frags to be specified independently of keep state.
180 To maintain previous behaviour, also specify keep frags with
181 keep state (as documented in ipf.conf.5).
184 arm64 builds now use the base system LLD 4.0.0 linker by default,
185 instead of requiring that the aarch64-binutils port or package be
186 installed. To continue using aarch64-binutils, set
187 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
190 The UDP optimization in entry 20160818 that added the sysctl
191 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
192 packets will no longer be treated as L3 broadcast packets.
195 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
196 use any explicitly assigned loopback address available in the jail
197 instead of using the first assigned address of the jail.
200 The ctl.ko module no longer implements the iSCSI target frontend:
201 cfiscsi.ko does instead.
203 If building cfiscsi.ko as a kernel module, the module can be loaded
204 via one of the following methods:
205 - `cfiscsi_load="YES"` in loader.conf(5).
206 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
207 - ctladm(8)/ctld(8), when compiled with iSCSI support
208 (`WITH_ISCSI=yes` in src.conf(5))
210 Please see cfiscsi(4) for more details.
213 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
214 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
215 same source (previously, the dependency of mmcsd.ko on mmc.ko was
216 missing, but mmcsd.ko now will refuse to load if it is incompatible
220 The syntax of ipfw(8) named states was changed to avoid ambiguity.
221 If you have used named states in the firewall rules, you need to modify
222 them after installworld and before rebooting. Now named states must
223 be prefixed with colon.
226 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
227 removed as the userland we provide cannot use them. The KMS version
228 (sys/dev/drm2) supports the same hardware.
231 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
232 Please see the 20141231 entry below for information about prerequisites
233 and upgrading, if you are not already using clang 3.5.0 or higher.
236 The code that provides support for ZFS .zfs/ directory functionality
237 has been reimplemented. It's not possible now to create a snapshot
238 by mkdir under .zfs/snapshot/. That should be the only user visible
242 EISA bus support has been removed. The WITH_EISA option is no longer
246 MCA bus support has been removed.
249 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
250 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
253 The EM_MULTIQUEUE kernel configuration option is deprecated now that
254 the em(4) driver conforms to iflib specifications.
257 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
258 IFLIB. If you have a custom kernel configuration that excludes em(4)
259 but you use igb(4), you need to re-add em(4) to your custom configuration.
262 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
263 Please see the 20141231 entry below for information about prerequisites
264 and upgrading, if you are not already using clang 3.5.0 or higher.
267 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
268 Please see the 20141231 entry below for information about prerequisites
269 and upgrading, if you are not already using clang 3.5.0 or higher.
272 The layout of the pmap structure has changed for powerpc to put the pmap
273 statistics at the front for all CPU variations. libkvm(3) and all tools
274 that link against it need to be recompiled.
277 isl(4) and cyapa(4) drivers now require a new driver,
278 chromebook_platform(4), to work properly on Chromebook-class hardware.
279 On other types of hardware the drivers may need to be configured using
280 device hints. Please see the corresponding manual pages for details.
283 The urtwn(4) driver was merged into rtwn(4) and now consists of
284 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
286 Also, firmware for RTL8188CE was renamed due to possible name
287 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
290 GNU rcs has been removed from base. It is available as packages:
291 - rcs: Latest GPLv3 GNU rcs version.
292 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
296 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
297 modules now requires that the kernel configuration contain the
298 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
301 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
302 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
305 Relocatable object files with the extension of .So have been renamed
306 to use an extension of .pico instead. The purpose of this change is
307 to avoid a name clash with shared libraries on case-insensitive file
308 systems. On those file systems, foo.So is the same file as foo.so.
311 GNU rcs has been turned off by default. It can (temporarily) be built
312 again by adding WITH_RCS knob in src.conf.
313 Otherwise, GNU rcs is available from packages:
314 - rcs: Latest GPLv3 GNU rcs version.
315 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
318 The backup_uses_rcs functionality has been removed from rc.subr.
321 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
322 two separate components, QUEUE_MACRO_DEBUG_TRACE and
323 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
324 QUEUE_MACRO_DEBUG behavior.
327 r304787 changed some ioctl interfaces between the iSCSI userspace
328 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
329 rebuilt to work with new kernels. __FreeBSD_version has been bumped
333 The UDP receive code has been updated to only treat incoming UDP
334 packets that were addressed to an L2 broadcast address as L3
335 broadcast packets. It is not expected that this will affect any
336 standards-conforming UDP application. The new behaviour can be
337 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
341 Remove the openbsd_poll system call.
342 __FreeBSD_version has been bumped because of this.
345 The libc stub for the pipe(2) system call has been replaced with
346 a wrapper that calls the pipe2(2) system call and the pipe(2)
347 system call is now only implemented by the kernels that include
348 "options COMPAT_FREEBSD10" in their config file (this is the
349 default). Users should ensure that this option is enabled in
350 their kernel or upgrade userspace to r302092 before upgrading their
354 CAM will now strip leading spaces from SCSI disks' serial numbers.
355 This will affect users who create UFS filesystems on SCSI disks using
356 those disk's diskid device nodes. For example, if /etc/fstab
357 previously contained a line like
358 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
359 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
360 transforms like gmirror may also be affected. ZFS users should
364 The bitstring(3) API has been updated with new functionality and
365 improved performance. But it is binary-incompatible with the old API.
366 Objects built with the new headers may not be linked against objects
367 built with the old headers.
370 The brk and sbrk functions have been removed from libc on arm64.
371 Binutils from ports has been updated to not link to these
372 functions and should be updated to the latest version before
373 installing a new libc.
376 The armv6 port now defaults to hard float ABI. Limited support
377 for running both hardfloat and soft float on the same system
378 is available using the libraries installed with -DWITH_LIBSOFT.
379 This has only been tested as an upgrade path for installworld
380 and packages may fail or need manual intervention to run. New
381 packages will be needed.
383 To update an existing self-hosted armv6hf system, you must add
384 TARGET_ARCH=armv6 on the make command line for both the build
385 and the install steps.
388 Kernel modules compiled outside of a kernel build now default to
389 installing to /boot/modules instead of /boot/kernel. Many kernel
390 modules built this way (such as those in ports) already overrode
391 KMODDIR explicitly to install into /boot/modules. However,
392 manually building and installing a module from /sys/modules will
393 now install to /boot/modules instead of /boot/kernel.
396 The CAM I/O scheduler has been committed to the kernel. There should be
397 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
398 list of known rogues that claim support for this but actually corrupt
399 data is believed to be complete, be on the lookout for data
400 corruption. The known rogue list is believed to be complete:
402 o Crucial MX100, M550 drives with MU01 firmware.
403 o Micron M510 and M550 drives with MU01 firmware.
404 o Micron M500 prior to MU07 firmware
405 o Samsung 830, 840, and 850 all firmwares
406 o FCCT M500 all firmwares
408 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
409 with working NCQ TRIM. For Micron branded drives, see your sales rep for
410 updated firmware. Black listed drives will work correctly because these
411 drives work correctly so long as no NCQ TRIMs are sent to them. Given
412 this list is the same as found in Linux, it's believed there are no
413 other rogues in the market place. All other models from the above
416 To be safe, if you are at all concerned, you can quirk each of your
417 drives to prevent NCQ from being sent by setting:
418 kern.cam.ada.X.quirks="0x2"
419 in loader.conf. If the drive requires the 4k sector quirk, set the
423 The FAST_DEPEND build option has been removed and its functionality is
424 now the one true way. The old mkdep(1) style of 'make depend' has
425 been removed. See 20160311 for further details.
428 Resource range types have grown from unsigned long to uintmax_t. All
429 drivers, and anything using libdevinfo, need to be recompiled.
432 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
433 builds. It no longer runs mkdep(1) during 'make depend', and the
434 'make depend' stage can safely be skipped now as it is auto ran
435 when building 'make all' and will generate all SRCS and DPSRCS before
436 building anything else. Dependencies are gathered at compile time with
437 -MF flags kept in separate .depend files per object file. Users should
438 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
442 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
443 kernel modules. Therefore, if you load any kernel modules at boot time,
444 please install the boot loaders after you install the kernel, but before
448 make kernel KERNCONF=YOUR_KERNEL_HERE
449 make -C sys/boot install
450 <reboot in single user>
452 Then follow the usual steps, described in the General Notes section,
456 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
457 see the 20141231 entry below for information about prerequisites and
458 upgrading, if you are not already using clang 3.5.0 or higher.
461 The AIO subsystem is now a standard part of the kernel. The
462 VFS_AIO kernel option and aio.ko kernel module have been removed.
463 Due to stability concerns, asynchronous I/O requests are only
464 permitted on sockets and raw disks by default. To enable
465 asynchronous I/O requests on all file types, set the
466 vfs.aio.enable_unsafe sysctl to a non-zero value.
469 The ELF object manipulation tool objcopy is now provided by the
470 ELF Tool Chain project rather than by GNU binutils. It should be a
471 drop-in replacement, with the addition of arm64 support. The
472 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
473 to obtain the GNU version if necessary.
476 Building ZFS pools on top of zvols is prohibited by default. That
477 feature has never worked safely; it's always been prone to deadlocks.
478 Using a zvol as the backing store for a VM guest's virtual disk will
479 still work, even if the guest is using ZFS. Legacy behavior can be
480 restored by setting vfs.zfs.vol.recursive=1.
483 The NONE and HPN patches has been removed from OpenSSH. They are
484 still available in the security/openssh-portable port.
487 With the addition of ypldap(8), a new _ypldap user is now required
488 during installworld. "mergemaster -p" can be used to add the user
489 prior to installworld, as documented in the handbook.
492 The tftp loader (pxeboot) now uses the option root-path directive. As a
493 consequence it no longer looks for a pxeboot.4th file on the tftp
494 server. Instead it uses the regular /boot infrastructure as with the
498 The code to start recording plug and play data into the modules has
499 been committed. While the old tools will properly build a new kernel,
500 a number of warnings about "unknown metadata record 4" will be produced
501 for an older kldxref. To avoid such warnings, make sure to rebuild
502 the kernel toolchain (or world). Make sure that you have r292078 or
503 later when trying to build 292077 or later before rebuilding.
506 Debug data files are now built by default with 'make buildworld' and
507 installed with 'make installworld'. This facilitates debugging but
508 requires more disk space both during the build and for the installed
509 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
513 r291527 changed the internal interface between the nfsd.ko and
514 nfscommon.ko modules. As such, they must both be upgraded to-gether.
515 __FreeBSD_version has been bumped because of this.
518 Add support for unicode collation strings leads to a change of
519 order of files listed by ls(1) for example. To get back to the old
520 behaviour, set LC_COLLATE environment variable to "C".
522 Databases administrators will need to reindex their databases given
523 collation results will be different.
525 Due to a bug in install(1) it is recommended to remove the ancient
526 locales before running make installworld.
528 rm -rf /usr/share/locale/*
531 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
532 libcrypto.so.7 or libssl.so.7 must be recompiled.
535 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
536 Kernel modules isp_2400_multi and isp_2500_multi were removed and
537 should be replaced with isp_2400 and isp_2500 modules respectively.
540 The build previously allowed using 'make -n' to not recurse into
541 sub-directories while showing what commands would be executed, and
542 'make -n -n' to recursively show commands. Now 'make -n' will recurse
543 and 'make -N' will not.
546 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
547 and etcupdate will now use this file. A custom sendmail.cf is now
548 updated via this mechanism rather than via installworld. If you had
549 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
550 want to remove the exclusion or change it to "always install".
551 /etc/mail/sendmail.cf is now managed the same way regardless of
552 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
553 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
556 Compatibility shims for legacy ATA device names have been removed.
557 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
558 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
559 environment variables, /dev/ad* and /dev/ar* symbolic links.
562 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
563 Please see the 20141231 entry below for information about prerequisites
564 and upgrading, if you are not already using clang 3.5.0 or higher.
567 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
568 and renamed from .symbols to .debug. This reduces the size requirements
569 on the boot partition or file system and provides consistency with
570 userland debug files.
572 When using the supported kernel installation method the
573 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
574 as is done with /boot/kernel.
576 Developers wishing to maintain the historical behavior of installing
577 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
580 The wireless drivers had undergone changes that remove the 'parent
581 interface' from the ifconfig -l output. The rc.d network scripts
582 used to check presence of a parent interface in the list, so old
583 scripts would fail to start wireless networking. Thus, etcupdate(3)
584 or mergemaster(8) run is required after kernel update, to update your
585 rc.d scripts in /etc.
588 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
589 These configurations are now automatically interpreted as
590 'scrub fragment reassemble'.
593 Kernel-loadable modules for the random(4) device are back. To use
594 them, the kernel must have
597 options RANDOM_LOADABLE
599 kldload(8) can then be used to load random_fortuna.ko
600 or random_yarrow.ko. Please note that due to the indirect
601 function calls that the loadable modules need to provide,
602 the build-in variants will be slightly more efficient.
604 The random(4) kernel option RANDOM_DUMMY has been retired due to
605 unpopularity. It was not all that useful anyway.
608 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
609 Control over building the ELF Tool Chain tools is now provided by
610 the WITHOUT_TOOLCHAIN knob.
613 The polarity of Pulse Per Second (PPS) capture events with the
614 uart(4) driver has been corrected. Prior to this change the PPS
615 "assert" event corresponded to the trailing edge of a positive PPS
616 pulse and the "clear" event was the leading edge of the next pulse.
618 As the width of a PPS pulse in a typical GPS receiver is on the
619 order of 1 millisecond, most users will not notice any significant
620 difference with this change.
622 Anyone who has compensated for the historical polarity reversal by
623 configuring a negative offset equal to the pulse width will need to
624 remove that workaround.
627 The default group assigned to /dev/dri entries has been changed
628 from 'wheel' to 'video' with the id of '44'. If you want to have
629 access to the dri devices please add yourself to the video group
632 # pw groupmod video -m $USER
635 The menu.rc and loader.rc files will now be replaced during
636 upgrades. Please migrate local changes to menu.rc.local and
637 loader.rc.local instead.
640 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
641 strings and strip have been removed. The src.conf(5) knob
642 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
645 As ZFS requires more kernel stack pages than is the default on some
646 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
647 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
649 Please consider using 'options KSTACK_PAGES=X' where X is greater
650 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
653 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
654 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
655 default, i.e., they will not contain "::". For example, instead
656 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
657 to have a more specific match, such as different map entries for
658 IPv6:0:0 vs IPv6:0. This change requires that configuration
659 data (including maps, files, classes, custom ruleset, etc.) must
660 use the same format, so make certain such configuration data is
661 upgrading. As a very simple check search for patterns like
662 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
663 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
664 the cf option UseCompressedIPv6Addresses.
667 The default kernel entropy-processing algorithm is now
668 Fortuna, replacing Yarrow.
670 Assuming you have 'device random' in your kernel config
671 file, the configurations allow a kernel option to override
672 this default. You may choose *ONE* of:
674 options RANDOM_YARROW # Legacy /dev/random algorithm.
675 options RANDOM_DUMMY # Blocking-only driver.
677 If you have neither, you get Fortuna. For most people,
678 read no further, Fortuna will give a /dev/random that works
679 like it always used to, and the difference will be irrelevant.
681 If you remove 'device random', you get *NO* kernel-processed
682 entropy at all. This may be acceptable to folks building
683 embedded systems, but has complications. Carry on reading,
684 and it is assumed you know what you need.
686 *PLEASE* read random(4) and random(9) if you are in the
687 habit of tweaking kernel configs, and/or if you are a member
688 of the embedded community, wanting specific and not-usual
689 behaviour from your security subsystems.
691 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
692 random', you will NOT have a functioning /dev/random, and
693 many cryptographic features will not work, including SSH.
694 You may also find strange behaviour from the random(3) set
695 of library functions, in particular sranddev(3), srandomdev(3)
696 and arc4random(3). The reason for this is that the KERN_ARND
697 sysctl only returns entropy if it thinks it has some to
698 share, and with RANDOM_DUMMY or no 'device random' this
702 An additional fix for the issue described in the 20150614 sendmail
703 entry below has been been committed in revision 284717.
706 FreeBSD's old make (fmake) has been removed from the system. It is
707 available as the devel/fmake port or via pkg install fmake.
710 The fix for the issue described in the 20150614 sendmail entry
711 below has been been committed in revision 284436. The work
712 around described in that entry is no longer needed unless the
713 default setting is overridden by a confDH_PARAMETERS configuration
714 setting of '5' or pointing to a 512 bit DH parameter file.
717 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
718 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
719 and devel/kyua to version 0.20+ and adjust any calling code to work
720 with Kyuafile and kyua.
723 The import of openssl to address the FreeBSD-SA-15:10.openssl
724 security advisory includes a change which rejects handshakes
725 with DH parameters below 768 bits. sendmail releases prior
726 to 8.15.2 (not yet released), defaulted to a 512 bit
727 DH parameter setting for client connections. To work around
728 this interoperability, sendmail can be configured to use a
729 2048 bit DH parameter by:
731 1. Edit /etc/mail/`hostname`.mc
732 2. If a setting for confDH_PARAMETERS does not exist or
733 exists and is set to a string beginning with '5',
735 3. If a setting for confDH_PARAMETERS exists and is set to
736 a file path, create a new file with:
737 openssl dhparam -out /path/to/file 2048
738 4. Rebuild the .cf file:
739 cd /etc/mail/; make; make install
741 cd /etc/mail/; make restart
743 A sendmail patch is coming, at which time this file will be
747 Generation of legacy formatted entries have been disabled by default
748 in pwd_mkdb(8), as all base system consumers of the legacy formatted
749 entries were converted to use the new format by default when the new,
750 machine independent format have been added and supported since FreeBSD
753 Please see the pwd_mkdb(8) manual page for further details.
756 Clang and llvm have been upgraded to 3.6.1 release. Please see the
757 20141231 entry below for information about prerequisites and upgrading,
758 if you are not already using 3.5.0 or higher.
761 TI platform code switched to using vendor DTS files and this update
762 may break existing systems running on Beaglebone, Beaglebone Black,
765 - dtb files should be regenerated/reinstalled. Filenames are the
766 same but content is different now
767 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
768 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
769 addressing scheme is now pin 25 on /dev/gpioc3.
770 - Pandaboard: /etc/ttys should be updated, serial console device is
771 now /dev/ttyu2, not /dev/ttyu0
774 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
775 If you need the GNU extension from groff soelim(1), install groff
776 from package: pkg install groff, or via ports: textproc/groff.
779 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
780 defined in symlink(7); previously symlinks were silently ignored.
783 The const qualifier has been removed from iconv(3) to comply with
784 POSIX. The ports tree is aware of this from r384038 onwards.
787 Libraries specified by LIBADD in Makefiles must have a corresponding
788 DPADD_<lib> variable to ensure correct dependencies. This is now
789 enforced in src.libnames.mk.
792 From legacy ata(4) driver was removed support for SATA controllers
793 supported by more functional drivers ahci(4), siis(4) and mvs(4).
794 Kernel modules ataahci and ataadaptec were removed completely,
795 replaced by ahci and mvs modules respectively.
798 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
799 the 20141231 entry below for information about prerequisites and
800 upgrading, if you are not already using 3.5.0 or higher.
803 The 32-bit PowerPC kernel has been changed to a position-independent
804 executable. This can only be booted with a version of loader(8)
805 newer than January 31, 2015, so make sure to update both world and
806 kernel before rebooting.
809 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
810 but before r278950, the RNG was not seeded properly. Immediately
811 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
812 ssh keys or openssl keys) that were generated w/ a kernel from that
813 range. This does not affect programs that directly used /dev/random
814 or /dev/urandom. All userland uses of arc4random(3) are affected.
817 The autofs(4) ABI was changed in order to restore binary compatibility
818 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
822 The powerpc64 kernel has been changed to a position-independent
823 executable. This can only be booted with a new version of loader(8),
824 so make sure to update both world and kernel before rebooting.
827 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
828 only release, no new features have been added. Please see the 20141231
829 entry below for information about prerequisites and upgrading, if you
830 are not already using 3.5.0.
833 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
834 taken from the ELF Tool Chain project rather than GNU binutils. They
835 should be drop-in replacements, with the addition of arm64 support.
836 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
837 binutils tools, if necessary. See 20150805 for updated information.
840 The default Unbound configuration now enables remote control
841 using a local socket. Users who have already enabled the
842 local_unbound service should regenerate their configuration
843 by running "service local_unbound setup" as root.
846 The GNU texinfo and GNU info pages have been removed.
847 To be able to view GNU info pages please install texinfo from ports.
850 Clang, llvm and lldb have been upgraded to 3.5.0 release.
852 As of this release, a prerequisite for building clang, llvm and lldb is
853 a C++11 capable compiler and C++11 standard library. This means that to
854 be able to successfully build the cross-tools stage of buildworld, with
855 clang as the bootstrap compiler, your system compiler or cross compiler
856 should either be clang 3.3 or later, or gcc 4.8 or later, and your
857 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
860 On any standard FreeBSD 10.x or 11.x installation, where clang and
861 libc++ are on by default (that is, on x86 or arm), this should work out
864 On 9.x installations where clang is enabled by default, e.g. on x86 and
865 powerpc, libc++ will not be enabled by default, so libc++ should be
866 built (with clang) and installed first. If both clang and libc++ are
867 missing, build clang first, then use it to build libc++.
869 On 8.x and earlier installations, upgrade to 9.x first, and then follow
870 the instructions for 9.x above.
872 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
873 default, and do not build clang.
875 Many embedded systems are resource constrained, and will not be able to
876 build clang in a reasonable time, or in some cases at all. In those
877 cases, cross building bootable systems on amd64 is a workaround.
879 This new version of clang introduces a number of new warnings, of which
880 the following are most likely to appear:
884 This warns in two cases, for both C and C++:
885 * When the code is trying to take the absolute value of an unsigned
886 quantity, which is effectively a no-op, and almost never what was
887 intended. The code should be fixed, if at all possible. If you are
888 sure that the unsigned quantity can be safely cast to signed, without
889 loss of information or undefined behavior, you can add an explicit
890 cast, or disable the warning.
892 * When the code is trying to take an absolute value, but the called
893 abs() variant is for the wrong type, which can lead to truncation.
894 If you want to disable the warning instead of fixing the code, please
895 make sure that truncation will not occur, or it might lead to unwanted
898 -Wtautological-undefined-compare and
899 -Wundefined-bool-conversion
901 These warn when C++ code is trying to compare 'this' against NULL, while
902 'this' should never be NULL in well-defined C++ code. However, there is
903 some legacy (pre C++11) code out there, which actively abuses this
904 feature, which was less strictly defined in previous C++ versions.
906 Squid and openjdk do this, for example. The warning can be turned off
907 for C++98 and earlier, but compiling the code in C++11 mode might result
908 in unexpected behavior; for example, the parts of the program that are
909 unreachable could be optimized away.
912 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
913 kernel sources have been removed. The .h files remain, since some
914 utilities include them. This will need to be fixed later.
915 If "mount -t oldnfs ..." is attempted, it will fail.
916 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
917 the utilities will report errors.
920 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
921 directories to top level SUBDIR variable when their parent
922 directory is included in LOCAL_DIRS. Users with build systems with
923 such hierarchies and without SUBDIR entries in the parent
924 directory Makefiles should add them or add the directories to
928 faith(4) and faithd(8) have been removed from the base system. Faith
929 has been obsolete for a very long time.
932 vt(4), the new console driver, is enabled by default. It brings
933 support for Unicode and double-width characters, as well as
934 support for UEFI and integration with the KMS kernel video
937 You may need to update your console settings in /etc/rc.conf,
938 most probably the keymap. During boot, /etc/rc.d/syscons will
939 indicate what you need to do.
941 vt(4) still has issues and lacks some features compared to
942 syscons(4). See the wiki for up-to-date information:
943 https://wiki.freebsd.org/Newcons
945 If you want to keep using syscons(4), you can do so by adding
946 the following line to /boot/loader.conf:
950 pjdfstest has been integrated into kyua as an opt-in test suite.
951 Please see share/doc/pjdfstest/README for more details on how to
955 gperf has been removed from the base system for architectures
956 that use clang. Ports that require gperf will obtain it from the
960 pjdfstest has been moved from tools/regression/pjdfstest to
964 At svn r271982, The default linux compat kernel ABI has been adjusted
965 to 2.6.18 in support of the linux-c6 compat ports infrastructure
966 update. If you wish to continue using the linux-f10 compat ports,
967 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
968 encouraged to update their linux-compat packages to linux-c6 during
969 their next update cycle.
972 The ofwfb driver, used to provide a graphics console on PowerPC when
973 using vt(4), no longer allows mmap() of all physical memory. This
974 will prevent Xorg on PowerPC with some ATI graphics cards from
975 initializing properly unless x11-servers/xorg-server is updated to
979 The xdev targets have been converted to using TARGET and
980 TARGET_ARCH instead of XDEV and XDEV_ARCH.
983 The default unbound configuration has been modified to address
984 issues with reverse lookups on networks that use private
985 address ranges. If you use the local_unbound service, run
986 "service local_unbound setup" as root to regenerate your
987 configuration, then "service local_unbound reload" to load the
991 The GNU texinfo and GNU info pages are not built and installed
992 anymore, WITH_INFO knob has been added to allow to built and install
994 UPDATE: see 20150102 entry on texinfo's removal
997 The GNU readline library is now an INTERNALLIB - that is, it is
998 statically linked into consumers (GDB and variants) in the base
999 system, and the shared library is no longer installed. The
1000 devel/readline port is available for third party software that
1004 The Itanium architecture (ia64) has been removed from the list of
1005 known architectures. This is the first step in the removal of the
1009 Commit r268115 has added NFSv4.1 server support, merged from
1010 projects/nfsv4.1-server. Since this includes changes to the
1011 internal interfaces between the NFS related modules, a full
1012 build of the kernel and modules will be necessary.
1013 __FreeBSD_version has been bumped.
1016 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1017 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1018 which differs from the behaviour controlled by this knob.)
1021 Maximal length of the serial number in CTL was increased from 16 to
1022 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1023 and ctld, need to be rebuilt to work with a new kernel.
1026 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1027 1 respectively to match the upstream numbers. They were out of
1028 sync because, when they were originally added to FreeBSD, the
1029 upstream versions were not respected. These libraries are private
1030 and not yet built by default, so renumbering them should be a
1031 non-issue. However, unclean source trees will yield broken test
1032 programs once the operator executes "make delete-old-libs" after a
1033 "make installworld".
1035 Additionally, the atf-sh binary was made private by moving it into
1036 /usr/libexec/. Already-built shell test programs will keep the
1037 path to the old binary so they will break after "make delete-old"
1040 If you are using WITH_TESTS=yes (not the default), wipe the object
1041 tree and rebuild from scratch to prevent spurious test failures.
1042 This is only needed once: the misnumbered libraries and misplaced
1043 binaries have been added to OptionalObsoleteFiles.inc so they will
1044 be removed during a clean upgrade.
1047 Clang and llvm have been upgraded to 3.4.1 release.
1050 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1051 be removed to avoid issues in the future (and has been added to
1055 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1056 past, it affected all builds that used the bsd.*.mk files. The old
1057 behavior was a bug, but people may have relied upon it. To get this
1058 behavior back, you can .include /etc/src.conf from /etc/make.conf
1059 (which is still global and isn't changed). This also changes the
1060 behavior of incremental builds inside the tree of individual
1061 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1062 Although this has survived make universe and some upgrade scenarios,
1063 other upgrade scenarios may have broken. At least one form of
1064 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1065 as well... In cases where MAKESYSPATH isn't working with this
1066 setting, you'll need to set it to the full path to your tree.
1068 One side effect of all this cleaning up is that bsd.compiler.mk
1069 is no longer implicitly included by bsd.own.mk. If you wish to
1070 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1074 The lindev device has been removed since /dev/full has been made a
1075 standard device. __FreeBSD_version has been bumped.
1078 The knob WITHOUT_VI was added to the base system, which controls
1079 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1080 in order to reorder files share/termcap and didn't build ex(1) as a
1081 build tool, so building/installing with WITH_VI is highly advised for
1082 build hosts for older releases.
1084 This issue has been fixed in stable/9 and stable/10 in r277022 and
1085 r276991, respectively.
1088 The YES_HESIOD knob has been removed. It has been obsolete for
1089 a decade. Please move to using WITH_HESIOD instead or your builds
1090 will silently lack HESIOD.
1093 The uart(4) driver has been changed with respect to its handling
1094 of the low-level console. Previously the uart(4) driver prevented
1095 any process from changing the baudrate or the CLOCAL and HUPCL
1096 control flags. By removing the restrictions, operators can make
1097 changes to the serial console port without having to reboot.
1098 However, when getty(8) is started on the serial device that is
1099 associated with the low-level console, a misconfigured terminal
1100 line in /etc/ttys will now have a real impact.
1101 Before upgrading the kernel, make sure that /etc/ttys has the
1102 serial console device configured as 3wire without baudrate to
1103 preserve the previous behaviour. E.g:
1104 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1107 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1108 to improve performance. To re-enable it, if needed, run rpcbind
1109 with command line option -W.
1112 Switched back to the GPL dtc compiler due to updates in the upstream
1113 dts files not being supported by the BSDL dtc compiler. You will need
1114 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1115 may result while building dtb files during a kernel build if you fail
1116 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1119 Clang and llvm have been upgraded to 3.4 release.
1122 The nve(4) driver has been removed. Please use the nfe(4) driver
1123 for NVIDIA nForce MCP Ethernet adapters instead.
1126 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1127 This could cause certain C++ applications using shared libraries built
1128 against the previous version of libc++ to crash. The incompatibility
1129 has now been fixed, but any C++ applications or shared libraries built
1130 between r261283 and r261801 should be recompiled.
1133 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1134 capability mode support. Please note that enabling the feature in
1135 kernel is still highly recommended.
1138 OpenSSH is now built with sandbox support, and will use sandbox as
1139 the default privilege separation method. This requires Capsicum
1140 capability mode support in kernel.
1143 The libelf and libdwarf libraries have been updated to newer
1144 versions from upstream. Shared library version numbers for
1145 these two libraries were bumped. Any ports or binaries
1146 requiring these two libraries should be recompiled.
1147 __FreeBSD_version is bumped to 1100006.
1150 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1151 instead of providing an explicit one, this would prevent such
1152 Makefile from providing its own Kyuafile in the future during
1153 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1154 intervention is needed to clean an objdir if you use NO_CLEAN:
1155 # find /usr/obj -name Kyuafile | xargs rm -f
1158 The behavior of gss_pseudo_random() for the krb5 mechanism
1159 has changed, for applications requesting a longer random string
1160 than produced by the underlying enctype's pseudo-random() function.
1161 In particular, the random string produced from a session key of
1162 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1163 be different at the 17th octet and later, after this change.
1164 The counter used in the PRF+ construction is now encoded as a
1165 big-endian integer in accordance with RFC 4402.
1166 __FreeBSD_version is bumped to 1100004.
1169 The WITHOUT_ATF build knob has been removed and its functionality
1170 has been subsumed into the more generic WITHOUT_TESTS. If you were
1171 using the former to disable the build of the ATF libraries, you
1172 should change your settings to use the latter.
1175 The default version of mtree is nmtree which is obtained from
1176 NetBSD. The output is generally the same, but may vary
1177 slightly. If you found you need identical output adding
1178 "-F freebsd9" to the command line should do the trick. For the
1179 time being, the old mtree is available as fmtree.
1182 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1183 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1184 1.1.4_8 and verify bsdyml not linked in, before running "make
1186 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1188 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1191 The stable/10 branch has been created in subversion from head
1195 The rc.d/jail script has been updated to support jail(8)
1196 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1197 for per-jail configuration are automatically converted to
1198 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1199 This is transparently backward compatible. See below about some
1200 incompatibilities and rc.conf(5) manual page for more details.
1202 These variables are now deprecated in favor of jail(8) configuration
1203 file. One can use "rc.d/jail config <jname>" command to generate
1204 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1205 running the jail(8) utility. The default pathname of the
1206 configuration file is /etc/jail.conf and can be specified by
1207 using $jail_conf or $jail_<jname>_conf variables.
1209 Please note that jail_devfs_ruleset accepts an integer at
1210 this moment. Please consider to rewrite the ruleset name
1214 BIND has been removed from the base system. If all you need
1215 is a local resolver, simply enable and start the local_unbound
1216 service instead. Otherwise, several versions of BIND are
1217 available in the ports tree. The dns/bind99 port is one example.
1219 With this change, nslookup(1) and dig(1) are no longer in the base
1220 system. Users should instead use host(1) and drill(1) which are
1221 in the base system. Alternatively, nslookup and dig can
1222 be obtained by installing the dns/bind-tools port.
1225 With the addition of unbound(8), a new unbound user is now
1226 required during installworld. "mergemaster -p" can be used to
1227 add the user prior to installworld, as documented in the handbook.
1230 OpenSSH is now built with DNSSEC support, and will by default
1231 silently trust signed SSHFP records. This can be controlled with
1232 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1233 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1236 The GNU Compiler Collection and C++ standard library (libstdc++)
1237 are no longer built by default on platforms where clang is the system
1238 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1239 options in src.conf.
1242 The PROCDESC kernel option is now part of the GENERIC kernel
1243 configuration and is required for the rwhod(8) to work.
1244 If you are using custom kernel configuration, you should include
1248 The API and ABI related to the Capsicum framework was modified
1249 in backward incompatible way. The userland libraries and programs
1250 have to be recompiled to work with the new kernel. This includes the
1251 following libraries and programs, but the whole buildworld is
1252 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1253 kdump, procstat, rwho, rwhod, uniq.
1256 AES-NI intrinsic support has been added to gcc. The AES-NI module
1257 has been updated to use this support. A new gcc is required to build
1258 the aesni module on both i386 and amd64.
1261 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1262 Thus "device padlock_rng" and "device rdrand_rng" should be
1263 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1266 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1267 enables just the iconv* functionality and is now on by default.
1268 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1269 compatibility. Set WITHOUT_ICONV to build the old way.
1270 If you have been using WITH_ICONV before, you will very likely
1271 need to turn on WITH_LIBICONV_COMPAT.
1274 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1275 Illumos origin, including ZFS. If you have INVARIANTS in your
1276 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1278 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1279 locks if WITNESS option was set. Because that generated a lot of
1280 witness(9) reports and all of them were believed to be false
1281 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1282 can be used to achieve the previous behavior.
1285 Timer values in IPv6 data structures now use time_uptime instead
1286 of time_second. Although this is not a user-visible functional
1287 change, userland utilities which directly use them---ndp(8),
1288 rtadvd(8), and rtsold(8) in the base system---need to be updated
1289 to r253970 or later.
1292 find -delete can now delete the pathnames given as arguments,
1293 instead of only files found below them or if the pathname did
1294 not contain any slashes. Formerly, the following error message
1297 find: -delete: <path>: relative path potentially not safe
1299 Deleting the pathnames given as arguments can be prevented
1300 without error messages using -mindepth 1 or by changing
1301 directory and passing "." as argument to find. This works in the
1302 old as well as the new version of find.
1305 Behavior of devfs rules path matching has been changed.
1306 Pattern is now always matched against fully qualified devfs
1307 path and slash characters must be explicitly matched by
1308 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1309 subdirectories must be reviewed.
1312 The default ARM ABI has changed to the ARM EABI. The old ABI is
1313 incompatible with the ARM EABI and all programs and modules will
1314 need to be rebuilt to work with a new kernel.
1316 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1318 NOTE: Support for the old ABI will be removed in the future and
1319 users are advised to upgrade.
1322 pkg_install has been disconnected from the build if you really need it
1323 you should add WITH_PKGTOOLS in your src.conf(5).
1326 Most of network statistics structures were changed to be able
1327 keep 64-bits counters. Thus all tools, that work with networking
1328 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1331 Fix a bug that allowed a tracing process (e.g. gdb) to write
1332 to a memory-mapped file in the traced process's address space
1333 even if neither the traced process nor the tracing process had
1334 write access to that file.
1337 CVS has been removed from the base system. An exact copy
1338 of the code is available from the devel/cvs port.
1341 Some people report the following error after the switch to bmake:
1343 make: illegal option -- J
1344 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1346 *** [buildworld] Error code 2
1348 this likely due to an old instance of make in
1349 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1350 which src/Makefile will use that blindly, if it exists, so if
1351 you see the above error:
1353 rm -rf `make -V MAKEPATH`
1358 Use bmake by default.
1359 Whereas before one could choose to build with bmake via
1360 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1361 make. The goal is to remove these knobs for 10-RELEASE.
1363 It is worth noting that bmake (like gmake) treats the command
1364 line as the unit of failure, rather than statements within the
1365 command line. Thus '(cd some/where && dosomething)' is safer
1366 than 'cd some/where; dosomething'. The '()' allows consistent
1367 behavior in parallel build.
1370 Fix a bug that allows NFS clients to issue READDIR on files.
1373 The WITHOUT_IDEA option has been removed because
1374 the IDEA patent expired.
1377 The sysctl which controls TRIM support under ZFS has been renamed
1378 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1382 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1383 rather than creating it's own in the temporary directory in
1384 order allow access to bootstrapped versions of tools such as
1385 install and mtree. When upgrading from version of FreeBSD where
1386 the install command does not support -l, you will need to
1387 install a new mergemaster command if mergemaster -p is required.
1388 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1392 Legacy ATA stack, disabled and replaced by new CAM-based one since
1393 FreeBSD 9.0, completely removed from the sources. Kernel modules
1394 atadisk and atapi*, user-level tools atacontrol and burncd are
1395 removed. Kernel option `options ATA_CAM` is now permanently enabled
1399 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1400 and socketpair(2). Software, in particular Kerberos, may
1401 automatically detect and use these during building. The resulting
1402 binaries will not work on older kernels.
1405 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1406 information, see the respective 20130304 entry).
1409 Recent commits to callout(9) changed the size of struct callout,
1410 so the KBI is probably heavily disturbed. Also, some functions
1411 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1412 by macros. Every kernel module using it won't load, so rebuild
1415 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1416 but does not initialize by default (because of the new CTL_DISABLE
1417 option) to save memory. To re-enable it, remove the CTL_DISABLE
1418 option from the kernel config file or set kern.cam.ctl.disable=0
1419 in /boot/loader.conf.
1422 The ctl device has been disabled in GENERIC for i386 and amd64.
1423 This was done due to the extra memory being allocated at system
1424 initialisation time by the ctl driver which was only used if
1425 a CAM target device was created. This makes a FreeBSD system
1426 unusable on 128MB or less of RAM.
1429 A new compression method (lz4) has been merged to -HEAD. Please
1430 refer to zpool-features(7) for more information.
1432 Please refer to the "ZFS notes" section of this file for information
1433 on upgrading boot ZFS pools.
1436 A BSD-licensed patch(1) variant has been added and is installed
1437 as bsdpatch, being the GNU version the default patch.
1438 To inverse the logic and use the BSD-licensed one as default,
1439 while having the GNU version installed as gnupatch, rebuild
1440 and install world with the WITH_BSD_PATCH knob set.
1443 Due to the use of the new -l option to install(1) during build
1444 and install, you must take care not to directly set the INSTALL
1445 make variable in your /etc/make.conf, /etc/src.conf, or on the
1446 command line. If you wish to use the -C flag for all installs
1447 you may be able to add INSTALL+=-C to /etc/make.conf or
1451 The install(1) option -M has changed meaning and now takes an
1452 argument that is a file or path to append logs to. In the
1453 unlikely event that -M was the last option on the command line
1454 and the command line contained at least two files and a target
1455 directory the first file will have logs appended to it. The -M
1456 option served little practical purpose in the last decade so its
1457 use is expected to be extremely rare.
1460 After switching to Clang as the default compiler some users of ZFS
1461 on i386 systems started to experience stack overflow kernel panics.
1462 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1465 GEOM_LABEL now mangles label names read from file system metadata.
1466 Mangling affect labels containing spaces, non-printable characters,
1467 '%' or '"'. Device names in /etc/fstab and other places may need to
1471 By default, only the 10 most recent kernel dumps will be saved. To
1472 restore the previous behaviour (no limit on the number of kernel dumps
1473 stored in the dump directory) add the following line to /etc/rc.conf:
1478 With the addition of auditdistd(8), a new auditdistd user is now
1479 required during installworld. "mergemaster -p" can be used to
1480 add the user prior to installworld, as documented in the handbook.
1483 The sin6_scope_id member variable in struct sockaddr_in6 is now
1484 filled by the kernel before passing the structure to the userland via
1485 sysctl or routing socket. This means the KAME-specific embedded scope
1486 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1487 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1488 __FreeBSD_version is bumped to 1000025.
1491 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1492 This means that the world and kernel will be compiled with clang
1493 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1494 and /usr/bin/cpp. To disable this behavior and revert to building
1495 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1496 of current may need to bootstrap WITHOUT_CLANG first if the clang
1497 build fails (its compatibility window doesn't extend to the 9 stable
1501 The IPFIREWALL_FORWARD kernel option has been removed. Its
1502 functionality now turned on by default.
1505 The ZERO_COPY_SOCKET kernel option has been removed and
1506 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1507 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1508 mechanism which is not safe and may result in kernel crashes.
1509 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1510 driver supports disposeable external page sized mbuf storage.
1511 Proper replacements for both zero-copy mechanisms are under
1512 consideration and will eventually lead to complete removal
1513 of the two kernel options.
1516 The IPv4 network stack has been converted to network byte
1517 order. The following modules need to be recompiled together
1518 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1519 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1522 Support for non-MPSAFE filesystems was removed from VFS. The
1523 VFS_VERSION was bumped, all filesystem modules shall be
1527 All the non-MPSAFE filesystems have been disconnected from
1528 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1529 portalfs, smbfs, xfs.
1532 The interface cloning API and ABI has changed. The following
1533 modules need to be recompiled together with kernel:
1534 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1535 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1536 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1539 The sdhci driver was split in two parts: sdhci (generic SD Host
1540 Controller logic) and sdhci_pci (actual hardware driver).
1541 No kernel config modifications are required, but if you
1542 load sdhc as a module you must switch to sdhci_pci instead.
1545 Import the FUSE kernel and userland support into base system.
1548 The GNU sort(1) program has been removed since the BSD-licensed
1549 sort(1) has been the default for quite some time and no serious
1550 problems have been reported. The corresponding WITH_GNU_SORT
1554 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1555 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1559 The net80211(4) ABI has been changed to allow for improved driver
1560 PS-POLL and power-save support. All wireless drivers need to be
1561 recompiled to work with the new kernel.
1564 The random(4) support for the VIA hardware random number
1565 generator (`PADLOCK') is no longer enabled unconditionally.
1566 Add the padlock_rng device in the custom kernel config if
1567 needed. The GENERIC kernels on i386 and amd64 do include the
1568 device, so the change only affects the custom kernel
1572 The pf(4) packet filter ABI has been changed. pfctl(8) and
1573 snmp_pf module need to be recompiled to work with new kernel.
1576 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1577 to -HEAD. Pools that have empty_bpobj in active state can not be
1578 imported read-write with ZFS implementations that do not support
1579 this feature. For more information read the zpool-features(5)
1583 The sparc64 ZFS loader has been changed to no longer try to auto-
1584 detect ZFS providers based on diskN aliases but now requires these
1585 to be explicitly listed in the OFW boot-device environment variable.
1588 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1589 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1590 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1593 The following sysctls and tunables have been renamed for consistency
1594 with other variables:
1595 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1596 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1599 The sort utility has been replaced with BSD sort. For now, GNU sort
1600 is also available as "gnusort" or the default can be set back to
1601 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1602 installed as "bsdsort".
1605 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1606 Starting with this version the old system of ZFS pool versioning
1607 is superseded by "feature flags". This concept enables forward
1608 compatibility against certain future changes in functionality of ZFS
1609 pools. The first read-only compatible "feature flag" for ZFS pools
1610 is named "com.delphix:async_destroy". For more information
1611 read the new zpool-features(5) manual page.
1612 Please refer to the "ZFS notes" section of this file for information
1613 on upgrading boot ZFS pools.
1616 The malloc(3) implementation embedded in libc now uses sources imported
1617 as contrib/jemalloc. The most disruptive API change is to
1618 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1619 delete it prior to installworld, and optionally re-create it using the
1620 new format after rebooting. See malloc.conf(5) for details
1621 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1625 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1626 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1627 now spelled mips. This is to aid compatibility with third-party
1628 software that expects this naming scheme in uname(3). Little-endian
1629 settings are unchanged. If you are updating a big-endian mips64 machine
1630 from before this change, you may need to set MACHINE_ARCH=mips64 in
1631 your environment before the new build system will recognize your machine.
1634 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1638 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1639 nullfs(5) did not pass through all behaviours to the underlying layer,
1640 as a result if we bound to a socket on the lower layer we could connect
1641 only to the lower path; if we bound to the upper layer we could connect
1642 only to the upper path. The new behavior is one can connect to both the
1643 lower and the upper paths regardless what layer path one binds to.
1646 The getifaddrs upgrade path broken with 20111215 has been restored.
1647 If you have upgraded in between 20111215 and 20120209 you need to
1648 recompile libc again with your kernel. You still need to recompile
1649 world to be able to configure CARP but this restriction already
1650 comes from 20111215.
1653 The set_rcvar() function has been removed from /etc/rc.subr. All
1654 base and ports rc.d scripts have been updated, so if you have a
1655 port installed with a script in /usr/local/etc/rc.d you can either
1656 hand-edit the rcvar= line, or reinstall the port.
1658 An easy way to handle the mass-update of /etc/rc.d:
1659 rm /etc/rc.d/* && mergemaster -i
1662 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1663 on the current CPU and prevents other threads from running.
1664 This behavior can be reverted using the kern.stop_scheduler_on_panic
1666 The new behavior can be incompatible with kern.sync_on_panic.
1669 The carp(4) facility has been changed significantly. Configuration
1670 of the CARP protocol via ifconfig(8) has changed, as well as format
1671 of CARP events submitted to devd(8) has changed. See manual pages
1672 for more information. The arpbalance feature of carp(4) is currently
1673 not supported anymore.
1675 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1676 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1677 need to be recompiled.
1680 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1684 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1685 explicitely support non-MPSAFE filesystems.
1686 It is on by default for all supported platform at this present
1690 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1691 i386 and pc98 GENERIC kernel configuration files.
1694 sysinstall has been removed
1697 The stable/9 branch created in subversion. This corresponds to the
1698 RELENG_9 branch in CVS.
1704 Avoid using make -j when upgrading. While generally safe, there are
1705 sometimes problems using -j to upgrade. If your upgrade fails with
1706 -j, please try again without -j. From time to time in the past there
1707 have been problems using -j with buildworld and/or installworld. This
1708 is especially true when upgrading between "distant" versions (eg one
1709 that cross a major release boundary or several minor releases, or when
1710 several months have passed on the -current branch).
1712 Sometimes, obscure build problems are the result of environment
1713 poisoning. This can happen because the make utility reads its
1714 environment when searching for values for global variables. To run
1715 your build attempts in an "environmental clean room", prefix all make
1716 commands with 'env -i '. See the env(1) manual page for more details.
1718 When upgrading from one major version to another it is generally best to
1719 upgrade to the latest code in the currently installed branch first, then
1720 do an upgrade to the new branch. This is the best-tested upgrade path,
1721 and has the highest probability of being successful. Please try this
1722 approach if you encounter problems with a major version upgrade. Since
1723 the stable 4.x branch point, one has generally been able to upgade from
1724 anywhere in the most recent stable branch to head / current (or even the
1725 last couple of stable branches). See the top of this file when there's
1728 When upgrading a live system, having a root shell around before
1729 installing anything can help undo problems. Not having a root shell
1730 around can lead to problems if pam has changed too much from your
1731 starting point to allow continued authentication after the upgrade.
1733 This file should be read as a log of events. When a later event changes
1734 information of a prior event, the prior event should not be deleted.
1735 Instead, a pointer to the entry with the new information should be
1736 placed in the old entry. Readers of this file should also sanity check
1737 older entries before relying on them blindly. Authors of new entries
1738 should write them with this in mind.
1742 When upgrading the boot ZFS pool to a new version, always follow
1745 1.) recompile and reinstall the ZFS boot loader and boot block
1746 (this is part of "make buildworld" and "make installworld")
1748 2.) update the ZFS boot block on your boot drive
1750 The following example updates the ZFS boot block on the first
1751 partition (freebsd-boot) of a GPT partitioned drive ada0:
1752 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1754 Non-boot pools do not need these updates.
1758 If you are updating from a prior version of FreeBSD (even one just
1759 a few days old), you should follow this procedure. It is the most
1760 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1762 make kernel-toolchain
1763 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1764 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1766 To test a kernel once
1767 ---------------------
1768 If you just want to boot a kernel once (because you are not sure
1769 if it works, or if you want to boot a known bad kernel to provide
1770 debugging information) run
1771 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1772 nextboot -k testkernel
1774 To just build a kernel when you know that it won't mess you up
1775 --------------------------------------------------------------
1776 This assumes you are already running a CURRENT system. Replace
1777 ${arch} with the architecture of your machine (e.g. "i386",
1778 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1780 cd src/sys/${arch}/conf
1781 config KERNEL_NAME_HERE
1782 cd ../compile/KERNEL_NAME_HERE
1787 If this fails, go to the "To build a kernel" section.
1789 To rebuild everything and install it on the current system.
1790 -----------------------------------------------------------
1791 # Note: sometimes if you are running current you gotta do more than
1792 # is listed here if you are upgrading from a really old current.
1794 <make sure you have good level 0 dumps>
1796 make kernel KERNCONF=YOUR_KERNEL_HERE
1798 <reboot in single user> [3]
1805 To cross-install current onto a separate partition
1806 --------------------------------------------------
1807 # In this approach we use a separate partition to hold
1808 # current's root, 'usr', and 'var' directories. A partition
1809 # holding "/", "/usr" and "/var" should be about 2GB in
1812 <make sure you have good level 0 dumps>
1815 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1816 <maybe newfs current's root partition>
1817 <mount current's root partition on directory ${CURRENT_ROOT}>
1818 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1819 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1820 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1821 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1822 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1823 <reboot into current>
1824 <do a "native" rebuild/install as described in the previous section>
1825 <maybe install compatibility libraries from ports/misc/compat*>
1829 To upgrade in-place from stable to current
1830 ----------------------------------------------
1831 <make sure you have good level 0 dumps>
1833 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1835 <reboot in single user> [3]
1842 Make sure that you've read the UPDATING file to understand the
1843 tweaks to various things you need. At this point in the life
1844 cycle of current, things change often and you are on your own
1845 to cope. The defaults can also change, so please read ALL of
1846 the UPDATING entries.
1848 Also, if you are tracking -current, you must be subscribed to
1849 freebsd-current@freebsd.org. Make sure that before you update
1850 your sources that you have read and understood all the recent
1851 messages there. If in doubt, please track -stable which has
1852 much fewer pitfalls.
1854 [1] If you have third party modules, such as vmware, you
1855 should disable them at this point so they don't crash your
1858 [3] From the bootblocks, boot -s, and then do
1863 adjkerntz -i # if CMOS is wall time
1864 Also, when doing a major release upgrade, it is required that
1865 you boot into single user mode to do the installworld.
1867 [4] Note: This step is non-optional. Failure to do this step
1868 can result in a significant reduction in the functionality of the
1869 system. Attempting to do it by hand is not recommended and those
1870 that pursue this avenue should read this file carefully, as well
1871 as the archives of freebsd-current and freebsd-hackers mailing lists
1872 for potential gotchas. The -U option is also useful to consider.
1873 See mergemaster(8) for more information.
1875 [5] Usually this step is a noop. However, from time to time
1876 you may need to do this if you get unknown user in the following
1877 step. It never hurts to do it all the time. You may need to
1878 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1879 install) after the buildworld before this step if you last updated
1880 from current before 20130425 or from -stable before 20130430.
1882 [6] This only deletes old files and directories. Old libraries
1883 can be deleted by "make delete-old-libs", but you have to make
1884 sure that no program is using those libraries anymore.
1886 [8] In order to have a kernel that can run the 4.x binaries needed to
1887 do an installworld, you must include the COMPAT_FREEBSD4 option in
1888 your kernel. Failure to do so may leave you with a system that is
1889 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1890 required to run the 5.x binaries on more recent kernels. And so on
1891 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1893 Make sure that you merge any new devices from GENERIC since the
1894 last time you updated your kernel config file.
1896 [9] When checking out sources, you must include the -P flag to have
1897 cvs prune empty directories.
1899 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1900 "?=" instead of the "=" assignment operator, so that buildworld can
1901 override the CPUTYPE if it needs to.
1903 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1904 not on the command line, or in /etc/make.conf. buildworld will
1905 warn if it is improperly defined.
1908 This file contains a list, in reverse chronological order, of major
1909 breakages in tracking -current. It is not guaranteed to be a complete
1910 list of such breakages, and only contains entries since September 23, 2011.
1911 If you need to see UPDATING entries from before that date, you will need
1912 to fetch an UPDATING file from an older FreeBSD release.
1914 Copyright information:
1916 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1918 Redistribution, publication, translation and use, with or without
1919 modification, in full or in part, in any form or format of this
1920 document are permitted without further permission from the author.
1922 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1923 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1924 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1925 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1926 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1927 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1928 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1929 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1930 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1931 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1932 POSSIBILITY OF SUCH DAMAGE.
1934 Contact Warner Losh if you have any questions about your use of