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