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/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
20 The RETPOLINE option produces non-functional ifunc-using binaries
21 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
22 Once Clang 8 is merged it may be enabled again.
25 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
26 7.0.1. Please see the 20141231 entry below for information about
27 prerequisites and upgrading, if you are not already using clang 3.5.0
31 Iflib is no longer unconditionally compiled into the kernel. Drivers
32 using iflib and statically compiled into the kernel, now require
33 the 'device iflib' config option. For the same drivers loaded as
34 modules on kernels not having 'device iflib', the iflib.ko module
35 is loaded automatically.
38 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
39 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
40 servers that have vfs.nfsd.nfs_privport set will only allow mounts
41 from clients using a reserved port#. Since both the FreeBSD and Linux
42 NFSv4 clients use reserved port#s by default, this should not affect
46 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
47 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
48 it produces broken binaries when ifuncs are in use. Users needing
49 GNU ld should install the binutils port or package.
52 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
53 has been converted to a port (misc/ctm) and will be removed from
54 FreeBSD-13. A depreciation warning will be printed to stderr by
55 the ctm command, but the functionality will remain in base for all
59 The stable/12 branch has been created in subversion from head
63 Ports for the DRM modules have been simplified. Now, amd64 users should
64 just install the drm-kmod port. All others should install
67 Graphics hardware that's newer than about 2010 usually works with
68 drm-kmod. For hardware older than 2013, however, some users will need
69 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
70 than 2008 usually only works in drm-legacy-kmod. The graphics team can
71 only commit to hardware made since 2013 due to the complexity of the
72 market and difficulty to test all the older cards effectively. If you
73 have hardware supported by drm-kmod, you are strongly encouraged to use
74 that as you will get better support.
76 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
77 elsewhere, the drm and drm2 modules will be eliminated from the src base
78 soon (with a limited exception for arm). Please update to the package asap
79 and report any issues to x11@freebsd.org.
81 Generally, anybody using the drm*-kmod packages should add
82 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
83 cross-threading surprises, especially with automatic driver
84 loading from X11 startup. These will become the defaults in 13-current
88 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
89 custom kernel and module loading configuration files must be updated
90 accordingly. Moreover, interfaces previous presented as ixlvN to the
91 system are now exposed as iavfN and network configuration files must
92 be adjusted as necessary.
95 OpenSSL has been updated to version 1.1.1. This update included
96 additional various API changes througout the base system. It is
97 important to rebuild third-party software after upgrading. The value
98 of __FreeBSD_version has been bumped accordingly.
101 The legacy DRM modules and drivers have now been added to the loader's
102 module blacklist, in favor of loading them with kld_list in rc.conf(5).
103 The module blacklist may be overridden with the loader.conf(5)
104 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
108 The cam(4) based nda(4) driver will be used over nvd(4) by default on
109 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
110 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
111 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
115 Reproducible build mode is now on by default, in preparation for
116 FreeBSD 12.0. This eliminates build metadata such as the user,
117 host, and time from the kernel (and uname), unless the working tree
118 corresponds to a modified checkout from a version control system.
119 The previous behavior can be obtained by setting the /etc/src.conf
120 knob WITHOUT_REPRODUCIBLE_BUILD.
123 The Yarrow CSPRNG has been removed from the kernel as it has not been
124 supported by its designers since at least 2003. Fortuna has been the
125 default since FreeBSD-11.
128 devctl freeze/thaw have gone into the tree, the rc scripts have been
129 updated to use them and devmatch has been changed. You should update
130 kernel, userland and rc scripts all at the same time.
133 The default interpreter has been switched from 4th to Lua.
134 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
135 interpreter. If you have custom FORTH code you will need to set
136 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
137 src.conf for the build. This will create default hard links between
138 loader and loader_4th instead of loader and loader_lua, the new default.
139 If you are using UEFI it will create the proper hard link to loader.efi.
141 bhyve uses userboot.so. It remains 4th-only until some issues are solved
142 regarding coexisting with multiple versions of FreeBSD are resolved.
145 ls(1) now respects the COLORTERM environment variable used in other
146 systems and software to indicate that a colored terminal is both
147 supported and desired. If ls(1) is suddenly emitting colors, they may
148 be disabled again by either removing the unwanted COLORTERM from your
149 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
150 may not be observed in a future release.
153 The default pager for most commands has been changed to "less". To
154 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
158 The jedec_ts(4) driver has been removed. A superset of its functionality
159 is available in the jedec_dimm(4) driver, and the manpage for that
160 driver includes migration instructions. If you have "device jedec_ts"
161 in your kernel configuration file, it must be removed.
164 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
165 This should have no effect if the kernel is booted via BIOS/legacy boot.
166 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
167 has a buggy firmware that prevents a successful boot due to use of
171 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
172 support has been removed from the tree. These ports were
173 obsolete and/or known to be broken for many years.
176 loader.efi has been augmented to participate more fully in the
177 UEFI boot manager protocol. loader.efi will now look at the
178 BootXXXX environment variable to determine if a specific kernel
179 or root partition was specified. XXXX is derived from BootCurrent.
180 efibootmgr(8) manages these standard UEFI variables.
183 zfsloader's functionality has now been folded into loader.
184 zfsloader is no longer necessary once you've updated your
185 boot blocks. For a transition period, we will install a
186 hardlink for zfsloader to loader to allow a smooth transition
187 until the boot blocks can be updated (hard link because old
188 zfs boot blocks don't understand symlinks).
191 ARM64 now have efifb support, if you want to have serial console
192 on your arm64 board when an screen is connected and the bootloader
193 setup a frambuffer for us to use, just add :
197 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
198 an screen connected as the firmware will setup a framebuffer are that
199 u-boot will expose as an EFI framebuffer.
202 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
203 or take steps to update /etc/passwd before doing installworld on
204 existing systems. Do not skip the "mergemaster -Fp" step before
205 installworld, as described in the update procedures near the bottom
206 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
207 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
208 the ntp config file contain options that change file/dir locations.
209 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
210 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
211 taking steps to ensure that all required files/dirs are accessible
215 Big endian arm support has been removed.
218 The static environment setup in kernel configs is no longer mutually
219 exclusive with the loader(8) environment by default. In order to
220 restore the previous default behavior of disabling the loader(8)
221 environment if a static environment is present, you must specify
222 loader_env.disabled=1 in the static environment.
225 The ABI of syscalls used by management tools like sockstat and
226 netstat has been broken to allow 32-bit binaries to work on
227 64-bit kernels without modification. These programs will need
228 to match the kernel in order to function. External programs may
229 require minor modifications to accommodate a change of type in
230 structures from pointers to 64-bit virtual addresses.
233 On i386 and amd64 atomics are now inlined. Out of tree modules using
234 atomics will need to be rebuilt.
237 The '%I' format in the kern.corefile sysctl limits the number of
238 core files that a process can generate to the number stored in the
239 debug.ncores sysctl. The '%I' format is replaced by the single digit
240 index. Previously, if all indexes were taken the kernel would overwrite
241 only a core file with the highest index in a filename.
242 Currently the system will create a new core file if there is a free
243 index or if all slots are taken it will overwrite the oldest one.
246 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
247 6.0.1. Please see the 20141231 entry below for information about
248 prerequisites and upgrading, if you are not already using clang 3.5.0
252 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
253 needed to be changed to work with it. This change was made with r335763
254 and requires a mergemaster / etcupdate / etc to update the installed file.
257 r334930 changed the interface between the NFS modules, so they all
258 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
261 As of r334391 lld is the default amd64 system linker; it is installed
262 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
266 The kernel / userland interface for devinfo changed, so you'll
267 need a new kernel and userland as a pair for it to work (rebuilding
268 lib/libdevinfo is all that's required). devinfo and devmatch will
269 not work, but everything else will when there's a mismatch.
272 The on-disk format for hwpmc callchain records has changed to include
273 threadid corresponding to a given record. This changes the field offsets
274 and thus requires that libpmcstat be rebuilt before using a kernel
278 The vxge(4) driver has been removed. This driver was introduced into
279 HEAD one week before the Exar left the Ethernet market and is not
280 known to be used. If you have device vxge in your kernel config file
284 The amd64 kernel now requires a ld that supports ifunc to produce a
285 working kernel, either lld or a newer binutils. lld is built by default
286 on amd64, and the 'buildkernel' target uses it automatically. However,
287 it is not the default linker, so building the kernel the traditional
288 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
289 binutils port/package). lld will soon be default, and this requirement
292 NOTE: As of r334391 lld is the default system linker on amd64, and no
293 workaround is necessary.
296 The nxge(4) driver has been removed. This driver was for PCI-X 10g
297 cards made by s2io/Neterion. The company was aquired by Exar and
298 no longer sells or supports Ethernet products. If you have device
299 nxge in your kernel config file it must be removed.
302 The tz database (tzdb) has been updated to 2018e. This version more
303 correctly models time stamps in time zones with negative DST such as
304 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
305 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
306 time zone abbreviations and the tm_isdst flag.
309 The ixgb(4) driver has been removed. This driver was for an early and
310 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
311 quickly shifted to the long lived ixgbe family. If you have device
312 ixgb in your kernel config file it must be removed.
315 The lmc(4) driver has been removed. This was a WAN interface
316 card that was already reportedly rare in 2003, and had an ambiguous
317 license. If you have device lmc in your kernel config file it must
321 Support for Arcnet networks has been removed. If you have device
322 arcnet or device cm in your kernel config file they must be
326 Support for FDDI networks has been removed. If you have device
327 fddi or device fpa in your kernel config file they must be
331 In addition to supporting RFC 3164 formatted messages, the
332 syslogd(8) service is now capable of parsing RFC 5424 formatted
333 log messages. The main benefit of using RFC 5424 is that clients
334 may now send log messages with timestamps containing year numbers,
335 microseconds and time zone offsets.
337 Similarly, the syslog(3) C library function has been altered to
338 send RFC 5424 formatted messages to the local system logging
339 daemon. On systems using syslogd(8), this change should have no
340 negative impact, as long as syslogd(8) and the C library are
341 updated at the same time. On systems using a different system
342 logging daemon, it may be necessary to make configuration
343 adjustments, depending on the software used.
345 When using syslog-ng, add the 'syslog-protocol' flag to local
346 input sources to enable parsing of RFC 5424 formatted messages:
349 unix-dgram("/var/run/log" flags(syslog-protocol));
352 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
353 of the 'imuxsock' module to let messages be processed by the
354 regular RFC 3164/5424 parsing pipeline:
356 module(load="imuxsock" SysSock.UseSpecialParser="off")
358 Do note that these changes only affect communication between local
359 applications and syslogd(8). The format that syslogd(8) uses to
360 store messages on disk or forward messages to other systems
361 remains unchanged. syslogd(8) still uses RFC 3164 for these
362 purposes. Options to customize this behaviour will be added in the
363 future. Utilities that process log files stored in /var/log are
364 thus expected to continue to function as before.
366 __FreeBSD_version has been incremented to 1200061 to denote this
370 Support for token ring networks has been removed. If you
371 have "device token" in your kernel config you should remove
372 it. No device drivers supported token ring.
375 makefs was modified to be able to tag ISO9660 El Torito boot catalog
376 entries as EFI instead of overloading the i386 tag as done previously.
377 The amd64 mkisoimages.sh script used to build amd64 ISO images for
378 release was updated to use this. This may mean that makefs must be
379 updated before "make cdrom" can be run in the release directory. This
380 should be as simple as:
382 $ cd $SRCDIR/usr.sbin/makefs
383 $ make depend all install
386 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
387 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
388 Co-existance for the transition period will come shortly. Booting is a
389 complex environment and test coverage for Lua-enabled loaders has been
390 thin, so it would be prudent to assume it might not work and make
391 provisions for backup boot methods.
394 devmatch functionality has been turned on in devd. It will automatically
395 load drivers for unattached devices. This may cause unexpected drivers to
396 be loaded. Please report any problems to current@ and imp@freebsd.org.
399 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
400 6.0.0. Please see the 20141231 entry below for information about
401 prerequisites and upgrading, if you are not already using clang 3.5.0
405 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
406 This means it is used to link the kernel and userland libraries and
407 executables, but is not yet installed as /usr/bin/ld by default.
409 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
410 WITHOUT_LLD_BOOTSTRAP=yes
413 On i386, pmtimer has been removed. Its functionality has been folded
414 into apm. It was a no-op on ACPI in current for a while now (but was still
415 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
416 from kernel config files.
419 The use of RSS hash from the network card aka flowid has been
420 disabled by default for lagg(4) as it's currently incompatible with
421 the lacp and loadbalance protocols.
423 This can be re-enabled by setting the following in loader.conf:
424 net.link.lagg.default_use_flowid="1"
427 The SW_WATCHDOG option is no longer necessary to enable the
428 hardclock-based software watchdog if no hardware watchdog is
429 configured. As before, SW_WATCHDOG will cause the software
430 watchdog to be enabled even if a hardware watchdog is configured.
433 r326887 fixes the issue described in the 20171214 UPDATING entry.
434 r326888 flips the switch back to building GELI support always.
437 r362593 broke ZFS + GELI support for reasons unknown. However,
438 it also broke ZFS support generally, so GELI has been turned off
439 by default as the lesser evil in r326857. If you boot off ZFS and/or
440 GELI, it might not be a good time to update.
443 PowerPC users must update loader(8) by rebuilding world before
444 installing a new kernel, as the protocol connecting them has
445 changed. Without the update, loader metadata will not be passed
446 successfully to the kernel and users will have to enter their
447 root partition at the kernel mountroot prompt to continue booting.
448 Newer versions of loader can boot old kernels without issue.
451 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
452 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
453 to WITH/OUT_LOADER_GELI.
456 The naive and non-compliant support of posix_fallocate(2) in ZFS
457 has been removed as of r325320. The system call now returns EINVAL
458 when used on a ZFS file. Although the new behavior complies with the
459 standard, some consumers are not prepared to cope with it.
460 One known victim is lld prior to r325420.
463 Building in a FreeBSD src checkout will automatically create object
464 directories now rather than store files in the current directory if
465 'make obj' was not ran. Calling 'make obj' is no longer necessary.
466 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
467 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
471 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
472 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
473 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
474 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
475 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
476 The UNIFIED_OBJDIR option is a transitional feature that will be
477 removed for 12.0 release; please migrate to the new format for any
478 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
479 than hardcoding paths.
482 The native-xtools target no longer installs the files by default to the
483 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
484 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
487 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
488 options are changing from controlling the build if defined / undefined
489 to controlling the build with explicit 'yes' or 'no' values. They will
490 shift to WITH/WITHOUT options to match other options in the system.
493 libstand has turned into a private library for sys/boot use only.
494 It is no longer supported as a public interface outside of sys/boot.
497 The arm port has split armv6 into armv6 and armv7. armv7 is now
498 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
499 and are running a kernel from before r324363, you will need to add
500 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
503 When building multiple kernels using KERNCONF, non-existent KERNCONF
504 files will produce an error and buildkernel will fail. Previously
505 missing KERNCONF files silently failed giving no indication as to
506 why, only to subsequently discover during installkernel that the
507 desired kernel was never built in the first place.
510 The default serial number format for CTL LUNs has changed. This will
511 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
512 or iSCSI clients care about their LUNs' serial numbers. Users who
513 require serial number stability should hardcode serial numbers in
517 For 32-bit arm compiled for hard-float support, soft-floating point
518 binaries now always get their shared libraries from
519 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
520 /usr/libsoft also existed). Only users with a hard-float ld.so, but
521 soft-float everything else should be affected.
524 The geli password typed at boot is now hidden. To restore the previous
525 behavior, see geli(8) for configuration options.
528 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
529 sysctl values. Minor nit, but requires a rebuild of both world/kernel
533 "make check" behavior (made in ^/head@r295380) has been changed to
534 execute from a limited sandbox, as opposed to executing from
538 - The "beforecheck" and "aftercheck" targets are now specified.
539 - ${CHECKDIR} (added in commit noted above) has been removed.
540 - Legacy behavior can be enabled by setting
541 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
543 If the limited sandbox mode is enabled, "make check" will execute
544 "make distribution", then install, execute the tests, and clean up the
545 sandbox if successful.
547 The "make distribution" and "make install" targets are typically run as
548 root to set appropriate permissions and ownership at installation time.
549 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
550 environment if executing "make check" with limited sandbox mode using
551 an unprivileged user.
554 Since the switch to GPT disk labels, fsck for UFS/FFS has been
555 unable to automatically find alternate superblocks. As of r322297,
556 the information needed to find alternate superblocks has been
557 moved to the end of the area reserved for the boot block.
558 Filesystems created with a newfs of this vintage or later
559 will create the recovery information. If you have a filesystem
560 created prior to this change and wish to have a recovery block
561 created for your filesystem, you can do so by running fsck in
562 foreground mode (i.e., do not use the -p or -y options). As it
563 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
564 to which you should answer yes.
567 As of r321665, an NFSv4 server configuration that services
568 Kerberos mounts or clients that do not support the uid/gid in
569 owner/owner_group string capability, must explicitly enable
570 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
571 machine's /etc/rc.conf file.
574 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
575 Please see the 20141231 entry below for information about prerequisites
576 and upgrading, if you are not already using clang 3.5.0 or higher.
579 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
580 r-commands (rlogin, rsh, etc.) to be built with the base system.
583 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
584 a very major ABI incompatible change, so users of FreeBSD/powerpc must
585 be careful when performing source upgrades. It is best to run
586 'make installworld' from an alternate root system, either a live
587 CD/memory stick, or a temporary root partition. Additionally, all ports
588 must be recompiled. powerpc64 is largely unaffected, except in the case
589 of 32-bit compatibility. All 32-bit binaries will be affected.
592 Forward compatibility for the "ino64" project have been committed. This
593 will allow most new binaries to run on older kernels in a limited
594 fashion. This prevents many of the common foot-shooting actions in the
595 upgrade as well as the limited ability to roll back the kernel across
596 the ino64 upgrade. Complicated use cases may not work properly, though
597 enough simpler ones work to allow recovery in most situations.
600 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
601 if you require the GPL compiler.
604 The internal ABI used for communication between the NFS kernel modules
605 was changed by r320085, so __FreeBSD_version was bumped to
606 ensure all the NFS related modules are updated together.
609 The ABI of struct event was changed by extending the data
610 member to 64bit and adding ext fields. For upgrade, same
611 precautions as for the entry 20170523 "ino64" must be
615 The GNU roff toolchain has been removed from base. To render manpages
616 which are not supported by mandoc(1), man(1) can fallback on GNU roff
617 from ports (and recommends to install it).
618 To render roff(7) documents, consider using GNU roff from ports or the
619 heirloom doctools roff toolchain from ports via pkg install groff or
620 via pkg install heirloom-doctools.
623 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
624 smaller runtime footprint builds. This is useful for embedded systems
625 which only require one chipset support.
627 If you load it as a module, make sure this is in /boot/loader.conf:
631 This will load the HAL, all chip/RF backends and if_ath_pci.
632 If you have if_ath_pci in /boot/loader.conf, ensure it is after
633 if_ath or it will not load any HAL chipset support.
635 If you want to selectively load things (eg on ye cheape ARM/MIPS
636 platforms where RAM is at a premium) you should:
639 * load the chip modules in question
640 * load ath_rate, ath_dfs
642 * load if_ath_pci and/or if_ath_ahb depending upon your particular
643 bus bind type - this is where probe/attach is done.
645 For further comments/feedback, poke adrian@ .
648 The "ino64" 64-bit inode project has been committed, which extends
649 a number of types to 64 bits. Upgrading in place requires care and
650 adherence to the documented upgrade procedure.
652 If using a custom kernel configuration ensure that the
653 COMPAT_FREEBSD11 option is included (as during the upgrade the
654 system will be running the ino64 kernel with the existing world).
656 For the safest in-place upgrade begin by removing previous build
657 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
658 full procedure documented below under the heading "To rebuild
659 everything and install it on the current system." Specifically,
660 a reboot is required after installing the new kernel before
664 The NATM framework including the en(4), fatm(4), hatm(4), and
665 patm(4) devices has been removed. Consumers should plan a
666 migration before the end-of-life date for FreeBSD 11.
669 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
670 diff has not been implemented, if those are needed a newer version of
671 GNU diff is available via the diffutils package under the gdiff name.
674 As of r316810 for ipfilter, keep frags is no longer assumed when
675 keep state is specified in a rule. r316810 aligns ipfilter with
676 documentation in man pages separating keep frags from keep state.
677 This allows keep state to be specified without forcing keep frags
678 and allows keep frags to be specified independently of keep state.
679 To maintain previous behaviour, also specify keep frags with
680 keep state (as documented in ipf.conf.5).
683 arm64 builds now use the base system LLD 4.0.0 linker by default,
684 instead of requiring that the aarch64-binutils port or package be
685 installed. To continue using aarch64-binutils, set
686 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
689 The UDP optimization in entry 20160818 that added the sysctl
690 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
691 packets will no longer be treated as L3 broadcast packets.
694 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
695 use any explicitly assigned loopback address available in the jail
696 instead of using the first assigned address of the jail.
699 The ctl.ko module no longer implements the iSCSI target frontend:
700 cfiscsi.ko does instead.
702 If building cfiscsi.ko as a kernel module, the module can be loaded
703 via one of the following methods:
704 - `cfiscsi_load="YES"` in loader.conf(5).
705 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
706 - ctladm(8)/ctld(8), when compiled with iSCSI support
707 (`WITH_ISCSI=yes` in src.conf(5))
709 Please see cfiscsi(4) for more details.
712 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
713 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
714 same source (previously, the dependency of mmcsd.ko on mmc.ko was
715 missing, but mmcsd.ko now will refuse to load if it is incompatible
719 The syntax of ipfw(8) named states was changed to avoid ambiguity.
720 If you have used named states in the firewall rules, you need to modify
721 them after installworld and before rebooting. Now named states must
722 be prefixed with colon.
725 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
726 removed as the userland we provide cannot use them. The KMS version
727 (sys/dev/drm2) supports the same hardware.
730 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
731 Please see the 20141231 entry below for information about prerequisites
732 and upgrading, if you are not already using clang 3.5.0 or higher.
735 The code that provides support for ZFS .zfs/ directory functionality
736 has been reimplemented. It's not possible now to create a snapshot
737 by mkdir under .zfs/snapshot/. That should be the only user visible
741 EISA bus support has been removed. The WITH_EISA option is no longer
745 MCA bus support has been removed.
748 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
749 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
752 The EM_MULTIQUEUE kernel configuration option is deprecated now that
753 the em(4) driver conforms to iflib specifications.
756 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
757 IFLIB. If you have a custom kernel configuration that excludes em(4)
758 but you use igb(4), you need to re-add em(4) to your custom configuration.
761 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
762 Please see the 20141231 entry below for information about prerequisites
763 and upgrading, if you are not already using clang 3.5.0 or higher.
766 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
767 Please see the 20141231 entry below for information about prerequisites
768 and upgrading, if you are not already using clang 3.5.0 or higher.
771 The layout of the pmap structure has changed for powerpc to put the pmap
772 statistics at the front for all CPU variations. libkvm(3) and all tools
773 that link against it need to be recompiled.
776 isl(4) and cyapa(4) drivers now require a new driver,
777 chromebook_platform(4), to work properly on Chromebook-class hardware.
778 On other types of hardware the drivers may need to be configured using
779 device hints. Please see the corresponding manual pages for details.
782 The urtwn(4) driver was merged into rtwn(4) and now consists of
783 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
785 Also, firmware for RTL8188CE was renamed due to possible name
786 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
789 GNU rcs has been removed from base. It is available as packages:
790 - rcs: Latest GPLv3 GNU rcs version.
791 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
795 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
796 modules now requires that the kernel configuration contain the
797 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
800 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
801 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
804 Relocatable object files with the extension of .So have been renamed
805 to use an extension of .pico instead. The purpose of this change is
806 to avoid a name clash with shared libraries on case-insensitive file
807 systems. On those file systems, foo.So is the same file as foo.so.
810 GNU rcs has been turned off by default. It can (temporarily) be built
811 again by adding WITH_RCS knob in src.conf.
812 Otherwise, GNU rcs is available from packages:
813 - rcs: Latest GPLv3 GNU rcs version.
814 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
817 The backup_uses_rcs functionality has been removed from rc.subr.
820 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
821 two separate components, QUEUE_MACRO_DEBUG_TRACE and
822 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
823 QUEUE_MACRO_DEBUG behavior.
826 r304787 changed some ioctl interfaces between the iSCSI userspace
827 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
828 rebuilt to work with new kernels. __FreeBSD_version has been bumped
832 The UDP receive code has been updated to only treat incoming UDP
833 packets that were addressed to an L2 broadcast address as L3
834 broadcast packets. It is not expected that this will affect any
835 standards-conforming UDP application. The new behaviour can be
836 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
840 Remove the openbsd_poll system call.
841 __FreeBSD_version has been bumped because of this.
844 The stable/11 branch has been created from head@r302406.
847 The libc stub for the pipe(2) system call has been replaced with
848 a wrapper that calls the pipe2(2) system call and the pipe(2)
849 system call is now only implemented by the kernels that include
850 "options COMPAT_FREEBSD10" in their config file (this is the
851 default). Users should ensure that this option is enabled in
852 their kernel or upgrade userspace to r302092 before upgrading their
856 CAM will now strip leading spaces from SCSI disks' serial numbers.
857 This will affect users who create UFS filesystems on SCSI disks using
858 those disk's diskid device nodes. For example, if /etc/fstab
859 previously contained a line like
860 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
861 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
862 transforms like gmirror may also be affected. ZFS users should
866 The bitstring(3) API has been updated with new functionality and
867 improved performance. But it is binary-incompatible with the old API.
868 Objects built with the new headers may not be linked against objects
869 built with the old headers.
872 The brk and sbrk functions have been removed from libc on arm64.
873 Binutils from ports has been updated to not link to these
874 functions and should be updated to the latest version before
875 installing a new libc.
878 The armv6 port now defaults to hard float ABI. Limited support
879 for running both hardfloat and soft float on the same system
880 is available using the libraries installed with -DWITH_LIBSOFT.
881 This has only been tested as an upgrade path for installworld
882 and packages may fail or need manual intervention to run. New
883 packages will be needed.
885 To update an existing self-hosted armv6hf system, you must add
886 TARGET_ARCH=armv6 on the make command line for both the build
887 and the install steps.
890 Kernel modules compiled outside of a kernel build now default to
891 installing to /boot/modules instead of /boot/kernel. Many kernel
892 modules built this way (such as those in ports) already overrode
893 KMODDIR explicitly to install into /boot/modules. However,
894 manually building and installing a module from /sys/modules will
895 now install to /boot/modules instead of /boot/kernel.
898 The CAM I/O scheduler has been committed to the kernel. There should be
899 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
900 list of known rogues that claim support for this but actually corrupt
901 data is believed to be complete, be on the lookout for data
902 corruption. The known rogue list is believed to be complete:
904 o Crucial MX100, M550 drives with MU01 firmware.
905 o Micron M510 and M550 drives with MU01 firmware.
906 o Micron M500 prior to MU07 firmware
907 o Samsung 830, 840, and 850 all firmwares
908 o FCCT M500 all firmwares
910 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
911 with working NCQ TRIM. For Micron branded drives, see your sales rep for
912 updated firmware. Black listed drives will work correctly because these
913 drives work correctly so long as no NCQ TRIMs are sent to them. Given
914 this list is the same as found in Linux, it's believed there are no
915 other rogues in the market place. All other models from the above
918 To be safe, if you are at all concerned, you can quirk each of your
919 drives to prevent NCQ from being sent by setting:
920 kern.cam.ada.X.quirks="0x2"
921 in loader.conf. If the drive requires the 4k sector quirk, set the
925 The FAST_DEPEND build option has been removed and its functionality is
926 now the one true way. The old mkdep(1) style of 'make depend' has
927 been removed. See 20160311 for further details.
930 Resource range types have grown from unsigned long to uintmax_t. All
931 drivers, and anything using libdevinfo, need to be recompiled.
934 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
935 builds. It no longer runs mkdep(1) during 'make depend', and the
936 'make depend' stage can safely be skipped now as it is auto ran
937 when building 'make all' and will generate all SRCS and DPSRCS before
938 building anything else. Dependencies are gathered at compile time with
939 -MF flags kept in separate .depend files per object file. Users should
940 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
944 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
945 kernel modules. Therefore, if you load any kernel modules at boot time,
946 please install the boot loaders after you install the kernel, but before
950 make buildkernel KERNCONF=YOUR_KERNEL_HERE
951 make installkernel KERNCONF=YOUR_KERNEL_HERE
952 make -C sys/boot install
953 <reboot in single user>
955 Then follow the usual steps, described in the General Notes section,
959 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
960 see the 20141231 entry below for information about prerequisites and
961 upgrading, if you are not already using clang 3.5.0 or higher.
964 The AIO subsystem is now a standard part of the kernel. The
965 VFS_AIO kernel option and aio.ko kernel module have been removed.
966 Due to stability concerns, asynchronous I/O requests are only
967 permitted on sockets and raw disks by default. To enable
968 asynchronous I/O requests on all file types, set the
969 vfs.aio.enable_unsafe sysctl to a non-zero value.
972 The ELF object manipulation tool objcopy is now provided by the
973 ELF Tool Chain project rather than by GNU binutils. It should be a
974 drop-in replacement, with the addition of arm64 support. The
975 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
976 to obtain the GNU version if necessary.
979 Building ZFS pools on top of zvols is prohibited by default. That
980 feature has never worked safely; it's always been prone to deadlocks.
981 Using a zvol as the backing store for a VM guest's virtual disk will
982 still work, even if the guest is using ZFS. Legacy behavior can be
983 restored by setting vfs.zfs.vol.recursive=1.
986 The NONE and HPN patches has been removed from OpenSSH. They are
987 still available in the security/openssh-portable port.
990 With the addition of ypldap(8), a new _ypldap user is now required
991 during installworld. "mergemaster -p" can be used to add the user
992 prior to installworld, as documented in the handbook.
995 The tftp loader (pxeboot) now uses the option root-path directive. As a
996 consequence it no longer looks for a pxeboot.4th file on the tftp
997 server. Instead it uses the regular /boot infrastructure as with the
1001 The code to start recording plug and play data into the modules has
1002 been committed. While the old tools will properly build a new kernel,
1003 a number of warnings about "unknown metadata record 4" will be produced
1004 for an older kldxref. To avoid such warnings, make sure to rebuild
1005 the kernel toolchain (or world). Make sure that you have r292078 or
1006 later when trying to build 292077 or later before rebuilding.
1009 Debug data files are now built by default with 'make buildworld' and
1010 installed with 'make installworld'. This facilitates debugging but
1011 requires more disk space both during the build and for the installed
1012 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1016 r291527 changed the internal interface between the nfsd.ko and
1017 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1018 __FreeBSD_version has been bumped because of this.
1021 Add support for unicode collation strings leads to a change of
1022 order of files listed by ls(1) for example. To get back to the old
1023 behaviour, set LC_COLLATE environment variable to "C".
1025 Databases administrators will need to reindex their databases given
1026 collation results will be different.
1028 Due to a bug in install(1) it is recommended to remove the ancient
1029 locales before running make installworld.
1031 rm -rf /usr/share/locale/*
1034 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1035 libcrypto.so.7 or libssl.so.7 must be recompiled.
1038 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1039 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1040 should be replaced with isp_2400 and isp_2500 modules respectively.
1043 The build previously allowed using 'make -n' to not recurse into
1044 sub-directories while showing what commands would be executed, and
1045 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1046 and 'make -N' will not.
1049 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1050 and etcupdate will now use this file. A custom sendmail.cf is now
1051 updated via this mechanism rather than via installworld. If you had
1052 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1053 want to remove the exclusion or change it to "always install".
1054 /etc/mail/sendmail.cf is now managed the same way regardless of
1055 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1056 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1059 Compatibility shims for legacy ATA device names have been removed.
1060 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1061 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1062 environment variables, /dev/ad* and /dev/ar* symbolic links.
1065 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1066 Please see the 20141231 entry below for information about prerequisites
1067 and upgrading, if you are not already using clang 3.5.0 or higher.
1070 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1071 and renamed from .symbols to .debug. This reduces the size requirements
1072 on the boot partition or file system and provides consistency with
1073 userland debug files.
1075 When using the supported kernel installation method the
1076 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1077 as is done with /boot/kernel.
1079 Developers wishing to maintain the historical behavior of installing
1080 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1083 The wireless drivers had undergone changes that remove the 'parent
1084 interface' from the ifconfig -l output. The rc.d network scripts
1085 used to check presence of a parent interface in the list, so old
1086 scripts would fail to start wireless networking. Thus, etcupdate(3)
1087 or mergemaster(8) run is required after kernel update, to update your
1088 rc.d scripts in /etc.
1091 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1092 These configurations are now automatically interpreted as
1093 'scrub fragment reassemble'.
1096 Kernel-loadable modules for the random(4) device are back. To use
1097 them, the kernel must have
1100 options RANDOM_LOADABLE
1102 kldload(8) can then be used to load random_fortuna.ko
1103 or random_yarrow.ko. Please note that due to the indirect
1104 function calls that the loadable modules need to provide,
1105 the build-in variants will be slightly more efficient.
1107 The random(4) kernel option RANDOM_DUMMY has been retired due to
1108 unpopularity. It was not all that useful anyway.
1111 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1112 Control over building the ELF Tool Chain tools is now provided by
1113 the WITHOUT_TOOLCHAIN knob.
1116 The polarity of Pulse Per Second (PPS) capture events with the
1117 uart(4) driver has been corrected. Prior to this change the PPS
1118 "assert" event corresponded to the trailing edge of a positive PPS
1119 pulse and the "clear" event was the leading edge of the next pulse.
1121 As the width of a PPS pulse in a typical GPS receiver is on the
1122 order of 1 millisecond, most users will not notice any significant
1123 difference with this change.
1125 Anyone who has compensated for the historical polarity reversal by
1126 configuring a negative offset equal to the pulse width will need to
1127 remove that workaround.
1130 The default group assigned to /dev/dri entries has been changed
1131 from 'wheel' to 'video' with the id of '44'. If you want to have
1132 access to the dri devices please add yourself to the video group
1135 # pw groupmod video -m $USER
1138 The menu.rc and loader.rc files will now be replaced during
1139 upgrades. Please migrate local changes to menu.rc.local and
1140 loader.rc.local instead.
1143 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1144 strings and strip have been removed. The src.conf(5) knob
1145 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1148 As ZFS requires more kernel stack pages than is the default on some
1149 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1150 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1152 Please consider using 'options KSTACK_PAGES=X' where X is greater
1153 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1156 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1157 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1158 default, i.e., they will not contain "::". For example, instead
1159 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1160 to have a more specific match, such as different map entries for
1161 IPv6:0:0 vs IPv6:0. This change requires that configuration
1162 data (including maps, files, classes, custom ruleset, etc.) must
1163 use the same format, so make certain such configuration data is
1164 upgrading. As a very simple check search for patterns like
1165 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1166 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1167 the cf option UseCompressedIPv6Addresses.
1170 The default kernel entropy-processing algorithm is now
1171 Fortuna, replacing Yarrow.
1173 Assuming you have 'device random' in your kernel config
1174 file, the configurations allow a kernel option to override
1175 this default. You may choose *ONE* of:
1177 options RANDOM_YARROW # Legacy /dev/random algorithm.
1178 options RANDOM_DUMMY # Blocking-only driver.
1180 If you have neither, you get Fortuna. For most people,
1181 read no further, Fortuna will give a /dev/random that works
1182 like it always used to, and the difference will be irrelevant.
1184 If you remove 'device random', you get *NO* kernel-processed
1185 entropy at all. This may be acceptable to folks building
1186 embedded systems, but has complications. Carry on reading,
1187 and it is assumed you know what you need.
1189 *PLEASE* read random(4) and random(9) if you are in the
1190 habit of tweaking kernel configs, and/or if you are a member
1191 of the embedded community, wanting specific and not-usual
1192 behaviour from your security subsystems.
1194 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1195 random', you will NOT have a functioning /dev/random, and
1196 many cryptographic features will not work, including SSH.
1197 You may also find strange behaviour from the random(3) set
1198 of library functions, in particular sranddev(3), srandomdev(3)
1199 and arc4random(3). The reason for this is that the KERN_ARND
1200 sysctl only returns entropy if it thinks it has some to
1201 share, and with RANDOM_DUMMY or no 'device random' this
1205 An additional fix for the issue described in the 20150614 sendmail
1206 entry below has been committed in revision 284717.
1209 FreeBSD's old make (fmake) has been removed from the system. It is
1210 available as the devel/fmake port or via pkg install fmake.
1213 The fix for the issue described in the 20150614 sendmail entry
1214 below has been committed in revision 284436. The work
1215 around described in that entry is no longer needed unless the
1216 default setting is overridden by a confDH_PARAMETERS configuration
1217 setting of '5' or pointing to a 512 bit DH parameter file.
1220 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1221 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1222 and devel/kyua to version 0.20+ and adjust any calling code to work
1223 with Kyuafile and kyua.
1226 The import of openssl to address the FreeBSD-SA-15:10.openssl
1227 security advisory includes a change which rejects handshakes
1228 with DH parameters below 768 bits. sendmail releases prior
1229 to 8.15.2 (not yet released), defaulted to a 512 bit
1230 DH parameter setting for client connections. To work around
1231 this interoperability, sendmail can be configured to use a
1232 2048 bit DH parameter by:
1234 1. Edit /etc/mail/`hostname`.mc
1235 2. If a setting for confDH_PARAMETERS does not exist or
1236 exists and is set to a string beginning with '5',
1237 replace it with '2'.
1238 3. If a setting for confDH_PARAMETERS exists and is set to
1239 a file path, create a new file with:
1240 openssl dhparam -out /path/to/file 2048
1241 4. Rebuild the .cf file:
1242 cd /etc/mail/; make; make install
1243 5. Restart sendmail:
1244 cd /etc/mail/; make restart
1246 A sendmail patch is coming, at which time this file will be
1250 Generation of legacy formatted entries have been disabled by default
1251 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1252 entries were converted to use the new format by default when the new,
1253 machine independent format have been added and supported since FreeBSD
1256 Please see the pwd_mkdb(8) manual page for further details.
1259 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1260 20141231 entry below for information about prerequisites and upgrading,
1261 if you are not already using 3.5.0 or higher.
1264 TI platform code switched to using vendor DTS files and this update
1265 may break existing systems running on Beaglebone, Beaglebone Black,
1268 - dtb files should be regenerated/reinstalled. Filenames are the
1269 same but content is different now
1270 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1271 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1272 addressing scheme is now pin 25 on /dev/gpioc3.
1273 - Pandaboard: /etc/ttys should be updated, serial console device is
1274 now /dev/ttyu2, not /dev/ttyu0
1277 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1278 If you need the GNU extension from groff soelim(1), install groff
1279 from package: pkg install groff, or via ports: textproc/groff.
1282 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1283 defined in symlink(7); previously symlinks were silently ignored.
1286 The const qualifier has been removed from iconv(3) to comply with
1287 POSIX. The ports tree is aware of this from r384038 onwards.
1290 Libraries specified by LIBADD in Makefiles must have a corresponding
1291 DPADD_<lib> variable to ensure correct dependencies. This is now
1292 enforced in src.libnames.mk.
1295 From legacy ata(4) driver was removed support for SATA controllers
1296 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1297 Kernel modules ataahci and ataadaptec were removed completely,
1298 replaced by ahci and mvs modules respectively.
1301 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1302 the 20141231 entry below for information about prerequisites and
1303 upgrading, if you are not already using 3.5.0 or higher.
1306 The 32-bit PowerPC kernel has been changed to a position-independent
1307 executable. This can only be booted with a version of loader(8)
1308 newer than January 31, 2015, so make sure to update both world and
1309 kernel before rebooting.
1312 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1313 but before r278950, the RNG was not seeded properly. Immediately
1314 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1315 ssh keys or openssl keys) that were generated w/ a kernel from that
1316 range. This does not affect programs that directly used /dev/random
1317 or /dev/urandom. All userland uses of arc4random(3) are affected.
1320 The autofs(4) ABI was changed in order to restore binary compatibility
1321 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1322 with the new kernel.
1325 The powerpc64 kernel has been changed to a position-independent
1326 executable. This can only be booted with a new version of loader(8),
1327 so make sure to update both world and kernel before rebooting.
1330 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1331 only release, no new features have been added. Please see the 20141231
1332 entry below for information about prerequisites and upgrading, if you
1333 are not already using 3.5.0.
1336 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1337 taken from the ELF Tool Chain project rather than GNU binutils. They
1338 should be drop-in replacements, with the addition of arm64 support.
1339 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1340 binutils tools, if necessary. See 20150805 for updated information.
1343 The default Unbound configuration now enables remote control
1344 using a local socket. Users who have already enabled the
1345 local_unbound service should regenerate their configuration
1346 by running "service local_unbound setup" as root.
1349 The GNU texinfo and GNU info pages have been removed.
1350 To be able to view GNU info pages please install texinfo from ports.
1353 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1355 As of this release, a prerequisite for building clang, llvm and lldb is
1356 a C++11 capable compiler and C++11 standard library. This means that to
1357 be able to successfully build the cross-tools stage of buildworld, with
1358 clang as the bootstrap compiler, your system compiler or cross compiler
1359 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1360 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1363 On any standard FreeBSD 10.x or 11.x installation, where clang and
1364 libc++ are on by default (that is, on x86 or arm), this should work out
1367 On 9.x installations where clang is enabled by default, e.g. on x86 and
1368 powerpc, libc++ will not be enabled by default, so libc++ should be
1369 built (with clang) and installed first. If both clang and libc++ are
1370 missing, build clang first, then use it to build libc++.
1372 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1373 the instructions for 9.x above.
1375 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1376 default, and do not build clang.
1378 Many embedded systems are resource constrained, and will not be able to
1379 build clang in a reasonable time, or in some cases at all. In those
1380 cases, cross building bootable systems on amd64 is a workaround.
1382 This new version of clang introduces a number of new warnings, of which
1383 the following are most likely to appear:
1387 This warns in two cases, for both C and C++:
1388 * When the code is trying to take the absolute value of an unsigned
1389 quantity, which is effectively a no-op, and almost never what was
1390 intended. The code should be fixed, if at all possible. If you are
1391 sure that the unsigned quantity can be safely cast to signed, without
1392 loss of information or undefined behavior, you can add an explicit
1393 cast, or disable the warning.
1395 * When the code is trying to take an absolute value, but the called
1396 abs() variant is for the wrong type, which can lead to truncation.
1397 If you want to disable the warning instead of fixing the code, please
1398 make sure that truncation will not occur, or it might lead to unwanted
1401 -Wtautological-undefined-compare and
1402 -Wundefined-bool-conversion
1404 These warn when C++ code is trying to compare 'this' against NULL, while
1405 'this' should never be NULL in well-defined C++ code. However, there is
1406 some legacy (pre C++11) code out there, which actively abuses this
1407 feature, which was less strictly defined in previous C++ versions.
1409 Squid and openjdk do this, for example. The warning can be turned off
1410 for C++98 and earlier, but compiling the code in C++11 mode might result
1411 in unexpected behavior; for example, the parts of the program that are
1412 unreachable could be optimized away.
1415 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1416 kernel sources have been removed. The .h files remain, since some
1417 utilities include them. This will need to be fixed later.
1418 If "mount -t oldnfs ..." is attempted, it will fail.
1419 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1420 the utilities will report errors.
1423 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1424 directories to top level SUBDIR variable when their parent
1425 directory is included in LOCAL_DIRS. Users with build systems with
1426 such hierarchies and without SUBDIR entries in the parent
1427 directory Makefiles should add them or add the directories to
1431 faith(4) and faithd(8) have been removed from the base system. Faith
1432 has been obsolete for a very long time.
1435 vt(4), the new console driver, is enabled by default. It brings
1436 support for Unicode and double-width characters, as well as
1437 support for UEFI and integration with the KMS kernel video
1440 You may need to update your console settings in /etc/rc.conf,
1441 most probably the keymap. During boot, /etc/rc.d/syscons will
1442 indicate what you need to do.
1444 vt(4) still has issues and lacks some features compared to
1445 syscons(4). See the wiki for up-to-date information:
1446 https://wiki.freebsd.org/Newcons
1448 If you want to keep using syscons(4), you can do so by adding
1449 the following line to /boot/loader.conf:
1453 pjdfstest has been integrated into kyua as an opt-in test suite.
1454 Please see share/doc/pjdfstest/README for more details on how to
1458 gperf has been removed from the base system for architectures
1459 that use clang. Ports that require gperf will obtain it from the
1463 pjdfstest has been moved from tools/regression/pjdfstest to
1467 At svn r271982, The default linux compat kernel ABI has been adjusted
1468 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1469 update. If you wish to continue using the linux-f10 compat ports,
1470 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1471 encouraged to update their linux-compat packages to linux-c6 during
1472 their next update cycle.
1475 The ofwfb driver, used to provide a graphics console on PowerPC when
1476 using vt(4), no longer allows mmap() of all physical memory. This
1477 will prevent Xorg on PowerPC with some ATI graphics cards from
1478 initializing properly unless x11-servers/xorg-server is updated to
1482 The xdev targets have been converted to using TARGET and
1483 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1486 The default unbound configuration has been modified to address
1487 issues with reverse lookups on networks that use private
1488 address ranges. If you use the local_unbound service, run
1489 "service local_unbound setup" as root to regenerate your
1490 configuration, then "service local_unbound reload" to load the
1494 The GNU texinfo and GNU info pages are not built and installed
1495 anymore, WITH_INFO knob has been added to allow to built and install
1497 UPDATE: see 20150102 entry on texinfo's removal
1500 The GNU readline library is now an INTERNALLIB - that is, it is
1501 statically linked into consumers (GDB and variants) in the base
1502 system, and the shared library is no longer installed. The
1503 devel/readline port is available for third party software that
1507 The Itanium architecture (ia64) has been removed from the list of
1508 known architectures. This is the first step in the removal of the
1512 Commit r268115 has added NFSv4.1 server support, merged from
1513 projects/nfsv4.1-server. Since this includes changes to the
1514 internal interfaces between the NFS related modules, a full
1515 build of the kernel and modules will be necessary.
1516 __FreeBSD_version has been bumped.
1519 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1520 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1521 which differs from the behaviour controlled by this knob.)
1524 Maximal length of the serial number in CTL was increased from 16 to
1525 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1526 and ctld, need to be rebuilt to work with a new kernel.
1529 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1530 1 respectively to match the upstream numbers. They were out of
1531 sync because, when they were originally added to FreeBSD, the
1532 upstream versions were not respected. These libraries are private
1533 and not yet built by default, so renumbering them should be a
1534 non-issue. However, unclean source trees will yield broken test
1535 programs once the operator executes "make delete-old-libs" after a
1536 "make installworld".
1538 Additionally, the atf-sh binary was made private by moving it into
1539 /usr/libexec/. Already-built shell test programs will keep the
1540 path to the old binary so they will break after "make delete-old"
1543 If you are using WITH_TESTS=yes (not the default), wipe the object
1544 tree and rebuild from scratch to prevent spurious test failures.
1545 This is only needed once: the misnumbered libraries and misplaced
1546 binaries have been added to OptionalObsoleteFiles.inc so they will
1547 be removed during a clean upgrade.
1550 Clang and llvm have been upgraded to 3.4.1 release.
1553 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1554 be removed to avoid issues in the future (and has been added to
1558 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1559 past, it affected all builds that used the bsd.*.mk files. The old
1560 behavior was a bug, but people may have relied upon it. To get this
1561 behavior back, you can .include /etc/src.conf from /etc/make.conf
1562 (which is still global and isn't changed). This also changes the
1563 behavior of incremental builds inside the tree of individual
1564 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1565 Although this has survived make universe and some upgrade scenarios,
1566 other upgrade scenarios may have broken. At least one form of
1567 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1568 as well... In cases where MAKESYSPATH isn't working with this
1569 setting, you'll need to set it to the full path to your tree.
1571 One side effect of all this cleaning up is that bsd.compiler.mk
1572 is no longer implicitly included by bsd.own.mk. If you wish to
1573 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1577 The lindev device has been removed since /dev/full has been made a
1578 standard device. __FreeBSD_version has been bumped.
1581 The knob WITHOUT_VI was added to the base system, which controls
1582 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1583 in order to reorder files share/termcap and didn't build ex(1) as a
1584 build tool, so building/installing with WITH_VI is highly advised for
1585 build hosts for older releases.
1587 This issue has been fixed in stable/9 and stable/10 in r277022 and
1588 r276991, respectively.
1591 The YES_HESIOD knob has been removed. It has been obsolete for
1592 a decade. Please move to using WITH_HESIOD instead or your builds
1593 will silently lack HESIOD.
1596 The uart(4) driver has been changed with respect to its handling
1597 of the low-level console. Previously the uart(4) driver prevented
1598 any process from changing the baudrate or the CLOCAL and HUPCL
1599 control flags. By removing the restrictions, operators can make
1600 changes to the serial console port without having to reboot.
1601 However, when getty(8) is started on the serial device that is
1602 associated with the low-level console, a misconfigured terminal
1603 line in /etc/ttys will now have a real impact.
1604 Before upgrading the kernel, make sure that /etc/ttys has the
1605 serial console device configured as 3wire without baudrate to
1606 preserve the previous behaviour. E.g:
1607 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1610 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1611 to improve performance. To re-enable it, if needed, run rpcbind
1612 with command line option -W.
1615 Switched back to the GPL dtc compiler due to updates in the upstream
1616 dts files not being supported by the BSDL dtc compiler. You will need
1617 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1618 may result while building dtb files during a kernel build if you fail
1619 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1622 Clang and llvm have been upgraded to 3.4 release.
1625 The nve(4) driver has been removed. Please use the nfe(4) driver
1626 for NVIDIA nForce MCP Ethernet adapters instead.
1629 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1630 This could cause certain C++ applications using shared libraries built
1631 against the previous version of libc++ to crash. The incompatibility
1632 has now been fixed, but any C++ applications or shared libraries built
1633 between r261283 and r261801 should be recompiled.
1636 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1637 capability mode support. Please note that enabling the feature in
1638 kernel is still highly recommended.
1641 OpenSSH is now built with sandbox support, and will use sandbox as
1642 the default privilege separation method. This requires Capsicum
1643 capability mode support in kernel.
1646 The libelf and libdwarf libraries have been updated to newer
1647 versions from upstream. Shared library version numbers for
1648 these two libraries were bumped. Any ports or binaries
1649 requiring these two libraries should be recompiled.
1650 __FreeBSD_version is bumped to 1100006.
1653 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1654 instead of providing an explicit one, this would prevent such
1655 Makefile from providing its own Kyuafile in the future during
1656 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1657 intervention is needed to clean an objdir if you use NO_CLEAN:
1658 # find /usr/obj -name Kyuafile | xargs rm -f
1661 The behavior of gss_pseudo_random() for the krb5 mechanism
1662 has changed, for applications requesting a longer random string
1663 than produced by the underlying enctype's pseudo-random() function.
1664 In particular, the random string produced from a session key of
1665 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1666 be different at the 17th octet and later, after this change.
1667 The counter used in the PRF+ construction is now encoded as a
1668 big-endian integer in accordance with RFC 4402.
1669 __FreeBSD_version is bumped to 1100004.
1672 The WITHOUT_ATF build knob has been removed and its functionality
1673 has been subsumed into the more generic WITHOUT_TESTS. If you were
1674 using the former to disable the build of the ATF libraries, you
1675 should change your settings to use the latter.
1678 The default version of mtree is nmtree which is obtained from
1679 NetBSD. The output is generally the same, but may vary
1680 slightly. If you found you need identical output adding
1681 "-F freebsd9" to the command line should do the trick. For the
1682 time being, the old mtree is available as fmtree.
1685 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1686 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1687 1.1.4_8 and verify bsdyml not linked in, before running "make
1689 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1691 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1694 The stable/10 branch has been created in subversion from head
1701 Avoid using make -j when upgrading. While generally safe, there are
1702 sometimes problems using -j to upgrade. If your upgrade fails with
1703 -j, please try again without -j. From time to time in the past there
1704 have been problems using -j with buildworld and/or installworld. This
1705 is especially true when upgrading between "distant" versions (eg one
1706 that cross a major release boundary or several minor releases, or when
1707 several months have passed on the -current branch).
1709 Sometimes, obscure build problems are the result of environment
1710 poisoning. This can happen because the make utility reads its
1711 environment when searching for values for global variables. To run
1712 your build attempts in an "environmental clean room", prefix all make
1713 commands with 'env -i '. See the env(1) manual page for more details.
1715 When upgrading from one major version to another it is generally best to
1716 upgrade to the latest code in the currently installed branch first, then
1717 do an upgrade to the new branch. This is the best-tested upgrade path,
1718 and has the highest probability of being successful. Please try this
1719 approach if you encounter problems with a major version upgrade. Since
1720 the stable 4.x branch point, one has generally been able to upgrade from
1721 anywhere in the most recent stable branch to head / current (or even the
1722 last couple of stable branches). See the top of this file when there's
1725 When upgrading a live system, having a root shell around before
1726 installing anything can help undo problems. Not having a root shell
1727 around can lead to problems if pam has changed too much from your
1728 starting point to allow continued authentication after the upgrade.
1730 This file should be read as a log of events. When a later event changes
1731 information of a prior event, the prior event should not be deleted.
1732 Instead, a pointer to the entry with the new information should be
1733 placed in the old entry. Readers of this file should also sanity check
1734 older entries before relying on them blindly. Authors of new entries
1735 should write them with this in mind.
1739 When upgrading the boot ZFS pool to a new version, always follow
1742 1.) recompile and reinstall the ZFS boot loader and boot block
1743 (this is part of "make buildworld" and "make installworld")
1745 2.) update the ZFS boot block on your boot drive
1747 The following example updates the ZFS boot block on the first
1748 partition (freebsd-boot) of a GPT partitioned drive ada0:
1749 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1751 Non-boot pools do not need these updates.
1755 If you are updating from a prior version of FreeBSD (even one just
1756 a few days old), you should follow this procedure. It is the most
1757 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1759 make kernel-toolchain
1760 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1761 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1763 To test a kernel once
1764 ---------------------
1765 If you just want to boot a kernel once (because you are not sure
1766 if it works, or if you want to boot a known bad kernel to provide
1767 debugging information) run
1768 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1769 nextboot -k testkernel
1771 To rebuild everything and install it on the current system.
1772 -----------------------------------------------------------
1773 # Note: sometimes if you are running current you gotta do more than
1774 # is listed here if you are upgrading from a really old current.
1776 <make sure you have good level 0 dumps>
1778 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1779 make installkernel KERNCONF=YOUR_KERNEL_HERE
1781 <reboot in single user> [3]
1788 To cross-install current onto a separate partition
1789 --------------------------------------------------
1790 # In this approach we use a separate partition to hold
1791 # current's root, 'usr', and 'var' directories. A partition
1792 # holding "/", "/usr" and "/var" should be about 2GB in
1795 <make sure you have good level 0 dumps>
1798 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1799 <maybe newfs current's root partition>
1800 <mount current's root partition on directory ${CURRENT_ROOT}>
1801 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1802 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1803 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1804 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1805 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1806 <reboot into current>
1807 <do a "native" rebuild/install as described in the previous section>
1808 <maybe install compatibility libraries from ports/misc/compat*>
1812 To upgrade in-place from stable to current
1813 ----------------------------------------------
1814 <make sure you have good level 0 dumps>
1816 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1817 make installkernel KERNCONF=YOUR_KERNEL_HERE
1819 <reboot in single user> [3]
1826 Make sure that you've read the UPDATING file to understand the
1827 tweaks to various things you need. At this point in the life
1828 cycle of current, things change often and you are on your own
1829 to cope. The defaults can also change, so please read ALL of
1830 the UPDATING entries.
1832 Also, if you are tracking -current, you must be subscribed to
1833 freebsd-current@freebsd.org. Make sure that before you update
1834 your sources that you have read and understood all the recent
1835 messages there. If in doubt, please track -stable which has
1836 much fewer pitfalls.
1838 [1] If you have third party modules, such as vmware, you
1839 should disable them at this point so they don't crash your
1842 [3] From the bootblocks, boot -s, and then do
1847 adjkerntz -i # if CMOS is wall time
1848 Also, when doing a major release upgrade, it is required that
1849 you boot into single user mode to do the installworld.
1851 [4] Note: This step is non-optional. Failure to do this step
1852 can result in a significant reduction in the functionality of the
1853 system. Attempting to do it by hand is not recommended and those
1854 that pursue this avenue should read this file carefully, as well
1855 as the archives of freebsd-current and freebsd-hackers mailing lists
1856 for potential gotchas. The -U option is also useful to consider.
1857 See mergemaster(8) for more information.
1859 [5] Usually this step is a no-op. However, from time to time
1860 you may need to do this if you get unknown user in the following
1861 step. It never hurts to do it all the time. You may need to
1862 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1863 install) after the buildworld before this step if you last updated
1864 from current before 20130425 or from -stable before 20130430.
1866 [6] This only deletes old files and directories. Old libraries
1867 can be deleted by "make delete-old-libs", but you have to make
1868 sure that no program is using those libraries anymore.
1870 [8] In order to have a kernel that can run the 4.x binaries needed to
1871 do an installworld, you must include the COMPAT_FREEBSD4 option in
1872 your kernel. Failure to do so may leave you with a system that is
1873 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1874 required to run the 5.x binaries on more recent kernels. And so on
1875 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1877 Make sure that you merge any new devices from GENERIC since the
1878 last time you updated your kernel config file.
1880 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1881 "?=" instead of the "=" assignment operator, so that buildworld can
1882 override the CPUTYPE if it needs to.
1884 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1885 not on the command line, or in /etc/make.conf. buildworld will
1886 warn if it is improperly defined.
1889 This file contains a list, in reverse chronological order, of major
1890 breakages in tracking -current. It is not guaranteed to be a complete
1891 list of such breakages, and only contains entries since September 23, 2011.
1892 If you need to see UPDATING entries from before that date, you will need
1893 to fetch an UPDATING file from an older FreeBSD release.
1895 Copyright information:
1897 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1899 Redistribution, publication, translation and use, with or without
1900 modification, in full or in part, in any form or format of this
1901 document are permitted without further permission from the author.
1903 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1904 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1905 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1906 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1907 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1908 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1909 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1910 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1911 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1912 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1913 POSSIBILITY OF SUCH DAMAGE.
1915 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob