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 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
21 8.0.0. Please see the 20141231 entry below for information about
22 prerequisites and upgrading, if you are not already using clang 3.5.0
26 The RETPOLINE option produces non-functional ifunc-using binaries
27 with Clang 7.0.1, and has been forced off (via BROKEN_OPTIONS).
28 Once Clang 8 is merged it may be enabled again.
31 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
32 7.0.1. Please see the 20141231 entry below for information about
33 prerequisites and upgrading, if you are not already using clang 3.5.0
37 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
38 compiled into your custom kernel, add 'device xz' statement to the
42 Iflib is no longer unconditionally compiled into the kernel. Drivers
43 using iflib and statically compiled into the kernel, now require
44 the 'device iflib' config option. For the same drivers loaded as
45 modules on kernels not having 'device iflib', the iflib.ko module
46 is loaded automatically.
49 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
50 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
51 servers that have vfs.nfsd.nfs_privport set will only allow mounts
52 from clients using a reserved port#. Since both the FreeBSD and Linux
53 NFSv4 clients use reserved port#s by default, this should not affect
57 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
58 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
59 it produces broken binaries when ifuncs are in use. Users needing
60 GNU ld should install the binutils port or package.
63 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
64 has been converted to a port (misc/ctm) and will be removed from
65 FreeBSD-13. A depreciation warning will be printed to stderr by
66 the ctm command, but the functionality will remain in base for all
70 The stable/12 branch has been created in subversion from head
74 Ports for the DRM modules have been simplified. Now, amd64 users should
75 just install the drm-kmod port. All others should install
78 Graphics hardware that's newer than about 2010 usually works with
79 drm-kmod. For hardware older than 2013, however, some users will need
80 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
81 than 2008 usually only works in drm-legacy-kmod. The graphics team can
82 only commit to hardware made since 2013 due to the complexity of the
83 market and difficulty to test all the older cards effectively. If you
84 have hardware supported by drm-kmod, you are strongly encouraged to use
85 that as you will get better support.
87 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
88 elsewhere, the drm and drm2 modules will be eliminated from the src base
89 soon (with a limited exception for arm). Please update to the package asap
90 and report any issues to x11@freebsd.org.
92 Generally, anybody using the drm*-kmod packages should add
93 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
94 cross-threading surprises, especially with automatic driver
95 loading from X11 startup. These will become the defaults in 13-current
99 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
100 custom kernel and module loading configuration files must be updated
101 accordingly. Moreover, interfaces previous presented as ixlvN to the
102 system are now exposed as iavfN and network configuration files must
103 be adjusted as necessary.
106 OpenSSL has been updated to version 1.1.1. This update included
107 additional various API changes througout the base system. It is
108 important to rebuild third-party software after upgrading. The value
109 of __FreeBSD_version has been bumped accordingly.
112 The legacy DRM modules and drivers have now been added to the loader's
113 module blacklist, in favor of loading them with kld_list in rc.conf(5).
114 The module blacklist may be overridden with the loader.conf(5)
115 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
119 The cam(4) based nda(4) driver will be used over nvd(4) by default on
120 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
121 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
122 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
126 Reproducible build mode is now on by default, in preparation for
127 FreeBSD 12.0. This eliminates build metadata such as the user,
128 host, and time from the kernel (and uname), unless the working tree
129 corresponds to a modified checkout from a version control system.
130 The previous behavior can be obtained by setting the /etc/src.conf
131 knob WITHOUT_REPRODUCIBLE_BUILD.
134 The Yarrow CSPRNG has been removed from the kernel as it has not been
135 supported by its designers since at least 2003. Fortuna has been the
136 default since FreeBSD-11.
139 devctl freeze/thaw have gone into the tree, the rc scripts have been
140 updated to use them and devmatch has been changed. You should update
141 kernel, userland and rc scripts all at the same time.
144 The default interpreter has been switched from 4th to Lua.
145 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
146 interpreter. If you have custom FORTH code you will need to set
147 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
148 src.conf for the build. This will create default hard links between
149 loader and loader_4th instead of loader and loader_lua, the new default.
150 If you are using UEFI it will create the proper hard link to loader.efi.
152 bhyve uses userboot.so. It remains 4th-only until some issues are solved
153 regarding coexisting with multiple versions of FreeBSD are resolved.
156 ls(1) now respects the COLORTERM environment variable used in other
157 systems and software to indicate that a colored terminal is both
158 supported and desired. If ls(1) is suddenly emitting colors, they may
159 be disabled again by either removing the unwanted COLORTERM from your
160 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
161 may not be observed in a future release.
164 The default pager for most commands has been changed to "less". To
165 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
169 The jedec_ts(4) driver has been removed. A superset of its functionality
170 is available in the jedec_dimm(4) driver, and the manpage for that
171 driver includes migration instructions. If you have "device jedec_ts"
172 in your kernel configuration file, it must be removed.
175 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
176 This should have no effect if the kernel is booted via BIOS/legacy boot.
177 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
178 has a buggy firmware that prevents a successful boot due to use of
182 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
183 support has been removed from the tree. These ports were
184 obsolete and/or known to be broken for many years.
187 loader.efi has been augmented to participate more fully in the
188 UEFI boot manager protocol. loader.efi will now look at the
189 BootXXXX environment variable to determine if a specific kernel
190 or root partition was specified. XXXX is derived from BootCurrent.
191 efibootmgr(8) manages these standard UEFI variables.
194 zfsloader's functionality has now been folded into loader.
195 zfsloader is no longer necessary once you've updated your
196 boot blocks. For a transition period, we will install a
197 hardlink for zfsloader to loader to allow a smooth transition
198 until the boot blocks can be updated (hard link because old
199 zfs boot blocks don't understand symlinks).
202 ARM64 now have efifb support, if you want to have serial console
203 on your arm64 board when an screen is connected and the bootloader
204 setup a frambuffer for us to use, just add :
208 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
209 an screen connected as the firmware will setup a framebuffer are that
210 u-boot will expose as an EFI framebuffer.
213 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
214 or take steps to update /etc/passwd before doing installworld on
215 existing systems. Do not skip the "mergemaster -Fp" step before
216 installworld, as described in the update procedures near the bottom
217 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
218 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
219 the ntp config file contain options that change file/dir locations.
220 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
221 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
222 taking steps to ensure that all required files/dirs are accessible
226 Big endian arm support has been removed.
229 The static environment setup in kernel configs is no longer mutually
230 exclusive with the loader(8) environment by default. In order to
231 restore the previous default behavior of disabling the loader(8)
232 environment if a static environment is present, you must specify
233 loader_env.disabled=1 in the static environment.
236 The ABI of syscalls used by management tools like sockstat and
237 netstat has been broken to allow 32-bit binaries to work on
238 64-bit kernels without modification. These programs will need
239 to match the kernel in order to function. External programs may
240 require minor modifications to accommodate a change of type in
241 structures from pointers to 64-bit virtual addresses.
244 On i386 and amd64 atomics are now inlined. Out of tree modules using
245 atomics will need to be rebuilt.
248 The '%I' format in the kern.corefile sysctl limits the number of
249 core files that a process can generate to the number stored in the
250 debug.ncores sysctl. The '%I' format is replaced by the single digit
251 index. Previously, if all indexes were taken the kernel would overwrite
252 only a core file with the highest index in a filename.
253 Currently the system will create a new core file if there is a free
254 index or if all slots are taken it will overwrite the oldest one.
257 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
258 6.0.1. Please see the 20141231 entry below for information about
259 prerequisites and upgrading, if you are not already using clang 3.5.0
263 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
264 needed to be changed to work with it. This change was made with r335763
265 and requires a mergemaster / etcupdate / etc to update the installed file.
268 r334930 changed the interface between the NFS modules, so they all
269 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
272 As of r334391 lld is the default amd64 system linker; it is installed
273 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
277 The kernel / userland interface for devinfo changed, so you'll
278 need a new kernel and userland as a pair for it to work (rebuilding
279 lib/libdevinfo is all that's required). devinfo and devmatch will
280 not work, but everything else will when there's a mismatch.
283 The on-disk format for hwpmc callchain records has changed to include
284 threadid corresponding to a given record. This changes the field offsets
285 and thus requires that libpmcstat be rebuilt before using a kernel
289 The vxge(4) driver has been removed. This driver was introduced into
290 HEAD one week before the Exar left the Ethernet market and is not
291 known to be used. If you have device vxge in your kernel config file
295 The amd64 kernel now requires a ld that supports ifunc to produce a
296 working kernel, either lld or a newer binutils. lld is built by default
297 on amd64, and the 'buildkernel' target uses it automatically. However,
298 it is not the default linker, so building the kernel the traditional
299 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
300 binutils port/package). lld will soon be default, and this requirement
303 NOTE: As of r334391 lld is the default system linker on amd64, and no
304 workaround is necessary.
307 The nxge(4) driver has been removed. This driver was for PCI-X 10g
308 cards made by s2io/Neterion. The company was aquired by Exar and
309 no longer sells or supports Ethernet products. If you have device
310 nxge in your kernel config file it must be removed.
313 The tz database (tzdb) has been updated to 2018e. This version more
314 correctly models time stamps in time zones with negative DST such as
315 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
316 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
317 time zone abbreviations and the tm_isdst flag.
320 The ixgb(4) driver has been removed. This driver was for an early and
321 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
322 quickly shifted to the long lived ixgbe family. If you have device
323 ixgb in your kernel config file it must be removed.
326 The lmc(4) driver has been removed. This was a WAN interface
327 card that was already reportedly rare in 2003, and had an ambiguous
328 license. If you have device lmc in your kernel config file it must
332 Support for Arcnet networks has been removed. If you have device
333 arcnet or device cm in your kernel config file they must be
337 Support for FDDI networks has been removed. If you have device
338 fddi or device fpa in your kernel config file they must be
342 In addition to supporting RFC 3164 formatted messages, the
343 syslogd(8) service is now capable of parsing RFC 5424 formatted
344 log messages. The main benefit of using RFC 5424 is that clients
345 may now send log messages with timestamps containing year numbers,
346 microseconds and time zone offsets.
348 Similarly, the syslog(3) C library function has been altered to
349 send RFC 5424 formatted messages to the local system logging
350 daemon. On systems using syslogd(8), this change should have no
351 negative impact, as long as syslogd(8) and the C library are
352 updated at the same time. On systems using a different system
353 logging daemon, it may be necessary to make configuration
354 adjustments, depending on the software used.
356 When using syslog-ng, add the 'syslog-protocol' flag to local
357 input sources to enable parsing of RFC 5424 formatted messages:
360 unix-dgram("/var/run/log" flags(syslog-protocol));
363 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
364 of the 'imuxsock' module to let messages be processed by the
365 regular RFC 3164/5424 parsing pipeline:
367 module(load="imuxsock" SysSock.UseSpecialParser="off")
369 Do note that these changes only affect communication between local
370 applications and syslogd(8). The format that syslogd(8) uses to
371 store messages on disk or forward messages to other systems
372 remains unchanged. syslogd(8) still uses RFC 3164 for these
373 purposes. Options to customize this behaviour will be added in the
374 future. Utilities that process log files stored in /var/log are
375 thus expected to continue to function as before.
377 __FreeBSD_version has been incremented to 1200061 to denote this
381 Support for token ring networks has been removed. If you
382 have "device token" in your kernel config you should remove
383 it. No device drivers supported token ring.
386 makefs was modified to be able to tag ISO9660 El Torito boot catalog
387 entries as EFI instead of overloading the i386 tag as done previously.
388 The amd64 mkisoimages.sh script used to build amd64 ISO images for
389 release was updated to use this. This may mean that makefs must be
390 updated before "make cdrom" can be run in the release directory. This
391 should be as simple as:
393 $ cd $SRCDIR/usr.sbin/makefs
394 $ make depend all install
397 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
398 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
399 Co-existance for the transition period will come shortly. Booting is a
400 complex environment and test coverage for Lua-enabled loaders has been
401 thin, so it would be prudent to assume it might not work and make
402 provisions for backup boot methods.
405 devmatch functionality has been turned on in devd. It will automatically
406 load drivers for unattached devices. This may cause unexpected drivers to
407 be loaded. Please report any problems to current@ and imp@freebsd.org.
410 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
411 6.0.0. Please see the 20141231 entry below for information about
412 prerequisites and upgrading, if you are not already using clang 3.5.0
416 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
417 This means it is used to link the kernel and userland libraries and
418 executables, but is not yet installed as /usr/bin/ld by default.
420 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
421 WITHOUT_LLD_BOOTSTRAP=yes
424 On i386, pmtimer has been removed. Its functionality has been folded
425 into apm. It was a no-op on ACPI in current for a while now (but was still
426 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
427 from kernel config files.
430 The use of RSS hash from the network card aka flowid has been
431 disabled by default for lagg(4) as it's currently incompatible with
432 the lacp and loadbalance protocols.
434 This can be re-enabled by setting the following in loader.conf:
435 net.link.lagg.default_use_flowid="1"
438 The SW_WATCHDOG option is no longer necessary to enable the
439 hardclock-based software watchdog if no hardware watchdog is
440 configured. As before, SW_WATCHDOG will cause the software
441 watchdog to be enabled even if a hardware watchdog is configured.
444 r326887 fixes the issue described in the 20171214 UPDATING entry.
445 r326888 flips the switch back to building GELI support always.
448 r362593 broke ZFS + GELI support for reasons unknown. However,
449 it also broke ZFS support generally, so GELI has been turned off
450 by default as the lesser evil in r326857. If you boot off ZFS and/or
451 GELI, it might not be a good time to update.
454 PowerPC users must update loader(8) by rebuilding world before
455 installing a new kernel, as the protocol connecting them has
456 changed. Without the update, loader metadata will not be passed
457 successfully to the kernel and users will have to enter their
458 root partition at the kernel mountroot prompt to continue booting.
459 Newer versions of loader can boot old kernels without issue.
462 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
463 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
464 to WITH/OUT_LOADER_GELI.
467 The naive and non-compliant support of posix_fallocate(2) in ZFS
468 has been removed as of r325320. The system call now returns EINVAL
469 when used on a ZFS file. Although the new behavior complies with the
470 standard, some consumers are not prepared to cope with it.
471 One known victim is lld prior to r325420.
474 Building in a FreeBSD src checkout will automatically create object
475 directories now rather than store files in the current directory if
476 'make obj' was not ran. Calling 'make obj' is no longer necessary.
477 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
478 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
482 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
483 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
484 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
485 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
486 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
487 The UNIFIED_OBJDIR option is a transitional feature that will be
488 removed for 12.0 release; please migrate to the new format for any
489 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
490 than hardcoding paths.
493 The native-xtools target no longer installs the files by default to the
494 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
495 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
498 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
499 options are changing from controlling the build if defined / undefined
500 to controlling the build with explicit 'yes' or 'no' values. They will
501 shift to WITH/WITHOUT options to match other options in the system.
504 libstand has turned into a private library for sys/boot use only.
505 It is no longer supported as a public interface outside of sys/boot.
508 The arm port has split armv6 into armv6 and armv7. armv7 is now
509 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
510 and are running a kernel from before r324363, you will need to add
511 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
514 When building multiple kernels using KERNCONF, non-existent KERNCONF
515 files will produce an error and buildkernel will fail. Previously
516 missing KERNCONF files silently failed giving no indication as to
517 why, only to subsequently discover during installkernel that the
518 desired kernel was never built in the first place.
521 The default serial number format for CTL LUNs has changed. This will
522 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
523 or iSCSI clients care about their LUNs' serial numbers. Users who
524 require serial number stability should hardcode serial numbers in
528 For 32-bit arm compiled for hard-float support, soft-floating point
529 binaries now always get their shared libraries from
530 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
531 /usr/libsoft also existed). Only users with a hard-float ld.so, but
532 soft-float everything else should be affected.
535 The geli password typed at boot is now hidden. To restore the previous
536 behavior, see geli(8) for configuration options.
539 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
540 sysctl values. Minor nit, but requires a rebuild of both world/kernel
544 "make check" behavior (made in ^/head@r295380) has been changed to
545 execute from a limited sandbox, as opposed to executing from
549 - The "beforecheck" and "aftercheck" targets are now specified.
550 - ${CHECKDIR} (added in commit noted above) has been removed.
551 - Legacy behavior can be enabled by setting
552 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
554 If the limited sandbox mode is enabled, "make check" will execute
555 "make distribution", then install, execute the tests, and clean up the
556 sandbox if successful.
558 The "make distribution" and "make install" targets are typically run as
559 root to set appropriate permissions and ownership at installation time.
560 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
561 environment if executing "make check" with limited sandbox mode using
562 an unprivileged user.
565 Since the switch to GPT disk labels, fsck for UFS/FFS has been
566 unable to automatically find alternate superblocks. As of r322297,
567 the information needed to find alternate superblocks has been
568 moved to the end of the area reserved for the boot block.
569 Filesystems created with a newfs of this vintage or later
570 will create the recovery information. If you have a filesystem
571 created prior to this change and wish to have a recovery block
572 created for your filesystem, you can do so by running fsck in
573 foreground mode (i.e., do not use the -p or -y options). As it
574 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
575 to which you should answer yes.
578 As of r321665, an NFSv4 server configuration that services
579 Kerberos mounts or clients that do not support the uid/gid in
580 owner/owner_group string capability, must explicitly enable
581 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
582 machine's /etc/rc.conf file.
585 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
586 Please see the 20141231 entry below for information about prerequisites
587 and upgrading, if you are not already using clang 3.5.0 or higher.
590 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
591 r-commands (rlogin, rsh, etc.) to be built with the base system.
594 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
595 a very major ABI incompatible change, so users of FreeBSD/powerpc must
596 be careful when performing source upgrades. It is best to run
597 'make installworld' from an alternate root system, either a live
598 CD/memory stick, or a temporary root partition. Additionally, all ports
599 must be recompiled. powerpc64 is largely unaffected, except in the case
600 of 32-bit compatibility. All 32-bit binaries will be affected.
603 Forward compatibility for the "ino64" project have been committed. This
604 will allow most new binaries to run on older kernels in a limited
605 fashion. This prevents many of the common foot-shooting actions in the
606 upgrade as well as the limited ability to roll back the kernel across
607 the ino64 upgrade. Complicated use cases may not work properly, though
608 enough simpler ones work to allow recovery in most situations.
611 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
612 if you require the GPL compiler.
615 The internal ABI used for communication between the NFS kernel modules
616 was changed by r320085, so __FreeBSD_version was bumped to
617 ensure all the NFS related modules are updated together.
620 The ABI of struct event was changed by extending the data
621 member to 64bit and adding ext fields. For upgrade, same
622 precautions as for the entry 20170523 "ino64" must be
626 The GNU roff toolchain has been removed from base. To render manpages
627 which are not supported by mandoc(1), man(1) can fallback on GNU roff
628 from ports (and recommends to install it).
629 To render roff(7) documents, consider using GNU roff from ports or the
630 heirloom doctools roff toolchain from ports via pkg install groff or
631 via pkg install heirloom-doctools.
634 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
635 smaller runtime footprint builds. This is useful for embedded systems
636 which only require one chipset support.
638 If you load it as a module, make sure this is in /boot/loader.conf:
642 This will load the HAL, all chip/RF backends and if_ath_pci.
643 If you have if_ath_pci in /boot/loader.conf, ensure it is after
644 if_ath or it will not load any HAL chipset support.
646 If you want to selectively load things (eg on ye cheape ARM/MIPS
647 platforms where RAM is at a premium) you should:
650 * load the chip modules in question
651 * load ath_rate, ath_dfs
653 * load if_ath_pci and/or if_ath_ahb depending upon your particular
654 bus bind type - this is where probe/attach is done.
656 For further comments/feedback, poke adrian@ .
659 The "ino64" 64-bit inode project has been committed, which extends
660 a number of types to 64 bits. Upgrading in place requires care and
661 adherence to the documented upgrade procedure.
663 If using a custom kernel configuration ensure that the
664 COMPAT_FREEBSD11 option is included (as during the upgrade the
665 system will be running the ino64 kernel with the existing world).
667 For the safest in-place upgrade begin by removing previous build
668 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
669 full procedure documented below under the heading "To rebuild
670 everything and install it on the current system." Specifically,
671 a reboot is required after installing the new kernel before
675 The NATM framework including the en(4), fatm(4), hatm(4), and
676 patm(4) devices has been removed. Consumers should plan a
677 migration before the end-of-life date for FreeBSD 11.
680 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
681 diff has not been implemented, if those are needed a newer version of
682 GNU diff is available via the diffutils package under the gdiff name.
685 As of r316810 for ipfilter, keep frags is no longer assumed when
686 keep state is specified in a rule. r316810 aligns ipfilter with
687 documentation in man pages separating keep frags from keep state.
688 This allows keep state to be specified without forcing keep frags
689 and allows keep frags to be specified independently of keep state.
690 To maintain previous behaviour, also specify keep frags with
691 keep state (as documented in ipf.conf.5).
694 arm64 builds now use the base system LLD 4.0.0 linker by default,
695 instead of requiring that the aarch64-binutils port or package be
696 installed. To continue using aarch64-binutils, set
697 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
700 The UDP optimization in entry 20160818 that added the sysctl
701 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
702 packets will no longer be treated as L3 broadcast packets.
705 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
706 use any explicitly assigned loopback address available in the jail
707 instead of using the first assigned address of the jail.
710 The ctl.ko module no longer implements the iSCSI target frontend:
711 cfiscsi.ko does instead.
713 If building cfiscsi.ko as a kernel module, the module can be loaded
714 via one of the following methods:
715 - `cfiscsi_load="YES"` in loader.conf(5).
716 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
717 - ctladm(8)/ctld(8), when compiled with iSCSI support
718 (`WITH_ISCSI=yes` in src.conf(5))
720 Please see cfiscsi(4) for more details.
723 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
724 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
725 same source (previously, the dependency of mmcsd.ko on mmc.ko was
726 missing, but mmcsd.ko now will refuse to load if it is incompatible
730 The syntax of ipfw(8) named states was changed to avoid ambiguity.
731 If you have used named states in the firewall rules, you need to modify
732 them after installworld and before rebooting. Now named states must
733 be prefixed with colon.
736 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
737 removed as the userland we provide cannot use them. The KMS version
738 (sys/dev/drm2) supports the same hardware.
741 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
742 Please see the 20141231 entry below for information about prerequisites
743 and upgrading, if you are not already using clang 3.5.0 or higher.
746 The code that provides support for ZFS .zfs/ directory functionality
747 has been reimplemented. It's not possible now to create a snapshot
748 by mkdir under .zfs/snapshot/. That should be the only user visible
752 EISA bus support has been removed. The WITH_EISA option is no longer
756 MCA bus support has been removed.
759 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
760 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
763 The EM_MULTIQUEUE kernel configuration option is deprecated now that
764 the em(4) driver conforms to iflib specifications.
767 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
768 IFLIB. If you have a custom kernel configuration that excludes em(4)
769 but you use igb(4), you need to re-add em(4) to your custom configuration.
772 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
773 Please see the 20141231 entry below for information about prerequisites
774 and upgrading, if you are not already using clang 3.5.0 or higher.
777 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
778 Please see the 20141231 entry below for information about prerequisites
779 and upgrading, if you are not already using clang 3.5.0 or higher.
782 The layout of the pmap structure has changed for powerpc to put the pmap
783 statistics at the front for all CPU variations. libkvm(3) and all tools
784 that link against it need to be recompiled.
787 isl(4) and cyapa(4) drivers now require a new driver,
788 chromebook_platform(4), to work properly on Chromebook-class hardware.
789 On other types of hardware the drivers may need to be configured using
790 device hints. Please see the corresponding manual pages for details.
793 The urtwn(4) driver was merged into rtwn(4) and now consists of
794 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
796 Also, firmware for RTL8188CE was renamed due to possible name
797 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
800 GNU rcs has been removed from base. It is available as packages:
801 - rcs: Latest GPLv3 GNU rcs version.
802 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
806 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
807 modules now requires that the kernel configuration contain the
808 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
811 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
812 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
815 Relocatable object files with the extension of .So have been renamed
816 to use an extension of .pico instead. The purpose of this change is
817 to avoid a name clash with shared libraries on case-insensitive file
818 systems. On those file systems, foo.So is the same file as foo.so.
821 GNU rcs has been turned off by default. It can (temporarily) be built
822 again by adding WITH_RCS knob in src.conf.
823 Otherwise, GNU rcs is available from packages:
824 - rcs: Latest GPLv3 GNU rcs version.
825 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
828 The backup_uses_rcs functionality has been removed from rc.subr.
831 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
832 two separate components, QUEUE_MACRO_DEBUG_TRACE and
833 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
834 QUEUE_MACRO_DEBUG behavior.
837 r304787 changed some ioctl interfaces between the iSCSI userspace
838 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
839 rebuilt to work with new kernels. __FreeBSD_version has been bumped
843 The UDP receive code has been updated to only treat incoming UDP
844 packets that were addressed to an L2 broadcast address as L3
845 broadcast packets. It is not expected that this will affect any
846 standards-conforming UDP application. The new behaviour can be
847 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
851 Remove the openbsd_poll system call.
852 __FreeBSD_version has been bumped because of this.
855 The stable/11 branch has been created from head@r302406.
858 The libc stub for the pipe(2) system call has been replaced with
859 a wrapper that calls the pipe2(2) system call and the pipe(2)
860 system call is now only implemented by the kernels that include
861 "options COMPAT_FREEBSD10" in their config file (this is the
862 default). Users should ensure that this option is enabled in
863 their kernel or upgrade userspace to r302092 before upgrading their
867 CAM will now strip leading spaces from SCSI disks' serial numbers.
868 This will affect users who create UFS filesystems on SCSI disks using
869 those disk's diskid device nodes. For example, if /etc/fstab
870 previously contained a line like
871 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
872 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
873 transforms like gmirror may also be affected. ZFS users should
877 The bitstring(3) API has been updated with new functionality and
878 improved performance. But it is binary-incompatible with the old API.
879 Objects built with the new headers may not be linked against objects
880 built with the old headers.
883 The brk and sbrk functions have been removed from libc on arm64.
884 Binutils from ports has been updated to not link to these
885 functions and should be updated to the latest version before
886 installing a new libc.
889 The armv6 port now defaults to hard float ABI. Limited support
890 for running both hardfloat and soft float on the same system
891 is available using the libraries installed with -DWITH_LIBSOFT.
892 This has only been tested as an upgrade path for installworld
893 and packages may fail or need manual intervention to run. New
894 packages will be needed.
896 To update an existing self-hosted armv6hf system, you must add
897 TARGET_ARCH=armv6 on the make command line for both the build
898 and the install steps.
901 Kernel modules compiled outside of a kernel build now default to
902 installing to /boot/modules instead of /boot/kernel. Many kernel
903 modules built this way (such as those in ports) already overrode
904 KMODDIR explicitly to install into /boot/modules. However,
905 manually building and installing a module from /sys/modules will
906 now install to /boot/modules instead of /boot/kernel.
909 The CAM I/O scheduler has been committed to the kernel. There should be
910 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
911 list of known rogues that claim support for this but actually corrupt
912 data is believed to be complete, be on the lookout for data
913 corruption. The known rogue list is believed to be complete:
915 o Crucial MX100, M550 drives with MU01 firmware.
916 o Micron M510 and M550 drives with MU01 firmware.
917 o Micron M500 prior to MU07 firmware
918 o Samsung 830, 840, and 850 all firmwares
919 o FCCT M500 all firmwares
921 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
922 with working NCQ TRIM. For Micron branded drives, see your sales rep for
923 updated firmware. Black listed drives will work correctly because these
924 drives work correctly so long as no NCQ TRIMs are sent to them. Given
925 this list is the same as found in Linux, it's believed there are no
926 other rogues in the market place. All other models from the above
929 To be safe, if you are at all concerned, you can quirk each of your
930 drives to prevent NCQ from being sent by setting:
931 kern.cam.ada.X.quirks="0x2"
932 in loader.conf. If the drive requires the 4k sector quirk, set the
936 The FAST_DEPEND build option has been removed and its functionality is
937 now the one true way. The old mkdep(1) style of 'make depend' has
938 been removed. See 20160311 for further details.
941 Resource range types have grown from unsigned long to uintmax_t. All
942 drivers, and anything using libdevinfo, need to be recompiled.
945 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
946 builds. It no longer runs mkdep(1) during 'make depend', and the
947 'make depend' stage can safely be skipped now as it is auto ran
948 when building 'make all' and will generate all SRCS and DPSRCS before
949 building anything else. Dependencies are gathered at compile time with
950 -MF flags kept in separate .depend files per object file. Users should
951 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
955 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
956 kernel modules. Therefore, if you load any kernel modules at boot time,
957 please install the boot loaders after you install the kernel, but before
961 make buildkernel KERNCONF=YOUR_KERNEL_HERE
962 make installkernel KERNCONF=YOUR_KERNEL_HERE
963 make -C sys/boot install
964 <reboot in single user>
966 Then follow the usual steps, described in the General Notes section,
970 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
971 see the 20141231 entry below for information about prerequisites and
972 upgrading, if you are not already using clang 3.5.0 or higher.
975 The AIO subsystem is now a standard part of the kernel. The
976 VFS_AIO kernel option and aio.ko kernel module have been removed.
977 Due to stability concerns, asynchronous I/O requests are only
978 permitted on sockets and raw disks by default. To enable
979 asynchronous I/O requests on all file types, set the
980 vfs.aio.enable_unsafe sysctl to a non-zero value.
983 The ELF object manipulation tool objcopy is now provided by the
984 ELF Tool Chain project rather than by GNU binutils. It should be a
985 drop-in replacement, with the addition of arm64 support. The
986 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
987 to obtain the GNU version if necessary.
990 Building ZFS pools on top of zvols is prohibited by default. That
991 feature has never worked safely; it's always been prone to deadlocks.
992 Using a zvol as the backing store for a VM guest's virtual disk will
993 still work, even if the guest is using ZFS. Legacy behavior can be
994 restored by setting vfs.zfs.vol.recursive=1.
997 The NONE and HPN patches has been removed from OpenSSH. They are
998 still available in the security/openssh-portable port.
1001 With the addition of ypldap(8), a new _ypldap user is now required
1002 during installworld. "mergemaster -p" can be used to add the user
1003 prior to installworld, as documented in the handbook.
1006 The tftp loader (pxeboot) now uses the option root-path directive. As a
1007 consequence it no longer looks for a pxeboot.4th file on the tftp
1008 server. Instead it uses the regular /boot infrastructure as with the
1012 The code to start recording plug and play data into the modules has
1013 been committed. While the old tools will properly build a new kernel,
1014 a number of warnings about "unknown metadata record 4" will be produced
1015 for an older kldxref. To avoid such warnings, make sure to rebuild
1016 the kernel toolchain (or world). Make sure that you have r292078 or
1017 later when trying to build 292077 or later before rebuilding.
1020 Debug data files are now built by default with 'make buildworld' and
1021 installed with 'make installworld'. This facilitates debugging but
1022 requires more disk space both during the build and for the installed
1023 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1027 r291527 changed the internal interface between the nfsd.ko and
1028 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1029 __FreeBSD_version has been bumped because of this.
1032 Add support for unicode collation strings leads to a change of
1033 order of files listed by ls(1) for example. To get back to the old
1034 behaviour, set LC_COLLATE environment variable to "C".
1036 Databases administrators will need to reindex their databases given
1037 collation results will be different.
1039 Due to a bug in install(1) it is recommended to remove the ancient
1040 locales before running make installworld.
1042 rm -rf /usr/share/locale/*
1045 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1046 libcrypto.so.7 or libssl.so.7 must be recompiled.
1049 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1050 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1051 should be replaced with isp_2400 and isp_2500 modules respectively.
1054 The build previously allowed using 'make -n' to not recurse into
1055 sub-directories while showing what commands would be executed, and
1056 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1057 and 'make -N' will not.
1060 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1061 and etcupdate will now use this file. A custom sendmail.cf is now
1062 updated via this mechanism rather than via installworld. If you had
1063 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1064 want to remove the exclusion or change it to "always install".
1065 /etc/mail/sendmail.cf is now managed the same way regardless of
1066 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1067 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1070 Compatibility shims for legacy ATA device names have been removed.
1071 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1072 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1073 environment variables, /dev/ad* and /dev/ar* symbolic links.
1076 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1077 Please see the 20141231 entry below for information about prerequisites
1078 and upgrading, if you are not already using clang 3.5.0 or higher.
1081 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1082 and renamed from .symbols to .debug. This reduces the size requirements
1083 on the boot partition or file system and provides consistency with
1084 userland debug files.
1086 When using the supported kernel installation method the
1087 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1088 as is done with /boot/kernel.
1090 Developers wishing to maintain the historical behavior of installing
1091 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1094 The wireless drivers had undergone changes that remove the 'parent
1095 interface' from the ifconfig -l output. The rc.d network scripts
1096 used to check presence of a parent interface in the list, so old
1097 scripts would fail to start wireless networking. Thus, etcupdate(3)
1098 or mergemaster(8) run is required after kernel update, to update your
1099 rc.d scripts in /etc.
1102 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1103 These configurations are now automatically interpreted as
1104 'scrub fragment reassemble'.
1107 Kernel-loadable modules for the random(4) device are back. To use
1108 them, the kernel must have
1111 options RANDOM_LOADABLE
1113 kldload(8) can then be used to load random_fortuna.ko
1114 or random_yarrow.ko. Please note that due to the indirect
1115 function calls that the loadable modules need to provide,
1116 the build-in variants will be slightly more efficient.
1118 The random(4) kernel option RANDOM_DUMMY has been retired due to
1119 unpopularity. It was not all that useful anyway.
1122 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1123 Control over building the ELF Tool Chain tools is now provided by
1124 the WITHOUT_TOOLCHAIN knob.
1127 The polarity of Pulse Per Second (PPS) capture events with the
1128 uart(4) driver has been corrected. Prior to this change the PPS
1129 "assert" event corresponded to the trailing edge of a positive PPS
1130 pulse and the "clear" event was the leading edge of the next pulse.
1132 As the width of a PPS pulse in a typical GPS receiver is on the
1133 order of 1 millisecond, most users will not notice any significant
1134 difference with this change.
1136 Anyone who has compensated for the historical polarity reversal by
1137 configuring a negative offset equal to the pulse width will need to
1138 remove that workaround.
1141 The default group assigned to /dev/dri entries has been changed
1142 from 'wheel' to 'video' with the id of '44'. If you want to have
1143 access to the dri devices please add yourself to the video group
1146 # pw groupmod video -m $USER
1149 The menu.rc and loader.rc files will now be replaced during
1150 upgrades. Please migrate local changes to menu.rc.local and
1151 loader.rc.local instead.
1154 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1155 strings and strip have been removed. The src.conf(5) knob
1156 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1159 As ZFS requires more kernel stack pages than is the default on some
1160 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1161 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1163 Please consider using 'options KSTACK_PAGES=X' where X is greater
1164 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1167 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1168 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1169 default, i.e., they will not contain "::". For example, instead
1170 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1171 to have a more specific match, such as different map entries for
1172 IPv6:0:0 vs IPv6:0. This change requires that configuration
1173 data (including maps, files, classes, custom ruleset, etc.) must
1174 use the same format, so make certain such configuration data is
1175 upgrading. As a very simple check search for patterns like
1176 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1177 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1178 the cf option UseCompressedIPv6Addresses.
1181 The default kernel entropy-processing algorithm is now
1182 Fortuna, replacing Yarrow.
1184 Assuming you have 'device random' in your kernel config
1185 file, the configurations allow a kernel option to override
1186 this default. You may choose *ONE* of:
1188 options RANDOM_YARROW # Legacy /dev/random algorithm.
1189 options RANDOM_DUMMY # Blocking-only driver.
1191 If you have neither, you get Fortuna. For most people,
1192 read no further, Fortuna will give a /dev/random that works
1193 like it always used to, and the difference will be irrelevant.
1195 If you remove 'device random', you get *NO* kernel-processed
1196 entropy at all. This may be acceptable to folks building
1197 embedded systems, but has complications. Carry on reading,
1198 and it is assumed you know what you need.
1200 *PLEASE* read random(4) and random(9) if you are in the
1201 habit of tweaking kernel configs, and/or if you are a member
1202 of the embedded community, wanting specific and not-usual
1203 behaviour from your security subsystems.
1205 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1206 random', you will NOT have a functioning /dev/random, and
1207 many cryptographic features will not work, including SSH.
1208 You may also find strange behaviour from the random(3) set
1209 of library functions, in particular sranddev(3), srandomdev(3)
1210 and arc4random(3). The reason for this is that the KERN_ARND
1211 sysctl only returns entropy if it thinks it has some to
1212 share, and with RANDOM_DUMMY or no 'device random' this
1216 An additional fix for the issue described in the 20150614 sendmail
1217 entry below has been committed in revision 284717.
1220 FreeBSD's old make (fmake) has been removed from the system. It is
1221 available as the devel/fmake port or via pkg install fmake.
1224 The fix for the issue described in the 20150614 sendmail entry
1225 below has been committed in revision 284436. The work
1226 around described in that entry is no longer needed unless the
1227 default setting is overridden by a confDH_PARAMETERS configuration
1228 setting of '5' or pointing to a 512 bit DH parameter file.
1231 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1232 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1233 and devel/kyua to version 0.20+ and adjust any calling code to work
1234 with Kyuafile and kyua.
1237 The import of openssl to address the FreeBSD-SA-15:10.openssl
1238 security advisory includes a change which rejects handshakes
1239 with DH parameters below 768 bits. sendmail releases prior
1240 to 8.15.2 (not yet released), defaulted to a 512 bit
1241 DH parameter setting for client connections. To work around
1242 this interoperability, sendmail can be configured to use a
1243 2048 bit DH parameter by:
1245 1. Edit /etc/mail/`hostname`.mc
1246 2. If a setting for confDH_PARAMETERS does not exist or
1247 exists and is set to a string beginning with '5',
1248 replace it with '2'.
1249 3. If a setting for confDH_PARAMETERS exists and is set to
1250 a file path, create a new file with:
1251 openssl dhparam -out /path/to/file 2048
1252 4. Rebuild the .cf file:
1253 cd /etc/mail/; make; make install
1254 5. Restart sendmail:
1255 cd /etc/mail/; make restart
1257 A sendmail patch is coming, at which time this file will be
1261 Generation of legacy formatted entries have been disabled by default
1262 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1263 entries were converted to use the new format by default when the new,
1264 machine independent format have been added and supported since FreeBSD
1267 Please see the pwd_mkdb(8) manual page for further details.
1270 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1271 20141231 entry below for information about prerequisites and upgrading,
1272 if you are not already using 3.5.0 or higher.
1275 TI platform code switched to using vendor DTS files and this update
1276 may break existing systems running on Beaglebone, Beaglebone Black,
1279 - dtb files should be regenerated/reinstalled. Filenames are the
1280 same but content is different now
1281 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1282 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1283 addressing scheme is now pin 25 on /dev/gpioc3.
1284 - Pandaboard: /etc/ttys should be updated, serial console device is
1285 now /dev/ttyu2, not /dev/ttyu0
1288 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1289 If you need the GNU extension from groff soelim(1), install groff
1290 from package: pkg install groff, or via ports: textproc/groff.
1293 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1294 defined in symlink(7); previously symlinks were silently ignored.
1297 The const qualifier has been removed from iconv(3) to comply with
1298 POSIX. The ports tree is aware of this from r384038 onwards.
1301 Libraries specified by LIBADD in Makefiles must have a corresponding
1302 DPADD_<lib> variable to ensure correct dependencies. This is now
1303 enforced in src.libnames.mk.
1306 From legacy ata(4) driver was removed support for SATA controllers
1307 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1308 Kernel modules ataahci and ataadaptec were removed completely,
1309 replaced by ahci and mvs modules respectively.
1312 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1313 the 20141231 entry below for information about prerequisites and
1314 upgrading, if you are not already using 3.5.0 or higher.
1317 The 32-bit PowerPC kernel has been changed to a position-independent
1318 executable. This can only be booted with a version of loader(8)
1319 newer than January 31, 2015, so make sure to update both world and
1320 kernel before rebooting.
1323 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1324 but before r278950, the RNG was not seeded properly. Immediately
1325 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1326 ssh keys or openssl keys) that were generated w/ a kernel from that
1327 range. This does not affect programs that directly used /dev/random
1328 or /dev/urandom. All userland uses of arc4random(3) are affected.
1331 The autofs(4) ABI was changed in order to restore binary compatibility
1332 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1333 with the new kernel.
1336 The powerpc64 kernel has been changed to a position-independent
1337 executable. This can only be booted with a new version of loader(8),
1338 so make sure to update both world and kernel before rebooting.
1341 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1342 only release, no new features have been added. Please see the 20141231
1343 entry below for information about prerequisites and upgrading, if you
1344 are not already using 3.5.0.
1347 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1348 taken from the ELF Tool Chain project rather than GNU binutils. They
1349 should be drop-in replacements, with the addition of arm64 support.
1350 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1351 binutils tools, if necessary. See 20150805 for updated information.
1354 The default Unbound configuration now enables remote control
1355 using a local socket. Users who have already enabled the
1356 local_unbound service should regenerate their configuration
1357 by running "service local_unbound setup" as root.
1360 The GNU texinfo and GNU info pages have been removed.
1361 To be able to view GNU info pages please install texinfo from ports.
1364 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1366 As of this release, a prerequisite for building clang, llvm and lldb is
1367 a C++11 capable compiler and C++11 standard library. This means that to
1368 be able to successfully build the cross-tools stage of buildworld, with
1369 clang as the bootstrap compiler, your system compiler or cross compiler
1370 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1371 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1374 On any standard FreeBSD 10.x or 11.x installation, where clang and
1375 libc++ are on by default (that is, on x86 or arm), this should work out
1378 On 9.x installations where clang is enabled by default, e.g. on x86 and
1379 powerpc, libc++ will not be enabled by default, so libc++ should be
1380 built (with clang) and installed first. If both clang and libc++ are
1381 missing, build clang first, then use it to build libc++.
1383 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1384 the instructions for 9.x above.
1386 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1387 default, and do not build clang.
1389 Many embedded systems are resource constrained, and will not be able to
1390 build clang in a reasonable time, or in some cases at all. In those
1391 cases, cross building bootable systems on amd64 is a workaround.
1393 This new version of clang introduces a number of new warnings, of which
1394 the following are most likely to appear:
1398 This warns in two cases, for both C and C++:
1399 * When the code is trying to take the absolute value of an unsigned
1400 quantity, which is effectively a no-op, and almost never what was
1401 intended. The code should be fixed, if at all possible. If you are
1402 sure that the unsigned quantity can be safely cast to signed, without
1403 loss of information or undefined behavior, you can add an explicit
1404 cast, or disable the warning.
1406 * When the code is trying to take an absolute value, but the called
1407 abs() variant is for the wrong type, which can lead to truncation.
1408 If you want to disable the warning instead of fixing the code, please
1409 make sure that truncation will not occur, or it might lead to unwanted
1412 -Wtautological-undefined-compare and
1413 -Wundefined-bool-conversion
1415 These warn when C++ code is trying to compare 'this' against NULL, while
1416 'this' should never be NULL in well-defined C++ code. However, there is
1417 some legacy (pre C++11) code out there, which actively abuses this
1418 feature, which was less strictly defined in previous C++ versions.
1420 Squid and openjdk do this, for example. The warning can be turned off
1421 for C++98 and earlier, but compiling the code in C++11 mode might result
1422 in unexpected behavior; for example, the parts of the program that are
1423 unreachable could be optimized away.
1426 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1427 kernel sources have been removed. The .h files remain, since some
1428 utilities include them. This will need to be fixed later.
1429 If "mount -t oldnfs ..." is attempted, it will fail.
1430 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1431 the utilities will report errors.
1434 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1435 directories to top level SUBDIR variable when their parent
1436 directory is included in LOCAL_DIRS. Users with build systems with
1437 such hierarchies and without SUBDIR entries in the parent
1438 directory Makefiles should add them or add the directories to
1442 faith(4) and faithd(8) have been removed from the base system. Faith
1443 has been obsolete for a very long time.
1446 vt(4), the new console driver, is enabled by default. It brings
1447 support for Unicode and double-width characters, as well as
1448 support for UEFI and integration with the KMS kernel video
1451 You may need to update your console settings in /etc/rc.conf,
1452 most probably the keymap. During boot, /etc/rc.d/syscons will
1453 indicate what you need to do.
1455 vt(4) still has issues and lacks some features compared to
1456 syscons(4). See the wiki for up-to-date information:
1457 https://wiki.freebsd.org/Newcons
1459 If you want to keep using syscons(4), you can do so by adding
1460 the following line to /boot/loader.conf:
1464 pjdfstest has been integrated into kyua as an opt-in test suite.
1465 Please see share/doc/pjdfstest/README for more details on how to
1469 gperf has been removed from the base system for architectures
1470 that use clang. Ports that require gperf will obtain it from the
1474 pjdfstest has been moved from tools/regression/pjdfstest to
1478 At svn r271982, The default linux compat kernel ABI has been adjusted
1479 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1480 update. If you wish to continue using the linux-f10 compat ports,
1481 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1482 encouraged to update their linux-compat packages to linux-c6 during
1483 their next update cycle.
1486 The ofwfb driver, used to provide a graphics console on PowerPC when
1487 using vt(4), no longer allows mmap() of all physical memory. This
1488 will prevent Xorg on PowerPC with some ATI graphics cards from
1489 initializing properly unless x11-servers/xorg-server is updated to
1493 The xdev targets have been converted to using TARGET and
1494 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1497 The default unbound configuration has been modified to address
1498 issues with reverse lookups on networks that use private
1499 address ranges. If you use the local_unbound service, run
1500 "service local_unbound setup" as root to regenerate your
1501 configuration, then "service local_unbound reload" to load the
1505 The GNU texinfo and GNU info pages are not built and installed
1506 anymore, WITH_INFO knob has been added to allow to built and install
1508 UPDATE: see 20150102 entry on texinfo's removal
1511 The GNU readline library is now an INTERNALLIB - that is, it is
1512 statically linked into consumers (GDB and variants) in the base
1513 system, and the shared library is no longer installed. The
1514 devel/readline port is available for third party software that
1518 The Itanium architecture (ia64) has been removed from the list of
1519 known architectures. This is the first step in the removal of the
1523 Commit r268115 has added NFSv4.1 server support, merged from
1524 projects/nfsv4.1-server. Since this includes changes to the
1525 internal interfaces between the NFS related modules, a full
1526 build of the kernel and modules will be necessary.
1527 __FreeBSD_version has been bumped.
1530 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1531 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1532 which differs from the behaviour controlled by this knob.)
1535 Maximal length of the serial number in CTL was increased from 16 to
1536 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1537 and ctld, need to be rebuilt to work with a new kernel.
1540 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1541 1 respectively to match the upstream numbers. They were out of
1542 sync because, when they were originally added to FreeBSD, the
1543 upstream versions were not respected. These libraries are private
1544 and not yet built by default, so renumbering them should be a
1545 non-issue. However, unclean source trees will yield broken test
1546 programs once the operator executes "make delete-old-libs" after a
1547 "make installworld".
1549 Additionally, the atf-sh binary was made private by moving it into
1550 /usr/libexec/. Already-built shell test programs will keep the
1551 path to the old binary so they will break after "make delete-old"
1554 If you are using WITH_TESTS=yes (not the default), wipe the object
1555 tree and rebuild from scratch to prevent spurious test failures.
1556 This is only needed once: the misnumbered libraries and misplaced
1557 binaries have been added to OptionalObsoleteFiles.inc so they will
1558 be removed during a clean upgrade.
1561 Clang and llvm have been upgraded to 3.4.1 release.
1564 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1565 be removed to avoid issues in the future (and has been added to
1569 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1570 past, it affected all builds that used the bsd.*.mk files. The old
1571 behavior was a bug, but people may have relied upon it. To get this
1572 behavior back, you can .include /etc/src.conf from /etc/make.conf
1573 (which is still global and isn't changed). This also changes the
1574 behavior of incremental builds inside the tree of individual
1575 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1576 Although this has survived make universe and some upgrade scenarios,
1577 other upgrade scenarios may have broken. At least one form of
1578 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1579 as well... In cases where MAKESYSPATH isn't working with this
1580 setting, you'll need to set it to the full path to your tree.
1582 One side effect of all this cleaning up is that bsd.compiler.mk
1583 is no longer implicitly included by bsd.own.mk. If you wish to
1584 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1588 The lindev device has been removed since /dev/full has been made a
1589 standard device. __FreeBSD_version has been bumped.
1592 The knob WITHOUT_VI was added to the base system, which controls
1593 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1594 in order to reorder files share/termcap and didn't build ex(1) as a
1595 build tool, so building/installing with WITH_VI is highly advised for
1596 build hosts for older releases.
1598 This issue has been fixed in stable/9 and stable/10 in r277022 and
1599 r276991, respectively.
1602 The YES_HESIOD knob has been removed. It has been obsolete for
1603 a decade. Please move to using WITH_HESIOD instead or your builds
1604 will silently lack HESIOD.
1607 The uart(4) driver has been changed with respect to its handling
1608 of the low-level console. Previously the uart(4) driver prevented
1609 any process from changing the baudrate or the CLOCAL and HUPCL
1610 control flags. By removing the restrictions, operators can make
1611 changes to the serial console port without having to reboot.
1612 However, when getty(8) is started on the serial device that is
1613 associated with the low-level console, a misconfigured terminal
1614 line in /etc/ttys will now have a real impact.
1615 Before upgrading the kernel, make sure that /etc/ttys has the
1616 serial console device configured as 3wire without baudrate to
1617 preserve the previous behaviour. E.g:
1618 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1621 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1622 to improve performance. To re-enable it, if needed, run rpcbind
1623 with command line option -W.
1626 Switched back to the GPL dtc compiler due to updates in the upstream
1627 dts files not being supported by the BSDL dtc compiler. You will need
1628 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1629 may result while building dtb files during a kernel build if you fail
1630 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1633 Clang and llvm have been upgraded to 3.4 release.
1636 The nve(4) driver has been removed. Please use the nfe(4) driver
1637 for NVIDIA nForce MCP Ethernet adapters instead.
1640 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1641 This could cause certain C++ applications using shared libraries built
1642 against the previous version of libc++ to crash. The incompatibility
1643 has now been fixed, but any C++ applications or shared libraries built
1644 between r261283 and r261801 should be recompiled.
1647 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1648 capability mode support. Please note that enabling the feature in
1649 kernel is still highly recommended.
1652 OpenSSH is now built with sandbox support, and will use sandbox as
1653 the default privilege separation method. This requires Capsicum
1654 capability mode support in kernel.
1657 The libelf and libdwarf libraries have been updated to newer
1658 versions from upstream. Shared library version numbers for
1659 these two libraries were bumped. Any ports or binaries
1660 requiring these two libraries should be recompiled.
1661 __FreeBSD_version is bumped to 1100006.
1664 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1665 instead of providing an explicit one, this would prevent such
1666 Makefile from providing its own Kyuafile in the future during
1667 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1668 intervention is needed to clean an objdir if you use NO_CLEAN:
1669 # find /usr/obj -name Kyuafile | xargs rm -f
1672 The behavior of gss_pseudo_random() for the krb5 mechanism
1673 has changed, for applications requesting a longer random string
1674 than produced by the underlying enctype's pseudo-random() function.
1675 In particular, the random string produced from a session key of
1676 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1677 be different at the 17th octet and later, after this change.
1678 The counter used in the PRF+ construction is now encoded as a
1679 big-endian integer in accordance with RFC 4402.
1680 __FreeBSD_version is bumped to 1100004.
1683 The WITHOUT_ATF build knob has been removed and its functionality
1684 has been subsumed into the more generic WITHOUT_TESTS. If you were
1685 using the former to disable the build of the ATF libraries, you
1686 should change your settings to use the latter.
1689 The default version of mtree is nmtree which is obtained from
1690 NetBSD. The output is generally the same, but may vary
1691 slightly. If you found you need identical output adding
1692 "-F freebsd9" to the command line should do the trick. For the
1693 time being, the old mtree is available as fmtree.
1696 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1697 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1698 1.1.4_8 and verify bsdyml not linked in, before running "make
1700 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1702 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1705 The stable/10 branch has been created in subversion from head
1712 Avoid using make -j when upgrading. While generally safe, there are
1713 sometimes problems using -j to upgrade. If your upgrade fails with
1714 -j, please try again without -j. From time to time in the past there
1715 have been problems using -j with buildworld and/or installworld. This
1716 is especially true when upgrading between "distant" versions (eg one
1717 that cross a major release boundary or several minor releases, or when
1718 several months have passed on the -current branch).
1720 Sometimes, obscure build problems are the result of environment
1721 poisoning. This can happen because the make utility reads its
1722 environment when searching for values for global variables. To run
1723 your build attempts in an "environmental clean room", prefix all make
1724 commands with 'env -i '. See the env(1) manual page for more details.
1726 When upgrading from one major version to another it is generally best to
1727 upgrade to the latest code in the currently installed branch first, then
1728 do an upgrade to the new branch. This is the best-tested upgrade path,
1729 and has the highest probability of being successful. Please try this
1730 approach if you encounter problems with a major version upgrade. Since
1731 the stable 4.x branch point, one has generally been able to upgrade from
1732 anywhere in the most recent stable branch to head / current (or even the
1733 last couple of stable branches). See the top of this file when there's
1736 When upgrading a live system, having a root shell around before
1737 installing anything can help undo problems. Not having a root shell
1738 around can lead to problems if pam has changed too much from your
1739 starting point to allow continued authentication after the upgrade.
1741 This file should be read as a log of events. When a later event changes
1742 information of a prior event, the prior event should not be deleted.
1743 Instead, a pointer to the entry with the new information should be
1744 placed in the old entry. Readers of this file should also sanity check
1745 older entries before relying on them blindly. Authors of new entries
1746 should write them with this in mind.
1750 When upgrading the boot ZFS pool to a new version, always follow
1753 1.) recompile and reinstall the ZFS boot loader and boot block
1754 (this is part of "make buildworld" and "make installworld")
1756 2.) update the ZFS boot block on your boot drive
1758 The following example updates the ZFS boot block on the first
1759 partition (freebsd-boot) of a GPT partitioned drive ada0:
1760 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1762 Non-boot pools do not need these updates.
1766 If you are updating from a prior version of FreeBSD (even one just
1767 a few days old), you should follow this procedure. It is the most
1768 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1770 make kernel-toolchain
1771 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1772 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1774 To test a kernel once
1775 ---------------------
1776 If you just want to boot a kernel once (because you are not sure
1777 if it works, or if you want to boot a known bad kernel to provide
1778 debugging information) run
1779 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1780 nextboot -k testkernel
1782 To rebuild everything and install it on the current system.
1783 -----------------------------------------------------------
1784 # Note: sometimes if you are running current you gotta do more than
1785 # is listed here if you are upgrading from a really old current.
1787 <make sure you have good level 0 dumps>
1789 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1790 make installkernel KERNCONF=YOUR_KERNEL_HERE
1792 <reboot in single user> [3]
1799 To cross-install current onto a separate partition
1800 --------------------------------------------------
1801 # In this approach we use a separate partition to hold
1802 # current's root, 'usr', and 'var' directories. A partition
1803 # holding "/", "/usr" and "/var" should be about 2GB in
1806 <make sure you have good level 0 dumps>
1809 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1810 <maybe newfs current's root partition>
1811 <mount current's root partition on directory ${CURRENT_ROOT}>
1812 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1813 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1814 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1815 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1816 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1817 <reboot into current>
1818 <do a "native" rebuild/install as described in the previous section>
1819 <maybe install compatibility libraries from ports/misc/compat*>
1823 To upgrade in-place from stable to current
1824 ----------------------------------------------
1825 <make sure you have good level 0 dumps>
1827 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1828 make installkernel KERNCONF=YOUR_KERNEL_HERE
1830 <reboot in single user> [3]
1837 Make sure that you've read the UPDATING file to understand the
1838 tweaks to various things you need. At this point in the life
1839 cycle of current, things change often and you are on your own
1840 to cope. The defaults can also change, so please read ALL of
1841 the UPDATING entries.
1843 Also, if you are tracking -current, you must be subscribed to
1844 freebsd-current@freebsd.org. Make sure that before you update
1845 your sources that you have read and understood all the recent
1846 messages there. If in doubt, please track -stable which has
1847 much fewer pitfalls.
1849 [1] If you have third party modules, such as vmware, you
1850 should disable them at this point so they don't crash your
1853 [3] From the bootblocks, boot -s, and then do
1858 adjkerntz -i # if CMOS is wall time
1859 Also, when doing a major release upgrade, it is required that
1860 you boot into single user mode to do the installworld.
1862 [4] Note: This step is non-optional. Failure to do this step
1863 can result in a significant reduction in the functionality of the
1864 system. Attempting to do it by hand is not recommended and those
1865 that pursue this avenue should read this file carefully, as well
1866 as the archives of freebsd-current and freebsd-hackers mailing lists
1867 for potential gotchas. The -U option is also useful to consider.
1868 See mergemaster(8) for more information.
1870 [5] Usually this step is a no-op. However, from time to time
1871 you may need to do this if you get unknown user in the following
1872 step. It never hurts to do it all the time. You may need to
1873 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1874 install) after the buildworld before this step if you last updated
1875 from current before 20130425 or from -stable before 20130430.
1877 [6] This only deletes old files and directories. Old libraries
1878 can be deleted by "make delete-old-libs", but you have to make
1879 sure that no program is using those libraries anymore.
1881 [8] The new kernel must be able to run existing binaries used by
1882 an installworld. When upgrading across major versions, the new
1883 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1884 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1885 binaries). Failure to do so may leave you with a system that is
1886 hard to boot to recover. A GENERIC kernel will include suitable
1887 compatibility options to run binaries from older branches.
1889 Make sure that you merge any new devices from GENERIC since the
1890 last time you updated your kernel config file.
1892 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1893 "?=" instead of the "=" assignment operator, so that buildworld can
1894 override the CPUTYPE if it needs to.
1896 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1897 not on the command line, or in /etc/make.conf. buildworld will
1898 warn if it is improperly defined.
1901 This file contains a list, in reverse chronological order, of major
1902 breakages in tracking -current. It is not guaranteed to be a complete
1903 list of such breakages, and only contains entries since September 23, 2011.
1904 If you need to see UPDATING entries from before that date, you will need
1905 to fetch an UPDATING file from an older FreeBSD release.
1907 Copyright information:
1909 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1911 Redistribution, publication, translation and use, with or without
1912 modification, in full or in part, in any form or format of this
1913 document are permitted without further permission from the author.
1915 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1916 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1917 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1918 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1919 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1920 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1921 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1922 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1923 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1924 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1925 POSSIBILITY OF SUCH DAMAGE.
1927 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob