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.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
36 7.0.1. Please see the 20141231 entry below for information about
37 prerequisites and upgrading, if you are not already using clang 3.5.0
41 Remove the timed and netdate programs from the base tree. Setting
42 the time with these deamons has been obsolete for over a decade.
45 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
46 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
47 it produces broken binaries when ifuncs are in use. Users needing
48 GNU ld should install the binutils port or package.
51 The BSD crtbegin and crtend code has been enabled by default. It has
52 had extensive testing on amd64, arm64, and i386. It can be disabled
53 by building a world with -DWITHOUT_BSD_CRTBEGIN.
56 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
57 has been converted to a port (misc/ctm) and will be removed from
58 FreeBSD-13. It is available as a package (ctm) for all supported
62 The default newsyslog.conf(5) file has been changed to only include
63 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
64 the filenames end in '.conf' and do not begin with a '.'.
66 You should check the configuration files in these two directories match
67 this naming convention. You can verify which configuration files are
68 being included using the command:
72 Ports for the DRM modules have been simplified. Now, amd64 users should
73 just install the drm-kmod port. All others should install
76 Graphics hardware that's newer than about 2010 usually works with
77 drm-kmod. For hardware older than 2013, however, some users will need
78 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
79 than 2008 usually only works in drm-legacy-kmod. The graphics team can
80 only commit to hardware made since 2013 due to the complexity of the
81 market and difficulty to test all the older cards effectively. If you
82 have hardware supported by drm-kmod, you are strongly encouraged to use
83 that as you will get better support.
85 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
86 elsewhere, the drm and drm2 modules will be eliminated from the src base
87 soon (with a limited exception for arm). Please update to the package asap
88 and report any issues to x11@freebsd.org.
90 Generally, anybody using the drm*-kmod packages should add
91 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
92 cross-threading surprises, especially with automatic driver
93 loading from X11 startup. These will become the defaults in 13-current
97 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
98 custom kernel and module loading configuration files must be updated
99 accordingly. Moreover, interfaces previous presented as ixlvN to the
100 system are now exposed as iavfN and network configuration files must
101 be adjusted as necessary.
104 OpenSSL has been updated to version 1.1.1. This update included
105 additional various API changes througout the base system. It is
106 important to rebuild third-party software after upgrading. The value
107 of __FreeBSD_version has been bumped accordingly.
110 The legacy DRM modules and drivers have now been added to the loader's
111 module blacklist, in favor of loading them with kld_list in rc.conf(5).
112 The module blacklist may be overridden with the loader.conf(5)
113 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
117 The cam(4) based nda(4) driver will be used over nvd(4) by default on
118 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
119 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
120 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
124 Reproducible build mode is now on by default, in preparation for
125 FreeBSD 12.0. This eliminates build metadata such as the user,
126 host, and time from the kernel (and uname), unless the working tree
127 corresponds to a modified checkout from a version control system.
128 The previous behavior can be obtained by setting the /etc/src.conf
129 knob WITHOUT_REPRODUCIBLE_BUILD.
132 The Yarrow CSPRNG has been removed from the kernel as it has not been
133 supported by its designers since at least 2003. Fortuna has been the
134 default since FreeBSD-11.
137 devctl freeze/thaw have gone into the tree, the rc scripts have been
138 updated to use them and devmatch has been changed. You should update
139 kernel, userland and rc scripts all at the same time.
142 The default interpreter has been switched from 4th to Lua.
143 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
144 interpreter. If you have custom FORTH code you will need to set
145 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
146 src.conf for the build. This will create default hard links between
147 loader and loader_4th instead of loader and loader_lua, the new default.
148 If you are using UEFI it will create the proper hard link to loader.efi.
150 bhyve uses userboot.so. It remains 4th-only until some issues are solved
151 regarding coexisting with multiple versions of FreeBSD are resolved.
154 ls(1) now respects the COLORTERM environment variable used in other
155 systems and software to indicate that a colored terminal is both
156 supported and desired. If ls(1) is suddenly emitting colors, they may
157 be disabled again by either removing the unwanted COLORTERM from your
158 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
159 may not be observed in a future release.
162 The default pager for most commands has been changed to "less". To
163 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
167 The jedec_ts(4) driver has been removed. A superset of its functionality
168 is available in the jedec_dimm(4) driver, and the manpage for that
169 driver includes migration instructions. If you have "device jedec_ts"
170 in your kernel configuration file, it must be removed.
173 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
174 This should have no effect if the kernel is booted via BIOS/legacy boot.
175 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
176 has a buggy firmware that prevents a successful boot due to use of
180 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
181 support has been removed from the tree. These ports were
182 obsolete and/or known to be broken for many years.
185 loader.efi has been augmented to participate more fully in the
186 UEFI boot manager protocol. loader.efi will now look at the
187 BootXXXX environment variable to determine if a specific kernel
188 or root partition was specified. XXXX is derived from BootCurrent.
189 efibootmgr(8) manages these standard UEFI variables.
192 zfsloader's functionality has now been folded into loader.
193 zfsloader is no longer necessary once you've updated your
194 boot blocks. For a transition period, we will install a
195 hardlink for zfsloader to loader to allow a smooth transition
196 until the boot blocks can be updated (hard link because old
197 zfs boot blocks don't understand symlinks).
200 ARM64 now have efifb support, if you want to have serial console
201 on your arm64 board when an screen is connected and the bootloader
202 setup a frambuffer for us to use, just add :
206 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
207 an screen connected as the firmware will setup a framebuffer are that
208 u-boot will expose as an EFI framebuffer.
211 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
212 or take steps to update /etc/passwd before doing installworld on
213 existing systems. Do not skip the "mergemaster -Fp" step before
214 installworld, as described in the update procedures near the bottom
215 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
216 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
217 the ntp config file contain options that change file/dir locations.
218 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
219 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
220 taking steps to ensure that all required files/dirs are accessible
224 Big endian arm support has been removed.
227 The static environment setup in kernel configs is no longer mutually
228 exclusive with the loader(8) environment by default. In order to
229 restore the previous default behavior of disabling the loader(8)
230 environment if a static environment is present, you must specify
231 loader_env.disabled=1 in the static environment.
234 The ABI of syscalls used by management tools like sockstat and
235 netstat has been broken to allow 32-bit binaries to work on
236 64-bit kernels without modification. These programs will need
237 to match the kernel in order to function. External programs may
238 require minor modifications to accommodate a change of type in
239 structures from pointers to 64-bit virtual addresses.
242 On i386 and amd64 atomics are now inlined. Out of tree modules using
243 atomics will need to be rebuilt.
246 The '%I' format in the kern.corefile sysctl limits the number of
247 core files that a process can generate to the number stored in the
248 debug.ncores sysctl. The '%I' format is replaced by the single digit
249 index. Previously, if all indexes were taken the kernel would overwrite
250 only a core file with the highest index in a filename.
251 Currently the system will create a new core file if there is a free
252 index or if all slots are taken it will overwrite the oldest one.
255 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
256 6.0.1. Please see the 20141231 entry below for information about
257 prerequisites and upgrading, if you are not already using clang 3.5.0
261 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
262 needed to be changed to work with it. This change was made with r335763
263 and requires a mergemaster / etcupdate / etc to update the installed file.
266 r334930 changed the interface between the NFS modules, so they all
267 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
270 As of r334391 lld is the default amd64 system linker; it is installed
271 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
275 The kernel / userland interface for devinfo changed, so you'll
276 need a new kernel and userland as a pair for it to work (rebuilding
277 lib/libdevinfo is all that's required). devinfo and devmatch will
278 not work, but everything else will when there's a mismatch.
281 The on-disk format for hwpmc callchain records has changed to include
282 threadid corresponding to a given record. This changes the field offsets
283 and thus requires that libpmcstat be rebuilt before using a kernel
287 The vxge(4) driver has been removed. This driver was introduced into
288 HEAD one week before the Exar left the Ethernet market and is not
289 known to be used. If you have device vxge in your kernel config file
293 The amd64 kernel now requires a ld that supports ifunc to produce a
294 working kernel, either lld or a newer binutils. lld is built by default
295 on amd64, and the 'buildkernel' target uses it automatically. However,
296 it is not the default linker, so building the kernel the traditional
297 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
298 binutils port/package). lld will soon be default, and this requirement
301 NOTE: As of r334391 lld is the default system linker on amd64, and no
302 workaround is necessary.
305 The nxge(4) driver has been removed. This driver was for PCI-X 10g
306 cards made by s2io/Neterion. The company was aquired by Exar and
307 no longer sells or supports Ethernet products. If you have device
308 nxge in your kernel config file it must be removed.
311 The tz database (tzdb) has been updated to 2018e. This version more
312 correctly models time stamps in time zones with negative DST such as
313 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
314 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
315 time zone abbreviations and the tm_isdst flag.
318 The ixgb(4) driver has been removed. This driver was for an early and
319 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
320 quickly shifted to the long lived ixgbe family. If you have device
321 ixgb in your kernel config file it must be removed.
324 The lmc(4) driver has been removed. This was a WAN interface
325 card that was already reportedly rare in 2003, and had an ambiguous
326 license. If you have device lmc in your kernel config file it must
330 Support for Arcnet networks has been removed. If you have device
331 arcnet or device cm in your kernel config file they must be
335 Support for FDDI networks has been removed. If you have device
336 fddi or device fpa in your kernel config file they must be
340 In addition to supporting RFC 3164 formatted messages, the
341 syslogd(8) service is now capable of parsing RFC 5424 formatted
342 log messages. The main benefit of using RFC 5424 is that clients
343 may now send log messages with timestamps containing year numbers,
344 microseconds and time zone offsets.
346 Similarly, the syslog(3) C library function has been altered to
347 send RFC 5424 formatted messages to the local system logging
348 daemon. On systems using syslogd(8), this change should have no
349 negative impact, as long as syslogd(8) and the C library are
350 updated at the same time. On systems using a different system
351 logging daemon, it may be necessary to make configuration
352 adjustments, depending on the software used.
354 When using syslog-ng, add the 'syslog-protocol' flag to local
355 input sources to enable parsing of RFC 5424 formatted messages:
358 unix-dgram("/var/run/log" flags(syslog-protocol));
361 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
362 of the 'imuxsock' module to let messages be processed by the
363 regular RFC 3164/5424 parsing pipeline:
365 module(load="imuxsock" SysSock.UseSpecialParser="off")
367 Do note that these changes only affect communication between local
368 applications and syslogd(8). The format that syslogd(8) uses to
369 store messages on disk or forward messages to other systems
370 remains unchanged. syslogd(8) still uses RFC 3164 for these
371 purposes. Options to customize this behaviour will be added in the
372 future. Utilities that process log files stored in /var/log are
373 thus expected to continue to function as before.
375 __FreeBSD_version has been incremented to 1200061 to denote this
379 Support for token ring networks has been removed. If you
380 have "device token" in your kernel config you should remove
381 it. No device drivers supported token ring.
384 makefs was modified to be able to tag ISO9660 El Torito boot catalog
385 entries as EFI instead of overloading the i386 tag as done previously.
386 The amd64 mkisoimages.sh script used to build amd64 ISO images for
387 release was updated to use this. This may mean that makefs must be
388 updated before "make cdrom" can be run in the release directory. This
389 should be as simple as:
391 $ cd $SRCDIR/usr.sbin/makefs
392 $ make depend all install
395 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
396 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
397 Co-existance for the transition period will come shortly. Booting is a
398 complex environment and test coverage for Lua-enabled loaders has been
399 thin, so it would be prudent to assume it might not work and make
400 provisions for backup boot methods.
403 devmatch functionality has been turned on in devd. It will automatically
404 load drivers for unattached devices. This may cause unexpected drivers to
405 be loaded. Please report any problems to current@ and imp@freebsd.org.
408 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
409 6.0.0. Please see the 20141231 entry below for information about
410 prerequisites and upgrading, if you are not already using clang 3.5.0
414 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
415 This means it is used to link the kernel and userland libraries and
416 executables, but is not yet installed as /usr/bin/ld by default.
418 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
419 WITHOUT_LLD_BOOTSTRAP=yes
422 On i386, pmtimer has been removed. Its functionality has been folded
423 into apm. It was a no-op on ACPI in current for a while now (but was still
424 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
425 from kernel config files.
428 The use of RSS hash from the network card aka flowid has been
429 disabled by default for lagg(4) as it's currently incompatible with
430 the lacp and loadbalance protocols.
432 This can be re-enabled by setting the following in loader.conf:
433 net.link.lagg.default_use_flowid="1"
436 The SW_WATCHDOG option is no longer necessary to enable the
437 hardclock-based software watchdog if no hardware watchdog is
438 configured. As before, SW_WATCHDOG will cause the software
439 watchdog to be enabled even if a hardware watchdog is configured.
442 r326887 fixes the issue described in the 20171214 UPDATING entry.
443 r326888 flips the switch back to building GELI support always.
446 r362593 broke ZFS + GELI support for reasons unknown. However,
447 it also broke ZFS support generally, so GELI has been turned off
448 by default as the lesser evil in r326857. If you boot off ZFS and/or
449 GELI, it might not be a good time to update.
452 PowerPC users must update loader(8) by rebuilding world before
453 installing a new kernel, as the protocol connecting them has
454 changed. Without the update, loader metadata will not be passed
455 successfully to the kernel and users will have to enter their
456 root partition at the kernel mountroot prompt to continue booting.
457 Newer versions of loader can boot old kernels without issue.
460 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
461 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
462 to WITH/OUT_LOADER_GELI.
465 The naive and non-compliant support of posix_fallocate(2) in ZFS
466 has been removed as of r325320. The system call now returns EINVAL
467 when used on a ZFS file. Although the new behavior complies with the
468 standard, some consumers are not prepared to cope with it.
469 One known victim is lld prior to r325420.
472 Building in a FreeBSD src checkout will automatically create object
473 directories now rather than store files in the current directory if
474 'make obj' was not ran. Calling 'make obj' is no longer necessary.
475 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
476 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
480 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
481 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
482 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
483 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
484 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
485 The UNIFIED_OBJDIR option is a transitional feature that will be
486 removed for 12.0 release; please migrate to the new format for any
487 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
488 than hardcoding paths.
491 The native-xtools target no longer installs the files by default to the
492 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
493 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
496 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
497 options are changing from controlling the build if defined / undefined
498 to controlling the build with explicit 'yes' or 'no' values. They will
499 shift to WITH/WITHOUT options to match other options in the system.
502 libstand has turned into a private library for sys/boot use only.
503 It is no longer supported as a public interface outside of sys/boot.
506 The arm port has split armv6 into armv6 and armv7. armv7 is now
507 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
508 and are running a kernel from before r324363, you will need to add
509 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
512 When building multiple kernels using KERNCONF, non-existent KERNCONF
513 files will produce an error and buildkernel will fail. Previously
514 missing KERNCONF files silently failed giving no indication as to
515 why, only to subsequently discover during installkernel that the
516 desired kernel was never built in the first place.
519 The default serial number format for CTL LUNs has changed. This will
520 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
521 or iSCSI clients care about their LUNs' serial numbers. Users who
522 require serial number stability should hardcode serial numbers in
526 For 32-bit arm compiled for hard-float support, soft-floating point
527 binaries now always get their shared libraries from
528 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
529 /usr/libsoft also existed). Only users with a hard-float ld.so, but
530 soft-float everything else should be affected.
533 The geli password typed at boot is now hidden. To restore the previous
534 behavior, see geli(8) for configuration options.
537 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
538 sysctl values. Minor nit, but requires a rebuild of both world/kernel
542 "make check" behavior (made in ^/head@r295380) has been changed to
543 execute from a limited sandbox, as opposed to executing from
547 - The "beforecheck" and "aftercheck" targets are now specified.
548 - ${CHECKDIR} (added in commit noted above) has been removed.
549 - Legacy behavior can be enabled by setting
550 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
552 If the limited sandbox mode is enabled, "make check" will execute
553 "make distribution", then install, execute the tests, and clean up the
554 sandbox if successful.
556 The "make distribution" and "make install" targets are typically run as
557 root to set appropriate permissions and ownership at installation time.
558 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
559 environment if executing "make check" with limited sandbox mode using
560 an unprivileged user.
563 Since the switch to GPT disk labels, fsck for UFS/FFS has been
564 unable to automatically find alternate superblocks. As of r322297,
565 the information needed to find alternate superblocks has been
566 moved to the end of the area reserved for the boot block.
567 Filesystems created with a newfs of this vintage or later
568 will create the recovery information. If you have a filesystem
569 created prior to this change and wish to have a recovery block
570 created for your filesystem, you can do so by running fsck in
571 foreground mode (i.e., do not use the -p or -y options). As it
572 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
573 to which you should answer yes.
576 As of r321665, an NFSv4 server configuration that services
577 Kerberos mounts or clients that do not support the uid/gid in
578 owner/owner_group string capability, must explicitly enable
579 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
580 machine's /etc/rc.conf file.
583 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
584 Please see the 20141231 entry below for information about prerequisites
585 and upgrading, if you are not already using clang 3.5.0 or higher.
588 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
589 r-commands (rlogin, rsh, etc.) to be built with the base system.
592 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
593 a very major ABI incompatible change, so users of FreeBSD/powerpc must
594 be careful when performing source upgrades. It is best to run
595 'make installworld' from an alternate root system, either a live
596 CD/memory stick, or a temporary root partition. Additionally, all ports
597 must be recompiled. powerpc64 is largely unaffected, except in the case
598 of 32-bit compatibility. All 32-bit binaries will be affected.
601 Forward compatibility for the "ino64" project have been committed. This
602 will allow most new binaries to run on older kernels in a limited
603 fashion. This prevents many of the common foot-shooting actions in the
604 upgrade as well as the limited ability to roll back the kernel across
605 the ino64 upgrade. Complicated use cases may not work properly, though
606 enough simpler ones work to allow recovery in most situations.
609 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
610 if you require the GPL compiler.
613 The internal ABI used for communication between the NFS kernel modules
614 was changed by r320085, so __FreeBSD_version was bumped to
615 ensure all the NFS related modules are updated together.
618 The ABI of struct event was changed by extending the data
619 member to 64bit and adding ext fields. For upgrade, same
620 precautions as for the entry 20170523 "ino64" must be
624 The GNU roff toolchain has been removed from base. To render manpages
625 which are not supported by mandoc(1), man(1) can fallback on GNU roff
626 from ports (and recommends to install it).
627 To render roff(7) documents, consider using GNU roff from ports or the
628 heirloom doctools roff toolchain from ports via pkg install groff or
629 via pkg install heirloom-doctools.
632 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
633 smaller runtime footprint builds. This is useful for embedded systems
634 which only require one chipset support.
636 If you load it as a module, make sure this is in /boot/loader.conf:
640 This will load the HAL, all chip/RF backends and if_ath_pci.
641 If you have if_ath_pci in /boot/loader.conf, ensure it is after
642 if_ath or it will not load any HAL chipset support.
644 If you want to selectively load things (eg on ye cheape ARM/MIPS
645 platforms where RAM is at a premium) you should:
648 * load the chip modules in question
649 * load ath_rate, ath_dfs
651 * load if_ath_pci and/or if_ath_ahb depending upon your particular
652 bus bind type - this is where probe/attach is done.
654 For further comments/feedback, poke adrian@ .
657 The "ino64" 64-bit inode project has been committed, which extends
658 a number of types to 64 bits. Upgrading in place requires care and
659 adherence to the documented upgrade procedure.
661 If using a custom kernel configuration ensure that the
662 COMPAT_FREEBSD11 option is included (as during the upgrade the
663 system will be running the ino64 kernel with the existing world).
665 For the safest in-place upgrade begin by removing previous build
666 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
667 full procedure documented below under the heading "To rebuild
668 everything and install it on the current system." Specifically,
669 a reboot is required after installing the new kernel before
673 The NATM framework including the en(4), fatm(4), hatm(4), and
674 patm(4) devices has been removed. Consumers should plan a
675 migration before the end-of-life date for FreeBSD 11.
678 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
679 diff has not been implemented, if those are needed a newer version of
680 GNU diff is available via the diffutils package under the gdiff name.
683 As of r316810 for ipfilter, keep frags is no longer assumed when
684 keep state is specified in a rule. r316810 aligns ipfilter with
685 documentation in man pages separating keep frags from keep state.
686 This allows keep state to be specified without forcing keep frags
687 and allows keep frags to be specified independently of keep state.
688 To maintain previous behaviour, also specify keep frags with
689 keep state (as documented in ipf.conf.5).
692 arm64 builds now use the base system LLD 4.0.0 linker by default,
693 instead of requiring that the aarch64-binutils port or package be
694 installed. To continue using aarch64-binutils, set
695 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
698 The UDP optimization in entry 20160818 that added the sysctl
699 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
700 packets will no longer be treated as L3 broadcast packets.
703 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
704 use any explicitly assigned loopback address available in the jail
705 instead of using the first assigned address of the jail.
708 The ctl.ko module no longer implements the iSCSI target frontend:
709 cfiscsi.ko does instead.
711 If building cfiscsi.ko as a kernel module, the module can be loaded
712 via one of the following methods:
713 - `cfiscsi_load="YES"` in loader.conf(5).
714 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
715 - ctladm(8)/ctld(8), when compiled with iSCSI support
716 (`WITH_ISCSI=yes` in src.conf(5))
718 Please see cfiscsi(4) for more details.
721 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
722 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
723 same source (previously, the dependency of mmcsd.ko on mmc.ko was
724 missing, but mmcsd.ko now will refuse to load if it is incompatible
728 The syntax of ipfw(8) named states was changed to avoid ambiguity.
729 If you have used named states in the firewall rules, you need to modify
730 them after installworld and before rebooting. Now named states must
731 be prefixed with colon.
734 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
735 removed as the userland we provide cannot use them. The KMS version
736 (sys/dev/drm2) supports the same hardware.
739 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
740 Please see the 20141231 entry below for information about prerequisites
741 and upgrading, if you are not already using clang 3.5.0 or higher.
744 The code that provides support for ZFS .zfs/ directory functionality
745 has been reimplemented. It's not possible now to create a snapshot
746 by mkdir under .zfs/snapshot/. That should be the only user visible
750 EISA bus support has been removed. The WITH_EISA option is no longer
754 MCA bus support has been removed.
757 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
758 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
761 The EM_MULTIQUEUE kernel configuration option is deprecated now that
762 the em(4) driver conforms to iflib specifications.
765 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
766 IFLIB. If you have a custom kernel configuration that excludes em(4)
767 but you use igb(4), you need to re-add em(4) to your custom configuration.
770 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
771 Please see the 20141231 entry below for information about prerequisites
772 and upgrading, if you are not already using clang 3.5.0 or higher.
775 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
776 Please see the 20141231 entry below for information about prerequisites
777 and upgrading, if you are not already using clang 3.5.0 or higher.
780 The layout of the pmap structure has changed for powerpc to put the pmap
781 statistics at the front for all CPU variations. libkvm(3) and all tools
782 that link against it need to be recompiled.
785 isl(4) and cyapa(4) drivers now require a new driver,
786 chromebook_platform(4), to work properly on Chromebook-class hardware.
787 On other types of hardware the drivers may need to be configured using
788 device hints. Please see the corresponding manual pages for details.
791 The urtwn(4) driver was merged into rtwn(4) and now consists of
792 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
794 Also, firmware for RTL8188CE was renamed due to possible name
795 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
798 GNU rcs has been removed from base. It is available as packages:
799 - rcs: Latest GPLv3 GNU rcs version.
800 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
804 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
805 modules now requires that the kernel configuration contain the
806 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
809 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
810 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
813 Relocatable object files with the extension of .So have been renamed
814 to use an extension of .pico instead. The purpose of this change is
815 to avoid a name clash with shared libraries on case-insensitive file
816 systems. On those file systems, foo.So is the same file as foo.so.
819 GNU rcs has been turned off by default. It can (temporarily) be built
820 again by adding WITH_RCS knob in src.conf.
821 Otherwise, GNU rcs is available from packages:
822 - rcs: Latest GPLv3 GNU rcs version.
823 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
826 The backup_uses_rcs functionality has been removed from rc.subr.
829 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
830 two separate components, QUEUE_MACRO_DEBUG_TRACE and
831 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
832 QUEUE_MACRO_DEBUG behavior.
835 r304787 changed some ioctl interfaces between the iSCSI userspace
836 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
837 rebuilt to work with new kernels. __FreeBSD_version has been bumped
841 The UDP receive code has been updated to only treat incoming UDP
842 packets that were addressed to an L2 broadcast address as L3
843 broadcast packets. It is not expected that this will affect any
844 standards-conforming UDP application. The new behaviour can be
845 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
849 Remove the openbsd_poll system call.
850 __FreeBSD_version has been bumped because of this.
853 The stable/11 branch has been created from head@r302406.
856 The libc stub for the pipe(2) system call has been replaced with
857 a wrapper that calls the pipe2(2) system call and the pipe(2)
858 system call is now only implemented by the kernels that include
859 "options COMPAT_FREEBSD10" in their config file (this is the
860 default). Users should ensure that this option is enabled in
861 their kernel or upgrade userspace to r302092 before upgrading their
865 CAM will now strip leading spaces from SCSI disks' serial numbers.
866 This will affect users who create UFS filesystems on SCSI disks using
867 those disk's diskid device nodes. For example, if /etc/fstab
868 previously contained a line like
869 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
870 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
871 transforms like gmirror may also be affected. ZFS users should
875 The bitstring(3) API has been updated with new functionality and
876 improved performance. But it is binary-incompatible with the old API.
877 Objects built with the new headers may not be linked against objects
878 built with the old headers.
881 The brk and sbrk functions have been removed from libc on arm64.
882 Binutils from ports has been updated to not link to these
883 functions and should be updated to the latest version before
884 installing a new libc.
887 The armv6 port now defaults to hard float ABI. Limited support
888 for running both hardfloat and soft float on the same system
889 is available using the libraries installed with -DWITH_LIBSOFT.
890 This has only been tested as an upgrade path for installworld
891 and packages may fail or need manual intervention to run. New
892 packages will be needed.
894 To update an existing self-hosted armv6hf system, you must add
895 TARGET_ARCH=armv6 on the make command line for both the build
896 and the install steps.
899 Kernel modules compiled outside of a kernel build now default to
900 installing to /boot/modules instead of /boot/kernel. Many kernel
901 modules built this way (such as those in ports) already overrode
902 KMODDIR explicitly to install into /boot/modules. However,
903 manually building and installing a module from /sys/modules will
904 now install to /boot/modules instead of /boot/kernel.
907 The CAM I/O scheduler has been committed to the kernel. There should be
908 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
909 list of known rogues that claim support for this but actually corrupt
910 data is believed to be complete, be on the lookout for data
911 corruption. The known rogue list is believed to be complete:
913 o Crucial MX100, M550 drives with MU01 firmware.
914 o Micron M510 and M550 drives with MU01 firmware.
915 o Micron M500 prior to MU07 firmware
916 o Samsung 830, 840, and 850 all firmwares
917 o FCCT M500 all firmwares
919 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
920 with working NCQ TRIM. For Micron branded drives, see your sales rep for
921 updated firmware. Black listed drives will work correctly because these
922 drives work correctly so long as no NCQ TRIMs are sent to them. Given
923 this list is the same as found in Linux, it's believed there are no
924 other rogues in the market place. All other models from the above
927 To be safe, if you are at all concerned, you can quirk each of your
928 drives to prevent NCQ from being sent by setting:
929 kern.cam.ada.X.quirks="0x2"
930 in loader.conf. If the drive requires the 4k sector quirk, set the
934 The FAST_DEPEND build option has been removed and its functionality is
935 now the one true way. The old mkdep(1) style of 'make depend' has
936 been removed. See 20160311 for further details.
939 Resource range types have grown from unsigned long to uintmax_t. All
940 drivers, and anything using libdevinfo, need to be recompiled.
943 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
944 builds. It no longer runs mkdep(1) during 'make depend', and the
945 'make depend' stage can safely be skipped now as it is auto ran
946 when building 'make all' and will generate all SRCS and DPSRCS before
947 building anything else. Dependencies are gathered at compile time with
948 -MF flags kept in separate .depend files per object file. Users should
949 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
953 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
954 kernel modules. Therefore, if you load any kernel modules at boot time,
955 please install the boot loaders after you install the kernel, but before
959 make buildkernel KERNCONF=YOUR_KERNEL_HERE
960 make installkernel KERNCONF=YOUR_KERNEL_HERE
961 make -C sys/boot install
962 <reboot in single user>
964 Then follow the usual steps, described in the General Notes section,
968 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
969 see the 20141231 entry below for information about prerequisites and
970 upgrading, if you are not already using clang 3.5.0 or higher.
973 The AIO subsystem is now a standard part of the kernel. The
974 VFS_AIO kernel option and aio.ko kernel module have been removed.
975 Due to stability concerns, asynchronous I/O requests are only
976 permitted on sockets and raw disks by default. To enable
977 asynchronous I/O requests on all file types, set the
978 vfs.aio.enable_unsafe sysctl to a non-zero value.
981 The ELF object manipulation tool objcopy is now provided by the
982 ELF Tool Chain project rather than by GNU binutils. It should be a
983 drop-in replacement, with the addition of arm64 support. The
984 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
985 to obtain the GNU version if necessary.
988 Building ZFS pools on top of zvols is prohibited by default. That
989 feature has never worked safely; it's always been prone to deadlocks.
990 Using a zvol as the backing store for a VM guest's virtual disk will
991 still work, even if the guest is using ZFS. Legacy behavior can be
992 restored by setting vfs.zfs.vol.recursive=1.
995 The NONE and HPN patches has been removed from OpenSSH. They are
996 still available in the security/openssh-portable port.
999 With the addition of ypldap(8), a new _ypldap user is now required
1000 during installworld. "mergemaster -p" can be used to add the user
1001 prior to installworld, as documented in the handbook.
1004 The tftp loader (pxeboot) now uses the option root-path directive. As a
1005 consequence it no longer looks for a pxeboot.4th file on the tftp
1006 server. Instead it uses the regular /boot infrastructure as with the
1010 The code to start recording plug and play data into the modules has
1011 been committed. While the old tools will properly build a new kernel,
1012 a number of warnings about "unknown metadata record 4" will be produced
1013 for an older kldxref. To avoid such warnings, make sure to rebuild
1014 the kernel toolchain (or world). Make sure that you have r292078 or
1015 later when trying to build 292077 or later before rebuilding.
1018 Debug data files are now built by default with 'make buildworld' and
1019 installed with 'make installworld'. This facilitates debugging but
1020 requires more disk space both during the build and for the installed
1021 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1025 r291527 changed the internal interface between the nfsd.ko and
1026 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1027 __FreeBSD_version has been bumped because of this.
1030 Add support for unicode collation strings leads to a change of
1031 order of files listed by ls(1) for example. To get back to the old
1032 behaviour, set LC_COLLATE environment variable to "C".
1034 Databases administrators will need to reindex their databases given
1035 collation results will be different.
1037 Due to a bug in install(1) it is recommended to remove the ancient
1038 locales before running make installworld.
1040 rm -rf /usr/share/locale/*
1043 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1044 libcrypto.so.7 or libssl.so.7 must be recompiled.
1047 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1048 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1049 should be replaced with isp_2400 and isp_2500 modules respectively.
1052 The build previously allowed using 'make -n' to not recurse into
1053 sub-directories while showing what commands would be executed, and
1054 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1055 and 'make -N' will not.
1058 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1059 and etcupdate will now use this file. A custom sendmail.cf is now
1060 updated via this mechanism rather than via installworld. If you had
1061 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1062 want to remove the exclusion or change it to "always install".
1063 /etc/mail/sendmail.cf is now managed the same way regardless of
1064 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1065 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1068 Compatibility shims for legacy ATA device names have been removed.
1069 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1070 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1071 environment variables, /dev/ad* and /dev/ar* symbolic links.
1074 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1075 Please see the 20141231 entry below for information about prerequisites
1076 and upgrading, if you are not already using clang 3.5.0 or higher.
1079 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1080 and renamed from .symbols to .debug. This reduces the size requirements
1081 on the boot partition or file system and provides consistency with
1082 userland debug files.
1084 When using the supported kernel installation method the
1085 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1086 as is done with /boot/kernel.
1088 Developers wishing to maintain the historical behavior of installing
1089 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1092 The wireless drivers had undergone changes that remove the 'parent
1093 interface' from the ifconfig -l output. The rc.d network scripts
1094 used to check presence of a parent interface in the list, so old
1095 scripts would fail to start wireless networking. Thus, etcupdate(3)
1096 or mergemaster(8) run is required after kernel update, to update your
1097 rc.d scripts in /etc.
1100 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1101 These configurations are now automatically interpreted as
1102 'scrub fragment reassemble'.
1105 Kernel-loadable modules for the random(4) device are back. To use
1106 them, the kernel must have
1109 options RANDOM_LOADABLE
1111 kldload(8) can then be used to load random_fortuna.ko
1112 or random_yarrow.ko. Please note that due to the indirect
1113 function calls that the loadable modules need to provide,
1114 the build-in variants will be slightly more efficient.
1116 The random(4) kernel option RANDOM_DUMMY has been retired due to
1117 unpopularity. It was not all that useful anyway.
1120 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1121 Control over building the ELF Tool Chain tools is now provided by
1122 the WITHOUT_TOOLCHAIN knob.
1125 The polarity of Pulse Per Second (PPS) capture events with the
1126 uart(4) driver has been corrected. Prior to this change the PPS
1127 "assert" event corresponded to the trailing edge of a positive PPS
1128 pulse and the "clear" event was the leading edge of the next pulse.
1130 As the width of a PPS pulse in a typical GPS receiver is on the
1131 order of 1 millisecond, most users will not notice any significant
1132 difference with this change.
1134 Anyone who has compensated for the historical polarity reversal by
1135 configuring a negative offset equal to the pulse width will need to
1136 remove that workaround.
1139 The default group assigned to /dev/dri entries has been changed
1140 from 'wheel' to 'video' with the id of '44'. If you want to have
1141 access to the dri devices please add yourself to the video group
1144 # pw groupmod video -m $USER
1147 The menu.rc and loader.rc files will now be replaced during
1148 upgrades. Please migrate local changes to menu.rc.local and
1149 loader.rc.local instead.
1152 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1153 strings and strip have been removed. The src.conf(5) knob
1154 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1157 As ZFS requires more kernel stack pages than is the default on some
1158 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1159 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1161 Please consider using 'options KSTACK_PAGES=X' where X is greater
1162 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1165 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1166 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1167 default, i.e., they will not contain "::". For example, instead
1168 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1169 to have a more specific match, such as different map entries for
1170 IPv6:0:0 vs IPv6:0. This change requires that configuration
1171 data (including maps, files, classes, custom ruleset, etc.) must
1172 use the same format, so make certain such configuration data is
1173 upgrading. As a very simple check search for patterns like
1174 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1175 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1176 the cf option UseCompressedIPv6Addresses.
1179 The default kernel entropy-processing algorithm is now
1180 Fortuna, replacing Yarrow.
1182 Assuming you have 'device random' in your kernel config
1183 file, the configurations allow a kernel option to override
1184 this default. You may choose *ONE* of:
1186 options RANDOM_YARROW # Legacy /dev/random algorithm.
1187 options RANDOM_DUMMY # Blocking-only driver.
1189 If you have neither, you get Fortuna. For most people,
1190 read no further, Fortuna will give a /dev/random that works
1191 like it always used to, and the difference will be irrelevant.
1193 If you remove 'device random', you get *NO* kernel-processed
1194 entropy at all. This may be acceptable to folks building
1195 embedded systems, but has complications. Carry on reading,
1196 and it is assumed you know what you need.
1198 *PLEASE* read random(4) and random(9) if you are in the
1199 habit of tweaking kernel configs, and/or if you are a member
1200 of the embedded community, wanting specific and not-usual
1201 behaviour from your security subsystems.
1203 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1204 random', you will NOT have a functioning /dev/random, and
1205 many cryptographic features will not work, including SSH.
1206 You may also find strange behaviour from the random(3) set
1207 of library functions, in particular sranddev(3), srandomdev(3)
1208 and arc4random(3). The reason for this is that the KERN_ARND
1209 sysctl only returns entropy if it thinks it has some to
1210 share, and with RANDOM_DUMMY or no 'device random' this
1214 An additional fix for the issue described in the 20150614 sendmail
1215 entry below has been committed in revision 284717.
1218 FreeBSD's old make (fmake) has been removed from the system. It is
1219 available as the devel/fmake port or via pkg install fmake.
1222 The fix for the issue described in the 20150614 sendmail entry
1223 below has been committed in revision 284436. The work
1224 around described in that entry is no longer needed unless the
1225 default setting is overridden by a confDH_PARAMETERS configuration
1226 setting of '5' or pointing to a 512 bit DH parameter file.
1229 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1230 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1231 and devel/kyua to version 0.20+ and adjust any calling code to work
1232 with Kyuafile and kyua.
1235 The import of openssl to address the FreeBSD-SA-15:10.openssl
1236 security advisory includes a change which rejects handshakes
1237 with DH parameters below 768 bits. sendmail releases prior
1238 to 8.15.2 (not yet released), defaulted to a 512 bit
1239 DH parameter setting for client connections. To work around
1240 this interoperability, sendmail can be configured to use a
1241 2048 bit DH parameter by:
1243 1. Edit /etc/mail/`hostname`.mc
1244 2. If a setting for confDH_PARAMETERS does not exist or
1245 exists and is set to a string beginning with '5',
1246 replace it with '2'.
1247 3. If a setting for confDH_PARAMETERS exists and is set to
1248 a file path, create a new file with:
1249 openssl dhparam -out /path/to/file 2048
1250 4. Rebuild the .cf file:
1251 cd /etc/mail/; make; make install
1252 5. Restart sendmail:
1253 cd /etc/mail/; make restart
1255 A sendmail patch is coming, at which time this file will be
1259 Generation of legacy formatted entries have been disabled by default
1260 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1261 entries were converted to use the new format by default when the new,
1262 machine independent format have been added and supported since FreeBSD
1265 Please see the pwd_mkdb(8) manual page for further details.
1268 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1269 20141231 entry below for information about prerequisites and upgrading,
1270 if you are not already using 3.5.0 or higher.
1273 TI platform code switched to using vendor DTS files and this update
1274 may break existing systems running on Beaglebone, Beaglebone Black,
1277 - dtb files should be regenerated/reinstalled. Filenames are the
1278 same but content is different now
1279 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1280 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1281 addressing scheme is now pin 25 on /dev/gpioc3.
1282 - Pandaboard: /etc/ttys should be updated, serial console device is
1283 now /dev/ttyu2, not /dev/ttyu0
1286 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1287 If you need the GNU extension from groff soelim(1), install groff
1288 from package: pkg install groff, or via ports: textproc/groff.
1291 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1292 defined in symlink(7); previously symlinks were silently ignored.
1295 The const qualifier has been removed from iconv(3) to comply with
1296 POSIX. The ports tree is aware of this from r384038 onwards.
1299 Libraries specified by LIBADD in Makefiles must have a corresponding
1300 DPADD_<lib> variable to ensure correct dependencies. This is now
1301 enforced in src.libnames.mk.
1304 From legacy ata(4) driver was removed support for SATA controllers
1305 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1306 Kernel modules ataahci and ataadaptec were removed completely,
1307 replaced by ahci and mvs modules respectively.
1310 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1311 the 20141231 entry below for information about prerequisites and
1312 upgrading, if you are not already using 3.5.0 or higher.
1315 The 32-bit PowerPC kernel has been changed to a position-independent
1316 executable. This can only be booted with a version of loader(8)
1317 newer than January 31, 2015, so make sure to update both world and
1318 kernel before rebooting.
1321 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1322 but before r278950, the RNG was not seeded properly. Immediately
1323 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1324 ssh keys or openssl keys) that were generated w/ a kernel from that
1325 range. This does not affect programs that directly used /dev/random
1326 or /dev/urandom. All userland uses of arc4random(3) are affected.
1329 The autofs(4) ABI was changed in order to restore binary compatibility
1330 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1331 with the new kernel.
1334 The powerpc64 kernel has been changed to a position-independent
1335 executable. This can only be booted with a new version of loader(8),
1336 so make sure to update both world and kernel before rebooting.
1339 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1340 only release, no new features have been added. Please see the 20141231
1341 entry below for information about prerequisites and upgrading, if you
1342 are not already using 3.5.0.
1345 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1346 taken from the ELF Tool Chain project rather than GNU binutils. They
1347 should be drop-in replacements, with the addition of arm64 support.
1348 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1349 binutils tools, if necessary. See 20150805 for updated information.
1352 The default Unbound configuration now enables remote control
1353 using a local socket. Users who have already enabled the
1354 local_unbound service should regenerate their configuration
1355 by running "service local_unbound setup" as root.
1358 The GNU texinfo and GNU info pages have been removed.
1359 To be able to view GNU info pages please install texinfo from ports.
1362 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1364 As of this release, a prerequisite for building clang, llvm and lldb is
1365 a C++11 capable compiler and C++11 standard library. This means that to
1366 be able to successfully build the cross-tools stage of buildworld, with
1367 clang as the bootstrap compiler, your system compiler or cross compiler
1368 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1369 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1372 On any standard FreeBSD 10.x or 11.x installation, where clang and
1373 libc++ are on by default (that is, on x86 or arm), this should work out
1376 On 9.x installations where clang is enabled by default, e.g. on x86 and
1377 powerpc, libc++ will not be enabled by default, so libc++ should be
1378 built (with clang) and installed first. If both clang and libc++ are
1379 missing, build clang first, then use it to build libc++.
1381 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1382 the instructions for 9.x above.
1384 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1385 default, and do not build clang.
1387 Many embedded systems are resource constrained, and will not be able to
1388 build clang in a reasonable time, or in some cases at all. In those
1389 cases, cross building bootable systems on amd64 is a workaround.
1391 This new version of clang introduces a number of new warnings, of which
1392 the following are most likely to appear:
1396 This warns in two cases, for both C and C++:
1397 * When the code is trying to take the absolute value of an unsigned
1398 quantity, which is effectively a no-op, and almost never what was
1399 intended. The code should be fixed, if at all possible. If you are
1400 sure that the unsigned quantity can be safely cast to signed, without
1401 loss of information or undefined behavior, you can add an explicit
1402 cast, or disable the warning.
1404 * When the code is trying to take an absolute value, but the called
1405 abs() variant is for the wrong type, which can lead to truncation.
1406 If you want to disable the warning instead of fixing the code, please
1407 make sure that truncation will not occur, or it might lead to unwanted
1410 -Wtautological-undefined-compare and
1411 -Wundefined-bool-conversion
1413 These warn when C++ code is trying to compare 'this' against NULL, while
1414 'this' should never be NULL in well-defined C++ code. However, there is
1415 some legacy (pre C++11) code out there, which actively abuses this
1416 feature, which was less strictly defined in previous C++ versions.
1418 Squid and openjdk do this, for example. The warning can be turned off
1419 for C++98 and earlier, but compiling the code in C++11 mode might result
1420 in unexpected behavior; for example, the parts of the program that are
1421 unreachable could be optimized away.
1424 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1425 kernel sources have been removed. The .h files remain, since some
1426 utilities include them. This will need to be fixed later.
1427 If "mount -t oldnfs ..." is attempted, it will fail.
1428 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1429 the utilities will report errors.
1432 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1433 directories to top level SUBDIR variable when their parent
1434 directory is included in LOCAL_DIRS. Users with build systems with
1435 such hierarchies and without SUBDIR entries in the parent
1436 directory Makefiles should add them or add the directories to
1440 faith(4) and faithd(8) have been removed from the base system. Faith
1441 has been obsolete for a very long time.
1444 vt(4), the new console driver, is enabled by default. It brings
1445 support for Unicode and double-width characters, as well as
1446 support for UEFI and integration with the KMS kernel video
1449 You may need to update your console settings in /etc/rc.conf,
1450 most probably the keymap. During boot, /etc/rc.d/syscons will
1451 indicate what you need to do.
1453 vt(4) still has issues and lacks some features compared to
1454 syscons(4). See the wiki for up-to-date information:
1455 https://wiki.freebsd.org/Newcons
1457 If you want to keep using syscons(4), you can do so by adding
1458 the following line to /boot/loader.conf:
1462 pjdfstest has been integrated into kyua as an opt-in test suite.
1463 Please see share/doc/pjdfstest/README for more details on how to
1467 gperf has been removed from the base system for architectures
1468 that use clang. Ports that require gperf will obtain it from the
1472 pjdfstest has been moved from tools/regression/pjdfstest to
1476 At svn r271982, The default linux compat kernel ABI has been adjusted
1477 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1478 update. If you wish to continue using the linux-f10 compat ports,
1479 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1480 encouraged to update their linux-compat packages to linux-c6 during
1481 their next update cycle.
1484 The ofwfb driver, used to provide a graphics console on PowerPC when
1485 using vt(4), no longer allows mmap() of all physical memory. This
1486 will prevent Xorg on PowerPC with some ATI graphics cards from
1487 initializing properly unless x11-servers/xorg-server is updated to
1491 The xdev targets have been converted to using TARGET and
1492 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1495 The default unbound configuration has been modified to address
1496 issues with reverse lookups on networks that use private
1497 address ranges. If you use the local_unbound service, run
1498 "service local_unbound setup" as root to regenerate your
1499 configuration, then "service local_unbound reload" to load the
1503 The GNU texinfo and GNU info pages are not built and installed
1504 anymore, WITH_INFO knob has been added to allow to built and install
1506 UPDATE: see 20150102 entry on texinfo's removal
1509 The GNU readline library is now an INTERNALLIB - that is, it is
1510 statically linked into consumers (GDB and variants) in the base
1511 system, and the shared library is no longer installed. The
1512 devel/readline port is available for third party software that
1516 The Itanium architecture (ia64) has been removed from the list of
1517 known architectures. This is the first step in the removal of the
1521 Commit r268115 has added NFSv4.1 server support, merged from
1522 projects/nfsv4.1-server. Since this includes changes to the
1523 internal interfaces between the NFS related modules, a full
1524 build of the kernel and modules will be necessary.
1525 __FreeBSD_version has been bumped.
1528 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1529 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1530 which differs from the behaviour controlled by this knob.)
1533 Maximal length of the serial number in CTL was increased from 16 to
1534 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1535 and ctld, need to be rebuilt to work with a new kernel.
1538 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1539 1 respectively to match the upstream numbers. They were out of
1540 sync because, when they were originally added to FreeBSD, the
1541 upstream versions were not respected. These libraries are private
1542 and not yet built by default, so renumbering them should be a
1543 non-issue. However, unclean source trees will yield broken test
1544 programs once the operator executes "make delete-old-libs" after a
1545 "make installworld".
1547 Additionally, the atf-sh binary was made private by moving it into
1548 /usr/libexec/. Already-built shell test programs will keep the
1549 path to the old binary so they will break after "make delete-old"
1552 If you are using WITH_TESTS=yes (not the default), wipe the object
1553 tree and rebuild from scratch to prevent spurious test failures.
1554 This is only needed once: the misnumbered libraries and misplaced
1555 binaries have been added to OptionalObsoleteFiles.inc so they will
1556 be removed during a clean upgrade.
1559 Clang and llvm have been upgraded to 3.4.1 release.
1562 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1563 be removed to avoid issues in the future (and has been added to
1567 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1568 past, it affected all builds that used the bsd.*.mk files. The old
1569 behavior was a bug, but people may have relied upon it. To get this
1570 behavior back, you can .include /etc/src.conf from /etc/make.conf
1571 (which is still global and isn't changed). This also changes the
1572 behavior of incremental builds inside the tree of individual
1573 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1574 Although this has survived make universe and some upgrade scenarios,
1575 other upgrade scenarios may have broken. At least one form of
1576 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1577 as well... In cases where MAKESYSPATH isn't working with this
1578 setting, you'll need to set it to the full path to your tree.
1580 One side effect of all this cleaning up is that bsd.compiler.mk
1581 is no longer implicitly included by bsd.own.mk. If you wish to
1582 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1586 The lindev device has been removed since /dev/full has been made a
1587 standard device. __FreeBSD_version has been bumped.
1590 The knob WITHOUT_VI was added to the base system, which controls
1591 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1592 in order to reorder files share/termcap and didn't build ex(1) as a
1593 build tool, so building/installing with WITH_VI is highly advised for
1594 build hosts for older releases.
1596 This issue has been fixed in stable/9 and stable/10 in r277022 and
1597 r276991, respectively.
1600 The YES_HESIOD knob has been removed. It has been obsolete for
1601 a decade. Please move to using WITH_HESIOD instead or your builds
1602 will silently lack HESIOD.
1605 The uart(4) driver has been changed with respect to its handling
1606 of the low-level console. Previously the uart(4) driver prevented
1607 any process from changing the baudrate or the CLOCAL and HUPCL
1608 control flags. By removing the restrictions, operators can make
1609 changes to the serial console port without having to reboot.
1610 However, when getty(8) is started on the serial device that is
1611 associated with the low-level console, a misconfigured terminal
1612 line in /etc/ttys will now have a real impact.
1613 Before upgrading the kernel, make sure that /etc/ttys has the
1614 serial console device configured as 3wire without baudrate to
1615 preserve the previous behaviour. E.g:
1616 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1619 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1620 to improve performance. To re-enable it, if needed, run rpcbind
1621 with command line option -W.
1624 Switched back to the GPL dtc compiler due to updates in the upstream
1625 dts files not being supported by the BSDL dtc compiler. You will need
1626 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1627 may result while building dtb files during a kernel build if you fail
1628 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1631 Clang and llvm have been upgraded to 3.4 release.
1634 The nve(4) driver has been removed. Please use the nfe(4) driver
1635 for NVIDIA nForce MCP Ethernet adapters instead.
1638 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1639 This could cause certain C++ applications using shared libraries built
1640 against the previous version of libc++ to crash. The incompatibility
1641 has now been fixed, but any C++ applications or shared libraries built
1642 between r261283 and r261801 should be recompiled.
1645 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1646 capability mode support. Please note that enabling the feature in
1647 kernel is still highly recommended.
1650 OpenSSH is now built with sandbox support, and will use sandbox as
1651 the default privilege separation method. This requires Capsicum
1652 capability mode support in kernel.
1655 The libelf and libdwarf libraries have been updated to newer
1656 versions from upstream. Shared library version numbers for
1657 these two libraries were bumped. Any ports or binaries
1658 requiring these two libraries should be recompiled.
1659 __FreeBSD_version is bumped to 1100006.
1662 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1663 instead of providing an explicit one, this would prevent such
1664 Makefile from providing its own Kyuafile in the future during
1665 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1666 intervention is needed to clean an objdir if you use NO_CLEAN:
1667 # find /usr/obj -name Kyuafile | xargs rm -f
1670 The behavior of gss_pseudo_random() for the krb5 mechanism
1671 has changed, for applications requesting a longer random string
1672 than produced by the underlying enctype's pseudo-random() function.
1673 In particular, the random string produced from a session key of
1674 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1675 be different at the 17th octet and later, after this change.
1676 The counter used in the PRF+ construction is now encoded as a
1677 big-endian integer in accordance with RFC 4402.
1678 __FreeBSD_version is bumped to 1100004.
1681 The WITHOUT_ATF build knob has been removed and its functionality
1682 has been subsumed into the more generic WITHOUT_TESTS. If you were
1683 using the former to disable the build of the ATF libraries, you
1684 should change your settings to use the latter.
1687 The default version of mtree is nmtree which is obtained from
1688 NetBSD. The output is generally the same, but may vary
1689 slightly. If you found you need identical output adding
1690 "-F freebsd9" to the command line should do the trick. For the
1691 time being, the old mtree is available as fmtree.
1694 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1695 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1696 1.1.4_8 and verify bsdyml not linked in, before running "make
1698 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1700 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1703 The stable/10 branch has been created in subversion from head
1710 Avoid using make -j when upgrading. While generally safe, there are
1711 sometimes problems using -j to upgrade. If your upgrade fails with
1712 -j, please try again without -j. From time to time in the past there
1713 have been problems using -j with buildworld and/or installworld. This
1714 is especially true when upgrading between "distant" versions (eg one
1715 that cross a major release boundary or several minor releases, or when
1716 several months have passed on the -current branch).
1718 Sometimes, obscure build problems are the result of environment
1719 poisoning. This can happen because the make utility reads its
1720 environment when searching for values for global variables. To run
1721 your build attempts in an "environmental clean room", prefix all make
1722 commands with 'env -i '. See the env(1) manual page for more details.
1724 When upgrading from one major version to another it is generally best to
1725 upgrade to the latest code in the currently installed branch first, then
1726 do an upgrade to the new branch. This is the best-tested upgrade path,
1727 and has the highest probability of being successful. Please try this
1728 approach if you encounter problems with a major version upgrade. Since
1729 the stable 4.x branch point, one has generally been able to upgrade from
1730 anywhere in the most recent stable branch to head / current (or even the
1731 last couple of stable branches). See the top of this file when there's
1734 When upgrading a live system, having a root shell around before
1735 installing anything can help undo problems. Not having a root shell
1736 around can lead to problems if pam has changed too much from your
1737 starting point to allow continued authentication after the upgrade.
1739 This file should be read as a log of events. When a later event changes
1740 information of a prior event, the prior event should not be deleted.
1741 Instead, a pointer to the entry with the new information should be
1742 placed in the old entry. Readers of this file should also sanity check
1743 older entries before relying on them blindly. Authors of new entries
1744 should write them with this in mind.
1748 When upgrading the boot ZFS pool to a new version, always follow
1751 1.) recompile and reinstall the ZFS boot loader and boot block
1752 (this is part of "make buildworld" and "make installworld")
1754 2.) update the ZFS boot block on your boot drive
1756 The following example updates the ZFS boot block on the first
1757 partition (freebsd-boot) of a GPT partitioned drive ada0:
1758 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1760 Non-boot pools do not need these updates.
1764 If you are updating from a prior version of FreeBSD (even one just
1765 a few days old), you should follow this procedure. It is the most
1766 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1768 make kernel-toolchain
1769 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1770 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1772 To test a kernel once
1773 ---------------------
1774 If you just want to boot a kernel once (because you are not sure
1775 if it works, or if you want to boot a known bad kernel to provide
1776 debugging information) run
1777 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1778 nextboot -k testkernel
1780 To rebuild everything and install it on the current system.
1781 -----------------------------------------------------------
1782 # Note: sometimes if you are running current you gotta do more than
1783 # is listed here if you are upgrading from a really old current.
1785 <make sure you have good level 0 dumps>
1787 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1788 make installkernel KERNCONF=YOUR_KERNEL_HERE
1790 <reboot in single user> [3]
1797 To cross-install current onto a separate partition
1798 --------------------------------------------------
1799 # In this approach we use a separate partition to hold
1800 # current's root, 'usr', and 'var' directories. A partition
1801 # holding "/", "/usr" and "/var" should be about 2GB in
1804 <make sure you have good level 0 dumps>
1807 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1808 <maybe newfs current's root partition>
1809 <mount current's root partition on directory ${CURRENT_ROOT}>
1810 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1811 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1812 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1813 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1814 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1815 <reboot into current>
1816 <do a "native" rebuild/install as described in the previous section>
1817 <maybe install compatibility libraries from ports/misc/compat*>
1821 To upgrade in-place from stable to current
1822 ----------------------------------------------
1823 <make sure you have good level 0 dumps>
1825 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1826 make installkernel KERNCONF=YOUR_KERNEL_HERE
1828 <reboot in single user> [3]
1835 Make sure that you've read the UPDATING file to understand the
1836 tweaks to various things you need. At this point in the life
1837 cycle of current, things change often and you are on your own
1838 to cope. The defaults can also change, so please read ALL of
1839 the UPDATING entries.
1841 Also, if you are tracking -current, you must be subscribed to
1842 freebsd-current@freebsd.org. Make sure that before you update
1843 your sources that you have read and understood all the recent
1844 messages there. If in doubt, please track -stable which has
1845 much fewer pitfalls.
1847 [1] If you have third party modules, such as vmware, you
1848 should disable them at this point so they don't crash your
1851 [3] From the bootblocks, boot -s, and then do
1856 adjkerntz -i # if CMOS is wall time
1857 Also, when doing a major release upgrade, it is required that
1858 you boot into single user mode to do the installworld.
1860 [4] Note: This step is non-optional. Failure to do this step
1861 can result in a significant reduction in the functionality of the
1862 system. Attempting to do it by hand is not recommended and those
1863 that pursue this avenue should read this file carefully, as well
1864 as the archives of freebsd-current and freebsd-hackers mailing lists
1865 for potential gotchas. The -U option is also useful to consider.
1866 See mergemaster(8) for more information.
1868 [5] Usually this step is a no-op. However, from time to time
1869 you may need to do this if you get unknown user in the following
1870 step. It never hurts to do it all the time. You may need to
1871 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1872 install) after the buildworld before this step if you last updated
1873 from current before 20130425 or from -stable before 20130430.
1875 [6] This only deletes old files and directories. Old libraries
1876 can be deleted by "make delete-old-libs", but you have to make
1877 sure that no program is using those libraries anymore.
1879 [8] In order to have a kernel that can run the 4.x binaries needed to
1880 do an installworld, you must include the COMPAT_FREEBSD4 option in
1881 your kernel. Failure to do so may leave you with a system that is
1882 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1883 required to run the 5.x binaries on more recent kernels. And so on
1884 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1886 Make sure that you merge any new devices from GENERIC since the
1887 last time you updated your kernel config file.
1889 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1890 "?=" instead of the "=" assignment operator, so that buildworld can
1891 override the CPUTYPE if it needs to.
1893 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1894 not on the command line, or in /etc/make.conf. buildworld will
1895 warn if it is improperly defined.
1898 This file contains a list, in reverse chronological order, of major
1899 breakages in tracking -current. It is not guaranteed to be a complete
1900 list of such breakages, and only contains entries since September 23, 2011.
1901 If you need to see UPDATING entries from before that date, you will need
1902 to fetch an UPDATING file from an older FreeBSD release.
1904 Copyright information:
1906 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1908 Redistribution, publication, translation and use, with or without
1909 modification, in full or in part, in any form or format of this
1910 document are permitted without further permission from the author.
1912 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1913 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1914 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1915 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1916 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1917 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1918 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1919 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1920 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1921 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1922 POSSIBILITY OF SUCH DAMAGE.
1924 Contact Warner Losh if you have any questions about your use of