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 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
56 a very major ABI incompatible change, so users of FreeBSD/powerpc must
57 be careful when performing source upgrades. It is best to run
58 'make installworld' from an alternate root system, either a live
59 CD/memory stick, or a temporary root partition. Additionally, all ports
60 must be recompiled. powerpc64 is largely unaffected, except in the case
61 of 32-bit compatibility. All 32-bit binaries will be affected.
64 Forward compatibility for the "ino64" project have been committed. This
65 will allow most new binaries to run on older kernels in a limited
66 fashion. This prevents many of the common foot-shooting actions in the
67 upgrade as well as the limited ability to roll back the kernel across
68 the ino64 upgrade. Complicated use cases may not work properly, though
69 enough simpler ones work to allow recovery in most situations.
72 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
73 if you require the GPL compiler.
76 The internal ABI used for communication between the NFS kernel modules
77 was changed by r320085, so __FreeBSD_version was bumped to
78 ensure all the NFS related modules are updated together.
81 The ABI of struct event was changed by extending the data
82 member to 64bit and adding ext fields. For upgrade, same
83 precautions as for the entry 20170523 "ino64" must be
87 The GNU roff toolchain has been removed from base. To render manpages
88 which are not supported by mandoc(1), man(1) can fallback on GNU roff
89 from ports (and recommends to install it).
90 To render roff(7) documents, consider using GNU roff from ports or the
91 heirloom doctools roff toolchain from ports via pkg install groff or
92 via pkg install heirloom-doctools.
95 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
96 smaller runtime footprint builds. This is useful for embedded systems
97 which only require one chipset support.
99 If you load it as a module, make sure this is in /boot/loader.conf:
103 This will load the HAL, all chip/RF backends and if_ath_pci.
104 If you have if_ath_pci in /boot/loader.conf, ensure it is after
105 if_ath or it will not load any HAL chipset support.
107 If you want to selectively load things (eg on ye cheape ARM/MIPS
108 platforms where RAM is at a premium) you should:
111 * load the chip modules in question
112 * load ath_rate, ath_dfs
114 * load if_ath_pci and/or if_ath_ahb depending upon your particular
115 bus bind type - this is where probe/attach is done.
117 For further comments/feedback, poke adrian@ .
120 The "ino64" 64-bit inode project has been committed, which extends
121 a number of types to 64 bits. Upgrading in place requires care and
122 adherence to the documented upgrade procedure.
124 If using a custom kernel configuration ensure that the
125 COMPAT_FREEBSD11 option is included (as during the upgrade the
126 system will be running the ino64 kernel with the existing world).
128 For the safest in-place upgrade begin by removing previous build
129 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
130 full procedure documented below under the heading "To rebuild
131 everything and install it on the current system." Specifically,
132 a reboot is required after installing the new kernel before
136 The NATM framework including the en(4), fatm(4), hatm(4), and
137 patm(4) devices has been removed. Consumers should plan a
138 migration before the end-of-life date for FreeBSD 11.
141 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
142 diff has not been implemented, if those are needed a newer version of
143 GNU diff is available via the diffutils package under the gdiff name.
146 As of r316810 for ipfilter, keep frags is no longer assumed when
147 keep state is specified in a rule. r316810 aligns ipfilter with
148 documentation in man pages separating keep frags from keep state.
149 This allows keep state to be specified without forcing keep frags
150 and allows keep frags to be specified independently of keep state.
151 To maintain previous behaviour, also specify keep frags with
152 keep state (as documented in ipf.conf.5).
155 arm64 builds now use the base system LLD 4.0.0 linker by default,
156 instead of requiring that the aarch64-binutils port or package be
157 installed. To continue using aarch64-binutils, set
158 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
161 The UDP optimization in entry 20160818 that added the sysctl
162 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
163 packets will no longer be treated as L3 broadcast packets.
166 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
167 use any explicitly assigned loopback address available in the jail
168 instead of using the first assigned address of the jail.
171 The ctl.ko module no longer implements the iSCSI target frontend:
172 cfiscsi.ko does instead.
174 If building cfiscsi.ko as a kernel module, the module can be loaded
175 via one of the following methods:
176 - `cfiscsi_load="YES"` in loader.conf(5).
177 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
178 - ctladm(8)/ctld(8), when compiled with iSCSI support
179 (`WITH_ISCSI=yes` in src.conf(5))
181 Please see cfiscsi(4) for more details.
184 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
185 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
186 same source (previously, the dependency of mmcsd.ko on mmc.ko was
187 missing, but mmcsd.ko now will refuse to load if it is incompatible
191 The syntax of ipfw(8) named states was changed to avoid ambiguity.
192 If you have used named states in the firewall rules, you need to modify
193 them after installworld and before rebooting. Now named states must
194 be prefixed with colon.
197 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
198 removed as the userland we provide cannot use them. The KMS version
199 (sys/dev/drm2) supports the same hardware.
202 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
203 Please see the 20141231 entry below for information about prerequisites
204 and upgrading, if you are not already using clang 3.5.0 or higher.
207 The code that provides support for ZFS .zfs/ directory functionality
208 has been reimplemented. It's not possible now to create a snapshot
209 by mkdir under .zfs/snapshot/. That should be the only user visible
213 EISA bus support has been removed. The WITH_EISA option is no longer
217 MCA bus support has been removed.
220 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
221 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
224 The EM_MULTIQUEUE kernel configuration option is deprecated now that
225 the em(4) driver conforms to iflib specifications.
228 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
229 IFLIB. If you have a custom kernel configuration that excludes em(4)
230 but you use igb(4), you need to re-add em(4) to your custom configuration.
233 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
234 Please see the 20141231 entry below for information about prerequisites
235 and upgrading, if you are not already using clang 3.5.0 or higher.
238 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
239 Please see the 20141231 entry below for information about prerequisites
240 and upgrading, if you are not already using clang 3.5.0 or higher.
243 The layout of the pmap structure has changed for powerpc to put the pmap
244 statistics at the front for all CPU variations. libkvm(3) and all tools
245 that link against it need to be recompiled.
248 isl(4) and cyapa(4) drivers now require a new driver,
249 chromebook_platform(4), to work properly on Chromebook-class hardware.
250 On other types of hardware the drivers may need to be configured using
251 device hints. Please see the corresponding manual pages for details.
254 The urtwn(4) driver was merged into rtwn(4) and now consists of
255 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
257 Also, firmware for RTL8188CE was renamed due to possible name
258 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
261 GNU rcs has been removed from base. It is available as packages:
262 - rcs: Latest GPLv3 GNU rcs version.
263 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
267 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
268 modules now requires that the kernel configuration contain the
269 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
272 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
273 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
276 Relocatable object files with the extension of .So have been renamed
277 to use an extension of .pico instead. The purpose of this change is
278 to avoid a name clash with shared libraries on case-insensitive file
279 systems. On those file systems, foo.So is the same file as foo.so.
282 GNU rcs has been turned off by default. It can (temporarily) be built
283 again by adding WITH_RCS knob in src.conf.
284 Otherwise, GNU rcs is available from packages:
285 - rcs: Latest GPLv3 GNU rcs version.
286 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
289 The backup_uses_rcs functionality has been removed from rc.subr.
292 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
293 two separate components, QUEUE_MACRO_DEBUG_TRACE and
294 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
295 QUEUE_MACRO_DEBUG behavior.
298 r304787 changed some ioctl interfaces between the iSCSI userspace
299 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
300 rebuilt to work with new kernels. __FreeBSD_version has been bumped
304 The UDP receive code has been updated to only treat incoming UDP
305 packets that were addressed to an L2 broadcast address as L3
306 broadcast packets. It is not expected that this will affect any
307 standards-conforming UDP application. The new behaviour can be
308 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
312 Remove the openbsd_poll system call.
313 __FreeBSD_version has been bumped because of this.
316 The libc stub for the pipe(2) system call has been replaced with
317 a wrapper that calls the pipe2(2) system call and the pipe(2)
318 system call is now only implemented by the kernels that include
319 "options COMPAT_FREEBSD10" in their config file (this is the
320 default). Users should ensure that this option is enabled in
321 their kernel or upgrade userspace to r302092 before upgrading their
325 CAM will now strip leading spaces from SCSI disks' serial numbers.
326 This will affect users who create UFS filesystems on SCSI disks using
327 those disk's diskid device nodes. For example, if /etc/fstab
328 previously contained a line like
329 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
330 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
331 transforms like gmirror may also be affected. ZFS users should
335 The bitstring(3) API has been updated with new functionality and
336 improved performance. But it is binary-incompatible with the old API.
337 Objects built with the new headers may not be linked against objects
338 built with the old headers.
341 The brk and sbrk functions have been removed from libc on arm64.
342 Binutils from ports has been updated to not link to these
343 functions and should be updated to the latest version before
344 installing a new libc.
347 The armv6 port now defaults to hard float ABI. Limited support
348 for running both hardfloat and soft float on the same system
349 is available using the libraries installed with -DWITH_LIBSOFT.
350 This has only been tested as an upgrade path for installworld
351 and packages may fail or need manual intervention to run. New
352 packages will be needed.
354 To update an existing self-hosted armv6hf system, you must add
355 TARGET_ARCH=armv6 on the make command line for both the build
356 and the install steps.
359 Kernel modules compiled outside of a kernel build now default to
360 installing to /boot/modules instead of /boot/kernel. Many kernel
361 modules built this way (such as those in ports) already overrode
362 KMODDIR explicitly to install into /boot/modules. However,
363 manually building and installing a module from /sys/modules will
364 now install to /boot/modules instead of /boot/kernel.
367 The CAM I/O scheduler has been committed to the kernel. There should be
368 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
369 list of known rogues that claim support for this but actually corrupt
370 data is believed to be complete, be on the lookout for data
371 corruption. The known rogue list is believed to be complete:
373 o Crucial MX100, M550 drives with MU01 firmware.
374 o Micron M510 and M550 drives with MU01 firmware.
375 o Micron M500 prior to MU07 firmware
376 o Samsung 830, 840, and 850 all firmwares
377 o FCCT M500 all firmwares
379 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
380 with working NCQ TRIM. For Micron branded drives, see your sales rep for
381 updated firmware. Black listed drives will work correctly because these
382 drives work correctly so long as no NCQ TRIMs are sent to them. Given
383 this list is the same as found in Linux, it's believed there are no
384 other rogues in the market place. All other models from the above
387 To be safe, if you are at all concerned, you can quirk each of your
388 drives to prevent NCQ from being sent by setting:
389 kern.cam.ada.X.quirks="0x2"
390 in loader.conf. If the drive requires the 4k sector quirk, set the
394 The FAST_DEPEND build option has been removed and its functionality is
395 now the one true way. The old mkdep(1) style of 'make depend' has
396 been removed. See 20160311 for further details.
399 Resource range types have grown from unsigned long to uintmax_t. All
400 drivers, and anything using libdevinfo, need to be recompiled.
403 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
404 builds. It no longer runs mkdep(1) during 'make depend', and the
405 'make depend' stage can safely be skipped now as it is auto ran
406 when building 'make all' and will generate all SRCS and DPSRCS before
407 building anything else. Dependencies are gathered at compile time with
408 -MF flags kept in separate .depend files per object file. Users should
409 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
413 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
414 kernel modules. Therefore, if you load any kernel modules at boot time,
415 please install the boot loaders after you install the kernel, but before
419 make kernel KERNCONF=YOUR_KERNEL_HERE
420 make -C sys/boot install
421 <reboot in single user>
423 Then follow the usual steps, described in the General Notes section,
427 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
428 see the 20141231 entry below for information about prerequisites and
429 upgrading, if you are not already using clang 3.5.0 or higher.
432 The AIO subsystem is now a standard part of the kernel. The
433 VFS_AIO kernel option and aio.ko kernel module have been removed.
434 Due to stability concerns, asynchronous I/O requests are only
435 permitted on sockets and raw disks by default. To enable
436 asynchronous I/O requests on all file types, set the
437 vfs.aio.enable_unsafe sysctl to a non-zero value.
440 The ELF object manipulation tool objcopy is now provided by the
441 ELF Tool Chain project rather than by GNU binutils. It should be a
442 drop-in replacement, with the addition of arm64 support. The
443 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
444 to obtain the GNU version if necessary.
447 Building ZFS pools on top of zvols is prohibited by default. That
448 feature has never worked safely; it's always been prone to deadlocks.
449 Using a zvol as the backing store for a VM guest's virtual disk will
450 still work, even if the guest is using ZFS. Legacy behavior can be
451 restored by setting vfs.zfs.vol.recursive=1.
454 The NONE and HPN patches has been removed from OpenSSH. They are
455 still available in the security/openssh-portable port.
458 With the addition of ypldap(8), a new _ypldap user is now required
459 during installworld. "mergemaster -p" can be used to add the user
460 prior to installworld, as documented in the handbook.
463 The tftp loader (pxeboot) now uses the option root-path directive. As a
464 consequence it no longer looks for a pxeboot.4th file on the tftp
465 server. Instead it uses the regular /boot infrastructure as with the
469 The code to start recording plug and play data into the modules has
470 been committed. While the old tools will properly build a new kernel,
471 a number of warnings about "unknown metadata record 4" will be produced
472 for an older kldxref. To avoid such warnings, make sure to rebuild
473 the kernel toolchain (or world). Make sure that you have r292078 or
474 later when trying to build 292077 or later before rebuilding.
477 Debug data files are now built by default with 'make buildworld' and
478 installed with 'make installworld'. This facilitates debugging but
479 requires more disk space both during the build and for the installed
480 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
484 r291527 changed the internal interface between the nfsd.ko and
485 nfscommon.ko modules. As such, they must both be upgraded to-gether.
486 __FreeBSD_version has been bumped because of this.
489 Add support for unicode collation strings leads to a change of
490 order of files listed by ls(1) for example. To get back to the old
491 behaviour, set LC_COLLATE environment variable to "C".
493 Databases administrators will need to reindex their databases given
494 collation results will be different.
496 Due to a bug in install(1) it is recommended to remove the ancient
497 locales before running make installworld.
499 rm -rf /usr/share/locale/*
502 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
503 libcrypto.so.7 or libssl.so.7 must be recompiled.
506 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
507 Kernel modules isp_2400_multi and isp_2500_multi were removed and
508 should be replaced with isp_2400 and isp_2500 modules respectively.
511 The build previously allowed using 'make -n' to not recurse into
512 sub-directories while showing what commands would be executed, and
513 'make -n -n' to recursively show commands. Now 'make -n' will recurse
514 and 'make -N' will not.
517 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
518 and etcupdate will now use this file. A custom sendmail.cf is now
519 updated via this mechanism rather than via installworld. If you had
520 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
521 want to remove the exclusion or change it to "always install".
522 /etc/mail/sendmail.cf is now managed the same way regardless of
523 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
524 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
527 Compatibility shims for legacy ATA device names have been removed.
528 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
529 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
530 environment variables, /dev/ad* and /dev/ar* symbolic links.
533 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
534 Please see the 20141231 entry below for information about prerequisites
535 and upgrading, if you are not already using clang 3.5.0 or higher.
538 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
539 and renamed from .symbols to .debug. This reduces the size requirements
540 on the boot partition or file system and provides consistency with
541 userland debug files.
543 When using the supported kernel installation method the
544 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
545 as is done with /boot/kernel.
547 Developers wishing to maintain the historical behavior of installing
548 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
551 The wireless drivers had undergone changes that remove the 'parent
552 interface' from the ifconfig -l output. The rc.d network scripts
553 used to check presence of a parent interface in the list, so old
554 scripts would fail to start wireless networking. Thus, etcupdate(3)
555 or mergemaster(8) run is required after kernel update, to update your
556 rc.d scripts in /etc.
559 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
560 These configurations are now automatically interpreted as
561 'scrub fragment reassemble'.
564 Kernel-loadable modules for the random(4) device are back. To use
565 them, the kernel must have
568 options RANDOM_LOADABLE
570 kldload(8) can then be used to load random_fortuna.ko
571 or random_yarrow.ko. Please note that due to the indirect
572 function calls that the loadable modules need to provide,
573 the build-in variants will be slightly more efficient.
575 The random(4) kernel option RANDOM_DUMMY has been retired due to
576 unpopularity. It was not all that useful anyway.
579 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
580 Control over building the ELF Tool Chain tools is now provided by
581 the WITHOUT_TOOLCHAIN knob.
584 The polarity of Pulse Per Second (PPS) capture events with the
585 uart(4) driver has been corrected. Prior to this change the PPS
586 "assert" event corresponded to the trailing edge of a positive PPS
587 pulse and the "clear" event was the leading edge of the next pulse.
589 As the width of a PPS pulse in a typical GPS receiver is on the
590 order of 1 millisecond, most users will not notice any significant
591 difference with this change.
593 Anyone who has compensated for the historical polarity reversal by
594 configuring a negative offset equal to the pulse width will need to
595 remove that workaround.
598 The default group assigned to /dev/dri entries has been changed
599 from 'wheel' to 'video' with the id of '44'. If you want to have
600 access to the dri devices please add yourself to the video group
603 # pw groupmod video -m $USER
606 The menu.rc and loader.rc files will now be replaced during
607 upgrades. Please migrate local changes to menu.rc.local and
608 loader.rc.local instead.
611 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
612 strings and strip have been removed. The src.conf(5) knob
613 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
616 As ZFS requires more kernel stack pages than is the default on some
617 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
618 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
620 Please consider using 'options KSTACK_PAGES=X' where X is greater
621 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
624 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
625 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
626 default, i.e., they will not contain "::". For example, instead
627 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
628 to have a more specific match, such as different map entries for
629 IPv6:0:0 vs IPv6:0. This change requires that configuration
630 data (including maps, files, classes, custom ruleset, etc.) must
631 use the same format, so make certain such configuration data is
632 upgrading. As a very simple check search for patterns like
633 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
634 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
635 the cf option UseCompressedIPv6Addresses.
638 The default kernel entropy-processing algorithm is now
639 Fortuna, replacing Yarrow.
641 Assuming you have 'device random' in your kernel config
642 file, the configurations allow a kernel option to override
643 this default. You may choose *ONE* of:
645 options RANDOM_YARROW # Legacy /dev/random algorithm.
646 options RANDOM_DUMMY # Blocking-only driver.
648 If you have neither, you get Fortuna. For most people,
649 read no further, Fortuna will give a /dev/random that works
650 like it always used to, and the difference will be irrelevant.
652 If you remove 'device random', you get *NO* kernel-processed
653 entropy at all. This may be acceptable to folks building
654 embedded systems, but has complications. Carry on reading,
655 and it is assumed you know what you need.
657 *PLEASE* read random(4) and random(9) if you are in the
658 habit of tweaking kernel configs, and/or if you are a member
659 of the embedded community, wanting specific and not-usual
660 behaviour from your security subsystems.
662 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
663 random', you will NOT have a functioning /dev/random, and
664 many cryptographic features will not work, including SSH.
665 You may also find strange behaviour from the random(3) set
666 of library functions, in particular sranddev(3), srandomdev(3)
667 and arc4random(3). The reason for this is that the KERN_ARND
668 sysctl only returns entropy if it thinks it has some to
669 share, and with RANDOM_DUMMY or no 'device random' this
673 An additional fix for the issue described in the 20150614 sendmail
674 entry below has been been committed in revision 284717.
677 FreeBSD's old make (fmake) has been removed from the system. It is
678 available as the devel/fmake port or via pkg install fmake.
681 The fix for the issue described in the 20150614 sendmail entry
682 below has been been committed in revision 284436. The work
683 around described in that entry is no longer needed unless the
684 default setting is overridden by a confDH_PARAMETERS configuration
685 setting of '5' or pointing to a 512 bit DH parameter file.
688 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
689 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
690 and devel/kyua to version 0.20+ and adjust any calling code to work
691 with Kyuafile and kyua.
694 The import of openssl to address the FreeBSD-SA-15:10.openssl
695 security advisory includes a change which rejects handshakes
696 with DH parameters below 768 bits. sendmail releases prior
697 to 8.15.2 (not yet released), defaulted to a 512 bit
698 DH parameter setting for client connections. To work around
699 this interoperability, sendmail can be configured to use a
700 2048 bit DH parameter by:
702 1. Edit /etc/mail/`hostname`.mc
703 2. If a setting for confDH_PARAMETERS does not exist or
704 exists and is set to a string beginning with '5',
706 3. If a setting for confDH_PARAMETERS exists and is set to
707 a file path, create a new file with:
708 openssl dhparam -out /path/to/file 2048
709 4. Rebuild the .cf file:
710 cd /etc/mail/; make; make install
712 cd /etc/mail/; make restart
714 A sendmail patch is coming, at which time this file will be
718 Generation of legacy formatted entries have been disabled by default
719 in pwd_mkdb(8), as all base system consumers of the legacy formatted
720 entries were converted to use the new format by default when the new,
721 machine independent format have been added and supported since FreeBSD
724 Please see the pwd_mkdb(8) manual page for further details.
727 Clang and llvm have been upgraded to 3.6.1 release. Please see the
728 20141231 entry below for information about prerequisites and upgrading,
729 if you are not already using 3.5.0 or higher.
732 TI platform code switched to using vendor DTS files and this update
733 may break existing systems running on Beaglebone, Beaglebone Black,
736 - dtb files should be regenerated/reinstalled. Filenames are the
737 same but content is different now
738 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
739 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
740 addressing scheme is now pin 25 on /dev/gpioc3.
741 - Pandaboard: /etc/ttys should be updated, serial console device is
742 now /dev/ttyu2, not /dev/ttyu0
745 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
746 If you need the GNU extension from groff soelim(1), install groff
747 from package: pkg install groff, or via ports: textproc/groff.
750 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
751 defined in symlink(7); previously symlinks were silently ignored.
754 The const qualifier has been removed from iconv(3) to comply with
755 POSIX. The ports tree is aware of this from r384038 onwards.
758 Libraries specified by LIBADD in Makefiles must have a corresponding
759 DPADD_<lib> variable to ensure correct dependencies. This is now
760 enforced in src.libnames.mk.
763 From legacy ata(4) driver was removed support for SATA controllers
764 supported by more functional drivers ahci(4), siis(4) and mvs(4).
765 Kernel modules ataahci and ataadaptec were removed completely,
766 replaced by ahci and mvs modules respectively.
769 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
770 the 20141231 entry below for information about prerequisites and
771 upgrading, if you are not already using 3.5.0 or higher.
774 The 32-bit PowerPC kernel has been changed to a position-independent
775 executable. This can only be booted with a version of loader(8)
776 newer than January 31, 2015, so make sure to update both world and
777 kernel before rebooting.
780 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
781 but before r278950, the RNG was not seeded properly. Immediately
782 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
783 ssh keys or openssl keys) that were generated w/ a kernel from that
784 range. This does not affect programs that directly used /dev/random
785 or /dev/urandom. All userland uses of arc4random(3) are affected.
788 The autofs(4) ABI was changed in order to restore binary compatibility
789 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
793 The powerpc64 kernel has been changed to a position-independent
794 executable. This can only be booted with a new version of loader(8),
795 so make sure to update both world and kernel before rebooting.
798 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
799 only release, no new features have been added. Please see the 20141231
800 entry below for information about prerequisites and upgrading, if you
801 are not already using 3.5.0.
804 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
805 taken from the ELF Tool Chain project rather than GNU binutils. They
806 should be drop-in replacements, with the addition of arm64 support.
807 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
808 binutils tools, if necessary. See 20150805 for updated information.
811 The default Unbound configuration now enables remote control
812 using a local socket. Users who have already enabled the
813 local_unbound service should regenerate their configuration
814 by running "service local_unbound setup" as root.
817 The GNU texinfo and GNU info pages have been removed.
818 To be able to view GNU info pages please install texinfo from ports.
821 Clang, llvm and lldb have been upgraded to 3.5.0 release.
823 As of this release, a prerequisite for building clang, llvm and lldb is
824 a C++11 capable compiler and C++11 standard library. This means that to
825 be able to successfully build the cross-tools stage of buildworld, with
826 clang as the bootstrap compiler, your system compiler or cross compiler
827 should either be clang 3.3 or later, or gcc 4.8 or later, and your
828 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
831 On any standard FreeBSD 10.x or 11.x installation, where clang and
832 libc++ are on by default (that is, on x86 or arm), this should work out
835 On 9.x installations where clang is enabled by default, e.g. on x86 and
836 powerpc, libc++ will not be enabled by default, so libc++ should be
837 built (with clang) and installed first. If both clang and libc++ are
838 missing, build clang first, then use it to build libc++.
840 On 8.x and earlier installations, upgrade to 9.x first, and then follow
841 the instructions for 9.x above.
843 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
844 default, and do not build clang.
846 Many embedded systems are resource constrained, and will not be able to
847 build clang in a reasonable time, or in some cases at all. In those
848 cases, cross building bootable systems on amd64 is a workaround.
850 This new version of clang introduces a number of new warnings, of which
851 the following are most likely to appear:
855 This warns in two cases, for both C and C++:
856 * When the code is trying to take the absolute value of an unsigned
857 quantity, which is effectively a no-op, and almost never what was
858 intended. The code should be fixed, if at all possible. If you are
859 sure that the unsigned quantity can be safely cast to signed, without
860 loss of information or undefined behavior, you can add an explicit
861 cast, or disable the warning.
863 * When the code is trying to take an absolute value, but the called
864 abs() variant is for the wrong type, which can lead to truncation.
865 If you want to disable the warning instead of fixing the code, please
866 make sure that truncation will not occur, or it might lead to unwanted
869 -Wtautological-undefined-compare and
870 -Wundefined-bool-conversion
872 These warn when C++ code is trying to compare 'this' against NULL, while
873 'this' should never be NULL in well-defined C++ code. However, there is
874 some legacy (pre C++11) code out there, which actively abuses this
875 feature, which was less strictly defined in previous C++ versions.
877 Squid and openjdk do this, for example. The warning can be turned off
878 for C++98 and earlier, but compiling the code in C++11 mode might result
879 in unexpected behavior; for example, the parts of the program that are
880 unreachable could be optimized away.
883 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
884 kernel sources have been removed. The .h files remain, since some
885 utilities include them. This will need to be fixed later.
886 If "mount -t oldnfs ..." is attempted, it will fail.
887 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
888 the utilities will report errors.
891 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
892 directories to top level SUBDIR variable when their parent
893 directory is included in LOCAL_DIRS. Users with build systems with
894 such hierarchies and without SUBDIR entries in the parent
895 directory Makefiles should add them or add the directories to
899 faith(4) and faithd(8) have been removed from the base system. Faith
900 has been obsolete for a very long time.
903 vt(4), the new console driver, is enabled by default. It brings
904 support for Unicode and double-width characters, as well as
905 support for UEFI and integration with the KMS kernel video
908 You may need to update your console settings in /etc/rc.conf,
909 most probably the keymap. During boot, /etc/rc.d/syscons will
910 indicate what you need to do.
912 vt(4) still has issues and lacks some features compared to
913 syscons(4). See the wiki for up-to-date information:
914 https://wiki.freebsd.org/Newcons
916 If you want to keep using syscons(4), you can do so by adding
917 the following line to /boot/loader.conf:
921 pjdfstest has been integrated into kyua as an opt-in test suite.
922 Please see share/doc/pjdfstest/README for more details on how to
926 gperf has been removed from the base system for architectures
927 that use clang. Ports that require gperf will obtain it from the
931 pjdfstest has been moved from tools/regression/pjdfstest to
935 At svn r271982, The default linux compat kernel ABI has been adjusted
936 to 2.6.18 in support of the linux-c6 compat ports infrastructure
937 update. If you wish to continue using the linux-f10 compat ports,
938 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
939 encouraged to update their linux-compat packages to linux-c6 during
940 their next update cycle.
943 The ofwfb driver, used to provide a graphics console on PowerPC when
944 using vt(4), no longer allows mmap() of all physical memory. This
945 will prevent Xorg on PowerPC with some ATI graphics cards from
946 initializing properly unless x11-servers/xorg-server is updated to
950 The xdev targets have been converted to using TARGET and
951 TARGET_ARCH instead of XDEV and XDEV_ARCH.
954 The default unbound configuration has been modified to address
955 issues with reverse lookups on networks that use private
956 address ranges. If you use the local_unbound service, run
957 "service local_unbound setup" as root to regenerate your
958 configuration, then "service local_unbound reload" to load the
962 The GNU texinfo and GNU info pages are not built and installed
963 anymore, WITH_INFO knob has been added to allow to built and install
965 UPDATE: see 20150102 entry on texinfo's removal
968 The GNU readline library is now an INTERNALLIB - that is, it is
969 statically linked into consumers (GDB and variants) in the base
970 system, and the shared library is no longer installed. The
971 devel/readline port is available for third party software that
975 The Itanium architecture (ia64) has been removed from the list of
976 known architectures. This is the first step in the removal of the
980 Commit r268115 has added NFSv4.1 server support, merged from
981 projects/nfsv4.1-server. Since this includes changes to the
982 internal interfaces between the NFS related modules, a full
983 build of the kernel and modules will be necessary.
984 __FreeBSD_version has been bumped.
987 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
988 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
989 which differs from the behaviour controlled by this knob.)
992 Maximal length of the serial number in CTL was increased from 16 to
993 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
994 and ctld, need to be rebuilt to work with a new kernel.
997 The libatf-c and libatf-c++ major versions were downgraded to 0 and
998 1 respectively to match the upstream numbers. They were out of
999 sync because, when they were originally added to FreeBSD, the
1000 upstream versions were not respected. These libraries are private
1001 and not yet built by default, so renumbering them should be a
1002 non-issue. However, unclean source trees will yield broken test
1003 programs once the operator executes "make delete-old-libs" after a
1004 "make installworld".
1006 Additionally, the atf-sh binary was made private by moving it into
1007 /usr/libexec/. Already-built shell test programs will keep the
1008 path to the old binary so they will break after "make delete-old"
1011 If you are using WITH_TESTS=yes (not the default), wipe the object
1012 tree and rebuild from scratch to prevent spurious test failures.
1013 This is only needed once: the misnumbered libraries and misplaced
1014 binaries have been added to OptionalObsoleteFiles.inc so they will
1015 be removed during a clean upgrade.
1018 Clang and llvm have been upgraded to 3.4.1 release.
1021 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1022 be removed to avoid issues in the future (and has been added to
1026 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1027 past, it affected all builds that used the bsd.*.mk files. The old
1028 behavior was a bug, but people may have relied upon it. To get this
1029 behavior back, you can .include /etc/src.conf from /etc/make.conf
1030 (which is still global and isn't changed). This also changes the
1031 behavior of incremental builds inside the tree of individual
1032 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1033 Although this has survived make universe and some upgrade scenarios,
1034 other upgrade scenarios may have broken. At least one form of
1035 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1036 as well... In cases where MAKESYSPATH isn't working with this
1037 setting, you'll need to set it to the full path to your tree.
1039 One side effect of all this cleaning up is that bsd.compiler.mk
1040 is no longer implicitly included by bsd.own.mk. If you wish to
1041 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1045 The lindev device has been removed since /dev/full has been made a
1046 standard device. __FreeBSD_version has been bumped.
1049 The knob WITHOUT_VI was added to the base system, which controls
1050 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1051 in order to reorder files share/termcap and didn't build ex(1) as a
1052 build tool, so building/installing with WITH_VI is highly advised for
1053 build hosts for older releases.
1055 This issue has been fixed in stable/9 and stable/10 in r277022 and
1056 r276991, respectively.
1059 The YES_HESIOD knob has been removed. It has been obsolete for
1060 a decade. Please move to using WITH_HESIOD instead or your builds
1061 will silently lack HESIOD.
1064 The uart(4) driver has been changed with respect to its handling
1065 of the low-level console. Previously the uart(4) driver prevented
1066 any process from changing the baudrate or the CLOCAL and HUPCL
1067 control flags. By removing the restrictions, operators can make
1068 changes to the serial console port without having to reboot.
1069 However, when getty(8) is started on the serial device that is
1070 associated with the low-level console, a misconfigured terminal
1071 line in /etc/ttys will now have a real impact.
1072 Before upgrading the kernel, make sure that /etc/ttys has the
1073 serial console device configured as 3wire without baudrate to
1074 preserve the previous behaviour. E.g:
1075 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1078 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1079 to improve performance. To re-enable it, if needed, run rpcbind
1080 with command line option -W.
1083 Switched back to the GPL dtc compiler due to updates in the upstream
1084 dts files not being supported by the BSDL dtc compiler. You will need
1085 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1086 may result while building dtb files during a kernel build if you fail
1087 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1090 Clang and llvm have been upgraded to 3.4 release.
1093 The nve(4) driver has been removed. Please use the nfe(4) driver
1094 for NVIDIA nForce MCP Ethernet adapters instead.
1097 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1098 This could cause certain C++ applications using shared libraries built
1099 against the previous version of libc++ to crash. The incompatibility
1100 has now been fixed, but any C++ applications or shared libraries built
1101 between r261283 and r261801 should be recompiled.
1104 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1105 capability mode support. Please note that enabling the feature in
1106 kernel is still highly recommended.
1109 OpenSSH is now built with sandbox support, and will use sandbox as
1110 the default privilege separation method. This requires Capsicum
1111 capability mode support in kernel.
1114 The libelf and libdwarf libraries have been updated to newer
1115 versions from upstream. Shared library version numbers for
1116 these two libraries were bumped. Any ports or binaries
1117 requiring these two libraries should be recompiled.
1118 __FreeBSD_version is bumped to 1100006.
1121 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1122 instead of providing an explicit one, this would prevent such
1123 Makefile from providing its own Kyuafile in the future during
1124 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1125 intervention is needed to clean an objdir if you use NO_CLEAN:
1126 # find /usr/obj -name Kyuafile | xargs rm -f
1129 The behavior of gss_pseudo_random() for the krb5 mechanism
1130 has changed, for applications requesting a longer random string
1131 than produced by the underlying enctype's pseudo-random() function.
1132 In particular, the random string produced from a session key of
1133 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1134 be different at the 17th octet and later, after this change.
1135 The counter used in the PRF+ construction is now encoded as a
1136 big-endian integer in accordance with RFC 4402.
1137 __FreeBSD_version is bumped to 1100004.
1140 The WITHOUT_ATF build knob has been removed and its functionality
1141 has been subsumed into the more generic WITHOUT_TESTS. If you were
1142 using the former to disable the build of the ATF libraries, you
1143 should change your settings to use the latter.
1146 The default version of mtree is nmtree which is obtained from
1147 NetBSD. The output is generally the same, but may vary
1148 slightly. If you found you need identical output adding
1149 "-F freebsd9" to the command line should do the trick. For the
1150 time being, the old mtree is available as fmtree.
1153 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1154 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1155 1.1.4_8 and verify bsdyml not linked in, before running "make
1157 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1159 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1162 The stable/10 branch has been created in subversion from head
1166 The rc.d/jail script has been updated to support jail(8)
1167 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1168 for per-jail configuration are automatically converted to
1169 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1170 This is transparently backward compatible. See below about some
1171 incompatibilities and rc.conf(5) manual page for more details.
1173 These variables are now deprecated in favor of jail(8) configuration
1174 file. One can use "rc.d/jail config <jname>" command to generate
1175 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1176 running the jail(8) utility. The default pathname of the
1177 configuration file is /etc/jail.conf and can be specified by
1178 using $jail_conf or $jail_<jname>_conf variables.
1180 Please note that jail_devfs_ruleset accepts an integer at
1181 this moment. Please consider to rewrite the ruleset name
1185 BIND has been removed from the base system. If all you need
1186 is a local resolver, simply enable and start the local_unbound
1187 service instead. Otherwise, several versions of BIND are
1188 available in the ports tree. The dns/bind99 port is one example.
1190 With this change, nslookup(1) and dig(1) are no longer in the base
1191 system. Users should instead use host(1) and drill(1) which are
1192 in the base system. Alternatively, nslookup and dig can
1193 be obtained by installing the dns/bind-tools port.
1196 With the addition of unbound(8), a new unbound user is now
1197 required during installworld. "mergemaster -p" can be used to
1198 add the user prior to installworld, as documented in the handbook.
1201 OpenSSH is now built with DNSSEC support, and will by default
1202 silently trust signed SSHFP records. This can be controlled with
1203 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1204 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1207 The GNU Compiler Collection and C++ standard library (libstdc++)
1208 are no longer built by default on platforms where clang is the system
1209 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1210 options in src.conf.
1213 The PROCDESC kernel option is now part of the GENERIC kernel
1214 configuration and is required for the rwhod(8) to work.
1215 If you are using custom kernel configuration, you should include
1219 The API and ABI related to the Capsicum framework was modified
1220 in backward incompatible way. The userland libraries and programs
1221 have to be recompiled to work with the new kernel. This includes the
1222 following libraries and programs, but the whole buildworld is
1223 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1224 kdump, procstat, rwho, rwhod, uniq.
1227 AES-NI intrinsic support has been added to gcc. The AES-NI module
1228 has been updated to use this support. A new gcc is required to build
1229 the aesni module on both i386 and amd64.
1232 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1233 Thus "device padlock_rng" and "device rdrand_rng" should be
1234 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1237 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1238 enables just the iconv* functionality and is now on by default.
1239 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1240 compatibility. Set WITHOUT_ICONV to build the old way.
1241 If you have been using WITH_ICONV before, you will very likely
1242 need to turn on WITH_LIBICONV_COMPAT.
1245 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1246 Illumos origin, including ZFS. If you have INVARIANTS in your
1247 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1249 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1250 locks if WITNESS option was set. Because that generated a lot of
1251 witness(9) reports and all of them were believed to be false
1252 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1253 can be used to achieve the previous behavior.
1256 Timer values in IPv6 data structures now use time_uptime instead
1257 of time_second. Although this is not a user-visible functional
1258 change, userland utilities which directly use them---ndp(8),
1259 rtadvd(8), and rtsold(8) in the base system---need to be updated
1260 to r253970 or later.
1263 find -delete can now delete the pathnames given as arguments,
1264 instead of only files found below them or if the pathname did
1265 not contain any slashes. Formerly, the following error message
1268 find: -delete: <path>: relative path potentially not safe
1270 Deleting the pathnames given as arguments can be prevented
1271 without error messages using -mindepth 1 or by changing
1272 directory and passing "." as argument to find. This works in the
1273 old as well as the new version of find.
1276 Behavior of devfs rules path matching has been changed.
1277 Pattern is now always matched against fully qualified devfs
1278 path and slash characters must be explicitly matched by
1279 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1280 subdirectories must be reviewed.
1283 The default ARM ABI has changed to the ARM EABI. The old ABI is
1284 incompatible with the ARM EABI and all programs and modules will
1285 need to be rebuilt to work with a new kernel.
1287 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1289 NOTE: Support for the old ABI will be removed in the future and
1290 users are advised to upgrade.
1293 pkg_install has been disconnected from the build if you really need it
1294 you should add WITH_PKGTOOLS in your src.conf(5).
1297 Most of network statistics structures were changed to be able
1298 keep 64-bits counters. Thus all tools, that work with networking
1299 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1302 Fix a bug that allowed a tracing process (e.g. gdb) to write
1303 to a memory-mapped file in the traced process's address space
1304 even if neither the traced process nor the tracing process had
1305 write access to that file.
1308 CVS has been removed from the base system. An exact copy
1309 of the code is available from the devel/cvs port.
1312 Some people report the following error after the switch to bmake:
1314 make: illegal option -- J
1315 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1317 *** [buildworld] Error code 2
1319 this likely due to an old instance of make in
1320 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1321 which src/Makefile will use that blindly, if it exists, so if
1322 you see the above error:
1324 rm -rf `make -V MAKEPATH`
1329 Use bmake by default.
1330 Whereas before one could choose to build with bmake via
1331 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1332 make. The goal is to remove these knobs for 10-RELEASE.
1334 It is worth noting that bmake (like gmake) treats the command
1335 line as the unit of failure, rather than statements within the
1336 command line. Thus '(cd some/where && dosomething)' is safer
1337 than 'cd some/where; dosomething'. The '()' allows consistent
1338 behavior in parallel build.
1341 Fix a bug that allows NFS clients to issue READDIR on files.
1344 The WITHOUT_IDEA option has been removed because
1345 the IDEA patent expired.
1348 The sysctl which controls TRIM support under ZFS has been renamed
1349 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1353 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1354 rather than creating it's own in the temporary directory in
1355 order allow access to bootstrapped versions of tools such as
1356 install and mtree. When upgrading from version of FreeBSD where
1357 the install command does not support -l, you will need to
1358 install a new mergemaster command if mergemaster -p is required.
1359 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1363 Legacy ATA stack, disabled and replaced by new CAM-based one since
1364 FreeBSD 9.0, completely removed from the sources. Kernel modules
1365 atadisk and atapi*, user-level tools atacontrol and burncd are
1366 removed. Kernel option `options ATA_CAM` is now permanently enabled
1370 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1371 and socketpair(2). Software, in particular Kerberos, may
1372 automatically detect and use these during building. The resulting
1373 binaries will not work on older kernels.
1376 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1377 information, see the respective 20130304 entry).
1380 Recent commits to callout(9) changed the size of struct callout,
1381 so the KBI is probably heavily disturbed. Also, some functions
1382 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1383 by macros. Every kernel module using it won't load, so rebuild
1386 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1387 but does not initialize by default (because of the new CTL_DISABLE
1388 option) to save memory. To re-enable it, remove the CTL_DISABLE
1389 option from the kernel config file or set kern.cam.ctl.disable=0
1390 in /boot/loader.conf.
1393 The ctl device has been disabled in GENERIC for i386 and amd64.
1394 This was done due to the extra memory being allocated at system
1395 initialisation time by the ctl driver which was only used if
1396 a CAM target device was created. This makes a FreeBSD system
1397 unusable on 128MB or less of RAM.
1400 A new compression method (lz4) has been merged to -HEAD. Please
1401 refer to zpool-features(7) for more information.
1403 Please refer to the "ZFS notes" section of this file for information
1404 on upgrading boot ZFS pools.
1407 A BSD-licensed patch(1) variant has been added and is installed
1408 as bsdpatch, being the GNU version the default patch.
1409 To inverse the logic and use the BSD-licensed one as default,
1410 while having the GNU version installed as gnupatch, rebuild
1411 and install world with the WITH_BSD_PATCH knob set.
1414 Due to the use of the new -l option to install(1) during build
1415 and install, you must take care not to directly set the INSTALL
1416 make variable in your /etc/make.conf, /etc/src.conf, or on the
1417 command line. If you wish to use the -C flag for all installs
1418 you may be able to add INSTALL+=-C to /etc/make.conf or
1422 The install(1) option -M has changed meaning and now takes an
1423 argument that is a file or path to append logs to. In the
1424 unlikely event that -M was the last option on the command line
1425 and the command line contained at least two files and a target
1426 directory the first file will have logs appended to it. The -M
1427 option served little practical purpose in the last decade so its
1428 use is expected to be extremely rare.
1431 After switching to Clang as the default compiler some users of ZFS
1432 on i386 systems started to experience stack overflow kernel panics.
1433 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1436 GEOM_LABEL now mangles label names read from file system metadata.
1437 Mangling affect labels containing spaces, non-printable characters,
1438 '%' or '"'. Device names in /etc/fstab and other places may need to
1442 By default, only the 10 most recent kernel dumps will be saved. To
1443 restore the previous behaviour (no limit on the number of kernel dumps
1444 stored in the dump directory) add the following line to /etc/rc.conf:
1449 With the addition of auditdistd(8), a new auditdistd user is now
1450 required during installworld. "mergemaster -p" can be used to
1451 add the user prior to installworld, as documented in the handbook.
1454 The sin6_scope_id member variable in struct sockaddr_in6 is now
1455 filled by the kernel before passing the structure to the userland via
1456 sysctl or routing socket. This means the KAME-specific embedded scope
1457 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1458 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1459 __FreeBSD_version is bumped to 1000025.
1462 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1463 This means that the world and kernel will be compiled with clang
1464 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1465 and /usr/bin/cpp. To disable this behavior and revert to building
1466 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1467 of current may need to bootstrap WITHOUT_CLANG first if the clang
1468 build fails (its compatibility window doesn't extend to the 9 stable
1472 The IPFIREWALL_FORWARD kernel option has been removed. Its
1473 functionality now turned on by default.
1476 The ZERO_COPY_SOCKET kernel option has been removed and
1477 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1478 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1479 mechanism which is not safe and may result in kernel crashes.
1480 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1481 driver supports disposeable external page sized mbuf storage.
1482 Proper replacements for both zero-copy mechanisms are under
1483 consideration and will eventually lead to complete removal
1484 of the two kernel options.
1487 The IPv4 network stack has been converted to network byte
1488 order. The following modules need to be recompiled together
1489 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1490 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1493 Support for non-MPSAFE filesystems was removed from VFS. The
1494 VFS_VERSION was bumped, all filesystem modules shall be
1498 All the non-MPSAFE filesystems have been disconnected from
1499 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1500 portalfs, smbfs, xfs.
1503 The interface cloning API and ABI has changed. The following
1504 modules need to be recompiled together with kernel:
1505 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1506 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1507 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1510 The sdhci driver was split in two parts: sdhci (generic SD Host
1511 Controller logic) and sdhci_pci (actual hardware driver).
1512 No kernel config modifications are required, but if you
1513 load sdhc as a module you must switch to sdhci_pci instead.
1516 Import the FUSE kernel and userland support into base system.
1519 The GNU sort(1) program has been removed since the BSD-licensed
1520 sort(1) has been the default for quite some time and no serious
1521 problems have been reported. The corresponding WITH_GNU_SORT
1525 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1526 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1530 The net80211(4) ABI has been changed to allow for improved driver
1531 PS-POLL and power-save support. All wireless drivers need to be
1532 recompiled to work with the new kernel.
1535 The random(4) support for the VIA hardware random number
1536 generator (`PADLOCK') is no longer enabled unconditionally.
1537 Add the padlock_rng device in the custom kernel config if
1538 needed. The GENERIC kernels on i386 and amd64 do include the
1539 device, so the change only affects the custom kernel
1543 The pf(4) packet filter ABI has been changed. pfctl(8) and
1544 snmp_pf module need to be recompiled to work with new kernel.
1547 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1548 to -HEAD. Pools that have empty_bpobj in active state can not be
1549 imported read-write with ZFS implementations that do not support
1550 this feature. For more information read the zpool-features(5)
1554 The sparc64 ZFS loader has been changed to no longer try to auto-
1555 detect ZFS providers based on diskN aliases but now requires these
1556 to be explicitly listed in the OFW boot-device environment variable.
1559 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1560 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1561 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1564 The following sysctls and tunables have been renamed for consistency
1565 with other variables:
1566 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1567 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1570 The sort utility has been replaced with BSD sort. For now, GNU sort
1571 is also available as "gnusort" or the default can be set back to
1572 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1573 installed as "bsdsort".
1576 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1577 Starting with this version the old system of ZFS pool versioning
1578 is superseded by "feature flags". This concept enables forward
1579 compatibility against certain future changes in functionality of ZFS
1580 pools. The first read-only compatible "feature flag" for ZFS pools
1581 is named "com.delphix:async_destroy". For more information
1582 read the new zpool-features(5) manual page.
1583 Please refer to the "ZFS notes" section of this file for information
1584 on upgrading boot ZFS pools.
1587 The malloc(3) implementation embedded in libc now uses sources imported
1588 as contrib/jemalloc. The most disruptive API change is to
1589 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1590 delete it prior to installworld, and optionally re-create it using the
1591 new format after rebooting. See malloc.conf(5) for details
1592 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1596 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1597 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1598 now spelled mips. This is to aid compatibility with third-party
1599 software that expects this naming scheme in uname(3). Little-endian
1600 settings are unchanged. If you are updating a big-endian mips64 machine
1601 from before this change, you may need to set MACHINE_ARCH=mips64 in
1602 your environment before the new build system will recognize your machine.
1605 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1609 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1610 nullfs(5) did not pass through all behaviours to the underlying layer,
1611 as a result if we bound to a socket on the lower layer we could connect
1612 only to the lower path; if we bound to the upper layer we could connect
1613 only to the upper path. The new behavior is one can connect to both the
1614 lower and the upper paths regardless what layer path one binds to.
1617 The getifaddrs upgrade path broken with 20111215 has been restored.
1618 If you have upgraded in between 20111215 and 20120209 you need to
1619 recompile libc again with your kernel. You still need to recompile
1620 world to be able to configure CARP but this restriction already
1621 comes from 20111215.
1624 The set_rcvar() function has been removed from /etc/rc.subr. All
1625 base and ports rc.d scripts have been updated, so if you have a
1626 port installed with a script in /usr/local/etc/rc.d you can either
1627 hand-edit the rcvar= line, or reinstall the port.
1629 An easy way to handle the mass-update of /etc/rc.d:
1630 rm /etc/rc.d/* && mergemaster -i
1633 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1634 on the current CPU and prevents other threads from running.
1635 This behavior can be reverted using the kern.stop_scheduler_on_panic
1637 The new behavior can be incompatible with kern.sync_on_panic.
1640 The carp(4) facility has been changed significantly. Configuration
1641 of the CARP protocol via ifconfig(8) has changed, as well as format
1642 of CARP events submitted to devd(8) has changed. See manual pages
1643 for more information. The arpbalance feature of carp(4) is currently
1644 not supported anymore.
1646 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1647 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1648 need to be recompiled.
1651 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1655 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1656 explicitely support non-MPSAFE filesystems.
1657 It is on by default for all supported platform at this present
1661 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1662 i386 and pc98 GENERIC kernel configuration files.
1665 sysinstall has been removed
1668 The stable/9 branch created in subversion. This corresponds to the
1669 RELENG_9 branch in CVS.
1675 Avoid using make -j when upgrading. While generally safe, there are
1676 sometimes problems using -j to upgrade. If your upgrade fails with
1677 -j, please try again without -j. From time to time in the past there
1678 have been problems using -j with buildworld and/or installworld. This
1679 is especially true when upgrading between "distant" versions (eg one
1680 that cross a major release boundary or several minor releases, or when
1681 several months have passed on the -current branch).
1683 Sometimes, obscure build problems are the result of environment
1684 poisoning. This can happen because the make utility reads its
1685 environment when searching for values for global variables. To run
1686 your build attempts in an "environmental clean room", prefix all make
1687 commands with 'env -i '. See the env(1) manual page for more details.
1689 When upgrading from one major version to another it is generally best to
1690 upgrade to the latest code in the currently installed branch first, then
1691 do an upgrade to the new branch. This is the best-tested upgrade path,
1692 and has the highest probability of being successful. Please try this
1693 approach if you encounter problems with a major version upgrade. Since
1694 the stable 4.x branch point, one has generally been able to upgade from
1695 anywhere in the most recent stable branch to head / current (or even the
1696 last couple of stable branches). See the top of this file when there's
1699 When upgrading a live system, having a root shell around before
1700 installing anything can help undo problems. Not having a root shell
1701 around can lead to problems if pam has changed too much from your
1702 starting point to allow continued authentication after the upgrade.
1704 This file should be read as a log of events. When a later event changes
1705 information of a prior event, the prior event should not be deleted.
1706 Instead, a pointer to the entry with the new information should be
1707 placed in the old entry. Readers of this file should also sanity check
1708 older entries before relying on them blindly. Authors of new entries
1709 should write them with this in mind.
1713 When upgrading the boot ZFS pool to a new version, always follow
1716 1.) recompile and reinstall the ZFS boot loader and boot block
1717 (this is part of "make buildworld" and "make installworld")
1719 2.) update the ZFS boot block on your boot drive
1721 The following example updates the ZFS boot block on the first
1722 partition (freebsd-boot) of a GPT partitioned drive ada0:
1723 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1725 Non-boot pools do not need these updates.
1729 If you are updating from a prior version of FreeBSD (even one just
1730 a few days old), you should follow this procedure. It is the most
1731 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1733 make kernel-toolchain
1734 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1735 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1737 To test a kernel once
1738 ---------------------
1739 If you just want to boot a kernel once (because you are not sure
1740 if it works, or if you want to boot a known bad kernel to provide
1741 debugging information) run
1742 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1743 nextboot -k testkernel
1745 To just build a kernel when you know that it won't mess you up
1746 --------------------------------------------------------------
1747 This assumes you are already running a CURRENT system. Replace
1748 ${arch} with the architecture of your machine (e.g. "i386",
1749 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1751 cd src/sys/${arch}/conf
1752 config KERNEL_NAME_HERE
1753 cd ../compile/KERNEL_NAME_HERE
1758 If this fails, go to the "To build a kernel" section.
1760 To rebuild everything and install it on the current system.
1761 -----------------------------------------------------------
1762 # Note: sometimes if you are running current you gotta do more than
1763 # is listed here if you are upgrading from a really old current.
1765 <make sure you have good level 0 dumps>
1767 make kernel KERNCONF=YOUR_KERNEL_HERE
1769 <reboot in single user> [3]
1776 To cross-install current onto a separate partition
1777 --------------------------------------------------
1778 # In this approach we use a separate partition to hold
1779 # current's root, 'usr', and 'var' directories. A partition
1780 # holding "/", "/usr" and "/var" should be about 2GB in
1783 <make sure you have good level 0 dumps>
1786 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1787 <maybe newfs current's root partition>
1788 <mount current's root partition on directory ${CURRENT_ROOT}>
1789 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1790 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1791 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1792 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1793 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1794 <reboot into current>
1795 <do a "native" rebuild/install as described in the previous section>
1796 <maybe install compatibility libraries from ports/misc/compat*>
1800 To upgrade in-place from stable to current
1801 ----------------------------------------------
1802 <make sure you have good level 0 dumps>
1804 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1806 <reboot in single user> [3]
1813 Make sure that you've read the UPDATING file to understand the
1814 tweaks to various things you need. At this point in the life
1815 cycle of current, things change often and you are on your own
1816 to cope. The defaults can also change, so please read ALL of
1817 the UPDATING entries.
1819 Also, if you are tracking -current, you must be subscribed to
1820 freebsd-current@freebsd.org. Make sure that before you update
1821 your sources that you have read and understood all the recent
1822 messages there. If in doubt, please track -stable which has
1823 much fewer pitfalls.
1825 [1] If you have third party modules, such as vmware, you
1826 should disable them at this point so they don't crash your
1829 [3] From the bootblocks, boot -s, and then do
1834 adjkerntz -i # if CMOS is wall time
1835 Also, when doing a major release upgrade, it is required that
1836 you boot into single user mode to do the installworld.
1838 [4] Note: This step is non-optional. Failure to do this step
1839 can result in a significant reduction in the functionality of the
1840 system. Attempting to do it by hand is not recommended and those
1841 that pursue this avenue should read this file carefully, as well
1842 as the archives of freebsd-current and freebsd-hackers mailing lists
1843 for potential gotchas. The -U option is also useful to consider.
1844 See mergemaster(8) for more information.
1846 [5] Usually this step is a noop. However, from time to time
1847 you may need to do this if you get unknown user in the following
1848 step. It never hurts to do it all the time. You may need to
1849 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1850 install) after the buildworld before this step if you last updated
1851 from current before 20130425 or from -stable before 20130430.
1853 [6] This only deletes old files and directories. Old libraries
1854 can be deleted by "make delete-old-libs", but you have to make
1855 sure that no program is using those libraries anymore.
1857 [8] In order to have a kernel that can run the 4.x binaries needed to
1858 do an installworld, you must include the COMPAT_FREEBSD4 option in
1859 your kernel. Failure to do so may leave you with a system that is
1860 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1861 required to run the 5.x binaries on more recent kernels. And so on
1862 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1864 Make sure that you merge any new devices from GENERIC since the
1865 last time you updated your kernel config file.
1867 [9] When checking out sources, you must include the -P flag to have
1868 cvs prune empty directories.
1870 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1871 "?=" instead of the "=" assignment operator, so that buildworld can
1872 override the CPUTYPE if it needs to.
1874 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1875 not on the command line, or in /etc/make.conf. buildworld will
1876 warn if it is improperly defined.
1879 This file contains a list, in reverse chronological order, of major
1880 breakages in tracking -current. It is not guaranteed to be a complete
1881 list of such breakages, and only contains entries since September 23, 2011.
1882 If you need to see UPDATING entries from before that date, you will need
1883 to fetch an UPDATING file from an older FreeBSD release.
1885 Copyright information:
1887 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1889 Redistribution, publication, translation and use, with or without
1890 modification, in full or in part, in any form or format of this
1891 document are permitted without further permission from the author.
1893 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1894 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1895 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1896 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1897 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1898 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1899 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1900 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1901 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1902 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1903 POSSIBILITY OF SUCH DAMAGE.
1905 Contact Warner Losh if you have any questions about your use of